No. This is build-to-order. ECOSIRE engineers the module against your specific Magento 2 or Adobe Commerce version, theme, and existing shipping setup, then installs and supports it on your environment. You receive code written for your catalog and conditions, not a generic Marketplace package you have to wrestle into shape.

A typical build for the standard feature set runs about 2 to 4 weeks from requirements sign-off, depending on the complexity of your shipping logic, the number of carriers involved, and whether you need GraphQL/headless coverage. We confirm a firm timeline during the scoping call before any work begins, and you get staging access for review before production deployment.

Every build includes a post-delivery support window for bug fixes and compatibility adjustments at no extra cost. For ongoing changes, new rule types, and Magento version upgrades, we offer a paid maintenance retainer. Because the module is delivered as clean composer-installable code with a handover document, your own developers can also maintain it independently if you prefer.

Yes. The module layers on top of Magento's shipping pipeline using prioritized di.xml plugins and observers, so it cooperates with native flat-rate, table-rate, and account-based carriers as well as third-party carrier extensions. We set plugin sort-order during the build to ensure rules evaluate after your carriers populate their rates.

Yes. All rule logic runs server-side in the quote total collectors, and outcomes are exposed through both REST and GraphQL cart-schema extensions. That means available methods, computed rates, and restrictions are identical whether your storefront is Luma, Hyvä, or a fully decoupled PWA Studio / headless frontend.

Yes. The module enforces payment restrictions server-side at checkout — for example, disabling Cash on Delivery for freight shipments or in-store pickup orders. Because the check happens in the quote pipeline rather than the browser, it cannot be bypassed by manipulating the frontend.