This is a build-to-order engagement, not an instant download. After purchase we schedule a short kickoff to collect your FBR registration details (NTN/STRN), tax categories and sandbox credentials. Typical delivery is around one working week: we build and install on a staging copy of your site, validate sample orders against FBR's sandbox, then go live on production credentials with you. The exact lead time depends on how quickly FBR API access and your tax mapping are confirmed, and we give you a firm date at kickoff.

Yes. ECOSIRE installs and supports the integration on your site. Because this is custom-built for you, we handle FBR API changes, WooCommerce/WordPress version compatibility, and fixes if the FBR schema or validation rules change. Support terms (response times and the maintenance window) are agreed in your engagement; we do not abandon you to a marketplace changelog — you have a direct line to the team that built it.

In most cases yes. The integration is designed to write the IRN, QR code and digital signature back onto the WooCommerce order so your existing PDF/print invoice plugin can render them, and to read tax from your configured WooCommerce tax classes. During the build we inspect your specific invoice and tax setup and integrate against it. If a plugin conflicts or stores data in an unusual way, we tell you honestly and propose the cleanest mapping rather than forcing a fragile workaround.

Yes. The plugin is HPOS-aware — it works whether your store uses WooCommerce's high-performance custom order tables or the legacy post-meta storage. FBR data (IRN, QR, signature, submission status) is persisted using the order storage API so it remains correct under either mode and survives a later HPOS migration.

Submission runs on order-status change and is queued, so a transient FBR outage or timeout does not break checkout. Failed or pending submissions go into a WP-Cron retry queue with backoff and re-submit automatically. The order shows a clear pending or failed flag in wp-admin, every request and response is logged to an audit table, and an operator can re-submit a single order with one click once the issue clears. If FBR returns a validation error (for example a tax or field mismatch), the message is recorded against the order so it can be corrected and resubmitted.