Delivery Cost-to-Serve Analysis: Profitability by Route, Parcel, and Customer

By Corin Hale on October 17, 2026

delivery-cost-to-serve-analysis-profitability

Average cost per delivery is a comfortable number and a misleading one. It hides the long rural route, the high-return customer, the oversized parcel, and the window that forces a half-empty van onto the road. Cost-to-serve analysis breaks the average apart so you can see which routes, parcels, and customers earn a margin and which quietly lose it. This guide explains how to build a delivery cost-to-serve model, segment profitability, and act on the result, including how maintenance management software supplies the vehicle cost data the model needs.

Delivery Cost-to-Serve Analysis: Profitability by Route, Parcel, and Customer

Find the routes, customers, and orders that lose money, and decide what to change with a cost model built on real activity data.

Illustrative cost waterfall for one delivered order
Order revenue
Product and picking cost
Linehaul and sorting
Last-mile route cost
Failed attempts and returns
Customer service and claims
Remaining margin
Shape is for explanation only. Your own data sets the real proportions.

Average Cost Versus True Cost to Serve

Cost to serve measures the full cost of delivering to a specific customer, route, or order. It assigns cost to the activities each one actually causes, not to an even share of the total.

Average costing says
Every delivery costs about the same, so price and service levels can be uniform.
versus
Cost to serve says
Cost varies by distance, density, window, parcel, failure rate, and customer behavior, so margins vary too.

The gap between the two is where cross-subsidy lives. Profitable customers silently pay for unprofitable ones until someone measures it.

The Three Levels of Analysis

Route level
Cost per stop and per kilometer by zone, day, and vehicle. Reveals geography and density problems.
Parcel level
Cost by size, weight, handling needs, and service option. Reveals pricing gaps for bulky or special parcels.
Customer level
Cost across all orders, returns, contacts, and special requests. Reveals which accounts need new terms.

Start at the route level, where data is easiest to obtain, then add parcel and customer detail as the model matures.

Why Some Deliveries Lose Money

Cost driverWhat causes itTypical symptom
Low delivery densityRemote or scattered addressesHigh cost per stop and long drive time
Narrow time windowsCustomer-specified slots that fragment routesPart-loaded vans and idle time
Failed first attemptsAccess issues, absent recipients, poor address dataRepeat visits and extra contacts
High returnsFit, quality, or expectation gapsReverse logistics cost exceeds forward cost
Bulky or heavy parcelsTwo-person handling, special vehiclesSlow stops and higher damage risk
Heavy customer contactMany status requests or changesSupport cost per order is high
Special handling termsSignature, scheduled calls, building rulesLonger service time per stop
Vehicle downtimeBreakdowns and unplanned repairsRescue runs and overtime

Add Reliable Vehicle Cost Data to Your Model

Vehicle repairs, downtime, and service history belong in your cost to serve. Track them per asset with Oxmaint.

Building a Delivery Cost-to-Serve Model

1
Define the cost object
Choose what you are costing: stop, parcel, route, or customer. Start with one.
2
List the activities
Pick, pack, sort, load, drive, deliver, retry, return, handle claims, answer contacts.
3
Assign cost to each activity
Labor, vehicle, fuel, insurance, maintenance, software, and facility cost.
4
Choose cost drivers
Use time, distance, stops, parcels, or contacts to allocate each activity cost.
5
Attribute cost to the object
Multiply each driver quantity by its rate for every route, parcel, or customer.
6
Compare with revenue
Calculate margin and rank the cost objects from best to worst.

Allocation Methods Compared

MethodHow it worksStrengthLimit
Simple averageTotal cost divided by total deliveriesEasy and fastHides all variation
Zone-based averageAverage cost within each delivery zoneCaptures geographyMisses customer and parcel differences
Time-basedCost allocated by minutes spent on each stopReflects service effortNeeds reliable stop timestamps
Activity-based costingEach activity costed by its own driverMost detailed and actionableNeeds more data and upkeep

Most operations get good results by starting with zone and time-based allocation, then refining only where the numbers suggest large differences.

Data Sources You Will Need

