What Goes Into a Wholesale Allocation Policy in Apparel

It is Tuesday in February. Spring 1 lands at the warehouse on Friday. Sales has already pre-sold 140 percent of the receipt to a mix of majors, specialty, and one international distributor. The DTC team is planning a Friday drop on the same SKUs. The planner has a spreadsheet with three tabs and a color-coded priority list that only she understands. By Thursday afternoon, two reps are escalating to the VP of Sales, the 3PL has been told to hold shipments until further notice, and someone in finance is asking why the same units appear committed in NuOrder and available on Shopify. Nobody is doing anything wrong. There is just no policy.

What is a wholesale allocation policy in apparel?

A wholesale allocation policy apparel operations teams can actually run is the written, channel-aware ruleset that decides which buyer, which door, and which channel receives units when committed demand exceeds available supply. It is not a planner’s instinct. It is not a Slack thread. It is a document, encoded into the system that holds your inventory of record, that answers four questions before the season starts: who is tier one, what protected pool sits behind each channel, what triggers a reallocation, and who is authorized to override.

Most brands in the $5M to $100M band do not have one. They have habits. The habits work until receipts slip, a major launches a chargeback program, or DTC and wholesale start fighting over the same SKU pool. Then the habits stop working and the planner starts working sixty-hour weeks.

This sits squarely inside Breakpoint 4 of the 6 Breakpoints framework, where order flow becomes harder to trust. Order flow does not break because the order entry tool is wrong. It breaks because the rules that govern what an order is allowed to consume were never written down.

Why does allocation become political instead of operational?

When I am sitting across from a buyer comparing vendors, the conversation about allocation almost always starts with a story about a fight. A rep got cut. A major got short-shipped. A drop sold out in eleven minutes and the wholesale team found out the units they had been promised had been moved into DTC the night before. The buyer is not asking me about features. They are asking me how to stop the fight.

The fight happens because three things are simultaneously true in most apparel operations stacks. The ERP or order management tool shows one available-to-sell number. The ecommerce platform shows another. The 3PL has a third. When a rep enters an order in the wholesale system, it commits against pool A. When a customer adds to cart on Shopify, it decrements pool B. Nobody is reconciling these in real time, so the same unit gets sold twice.

For a $15M brand running wholesale plus DTC plus a 3PL, we typically see six to nine hours a week of someone reconciling inventory across Shopify, the 3PL, and wholesale, and a two to three percent oversell rate at peak. That is one FTE effectively doing data plumbing. None of that work shows up in a planner’s job description. All of it disappears the moment the underlying pools are channel-aware and the allocation rules are encoded.

What are the components of a defensible allocation policy?

A policy that holds up under pressure has six parts. None of them are exotic. The discipline is writing them down and putting them in the system, not in a planner’s head.

Tiered customer groups

Not every account is equal, and pretending otherwise produces the worst outcomes for everyone. A defensible policy assigns every wholesale account to a tier. Tier one is the strategic majors and the specialty doors you would protect at any cost. Tier two is the bulk of the book. Tier three is opportunistic, including off-price and clearance channels. When supply is short, the system fills tier one to one hundred percent of order, tier two to a published fill rate target, and tier three from what is left. Reps know this before the season. Buyers know this before they write the order. There is nothing to negotiate.

A protected wholesale-committed pool

This is the architectural piece most brands miss. The units that have been written into pre-season wholesale orders do not belong in the DTC available-to-sell pool. They belong in a separate, named, protected pool that ecommerce cannot touch. Lufema, a multi-entity wholesale distributor we work with, runs this pattern across three brands and over one hundred retailer accounts. Their inventory accuracy sits at roughly ninety-nine percent, up from the ninety to ninety-five percent range they lived in before. They also carry about twenty percent less excess stock, because they are no longer over-buying to cover the oversell risk. The protected pool is the single biggest unlock.

Channel-aware ATS

Available-to-sell is not one number. It is a number per channel, calculated from the same physical inventory but governed by different rules. DTC ATS is on-hand minus DTC-committed minus a safety buffer. Wholesale ATS is on-hand plus inbound POs landing inside the ship window, minus wholesale-committed, minus the DTC protected pool. The two numbers should never be the same and should never be derived from the same query. The objections I hear most often in evaluations are about exactly this point: “our ERP shows one ATS number and our ecommerce shows another, and they never agree.” They are not supposed to agree. They are supposed to be different by design.

Ship-window logic

