Advantages and disadvantages of cost-plus pricing

Cost plus pricing survives because it answers a question every retailer has to answer daily: what should this cost? Take your cost, add a markup, move on. Thousands of SKUs priced before lunch.

Whether that is a strength or a weakness depends entirely on which SKUs.

The advantages

It scales without thinking. A new supplier sends 400 SKUs, half with no competitive data. Cost-plus prices all of them in an afternoon. Nothing else does that.

It guarantees a positive margin. If your cost input is right, you cannot accidentally sell at a loss. That sounds trivial until you have watched a competitor-matching rule chase someone below cost.

It is explainable. Every price traces to a documented formula. When finance asks why an item is priced that way, the answer is one line, not a model. In regulated or tendered contexts this matters more than optimality.

It is stable. Prices only move when costs move. Customers are not seeing a different number every visit, and your team is not firefighting.

It handles cost shocks cleanly. When freight or FX moves, cost-plus tells you exactly how much price has to move to hold margin. Market-driven methods leave you guessing.

The disadvantages

It ignores willingness to pay - in both directions. This is the big one, and it is usually framed as "you might price too high." The more common and more expensive error is pricing too low. On long-tail items nobody price-checks, a flat markup leaves real money uncollected, quietly, forever.

It ignores competitors entirely. Your cost has no relationship to what the shop across the street charges. Apply one markup across a catalog and you will be visibly expensive on the handful of known-value items shoppers actually remember - which then colours their perception of everything else you sell.

It rewards inefficiency. Higher cost produces higher price. There is no mechanism pushing you to source better, and a supplier increase gets passed through automatically rather than questioned.

It depends on a cost figure most teams get wrong. Invoice cost is not landed cost. Freight, duty, payment processing, returns, storage, and shrink all belong in the base. A 40% markup on the wrong base can be a single-digit margin on the right one - the landed cost math is where most of the damage happens.

It is circular on volume. Unit costs depend on volume, volume depends on price, price depends on unit cost. In practice you are guessing.

It cannot handle strategy. Cost-plus has no way to express "lose margin here to win the category." That is a market-position decision, which is why penetration pricing sits outside the formula rather than inside it.

The verdict

Cost-plus is not obsolete. It is a floor-setting tool that got promoted to a pricing strategy by default, and the fix is demotion rather than removal.

Use it as the boundary: cost-plus sets the lowest defensible price, and competitive position, elasticity, and product role decide how far above it you sit. Retailgrid handles this as layered rules - the margin floor is inviolable, and optimization works in the space above it.

Two things make that practical. Split markup by product role, so traffic drivers and long-tail items stop sharing a number. And keep live competitor data on the SKUs shoppers actually check, so you know when the floor and the market have diverged.

Keep cost-plus for what it is good at. Stop asking it to do the other job.