Moving beyond cost-plus: a retailer's migration guide

Cost-plus got your business here. It is transparent, quick to apply across thousands of SKUs, and easy to defend in a margin review. It also ignores what competitors charge, what customers will pay, and what each SKU does for the basket. Retailgrid is usually adopted at exactly this transition point - when a retailer is ready to keep cost as the floor and let competitive and demand signals decide the price above it.

Signals you have outgrown markup tables

• Competitors undercut you on visible items while you sit above the market on invisible ones
• Category margin holds on paper but realised margin erodes through unplanned markdowns
• Nobody can explain why a specific markup band was chosen - it predates the current team
• Repricing happens quarterly because the manual effort is too high to run more often

Phase 1: Fix the cost data first

No pricing method survives bad inputs. Before changing methodology, reconcile landed cost across the catalog: unit cost, freight, duty, handling, and returns provision. Retailers who skip this step migrate to a sophisticated model and get sophisticated wrong answers.

Also settle the markup-versus-margin ambiguity in writing. A 30% markup is a 23% margin, and teams using the terms interchangeably will be several points off across the whole assortment.

Phase 2: Classify before you optimise

Not every SKU deserves the same treatment. Split the catalog into roles: traffic drivers that shoppers price-check, margin builders that fund the category, and long-tail items with no reliable competitor match.

Product role classification makes this operational rather than a one-off workshop. The migration then becomes targeted - apply competitive logic to the top few hundred SKUs where it changes outcomes, and keep rules-based markup on the tail where elasticity data is noise.

Phase 3: Layer competitive position onto the floor

Cost-plus becomes the floor, not the answer. For traffic drivers, position against the market: match the competitor minimum, hold a defined index against a named competitor set, or maintain a fixed gap.

This requires live data. Competitive pricing rules only work when competitor price tracking is continuous and matched to your SKUs - a weekly manual check covers a fraction of a percent of a real catalog and misses every intraday move.

Phase 4: Introduce elasticity where the data supports it

On SKUs with sufficient sales history, elasticity tells you where price can rise without volume loss and where a small cut buys disproportionate units. This is where price optimization replaces judgement - proposing the margin-optimal price per SKU inside your rules, scored for confidence.

Confidence scoring matters more than the recommendation itself. It tells you which suggestions to auto-approve and which need a human, so the team's attention goes where it changes money.

Phase 5: Run both models in parallel

Do not flip the whole catalog at once. Pick two categories, run the new logic alongside existing markup pricing for a full cycle, and compare realised margin, sell-through, and price index. Parallel running produces the internal evidence that makes the wider rollout uncontested.

Phase 6: Make rules the system of record

The end state is not "no more cost-plus". It is a layered model: cost sets the floor, rules enforce discipline - rounding, daily change caps, category margin minimums - and optimisation decides the price within those bounds.

Rules-based pricing keeps that logic auditable and version-controlled, which is the difference between a pricing method the business owns and one that lives in a single analyst's workbook.

Book a demo and explore a smarter approach to retail pricing.