Managing Product Assortment Exceptions Without Fragmenting a Retail Brand

A retail chain needs enough consistency to be recognisable and enough flexibility to serve different neighbourhoods. A branch near a university may need smaller pack sizes and late-evening essentials, while a suburban family store may sell more bulk formats. Uncontrolled local variation creates confusing customer expectations, scattered purchasing, and inaccurate online availability. Overly rigid central control can be equally damaging when stores are forced to carry items that do not fit local demand. Assortment exception governance gives teams a structured way to test local needs while preserving the economics and identity of the wider range.

Define the operating boundary

Separate the core range from approved local extensions and temporary substitutions. The core range represents the chain's minimum promise: products customers should reasonably expect at every eligible branch. A local extension is an intentional addition based on evidence such as customer requests, sales patterns, or a distinctive catchment. A substitution is a short-term response to supply interruption and should not quietly become permanent. These states need different approval paths. Without explicit labels, a temporary workaround can be mistaken for a strategic assortment decision, and local teams may continue buying products long after the original need has disappeared.

Choose evidence that supports a decision

Require a concise business case for each proposed exception. The case should state the customer segment being served, the unmet need, expected demand, supplier availability, gross-margin assumptions, storage or display implications, and the planned review date. Include evidence from the branch's actual catchment rather than relying on a manager's personal preference. A store serving commuters might demonstrate requests for travel-size products during a defined time window; another branch might cite repeat enquiries that cannot be fulfilled by the core range. Small tests can be useful, but the proposal must explain what result would justify continuation.

Assign responsibility at the right level

Evaluate the operational cost of variation before approving a new item. Every additional SKU may affect replenishment, shelf labels, staff knowledge, stock counts, shrinkage, and customer support. If the product requires special handling, age checks, temperature control, or regulated claims, the approval should include the relevant specialist. A product that sells a few units but creates frequent stock adjustments may be less valuable than its gross margin suggests. Procurement should also examine minimum order quantities and supplier reliability, since an assortment exception can introduce disproportionate complexity when a vendor serves only one small outlet.

Give each exception a clear scope. Specify the eligible branch IDs, start date, maximum test duration, stock ceiling, and whether the item may appear in local advertising or the chain's store locator. This prevents an approved pilot from being copied informally to other locations. If online listings show product availability, connect the listing rule to inventory confidence: being authorised to sell an item does not mean the branch currently has it. Where stock feeds are delayed, use a cautious customer-facing claim and provide a route for confirming availability before travel.

Learn from the results

Design the test around a decision, not just a sales target. Track units sold, margin after markdowns, stockout days, write-offs, basket attachment, customer requests fulfilled, and replenishment effort. Compare with a sensible baseline and account for promotions or unusual local events. A low-volume branch may need a longer observation period than a flagship store, but do not extend the test indefinitely because results are inconclusive. Record the threshold for success in advance, such as contribution after handling costs or a meaningful reduction in unmet requests.

Operational example

Imagine a chain tests regional breakfast products in four outlets. Two perform well because nearby offices create morning demand; one has low sales because the product arrives after the commuter peak; the fourth records waste because customers prefer a different pack size. The correct conclusion is not automatically to approve or reject the product network-wide. The evidence may support a time-specific delivery adjustment, a pack-size change, and a narrower eligible-store list. Exception governance preserves these distinctions instead of flattening every branch result into one average.

Review and governance

When an exception is approved, update the systems and people who depend on the decision. Purchasing needs the vendor and reorder parameters; store staff need product knowledge and substitution guidance; finance needs the correct margin and tax treatment; digital teams need accurate listing rules; and customer support needs to know which branches can fulfil enquiries. Assign one owner to coordinate the launch and make the approved scope discoverable. A decision stored only in an email thread will eventually be forgotten, especially when a manager transfers or a regional team reorganises.

Measures of durable improvement

Schedule an expiry review and make renewal an active decision. At the review, compare the original hypothesis with actual results, note any operational side effects, and decide whether to retain, modify, expand, or stop the exception. If the item becomes part of the standard range, formally move it into the core-range process rather than leaving it in a permanent exception state. If it is removed, define how remaining inventory will be sold or transferred and when digital claims must be updated. These closure steps prevent old pilots from accumulating into an undocumented second assortment strategy.

Implementation checklist

• Define core range, local extension, and temporary substitution separately.
• Require a customer need and cost-to-serve rationale.
• Limit approval to named branches and a fixed test period.
• Connect listings and advertising to verified availability.
• Renew, standardise, or close each exception at review.

Conclusion

The goal is not to eliminate local judgement; it is to make local judgement measurable and reversible. A well-run exception process gives branch managers a legitimate route to serve their customers while protecting purchasing discipline, digital accuracy, and brand coherence. Start with a narrow pilot, document the reason for every deviation, and insist that each exception has an owner and an end date. Over time, the resulting evidence can reveal which local needs deserve a permanent place in the chain's operating model.