Ship Date Confirmation Accuracy: Why Acknowledged POs Still Miss Their Dates
🎧 Listen to this article (17 min)
Most procurement teams treat the purchase order acknowledgement as the finish line. The PO goes out, the supplier sends back a confirmation with a ship date, and the line gets marked confirmed in the ERP. Planning moves on. Then six weeks later the material does not show up, and nobody can explain why a confirmed date turned into a late delivery.
The gap is not acknowledgement volume. Plenty of teams get acknowledgements back on 80 or 90 percent of their lines. The gap is accuracy. A confirmation is only useful if the date in it reflects what the supplier can actually do, and if any change to that date gets back to you before it becomes a shortage.
According to Gartner, 50% of purchase order lines undergo changes after issuance, making real-time supplier visibility a procurement priority. That single number explains most of the problem. Half your confirmed dates are going to move. The question is whether you find out when it happens or when the dock is empty.
What a PO acknowledgement actually tells you
An acknowledgement is a supplier statement about three things: that they received the order, that they accept the commercial terms, and that they commit to a delivery or ship date. Most ERP systems record it as a single status flag. That flattening is where the information loss starts.
In practice there are at least four distinct acknowledgement states worth separating:
- Full acknowledgement. Supplier confirms quantity, price, and the requested date with no changes.
- Acknowledged with date change. Supplier accepts the order but commits to a different ship date than requested.
- Partial acknowledgement. Supplier confirms some lines or a split quantity, leaving the rest open.
- Acknowledged with commercial change. Price, unit of measure, or minimum order quantity differs from the PO.
If your system collapses all four into "confirmed," your planning data is already wrong on day one. A line acknowledged at week 10 against a week 6 request is not the same as a line acknowledged on time, but a binary flag treats them identically. Planners then build schedules against the requested date because that is what the MRP run sees.
Why confirmed dates slip anyway
Even clean acknowledgements degrade. The supplier commits in good faith, then their own upstream supply moves, a machine goes down, or a larger customer jumps the queue. None of that is unusual. What matters is the latency between the supplier knowing and you knowing.
A Deloitte supply chain study found that 70% of supply chain disruptions originate before materials leave the supplier's facility. The signal exists upstream well before it reaches you. In most mid-market operations the only mechanism for catching it is a buyer sending a follow-up email, which happens on a cadence set by how much time the buyer has that week.
That is the structural issue. Acknowledgement is treated as a one-time event rather than a commitment that needs monitoring across its life. The confirmation is captured once, written to the ERP, and never revisited until something breaks. Our team sees the same pattern across manufacturers running every major platform, and it has nothing to do with which ERP is in place.
The metrics that actually separate good from bad
Acknowledgement rate alone is a vanity metric. It tells you how responsive your suppliers are to email, not how reliable their commitments are. Four measures give you a real picture.
Acknowledgement rate within SLA
Not just whether a PO was acknowledged, but whether it was acknowledged inside your stated window. A 48 or 72 hour standard is common. Measure the percentage of lines confirmed within that window, broken out by supplier. Suppliers who routinely take two weeks to confirm are telling you something about how they will behave when a date slips.
Date change rate after acknowledgement
Of the lines acknowledged, what percentage had their ship date move at least once afterward? This is the number that predicts expedite spend. A supplier with a 10 percent post-acknowledgement change rate is operationally different from one at 45 percent, even if both acknowledge every order.
Confirmation accuracy
Compare the final acknowledged ship date against the actual ship date. The absolute variance in days, averaged by supplier, tells you how much to trust a given confirmation. Some suppliers are consistently three days late on every commitment, which is easy to plan around once you know it. Others are unpredictable, which is far more expensive.
Notification lead time on changes
When a date does move, how many days of warning did you get before the original commitment date? Negative numbers mean you found out after the fact. This is the single best indicator of whether a supplier relationship is actually working, and almost nobody tracks it.
According to McKinsey, companies with mature supply chain visibility capabilities outperform peers by 15-20% on OTIF metrics. The capability gap is mostly in this layer, the ability to see commitment changes early rather than at receipt. More on how this feeds delivery performance tracking in our breakdown of supplier OTIF tracking when ERP data is incomplete.
Where ERP acknowledgement handling falls short
Every major ERP has a field for a confirmed date. The problem is not the field. It is that the field has to be populated by someone, from information that arrives as unstructured email or a PDF attachment, and that it holds a single value with no history.
Whether your procurement team runs on SAP, Oracle NetSuite, Microsoft Dynamics 365, Epicor, or Infor, the built-in acknowledgement workflow assumes structured inbound data. That assumption holds for the fraction of your supplier base on EDI or a connected portal. For everyone else, and in most mid-market operations that is the clear majority, a buyer reads the email and retypes the date.
Three consequences follow. First, the data is as current as the last time a human touched it. Second, there is no audit trail of how many times a date moved, because each update overwrites the last. Third, nothing fires automatically when a commitment changes, because the system has no concept of a commitment changing. We go deeper on this split in our post on ERP-agnostic PO automation versus built-in ERP modules.
For teams running Microsoft Dynamics 365, whether Business Central, Finance and Supply Chain, or Navision, Leverage AI integrates directly with your existing ERP environment to automate supplier PO confirmations, flag exceptions in real time, and surface OTIF data without custom development or ERP modification. The details are in our guide to Dynamics 365 procurement automation and PO visibility.
Building an acknowledgement process that holds up
The teams that fix this do not start with software. They start by defining what a valid acknowledgement is, then enforce it.
Set an explicit acknowledgement standard and publish it. Suppliers need to know the window, the required fields, and what happens if they miss it. Most supplier agreements say nothing about acknowledgement timing, which makes enforcement a conversation rather than a term.
Require a committed ship date, not a lead time. "Four to six weeks" is not a commitment. A specific date is. Lead time ranges are the most common way an acknowledgement looks complete while carrying no planning value.
Separate the requested date from the confirmed date in your data model. Keep both. The variance between them, aggregated by supplier and by part, is one of the most useful datasets in procurement and most teams destroy it by overwriting one with the other.
Monitor confirmed dates continuously, not at the point of receipt. This is the piece that requires automation. Checking in on open commitments across hundreds of lines is not something a buyer can do manually at any useful frequency.
Define what happens when a date moves. Who gets notified, within what window, and what the escalation path is. A detected change that lands in an unmonitored inbox is the same as no detection. Our PO exception management checklist covers the routing side of this in detail.
What automation changes
The practical shift is moving acknowledgement from a manual data entry task to a monitored data flow. Supplier replies arrive the same way they always did, as email with text or a PDF attached. The difference is that the content gets parsed, validated against the open PO, and written back with the change history intact.
That makes a few things possible that are not possible with manual handling. Date changes get detected the day the supplier sends them rather than whenever a buyer next opens the thread. Acknowledgement SLA compliance becomes measurable per supplier without anyone building a spreadsheet. And the variance between confirmed and actual ship dates accumulates into supplier scorecards that reflect behavior rather than impressions.
None of this requires suppliers to log into anything or adopt a new system. That matters more than it sounds. The suppliers most likely to cause date problems are usually the smallest ones with the least IT capacity, which is exactly the group that will not adopt a portal. Any approach that depends on supplier onboarding will systematically miss the accounts where the risk actually sits.
On the cost side, the case is usually straightforward once you quantify expedite freight and unplanned downtime tied to late material. We built out the math in our PO tracking automation ROI model, and you can see how the platform handles acknowledgement capture on our product page.
Segmenting suppliers by acknowledgement behavior
Not every supplier needs the same level of attention, and treating them uniformly is how buyer time gets wasted. Once you have confirmation accuracy and notification lead time by supplier, a practical segmentation falls out of the data.
The first group confirms quickly and hits their dates. These need almost nothing beyond periodic verification. The second group confirms quickly but misses dates often. The commitment process works, the execution does not, and the fix is usually a conversation about capacity planning rather than communication. The third group is slow to confirm but reliable once they do, which often means the acknowledgement is being handled by someone whose main job is something else. The fourth group is slow and unreliable, and that is where buyer attention and escalation should concentrate.
Most teams discover that the fourth group is smaller than they assumed, usually 10 to 15 percent of active suppliers, but accounts for the majority of expedite activity. That concentration is what makes the measurement worth doing. Without it, buyers spread follow-up effort evenly across the base and spend most of their chase time on suppliers who were never going to be late.
Parsing and validating supplier replies
The mechanical problem underneath all of this is that supplier acknowledgements arrive as free text, PDF attachments, or scanned documents, in whatever format each supplier happens to use. There is no standard. One sends a formatted order confirmation document, another replies to the PO email with a sentence, a third attaches a spreadsheet.
Automating capture means handling all three without asking anyone to change. The parsing step pulls out the PO number, the line references, the quantities, and the dates. The validation step is where most of the value sits, because parsed data that goes straight into the ERP without checking is worse than no automation at all.
Useful validation rules are specific. Does the acknowledged quantity match the ordered quantity, and if not, is the difference inside an agreed tolerance? Is the confirmed date inside a plausible range given the part's historical lead time? Does the referenced PO number exist and is the line still open? Does the confirmed price match the PO price, and if not, by how much? Anything that fails a rule becomes an exception for a human to resolve. Anything that passes gets written back automatically.
That split is what makes the workload manageable. Aberdeen Group research shows that automated PO tracking reduces operational costs by up to 30% for mid-market manufacturers, and most of that reduction comes from eliminating the clean cases rather than from handling the messy ones. The exceptions still need judgment. The 70 or 80 percent that are straightforward do not.
A realistic first 60 days
If you want to improve confirmation accuracy without a large program, the sequence that tends to work looks like this.
Weeks one and two: pull the last six months of PO history and calculate current acknowledgement rate, date change rate, and confirmed-versus-actual variance by supplier. Most teams have never seen these numbers and the distribution is usually more skewed than expected, with a small group of suppliers driving most of the variance.
Weeks three and four: publish an acknowledgement standard. Define the window, the required fields, and the escalation path. Send it to the top 20 suppliers by line volume rather than by spend, since line volume is what drives buyer workload.
Weeks five through eight: instrument the monitoring. Automate the capture of inbound acknowledgements and date changes, set up alerting on commitment changes, and start reporting notification lead time alongside your existing OTIF numbers. Review with the supplier base at 60 days using their own data.
The outcome you are after is not a higher acknowledgement rate. It is a shorter gap between a supplier knowing their date moved and your planner knowing it.
Frequently asked questions
What is a good PO acknowledgement rate?
Most mid-market manufacturers land between 60 and 85 percent on raw acknowledgement rate. The more useful target is acknowledgement within a defined SLA window, typically 48 to 72 hours, where the same teams often sit below 50 percent. Rate alone does not predict delivery performance, so pair it with post-acknowledgement date change rate.
How is a PO acknowledgement different from a ship date confirmation?
An acknowledgement confirms the supplier received and accepted the order. A ship date confirmation is a specific commitment to when material will leave their facility. Many acknowledgements arrive without a firm date, or with a lead time range instead of a date, which makes them unusable for planning. Treat them as two separate data points.
Can our ERP track ship date changes over time?
Most ERP systems store a single confirmed date field that gets overwritten on each update, so the change history is lost. SAP, Oracle NetSuite, Microsoft Dynamics 365, Epicor, and Infor all handle the current value well. Preserving the full sequence of commitment changes generally requires either custom development or a layer that sits alongside the ERP and writes back.
What if our suppliers will not use a portal?
That is the normal case, not the exception. Smaller suppliers rarely have the staff to maintain logins across every customer. The workable approach is to meet them where they already are, which is email, and parse the content of their replies rather than requiring them to enter data into your system.
How long does it take to see improvement in confirmation accuracy?
Measurement improves immediately once you start capturing confirmed-versus-actual variance. Supplier behavior usually takes one to two quarters to shift, and it shifts fastest when you review the data with the supplier directly. Scorecards built from their own acknowledgement history are considerably more persuasive than general complaints about lateness.
Related reading
- Dynamics 365 Procurement Automation and PO Visibility
- ERP-Agnostic PO Automation vs Built-In ERP Modules
- Supplier OTIF Tracking When ERP Data Is Incomplete
- PO Exception Management Checklist
- PO Tracking Automation ROI Model
About Michael Ciavarella
Michael Vincent Ciavarella is a Director of Operations focused on modernizing old-school industries like logistics and manufacturing. He writes about simplifying messy workflows, introducing practical technology, and making change actually stick with the teams who use it every day.