When Factory Lead Times Move Mid-Season: An Allocation Playbook

It is Tuesday morning. The production coordinator forwards an email from the cut-and-sew partner in Portugal: the FW knit program is going to land three weeks late, staggered across two shipments instead of one. Sixteen wholesale POs are already confirmed against those units, with ship windows starting in nine days. Two DTC drops are on the marketing calendar. The 3PL is expecting an ASN for the original inbound. Nobody has told the wholesale ops lead yet. Nobody has told the CFO. Within an hour, the buyer at a major specialty account is going to ask whether her order still ships on time, and the honest answer is that no one in the building can say.

This is the moment a factory lead time change allocation playbook either exists or it does not. Most brands in the $10M to $20M band do not have one written down. What they have is a group chat, a merchandiser who knows the accounts in her head, and a spreadsheet that gets rebuilt every time a factory slips. That works until it does not, and the cost of it not working is measurable.

What is a factory lead time change allocation playbook?

A factory lead time change allocation playbook is the pre-agreed sequence a brand runs when a supplier moves a delivery date after orders are already committed. It answers, in order: which channels get cut first, which accounts get held whole, which drops get pushed, which POs get split-shipped, and who communicates what to whom on what day. It is not a policy document. It is an operational routine that ties production reality to order flow, inventory truth, and warehouse execution without requiring the merchandiser to hold the whole picture in her head.

The playbook has three layers. The first is signal: how the lead time change gets detected and posted to a system of record that the rest of the org sees. The second is decision: the rules that determine reallocation without a meeting. The third is execution: the workflow that pushes the new dates into wholesale confirmations, DTC drop calendars, 3PL inbound schedules, and finance forecasts. Brands usually have some version of the third layer. Almost none have the first two.

Why does this belong to Breakpoint 2?

This is the classic shape of Breakpoint 2 in the 6 Breakpoints framework: production and supply execution drift from the plan, and the rest of the operation finds out too late to react cleanly. The reason the 6 Breakpoints framework exists in the form it does is that these drifts do not stay contained. A three-week slip at the factory does not just move a delivery. It corrupts the ATS that DTC is selling against, breaks the ship windows that wholesale confirmed, forces the 3PL to re-plan inbound labor, and rewrites the revenue phasing that finance already sent to the board. One event, five downstream failures, all happening in different tools.

When I started Uphance, the pattern I saw repeatedly was brands treating each of those failures as a separate fire. The production team apologized to wholesale. The DTC team quietly turned off a product page. The 3PL sent an angry email about the missing ASN. The CFO adjusted the forecast a month later when the variance showed up in the P&L. Nobody connected the four events back to the original factory slip, so nobody built the routine that would have absorbed the next one.

What does the cost look like in practice?

For a $15M brand running wholesale and DTC simultaneously with a 3PL, the baseline operational tax without a playbook is already 6 to 9 hours a week reconciling inventory across Shopify, the 3PL, and wholesale, and a 2 to 3 percent oversell rate at peak. One FTE is effectively doing data plumbing. When a factory lead time change hits, those numbers do not degrade linearly, they spike. The reconciliation window blows out for two to three weeks, oversell doubles because DTC is still selling units that are no longer arriving on the original date, and the FTE stops doing plumbing and starts doing crisis triage.

The unrecovered cost is not just labor. It is the chargebacks from the wholesale accounts that get short-shipped because someone allocated to DTC by accident. It is the markdown risk on the drop that launches three weeks late into a colder retail window. It is the buyer who does not re-order next season because the ship window was missed without a conversation. None of that shows up in a single line item, which is exactly why it keeps happening.

What is the right allocation order when supply slips?

This is where a brand has to take a position, because the default of allocating first-in-first-out across all channels is wrong for apparel. My position is that wholesale-committed units should be held whole and DTC should absorb the slip. The reason is asymmetric downside. A DTC customer who sees a delayed drop is annoyed. A wholesale buyer who gets a partial shipment inside a ship window triggers a chargeback, a compliance mark, and a harder conversation on next season’s open-to-buy. The economics are not close.

