Customer Cost to Serve: Beyond Product Margin

Two customers buying the same products at the same prices can create different demands on fulfillment and support. Customer cost-to-serve analysis traces those activities to each account so product gross margin is not mistaken for the account's complete contribution. The purpose is to understand the service model and possible changes, not to declare that an allocated cost automatically disappears when a customer leaves.

Worked decision model

Suppose customers A and B each generate $20,000 revenue and $12,000 product cost during the year. Both show $8,000 gross profit and a 40% gross margin on sales. Customer A places ten orders, while B places 40. Preparing each order requires $15 of attributable handling. A therefore uses $150 of order handling and B $600. Identical revenue has not produced identical work.

Support time differs as well. A requires eight hours and B 40 hours, assigned at a defined internal cost of $30 per hour. Support assignments are $240 and $1,200. A also incurs $100 of account-specific return handling, while B incurs $500. After these specified service costs, A retains $7,510 and B $5,700. Their contribution shares of revenue are 37.55% and 28.5%, respectively, under this management boundary.

The $1,810 difference is an activity-based comparison, not necessarily an immediate cash saving available by ending B's relationship. If the support team remains on payroll and released time has no other use, some assigned cost continues. Conversely, if the time prevents service to other profitable accounts, its opportunity cost may matter. Keep direct outlays, assigned staff time, and continuing shared overhead in separate columns when evaluating an actual account decision.

A service redesign can be more useful than simply raising the price. Suppose B agrees to 20 consolidated orders and a support process requiring 25 hours, with return handling unchanged. Assigned order cost falls to $300 and support to $750, leaving $6,450 after the same $12,000 product cost and $500 returns handling. The modeled improvement is $750. Verify that consolidation is feasible and does not create higher freight, inventory, or service failures elsewhere.

Use observable activity records and consistent rates. Avoid assigning all difficult-to-explain overhead to the customer with the most complaints or the smallest revenue. Revenue credits, special packaging, rush requests, and collection work may need separate traces, but do not count the same expense in product cost and service cost. Review agreed service levels and actual customer needs before changing terms. A cost-to-serve report supports a specific conversation about order patterns, service scope, and capacity; it does not measure a customer's overall strategic value or guarantee a financial improvement.

Apply and verify the decision

1. Trace repeatable activities

   Use recorded orders, support hours, special shipments, and return events with a consistent cost definition for each driver.

2. Distinguish assignment from avoidability

   Show which costs are direct payments, which consume internal capacity, and which remain unchanged under the proposed account decision.

3. Test a concrete service change

   Model a feasible order or support redesign, check its effect on other costs, and compare actual results before treating the estimate as a saving.

Method reference: OpenStax: Relevant Information for Decision-Making. Accessed October 22, 2026. The reference supports the accounting concept; all scenario prices, rates, probabilities, and worked calculations are independently constructed hypothetical examples.