Product Profitability Analysis: Which SKUs Create Profit and Which Ones Quietly Consume It

What product profitability analysis is (and is not)

Product profitability analysis answers one operating question: after the costs that move with this product, and after the friction this product creates, what does the business keep?

It is not:

• a substitute for customer profitability (the same SKU can be healthy with one account and toxic with another);
• a department budget review — that belongs under profitability by department;
• a KPI dashboard method — tracking visibility sits on KPI tracking;
• a full retelling of company P&L → COGS root-cause already covered on locked financial-control pages.

Its job is narrower: SKU / product-line economics as a decision surface.

Why “best seller” rankings mislead

High volume often gets protected automatically. That is dangerous when volume is bought with discounts, rework, rush freight, or awkward setups that never appear in a simple sales report.

A useful product view separates at least three layers:

1. Revenue and mix — what you sell and how much.
2. Contribution — what remains after costs that vary with the product (see contribution margin explained).
3. Friction load — rework, returns, expediting, special handling, and schedule disruption that the product repeatedly triggers (often surfaced in margin leakage analysis).

A SKU can look strong on layer 1, acceptable on layer 2, and still look much weaker once recurring operating friction is considered.

A practical sequence: SKU economics → decision

Use this order so analysis stays decision-oriented rather than report-oriented.

1. Define the product unit you will judge

Choose a stable unit: SKU, family, or configurable base. If the unit keeps changing every month, rankings become politics. For configured products, judge the repeatable core separately from one-off options.

2. Build contribution by product first

For each unit, estimate contribution after variable product costs. Do not jump straight to fully absorbed “net profit per SKU” if overhead allocation is still unstable — that creates false precision. Contribution is the first honest filter. Detail and formulas live on the contribution-margin page; this page only uses that signal as an input.

3. Attach leakage and friction to the same SKU

Where possible, tag discounts, rework, rush logistics, and returns back to the product (or product family). If you cannot tag perfectly, start with the top volume SKUs and the SKUs that dominate complaints or expedites. The goal is not perfect accounting on day one — it is to stop treating friction as “someone else’s cost.”

4. Check capacity and constraint load

Two products with similar contribution are not equal if one consumes scarce machine time, scarce skilled labor, or scarce warehouse slots. When a constraint is binding, contribution per constrained hour (or per scarce resource) matters more than contribution per unit. Link the capacity conversation to operations pages when needed; do not replace shop-floor control analysis here.

5. Rank into action buckets

A simple working set of buckets:

• Protect — strong contribution, low friction, acceptable constraint use.
• Reprice / reshape — demand exists, economics fail after discount or service load.
• Redesign / process — product is strategically needed but creates avoidable rework or handling cost.
• Stop or contain — weak contribution plus high friction, or high constraint consumption with poor return.

Every bucket needs an owner and a next date. Analysis without a decision is just another report.

Planned vs actual — the minimum control loop

Product profitability becomes useful when planned assumptions meet actual outcomes on the same SKU:

• planned price / discount corridor vs actual invoice;
• planned variable cost vs actual consumption and scrap/rework;
• planned lead-time / service promise vs expedites and overtime.

Review frequency should match how quickly product mix, costs, pricing, and operating conditions change. The cadence should follow the company’s own control cycle rather than a borrowed KPI template.

Decisions this analysis should trigger

• Commercial: which SKUs may be discounted, and which require approval tied to contribution.
• Portfolio: which low-economics products stay only for strategic coverage, with explicit containment.
• Operations: which products need process fixes before more volume is pushed.
• Inventory: which slow, low-contribution items are inventory traps rather than “strategic stock” (connect to working-capital and inventory control pages when stock is the binding issue).

Common mistakes

• Ranking only by revenue or units sold.
• Allocating all overhead until every SKU looks “precise” — then arguing about allocation instead of decisions.
• Ignoring customer mix: a “good product” sold only through toxic accounts is still a business problem (open customer profitability).
• Treating this page as a replacement for leakage or contribution pages instead of using them as linked steps.
• Inventing industry benchmark margins and forcing SKUs to match them.

Where to go next

Use this page as the SKU decision surface. Then deepen:

• Contribution margin explained — product contribution math and constraint logic.
• Margin leakage analysis — where planned product margin disappears between functions.
• Customer profitability analysis — when the account, not the SKU, is the main destroyer.
• Profitability by department — when cost centers absorb product economics.
• Operational profitability analysis framework — the step order across product, customer, department, and leakage views.
• Gross margin vs operating margin — when product-looking profit still fails at company level.