Leak 13 · Freight & Cost-to-Serve - Low-value orders below economic minimum

A minimum exists on paper. A third of orders are below it. Each one is handled, delivered, and invoiced at a loss.

Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.

What is it?

This is the operational side of small-order pricing. Even with a policy, low-value orders keep flowing because CSRs do not want to refuse a customer, because the system does not enforce the minimum, and because nobody sees the count. The fix is mostly enforcement and customer conversation, and the count is the evidence for both.

Family
Freight & Cost-to-Serve
Primary owner
CFO
Secondary owners
Customer Service Manager, Sales Managers
Primary impact
EBITDA
Typical data source
ERP order headers
Detection difficulty
30-day measurability

Ask yourself

Do you have a minimum order value, and what share of orders fall below it?

Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.

What does it look like?

Warning signs. None of these proves the leak exists. They tell you where to look.

  • A minimum order value that is not enforced in the order-entry system.
  • A stable share of orders under the minimum, month after month.
  • The same customers repeatedly under the minimum.

What data do I need?

The minimum viable set. Most of it is already in your ERP.

Field
Order header: customer, order value, line count, date
Minimum order policy and any fee
Fees actually charged

The initial check

Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.

  1. 1Export last quarter’s orders and count the share below your minimum, or below $75 if you have none.
  2. 2Group the sub-minimum orders by customer and rank.
  3. 3Count how many of those orders carried a small-order fee.
Sub-minimum share = orders below minimum ÷ total orders; fee compliance = orders with fee ÷ orders below minimum

Then ask one question: Would the top five sub-minimum customers consolidate if someone asked them?

How much could it be costing us?

A conservative range, not a headline. The goal is a number management can trust enough to investigate.

Sub-minimum orders per year × (cost to serve − average gross profit on those orders) × share that can be consolidated or charged

Common root causes

Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.

Process
The policy exists but nobody enforces it or tracks exceptions.
Data
Sub-minimum orders are not counted or reported.
Technology
Order entry does not warn on or apply the minimum automatically.

What should we do?

Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.

  1. Level 1

    Visibility

    A monthly sub-minimum order report by customer and CSR.

  2. Level 2

    Enforcement

    Apply the fee automatically in order entry, with an approval step to waive it.

  3. Level 3

    Customer conversation

    Offer the top offenders a consolidation schedule, stocking program, or online ordering with a minimum built in.

Where AI helps

  • Suggesting consolidation opportunities from a customer’s order pattern and drafting the outreach.

Where AI probably doesn’t

This is a policy and configuration problem. A report and an ERP setting solve most of it.

Before you call it a leak

  • Sub-minimum orders from a large account may be the price of the large account. Segment before acting.

Think this might be happening in your business?

Turn the finding into a next step.

If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.

Let’s start with one thing.

What would better performance look like?

Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.

No transaction files needed for the first conversation.