Centralise the information that actually supports decisions
Bring the key data into one source: purchase order, supplier, item, quantity, requested date, confirmed date, received quantity, remaining balance and status. This avoids repeated checks across the ERP, emails and personal spreadsheets.
Keep only fields that have a clear use. A column without an owner or decision purpose will quickly become unreliable. Comments should remain factual: supplier commitment, reason for delay, next action and planned follow-up where relevant.
Minimum tracking dataset
These fields are enough to build an operational view.
- Purchase order and supplier.
- Item and quantity.
- Requested date.
- Confirmed date.
- Received quantity and balance.
- Status and next action.
Keep requested, confirmed and actual dates separate
The requested date represents the company need; the confirmed date represents the supplier commitment; the actual date measures final execution. Mixing them makes it impossible to understand how the schedule changed and who changed it.
Keep history when the confirmed date moves repeatedly. The latest promise supports daily operations, but the gap from the first commitment is valuable for supplier performance analysis.
Use explicit statuses
Statuses should describe an operational situation and trigger action.
- Awaiting confirmation.
- Confirmed.
- Follow-up required.
- Late.
- Partially received.
- Received / closed.
Build a follow-up logic
Do not chase every order at the same frequency. Prioritise lines approaching the due date without confirmation, items with declining inventory coverage and already late orders with operational impact.
A follow-up should request a precise answer: confirmed quantity, firm date, tracking number, explanation for a discrepancy or recovery plan. Generic messages often generate generic answers.
Automate without losing context
Alerts can identify a deadline, but the buyer still needs to interpret business criticality and impact.
Highlight exceptions instead of reading every line
The main view should not be a list of thousands of records. Use filters, priorities or dedicated views to expose late orders, missing confirmations, quantity gaps, partial receipts and repeated date changes.
A supplier-level summary also supports review meetings by showing open orders, delays, outstanding commitments and recurring issues in one place.
Useful indicators
A few measures are enough to monitor the open portfolio.
- Number of late lines.
- Value or quantity at risk.
- Unconfirmed orders.
- Delays by supplier.
- Age of open purchase orders.
Keep tracking reliable over time
Define who updates each field and when. Stale information is sometimes more dangerous than missing data because it creates false confidence.
Reconcile the tracking view with the ERP and close completed lines. Analyse recurring causes so the process improves rather than simply recording the same emergencies. Good order tracking should gradually reduce the number of surprises it reports.
Common mistake to avoid
Using the tracker only as an archive. Its main value is the clearly identified next action for every exception.
Implementation checklist
Before considering the topic under control, check these points in your procurement process.
- Data centralised.
- Statuses defined.
- Dates separated.
- Exceptions filtered.
- Next action recorded.
Continue with related procurement guides
Conclusion
Reliable procurement combines coherent parameters, current information and the ability to prioritise exceptions. Use this method as a working framework: adapt thresholds and indicators to your context, measure results and improve the rules progressively instead of managing only through emergencies.