Drop-Ship Routing in Apparel: Who Should Own the Decision

It is Tuesday morning at a $15M apparel brand. A Nordstrom drop-ship order for 18 units of a core knit lands in the EDI inbox. The same SKU has 42 units showing available in Shopify, 30 of which are physically at the 3PL in New Jersey, 12 of which are actually allocated to a wholesale PO that ships Friday. The customer service lead is looking at a spreadsheet. The ops manager is on Slack with the 3PL. The Shopify storefront is still selling the SKU as if all 42 units are free. Somebody is going to lose this round, and it is usually the brand, in the form of a chargeback or a cancelled retailer order.

This is the drop-ship routing problem, and it is almost never solved at the warehouse. It is solved, or not solved, in the order management layer.

What is drop-ship routing in apparel and why is it different from generic ecommerce routing?

Drop-ship routing in apparel is the decision logic that assigns every inbound order to a fulfillment node and a committed inventory pool. The nodes are usually some combination of an owned warehouse, one or more 3PLs, a retailer’s distribution center reached through EDI, and direct-to-consumer fulfillment performed on behalf of a retail partner. The decision has to happen before the order is promised, not after, and it has to respect channel-aware ATS rather than a single global available-to-sell number.

The reason apparel routing is harder than generic ecommerce routing is the channel mix. A pure DTC brand routes from one or two nodes against one inventory pool. An apparel brand running wholesale, DTC, and retailer drop-ship is routing against pools that are committed to different futures: wholesale POs with delivery windows, marketplace orders with retailer SLAs, DTC orders the brand controls entirely, and drop-ship orders where the retailer dictates the ship window, the carrier, the packing list, and the ASN format. One global inventory number across all of this is the source of most chargebacks I see.

Who actually owns the drop-ship routing decision today, and why that is the wrong answer?

In most brands in the $5M to $100M band, nobody owns it. The routing decision is distributed across four or five systems and two or three humans, and it changes hands every quarter when a new tool gets bolted on. The storefront decides what to promise. The 3PL decides what it can physically ship. The EDI provider decides what gets acknowledged to the retailer. A spreadsheet, maintained by one person, decides which wholesale POs are sacred and which can be borrowed against. The CS team manually resolves the gaps.

What I keep hearing from customers about why they bought is some version of this: “We had four tools that each thought they knew the inventory number, and none of them agreed.” The drop-ship routing decision is the most visible symptom of that disagreement, because retailers fine you for it. A late ASN, a short ship, a substitution that was not authorised, all of these trace back to a routing decision that was made by the wrong system at the wrong time with the wrong information.

This is Breakpoint 4 in the 6 Breakpoints framework. Order flow becomes harder to trust because the system promising orders is not the system that knows what inventory is actually committed. Drop-ship is where BP4 stops being a finance abstraction and starts costing real money in chargebacks.

What does the routing decision actually have to evaluate?

A correct drop-ship routing engine for an apparel brand evaluates at least eight things before it promises an order:

• The physical location of the inventory and its handling cost from that node.
• The retailer’s required ship window and carrier compliance rules.
• Existing wholesale PO commitments against the same SKU and size.
• The replenishment pipeline, including in-transit POs from production.
• The packing and labelling requirements at each node (retailer-specific cartons, hangtags, polybag rules).
• Whether the node can produce a compliant EDI 856 ASN within the required window from pick.
• The cost of a chargeback versus the cost of splitting the shipment.
• The brand’s own channel priority rules (is this retailer worth borrowing from DTC, or not).

No storefront has this view. No 3PL has this view. The EDI provider certainly does not. The order management layer is the only place this can live, and it has to be sitting on top of channel-aware ATS, not a flat number.

What goes wrong when the storefront owns the decision?

When Shopify or any DTC storefront owns the routing decision, the brand is effectively letting the DTC channel front-run every other channel. The storefront sells what it sees, and what it sees is usually a number that has not deducted committed wholesale or retailer drop-ship pools. The result is the 2 to 3 percent oversell rate I see at peak in $15M brands, and almost all of it is being absorbed as cancellations, customer service work, or short-shipped retailer orders that come back as chargebacks 60 days later.

Wholesale should not run through Shopify’s native flow, and drop-ship absolutely should not. Shopify is a storefront. It is excellent at converting consumers. It is not a channel-aware allocation engine, and treating it as one is one of the more expensive mistakes in this segment.

What goes wrong when the 3PL owns the decision?

When the 3PL owns routing, the brand has outsourced a margin decision to a logistics partner whose incentives are to ship what is in the bin in front of them. The 3PL does not know that the 12 units it just picked for a DTC order were the last 12 units that could have covered a Nordstrom drop-ship that lands tomorrow. It cannot know, because it does not see the inbound retailer order queue or the wholesale commit calendar. The 3PL ships what it is told. If you tell it nothing, it ships whatever is in front of it.

