What Your Cost-to-Serve Numbers Aren’t Telling You

Most distributors know their revenue per account. Few know their true cost to serve it and that gap is where margin quietly disappears.

The problem: revenue without cost is half a picture

Every distributor tracks what an account brings in. Far fewer track what it takes to keep that account running– the driver time, the merchandiser visits, the sales calls, the delivery assistant hours, all stacked against the actual delivery frequency the account needs.

Without that number, “servicing the customer well” and “servicing the customer profitably” get treated as the same thing. They aren’t. An account can be perfectly served and still lose money every week, and nothing in a standard sales report will flag it.

This isn’t a niche accounting problem. It’s a structural blind spot in how most distribution networks measure performance and it grows with every acquisition, every added route, and every account whose service frequency hasn’t been revisited in years.

What “cost to serve” actually means

Cost to serve is the total field time an account consumes, broken out by role: how many hours the delivery driver spends there, how many hours the merchandiser spends there, how much attention the sales rep puts in, how often a delivery assistant is involved. Add it up against what that account pays, and you get a real answer to three questions: How many hours are we spending on this customer? How much are we earning from it? Are we servicing it the right way?

Run that math and the results are often uncomfortable. A distributor might find it’s spending twelve hours a week servicing an account that generates a small delivery fee in return– a clear, quantified case of losing money on a customer every single week, hidden inside a relationship everyone assumed was fine.

There’s a second layer to this: reported time versus actual time. Distributors increasingly want to compare what field staff report working against what actually happened in the field– is someone logging ten hours when the real number is closer to seven? That’s not about distrust. It’s about knowing whether your cost-to-serve numbers are built on real data or on estimates.

How Wise Systems connects the dots

Cost to serve isn’t solved by a report– it’s solved by connecting the systems that generate the data in the first place. Wise Systems links strategic planning, daily routing, and on-road execution into one workflow, so the same data that plans a route also measures what happened on that route.

That workflow follows a simple cycle: analyze the current data, plan changes to delivery frequency or structure, implement those changes, measure what actually happens on the road, and control the operation based on results. Each step feeds the next. Strategic Planner answers “am I servicing this customer the right number of times?”– maybe an account visited twice a week only needs weekly or biweekly service. Once that plan goes live, on-road monitoring shows whether the new structure is holding, and the data flows back into the next planning cycle.

The same connected system also gives every field role visibility into each other. Merchandisers can see where a delivery actually is instead of calling the driver to ask. A manager can confirm a driver-and-assistant task is finished before routing the next person in. Everyone works off the same picture instead of a chain of texts and phone calls.

When this matters most

Renegotiating service frequency. An account visited more often than its revenue supports is a candidate for a lighter, still-reliable schedule.

Validating labor before it becomes a dispute. Comparing logged hours to reported hours turns a guessing game into a documented answer.

Coordinating multi-role accounts. Any account touched by a driver, merchandiser, and sales rep benefits from all three seeing the same real-time status.

Handling the unplanned. A stop gets added mid-route, a driver’s vehicle breaks down, an assistant needs to be sent to help– the plan should flex without losing visibility into what’s happening.

The bigger picture

Scale changes the stakes. One distributor moving every field employee– drivers, merchandisers, sales reps, delivery assistants– onto a single connected platform is on track to have well over a thousand people running through one system. At that size, a blind spot in cost to serve isn’t a rounding error. It compounds across thousands of stops a week.

The value isn’t just in optimizing a route once. It’s in the loop: plan, execute, measure, adjust, and plan again– continuously, with real field data instead of assumptions.

Want to see what your cost-to-serve numbers actually look like? Let’s talk.