Why your ERP doesn't show real profitability.
Your ERP reports revenue per customer and the cost of the goods they bought, then it stops at the gross-margin line. Everything that makes one customer cheaper to serve than another, the picking, the small urgent orders, the special requests, the returns, the support calls, sits in overhead and gets spread evenly across everyone. That is why a healthy-looking P&L can quietly hide relationships that lose money on every order.
Accurate, as far as it goes
- Revenue per customer, product and order
- Cost of goods sold
- Gross margin by line
- Volumes, prices, discounts
The cost of serving
- Picking and packing time per order
- The true cost of small and urgent orders
- Returns, rework and credits
- Support, account management, special requests
The overhead-allocation trap
An ERP has to put overhead somewhere, so it uses a simple rule: spread it as a percentage of sales, or per unit, or per order line. That rule is easy to run and almost always wrong. It assumes a large planned order and a tiny urgent one consume the operation in proportion to their revenue. They do not. The small order ties up the same picking, checking and dispatch attention, sometimes more, for a fraction of the value. Average that cost across everyone and you do two things at once: you over-charge the efficient customers and you subsidise the expensive ones, all while the report looks perfectly reasonable.
EVERY CUSTOMER, BY SIZE AND TRUE MARGIN
Illustrative. Once cost to serve is attributed, the picture the ERP cannot draw appears: profitable accounts above the line, and a cluster of smaller ones that fall below it into loss.
The ERP is not wrong. It is just answering a different question: what did we sell, not what did it cost us to serve.
A cost-to-serve model does not replace the ERP and does not require a system change. It sits on top, takes the revenue and goods cost the ERP already records, adds the activity and time data the ERP never held, and attributes the operational cost to the customers and products that actually caused it. The result is the same P&L, opened up far enough to manage.
Common questions
- Why doesn't my ERP show customer profitability?
- An ERP is built to record transactions, not to attribute the cost of serving. It reports revenue and cost of goods per customer accurately, then stops. The operational cost that differs from customer to customer, picking, small orders, special requests, returns, support, sits in overhead and is spread by a blunt rule such as a percentage of sales. So two customers with the same gross margin look identical even when one costs three times as much to serve.
- Does a cost-to-serve model replace my ERP?
- No. It sits on top of it. The ERP stays the system of record for transactions and goods cost. A cost-to-serve model takes those facts, adds the activity and time data the ERP does not hold, and attributes operational cost to the customers and products that caused it. The two are complementary, not competing.
- Which ERP systems does this work with?
- All of them. We work from the exports your system already produces, SAP, Microsoft Dynamics, Sage, Oracle NetSuite, Infor or a bespoke system. The model does not connect to or depend on a particular ERP, which is why it can be built quickly and updated from monthly extracts.
- Isn't gross margin enough to manage profitability?
- Gross margin tells you the product is sold above its goods cost. It says nothing about how expensive that customer is to serve. A customer with a healthy gross margin can still lose money once frequent small orders, returns and support are counted. Managing on gross margin alone systematically protects your most expensive relationships.
What is your ERP hiding?
The Profit Check points to where real profitability is hidden in your business, in five minutes, with no data upload.
Take the Profit Check