Right units to the right doors.
Allocation that rebalances across doors first, then stages what's left — lead-time aware, demand-weighted, and tied to the plan.
Right units to the right doors
Rebalance across doors first, then place the rest — demand-weighted, Winners protected.
Why allocation makes or breaks store cover.
Full-price sell-through gap between retail leaders and the field — driven by whether the units land in the right doors.
Source: Directional industry benchmark
Share of unplanned markdown that traces to stock landing in the wrong doors — over-covered here, stocked out there.
Source: Coresight industry research
Units rebalanced across the network in a typical week — cover moved to where demand is, without a new PO.
Source: Representative mid-market retailer
What breaks before allocation runs to plan.
Three steps to a split that lands in cover.
Each door's share from its own velocity
Every door's size curve and seasonal lift is learned from its own sales — the split is weighted to real demand per location, not last year spread flat across the fleet.
Rebalance across doors before you reorder
Over-covered doors ship their surplus to under-covered ones first. Free cover moves where demand is — no new PO raised until the network is balanced.
Winners protected, every door in cover
When stock is tight the capital quadrant sets priority — Winners' cover is protected first, Bleeders trimmed — so the units land where they earn, inside the 6–8 week band.
Allocate to demand, not averages.
Allocation that rebalances across doors first, then stages what's left — lead-time aware, demand-weighted, and tied to the plan.
| Door | Quadrant | Cover | Placed | Status |
|---|---|---|---|---|
| D-014 · high-vel | Winner | 3.1w → 7.2w | +260u | in cover |
| D-002 · flagship | Winner | 4.0w → 7.0w | +180u | in cover |
| D-008 · high-vel | Winner | 5.2w → 7.4w | +140u | in cover |
| D-021 · mid | Traffic | 5.6w → 7.1w | +90u | in cover |
| D-037 · mid | Traffic | 6.4w → 7.0w | +40u | in cover |
| D-031 · outlet | Bleeder | 11.4w → 8.0w | −140u | rebalanced out |
| D-042 · mall | Sleeper | 10.2w → 8.0w | −120u | rebalanced out |
| D-011 · flagship | Winner | 6.9w → 7.2w | +30u | in cover |
| D-045 · small | Sleeper | 4.8w → 6.2w | +60u | short |
Meet your Allocation agent
Distributes each receipt across doors demand-weighted, rebalances surplus from over-covered doors before raising any PO, and protects Winners' cover when stock is tight.
Meet the agentsRe-forecast ready — 3 categories have drifted from plan this week. Want me to stage the moves for your review?
“One of the most exciting propositions we've ever brought into the business. There is so much power under the hood that we honestly can't picture running the category without it now.”
Hero SKU availability
The allocation you run today, and the one Tightly delivers.
Allocation is one part of the connected plan.
Replenishment
When rebalancing can't cover a door, replenishment raises the reorder — same cover policy and lead times.
Demand forecasting
Per-location velocity forecasts drive the split — every door weighted to its own demand.
In-season management
As sell-through moves, the capital quadrant re-classifies each door — allocation priority follows.
Does it rebalance across locations before ordering?
Yes. Every SKU × location has its own cover, and Tightly proposes transfers from over-covered doors to under-covered ones first — you only raise a new PO for what the network genuinely can't cover.
How does it decide which doors get units when stock is tight?
By the capital quadrant, computed per variant per location — Winners (fast-selling and profitable) get their cover protected first; Bleeders (slow and low-margin) are trimmed. Scarce units land where they earn.
How is each door's size curve set?
From that door's own sales, not a fleet average — DTC, wholesale and each retail door get their own curve, so the middle sizes don't stock out while the tails mark down.
Does it write to our WMS / ERP?
Yes. Allocations and transfers stage as drafts to your system of record on approval — nothing auto-commits, and every override carries a reason and a name in the audit log.
Right units, right doors. Allocation that moves with demand.
There's nothing to rip out. Tightly runs on your existing ERP, EDI, e-commerce and POS. Give us 30 minutes and we'll show it on your own categories.