Most ecommerce developers focus on the front end product pages, checkout flows, conversion optimisation. The back end gets less attention. And within the back end, order routing gets almost none. That's a mistake. Here's why order routing matters more than most developers realise and what the correct architecture looks like. The problem with manual and default routing When a seller starts out, order routing is simple. One warehouse. One carrier. Every order goes to the same place the same way. As they scale multiple warehouses, FBA, 3PLs, multiple carriers, multiple channels — the single-location default stops making sense. But most ecommerce platforms don't route intelligently by default. They route to whatever location is configured first or leave the decision to a human. The result: javascript// What manual routing looks like at scale orders.forEach(order => { // Someone manually decides: // - Which warehouse has stock? // - Which carrier is cheapest for this weight/destination?…