Typical delivery is around one working week from when we receive your ETA credentials, signing certificate details, and store access. The timeline depends on your catalogue size (EGS/GS1 mapping), your tax configuration, and how quickly ETA onboarding/sandbox testing clears. We confirm a firm date after a short scoping call and install on your site once sandbox submissions pass.

Every build includes a post-launch support window for bug fixes and adjustments. Because the ETA schema, code lists, and API requirements change over time, we offer continued maintenance so your submissions keep passing. We update the plugin on your site as ETA publishes new versions — this is a supported engagement, not a fire-and-forget download.

Yes. ETA e-invoicing requires your business to be registered on the ETA portal with a valid client ID/secret and an approved signing certificate (USB token, HSM, or remote signing service). You provide these; we wire them into the plugin, run the onboarding handshake, and test signing in sandbox before going live. We can advise on the options but cannot issue the certificate on your behalf.

Yes. The plugin attaches to WooCommerce order events via standard hooks, so it is theme- and gateway-independent — it triggers after an order reaches the status you choose. It supports HPOS / custom order tables and stores ETA identifiers against the order regardless of which gateway captured payment. It is also WPML- and multisite-aware if you run multiple stores.

Failed or rejected documents are not lost. They go into a WP-Cron retry queue, and the full ETA error response is shown on the order in wp-admin so your team can fix a bad EGS code or tax line and resubmit. Checkout is never blocked by a portal outage — submission runs asynchronously after the order is placed.