Typical delivery is about one working week from kickoff, depending on your GSP/ASP, fulfilment complexity, and whether e-way bills are in scope. After requirements and access we build the module, validate it end-to-end against the IRP sandbox with your GSTIN, then install and smoke-test it on your Magento instance before go-live. This is a custom build delivered and installed by ECOSIRE, not an instant Adobe Commerce Marketplace download.

Every build includes a warranty period for defect fixes, and we offer an optional support/maintenance plan covering Magento and Adobe Commerce version upgrades, IRP schema or API changes published by GSTN, and GSP/ASP credential or endpoint changes. Because the IRP schema and government rules evolve, an active plan is the recommended way to stay compliant; you also receive the source code so another developer can maintain it if you prefer.

The IRP/GSTN production API is accessed through an authorised GSP (GST Suvidha Provider) or ASP. You bring or choose a GSP/ASP and provide its credentials; ECOSIRE builds the integration against it behind a service contract, so the provider can be swapped later without rewriting the invoice logic. We validate everything on the sandbox before pointing at production.

Yes. The module is built with standard Magento mechanisms — di.xml service contracts, observers on the invoice events, system.xml config, admin ACL, and cron — so it runs on both Magento Open Source and Adobe Commerce. We confirm your exact version and any B2B/MSI specifics during scoping and target that version explicitly.

Yes. IRNs can be cancelled within the IRP's 24-hour window via an admin action, and a cron-driven retry queue re-attempts submissions that failed due to timeouts or transient IRP errors, with each attempt and its error code recorded in an audit log. Documents outside scope, such as B2C and exempt invoices, are skipped according to the configured rules.