Cost plus pricing vs. markup pricing: key differences

Ask ten retail teams to explain the difference between cost plus pricing and markup pricing and you will get four answers, two shrugs, and one person who insists they are the same thing.

That last person is closest to right, which is the confusing part. The two overlap heavily - but they sit at different levels, and the real damage comes from a related confusion underneath them: markup versus margin. That one has a body count. If you want the full method first, our guide to cost plus pricing in retail covers it end to end.

The honest distinction

Cost plus pricing is a method. It is a philosophy of how you decide prices: start from what the product costs you, add a predetermined amount, and that is the price. It is inward-looking by design - it deliberately ignores competitors and demand.

Markup pricing is the calculation inside it. Markup is the mechanic: the percentage you add on top of cost. It is the arithmetic, not the strategy.

So markup is how cost plus pricing gets executed. Where people draw a harder line between them, it usually comes down to this: cost plus often implies a fixed amount or rate applied across a category or catalog, frequently in contracts and B2B ("cost plus 15%"); markup pricing more often implies varying rates by product, category, or role - different markups on different items based on judgment. In practice, retailers use the terms interchangeably. Do not lose an afternoon to it.

The distinction that actually costs money

Markup and margin are not the same number, and mixing them up is the single most expensive arithmetic error in retail. Markup is calculated on cost; margin is calculated on price.

Example. Landed cost €10, sell at €15. Markup = (15 − 10) / 10 = 50%. Margin = (15 − 10) / 15 = 33.3%. Same transaction. Two very different numbers.

Now run it backwards. If your finance team sets a 50% margin target and someone applies a 50% markup, you price at €15 instead of €20. You have missed the target by a third - on every unit, in every category, all year. And because the error is copied forward from last season's file, it compounds silently.

Quick conversions worth memorizing: a 25% markup is a 20% margin; 33% markup is a 25% margin; 50% markup is a 33% margin; 100% markup is a 50% margin; 150% markup is a 60% margin. Keystone pricing - the retail classic - is a 100% markup, which is a 50% margin.

The shared weakness

Both approaches inherit the same blind spot: they only know what you paid. They know nothing about what a shopper will pay or what the competitor down the street is charging.

Apply one rate across a catalog and you get two failures simultaneously. On known-value items that shoppers price-check, you are visibly expensive. On long-tail items nobody compares, you leave margin uncollected.

The fix is not abandoning the method - it is differentiating the rate by product role, then treating the cost-based number as a floor rather than the answer. Traffic drivers, margin generators, and long-tail SKUs should never share a markup.

Getting the cost input right

Both methods are only as good as the cost you feed them. Invoice cost is not landed cost. Add freight, duty, payment processing, returns, storage, and shrink, and a 40% markup on invoice can be a 6% margin in reality - discovered at year-end rather than at the decision. Fix the cost base first. Precision applied to a wrong number is still wrong.

Which should you use?

Use cost-based pricing as your floor everywhere, and let market signals set the ceiling on the SKUs that matter. Where competitive data is thin - private label, deep long tail, B2B contracts - the cost-based number can stand alone. Where shoppers actively compare, it should be the minimum you accept, not the price you charge.

That is what dynamic pricing does in practice: hold the cost-based floor as an inviolable rule, then optimize above it against live competitive position.