Cost-plus vs value-based vs optimization pricing
Cost-plus, value-based, and optimization pricing each get something right - and each has a blind spot. How the three compare and when to use which.
Pricing debates in retail tend to be tribal. The finance team defends cost-plus because it protects margin. The brand team preaches value-based because it captures willingness to pay. The data team pushes optimization because it actually measures things. The truth is less tribal: each approach gets something genuinely right, each has a blind spot, and mature retailers end up combining all three - usually with pricing optimization software doing the combining. Here's the honest comparison.
Cost-plus: the floor that thinks it's a strategy
How it works: take your cost, add a markup, done. Cost €140, markup 35%, price €189.
What it gets right: profitability by construction. Every sale clears a known margin, the math is simple enough to apply across 10,000 SKUs, and it gives finance the predictability they need. There's a reason it survives: as a floor, cost-plus logic is genuinely essential - it's the ancestor of the margin floor enforcement that keeps automated pricing safe today.
The blind spot: it ignores the customer and the market completely. A fixed markup treats your bestseller and your shelf-warmer identically, overprices you out of competitive categories, and leaves money on the table wherever customers would happily pay more. Cost-plus knows what a product costs you - and nothing about what it's worth to them.
Value-based: the ceiling that's hard to measure
How it works: price according to what the product is worth to the customer - differentiation, brand, outcomes - rather than what it cost.
What it gets right: it points at the real ceiling. On differentiated products - strong brands, exclusive lines, private label with genuine distinction - customers' willingness to pay has nothing to do with your cost sheet, and value-based thinking captures margin cost-plus never sees. It's also the right instinct for products with no clean competitor match, where the market can't tell you the answer.
The blind spot: measurement. "What customers value" is easy to say and hard to quantify - in practice it often decays into gut feel with a strategy label. And it scales badly: nobody is doing willingness-to-pay analysis on 7,000 long-tail SKUs by hand.
Optimization pricing: the measurement layer
How it works: use your own transaction history to measure how demand actually responds to price - the elasticity behind each SKU - and set prices based on evidence rather than markup convention or intuition. The mechanics are what we walk through in our guide to price elasticity in retail.
What it gets right: it replaces both the cost-plus guess and the value-based guess with data. It finds the inelastic SKUs quietly carrying unused pricing power and the elastic ones bleeding volume over a 3% gap - across the whole catalog, not just the products someone has time to study. Modern platforms score every estimate by confidence, so thin-data SKUs get conservative treatment instead of false precision.
The blind spot: it needs data and guardrails. On brand-new products there's no history to learn from, and without hard constraints an optimizer will cheerfully recommend whatever the math suggests - which is why serious systems wrap it in the boundaries we describe in how pricing guardrails work.
The real answer: layers, not tribes
Look at how a well-run pricing operation actually behaves and you'll see all three at once: cost-plus as the floor (margin enforcement on every price), value-based as the positioning logic (where you choose to sit on differentiated and own-label lines), and optimization as the engine (evidence-driven prices within those boundaries, catalog-wide). That layered architecture - strategy on top, measurement in the middle, floors underneath - is exactly what rules-based pricing encodes.
See the three layers working together on a real retail dataset in the interactive demo - no signup required.