Why Allocation Gets Hard at Three Channels
Inventory allocation for a brand selling through one channel is straightforward: you have stock, you have demand, you fulfill in order. Add a second channel and you introduce tradeoffs. Add a third — say a DTC storefront, a wholesale channel via Faire, and a physical retail presence — and the tradeoffs multiply fast enough that spreadsheet logic starts to fail.
The allocation challenge isn't purely computational. It's that the three channels have fundamentally different demand timing, different margin profiles, and different service level expectations. A stockout on your DTC site during a peak window costs you a $90 direct sale and the associated LTV. A stockout against a wholesale commitment costs you a buyer relationship and potentially a chargeback. Running too lean in your physical stores means empty fixtures on a Saturday afternoon. These aren't equivalent failures, and a good allocation framework treats them differently.
This guide walks through the core decisions in omnichannel allocation — from establishing DC buffers to handling store-to-store rebalancing — with the goal of giving planning teams a practical framework rather than a theoretical one.
Step One: Define Your Inventory Node Structure
Before you can allocate effectively, you need a clear map of where stock lives and what role each location plays. For most growing omnichannel brands, the node structure looks something like this:
- Central DC or 3PL: Master inventory position. Ships to all channels. The buffer location.
- DTC fulfillment (often the same as DC): Ships direct-to-consumer. Demand signal comes from your storefront — Shopify or similar.
- Wholesale pool: Committed or semi-committed inventory against open wholesale orders or platform commitments (Faire, etc.).
- Store network: Physical retail locations, each with their own on-hand position and localized demand patterns.
The reason this mapping matters: allocation decisions look entirely different depending on whether you're moving stock from the DC to a store vs. from one store to another vs. committing inventory to a wholesale order. Each of those movements has different lead times, different margin implications, and different reversibility.
Setting DC Buffer Rules Before You Allocate Downstream
A common allocation failure mode is committing too much inventory downstream — to stores or wholesale — before you've maintained sufficient DC buffer to handle DTC demand spikes or urgent reallocation needs. When the DC runs dry, you lose the flexibility to respond.
Buffer rules formalize how much stock the DC retains before allocating outbound. The number isn't arbitrary — it should be derived from your average DTC daily demand multiplied by your downstream replenishment lead time, plus a safety margin for demand variability.
A working example: a lifestyle apparel brand with 8 physical retail doors, a DTC site, and wholesale commitments. For their top-10 SKUs by velocity, they set a DC buffer rule of no less than 3 weeks of DTC demand before committing additional units to store replenishment. In practice this meant that if a SKU had 240 units at the DC and DTC was running at 40 units/week, the effective available-to-allocate to stores was 240 minus 120 (3 weeks x 40) = 120 units. That 120 could then be distributed across the store network based on localized demand signals.
This kind of rule prevents the scenario where stores are fully replenished on a slow week, DTC then spikes on the weekend, and there's nothing left at the DC to fulfill web orders. It's a simple constraint, but it needs to be explicitly modeled — not assumed.
Demand Signal Hierarchy: Which Channel Speaks Loudest
Not all demand signals are equal, and allocation decisions should reflect that. In most omnichannel brand structures, the signal hierarchy runs roughly as follows:
- Fulfilled wholesale commitments: Already contracted. Inventory is effectively spoken for. This isn't a demand signal — it's a liability. Reserve it first.
- Forward-committed DTC demand (pre-orders, subscriptions): Similarly contracted. Reserve before open allocation.
- Store replenishment based on coverage targets: Allocate to maintain minimum weeks-of-stock targets per location, weighted by store velocity.
- Opportunistic DTC stock building: If DC buffer allows, build DTC inventory position ahead of known demand events (promotions, editorial features, peak season).
We're not saying this hierarchy is universal — a brand with 70% of revenue in wholesale should weight those signals differently than a DTC-first brand. But having an explicit signal priority prevents the ad hoc decision-making that leads to allocation whiplash: over-shipping to stores one week, pulling back the next, leaving buyers and store managers frustrated.
Store-Level Allocation: Getting Beyond Average
The single biggest improvement most brands can make in their store allocation process is moving from an even-split or category-average distribution to a store-velocity-weighted distribution.
Even-split allocation — dividing available units equally across all store locations — is the path of least resistance, but it consistently produces the wrong result. A downtown flagship location selling 15 units/week of a specific SKU gets the same replenishment as a suburban strip-mall store selling 4 units/week. Within two weeks, the flagship has a stockout. The strip-mall store has 3 weeks of excess stock it may never sell through at full price.
Velocity-weighted allocation assigns replenishment units in proportion to each store's actual selling rate. It requires reliable POS data at the SKU-store level, which is now table stakes for any brand running retail planning software or even a structured spreadsheet approach. The output is a distribution key — a percentage share of available units that each store receives — that updates as velocity patterns shift.
An additional refinement: segmenting stores not just by velocity but by sell-through profile. Some stores are strong early-season performers on new arrivals; others run strong on carryover inventory. Allocating new-arrival units to early-sell-through stores and replenishment units to carryover-strong stores is a meaningful improvement over treating all locations as interchangeable.
Store-to-Store Rebalancing: When to Pull vs. Push
Even with good initial allocation, inventory positions drift over time as localized demand varies from forecast. A store that was allocated correctly in week one may have 8 weeks of stock in week six if a local competitor ran a promotion or the weather didn't cooperate. Meanwhile, a different door may be running at 1.5 weeks of stock and heading toward a weekend stockout.
Store-to-store rebalancing — physically moving inventory between locations — is the corrective mechanism. It's also the one most brands do inconsistently because the decision triggers are unclear and the operational friction (pick, pack, ship between stores) feels disproportionate to the benefit.
The way to make rebalancing systematic is to define a rebalancing trigger: a WOS differential threshold between locations that, once exceeded, generates a transfer recommendation. For example: if Store A has greater than 10 weeks of stock and Store B has less than 3 weeks of stock for the same SKU, generate a transfer recommendation for N units from A to B, where N brings both stores to approximately equal WOS coverage.
The threshold matters. Too tight, and you're running constant micro-transfers that don't justify the logistics cost. Too loose, and stockouts compound before you act. The right threshold depends on your transfer lead time, transfer cost per unit, and the margin risk of a lost sale — parameters that vary by brand but can be reasonably estimated.
The Wholesale Allocation Lock-In Problem
Wholesale allocation creates a particular challenge that DTC-only brands never face: inventory commitment visibility lag. When a wholesale buyer places a seasonal order in January for a March delivery, that inventory is spoken for — but it may not be physically reserved in your system until the order ships. In the intervening weeks, planning teams may inadvertently over-allocate those same units to DTC or stores, discovering the conflict only when the wholesale pick is imminent.
The fix is explicit wholesale reservation at the time of order confirmation, not at time of shipment. This means your available-to-allocate calculation for all other channels should exclude units committed to wholesale, regardless of how far out the wholesale ship date is.
This sounds obvious, but it requires your inventory system to distinguish between "on hand" and "available to allocate" — a distinction that many growing brands are still managing in a spreadsheet where those two columns are frequently confused. Getting that distinction right is a foundational requirement for any serious omnichannel allocation framework.
Allocation is ultimately a prioritization problem with time constraints. The brands that handle it well aren't necessarily using more sophisticated tools than the ones that struggle — they've just formalized the decision rules that their planning teams would otherwise improvise. Written-down rules beat intuition at scale.
