Why Sending Everything to Stores Up Front Backfires

The first drop should serve a window, not empty a warehouse

Sending every unit to stores can feel like progress because goods reach the selling floor. It also commits the location of stock before demand has tested the opening assumption. A slower store can then hold stock the faster branch needs, with another movement required to correct the decision.

Core Plus’s allocation workspace brings the shared stock pool, store quantities and stock held at the distribution centre into the review. Its DC holdback and store-by-size context help the owner inspect the proposed release. Decide what the first drop must support and when another usable receipt can respond; a visible reserve is not automatically available in every required size.

Compare the local cover behind the first release

The worked Everyday crew knit range owns 600 units for three stores. Assumed weekly demand is thirty, twenty and ten units. A full initial release of 300, 180 and 120 creates ten, nine and twelve weeks of local cover before any sales occur.

Those quantities are not wrong solely because they are large. Lead times, presentation needs and capacity matter. The concern is whether the business needs that much stock fixed in each location before learning more, especially when those quantities leave no central units for a later response.

Retain a reserve with an explicit first-review point

A phased alternative releases 120, ninety and sixty units, a 270-unit opening drop, while holding 330 centrally. Local cover becomes four, 4.5 and six weeks. The same 600 units remain owned; the distribution and timing of release change.

After two weeks at the assumed rates, store balances are sixty, fifty and forty. A proposed top-up of sixty, thirty and ten would leave stores with 120, eighty and fifty, and the central reserve with 230. Total owned stock is then 480 after 120 completed sales.

Do not treat the reserve as free stock for every request

The 330 central units are shared supply, not an allowance each store can claim independently. Review competing needs, sizes and existing movements before deciding the proposed hundred-unit top-up. If the right size is unavailable, an aggregate reserve total cannot fulfil it.

Core Plus supports refill models, minimums, maximums and store overrides. Confirm the configured policy and source position before release. The example uses a reviewable top-up; it does not assume the warehouse automatically follows this quantity or that every transfer can arrive instantly.

The central 330 units equal 5.5 weeks at the combined sixty-unit weekly rate, but that network ratio does not describe any store’s usable cover. A reserve concentrated in the wrong sizes or held behind a slow receiving process can be less responsive than its aggregate figure suggests. Review the response path as well as the percentage held.

The animation adds an illustrative S/M/L source split of 150/300/150. The phased opening leaves 83/164/83 centrally, totalling 330. Its later hundred-unit proposal uses 24/52/24 across those sizes, leaving 59/112/59, or 230 centrally. These are worked size quantities, not a recommended curve or evidence of actual store demand.

Check capacity and handling alongside cover

A full release may fit the quantity plan and still exceed a store’s practical capacity. A phased release can reduce local exposure while increasing handling frequency. Compare those consequences using the actual route, staffing and physical constraints rather than declare one method universally cheaper.

The worked example does not calculate transport or handling expense. At a common $25 unit cost, the original 600 units cost $15,000 regardless of their first location. Retaining stock centrally does not reduce that purchase cost or create a cash saving by itself.

Let the first trading period change the next release

Use the next review to compare actual selling with the original assumptions. A faster rate may justify earlier suitable stock; a slower rate may justify retaining more centrally. Recalculate from the current balance so the original allocation and an open top-up are not counted twice.

Core Plus gives the allocation owner a consistent operational context for the response. A proposal is separate from an authorised movement and a receipt. Keep transit and usable arrival visible so the reserve supports the customer before the shortage rather than merely improving a projected cover figure.

Set the next review before the shortest local cover reaches the effective replenishment lead time. Include the time needed to inspect the proposal, pick, move and receive it. The opening allocation must support that complete response interval, not only the vehicle’s travel time.

Approve flexibility that can actually be used

The phased opening in this comparison is 270 units with 330 held centrally, not a universal 55% holdback recommendation. Its suitability depends on the demand horizon, sizes and replenishment response. The later hundred-unit proposal remains under review.

The useful first allocation leaves each store enough relevant stock and the network a credible way to respond. Merchmix Core Plus connects those choices so the retailer can review the next release on evidence instead of treating a cleared distribution centre as proof of a completed allocation strategy.

Common questions