Key takeaways
- Rank customers by contribution after cost to serve, not by revenue.
- Allocate costs using activity drivers such as orders, deliveries, and support hours.
- Keep avoidable costs separate from allocated fixed overhead.
- Use tiers to set service, terms, and minimum order rules.
On this page
Why revenue ranking misleads
The largest customer is not necessarily the most profitable. Large accounts often bring smaller orders, more delivery points, more returns, custom packaging, and longer payment terms. Revenue ranking counts the benefit and ignores the cost of serving it.
Small orders are the usual culprit. An account that places ten orders a month for small quantities can consume more picking, packing, and delivery time than an account twice its size that orders once a week. Revenue per order hides that difference.
Customer profitability reporting puts a profit and loss account behind each account. The aim is not precision to two decimal places. It is a reliable ranking that shows which accounts fund the business and which consume it.
Build a customer profit and loss
Start with net revenue after discounts, rebates, and returns. Deduct cost of goods sold to get gross margin. Then deduct the costs incurred to serve that customer: order processing, picking, delivery, installation, support, returns handling, payment fees, and account management.
Show contribution after those costs before allocating fixed overhead. Contribution is the number a sales team can influence; fully loaded profit is the number the board sees. Publishing both, clearly labelled, avoids arguments about allocations.
Use the same revenue definition as the management accounts, and keep cost of goods sold on the same standard or actual basis. If the customer profit and loss uses a different margin from the product report, the two will disagree and trust in both will fall.
| Cost pool | Driver |
|---|---|
| Order processing | Orders or order lines |
| Delivery | Drops, weight, or distance |
| Customer support | Tickets or hours |
| Returns handling | Returned units |
| Payment terms | Days beyond standard terms |
| Account management | Agreed service hours |
Choose drivers, not revenue
Allocating cost to serve by revenue assumes a large customer costs proportionally more to serve, which is rarely true. Use activity drivers: number of orders, deliveries, support tickets, return units, or hours booked.
Keep the number of drivers small. Four or five cost pools are enough for most small and mid-sized businesses. More precision than the underlying data supports creates confidence without accuracy.
A simple test of a driver is whether the cost would disappear if the activity stopped. If cancelling a weekly delivery removes the cost, the delivery count is a valid driver. If the cost remains, it belongs in fixed overhead.
Read the shape of the book
Plot margin percentage against revenue and mark the quadrants. High revenue with healthy margin is the core. High revenue with thin margin needs a service or price review. Low revenue with high margin is a growth candidate. Low revenue with negative margin needs a decision.
Also look at cumulative profit. Test whether a small group of accounts carries the total, and check what happens to the business if one of them leaves.
The quadrant view is a conversation starter, not a verdict. An account in the low margin quadrant may still be worth keeping for cash flow, capacity fill, or access to a market.
- Contribution below zero after avoidable costs for two consecutive quarters.
- Margin below the segment floor while order frequency is rising.
- Cost to serve above a set share of gross margin.
- Payment behaviour outside terms combined with thin margin.
Turn tiers into rules
Use the analysis to set service tiers rather than to shame customers. A tier can define order minimums, delivery frequency, support response, payment terms, and whether customisation is chargeable.
Set thresholds in advance and apply them for a full quarter before changing anything. A customer that looks unprofitable in one busy month may look different over a year, especially if the cost allocation is new.
For example, a tier might require a minimum order value, charge for deliveries below it, and reserve named account management for accounts above a contribution threshold. The rules should be published, not applied quietly to one customer.
Avoid the common traps
Do not allocate all overhead by revenue and call the result customer profitability. Do not ignore growth potential or strategic value. Do not use last year's cost rates. And do not publish a ranking without a plan for the accounts at the bottom.
Review the model annually, refresh the cost rates, and check a sample of accounts against the ledger. A customer profit and loss is a decision tool, not an audited statement.
Finally, check the direction of causation. A customer may look expensive because the relationship is new and still ramping, or because a temporary service issue generated support calls. One year of data is a better basis than one quarter.
Frequently asked questions
What is the difference between gross margin and customer contribution?+
Gross margin deducts only cost of goods sold. Customer contribution also deducts the costs of serving that account, such as delivery, support, returns, and payment terms.
Should all overhead be allocated to customers?+
No. Allocate avoidable cost to serve, then show fixed overhead separately. Fully loaded figures invite arguments about allocation bases that the customer cannot influence.
How many customers should be in the analysis?+
Cover the accounts that make up most of revenue and margin, then group the rest into a single tail. Analysing every small account individually costs more than the insight is worth.
How can the result be used without damaging relationships?+
Use tiers and published rules rather than ad hoc penalties. Explain changes in terms, offer alternatives such as consolidated deliveries, and give notice before applying them.
Need help applying this?
Get help with Dashboards & BI.
Review the service scope or tell us what you are trying to improve. We will reply with a clear next step.
Free KPI definition templateRelated reading
Data mining for small business: practical use cases
Practical data mining use cases for small businesses, from customer segmentation and basket analysis to churn signals and anomaly checks.
Building a 13-week cash flow forecast
A 13-week cash flow forecast shows whether the business can meet its commitments week by week. Build it from invoices, payment terms, and dated commitments.