Because each build is configured to your exact catalog, chart of accounts, tax codes and warehouse setup, this is a build-to-order plugin — not an instant download. Typical delivery is about one working week from when we receive sandbox/API access and your mapping details, depending on catalog size and how many edge cases (variations, bundles, multi-warehouse, multi-entity) we need to handle. We confirm a firm lead time with you before you pay, build on staging first, and only go live after you've verified a test order and reconciliation pass.

ECOSIRE installs the plugin and includes a post-launch support window to fix any issues and tune mappings. After that, because the plugin talks to the QuickBooks Online and Xero OAuth APIs and to WooCommerce/WordPress core — all of which release breaking changes over time — we offer an optional maintenance arrangement that keeps it compatible with new WooCommerce, HPOS, PHP, QuickBooks and Xero API versions. You always own the installed code on your site; you are never locked out of it.

It works in both directions. WooCommerce orders create invoices/sales receipts in QuickBooks or Xero, and stock changes you make in the accounting system (or via a reconciliation) flow back into WooCommerce `_stock` levels through scheduled Action Scheduler jobs. SKU mapping and idempotency keys keep both sides consistent and prevent double-counting.

Yes. The build is HPOS-aware, so it reads and writes through WooCommerce's custom order tables rather than relying only on legacy post-meta. It hooks into standard WooCommerce order actions, so it's independent of your theme and works alongside most other WooCommerce extensions. If you run WPML or multisite, we map each store/language to the correct accounting entity as part of the build.

The plugin queues sync jobs through Action Scheduler with retry and exponential back-off, so a temporary API outage doesn't lose data — the record is retried automatically. Every push and pull is written to an in-dashboard sync log with its status and payload reference, and failed records can be re-synced with one click from wp-admin. Idempotency keys ensure a retry never creates a duplicate invoice.

No — each build targets one accounting system, either QuickBooks Online or Xero, since the mapping, tax handling and API behavior differ between them. We build for whichever one you use today. If you migrate accounting platforms later, the connector layer can be re-targeted as a follow-on engagement rather than a full rebuild, since the WooCommerce side stays the same.