The practical rule is a wholesale-committed inventory pool that is protected from DTC ATS by default, not by exception. Channel-aware ATS is the architectural piece most brands are missing. When Shopify is looking at the same inventory number as the wholesale system, and both are looking at a 3PL feed that has not been updated since Friday, the allocation logic is guessing. It should not be guessing. The wholesale pool should be a distinct commitment, visible to DTC only as unavailable, and the reallocation on a lead time change should run against the free pool first.

Within wholesale, the ranking is not first-in-first-out either. It is a function of ship window tightness, account compliance sensitivity, and reorder relationship value. A major department store with an eight-day ship window and a strict routing guide takes priority over a specialty account with a two-week window and a flexible buyer. This is not favoritism, it is math on chargeback exposure. The playbook writes this down so the merchandiser does not have to relitigate it every time.

When should the critical path do the work instead of a person?

The signal layer of the playbook is where most brands lose the game before allocation even starts. If the factory slip is detected by an email that a coordinator reads on Tuesday, the decision layer is already three days behind. The critical path, the time-and-action calendar that tracks every style and season against milestones with automatic slippage flagging, is the piece that should catch the drift at the earliest observable point. That is usually not the ex-factory date. It is the fabric-in-house date, or the sample approval date, or the PP sample sign-off, all of which slip weeks before the ex-factory date confirms the slip.

A critical path that flags slippage against dependencies, rather than just against a single delivery date, gives operations two to four weeks of lead time on the allocation conversation instead of three days. That is the difference between rerouting a wholesale PO through split shipment and negotiating a new ship window versus short-shipping and eating the chargeback. The value of that lead time compounds because it lets the finance forecast get updated in the current period rather than as a variance next month.

What does execution look like after the decision is made?

Execution is where the playbook stops being a document and starts being a workflow. Once the reallocation is decided, six things need to happen in a specific order, ideally on the same day. The wholesale confirmations get updated with new ship windows, communicated to buyers with a specific date and a specific reason. The DTC drop calendar gets rephased and the product page unpublish or preorder decision is made explicitly. The 3PL inbound schedule gets updated so labor is not wasted receiving air. The ATS across channels gets reset against the new expected receipt date. The finance revenue phasing gets updated in the current forecast cycle. The account managers get a one-line script for each of their accounts.

The reason this works as a routine rather than a crisis is that every one of these steps has a single owner and a single system of record. When production data, order data, inventory data, warehouse data, and accounting data live in one connected system, the reallocation is a set of updates to a shared model, not a set of emails between departments. When they live in five systems and a spreadsheet, the reallocation is a week of Slack messages and a wholesale account calling to ask where their order is.

How often should this actually get run?

More often than most brands admit. Factory slips are not a black swan event, they are a monthly occurrence for any brand sourcing across multiple mills and cut-and-sew partners in a compressed seasonal calendar. The playbook should be a routine that runs the same way whether the slip is three days or three weeks. If it only comes out for the big slips, it never gets rehearsed, and when the big slip hits it does not work.

The corollary POV: run allocation reviews weekly during selling season, not monthly. Monthly is the cadence at which factory slips become visible in the forecast variance report, which is exactly the wrong end of the timeline. Weekly is the cadence at which they become visible while there is still time to reroute. The merchandising and production leads should be in the same 30-minute meeting once a week, looking at the critical path together, with the wholesale ops lead on the call. That is the meeting that prevents the Tuesday email from becoming a Friday crisis.

What this means for an apparel operations team

The playbook is not a template you can download. It is a set of decisions your brand has to make once, write down, and rehearse: which channel absorbs the slip, how the wholesale pool is protected, how the critical path surfaces drift early, and what the six execution steps look like on the day a lead time changes. Making those decisions in advance is what separates a brand that handles a factory slip in an afternoon from a brand that spends two weeks recovering from one.

The architectural piece behind the playbook is that production, inventory, order, warehouse, and accounting data have to sit close enough together that a single reallocation decision propagates cleanly. That is the work of Breakpoint 2, and it is why the framework groups these functions the way it does. A brand can run the playbook manually for a while, but the operational tax of doing so, the 6 to 9 hours a week and the 2 to 3 percent oversell, is the signal that the tooling underneath is no longer fit for the size of the business.

If your brand is in the $10M to $20M band and a factory slip currently means a week of meetings, the playbook is the near-term fix and the connected system is the durable one. Both are worth building. Neither will build itself the next time a mill in Portugal sends an email on a Tuesday morning.