A minimum order value is useful only when it protects a real cost or margin threshold. A £100 minimum may sound precise, but it is only meaningful if it is based on your own cost-to-serve, margin and route economics.
The right starting point is not what competitors charge or what a system can validate. It is the cost of fulfilling and delivering the order, how much of that cost changes when the order changes, and what contribution you need the order to make. That is why minimum order value belongs next to cost per drop, not in a settings screen on its own.
This article gives you a method and a printable worksheet. The numbers are illustrative. Replace every one with your own.
Minimum order value starts with cost-to-serve, not average basket size
Separate fixed and variable costs before you build the threshold. A vehicle lease or salaried warehouse manager may be part of the operation's fixed cost base; extra pick time, payment handling, packaging or a route deviation may change more directly with the order. The accounting distinction between fixed and variable costs is useful here, but distribution adds a practical complication: some route-day costs are fixed for the day and variable when you change the fleet or route pattern.
Cost-to-serve
Which costs change with this order/drop?
Margin contribution
What does the relevant basket contribute?
Threshold
Set the rule from the economics
Exceptions
Define who can approve and why
Review
Check what the rule actually changed
Do not force every cost into “this one order caused it”. Instead build the version of cost-to-serve that matches the decision. If you are deciding whether a small incremental order on an existing dense route is acceptable, the relevant cost can be different from deciding whether an entire low-density route is commercially viable.
Use a worked threshold, then stress-test it
Stress-test the result. What happens if margin drops because the basket shifts to lower-margin lines? What if the customer sits on a route you are already driving past? What if the order requires a special vehicle, long dwell time or manual cash collection? A single MOV can still be the right commercial choice, but understand what you are simplifying.
Decide what the policy is trying to change
Minimum order value can serve different objectives. It can discourage uneconomic small drops, steer customers toward a fuller weekly order, reduce office handling, or protect delivery capacity. If you cannot name the behaviour you want to change, you will not know whether the threshold worked.
That is why the follow-up measures matter. Track the share of orders below the threshold before and after the policy, average order value, exception frequency, lost orders, route density and customer complaints. The existing guide to route density helps separate “small order” from “expensive stop”; the two are related but not identical.
Choose one rule or a controlled set of rules
One universal minimum
Simple to explain and train. Best when service conditions are similar enough that the simplification is acceptable.
Segmented minimums
Can reflect route, service or commercial differences, but needs clear ownership so exceptions do not become hidden negotiated prices.
Whichever you choose, define the exception path. Who can approve an order below the minimum? What reason should be recorded? Is the exception temporary, customer-specific or one-off? The aim is not to prevent judgement. It is to make judgement reviewable.
Be careful with credit too. A customer can meet the minimum order value and still be over a credit limit. Keep the commercial checks distinct. The existing credit-control guide explains why the order threshold and the account exposure need separate controls.
Minimum order value decision worksheet: on-page version
Use one row per customer segment or service model. The PDF carries the same fields for a working session.
| Input | Your figure / rule | What to verify |
|---|---|---|
| Incremental handling + delivery cost | Which costs actually change with one more order? | |
| Gross margin % on relevant mix | Use the margin of the served basket, not a company-wide average by habit | |
| Required contribution above cost | What must the order contribute? | |
| Indicative MOV | (cost + required contribution) ÷ margin % | |
| Exception owner | Who can approve and why? | |
| Review measures | Orders below MOV, AOV, route density, lost orders, exceptions |
Apply the rule consistently across order channels
RouteMagic can apply minimum-order checks in the order workflow, including the approval of Customer Portal orders. The software can enforce the threshold you set; it does not calculate the commercial minimum for you.
Orders from different channels can join the same order-management workflow, where pricing, credit and minimum-order checks can be applied consistently. This matters because a commercial rule that only exists on the website but not on a phone order is not really one rule.
Use the reporting layer to review what happened after the change. If exceptions are concentrated on one route or customer segment, revisit the economics rather than assuming the staff are “not enforcing the policy”.
Conclusion
A minimum order value should be the output of a commercial decision, not a number copied from the market. Start with the cost-to-serve that matters for the decision, use the margin of the relevant basket, add the contribution you need, and make the assumptions visible. Then stress-test the result against route density, customer mix and service requirements before deciding whether one rule or several controlled rules are appropriate. Keep credit control separate, define who can approve exceptions, and measure whether the policy changes the behaviour you intended without creating avoidable lost business. RouteMagic can enforce minimum-order checks consistently across the order workflow, but the threshold itself still belongs to management. Your practical next step is to complete the worksheet for one customer segment using real figures. If you cannot explain every input, the minimum is not ready to publish.
