How to Track Overdue Purchase Orders
An overdue purchase order is not a spreadsheet colour. It is open quantity you still need, past the date you were promised, while the floor plans as if the lorry is coming. Miss the pattern and Low stock grows, Transfers get raised in panic, and customers hear “tomorrow” for a week.
VORQ Analytics tracks overdue Purchase orders so operations can see which sent and partially_received orders still have outstanding quantity after the expected delivery date. This article turns that signal into a review routine you can run every week.
Answer first
Every open PO needs an expected delivery date. Treat missing dates as defects. Each week, review overdue sent and partially_received orders, chase suppliers with facts, update dates or cancel dead lines, and protect the Storage site that is waiting. Do not close overdue orders just to tidy a list.
What “overdue” means here
A purchase order is overdue when:
- Status is sent or partially_received (still open for inbound),
- Outstanding quantity remains,
- Expected delivery date is before today.
Draft or fully received orders are a different problem. Overdue tracking is about promises that slipped while stock is still owed.
For how Purchase orders and Receive stock fit together day to day, use the product guide at Purchase orders. For short deliveries that leave a balance open on purpose, see how to receive a partial purchase order.
Original asset: weekly overdue PO review checklist
| Step | Check | Pass rule | If it fails |
|---|---|---|---|
| 1 | Open Analytics / overdue Purchase orders view | List loads with destination Storage site visible | Fix filters before chasing suppliers |
| 2 | Missing expected delivery dates on open POs | Zero open POs without a date | Add a realistic date or park the PO as not yet committed |
| 3 | Overdue sent orders | Each has owner + last chase note | Call or email supplier same day with PO number and outstanding qty |
| 4 | Overdue partially_received orders | Outstanding lines match supplier backorder | Confirm remaining qty; do not invent a second PO |
| 5 | Impact on Low stock | Short SKUs linked to an open inbound or a Transfer plan | Raise Transfer from surplus site or revise customer promise |
| 6 | Date updates | New promised date written in the PO | Leave overdue visible until the date moves or stock arrives |
| 7 | Dead lines | Cancelled only when supplier confirms no shipment | Never close to “clean dashboards” |
Print or pin the table for the buying owner. A 20-minute Friday review beats a Monday morning dock surprise.
Routine detail: missing dates
Orders without an expected delivery date never become “overdue” in a useful way. They become fog. Rule: no Purchase order moves to sent without a date the supplier agreed, even if the date is soft. Soft dates still beat blank fields.
When you find blanks in the weekly review, fill them with the best known promise and mark the note “date estimated, confirm with Apex”. Analytics can then age the risk honestly.
Routine detail: partial receipts
Partial receipts are healthy when they tell the truth. PO-4821 ordered 100, received 60, status partially_received, outstanding 40. If the expected date for the remaining 40 has passed, that order belongs on the overdue list even though some stock already sits on the shelf.
Common failure: the team celebrates the 60 and forgets the 40 until Low stock fires again. The overdue review exists to stop that amnesia. Receive the next drop against the same PO via Receive stock, following your warehouse receiving SOP.
Supplier follow-up that works
- Lead with PO number, SKU, outstanding quantity, original expected date, and destination Storage site.
- Ask for a new date in writing. Update the PO the same day.
- If the supplier splits the remainder, keep one PO when possible and note the split dates. Two open POs for one backorder double the chase work.
- If the line is dead, cancel outstanding quantity and fix Low stock with a Transfer or a replacement supplier order.
Measure patterns, not one late van. How to measure supplier delivery performance turns overdue counts and missing ETAs into a simple scorecard.
Protect the warehouse while you chase
- Check Low stock for SKUs on overdue POs. Decide whether to Transfer from another Storage site.
- Do not let pickers “borrow” unlabelled inbound that has not been received.
- If customer orders depend on the late PO, change the promise early. Silence is worse than a revised date.
- Keep Stock counts honest on the short SKUs so you are not chasing a supplier for stock you already hold under a wrong bin.
Roles for a small team
One person owns the overdue list. Warehouse leads own Receive stock quality. Managers own the call when a chronic overdue supplier needs replacing. In a five-person warehouse those roles overlap, but the checklist still needs a named owner each week.
For broader purchasing context inside a WMS, see what a warehouse management system is. To run overdue visibility in VORQ, open signup or compare pricing.
Tracking overdue Purchase orders is a habit: dates on every sent order, weekly review of late and partially_received balances, and supplier follow-up that updates the system the same day. Analytics surfaces the list. The checklist turns it into action.
