Spark Inventory

Ideas for inventory operators

Margin vs Markup: Price Products Without Guesswork

Practical guidance on demand planning, purchasing, multichannel operations, and building a healthier inventory business.

A product can sell quickly and still weaken the business. That usually happens when the team uses margin vs markup interchangeably, then makes pricing or purchasing decisions from the wrong number. The difference is not accounting trivia. It affects whether a reorder creates healthy cash contribution, how much working capital sits in stock, and how much room you have for discounts, freight changes, and supplier price increases.

For an operations leader at a growing product business, the practical answer is simple: use markup to build a selling price from cost, and use margin to judge the share of sales dollars left after product cost. Then make sure the cost in both calculations reflects the real landed cost of getting a SKU ready to sell.

Margin vs markup: the essential difference

Markup is calculated from cost. It answers: how much did we add to what this item cost us?

Markup = (Selling price - Cost) / Cost

Margin is calculated from revenue. It answers: what percentage of the sale remains after the cost of goods sold?

Margin = (Selling price - Cost) / Selling price

The dollar profit is identical in both calculations. The percentage is not.

Say a SKU has a landed cost of $60 and sells for $90. The gross profit is $30. Its markup is $30 divided by $60, or 50%. Its gross margin is $30 divided by $90, or 33.3%.

That difference becomes expensive when a team says it needs a 50% margin but prices at 50% markup. The resulting $90 selling price delivers only 33.3% margin, not 50%. At volume, that gap can quietly consume the dollars meant to cover fulfillment, marketplace fees, payroll, and operating overhead.

Start with the cost that purchasing actually owns

Neither formula is useful if cost is incomplete. A supplier unit price is often only the first part of landed cost. Depending on the product and supply chain, a usable cost may also include inbound freight, duties, packaging, inspection, brokerage, and other direct costs required to make inventory available for sale.

Use a consistent policy. If inbound freight is material and varies by shipment, leaving it out of SKU cost will overstate margin and make reorder recommendations look safer than they are. If you include it, make sure the source data is updated consistently rather than relying on a one-time spreadsheet adjustment.

There is a tradeoff here. A highly detailed landed-cost model can be more accurate, but only if the team can maintain it. For many operators, a stable standard landed cost that is reviewed after each supplier or freight change is better than a perfect model that no one trusts.

Also separate gross margin from contribution margin. Gross margin usually subtracts product cost. Contribution margin may also subtract channel-specific costs such as marketplace commissions, payment fees, pick-and-pack charges, and shipping subsidies. A product can meet its gross-margin target while producing a much thinner contribution in one channel than another.

That matters when the same SKU sells through direct-to-consumer, Amazon, wholesale, and retail. One catalog price may be simple, but the economics are not always the same.

Convert the target before setting the price

Pricing conversations often begin with a target stated in the wrong language. The cleanest fix is to convert the target before anyone updates a price list.

If you know the desired margin, calculate the required selling price this way:

Selling price = Cost / (1 - Desired margin)

For a $60 cost and a 50% margin target, the required price is $60 / (1 - 0.50), or $120. That price represents 100% markup, not 50% markup.

If you know the desired markup, calculate the selling price this way:

Selling price = Cost x (1 + Desired markup)

At $60 cost and 50% markup, the selling price is $90. Again, that produces a 33.3% margin.

The conversion becomes more important as targets rise. A 20% markup equals a 16.7% margin. A 50% markup equals a 33.3% margin. A 100% markup equals a 50% margin. Operators who remember only one relationship should remember that margin rises more slowly than markup because margin uses the larger sales-price denominator.

Price with inventory decisions in view

Margin is not just a merchandising metric. It should influence the way you fund and replenish inventory.

First, look at margin dollars, not only margin percentage. A 60% margin SKU that sells a few units per quarter may not deserve the same attention as a 35% margin SKU with fast, predictable weekly demand. The first may tie up cash; the second may reliably fund operations. A per-SKU forecast helps distinguish a genuinely productive SKU from one that merely looks attractive on a product page.

