Running Wholesale and DTC Together: The Operating Model Decision for Fashion Brands

Wholesale plus DTC is the operating model most growing apparel brands arrive at whether they planned to or not. The brand started DTC on Shopify, picked up a few wholesale accounts, those accounts grew, a buyer at a major retailer showed up, the brand said yes, and suddenly the spreadsheet that tracked orders is doing the work of three systems. Somewhere in that arc, the question stopped being "should we do wholesale?" and started being "how do we run wholesale and DTC without them cannibalising each other?"

This is about that second question. Specifically: how to design the inventory allocation, the order flow, and the operational system architecture so that both channels get what they need out of one connected operation.

The core problem: one physical inventory, two commercial logics

Wholesale and DTC share the same warehouse, the same SKUs, the same production plan. They sell against the same physical stock. The rest of the operating model is different in almost every dimension:

• Time horizon. DTC sells on demand, day-to-day. Wholesale books pre-season — units are committed months before they ship.
• Pricing. DTC sells at retail. Wholesale sells at 40–60% of retail with trading terms, credit, and sometimes consignment or NFR allowances.
• Order size. DTC orders are 1–3 units. Wholesale orders are hundreds to thousands.
• Fulfilment cadence. DTC ships same day or next. Wholesale ships on a scheduled release window, often weeks after the order is booked.
• Customer service risk. An oversold wholesale order is a broken retailer relationship and a pulled PO. An oversold DTC order is a refund and a customer service hour. Both are painful; wholesale is more expensive.

Running both out of one physical inventory without explicit allocation rules means whichever channel touches the inventory first wins. That's usually DTC, because DTC sells in real time and wholesale books ahead. The result is the pattern every apparel ops lead has seen: DTC sells through the first drop aggressively, wholesale pre-book commitments have to be de-allocated, wholesale customer gets a partial ship, buyer is unhappy, next season's order is smaller or gone.

The allocation playbook

Well-run wholesale+DTC operations don't solve this with more communication. They solve it with explicit allocation rules enforced by the system, not by a human on Slack.

Rule 1: Pre-book first, release later

Wholesale pre-books are confirmed commitments with trading terms. They get allocated against incoming production before DTC sees any of it. The allocation rule: the full wholesale pre-book quantity is held against the production receipt, and only the remainder releases to DTC when the goods land.

Rule 2: Reserve percentage for DTC launch

For styles you expect to move fast on DTC — the drop pieces, the collab items, the social-media-driven SKUs — reserve a specific percentage up front. Typical rule: 40% reserved for wholesale pre-book, 60% released to DTC at launch. The reservation is a system rule, not a spreadsheet. It gets applied the moment the production is received.

Rule 3: Safety stock thresholds pause marketplace listings

Marketplaces — Amazon, Mirakl, Zalando — have their own inventory-sync cadences and oversell penalties. Best-practice apparel operations set a safety threshold per SKU that, when hit, pauses the marketplace listing automatically. Wholesale allocation uses this same threshold in reverse: the last N units of a style are reserved for wholesale or removed from DTC availability, not left exposed to marketplace over-sell.

Rule 4: Channel-specific price lists, one product master

The product master — the style, colour, size, image, description — is one record. Channel-specific pricing, trading terms, and MAP policies are applied at the order layer, not duplicated at the product layer. This is the biggest single driver of product-data consistency across channels, and the absence of it is the most common cause of wholesale customers seeing different pricing than Shopify — which is a compliance and relationship problem, not a technical one.

The systems architecture that holds

Allocation rules only work if the system enforcing them is the system both channels read from. This is the core argument for running wholesale plus DTC from one connected operational platform:

• One inventory pool visible to wholesale reps, DTC front-ends, and the warehouse in real time.
• One order queue that holds wholesale POs, DTC orders, marketplace orders, and B2B portal orders against the same inventory.
• One allocation engine that applies the pre-book, reservation, and safety-threshold rules at receipt, not at ship.
• One warehouse workflow that picks and packs wholesale orders (large, consolidated, often prepack) and DTC orders (small, individual) against the same inventory ledger.
• One reporting layer that shows sell-through by channel, wholesale backlog, and DTC performance from the same source.

Brands that run wholesale and DTC from separate systems — Shopify for DTC, spreadsheets for wholesale, a 3PL portal for fulfilment — end up reconciling across three truths. Every reconciliation is a moment where the rule fails and someone oversells.

The common mistakes

Mistake 1: Treating wholesale as "the same thing but bigger"

It is not. Wholesale has different commercial terms, different fulfilment expectations, different compliance (EDI, routing guides, labelling), and different customer service implications. Systems that treat wholesale as "DTC orders with a bigger quantity" fail on all four.

Mistake 2: Running wholesale on a spreadsheet past $5M

Once wholesale crosses $5M and involves more than a handful of accounts, the spreadsheet stops working for the same reason spreadsheets stop working for DTC at scale: allocation, reconciliation, and reporting all fall apart. The spreadsheet moment applies to wholesale too, usually earlier than it applies to DTC.

Mistake 3: Running two systems that are "integrated"

Shopify + a wholesale tool like JOOR or NuOrder "integrated" via middleware is the most common architecture for brands that outgrow spreadsheets but haven't yet consolidated. It works until it doesn't. The integration is where the latency, the oversell risk, and the reconciliation work live. Brands running this architecture typically still have a reconciliation spreadsheet — it just has a different name now.

Mistake 4: Waiting for revenue to hit a threshold

The decision to consolidate is an operational-model decision, not a revenue one. A $10M brand running wholesale plus DTC through a 3PL has the operational profile that justifies consolidation. A $25M DTC-only Shopify brand does not. "We're not big enough yet" is usually a way to postpone a decision that's already come due.

What "doing wholesale + DTC well" looks like

The operational benchmark for a mid-market apparel brand running both channels well:

• Oversell rate below 0.5% across both channels
• Wholesale pre-book fulfilment at or above 98% on committed units
• No weekly reconciliation spreadsheet between channels
• DTC inventory availability on Shopify refreshes in real time, not on a 15-minute batch
• Wholesale reps can see live availability at a booth without calling the office
• Season close takes days, not weeks

Brands hitting these numbers almost always have one system as the operational spine — typically an apparel-specific ERP — with Shopify, marketplaces, and 3PLs as connected channels rather than parallel systems of record.

If you're running wholesale and DTC from separate systems today and any of the mistakes above are familiar, the operational architecture is the decision to revisit. Not a tool swap — a model change. Start with a discovery conversation to walk through your specific allocation flow and identify where the reconciliation work currently lives.

Related: Wholesale + B2B operations on Uphance, DTC + Shopify on Uphance.