Why Your Procurement Team Doesn't Know When a Supplier Changes Your PO

2026-05-28

Suppliers change PO quantities and delivery dates without telling you. By the time your procurement team notices, production has already been affected. Here's how to catch PO amendments the day they happen.

Why Your Procurement Team Doesn't Know When a Supplier Changes Your PO

Here's something that happens at every manufacturing company, every week:

Your procurement team places a purchase order for 100,000 units of an API. The supplier confirms. Production plans the batch schedule around that delivery date. Everyone moves on.

Three weeks later, someone notices the PO now shows 49,000 units. The delivery date shifted by two weeks. Nobody was informed. Nobody approved it. The production schedule is already wrong.

How did this happen without anyone knowing?

Because the data changed inside SAP, and nobody was watching.

The Silent PO Amendment Problem

In most manufacturing setups, purchase orders live inside SAP or a similar ERP. The system updates PO data when suppliers push changes through EDI, or when someone at the supplier's end modifies the order in their system.

The problem is that these changes are silent. There's no alert. No email. No notification to the person who placed the order. The data simply changes, and the old values are overwritten.

Your procurement team sees the current state of every PO. But they never see what changed.

What Changes Without Warning

Based on real data from manufacturing companies tracking SAP PO changes, here are the most common silent amendments:

1. Ordered Quantity Reduction

The supplier reduces the total ordered quantity — sometimes by 50% or more. This is the most dangerous change because it directly impacts how much material you'll receive. If your production schedule assumes 100,000 units and only 49,000 arrive, you have a line stoppage.

Why it happens: Supplier capacity issues, raw material shortages on their end, or partial order cancellations that weren't communicated verbally.

2. Delivery Date Shifts

The promised delivery date quietly moves forward by days or weeks. Your production planning team is working off the original date. By the time someone notices, the buffer is gone.

Why it happens: Production delays at the supplier, logistics issues, or the supplier optimizing their own schedule at your expense.

3. Open Quantity Doesn't Add Up

After a partial delivery, the open quantity should equal the original order minus what was delivered. Sometimes it doesn't — open quantity drops by 10,000 but delivered only goes up by 5,000. The missing 5,000 units were silently cancelled.

Why it happens: The supplier adjusts the order after partial delivery, effectively reducing the remaining commitment.

Why Traditional Approaches Fail

"We review POs weekly"

A weekly review means changes can go unnoticed for up to 7 days. In manufacturing, that's enough time for a wrong production schedule to consume materials you don't have replacements for.

"SAP sends us reports"

SAP sends a snapshot — the current state. It doesn't tell you what the state was yesterday. Comparing two PDF reports manually is what your team is doing at 6 PM on a Friday, and they're missing things.

"Our supplier would tell us"

They should. They don't always. Sometimes the change is made by a different department at the supplier's end. Sometimes it's a system-level adjustment that nobody thinks to communicate. Relying on human communication for data that changes in a database is a process waiting to break.

What Actually Works: Automated Change Detection

The fix isn't more meetings or more reports. It's automated comparison:

Track Every Daily Snapshot

Store each day's PO data as a versioned record. Don't just look at today's numbers — keep yesterday's for comparison.

Compare Net Daily Changes

Don't compare every intermediate revision (the data might flip back and forth during the day). Compare the first value of the day to the last value. If they're the same, nothing meaningful happened.

Flag What Matters, Ignore What Doesn't

Not every change is a problem:

• Normal delivery: Open quantity goes down by 500, delivered goes up by 500. That's goods receipt — expected and good.
• Quantity amendment: Open quantity goes down by 500, delivered goes up by 200. The other 300 disappeared. That's a problem.
• Delivery date shift: Any change to the promised delivery date needs attention, period.
• Order quantity change: The total PO quantity itself changed. This is always actionable.

Surface Changes to the Right People

Plant heads should see changes for their group companies. Procurement should see changes for their vendors. The CEO should see a summary of all amendments above a threshold value.

The Business Impact

Companies that implemented automated PO change detection report:

• Catching delivery date shifts within 24 hours instead of discovering them when material doesn't arrive
• Identifying quantity reductions before production scheduling — adjusting batch plans proactively instead of reactively
• Better supplier conversations — "Your system shows you reduced PO 4500529979 from 1,000,000 to 492,720 on May 27th. Can you explain?" is a very different conversation than "We didn't get enough material, what happened?"
• Audit trail for disputes — when a supplier claims the order was always for 49,000 units, you have timestamped evidence showing it was 100,000 until three weeks ago

Getting Started

You don't need to replace your ERP or buy procurement software. Start with:

1. Store daily PO snapshots in a versioned table (your ERP already has the data — just capture it daily)

2. Build a simple daily comparison — first revision vs. last revision, per item, per day

3. Filter out normal deliveries — if open decreased by X and delivered increased by X, that's fine

4. Flag everything else — quantity changes, delivery date shifts, and mismatched open/delivered movements

5. Show it where people already look — embed the change log in the dashboard your plant heads check every morning

The difference between a team that's surprised by supplier changes and one that catches them the same day is just one comparison query running once a day.

Flobri automatically tracks SAP purchase order amendments — quantity changes, delivery date shifts, and silent cancellations — so your procurement team knows what changed before production is affected. See how it works →