Same Range in Every Store: Why It Underperforms

A shared brand promise does not require identical depth

Stores can serve different climates, shopping missions and space constraints while retaining a common brand proposition. A single assortment may place heavy outerwear where lightweight layering has stronger demand. Sending less of the same range does not necessarily fix the mismatch.

This article concerns the category and option mix chosen for a store group. It differs from moving an existing slow line between locations. Core supports the forward range decision; Core Plus helps review how the accepted range reaches stores within the supported grade, size and capacity settings.

Make the store group explain a commercial difference

Use a small number of groups whose differences the buyer can describe and test. Climate can suggest a hypothesis, but it is not a substitute for actual demand and availability evidence. Store size and customer mission may explain why two locations in the same region need different depth.

Core Plus supports location grading and size-related allocation inputs. Confirm how the intended assortment groups map to the configured store structure. The article does not claim an automatic demographic clustering engine, weather feed or unlimited store-specific range generator.

Compare two mixes across the same four stores

The worked range serves two warm-location stores and two cool-location stores, with 200 units per group. The uniform plan gives each group eighty lightweight knits and 120 coats, totalling 160 knits and 240 coats. At $20 and $40 unit costs, stock cost is $12,800.

The localised proposal gives the warm group 140 knits and sixty coats; the cool group sixty knits and 140 coats. Total units remain 400, but category totals become 200 of each. Stock cost is $12,000, leaving $800 against the original $12,800 envelope. The difference comes from product mix, not a supplier discount.

Read the group depth against the relevant demand

Assume weekly group demand of thirty knits and ten coats in warm locations, and ten knits and thirty coats in cool locations. These are rates for each two-store group, not for each store. Four weeks therefore require 120/40 units in warm locations and 40/120 in cool locations.

The localised quantities leave twenty units in each group-category combination after that assumed window. Total expected sales are 320 and closing stock eighty. The uniform plan gives warm knits only 2.7 weeks of cover while warm coats hold twelve, exposing a product-mix imbalance before any store transfer is considered.

Preserve common options where they earn their role

A localised proposal need not create a completely separate collection for every store. Retain a shared core where customer need is consistent, then specify which category or option module changes by group. The example changes knit and coat depth while keeping a recognisable overall range.

Core connects the revised quantities with the budget and MFP/WSSI. Confirm the costs and expected demand rather than assume local relevance always costs less. Here, forty planned coat units become forty knit units, reducing the cost by $800 under the stated prices; a different range could increase it.

Test the allocation that turns the range into stock

Core Plus supports buy grades, size curves, capacity and store-level overrides. Check those inputs after accepting the range mix. A group total can still conceal an unsuitable local size split or a store unable to hold the intended quantity. Do not stop the review at the category balance.

Keep the forward buying proposal distinct from existing stock. The animation does not move forty coats out of a warm store or place a supplier order. It compares uncommitted range structures; any real allocation, transfer or order change needs its own source, timing and authorisation.

Review exceptions before growing the complexity

For this range, the proposed mix is 140/60 for warm locations and 60/140 for cool locations, with a four-week closing assumption of twenty per combination. Confirm the group rates, costs and usable dates, then choose a review point for actual trading.

If one store repeatedly needs an exception, inspect whether the group definition is wrong before adding another permanent override. Merchmix connects the range and allocation discussion so local relevance can stay manageable. Different stores need a justified product offer, not an ever-growing collection of unexplained exceptions.

Common questions