How to set a minimum order value before small orders quietly drain your margin

A beverage distributor running nine vans out of a single depot had a route that looked fine on paper. Forty-one stops a day, decent case volume, a driver who knew every bodega owner by name. Nobody flagged it as a problem route. It just never made the money the sales numbers said it should.

The owner finally sat down with a spreadsheet one slow Friday and pulled a week of invoices against what each stop actually cost to serve — driver time, fuel, the ten minutes of unloading and paperwork at every door. About a third of the stops on that route were $15–$25 orders: two cases of soda, a few energy drinks, maybe a rack of chips. Each one took almost the same time to deliver as a $300 stop three doors down. The fuel was the same. The driver's hourly cost was the same. On paper the small orders carried a normal gross margin. After the cost of actually delivering them, most were break-even or worse.

The problem compounds quietly

No single small order looks like a crisis. That's what makes it easy to miss. A $20 order with 30% gross margin brings in $6 of gross profit. If it costs $9 in driver time and fuel to make that stop — not unusual on a dense urban route, worse on a rural one — the business loses money by serving the customer at all. Multiply that by a dozen stops a day, five days a week, across a fleet, and it stops being a rounding error. It becomes the gap between a route that pencils out and one that quietly subsidizes itself out of every other route's margin.

The trap is that these orders don't announce themselves. They show up scattered across good customers who also place large orders sometimes, so the account looks healthy in aggregate. The loss hides inside an invoice that looks fine on the summary line.

The turning point

What changed the distributor's thinking wasn't a single bad month — it was comparing two stops side by side on the same route, same day, same driver. One was a $280 order to a grocery store. The other was an $18 top-up order to a corner store two blocks away, placed because the owner had run out of one SKU between regular visits. The delivery cost was nearly identical. The profit wasn't.

That comparison is the whole argument for a minimum order value (MOV): not punishing small customers, but making sure every stop a van makes can actually cover the cost of making it.

How the fix works in practice

Setting an MOV well takes more than picking a round number. A few things matter:

Calculate cost-to-serve per stop first, not last. Total route cost — driver wages, fuel, vehicle cost, a share of overhead — divided by stops on that route gives a rough per-stop cost. It varies a lot by route density: a tight urban loop might cost a fraction of a sparse rural one. Set the MOV off that number, by route or zone, not off a single company-wide guess.

Set the threshold above cost-to-serve, not at it. An MOV that exactly covers delivery cost still leaves no margin for the product itself. The threshold needs to clear delivery cost plus a real gross margin on top, or it's not solving the problem — it's just making the break-even point official.

Don't apply it uniformly. A key account that occasionally places a small top-up order is not the problem; a long tail of marginal accounts that always order small is. Many distributors apply the MOV by account tier or by route, with exceptions for strategic customers, rather than as a blanket rule that risks alienating a good relationship over one slow week.

Give the customer an option, not just a rejection. The better rollout isn't "we won't deliver that" — it's "add two more items and we'll deliver today" or "we'll combine it with your regular visit in three days." A lot of below-threshold orders convert to above-threshold ones with a simple nudge at order time, because the customer didn't realize they were close.

Watch what the policy actually changes. The goal isn't fewer orders — it's fewer orders that lose money. After rolling out an MOV, track whether average order value on the affected route moved, and whether total case volume held. If customers just stopped ordering instead of ordering more, the threshold or the messaging needs adjusting.

For the beverage distributor, the fix wasn't dramatic. They set a route-specific minimum, let the driver's handheld flag an order below it before it was confirmed, and gave reps a one-tap way to suggest an add-on item at the point of order. Within a few weeks the small-order stops either grew past the threshold or consolidated into the next scheduled visit. The route's stop count dropped a little. Its margin didn't.

Practical takeaway

• Calculate actual cost-to-serve per stop (driver time + fuel + vehicle cost) before setting any number — don't guess.
• Set the minimum order value above cost-to-serve plus a real margin, not at the break-even line.
• Apply it by route or customer tier, with explicit exceptions for key accounts, rather than one flat rule for everyone.
• Surface the threshold at order time with a way to add items, not just a rejection after the fact.
• Review average order value and total volume a month after rollout to confirm the policy changed behavior rather than just lost orders.

iotoms calculates route and stop-level cost-to-serve automatically from actual delivery data, and can flag a below-threshold order on the rep's handheld before it's confirmed — so the minimum order value gets enforced at the moment it matters, not discovered three weeks later in a margin report.