Symptoms
How this shows up in operations
If you are reading this page, you have probably noticed some of the following symptoms in your operation:
- East Coast customers receive orders from a West Coast warehouse
- Single-item orders get split across two warehouses
- Back-ordered SKUs cause hold rather than ship
- Multi-warehouse inventory drifts because rules conflict
- Subscription renewals route to warehouses without subscription SKUs in stock
- Returns get routed to the wrong warehouse on the back-end
None of these alone is conclusive — every operation has bad weeks. The diagnostic question is whether the symptoms are recurring, growing, and resistant to one-off fixes. If yes, you are likely looking at one of the root causes below rather than a tactical problem.
Root causes
Root causes
Four root causes account for the majority of cases we see. They are not mutually exclusive; most operators have two or three running at once.
Default routing not customized. Shopify defaults route on simple rules. As soon as you have routing preferences (carrier optimization, SKU stocking patterns), defaults are wrong.
No routing-rule documentation. Custom rules accumulate without documentation. The original engineer leaves; the rules become invisible. New rules conflict with old ones.
Backorder behavior not designed. What happens when one item in a multi-item order is back-ordered? Without explicit design, the answer is unpredictable.
Carrier-cutoff misalignment. Warehouses route based on proximity but ignore carrier pickup windows. An order routed to a warehouse that already missed cutoff arrives a day later than the alternative.
Identifying the root cause is the leverage point. Symptoms can be patched indefinitely without making progress; root causes, once addressed, fix multiple symptoms at once.
Solutions
How specialists fix this
Vetted specialists in the network typically pursue these approaches, in roughly this order:
1. Define routing rules explicitly. Document your routing logic in plain English: zip code prefixes, carrier optimization, single-warehouse preference, backorder handling. Encode in the WMS or OMS where possible.
2. Build a routing-rule audit. Once a quarter, audit a sample of orders against expected routing. Identify mismatches and root-cause them. Update documentation when rules change.
3. Design backorder behavior. Choose: ship partial, hold for restock, or split with notification. Document the decision and implement it consistently. Most operations default to ship-partial below a threshold and hold above it.
4. Align with carrier windows. Adjust routing to factor in remaining carrier pickup time. If the closer warehouse has missed cutoff, route to the next closest that has not.
The order matters because the first two solutions often unlock the rest. Skipping them in favor of tactical patches is the most common path to repeated problems.
Sequencing
Sequencing the fix
Operators often try to fix these problems in the wrong order. The instinct is to start with whichever symptom hurts most this week, which produces tactical patches that do not stick.
A more durable sequence: stabilize the highest-impact symptom enough to buy thinking time, then attack the most upstream root cause (usually a missing source of truth, a missing process, or a missing owner), then layer the remaining solutions on top of the now-stable foundation.
Skipping the stabilization step leaves the team firefighting; skipping the root-cause step guarantees the problem returns in a different shape within a quarter.
A vetted specialist's first deliverable is usually this sequencing plan rather than any specific fix — because the sequence is where most operators lose months of progress.
Measurement
What to measure once you have fixed this
Once the root causes are addressed, set up the measurements that will catch the same problem if it returns.
The right metrics differ by situation but tend to share three properties: they are leading indicators rather than lagging ones, they are visible weekly rather than monthly, and they have explicit thresholds that trigger investigation.
For most operations problems the leading indicators are workflow-level (cycle time, accuracy, exception rate) rather than financial — by the time finance sees the issue, the operational damage has already been done.
The brands that stay out of this cycle for years are the ones that built the right measurements once and treated the weekly review as non-negotiable.
When to hire
When to bring in outside help
Hire a specialist when routing decisions feel ad-hoc, when you are adding a new warehouse, when carrier costs are growing faster than volume, or when customer complaints about split or delayed shipments increase.
The scoping call is free. We route requests to one or two vetted specialists whose case studies match the situation.
Within one business day, you have introductions and an opinionated recommendation about whether the situation needs a project engagement or a smaller-scope assessment first.