Order routing is the discipline of turning orders from many channels into one correct sequence of fulfillment work: consolidated into a single queue, prioritized by each platform’s promise, and dispatched from the right stock with the right method. Small multichannel sellers rarely need warehouse-grade routing engines; they need the queue, three clear rules, and promises that never slip.
Step one: one queue, always
Routing begins with consolidation. Orders living in five seller dashboards are not a queue, they are a scavenger hunt, and the marketplace you check least is where the late shipment happens. A hub that syncs your channels consolidates orders as a side effect of the architecture: every channel’s orders in one stream, each tagged with its source, promise, and status. Unifystock does exactly this across Amazon, eBay, Etsy, Shopify, WooCommerce, and OpenCart.
The immediate wins are mundane and large: packing day runs off one list, nothing is discovered late, and every customer question starts from one history.
The three routing decisions
1. What ships first: promise-driven priority. Sort by ship-by deadline, not by order age. Each platform’s clock differs, Amazon handling time, eBay’s defect-fed same-or-next-day expectations, Etsy processing windows you set yourself, and your store’s own promise. A newer Amazon order with a tomorrow deadline outranks an older store order with a three-day window. The queue should show the deadline, and the sort should BE the deadline.
2. From where: location rules, if you have them. Multiple stock locations (a garage plus a 3PL, or FBA plus merchant stock) need one rule set: which location serves which channel or region, and what happens when the preferred location is short. Keep supply pools separate in the count, the hybrid rule, and route by simple precedence rather than clever optimization until volume genuinely demands more.
3. By which method: cost against promise. The cheapest service that meets the deadline wins; the routing sin is paying express because the order was FOUND late, which is a queue failure wearing a shipping cost.
Keeping the promises that feed the metrics
Routing exists because promises are enforced: late shipments feed eBay defects and Amazon account health. Three habits keep the machine honest:
- Tracking uploads immediately on dispatch, per channel, automatically, the single strongest metric protector.
- Handling times set to reality: a promise you hit every day beats an ambitious one you miss weekly.
- Cancellations near zero: most routing-stage cancellations are stock lies discovered late, which is an inventory-sync problem, not a routing one, and fixed upstream.
When routing gets complicated, simplify the inputs
Routing complexity usually imports from elsewhere: duplicate SKUs confusing picks (identity hygiene), bundles without component mapping, counts that disagree with shelves (shrinkage). Fix the inputs and the routing rules stay three lines long.
Common questions
Do I need routing software at low volume?
You need the consolidated queue from channel two onward. The rules stay human-executed until volume makes them a bottleneck; the queue is what makes human execution reliable.
How do I route when an item is in two places?
Precedence rule first (nearest, cheapest, or protected-stock last), fallback second. Write it down once; the exception you decide ad hoc at 6 p.m. becomes tomorrow’s inconsistency.
Should marketplace orders outrank my own store’s?
Marketplaces enforce promises with metrics; your store forgives more. Deadline-sort handles this naturally, it is not favoritism, it is arithmetic on consequences.
Where do returns fit in routing?
Returns are inbound routing: received, inspected, restocked into the correct pool with the count updated everywhere. Treat the returns bench with receiving discipline.
One queue, honest promises
Every channel’s orders consolidated, deadlines visible, stock truth underneath, from $49/month with unlimited orders. See pricing.