No. This is a build-to-order extension. ECOSIRE designs and builds the module suite to fit your catalog, regions, and operational workflow, then installs it on your Magento 2 / Adobe Commerce environment and supports it. There is no instant Marketplace download and no auto-licensing — you receive a tailored, installed solution plus the source code.

Because each build is tailored, typical lead time is roughly 3 to 5 weeks from kickoff, depending on how many vendors, zones, and integrations you need and the state of your Magento environment. We start with a short scoping call, build on a branch, deploy to your staging for review, then install on production with setup:upgrade, di:compile, and static-content deploy. You get a firm timeline in writing before work begins.

Yes. Every build includes a warranty period for defect fixes, and we offer ongoing support and maintenance retainers covering Magento security-patch compatibility, minor version upgrades, and enhancements. Because you receive the source under app/code, your own team or any Magento developer can also maintain it — you are never locked in.

Yes. The module is written against standard Magento 2 APIs — service contracts, dependency injection, plugins, observers, declarative schema — so it runs on both Magento Open Source and Adobe Commerce (Cloud included). Where Adobe Commerce adds capabilities (e.g., B2B, advanced staging, native MSI tuning), we adapt the build to use them; on Open Source we provide equivalent implementations.

A service contract geocodes the shopper (browser geolocation or address) and ranks vendors by distance from their stored coordinates, filtered by your radius or polygon delivery zones. Each vendor's stock is modeled as its own inventory source (Magento MSI) or a dedicated vendor-stock table, so the same SKU can have different availability and price per vendor. Checkout plugins enforce that only an in-zone vendor with stock can fulfill, and the slot scheduler plus rider-assignment module handle the rest.