To track purchase order dates reliably, preserve the buyer’s requirement, the supplier’s commitment, and the actual event as different fields. Label every date as dispatch, receipt, or availability for use, and attach its quantity, location, source, and revision. A single “delivery date” column cannot explain whether the supplier is late or planning has changed the need.
Use the PO date register and change log (Excel) to define those fields and investigate changes. This guide is about keeping dates meaningful; use the delivery recovery plan when a credible commitment no longer covers the requirement.
Define the dates before collecting them
Agree a short field dictionary with buying, planning, logistics, and receiving:
- Requested receipt date: when the buyer asks for the material at the stated destination.
- Required usable date: when planning needs accepted material available for the intended operation.
- Supplier-promised dispatch: when the supplier commits to sending the stated quantity from the named origin.
- Supplier-promised receipt: when the supplier commits to arrival at the stated destination, if that is actually what it confirms.
- Expected receipt: your current estimate based on the best available evidence; label the estimator and assumptions.
- Actual dispatch and receipt: recorded events supported by the relevant supplier, carrier, or warehouse evidence.
- Actual usable time: when the responsible process makes the material available after required acceptance and internal movement.
Microsoft separately describes requested and confirmed ship and receipt dates. Its calculations depend on configured transport and calendars, illustrating why a date’s meaning and derivation matter. Microsoft date documentation.
Your field names can differ. What matters is that a buyer can distinguish a supplier promise from a system estimate and a warehouse event. Do not relabel an estimated receipt as confirmed merely because it was calculated from a confirmed dispatch.
Attach dates to quantities and places
A date without a quantity is incomplete for a partial order. Record one dated schedule for each relevant quantity and destination. Preserve the relationship to the PO line and current revision.
For example, “1,000 due October 16” is materially different from “200 due October 9, 800 due October 16.” The latter may cover an early production need that the former does not. Link split schedules to the partial shipment record so updates do not add or lose quantity.
Identify the place as well as the date: supplier warehouse, port, receiving dock, another plant, or customer site. A supplier saying goods will be “delivered Friday” may mean delivery to a carrier or to your dock. Ask before entering it into the receipt field.
Where time matters, include time zone and cutoff. A date-only promise may be enough for routine replenishment but insufficient for a 10 a.m. production need or a 2 p.m. carrier collection. Increase precision where the decision requires it, rather than inventing precision the supplier has not provided.
Preserve a baseline and a current view
Keep the original requested date and first accepted commitment. Then maintain the latest approved requirement, latest supplier proposal, latest accepted commitment, and actual outcome. Store a dated change record instead of overwriting the history.
For each change, capture who initiated it, which field changed, old and new values, affected quantity, reason, supporting source, approval if needed, and record-update status. A buyer-approved production reschedule is different from a supplier delay, even if both move the receipt date by a week.
Use the original requirement to understand performance against the initial plan. Use the current accepted view to run today’s work. Show both when reporting. Otherwise, a series of late promises can make an order appear consistently on time because the target moves with it.
If the original baseline is unavailable, label it unavailable. Recover it from a valid PO or acknowledgement if possible, but do not reconstruct a convenient date from memory and present it as the original commitment.
Translate free-text supplier replies carefully
Record the supplier’s exact date expression and your structured interpretation. Ask for clarification when the meaning affects the next decision.
“Week 42” needs a year and a definition of dispatch versus receipt. “Four weeks” needs a starting event: order acceptance, drawing approval, deposit, or another condition. “End of month” may be a planning estimate rather than a firm commitment.
For a range, preserve earliest and latest dates. If planning needs the material before the latest date, ask for a firm quantity by the required cutoff. Do not use the earliest date as the promise merely because it gives a better coverage result.
When the supplier says “same date as before,” link the earlier commitment being incorporated. If two earlier dates exist, ask which one applies. Keep a precise next question and owner rather than guessing from thread order.
Derive estimates without turning them into commitments
Logistics can estimate receipt from goods-ready time, pickup availability, route transit, and receiving calendars. Record the inputs and who supplied them. Include customs, cross-dock, or appointment dependencies where they affect the particular route; do not hide them in a universal transit allowance.
Planning can then estimate availability for use using the receiving, inspection, and movement allowances established by those functions. An allowance is a planning assumption. It does not authorize quality release or guarantee that the actual inspection will finish on time.
Recalculate when the origin, destination, transport method, lot size, or calendar changes. A Friday dispatch on a route with no weekend receiving differs from a Tuesday dispatch with the same nominal transit duration. Retain the reason for the changed estimate even when the supplier’s dispatch promise is unchanged.
Worked example: dispatch is on time, material is still late
This illustrative example uses calendar dates and stated operating assumptions. Planning needs 400 units usable at Plant A by 10 a.m. Wednesday, October 14. Receiving needs one working day after arrival for its inspection and movement process. The buyer therefore requests receipt by Monday, October 12.
The supplier confirms dispatch from its warehouse on Friday, October 9. Logistics estimates receipt Tuesday, October 13, because the route takes two working days and Plant A does not receive on the weekend. This makes estimated usability Wednesday, October 14, at the end of the working day, after the 10 a.m. requirement.
The date record is:
Quantity / destination: 400 units / Plant A
Required usable time: October 14, 10 a.m. local
Requested receipt: October 12
Supplier-promised dispatch: October 9
Supplier-promised receipt: not provided
Estimated receipt: October 13
Estimated usable time: October 14, end of day
Gap: usable estimate misses the need time
The supplier has not necessarily broken its dispatch promise. The buyer nevertheless has a planning gap to resolve. Logistics obtains an express option for receipt Monday. The authorized buyer approves the cost, receiving confirms inspection capacity, and the supplier confirms the relevant pickup. These facts produce a revised estimate, with the original values retained.
If the actual Monday receipt is only 300 units, do not copy Monday’s date to all 400. Record 300 received and preserve the remaining 100 as open. The date tracking and quantity tracking views must agree.
Turn date changes into specific work
For a proposed later date, ask planning whether the affected quantity still covers demand. If not, establish the last viable recovery decision time. For an earlier date, check capacity, storage, acceptance, and commercial implications before assuming early delivery is welcome.
For a buyer-requested acceleration, retain the old accepted promise until the supplier confirms the new one. A revised PO expresses the new request; it does not prove the supplier accepted it. Use the PO change confirmation guide to close that gap.
For a missed milestone with no new estimate, keep the date unknown and create a timed request for a credible update. Copying yesterday’s overdue date forward one day at a time obscures the absence of a commitment.
Route changes based on consequence. A date adjustment with no demand impact may need only the normal authorized update. A change that removes the last recovery option needs a buyer and planning decision, even if the numeric difference is only one day.
Review the schedule before updating the system
Check whether a newer supplier message, PO revision, receipt, or planning change supersedes the value you are about to enter. Keep the source timestamp and the update timestamp separate; they explain how long the record lagged the known commitment.
After the update, read back the line and any split schedules. Verify dates, quantities, destination, and calculated fields. If a header update propagates across lines in your system, verify that it did not replace a distinct promise for another item.
When a change cannot be applied because of permissions or a system error, keep a named update action open. Tell the operational owner which current value remains unreliable. The task is not complete merely because someone attempted the edit.
Measure date reliability with a declared baseline
Choose a cohort of due schedules and define whether performance compares actual dispatch, receipt, or usable time against the corresponding promise or requirement. Avoid mixing those outcomes in one percentage.
For example, define on-time receipt as schedules whose full scheduled quantity was received by the first accepted receipt date, divided by all schedules due against that baseline in the period. State treatment of early receipts, approved cancellations, partial receipts, and buyer-driven changes. An alternate report can use the latest accepted date, but label it separately.
Track missing-date coverage as schedules lacking an explicit current supplier commitment divided by active schedules requiring one. Measure update lag from receipt of credible changed evidence to authorized record update. Neither measure proves the shipment will arrive; they indicate whether the working record is current and supported.
Finish with a date trail another buyer can trust
Date tracking closes for a schedule when actual events and any final disposition are recorded, differences from the requirement are explained, and no remaining quantity depends on an unresolved promise. The full order may still have quality, invoice, or claim work open.
Mandel’s purchase order management work connects supplier commitments with the order record and the actions needed to resolve differences. The important result is a date that means something precise, backed by evidence and attached to the quantity planning actually needs.
