Supplier DIFOT: Measure the Delivery That Actually Matters

A supplier can tell you that an order will be late, your buyer can update the purchase order due date, and the goods can then arrive exactly when the system says they should. The report may show an on-time delivery.

That does not necessarily mean the supplier performed on time.

This is one of the common problems with supplier DIFOT reporting. DIFOT usually means **Delivered In Full On Time**, but the result is only as meaningful as the date, quantity and delivery event being measured. If those details change during the life of a purchase order and the original information is lost, a clean-looking score can hide a real delivery problem.

Start with the commitment you originally made

To assess delivery performance, retain the **original requested delivery date and quantity** for each purchase order line. This is the baseline: what the business asked the supplier to deliver, and when it asked for it.

You also need the latest information used to run the operation. If a supplier advises that an order will arrive later than planned, the current expected date should often be updated. Planners, warehouse teams and customer-facing teams need the best available view of when stock is likely to arrive.

The difficulty comes when a system has only one date on the purchase order line. If the original requested date is overwritten with the revised expected date, the historical commitment disappears.

For example:

- The original requested date is 10 June. - The supplier advises that delivery will be on 24 June. - The PO due date is changed to 24 June. - The goods arrive on 24 June.

A report based only on the current PO due date will show an on-time delivery. A report based on the original request will show that the supplier was two weeks late.

Neither date is useless. They answer different questions.

The current expected date helps the business manage its supply plan. The original requested date helps the business understand whether the supplier met the original requirement. Treating them as though they are the same thing makes both planning and performance reporting less clear.

A late promise is not always a harmful delivery

It is tempting to treat every revised delivery date as a DIFOT miss. In practice, that can produce a score that is technically accurate but not especially useful.

Suppose a supplier advises that an order will be three weeks late. At the same time, demand is lower than expected and existing inventory will comfortably cover requirements until the revised arrival date. There is no stockout risk, no production interruption and no customer service impact.

The business may decide to accept the revised date. In that situation, recording the delay as a negative result may add little value, particularly if the purpose of the measure is to identify supplier failures that affect the operation.

Now consider the same three-week delay where demand remains steady. Inventory is running down, customer orders are at risk, or production may stop without the material. This is a very different situation. The revised date has a genuine operational consequence, so a negative DIFOT result is appropriate.

The point is not to excuse poor supplier performance. It is to distinguish between a changed commitment and a delay that has materially affected the business.

A practical approach is to retain both the original and current dates, then use an **Ignore for DIFOT** flag when a revised date has been reviewed and accepted. This creates an auditable record:

- The original commitment remains visible. - The current expected date remains available for planning. - The business can show that the delay was considered. - The DIFOT result reflects whether the delay mattered operationally.

Changing the original requested date can achieve a similar outcome, but it weakens the ability to analyse the supplier's original performance later. Retaining the history is usually more informative.

Delivery needs an agreed finish line

Even with the right dates, supplier and customer can report very different DIFOT results if they define delivery differently.

Consider an overseas shipment under **FOB** Incoterms. The supplier may regard its delivery obligation as complete when the goods are delivered to the vessel. The buying business may measure delivery when the goods are physically received at its warehouse.

Those can be weeks apart.

If the supplier's report measures delivery to the vessel and the buyer's report measures receipt at site, one party may report a high DIFOT score while the other reports a low score. This does not automatically mean one of them has made a calculation error. They may simply be measuring different events.

Before comparing results with a supplier, agree what “delivery” means for that relationship. Depending on the product and Incoterms, the relevant event could be:

- dispatch from the supplier; - delivery to a carrier, port or vessel; - arrival at a port; - receipt at a distribution centre; or - receipt at the final manufacturing or customer-facing site.

Quantity needs the same clarity. Is “in full” measured when the supplier ships the goods, or when the receiving site confirms the actual quantity received? For many businesses, site receipt is the more useful measure because it reflects what is actually available to use or sell. But the right measure depends on the commercial arrangement and the decision the report is meant to support.

Keep planning data and performance data separate

A useful supplier delivery process can answer three separate questions.

What did we originally ask for?

This is the original requested date and original requested quantity on the PO line. It establishes the initial requirement and provides the baseline for measuring commitment performance.

What did the supplier later say they could provide?

This is the current expected date and, where relevant, the revised quantity. It is the information planners need to assess future inventory availability and respond to risks.

What happened, and did it affect the business?

This is the actual receipt date and actual received quantity, together with a review of the operational impact. Did the delay create an out-of-stock risk, disrupt production, require expediting, or affect customer service? Was the revised date accepted because there was enough stock to cover the gap?

Keeping these questions separate avoids a common reporting trap: using one changed PO due date to manage the current supply plan and judge historical performance at the same time.

Questions to settle before publishing a DIFOT score

DIFOT reports built into planning or purchasing systems can contain assumptions that are easy to miss. Before relying on the result, check the calculation logic with the people using the report.

Ask:

- Does the report use the original requested date or the latest revised due date? - Does it retain the original requested quantity if the PO quantity changes? - What date counts as the actual delivery date: dispatch, port delivery, vessel loading, warehouse receipt or site receipt? - Is the reported quantity based on shipment or confirmed receipt? - Which Incoterms apply, and do they match the point being measured? - Can an accepted delay be identified separately from a delay that caused an operational problem? - Are partial deliveries assessed in a way that reflects how the business actually uses the goods?

These are not technical details to leave entirely to a system configuration. They determine what the performance measure is actually saying.

Use the measure to improve decisions, not just score suppliers

A meaningful DIFOT measure can support supplier selection, performance reviews, contract discussions and improvement work. It can also help planners understand how much confidence to place in a supplier's expected dates when managing inventory and replenishment risk.

However, the score should lead to a useful conversation rather than become an end in itself. A low result may point to recurring late dispatches, unreliable transit times, incomplete shipments or a mismatch between the requested date and the agreed delivery terms. A high result may be genuine, or it may reflect a measure that has been made easier by repeatedly changing due dates.

The most useful reporting makes those distinctions visible. It gives the business a fair view of supplier performance while preserving the information needed to plan effectively.

Key Takeaways

- Retain the original requested delivery date and quantity for every PO line; they provide the baseline for supplier performance measurement. - Update the current expected date when better supplier information is available, but do not let that overwrite the original commitment. - A supplier delay should be assessed in terms of its business impact, not merely the fact that a date changed. - An accepted delay can be recorded separately, for example with an Ignore for DIFOT flag, while preserving the original history. - Agree exactly where delivery occurs and what quantity counts, especially where Incoterms mean that supplier dispatch and site receipt are different events. - A DIFOT score is only meaningful when the business and supplier are measuring the same commitment against the same delivery point.