The bestselling product may not be paying for its place on the line
For Finance controllers, CFOs and accounts teams · Understand the problem
TL;DR — what you’ll learn
- Define the revenue and cost boundary before comparing product margins.
- Connect actual recipe, packaging and output records to the cost of the product made.
- Separate product contribution from order-specific service costs and shared overhead allocations.
- Use the analysis to compare practical decisions such as run size, packaging and delivery frequency.
A popular sauce sells in a small pack that requires frequent line changes and separate deliveries. Its sales report looks healthy. Its contribution looks different once the business includes packaging, promotion credits and the work needed to serve those orders. The point of food costing is to expose those choices, not merely produce another percentage.
How do you find which food products make a worthwhile contribution?
Compare net revenue with the costs attributable to the product on a stated basis, then show shared-cost assumptions separately. Sales volume, gross margin and contribution after delivery answer different questions; keep them distinct before deciding what to change.
- 01Define the margin viewPeriod, SKU and cost scope
- 02Assemble revenue and costReturns, rebates and allocations
- 03Reconcile assumptionsUnits, shared costs and cut-offIs the allocation basis accepted?YesReview the product accountNoSeparate unresolved costs rather than presenting a precise unsupported margin.
- 04Review the product accountShow contribution and limitations
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Write the boundary above the number
An illustrative product earns ₹120 per pack after agreed commercial deductions. Ingredients cost ₹48, packaging ₹14 and directly attributable conversion costs ₹18. On that defined basis, ₹40 remains before delivery and shared costs. If a particular order adds ₹12 per pack in delivery expense, its contribution is different from an order collected by the customer.
These figures are a teaching example, not a recommended margin or accounting treatment. Use the organisation's approved costing policy for financial reporting. For an operating decision, make the included and excluded costs explicit so two teams do not debate different definitions of profit.
Cost the product that was actually made
Connect the recipe version, actual consumption, accepted output and packaging issued to the relevant run. A standard recipe can be useful for planning, but it will not explain an actual yield difference by itself. Microsoft documents production cost analysis using reported material and operation transactions; the accuracy of those reports depends on the production record beneath them.
Source: Microsoft Learn · Reported consumption and production-order cost analysis. Reference details
Separate a product problem from an order pattern
Return to the illustrative ₹40 contribution before delivery and shared costs. A customer collecting 500 packs leaves ₹20,000 on that stated basis. An order for fifty packs with ₹600 directly attributable delivery cost leaves ₹1,400 after that delivery: 50 × ₹40 − ₹600. The product recipe is identical, but the service pattern changes the decision.
The response could be a delivery minimum, consolidated drops or a different commercial arrangement. Calling the entire SKU unprofitable would overlook the collected order. Build the report at the level the decision requires, then roll it up. A product-level average can conceal both a useful product and an expensive way of serving one customer.
Allocated cost is not automatically avoidable cost
A finance report may allocate building, management or equipment costs across products. That can serve a reporting purpose, but removing one product may not remove those costs. For a discontinuation decision, identify what would actually stop, what capacity would become available and whether the business has a credible alternative use for it.
The reverse also matters. A product may appear attractive on material margin while consuming a constrained line through frequent changeovers. Evaluate the contribution and capacity implications together. Keep the financial-reporting view and the decision-specific view reconciled but labelled, so the team does not use an overhead allocation as a direct estimate of cash savings.
Make uncertainty part of the calculation
If promotion credits arrive after sales, show whether the current margin includes an approved estimate or only settled amounts. If freight cannot yet be linked to individual orders, show the allocation basis. Missing data should be marked as missing or estimated; entering zero creates a precise-looking answer with an undisclosed gap.
A useful sensitivity view changes one assumption at a time. For example, compare two run sizes while keeping the recipe and selling terms fixed, or compare two delivery patterns while retaining the same production cost. This lets the manager see which assumption drives the conclusion. An AI summary can describe the change, but the underlying numbers and source records should remain accessible.
Which decision would the analysis change?
The answer might be a larger minimum run, a different delivery frequency, a packaging review or a customer-specific price discussion. Discontinuing the product is only one possibility. Consider whether it uses otherwise idle capacity or supports a commercially important range before treating allocated overhead as an avoidable saving.
Build the first report for a manageable product family and reconcile it to finance totals. Keep missing costs visible rather than replacing them with zero. AI can help classify inconsistent invoice descriptions, but a transparent cost bridge is more useful than an unexplained profitability score.
Summary
SKU profitability becomes useful when the cost bridge is visible and the proposed decision is specific. A product can look different by customer, pack or order pattern. Keep assumptions and avoidable costs explicit so a margin report leads to a sensible operating choice rather than an automatic product deletion.
What to do next
- Choose a small product family and reconcile net revenue and attributable costs to finance records.
- Compare one high-volume order with one costly small delivery using the same cost definition.
- Evaluate a concrete change and identify which costs would actually change with it.
Recognise this problem in your operation?
Tell us where the records or handovers break down. We can discuss the process, data and software questions worth examining first.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Production order cost analysisMicrosoft Learn · Dynamics 365 Supply Chain Management documentation, accessed October 2026
Product documentation distinguishing reported production costs and variance categories. Examples in these articles are original teaching scenarios.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