Order and billing systems
Revenue, discounts, service level, and customer identifiers.
Route and delivery data
Stops, distance, time, failed attempts, and proof of delivery.
Warehouse systems
Pick, pack, and handling effort per order.
Finance
Wages, vehicle costs, insurance, overhead, and carrier invoices.
Customer service
Contacts, claims, and refunds linked to orders.
Maintenance system
Repair cost, service cost, and downtime by vehicle.

Segmenting Customers by Profitability

Plot customers by order volume and margin after cost to serve. Each quadrant suggests a different response.

Low volume, high margin
Protect and grow. These customers may be small but are profitable to serve.
High volume, high margin
Core accounts. Prioritize service quality and capacity.
Low volume, low margin
Review terms, minimums, or channel. Often the largest source of hidden loss.
High volume, low margin
Renegotiate carefully. Volume can mask poor economics.

Turning Analysis Into Action

FindingPossible responseTrade-off
Remote zone loses moneySurcharge, scheduled delivery days, or pickup pointsMay reduce volume in that zone
Customer with high failed attemptsImprove address data, add notifications, change delivery methodNeeds customer cooperation
High-return accountReview return policy or add return feesCan affect customer relationship
Narrow windows fragment routesPrice premium windows or offer flexible discountsCustomers may resist change
Bulky parcels underpricedAdd size-based pricingRequires contract updates
Vehicle downtime inflating route costImprove preventive maintenance and replace problem assetsNeeds maintenance investment
Network inefficiencyRedesign zones, depots, or carrier allocationLonger-term project

Treat each response as a test. Change one variable, measure again, and keep what improves margin without damaging service.

Maintenance Cost Is Part of Cost to Serve

Vehicle upkeep is often spread across the fleet as a single overhead line. That hides which routes and which vehicles drive repair spend.

Maintenance as a flat overhead
  • Repair cost split evenly across routes
  • Old vans look the same as new ones
  • Downtime cost is invisible
  • No link between route type and wear
Maintenance recorded per asset
  • Repair and service cost tied to each vehicle
  • Costly vehicles identified for replacement
  • Downtime hours available for route cost
  • Rough routes matched with higher wear

Oxmaint is maintenance management software, so it supplies this vehicle cost layer to your model. It does not calculate customer profitability.

  • Asset records with repair and service history for every vehicle.
  • Work orders capturing labor, parts, and downtime for each repair.
  • Preventive maintenance schedules that reduce unplanned breakdowns.
  • Inspection records that show recurring faults before they cause route disruption.
  • Reports on maintenance cost per vehicle that finance can allocate to routes.

KPIs for a Cost-to-Serve Program

KPIPurpose
Cost to serve per stop, by zoneShows geographic profitability
Margin per customer after delivery costIdentifies accounts to renegotiate
Failed-attempt cost per orderQuantifies waste from access and data problems
Return cost as a share of revenueFlags high-return segments
Share of customers with negative marginMeasures size of the cross-subsidy
Maintenance cost per route kilometerLinks asset cost to route cost

Common Pitfalls

Over-engineering the first model
A simple zone-based model that people use beats a perfect model that is never finished.
Ignoring revenue quality
Discounts, rebates, and fees change the margin. Use net revenue, not list price.
Acting without context
A negative-margin customer may bring strategic value. Review before ending a relationship.
Letting the model go stale
Rates, volumes, and routes change, so refresh the model at least quarterly.

Cost-to-Serve Questions

What is delivery cost to serve?
It is the full cost of delivering to a given customer, route, or order, based on the activities each one causes rather than an even share of total cost.
How is cost to serve different from average cost per delivery?
Average cost hides variation. Cost to serve shows which deliveries earn margin and which do not.
What data do I need first?
Route and stop data, revenue by customer, and cost by activity. Add maintenance and service data as the model grows.
Can maintenance data improve the model?
Yes. Repair and downtime cost per vehicle make route cost more accurate. Start with Oxmaint to record it.
Does Oxmaint calculate customer profitability?
No. It manages maintenance data that feeds the model. Book a demo to see the reporting.

A Small Worked Example

The numbers below are hypothetical and only show the mechanics. Two customers place the same number of orders each month, yet their economics differ.

Item (per month)Customer A: urban, one drop pointCustomer B: remote, many attempts
Orders100100
Net revenue1,5001,500
Product and handling cost900900
Route cost per order2.006.50
Failed attempts and redeliveries0.20 per order1.40 per order
Support contacts cost per order0.100.60
Margin after delivery costPositive, about 3.70 per orderNegative, about 6.50 per order lost

