Order Routing & Fulfillment Orchestration (OMS)

This is a build-to-order module, not an instant apps.odoo.com download. After a short scoping call to map your warehouses, 3PL partners, SLAs and substitution rules, typical delivery is 2–4 weeks: design and build, then deployment to your staging environment for UAT, then production go-live. You never install an unconfigured generic app — you receive a working, configured system tuned to your fulfillment network.

Every engagement includes a defined post-launch support window for bug fixes and configuration help, plus training so your team can adjust routing rules themselves. Because we hand over the full, commented source code, you are never locked in. We also provide a version-compatibility statement, and offer ongoing support and Odoo-version upgrade retainers (for example when you move from 17 to 18 or 19) as an optional continuation.

The module is built for Odoo 17, 18 and 19, on both Community and Enterprise. We confirm your exact version and edition during scoping and test against it, since some fulfillment features (like certain Enterprise delivery/costing tools) differ between editions. The routing logic itself is edition-independent and built on standard sale, stock and delivery models.

No. Routing runs through a transparent rule engine. For each sale.order.line the module scores candidate sources using computed @api.depends fields for available-to-promise stock, landed shipping cost, and SLA/cut-off feasibility, then applies your chosen strategy (nearest, cheapest, fastest or weighted). Every decision is written to a per-line fulfillment-decision log showing the candidates considered and why the winner was picked, so operations and audit can always see the 'why'.

Yes. Routing decisions are exposed over Odoo's XML-RPC and JSON-RPC APIs, so your storefront, middleware or marketplace connectors can request an allocation or force a manual override programmatically. 3PL and dropship handoffs are generated as native Odoo pickings or vendor purchase orders. We scope your specific partner and channel integrations up front and confirm what is API-driven versus configured.

When no single source can satisfy a line, it can split the shipment or ship partially now and create a linked backorder. A scheduled ir.cron job re-scans open backorders and re-routes them automatically as stock or a cheaper source appears. For out-of-stock SKUs you can define substitution rules that offer an equivalent product — either with an approval step or as an automatic swap — based on the policy we configure with you.

We build against Odoo conventions — a clean __manifest__.py, standard model inheritance, ir.model.access.csv and record rules rather than hacks — specifically to keep the module upgrade-safe. That said, no custom addon is guaranteed to migrate untouched across major versions, so we hand over readable source and offer optional upgrade support to move it from 17 to 18 or 19 when you are ready.