What Is a Drop-Ship Routing Decision and Who Should Own It

It is a Tuesday in October. A $22M contemporary brand is six weeks into pre-spring shipping. Wholesale orders are flowing to the New Jersey 3PL for pick. DTC orders are flowing to the same 3PL but against a different inventory pool the team set up in a spreadsheet. A Nordstrom drop-ship PO lands through EDI 850, and nobody is sure whether it should ship from the 3PL or from the brand’s small LA studio that still holds samples and one-offs. The CSR routes it to LA because that is where the style sits in NetSuite. LA does not have the polybag spec Nordstrom requires. The PO ships late, gets a compliance chargeback, and the team spends Thursday writing a dispute. Nobody made a bad decision. Nobody made the routing decision at all.

What is a drop ship routing decision in apparel operations?

A drop ship routing decision apparel teams encounter is the per-order, per-SKU choice of which fulfillment node ships a given order, against which inventory pool, under which service-level agreement, and against which channel’s committed quantity. It applies to three distinct flows that get conflated in most brands: retailer drop-ship (a wholesale partner like Nordstrom or Saks routes a DTC order to you for fulfillment under their compliance rules), brand drop-ship (your own DTC order routed to a vendor or factory that holds finished goods), and split-node DTC (your own order routed across two of your own warehouses or 3PLs).

The decision is not a single setting. It is a chain of small choices: which node has the unit, which node has capacity, which node is compliant for the destination retailer, which channel the unit is committed to, and what the cost-to-serve is on each path. Most brands do not have a system that holds all five of those variables in one place, so the decision gets made implicitly, by whichever tool happens to see the order first.

Why does routing become a breakpoint between $10M and $20M?

BP4 of the 6 Breakpoints framework is the point where order flow becomes hard to trust. Routing sits inside BP4 because once a brand is running wholesale, DTC, and at least one retailer drop-ship program at the same time, the number of valid fulfillment paths per order goes from one to four or five. The combinatorics break the way the brand has been handling it, which is usually a CSR following a runbook in their head.

What I keep hearing from customers about why they bought is some version of the same sentence: we did not realize routing was a discipline until we lost six figures to it in a season. The reason the 6 Breakpoints framework exists in the form it does is that this pattern shows up at almost exactly the same revenue band across categories. A $15M brand running wholesale plus DTC plus 3PL is spending 6 to 9 hours a week reconciling inventory across Shopify, the 3PL, and wholesale. A meaningful share of that reconciliation is downstream of routing decisions nobody owns. Oversell rates at peak run 2 to 3 percent. One FTE is effectively doing data plumbing instead of operations.

The combinatorics are not the problem. The problem is that no role is accountable for the routing logic, so the default is whatever the storefront, the 3PL WMS, or the EDI VAN happens to do on its own.

Who actually owns the routing decision today, and why is that wrong?

In most brands at this stage, four parties are competing to own routing by default, and none of them should.

Shopify owns DTC routing through native order routing rules. This works for single-warehouse brands. It breaks the moment you have channel-committed inventory, because Shopify cannot see what is reserved for Nordstrom’s open PO sitting in your wholesale system. Shopify will happily allocate a unit to a DTC order that is already committed to wholesale.

The 3PL owns physical routing through their WMS. The 3PL is optimizing for their cost per pick, not your margin per order. They will batch DTC and drop-ship together when that is cheapest for them, even if the drop-ship PO has a packing slip requirement that the batch process does not enforce.

The EDI VAN owns retailer drop-ship by handing the 850 to whichever endpoint is mapped. If you have two warehouses and the mapping was set up once in 2022, every Nordstrom drop-ship PO goes to the same node regardless of whether the unit is there.

The CSR owns the edge cases by deciding manually. This is where the LA studio scenario from the opening comes from. CSRs are smart and well-intentioned and they do not have the inventory truth or the compliance matrix in front of them when they make the call.

The right owner is the head of operations, with the routing logic codified in the order management layer, not the warehouse layer. This is the load-bearing claim of this post. Wholesale should not run through Shopify’s native flow. Drop-ship should not run through the 3PL’s WMS defaults. Both belong in the order system, because the order system is the only place that holds channel commitments, retailer compliance rules, and node-level inventory at the same time.

What does a routing decision actually look like when it is made well?

A well-made routing decision evaluates five inputs in this order. Inventory truth at the SKU-node level, net of channel commitments. Compliance fit between the destination and the node (polybag, hangtag, packing slip, ASN format, label format). Capacity at the node for the required ship window. Cost-to-serve including pick, pack, freight, and expected chargeback risk. Channel priority, meaning which channel the unit is committed to if there is a conflict.

