How to Localise Product Assortment Across Stores Without Fragmenting the Brand

Product assortment localisation is not simply sending more of whatever sold last week. A branch serves a particular mix of households, trip purposes, weather conditions, transport patterns, and nearby alternatives. A compact outlet beside a commuter station may need portable items and fast replenishment, while a suburban showroom can support slower-consideration products and broader demonstration stock. Treating every branch as identical hides these differences; allowing every manager to buy independently creates a disconnected brand and expensive inventory.

Start with the customer evidence

Build a catchment profile from evidence rather than stereotypes. Combine transaction-level product mix, lost-sale notes, local event calendars, shelf capacity, replenishment lead time, and customer questions. Do not infer preferences from a neighbourhood’s language, income, or demographic label alone. Those clues can guide a question, but purchase behaviour and direct research should decide the assortment. Separate what customers ask for from what they actually buy, since availability gaps can suppress recorded sales.

Create controlled assortment layers

Use three assortment layers: network essentials, cluster choices, and approved local tests. Essentials protect brand recognition and core availability. Cluster choices respond to repeatable patterns shared by similar outlets, such as small-format stores or locations near universities. Local tests are temporary and carry a named owner, a start date, a quantity cap, and a decision deadline. This architecture permits meaningful variation without allowing every store to become a separate buying operation.

Test the economics before expansion

A useful example is a home-and-kitchen retailer whose coastal branches report strong demand for corrosion-resistant outdoor fittings. Before rolling out a large range, the category team checks sales per available selling day, returns, stockouts, and supplier replenishment reliability. Two stores receive a limited trial; two comparable outlets remain unchanged. The team records whether the new range attracts incremental baskets or merely replaces existing products. That distinction matters more than raw unit sales.

Account for store constraints

Set minimum evidence thresholds before approving permanent assortment changes. A single festival spike, one influential manager, or a stockout-driven sales dip is not enough. Look for repeat patterns across comparable weeks and account for price changes, promotions, and display placement. When data volume is low, label the recommendation as provisional and use customer interviews or a controlled pilot rather than pretending the forecast is precise.

Set the approval boundary

Operational feasibility belongs in the same decision as customer demand. Confirm shelf dimensions, storage conditions, staff product knowledge, supplier minimum order quantities, and replenishment frequency. A product that sells well but arrives in oversized cartons or needs specialist explanation may underperform in a tiny branch. Document substitutions and transfer options so local selection does not leave neighbouring stores with stranded stock.

Revisit the range deliberately

Review the assortment on a defined calendar, but allow urgent exception reviews when a product becomes unsafe, unavailable, or commercially unviable. Retain the reason for each removal as well as each addition. Managers should be able to see why a range differs from another branch and how to request reconsideration. Publish the approved assortment by store code, effective date, and version so buyers and floor teams act on the same list.

Judge the complete outcome

Measure success with availability of priority items, gross margin, basket attachment, markdown exposure, customer-request fulfilment, and transfer volume. Compare stores with similar format and catchment conditions instead of ranking a flagship against a kiosk. If sales improve while markdowns and emergency transfers rise sharply, the change may have shifted risk rather than created value. The right assortment is one that fits demand and can be served profitably.

Field implementation note

For rollout, ask category planners to present one proposed addition and one proposed removal for each pilot store. This forces the review to consider opportunity cost, not only the excitement of a new product. Capture the store manager’s explanation, but ask a second reviewer to check whether the explanation matches transaction and availability evidence. If a local choice is approved, update replenishment parameters and staff reference material together. Otherwise the shelf may show a new range while ordering systems continue to treat it as exceptional stock. After four weeks, revisit the test with a fixed scorecard and decide whether to expand, alter, or end it.

Decision record and follow-through

Before the next buying cycle, require a one-page decision record showing the customer signal, test stores, control stores, range change, expected margin effect, and the date of review. This makes local variation visible to both buyers and branch teams. A good decision may be to keep the existing range when evidence is weak; the discipline is in explaining why, not in changing products for its own sake.