The symptom here is the most expensive variant. The brand only finds out about the misallocation when the chargeback shows up. By then the reconciliation is across three systems and two reporting periods, and the data plumbing FTE is spending a full day a week tracing it. That is the 6 to 9 hours of weekly reconciliation I keep landing on when I sketch out the math for a brand at this size, and drop-ship routing failures are usually the biggest single contributor.

Where should the drop-ship routing decision actually live?

In the order management layer, with three things wired into it: channel-aware ATS, a unified view of committed pools across wholesale POs, drop-ship orders, and DTC, and a routing ruleset the operations team can edit without engineering. Anything less than this and you are pushing the decision back out to the storefront, the 3PL, or a human with a spreadsheet, which is where it broke in the first place.

Channel-aware ATS is the non-negotiable piece. The system has to be able to say: of 42 physical units, 12 are committed to wholesale POs shipping Friday, 8 are reserved for a Nordstrom drop-ship pool with a 48-hour SLA, and 22 are genuinely available for DTC. The storefront then sees 22, not 42. The drop-ship inbox sees 8, not 42. The wholesale allocation sees 12 as locked. One pool of physical inventory, three honest numbers.

What does a good drop-ship routing ruleset look like?

The ruleset is where the brand expresses its commercial priorities. There is no universally correct ordering. What there is, is an honest hierarchy that the ops team can defend at the Monday meeting. A starting point that holds up for most brands in this segment:

1. Retailer drop-ship orders with active chargeback exposure get first call on the relevant pool, sized to the SLA window.
2. Wholesale PO commitments inside their ship window are sacred and cannot be borrowed against without exec sign-off.
3. DTC orders route against the residual DTC pool, with split-shipment logic only enabled for high-AOV orders.
4. Marketplace orders route last, against whatever is genuinely uncommitted.
5. Substitutions are never auto-approved on a drop-ship order. Ever. The chargeback cost is higher than the cancellation cost.

If your retailer chargebacks exceed 1 percent of wholesale revenue, the routing ruleset is the problem, not the warehouse. The warehouse is shipping what it is told. The ruleset is telling it the wrong thing.

What is the operational anti-pattern to avoid?

The anti-pattern is what I think of as “the heroic CS team.” The brand has no routing logic, so the customer service team manually resolves every conflict. They are smart, they are dedicated, they know the brand cold, and they are working from a spreadsheet that is 20 minutes out of date by the time they open it. They get most of it right. The misses, by definition, are the ones nobody catches until the chargeback notice arrives.

This pattern is expensive in three ways: the FTE cost of the team, the chargeback cost of the misses, and the strategic cost of having your best operational people doing data reconciliation instead of building the actual fulfillment capability the brand needs at $30M and $50M. The reason the 6 Breakpoints framework exists in the form it does is that this pattern repeats almost identically across every brand I sit with in the $10M to $20M zone. The names change. The spreadsheet does not.

How do you sequence the fix?

The fix is not a tool swap. It is a sequence, and the order matters.

First, get channel-aware ATS working. Until the system can produce honest available-to-sell numbers by channel, nothing else helps. This usually means consolidating the inventory ledger out of three or four systems into one.

Second, codify the routing ruleset on paper, with the commercial team, before you touch a system. The ruleset is a business decision, not a technical one. If the team cannot agree on the hierarchy in a meeting, no software will save them.

Third, implement the ruleset in the order management layer, with the operations team able to edit it. If changes require a developer ticket, the rules will go stale within a quarter and the heroic CS team will quietly take the work back.

Fourth, instrument it. Track chargeback rate by retailer, oversell rate by channel, and routing exceptions per week. These three numbers tell you whether the routing engine is working. If the chargeback rate does not move in 90 days, the ruleset is wrong, not the engine.

What this means for an apparel operations team

Drop-ship routing is not a warehouse problem and it is not a storefront problem. It is an order management problem that gets blamed on the warehouse when it goes wrong. If your team is spending 6 to 9 hours a week reconciling inventory, and your oversell rate is 2 to 3 percent at peak, the routing decision is sitting in the wrong place and the channel-aware ATS layer is missing or broken.

The fix is architectural before it is operational. Get the routing decision into a single layer that can see every committed pool. Write the ruleset with the commercial team. Make sure the ops team can edit it without engineering. Instrument the three numbers that tell you whether it is working.

When the routing layer is honest, the rest of the order flow gets quiet. Chargebacks drop. The CS team stops resolving exceptions and starts building. The drop-ship channel, which is usually the most profitable wholesale relationship the brand has, stops being the thing everyone dreads on Monday morning.