Wholesale orders carry start ship and cancel dates. A policy that ignores ship windows allocates inventory against orders that cannot legally ship for another six weeks, which means DTC sees those units as unavailable when they functionally are. A defensible policy allocates against the rolling ship window, not against the full open order book. Units committed to a June ship date do not need to be protected from a March drop. The system should know this without a human re-running the calculation.

A documented exception path

Exceptions will happen. A tier two account will get bumped to tier one for a specific season. A rep will pull strings for a buyer. A merch director will pull units back from wholesale to support a marketing campaign. None of that is wrong. What is wrong is when exceptions happen verbally and the system does not record them. Every exception should have a named approver, a reason code, and a unit count. When you look back at the season and ask why the fill rate to a major slipped, you should be able to trace it to specific exception entries, not to a vague memory of “sales pulled units in March.”

A reallocation trigger

Receipts slip. Production delivers ninety units against a hundred-unit PO. The policy should specify what happens automatically when supply drops below committed demand. Does the system pro-rate down across tier two? Does it hold tier one whole and absorb the entire cut in tier three? Does it alert the planner to make a manual call? All three are valid choices. Picking one in advance and writing it down is what separates a policy from a guess.

When does the lack of a policy actually cost money?

Policy debt does not show up evenly. It shows up at three predictable moments.

The first is at receipt. When inventory arrives short, the planner spends an afternoon manually figuring out who gets cut. The cost is the afternoon plus the trust damage with whichever account gets cut without a conversation.

The second is at the drop. When DTC and wholesale share a SKU pool and the drop sells through faster than expected, the brand either oversells DTC and eats refund costs and customer service load, or it oversells wholesale and absorbs chargebacks. At two to three percent oversell on a $15M business, that is meaningful money sitting on the floor.

The third is at the end of season. Without tiered allocation discipline, brands consistently end the season with too much inventory in the wrong channel. The off-price markdowns that follow are not a merchandising failure. They are an allocation failure that surfaced six months later.

If your retailer chargebacks exceed one percent of wholesale revenue, the allocation policy is almost certainly part of the problem, not just the EDI integration. Chargebacks for short-ships and late-ships trace back to commitments the system never should have accepted in the first place.

How should the policy live inside the system?

The policy is a document. The enforcement is architecture. The two have to match, and the architecture has to make the right behavior the default behavior.

That means customer tiers are a field on the account record, not a tag in a planner’s spreadsheet. It means the wholesale-committed pool is a real pool in the inventory system, with its own ledger, not a column in a report. It means ATS is calculated by the system at the moment of order entry or cart add, not pre-calculated and cached overnight. It means ship-window logic runs against the live PO book, not a snapshot. It means exceptions are recorded with approver and reason, in the system, at the moment they happen.

Most brands at the $10M to $20M breakpoint try to enforce policy through process discipline alone, on top of disconnected tools. It does not work. The planner becomes the policy, and when the planner is on vacation, the policy is on vacation too. The reason brands at this stage typically replace three to five tools plus spreadsheets is not because the tools are bad individually. It is because policy enforcement has to live in one place, and no individual tool was designed to hold it.

What does a working allocation cadence look like in season?

During the selling season, a brand running a defensible policy operates on a tight, predictable cadence. Open-to-buy gets reviewed weekly, not monthly. Monthly is too slow once orders are actively being written and receipts are actively landing. The allocation snapshot, who is committed for what, against which pool, with which ship window, is refreshed at the same cadence and shared with sales before any escalation happens.

Reallocation decisions happen in a scheduled meeting with named owners, not in ad hoc Slack threads. When a PO slips, the planner runs the documented reallocation logic, the exception entries get made, and the affected reps get notified before the buyer calls. None of this is glamorous. All of it is the difference between an operations team that controls the season and one that gets dragged through it.

What this means for an apparel operations team

The instinct, when allocation gets messy, is to hire another planner or buy a better order management tool. Neither solves the underlying problem. The underlying problem is that the rules governing what an order is allowed to consume have never been written down, and the inventory pools the rules would govern do not exist as distinct architectural objects.

The work is to write the policy first, on paper, with sales and merchandising in the room, before any system conversation. Decide your tiers. Decide your fill rate targets per tier. Decide what gets protected from DTC and what gets exposed. Decide your reallocation trigger. Decide who can override and what they have to record when they do.

Then put it in the system. A wholesale allocation policy that lives only in a planner’s head is not a policy. It is a single point of failure. The brands that get past Breakpoint 4 are the ones that treated allocation as architecture, not as a recurring negotiation, and built the protected pools and channel-aware ATS that make the policy enforceable without a human in the middle of every decision.