What we have seen in multi-location projects is this: activating another Shopify location is easy; deciding which location should fulfil each order is the real design work. A rule that chooses the nearest stock can increase split parcels, ignore warehouse capacity, consume store safety stock or break a premium delivery promise.
This guide creates an accountable routing model. For multi-location discovery, Contact StoreBuilt.
Table of contents
- Keyword decision and research inputs
- Map locations and promises
- Choose routing priorities
- Protect inventory truth
- Handle exceptions
- Test and measure
- Anonymous StoreBuilt example
- Final StoreBuilt point of view
Keyword decision and research inputs
Primary keyword: Shopify order routing. Secondary keywords: Shopify multi-location inventory, ecommerce order routing UK, Shopify split fulfilment, warehouse routing and Shopify location priority. Intent: implementation research. Funnel stage: middle to bottom funnel. Page type: operations blueprint.
Research checked on 15 July 2026 included current Charle and UK agency operations content, official Shopify order-routing, location, fulfilment and Flow documentation, and existing StoreBuilt inventory articles. Shopify’s default strategy can minimise split fulfilments, stay within the destination market and ship from the closest location; this article addresses how UK teams should sequence commercial priorities.
Map locations and promises
List every warehouse, store, 3PL, supplier, repair centre and virtual location. For each, record sellable inventory, channels, markets, cut-off times, carrier services, capacity, handling cost, packaging, restricted products and whether it may fulfil online orders. Do not let accounting or quarantine locations enter routing accidentally.
Define customer promises before rules. Standard UK delivery, next day, nominated day, click and collect, international, oversized and preorder orders may require different eligible nodes. Routing cannot repair a checkout promise that ignored real stock, cut-off and carrier constraints.
| Location fact | Why it matters | Owner |
|---|---|---|
| Stock availability | Determines eligible supply | Inventory team |
| Pick capacity | Prevents overloaded nodes | Operations |
| Cut-off/calendar | Protects dispatch promise | Warehouse |
| Carrier/service | Determines reachable postcode | Logistics |
| Cost per parcel | Exposes split economics | Finance |
| Safety stock | Protects retail or wholesale | Trading |
Choose routing priorities
Sequence rules explicitly. Minimising splits usually belongs early because a second parcel adds handling, postage, packaging, communication and carbon. Staying within market can reduce cross-border complexity. Proximity may improve speed, but straight-line distance is not carrier transit time or cost.
Create scenarios before configuration: one location holds all items; no location holds all; a store has stock but limited labour; a 3PL misses cut-off; an item is preorder; a parcel contains restricted goods; a location has stock reserved for wholesale. Record the intended answer and business reason.
Shopify supports ranked locations and location-metafield rules in appropriate configurations. Metafields can represent capacity or fulfilment speed, but require a reliable update owner. A stale “fast” flag is worse than a simple stable priority.
Do not optimise one metric. Cheapest routing can harm delivery; closest can split; fewest parcels can drain scarce stock; fastest can destroy margin. Use a hierarchy of hard constraints followed by commercial preferences.
Protect inventory truth
Routing quality is limited by available-to-sell accuracy. Align Shopify with WMS, ERP, POS, 3PL and marketplace reservations. Define sync frequency, conflict ownership, buffers and what happens during an integration delay.
Separate on-hand, committed, damaged, inbound, safety, retail display and available-to-sell quantities. Test bundles and kits: components may live across locations even when the storefront presents one product. Decide whether assembly happens before routing or at a nominated node.
Prevent negative inventory from becoming an invisible routing strategy. Official Shopify documentation notes that orders can split or a prioritised location can oversell in certain configurations. Monitor negative positions, transfers and manual reallocations daily.
StoreBuilt’s Shopify systems and operations service can model these boundaries across commerce and fulfilment systems.
Handle exceptions
Create queues for inventory mismatch, location rejection, carrier outage, address restriction, split after partial fulfilment, damaged last unit, missed cut-off and customer change. Each exception needs an owner, response target and customer message.
Hold orders when a human decision prevents a worse outcome. Shopify Flow and fulfilment events can support alerts and controlled actions, but automation should not silently reroute regulated, high-value or customised orders without suitable checks.
When a fulfilment is split, keep the customer view coherent. Explain which items travel together, expected dates, tracking and whether additional charges apply. Merge fulfilments from the same location when operationally valid. Do not send contradictory notifications from Shopify, WMS and carrier systems.
Establish a safe manual override. Record who changed the location, why, what inventory and promise were affected, and whether the rule needs correction. Repeated overrides are product evidence, not staff noise.
Test and measure
Use a scenario matrix in staging or controlled orders. Cover every service, postcode group, location combination, bundle, stock state, market, cancellation and partial fulfilment. Verify tax, shipping rate, label origin, notifications and inventory movements.
| Metric | Diagnostic use |
|---|---|
| Split rate | Finds fragmented inventory or poor priority |
| Cost per order | Tests routing economics |
| Promise miss rate | Finds cut-off and capacity failure |
| Reallocation rate | Exposes bad stock or rules |
| Distance/transit | Checks proximity assumption |
| Negative inventory | Exposes sync or oversell |
Review by order profile, not only average. A low overall split rate can hide severe problems for bundles or international orders. Compare intended versus actual route and track exception ageing. Change one rule at a time and retain configuration history.
Anonymous StoreBuilt example
In one operations review, stores were prioritised because they were geographically close to customers. In practice, store teams lacked consistent packing capacity and popular retail stock was consumed before weekends. The useful redesign placed fulfilment eligibility and capacity before proximity, protected store buffers and created an exception queue. The gain was a more accountable promise model; we do not invent savings without measured evidence.
Final StoreBuilt point of view
StoreBuilt’s view is that order routing is a promise engine. The correct location is not automatically the closest or cheapest; it is the eligible node most likely to deliver the promised order at an acceptable total cost. Start with constraints and inventory truth, then optimise preference rules.
For a Shopify routing blueprint, Contact StoreBuilt.