Leak 15 · Suppliers & Procurement - Missed volume discount thresholds

Buying 480 units at the 100-unit price when 500 would have earned the next break. Or buying 500 units of something that does not move to get the break. Both cost money.

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

What is it?

Supplier quantity breaks are simple in principle and missed in practice. Buyers place POs from the replenishment suggestion without seeing the next break. The opposite error is common too: rounding up to a break on slow items and creating dead stock. The leak is the difference between how you buy and how the price list rewards buying.

Family
Suppliers & Procurement
Primary owner
Purchasing Manager
Secondary owners
CFO, Inventory Manager
Primary impact
Gross profit
Typical data source
Supplier price lists with quantity breaks, purchase order history
Detection difficulty
30-day measurability

Ask yourself

Do your buyers see the next quantity-break price when they place a purchase 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.

  • POs with quantities just below a price break.
  • Buyers who do not have the current break schedule in front of them.
  • Frequent small POs to the same supplier that could be combined.

What data do I need?

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

Field
Supplier price list with quantity breaks
PO lines: item, quantity, unit cost, date
Item demand rate, to judge whether rounding up is sensible

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. 1Take your top supplier’s price list and last quarter’s POs to them.
  2. 2Find PO lines within 10% below a quantity break.
  3. 3For each, calculate the saving if the order had been rounded up, and check the item’s monthly demand.
Missed saving = (unit cost paid − break unit cost) × quantity, where rounding up is covered by less than 90 days of demand

Then ask one question: How many of these were a decision, and how many were the buyer not seeing the break?

How much could it be costing us?

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

Σ over near-miss PO lines of missed saving, for items where the extra quantity would sell within a defined window

Common root causes

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

Process
No review of PO quantities against breaks before release.
Data
Supplier quantity breaks are not loaded into the ERP, or are stale.
Technology
The PO screen does not show the next break or the saving.

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 near-miss report per supplier after each PO cycle.

  2. Level 2

    Data

    Load current quantity breaks into the ERP item-supplier record and keep them updated at each price change.

  3. Level 3

    Workflow

    Show the next break and the demand cover in the PO screen, and suggest consolidation across items to reach dollar-based breaks.

Where AI helps

  • Extracting break schedules from supplier price lists in varied formats.

Where AI probably doesn’t

Deciding whether to round up is a demand calculation the ERP can do once the breaks are loaded.

Before you call it a leak

  • A break earned by buying slow stock is not a saving. Always check demand cover.

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.