Every order to the right location without manual rules

Each order arriving in the Order Management System carries a channel tag, B2B account, direct-to-consumer storefront, marketplace listing, or program store. The routing engine reads that tag first and branches into the appropriate rule set. A B2B enterprise account order might apply speed-first logic with express carrier eligibility. A standard direct-to-consumer order might apply cost-first logic with economy carriers. A marketplace order might apply platform-specific service-level-agreement rules. All from the same engine, no separate configurations per system.

Yes. Routing rules are managed through an admin interface. Operations managers can add or modify rules, warehouse priority sequences, carrier preferences, region assignments, drop-ship thresholds, without writing code or submitting a development ticket. Rule changes take effect immediately on the next inbound order.

Fallback routing sequences are configured per rule set. If WH-East is out of stock for a product, the engine automatically evaluates the next destination in the priority sequence, WH-West, then 3PL-Central, then drop-ship supplier. The fallback is immediate and does not require a human decision or a failed order to be manually re-queued.

Routing works with partners that connect via REST application programming interface, electronic data interchange, or the Redefine supplier portal. For owned warehouses, native integration is available. For third-party logistics partners and suppliers with their own systems, standard data formats are supported. Partners without application programming interface access can use the supplier portal for order acknowledgment, status updates, and tracking, no custom development required on their side.

Initial routing configuration is completed in Sprint 1 of an Order Management System implementation. For a two-warehouse plus one third-party logistics setup with standard channel rules, live routing is active within the first two weeks. More complex configurations with five or more fulfillment destinations and multiple channel-origin rule sets take an additional sprint to validate before going live on full order volume.

Yes. When an order contains items stocked across different locations, the engine can split the order into multiple shipments routed to the appropriate fulfillment partners. Each shipment gets its own carrier assignment. The customer receives a single consolidated tracking notification. Split rules are configurable, you define when splitting is preferred versus when backorder hold is preferred based on your fulfillment policy.