The Magnolia Pearl pattern is instructive here. When a brand runs same-day fulfillment on drops, the routing decision has to be made in seconds, not hours, because the ship window is the product. The decision logic has to live in the order system because it has to evaluate inventory net of channel commitments at the moment the order is placed, not at the moment the warehouse picks it. If routing is decided at pick time, the unit is already gone.

For multi-entity wholesale brands like Lufema, the routing decision is more about which legal entity ships against which PO under which incoterm, and which catalog the retailer ordered from through the B2B portal. The decision is rarely about physical distance. It is about which entity’s inventory pool the unit belongs to. A generic ecommerce router cannot see that distinction.

What are the operational anti-patterns to look for?

Four anti-patterns indicate the routing decision is not owned in the right place.

First, the brand has a spreadsheet that the CSR or ops manager updates daily that says “ship Nordstrom from NJ, ship Saks from KY, ship DTC from wherever has stock.” If the routing logic lives in a spreadsheet, it is not in the order system, which means it is not enforced and it is not auditable.

Second, the same SKU is sold to a DTC customer and a retailer drop-ship customer within the same hour, and one of them gets a backorder email two days later. This is the channel commitment problem. The order system is allocating against a pool that does not respect channel reservations.

Third, retailer chargebacks are running above 1 percent of wholesale revenue and the conversation inside the company is about “the 3PL has to do better.” If your retailer chargebacks exceed 1 percent of wholesale revenue, your EDI integration is the problem, not your warehouse. Compliance failures are routing failures upstream of the pick. The 3PL is following whatever instructions the EDI flow handed them.

Fourth, the head of operations cannot answer the question “for a Nordstrom drop-ship PO arriving today for a SKU we hold in both NJ and LA, which node ships it and why” without opening three tools. If the answer is not in one place, the decision is not being made in one place.

How should the decision flow be sequenced?

The right sequence for a routing decision in apparel, regardless of channel, is the same five steps in the same order. Reading them as a checklist is the point of this section.

1. Identify the channel and destination. DTC, wholesale ship-to-DC, retailer drop-ship, marketplace. Each has different compliance and SLA.
2. Pull the channel-aware available-to-sell. Not raw on-hand. ATS net of wholesale-committed pools, allocated DTC, and open POs in flight.
3. Filter nodes by compliance fit for the destination. A node that cannot produce a Nordstrom-compliant ASN does not get to ship Nordstrom drop-ship, even if the unit is there.
4. Score remaining nodes by cost-to-serve, including expected chargeback risk weighted by node compliance history.
5. Confirm capacity against the ship window and commit the allocation in the order system, not in the WMS.

Step two is where most brands fail. They route against on-hand and discover the conflict at pick time. By then the alternative node cannot meet the ship window without expedited freight, which eats the margin the routing decision was supposed to protect.

When should a brand pull routing out of Shopify and the 3PL?

The trigger is not revenue. It is operational shape. Pull routing into a dedicated order layer when any two of the following are true: you ship the same SKU to more than one channel from the same inventory pool, you run more than one retailer drop-ship program with different compliance requirements, you operate more than one fulfillment node (including a 3PL plus a brand-owned studio), or your wholesale revenue is large enough that a 1 percent chargeback rate is a number you actively monitor.

For most apparel brands this lands between $10M and $20M, which is the predictable breakpoint zone. Below that, Shopify’s native routing plus a single 3PL is usually defensible. Above $20M, brands that have not centralized routing are typically replacing 3 to 5 tools plus spreadsheets in a year-long rebuild that should have happened earlier.

What this means for an apparel operations team

The routing decision is not a setting. It is a discipline. Treating it as a setting is how brands at $15M end up with one FTE doing data plumbing six to nine hours a week and a 2 to 3 percent oversell rate at peak. The work being done is real. The work being done is also downstream of a decision nobody owns.

The head of operations owns routing. Not the warehouse manager, not the CSR lead, not the ecommerce manager. The logic lives in the order layer because the order layer is the only place that sees channel commitments, compliance rules, and node inventory at the same time. The 3PL executes against routing decisions. It does not make them. Shopify processes DTC orders. It does not route wholesale or drop-ship.

If the brand is in the $10M to $20M band and the routing decision is being made implicitly, the path forward is not to write a better runbook. It is to move the decision into the system that holds the inputs. That is what BP4 of the 6 Breakpoints framework names. Until the decision has an owner and a place to live, every season will look like the Tuesday in October the post opened with, and the chargebacks will keep arriving on Thursday.