No. This is a build-to-order extension. ECOSIRE builds, installs and supports the module directly on your Magento install. There is no instant Marketplace download — you receive the source code, a managed installation on staging then production, and a defined support window. This lets us tune the 55-field mapping, SST classification and TIN handling to your specific tax setup rather than shipping a generic one-size listing.

Typical lead time is one working week from kickoff, depending on your Magento version, theme/customizations and whether your MyInvois sandbox credentials are ready. The flow is: requirements and tax-setup review, build and unit testing, installation on your staging environment, end-to-end clearance testing against the MyInvois preprod sandbox, then a supervised production go-live. We confirm a firm date in writing once we've reviewed your environment.

Yes. The module targets the standard Magento 2 framework (Open Source and Adobe Commerce / Cloud) and uses only supported extension points — di.xml dependency injection, plugins/interceptors, observers, service contracts and ACL. It does not rewrite core classes, so it is upgrade-safe. On Adobe Commerce Cloud we follow the read-only filesystem deployment model and submit changes via the standard composer/Git deployment pipeline.

Every build includes a warranty window for defect fixes, plus an optional ongoing support and maintenance plan. Because LHDN iterates the MyInvois SDK and validation rules, the support plan covers schema/version updates (for example new classification codes or field changes), MyInvois API endpoint changes, and Magento security-patch compatibility. You are never left on a frozen version of a regulated integration.

When a Magento invoice is created, an observer on sales_order_invoice_save_after assembles the LHDN document and submits it to the MyInvois API (synchronously or via an async queue/cron consumer for high volume). On a valid response the module persists the LHDN UUID, long-id and validation QR against the invoice, embeds the QR in the invoice PDF and email, and exposes the status via REST/GraphQL. Failed or pending submissions are retried and polled by cron, with full audit logging visible in the ACL-protected admin grid.

Yes. Credit memos in Magento map to LHDN credit notes and reference the original cleared invoice UUID, so adjustments and refunds stay compliant. Debit notes and, where your business model requires it, self-billed and consolidated e-invoices can be configured during the build. The exact document types enabled are scoped to your transaction flows during requirements review.