Second, match inventory exposure to demand confidence. Long supplier lead times, high minimum order quantities, and volatile demand increase the cost of being wrong. A high-margin SKU can still be a poor reorder if it would create 300 days of supply. Conversely, a lower-margin core item may warrant protection when stockout risk is high and demand is consistent across channels.

Third, account for incoming inventory before treating an item as understocked. A reorder point built from on-hand stock alone creates duplicate purchasing. The real question is whether on-hand inventory plus incoming inventory will cover forecast demand through the supplier lead time, with the safety stock your policy requires.

Fourth, review discounts as a margin decision, not just a revenue decision. A 20% discount has a very different effect on a SKU with 70% margin than on one with 35% margin. If sales teams can discount without seeing the post-discount contribution, purchasing may be asked to replenish demand that looks healthy in units but creates limited cash to fund the next order.

A practical monthly workflow for operators

You do not need to reprice every SKU every week. You do need a disciplined review when product cost, demand, or supply conditions change.

Begin with a cost exception report. Flag SKUs with supplier price changes, changed freight assumptions, new duties, or a meaningful currency movement if you buy internationally. Recalculate the current gross margin at the actual selling price, then compare it with the approved target.

Next, segment the exception list by operational consequence. Prioritize high-volume SKUs, products with upcoming purchase orders, items with low days of supply, and products that are already at stock risk. A small margin error on a slow item may wait. A small error on a fast mover can affect every reorder decision this month.

Then check the forecast and supply position before changing a price. If demand is accelerating, a price increase may reduce unit demand or shift demand between channels. If a replenishment is late, a promotion could worsen a stockout. Demand ESP forecasts every SKU from sales across channels and accounts for seasonality, giving operators a better basis for connecting price changes to likely inventory needs.

Finally, document the decision. Record the old cost, revised cost, current price, target margin, effective date, and owner. This is not bureaucracy. It allows purchasing, finance, and commercial teams to work from the same assumptions when they review a buying plan, open orders, or a questionable promotion.

Where spreadsheets break down

A spreadsheet can calculate margin and markup correctly. The failure usually comes from disconnected inputs. One tab has supplier costs, another has channel sales, another has incoming purchase orders, and a fourth holds reorder points that were set before demand shifted.

That fragmented process makes it hard to see the operating consequence of a pricing decision. The team might identify a margin shortfall but miss that the SKU has six months of incoming inventory. Or it might raise a price without recognizing a seasonal demand pattern that changes the next purchase quantity.

Modern inventory systems should connect these decisions without taking control away from the operator. Spark brings together sales history, on-hand and incoming inventory, supplier lead times, warehouse context, and inventory policies to identify stock risk and prepare reorder recommendations. Its buying plan turns those inputs into specific purchasing work rather than another report to interpret.

Spark MCP is particularly useful for teams that already work through Claude, ChatGPT, or another MCP client. It lets an operator connect through OAuth, map and validate data with an AI assistant, and approve what is imported. That is a more current operating model than legacy inventory software that requires long implementation cycles before anyone can ask a useful question.

Keep the approval point with the operator

AI can prepare the analysis, but it should not hide the tradeoffs. A good system explains why a SKU is at stock risk, what demand assumption it used, what incoming inventory it counted, and how supplier lead time affects the reorder date. The operator can then adjust for a planned price change, an upcoming promotion, or supplier intelligence that is not yet in the data.

Text with Sparki makes that review practical away from a desk. Sparki can text a low-stock or stock-risk alert, answer a question about what needs reordering, and prepare a draft purchase order when the operator replies YES. The draft still goes through operator review, adjustment, and approval before anything is sent or committed.

Margin tells you whether the sale supports the business. Markup helps you construct the price. Spark connects both to the inventory decisions that follow: Demand ESP plans each SKU, reorder recommendations account for supply and demand, and Text with Sparki keeps the operator able to review and approve the next draft purchase order from a phone.

All Spark Inventory Blog articles