Leak 06 · Pricing & Margin - Small orders priced below their cost-to-serve
A $40 order with $12 of gross profit costs $25 to pick, pack, invoice, and deliver. Multiply by thousands of orders a year.
Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.
What is it?
Gross margin looks fine on small orders. The problem is below the gross margin line: order entry, picking, packing, delivery, invoicing, and collections cost roughly the same for a one-line order as for a ten-line order. Below some order value the business loses money on every order, and nothing in the pricing structure discourages it.
- Family
- Pricing & Margin
- Primary owner
- CFO
- Secondary owners
- Pricing Manager, Operations Manager
- Primary impact
- EBITDA
- Typical data source
- ERP order headers and lines, warehouse and delivery cost estimates
- Detection difficulty
- 30-day measurability
Ask yourself
Do you know the fully loaded cost of picking, packing, and delivering a one-line order?
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 large share of orders below a small dollar value, often from the same customers.
- No minimum order value, small-order fee, or minimum line quantity.
- Customers who place daily small orders instead of a weekly consolidated one.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| Order header: customer, date, order value, gross profit, line count |
| Delivery method and freight charged |
| An estimate of cost per order for pick, pack, invoice, and deliver |
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.
- 1Estimate your cost per order: total warehouse, delivery, and order-processing cost for a month divided by orders shipped.
- 2Export last month’s orders with gross profit dollars.
- 3Count the orders whose gross profit is below the cost per order, and sum the gap.
Loss per order = cost to serve per order − gross profit on the order, where positive
Then ask one question: Which ten customers generate the most sub-economic orders, and what would happen if you asked them to consolidate?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Number of sub-economic orders per year × average shortfall × share you can realistically consolidate, surcharge, or reprice
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No minimum order policy, or one that is not enforced.
- Data
- Cost-to-serve has never been estimated, so nobody knows where the threshold is.
- Technology
- The order-entry system cannot warn on small orders or apply a small-order charge 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.
Level 1
Visibility
A monthly count of orders below the economic minimum by customer.
Level 2
Policy
A published minimum order value or small-order fee, applied consistently.
Level 3
Workflow
Prompt CSRs at order entry to consolidate with open orders for the same customer or apply the fee.
Where AI helps
- Identifying customers whose small orders could be consolidated based on their ordering pattern, and drafting the conversation.
Where AI probably doesn’t
Setting a minimum order value is a policy decision. Most of the value comes from making one and enforcing it.
Before you call it a leak
- Some small orders are strategically important: emergency support for a large account, or a new customer’s first purchase. Segment before acting.
- Cost-to-serve estimates are rough. Use them to find the threshold, not to price individual orders to the penny.
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.
Related leaks
- Leak 13 · FreightLow-value orders below economic minimumA minimum exists on paper. A third of orders are below it. Each one is handled, delivered, and invoiced at a loss.
- Leak 09 · FreightUnprofitable emergency deliveriesA driver spends two hours delivering a $90 part because the customer’s line is down. It was the right call once. It is now a habit nobody prices.
- Leak 10 · FreightExcessive split shipmentsOne order, three boxes, three carrier charges, one freight charge to the customer. Backorders and branch stocking decide it, not anyone in particular.
- Leak 12 · FreightExcessive customer-specific handlingCustom labels, kitting, special packaging, portal data entry, certs with every shipment. Real service, real labor, and usually free.
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.