Both look identical on an average-cost report. Only an activity-based view separates them, and only then can pricing or terms be addressed for Customer B.

Cost to Serve by Delivery Channel

Channel choice changes cost to serve more than almost any other lever. Compare channels on the same basis.

ChannelCost strengthsCost risks
Home deliveryConvenient, flexible for customersHigh stop cost, failed attempts, narrow windows
Parcel locker or pickup pointConsolidates stops, reduces failuresLocker upkeep, customer collection behavior
Scheduled neighborhood dayRaises densityLess flexibility for customers
Carrier or partner networkReduces fixed costLess control, harder to see cost drivers
Store or hub collectionUses existing locationsHandling cost at the site

Shifting a share of orders to lower-cost channels can improve margin, as long as customers still accept the option.

Allocating Shared Costs Fairly

Some costs cannot be traced to one route or customer. A clear rule prevents arguments later.

  • Depot rent and utilities: allocate by volume handled or floor space used.
  • Dispatch and planning labor: allocate by number of routes or stops planned.
  • Technology and software: allocate by active users or transactions.
  • Fleet overhead and insurance: allocate by vehicle days or distance, then by route.
  • Management overhead: keep it separate from route cost unless leadership wants a fully loaded figure.

Write the rules down and review them annually. Consistency matters more than perfection when comparing periods.

Who Owns the Model

Finance
Owns cost rates, revenue data, and allocation rules.
Operations
Owns route, stop, and service-time data, and acts on route findings.
Sales and account teams
Use customer results in pricing and contract talks.
Maintenance and fleet
Provide vehicle cost, downtime, and asset replacement data.

A named owner and a monthly review meeting keep the model from becoming a one-time project.

Presenting Results to Leadership

  1. Show the average cost per delivery first, so everyone starts from the familiar number.
  2. Reveal the spread: best and worst zones, customers, and parcel types.
  3. Quantify the cross-subsidy as the margin earned by profitable segments that is lost by unprofitable ones.
  4. Propose three actions, each with an owner, an expected effect, and a way to measure it.
  5. Agree a review date and the data that will show whether the change worked.

Leaders respond to specific, testable proposals more than to a long list of findings.

Data Quality Checklist Before You Trust the Numbers

  1. Every stop has a timestamp for arrival and completion, not only for route start and end.
  2. Failed attempts are coded with a reason, such as no access, absent recipient, or wrong address.
  3. Returns are linked to the original order and customer.
  4. Carrier invoices are matched to delivered parcels, including surcharges and adjustments.
  5. Vehicle costs are recorded against the correct asset and month.
  6. Customer identifiers are consistent across order, delivery, and support systems.

Fix the weakest data source first. One poor input, such as missing stop times, can distort every route comparison.

Quick Wins in the First 30 Days

Rank zones by cost per stop
Identify the worst five zones and check whether density, windows, or distance is the cause.
List top failed-attempt addresses
Repeat offenders are often fixed with better address data or a different drop point.
Review the lowest-margin accounts
Prepare terms for the next contract conversation, using the data you have.
Find the costliest vehicles
Check whether repair cost and downtime justify replacement or a revised service plan.

Trends Changing Delivery Cost Analysis

  • More granular data: route and stop events are now available in near real time, which allows daily cost views.
  • Customer pressure on delivery fees: shoppers compare shipping charges, which makes accurate cost knowledge valuable in pricing.
  • Returns growth: reverse logistics is becoming a major cost driver in many parcel segments.
  • Channel diversification: lockers, pickup points, and carrier partners all need separate cost lines.
  • Fleet electrification: charging, battery, and maintenance costs change vehicle cost per kilometer and must be added to the model.
  • Sustainability reporting: distance and emissions per delivery are increasingly reported, and the same route data can serve both cost and carbon analysis.
  • Service differentiation: operators use cost-to-serve results to design paid premium options, such as narrow windows, instead of absorbing their cost.

Give Your Cost Model Real Vehicle Data

Cost to serve is only as accurate as its inputs. Use Oxmaint to track repairs, downtime, and preventive maintenance for every vehicle behind your routes.


Share This Story, Choose Your Platform!