Supplier OTIF Tracking When Delivery Updates Live in Email, Not Your ERP
🎧 Listen to this article (11 min)
OTIF measures whether a supplier order arrived on time and in complete quantity. Most mid-market manufacturers cannot measure it accurately because the delivery updates that determine the answer arrive by email and PDF, not through the ERP. Your ERP records what you planned and what you eventually received. It does not record the ship date a supplier confirmed in a Tuesday afternoon email, the partial shipment noted in a PDF packing list, or the two-week slip mentioned in a reply to a follow-up. That gap is why OTIF reporting so often lags reality by weeks.
Closing it requires capturing supplier communications as structured data and joining them to open purchase orders. This guide covers what data you actually need, how to integrate unstructured supplier updates with ERP records, and how to evaluate platforms that do this work.
Why Supplier OTIF Breaks Down Outside the ERP
OTIF stands for On Time In Full. An order only counts as compliant if it arrives within the agreed delivery window and at the full ordered quantity. That makes it a stricter measure than on-time delivery, which ignores quantity entirely. A supplier who ships on the promised date at 70 percent of the ordered quantity passes OTD and fails OTIF.
The measurement problem is structural. ERPs are transaction systems. They capture the purchase order when it is issued and the receipt when goods arrive at the dock. What happens in between lives in email threads, attached PDFs, and supplier portal notifications that nobody reconciles back to the PO record.
According to Gartner, 50% of purchase order lines undergo changes after issuance, making real-time supplier visibility a procurement priority. Those changes almost never originate in the ERP. They originate in a supplier's reply.
A Deloitte supply chain study found that 70% of supply chain disruptions originate before materials leave the supplier's facility. The early warning signs are there. They are just sitting in an inbox where no dashboard can see them.
Four failure modes show up consistently at mid-market manufacturers and distributors:
- Inconsistent OTIF definitions. One buyer counts a two-day early delivery as compliant. Another counts it as a variance. Without a locked definition, cross-supplier comparison is meaningless.
- Long and variable lead times. When a supplier quotes 8 to 12 weeks, the "agreed date" becomes ambiguous, and OTIF scoring inherits that ambiguity.
- Data entry lag. A buyer updates the ERP promise date days after the supplier email arrives, if at all. The scorecard reflects when someone typed, not when the supplier said.
- Unstructured communications. Ship confirmations, split shipment notices, and quantity changes arrive as prose and attachments. None of it is queryable.
The result is a lagging KPI that operations leaders do not trust. By the time OTIF reports a decline, the late orders have already reached customers.
The Minimum Data Set for Accurate OTIF Measurement
Reliable OTIF requires a specific set of fields, and about half of them do not exist in most ERP records at the fidelity you need. Here is the minimum external OTIF data set and where each field actually originates:
| Field | Primary Source | Typically in ERP? |
|---|---|---|
| Supplier ID | ERP vendor master | Yes |
| SKU / Part number | ERP PO line | Yes |
| Order quantity | ERP PO line | Yes |
| Requested date | ERP PO line | Yes |
| Supplier-confirmed ship date | Supplier email or PDF acknowledgement | Rarely, and usually stale |
| Revised promise date | Supplier email reply | No |
| Shipped quantity | Packing list PDF, ASN, or email | Only at receipt |
| Split shipment flag | Supplier email | No |
| Delivery window tolerance | Contract or buyer policy | Sometimes |
| Delivery confirm source | Email, EDI 856, carrier feed, WMS | No |
The pattern is clear. Everything the ERP holds well describes intent. Everything that describes what the supplier actually committed to and shipped arrives through a channel the ERP does not read.
Consolidating these fields into one comparable record is the entire job. Without a single source of truth, you cannot compare supplier A against supplier B, because their data arrived through different channels with different completeness.
Integrating Email and PDF Updates With Your ERP
The integration pattern that works is a three-step loop: capture, match, write back.
Step one, capture and parse. Route supplier communications through a system that reads both the message body and attachments. Ship date confirmations, quantity changes, and delay notices need to be extracted as fields, not stored as text.
Step two, match to open POs. Extracted updates need to resolve to a specific PO line. This is where most homegrown attempts fail. Suppliers reference orders inconsistently, sometimes by their own sales order number, sometimes by part number and quantity, sometimes not at all. Matching logic has to handle partial and fuzzy identifiers.
Step three, write structured milestones back. Confirmed ship dates, revised promise dates, and shipped quantities post to the supplier performance record and, where appropriate, back to the ERP PO line. Now the scorecard reflects supplier commitments as they are made.
Whether your procurement team runs on SAP, Oracle NetSuite, Microsoft Dynamics 365, Epicor, or Infor, the capture and match logic sits outside the ERP and feeds it. That is the point. Rebuilding email parsing inside an ERP module means custom development you will maintain forever.
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.
Aberdeen Group research shows that automated PO tracking reduces operational costs by up to 30% for mid-market manufacturers. Most of that saving comes from eliminating the manual reconciliation step between inbox and ERP.
Connecting Supplier Delivery Performance to Operational Impact
An OTIF percentage on its own does not drive decisions. What drives decisions is knowing which suppliers are causing which downstream problems.
The linkage worth building runs supplier to part to order to customer. A supplier at 78 percent OTIF matters very differently depending on whether their parts feed a slow-moving spare or your highest-volume finished good. Same score, completely different operational exposure.
Three views make this concrete:
- Late order attribution. For every customer order that shipped late, which supplier PO was the constraint? This converts OTIF from a vendor metric into a revenue-risk metric.
- Lead time variance, not just averages. A supplier averaging 10 days with a range of 6 to 22 is harder to plan around than one consistently at 14. Variance is what breaks planning.
- Responsiveness. How long does a supplier take to acknowledge a PO or answer a status request? Slow responders correlate with late deliveries well before the delivery is actually late.
According to McKinsey, companies with mature supply chain visibility capabilities outperform peers by 15-20% on OTIF metrics. The maturity gap is largely about whether performance data is connected to operational consequence or sitting in an isolated procurement report.
Evaluating Supplier OTIF and Scorecard Platforms
If you are comparing platforms, the questions that actually separate them are narrow. Most tools can display a scorecard. Far fewer can populate one accurately when the source data arrives by email.
| Capability | Why It Matters | What to Ask |
|---|---|---|
| Unstructured data capture | Confirmations arrive as email prose and PDFs | Does it parse attachments, or only structured EDI? |
| PO line matching | Updates must resolve to a specific line to score OTIF | How does it match when the supplier references their own order number? |
| ERP integration depth | Determines whether data flows both ways | Read-only, or does it write confirmed dates back? |
| No supplier portal requirement | Suppliers will not adopt another login | Does it work with suppliers who only use email? |
| Automated follow-up | Chasing acknowledgements is the largest manual cost | Does it send and track follow-ups automatically? |
| Exception surfacing | Early warnings are the point | Does it flag date and quantity changes in real time? |
| ERP-agnostic architecture | Avoids lock-in and re-implementation | Does it depend on one ERP vendor's stack? |
The portal question deserves particular attention. Portal-based approaches assume suppliers will log in to provide updates. In practice, mid-market suppliers with dozens of customers do not adopt dozens of portals. They reply to email. A platform that requires supplier portal adoption will have coverage gaps exactly where you need data most.
IDC projects that 60% of enterprise procurement teams will transition to AI-powered automation by 2025. The teams seeing results are the ones that automated data capture from the channels suppliers already use rather than trying to change supplier behavior.
How to Start When Your Data Is Fragmented
You do not need clean data before you start. You need a narrow pilot that produces a comparable measurement.
Pick your top 10 suppliers by spend or by criticality. Lock a single OTIF definition, including the delivery window tolerance, and write it down. Connect ERP PO data and the supplier email channel for just those suppliers. Run it for one full order cycle and compare the automated OTIF number against whatever your current report says.
The gap between those two numbers is the value case. In most cases the automated number is worse, because it captures the slips your current process misses. That is the finding worth taking to your operations leadership.
From there, expand by supplier tier rather than trying to onboard everyone at once. Standardize as you go.
Frequently Asked Questions
What is the difference between OTIF and on-time delivery?
OTIF (On Time In Full) checks whether an order arrived on time and at the complete ordered quantity. On-time delivery only measures whether the order arrived by the promised date. A partial shipment delivered on schedule passes OTD and fails OTIF.
Why is ERP data often insufficient for real-time OTIF tracking?
ERP systems record planned and completed transactions. They do not capture the interim updates suppliers send by email, such as revised ship dates, split shipment notices, or quantity changes. Those updates determine OTIF compliance, so an ERP-only view reports OTIF weeks after the fact.
How can AI help track supplier updates that come via email and PDFs?
AI extracts shipment and confirmation details from email bodies and attachments, matches them to the correct open purchase order line, and updates the performance record automatically. That removes the manual re-keying step where most data loss and delay occurs.
What data sources are needed beyond the ERP to measure OTIF effectively?
Supplier emails and PDF acknowledgements, EDI 856 advance ship notices where available, carrier or TMS delivery feeds, and WMS receipt data. The ERP supplies order intent. These external sources supply what the supplier actually committed to and shipped.
How do I start automating supplier delivery tracking when data is fragmented?
Start with your top 10 suppliers, lock one OTIF definition including delivery window tolerance, connect ERP PO data and the email channel for that group only, and run one full order cycle. Compare the automated result against your current report, then expand by supplier tier.
Do suppliers need to adopt a portal for this to work?
No. Requiring portal adoption creates coverage gaps, because mid-market suppliers serving many customers rarely log into customer-specific portals. Capturing updates from email keeps coverage complete without asking suppliers to change how they work.
