How to Configure Shopify Order Routing

Shopify tracks inventory independently at each location and uses order-routing or shipping-profile configuration to determine where orders can be fulfilled. Begin with an inventory and eligibility register for every store, warehouse, fulfillment app, dropshipper, and custom fulfillment service. Record whether the location is active, whether it may fulfill online orders, which products are stocked there, available quantities, supported markets, delivery methods, cutoff times, capacity constraints, and the owner of exceptions. A routing strategy built on stale location inventory can produce an apparently valid assignment that operations cannot complete.

Reconcile a sample of location-level quantities with the source warehouse or fulfillment system before changing rules. Confirm that products are assigned to the intended locations and that inventory is not being treated as a pooled quantity. Shopify explains that each location maintains its own inventory record. Identify products allowed to continue selling when out of stock, because overselling behavior can change the result when no location can fulfill a cart. Also identify locations that should never receive online work. Repair those data and eligibility defects before using routing rules to compensate for them.

Shopify states that order-routing rules run in sequence to prioritize locations. Its default strategy can include minimizing split fulfillments, staying within the destination market when possible, and shipping from the closest location. These rules represent different operating goals. Minimizing splits can reduce the number of packages but may assign from a more distant location. Choosing the closest location can support a delivery objective but may draw down scarce regional stock. A preferred-location rule can protect a primary warehouse workflow but may create different customer or cost outcomes. Write the intended tradeoff for every rule and place the rules in the order that expresses it.

Build a test matrix before configuration. Include single-item carts, multi-item carts, products stocked at one location, products stocked at several locations, carts that no single location can complete, destinations inside and outside a market, backordered items, and locations near capacity. For each case, record the expected assignment and acceptable fallback. If custom routing uses location metafields or an app-provided rule, document the source, allowed values, update owner, and failure behavior. Use the options exposed in the current Shopify admin and verify plan or app requirements rather than assuming every store has identical controls.

Use draft or otherwise safe representative orders when the workflow permits, and avoid creating customer communications or real fulfillment work solely for testing. For each test cart, capture inventory before assignment, destination, eligible locations, routing-rule order, assigned location or split, inventory after assignment, and any oversell state. Shopify documents that when one location can fulfill the entire order it can receive the assignment, while insufficient inventory across a single location can lead to a split or oversell behavior depending on configuration. Verify the store's observed result instead of relying on a remembered default.

Launch the production change as a canary limited by time, product group, location, or another safely controllable boundary. Monitor unassigned orders, unexpected splits, manual reassignments, inventory mismatches, delayed acknowledgements from fulfillment apps, service-level risk, and address or market exceptions. Define rollback as the exact previous rule order and configuration, not a note to restore defaults. Do not judge the canary only by the absence of complaints. Compare the observed assignments with the test matrix and inspect a representative sample of successful and exceptional orders.

A routing assignment is an operational decision record, not a delivery or cost outcome. Join the order and assignment to pick start, pack completion, carrier service, label cost, invoice adjustments, tracking events, delivery date, split-package count, cancellation, return, and customer-service exceptions. Keep the checkout promise, carrier estimate, and actual delivery as separate fields. If a rule sent an order to the closest location, that fact alone does not prove that the parcel arrived faster. If a rule minimized a split, it does not prove lower cost until labels, adjustments, labor, and inventory effects are reconciled.

Review exception patterns by product, location pair, destination market, cart composition, rule path, fulfillment app, and cause. Choose a bounded next action: correct inventory, change location eligibility, reorder a rule, narrow a custom condition, revise the test matrix, or keep the current strategy. Preserve manual overrides and their reasons because they reveal conditions the routing design may not express. Schedule a repeat review after material changes to locations, inventory systems, shipping profiles, markets, fulfillment apps, or product assortment. Order routing stays reliable only when its location and inventory evidence stays current.

Publish the rule owner, review cadence, and emergency rollback path with the configuration. Warehouse and support teams need to know where an unexpected assignment should be reported, which evidence to capture, and who may override the result without silently rewriting inventory.