GCC E-Invoicing Core (Multi-Country) for WooCommerce

This is a build-to-order plugin, not an instant marketplace download. A typical single-jurisdiction build is delivered in roughly 2–4 weeks, and a multi-country configuration (for example KSA + UAE + EU) usually lands in about 4–6 weeks, depending on how many country profiles you activate and how clean your existing WooCommerce tax setup is. ECOSIRE builds it against your WordPress, WooCommerce and PHP versions, installs it on your site (we prefer to start on staging), and runs a real order through to signed UBL before you go live. You get the full source code at handover.

Because tax authorities change their schemas and access-point rules over time, the plugin includes a support and maintenance window after delivery covering bug fixes, compatibility with new WooCommerce / WordPress releases, and updates to the country profiles you purchased when a jurisdiction revises its requirements (for example a new ZATCA validation or an updated Peppol BIS version). You own the code, so your own developers can also extend it via the documented hooks. Extended/annual maintenance can be arranged separately.

Yes. The core reads and writes orders through the official WooCommerce order data store API rather than reaching into post-meta directly, so it is compatible with HPOS / custom order tables as well as the legacy storage model. Invoice metadata, signed XML and clearance responses are persisted against the order in whichever storage your store uses, and remain visible in wp-admin.

The architecture is built around pluggable country profiles, so adding a jurisdiction later is a profile activation and configuration job rather than a rewrite of your invoicing logic. We typically scope the page price around the profiles you need at build time; additional profiles (or a brand-new country we don't yet ship) are quoted as a follow-on engagement and slot into the same core engine.

It is designed to run alongside a standard WooCommerce store. It hooks into order status transitions instead of overriding checkout, uses WP-Cron for async submission so the buyer is never made to wait, and is WPML- and multisite-aware so locale and per-site configuration are respected. During the build we test against your actual theme, payment gateways and any tax/checkout plugins you run, and expose filters so edge cases in your data can be handled without patching core.