Route an online order using sellable, uncommitted inventory at eligible fulfillment locations, then confirm that the allocation reaches every connected sales channel. Adding location totals together is not enough when some units are reserved, in transit, damaged, or unavailable for online fulfillment.
Define the location’s actual role
List each shop, warehouse, external fulfillment app and other stock location. Record whether it stores inventory, can fulfill online orders, supports pickup, or only receives transfers. Shopify’s location documentation notes that some inventory and fulfillment apps are treated as locations. Check the actual inventory integration instead of assuming every location in the administration screen is a physical building your staff controls.
For each location, identify who maintains counts and who can release goods. A retail shop may have the nearest stock but lack a reliable packing process. A warehouse may have enough units but not serve the buyer’s region or selected delivery method. Eligibility belongs in the routing decision alongside quantity and distance.
Distinguish physical stock from availability
| Hypothetical location | Physical units | Already committed | Available in this illustration |
|---|---|---|---|
| Retail shop | 3 | 2 | 1 |
| Warehouse | 5 | 0 | 5 |
| Total | 8 | 2 | 6 |
The table is a simplified hypothetical example with no damaged, quarantined or in-transit units. An order for four units cannot be supplied from the shop alone, even though the business has eight physical units. If the warehouse is eligible and those five units are genuinely available, it could supply the order without a split. Treat the committed shop stock as already promised, not as spare inventory to borrow casually.
Read the routing rules in order
Shopify describes routing rules applied in sequence, with a default approach that includes minimizing split fulfillments, staying within the destination market when possible, and using a close location. That is different from a universal rule saying the nearest location always wins. Review the current rule order and any custom prioritization used by your account or integration.
Write a short explanation for each rule: what business problem it addresses, what data it needs, and the expected result when two locations qualify. If a location is preferred for operational reasons, confirm that preference does not override a required service restriction. Keep the rationale understandable to the person who handles the order when the automated result is unexpected.
Test complete orders, not just single units
Use a cart with several products and quantities, including one component available only at another location. Check whether the system chooses a single eligible source, splits the order, or requires an operator decision. Review the customer’s shipping charge and delivery explanation after routing. A technically valid allocation can still create an unpriced extra parcel or a misleading single-delivery promise.
Include an order that arrives when the last unit is being sold at a physical register. Ask how quickly a reservation or completed sale reaches the online store and any marketplace connection. A periodically synchronized count is not the same as a real-time reservation. Where timing leaves exposure, document the actual limitation and choose a supported control rather than claiming the system prevents every oversell.
Keep transfers out of double-counted stock
A transfer moves existing units; it does not create additional merchandise. If two units leave a warehouse for a shop, identify their in-transit state and the event that makes them sellable at the destination. Do not leave them fully available at the source while also making them immediately available at the destination unless a specific supported allocation model justifies that view.
Count and inspect the receiving transfer against the expected quantity. A transfer marked sent is not proof that the shop received the exact items. Record discrepancies against the transfer reference so an operator does not “fix” the store count by adding inventory that never arrived. Match product variants as carefully as quantities.
Use a routing acceptance matrix
- One eligible location has the entire order.
- Only several locations together can provide the order.
- The nearest location lacks enough uncommitted stock.
- A location has physical stock but cannot fulfill the selected delivery method.
- A transfer is sent but not yet received.
- A retail sale and online order compete for the final unit.
- A fulfillment app is unavailable or rejects the allocation.
For each case, save the expected source, permitted split, stock changes, shipping consequence and exception owner. Use controlled test data and the appropriate platform method. Do not experiment by redirecting real customer orders between warehouses without the relevant operational authorization.
Review exceptions at the correct layer
When an order routes badly, first determine whether the problem was inventory accuracy, location eligibility, rule order, synchronization or fulfillment execution. Changing priorities will not repair a false stock count, and adding stock will not make a location support an unavailable service. Resolve the cause where it originates and verify the next comparable order. Clear allocation records make that investigation possible without guessing which building had the goods.



