Calculate logistics cost to serve by the work each customer creates
For finance controller, hr / workforce manager, depot head · Compare approaches
TL;DR — what you’ll learn
- Customers with similar revenue can create different storage, handling, transport and exception work.
- Choose a measurable cost driver for each activity and retain the underlying records.
- Show unused capacity and unallocated costs instead of forcing every rupee onto a customer.
- Use cost to serve to investigate service design and pricing, with the commercial decision still explicit.
Topics: logistics cost to serve · customer logistics profitability · activity based logistics costing · cost per delivery customer

Illustrative 3PL warehouse dispatch and freight verification desk; not a client facility.
All quantities, amounts, product codes and events are illustrative teaching examples.
Two customers each generate ₹50,000 of monthly logistics service revenue. One orders predictable consolidated deliveries. The other sends smaller requests throughout the week and needs repeated clarification of invoices. A revenue-based cost allocation makes the accounts look identical even when the operation experiences them very differently.
Calculate logistics cost to serve from the activities each customer creates, within a defined period and cost boundary. Separate directly traceable costs from allocations, then reconcile the result to the included expense pool. The purpose is to explain the difference before changing a service promise or price.
Build a small activity ledger
The following illustrative month covers two customers in a shared operation. Revenue and costs exclude taxes. The activity rates are approved assumptions for this example, not market charges. Labour and resources appear in only one cost pool, so the rates do not duplicate a separately charged expense.
Scroll horizontally to see all columns.
| Activity and assumed cost driver | Customer A | Customer B |
|---|---|---|
| Storage: ₹20 per pallet-day | 100 × ₹20 = ₹2,000 | 100 × ₹20 = ₹2,000 |
| Handling: ₹10 per completed order line | 500 × ₹10 = ₹5,000 | 200 × ₹10 = ₹2,000 |
| Delivery: ₹600 per comparable dispatch | 10 × ₹600 = ₹6,000 | 25 × ₹600 = ₹15,000 |
| Exception work: ₹500 per recorded hour | 2 × ₹500 = ₹1,000 | 12 × ₹500 = ₹6,000 |
| Assigned service cost | ₹14,000 | ₹25,000 |
| Service revenue | ₹50,000 | ₹50,000 |
| Revenue less assigned service cost | ₹36,000 | ₹25,000 |
Customer B creates fewer handling lines but more dispatches and exception hours. Its assigned cost is ₹11,000 higher. That difference is visible without assuming its products are harder to handle or that its contract is unprofitable.
The included expense pool is ₹45,000. Customer allocations explain ₹39,000, leaving ₹6,000 of unused or unallocated capacity. Across both accounts, ₹100,000 revenue less ₹45,000 included expense gives ₹55,000. The customer contributions sum to ₹61,000 before the separate ₹6,000 capacity amount.
Keep that bridge visible. Dividing the residual equally may be an approved reporting choice, but it should not be disguised as work caused by each customer.
Select drivers that reflect the work
A useful driver changes when resource consumption changes. Pallet-days may suit a defined storage activity, while order lines, cartons, touches or handling minutes may suit different warehouse tasks. A dispatch count suits the example only because the dispatches have comparable cost.
If Customer B's destinations are substantially farther away, a flat dispatch rate becomes weak. Trace actual carrier charges where available or use a documented lane or distance model. If fragile items require more handling, separate the relevant task rather than counting every line as equivalent.
Document the driver, source, exclusions and owner for each pool. For storage, specify how opening balances and same-day movements affect the daily count. For exception time, define what starts and stops the activity and distinguish active work from waiting for a customer reply.
Avoid measuring everything merely because the system can emit an event. Start with the activities that plausibly explain a material cost difference and can be captured consistently.
Distinguish a billing rate from an operating cost
A tariff can charge ₹30 per pallet-day while the selected cost model allocates ₹20. The first is a commercial price; the second is an analytical allocation. Copying the tariff into the cost column would turn the analysis into a restatement of revenue.
CartonCloud describes activity-based billing capabilities for storage, handling and related services. Those billing records can help identify activities, but they do not establish the resources consumed or the cost of providing them. CartonCloud — Billing and invoicing
Likewise, a customer may receive an included number of urgent dispatches under its contract. Their operating cost still exists even if no additional invoice is raised. Show the service entitlement beside the activity pattern when discussing a change.
Invoice disputes also need classification. Hours spent correcting the provider's own inaccurate bill should remain visible as failure work. Calling all those hours “customer complexity” would shift responsibility without evidence.
Reconcile costs at the same grain
Use a common customer identity, service period and unit of measure across the WMS, TMS, labour records and finance ledger. A shared invoice may cover several clients, sites or months. Allocate its lines using an approved basis and preserve the original amount.
Oracle's invoice match-rule documentation illustrates configured relationships between invoices and transport records. A matched invoice can supply a traceable input; the cost-to-serve model still needs a justified allocation when a charge covers several customers. Oracle Transportation Management 26C — Match Rule
Reconcile assigned cost plus the explicitly unallocated remainder to the included expense pool. Explain any exclusions, such as corporate overhead, financing costs or a capital project. A report limited to operating service costs should not be labelled final customer profit.
For labour, check that task rates and directly assigned overtime do not charge the same hours twice. For vehicle costs, decide whether the delivery rate already includes fuel, driver time and depreciation before adding those items separately.
Test whether the result supports a decision
Investigate Customer B's 25 dispatches and 12 exception hours. Perhaps agreed order cutoffs could consolidate work, better invoice references could reduce clarification, or the service price needs commercial review. The table does not choose among those actions automatically.
Compare an actual service pattern with a clearly stated alternative. Reducing dispatch count from 25 to 20 would reduce assigned delivery cost by ₹3,000 at the illustrative rate. It does not establish ₹3,000 of cash savings: the resources may remain committed, and customer service could deteriorate.
A controlled worksheet can support the first review. A costing module or data pipeline helps when activity volumes and allocation rules become difficult to maintain manually. In either case, another reviewer should be able to reproduce a customer's total from source activities and the approved rate version.
Measure unexplained residuals, missing activity records and time needed to reproduce a total. More detailed charts are not useful if the cost pool no longer reconciles.
Discuss the work behind the margin
A focused cost-to-serve assessment starts with one customer pair, one month and the activity that appears to explain the difference. That makes the commercial discussion specific: change the work, change the service agreement, improve the provider's process or accept the cost knowingly.
Next actions
- Define the service period and included expense pool, separating operating contribution from final profit.
- Choose drivers for storage, handling, transport and material exception work, with one owner for each definition.
- Reconcile customer allocations and the unallocated remainder to finance records.
- Test one service-design alternative and distinguish an allocation change from an achievable cash saving.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Draft an assessment emailReferences
Sources checked 15 October 2026. Vendor documentation supports platform facts; the worked examples and diagrams are original.
- CartonCloud — Billing and invoicingAccessed 15 October 2026.
- Oracle Transportation Management 26C — Match RuleAccessed 15 October 2026.