This is build-to-order, not an instant Marketplace download. After a short scoping call we confirm your Magento version (Open Source or Adobe Commerce), your VAT/tax setup and your Access Point provider. Typical delivery is around one working week: we build the module, validate documents end-to-end in sandbox, then install on your staging and production environments. You receive the source code in your repository, so there's no black box.

A post-launch support window is included for bug fixes and for keeping the module compatible with your Magento upgrades and with BIS Billing 3.0 / EN 16931 spec changes (the Peppol spec is versioned and updated periodically). Because we build against your specific install, support is hands-on rather than a generic ticket queue. We can also extend the window or move to a retainer for continuous compliance monitoring.

No — the extension delivers through a Peppol Access Point, but ECOSIRE is not a certified Access Point operator and we don't pretend to be. You connect your own Access Point provider (most EU sellers already have one, or we'll recommend options). We integrate Magento to that provider's API and handle SMP/SML receiver lookup, UBL generation and validation on the Magento side.

That's exactly why it's built-to-order. UBL BIS 3.0 requires correct VAT category codes, reverse-charge handling and EN 16931 business-term mapping. We map the module to your real Magento tax classes and customer-group / country rules so the generated invoice passes validation instead of being rejected at the receiver. Generic off-the-shelf extensions usually leave this mapping to you.

Yes. Generation and delivery sit behind a Magento service contract interface, and the default trigger is an observer on sales_order_invoice_save_after. So whether an invoice is created from the admin, via REST/GraphQL, or by your custom order automation, the Peppol document is produced. For high volume we wire it through an async queue consumer so the storefront and admin stay responsive.