Feature Request: Conditional Order Routing logic like Flow

Shopify Discussion
, ,
1

I’d like to request an improvement to Order Routing in Shopify.

Current problem:
Order Routing is useful, but it doesn’t offer the same kind of flexible conditional logic that exists in Shopify Flow. For merchants with multiple fulfillment locations, routing decisions often need to depend on more specific business rules than simple location priority or stock availability.

What I’d like Shopify to add or change:
Please add Flow-like conditional logic to Order Routing, so merchants can create rule-based routing decisions using conditions and fallback logic.

Example use cases:

  • If more than one location can fulfill the entire order, route the order to a preferred location such as Location A

  • If an item is out of stock at all locations, route it to a default fallback location based on vendor

  • Allow routing rules to use fields such as:

    • Location availability

    • Can fulfill full order

    • Vendor

    • Product type

    • SKU

    • Tag

    • Market or destination region

Why this matters:

  • Operational impact: reduces manual review and exception handling

  • Fulfillment impact: improves routing consistency across multiple locations

  • Scalability: supports more complex fulfillment setups without requiring custom workarounds

  • Business impact: helps merchants maintain better control over split shipments, vendor workflows, and fallback behavior

Ideal workflow:

  1. Open Order Routing in the Shopify admin

  2. Create a routing rule with if/then conditions similar to Shopify Flow

  3. Add priority logic for cases where multiple locations qualify

  4. Add fallback rules when no location has stock

  5. Optionally assign a default location based on vendor or other product attributes

  6. Preview the expected routing result before saving

Important details:

  • This would be especially helpful for merchants using multi-location fulfillment, 3PLs, and mixed internal/vendor fulfillment models

  • Current workarounds are limited and don’t provide enough control for nuanced routing logic

  • A preview or test mode would make the feature much safer to implement at scale