Because this is built to order for your specific Magento version, gateways and warehouse setup, typical delivery is about one working week from confirmation. After a short scoping call we build the module, install it on your staging environment, validate it against your real orders and MSI sources, then deploy to production with you. You are not downloading a generic ZIP and hoping it fits — every step is done and verified by ECOSIRE.

Every build includes a post-launch support window covering defect fixes and compatibility with Magento security patches and minor version upgrades during that period. Because we ship the full module source under app/code/Ecosire/BulkOrderProcessing, nothing is locked or obfuscated — your team or ours can maintain it. Extended support and feature additions are available as an ongoing arrangement after the initial window.

Yes. The module is built against the same service contracts and UI component framework both editions share, so it runs on Open Source and Adobe Commerce. On Adobe Commerce we additionally respect B2B features where present — company accounts, shared catalogs and multi-website scope — so bulk actions behave correctly across your customer segments.

No — handling MSI correctly is the core reason this exists. On bulk shipment we resolve the assigned sources per order using GetSourcesAssignedToStockOrderedByPriorityInterface and your Source Selection Algorithm, so each shipment deducts from the right source_item quantities. We map and test this against your actual warehouse priorities before go-live.

The batch does not stop. Each order is processed in its own try/catch using Magento's service contracts, so a problem order — an uncaptured payment, an out-of-stock source, an invalid state transition — is skipped and reported in a result summary while every other order completes successfully. You see exactly which orders need attention instead of losing the whole run.