Your ERP knows the selling price of every SKU, the raw material cost, and the direct labor hours charged to each production order. Yet when the management controller needs to identify which product lines are genuinely profitable — and which ones are silently dragging down your EBITDA — the answer still comes out of a manually built spreadsheet, two weeks after month-end close.
That lag is not inevitable. It is the symptom of missing or incomplete analytical configuration in the ERP. This guide explains how to close that gap in five steps, which modules to use in the leading ERP platforms, and which mistakes to avoid so that your controller can rely on the numbers the system produces.
1. Why gross margin management by product line is non-negotiable in 2026
Inflation makes true profitability invisible
Between 2022 and 2026, raw material, energy, logistics and labor costs moved sharply — and not symmetrically across product families. A company that tracks margin only at the aggregate level can report a stable overall gross margin while masking serious deterioration in specific segments.
Illustrative example: a mid-market industrial company with £40 M in revenue and 800 active SKUs may have 30 % of its product lines at zero or negative gross margin, offset by 15 % of highly profitable references. Without per-SKU visibility, sales discounts keep flowing to the least profitable lines, and the company sells more while losing more.
The danger of averages and product family groupings
Rolling up SKUs into product families to compute an average margin is common practice — and it creates a dangerous blind spot. Within a single family, the gap between the best and worst gross margin can exceed 40 percentage points. A “family with 28 % margin” can hide individual references at 55 % and others at −8 %.
The ERP closes this gap, provided its analytical structure is configured to drill down to the product or SKU cost object level.
What ERP enables that spreadsheets cannot
A spreadsheet recalculates margin from periodic exports. The ERP calculates it continuously, using the same journal entries that feed the general ledger: every sales invoice, every goods receipt, every production posting. The margin figure is always current — no manual compilation required.
A second advantage is variant management: the same product offered in 12 colours or 6 sizes can carry very different cost-of-goods-sold figures per variant. The ERP tracks that granularity. The spreadsheet collapses it.
The 80/20 rule applied to product margin
In most companies that run this analysis, 20 % of SKUs generate between 70 % and 90 % of total gross margin. The ratio is not universal, but it is common enough that per-SKU analysis typically pays for itself within one quarter of implementation. Identifying those strategic references lets you concentrate commercial effort, prioritise procurement during supply constraints, and build an objective case for delisting decisions.
2. Prerequisites: configuring your ERP for margin management
Cost structure in the ERP
Gross margin is defined as net revenue (invoiced revenue less trade discounts and credit notes) minus direct costs — raw materials, direct labor, and directly attributable subcontracting for the goods sold.
For the ERP to calculate that margin at SKU level, every sales transaction and every resource consumption must be tagged to a cost object — in practice, an analytical code representing the product or product family.
The analytical plan: cost centres, profit centres, and cost objects
The most common configuration mistake is conflating three distinct analytical levels:
- Cost centres: organisational units that consume resources (production workshop, warehouse, sales team). Costs are allocated here; revenues are not.
- Profit centres: units that carry both revenues and costs. May correspond to product ranges, regions, or sales channels.
- Product cost objects: the most granular level, corresponding to a SKU, a project, or a production batch. This is where gross margin per product is calculated.
Effective configuration automatically links every sales invoice line to the corresponding cost object, and every direct cost allocation (materials, direct labor) to the same object.
Bills of Materials and routings: impact on cost of goods sold
In a manufacturing context, the cost of goods sold for a product depends on its Bill of Materials (BOM) and its production routing. If the BOM is incomplete or out of date, the ERP computes an incorrect COGS and the displayed margin is fictitious.
Before launching a margin management project, audit your BOMs: missing components, unrecorded scrap factors, recurring subcontracting costs not yet captured. This is a non-negotiable prerequisite.
Inventory valuation: FIFO, WAC, or standard cost?
The choice of valuation method directly affects the reported margin:
- Standard cost: the cost is set at the start of the year; variances against actuals are recorded separately. Easy to manage, but the displayed margin can diverge materially from reality during periods of significant input price movement.
- Weighted Average Cost (WAC): the cost is recalculated on every stock receipt. Better reflects price fluctuations, but complicates variance analysis.
- FIFO: earliest receipts flow out first. Appropriate for perishable goods or fast-moving inventory.
In 2026, after several years of volatile commodity pricing, many companies on standard cost are reporting margins that no longer reflect their actual economics. Review your valuation method with your external auditor before configuring margin management.
3. Five steps to manage gross margin by product line
Step 1: Define your analytical dimensions
Start by answering three questions: at what level of granularity do you want to manage (family, sub-family, individual SKU)? Along which cross-cutting dimensions (sales channel, region, customer, segment)? And at what reporting frequency (weekly, monthly, rolling)?
The temptation is to analyse everything at once. In practice, start with two dimensions maximum — the product SKU and the sales channel. Add further dimensions once the first layer is stable and trusted.
Step 2: Configure automatic analytical allocations
The goal is that every ERP entry — sales invoice, delivery note, production order, workshop posting — automatically generates analytical allocations to the relevant cost object, with no manual intervention.
In practice, this means building a mapping table between product references and their analytical cost objects, then configuring that table in your ERP’s allocation rules. Once in place, the controller enters nothing: data accumulates in real time.
Step 3: Capture the hidden costs that are routinely missed
Four cost categories are consistently under-allocated in first-time deployments:
- Trade discounts and credit notes: if they remain in the general ledger without analytical allocation, net revenue per product is overstated — and so is the margin.
- Returns and after-sales credits: a 3 % return rate on a reference can halve its gross margin.
- Per-order freight costs: allocating logistics as a global overhead charge spreads the cost across all references indiscriminately. For a bulky or fragile product, freight can represent 8–12 % of cost of goods sold.
- Compliance and certification costs: for industrial equipment, testing and regulatory documentation costs often sit in general overhead accounts, even though they are directly attributable to specific product families.
Step 4: Build standard-versus-actual margin reports
A useful margin report for a management controller shows at least three columns per SKU: standard margin (budget), actual margin (reported), and the variance in absolute value and percentage. Variance analysis then decomposes the cause: is the gap driven by volume (fewer units sold than planned), price (lower selling price than budget), or mix (the composition of sales has shifted)?
Most industrial ERP platforms deliver this report as standard once the analytical plan is configured. In more generalist platforms, you will need the embedded BI module or a connected reporting tool.
Step 5: Set up margin threshold alerts
Define a minimum gross margin threshold per SKU or product family, agreed with the CFO and sales leadership. Configure an automatic alert in the ERP or connected BI tool: whenever a reference falls below that threshold over the last 30 or 60 days, the controller and the sales manager receive a notification.
This step transforms margin management from a retrospective monthly exercise into an early-warning system. Slippage is addressed within days, not at quarter-end.
4. ERP-by-ERP configuration and reporting examples
SAP S/4HANA: Margin Analysis (formerly CO-PA)
SAP offers two product profitability analysis modes within its Controlling module:
- Account-Based CO-PA: margin is derived from general ledger accounts. Data is consistent with financial accounting and compliant with IFRS. The recommended approach for international groups.
- Costing-Based CO-PA: margin is derived from internal cost values not necessarily aligned with posted accounts. More flexible for internal analysis, but requires reconciliation with external reporting.
In S/4HANA, Margin Analysis merges both approaches into a unified view. Initial configuration (defining analysis characteristics, assigning value fields) typically takes 4–8 weeks depending on the complexity of the product structure.
Microsoft Dynamics 365 Finance & Supply Chain Management
D365 F&SCM delivers product profitability analysis through financial dimensions and native SSAS/Power BI reporting cubes. Configuring financial dimensions (the D365 equivalent of SAP analytical axes) enables margin breakdowns by product, channel, region, or customer segment.
The key advantage of D365 is native Power BI integration: margin reports are accessible directly within the interface, without exports. The limitation is that granularity rarely reaches the product variant level without additional development work.
Odoo 17/18: Costing and BI modules
Odoo’s integrated Product Costing module supports FIFO, WAC, or standard cost tracking by product category. Per-product margin reporting is available within the Sales module via filters, but remains limited compared to industrial ERP platforms.
For advanced margin management on Odoo, most integrators connect an external BI tool (Metabase, Tableau, Power BI) that queries the PostgreSQL database directly. Flexibility is real, but fine-grained analytical configuration — freight cost allocation, returns integration — requires custom development.
Sage X3: Multi-axis analytics as standard
Sage X3 includes a multi-criteria analytical engine that supports up to nine analysis axes, with each transaction allocated across multiple axes simultaneously. The integrated Budget & Reporting module compares actual against budget by product, site, division, and channel.
Key strength: variance management is native and requires no custom development. Key limitation: the built-in BI remains less ergonomic than specialist tools, and larger organisations typically connect a dedicated EPM platform for multi-entity consolidation.
5. Three mistakes that distort margin analysis in your ERP
Mistake 1: Freight costs allocated as global overhead
Allocating all freight and logistics costs to a general overhead account — without any per-product or per-order breakdown — effectively subsidises high-volume references with the margin generated by lightweight ones. The fix is straightforward: create an analytical “freight” code per order or per order line, and link it to the relevant product reference.
Mistake 2: Ignoring year-end volume rebates and credit notes
Year-end rebates are discounts granted to customers based on volume thresholds. If they are provisioned in the general ledger without analytical allocation by product, the net revenue shown in your margin report is systematically overstated eleven months out of twelve. Build the rebate provision into the analytical allocation at invoicing time, pro-rated by volume per SKU.
Mistake 3: Valuing work-in-progress at a frozen standard cost
Standard cost is calculated at the start of the financial year on the basis of forecast input prices. When commodity prices move 15–25 % mid-year — a scenario that has been routine since 2022 — WIP valued at standard cost generates large price variances that stay in variance accounts, never allocated to products. The result: the per-product margin reflects January economics, not the current month. Revise your standard cost mid-year if purchase prices have moved more than 10 % since the last update.
6. From analysis to decision: acting on underperforming products
How to present results to the executive committee
A gross margin dashboard by product is only useful if it drives decisions. The recommended structure for an executive committee presentation: a four-quadrant matrix (sales volume × gross margin rate) that visually surfaces “cash cows” (high volume, high margin), “rising stars” (low volume, high margin), “volume products” (high volume, acceptable but low margin), and “laggards” (low volume, low or negative margin).
Decisions never concern the first two quadrants. They concern the last two.
Three options for a reference below the threshold
For a product whose gross margin is structurally below the agreed threshold, three options exist — in order of preference:
- Reprice: the least disruptive option where the market allows. Per-product margin analysis gives the sales team a quantified argument in customer negotiations.
- Reduce costs: renegotiate with the supplier, substitute a component, adjust the production routing to cut direct labor hours, or bring subcontracted operations in-house.
- Delist: remove the SKU if its margin is structurally negative and the first two options have been exhausted. The ERP can simulate the revenue and margin impact of delisting before any decision is taken.
The make-or-buy decision informed by ERP data
The cost of goods sold calculated by the ERP enables a direct comparison between internal manufacturing cost and an external subcontractor quote. If the internal cost correctly absorbs overhead charges through the allocation keys configured in the analytical plan, the make-or-buy analysis rests on reliable data rather than estimates. This is one of the most concrete use cases for per-product margin management in an industrial SME.
To build the analytical foundation required for this kind of management, read our complete guide on management control and analytical accounting in the ERP and our ERP vs EPM comparison for CFOs.
Download our ERP evaluation grid — 30 criteria across 100 points to compare the analytical capabilities of three vendors side by side against your specific business requirements.
