Blog Workflow Automation Guides
Check purchase order delivery dates
Give a Midpoint worker your open purchase-order lines. Get delivery quantities, current supplier estimates and unresolved matches in one comparison.

Renee Park coordinates purchasing at an industrial parts distributor. Her open-order sheet has one requested date per purchase order. A supplier's split delivery now has 400 fittings estimated for November 12 and 200 for December 3. The sheet still says "November 14" for all 600.
Every Monday she has to find out which quantities are expected to arrive late. She gives that check to her Midpoint worker: "Check these open purchase order lines against the supplier pages I've given you access to. For each line, compare my requested date with every delivery the supplier shows. Tell me which lines and quantities are due after my requested date, where you read it, and anything you couldn't match. Don't change any orders and don't contact any suppliers."
What comes back
The worker returns a comparison file with one row per delivery, plus a short note for the Monday review. The affected line and quantity come first:
PO 40718, line 3: 600 hydraulic hose fittings. We asked for all 600 by November 14. The supplier page, read on Monday, November 2 at 9:40 a.m., shows two deliveries. The first 400 are marked shipped, with delivery estimated for November 12. The other 200 are estimated for December 3, 19 days after our requested date. Our receiving record shows zero received. All 600 remain unreceived in our records, including the 400 marked shipped.
A single date on the sheet cannot say that. If the sheet were marked "November 12" it would hide the 200 due after the requested date. If it stayed on "November 14" it would hide the earlier estimate for the first 400. The worker gives each delivery its own row and checks that 400 and 200 add up to the 600 ordered.
It also keeps three things apart. The supplier's estimate is what the supplier says will happen. The shipped quantity is what they say has left. Our receiving record is what our team has recorded as received. Each has its own column and check time. If the receiving record logs a receipt against the whole line, the worker keeps it there and doesn't guess which delivery it belongs to. A supplier page that says "shipped" doesn't make the line received, and an estimate stays an estimate.
The line it couldn't match
The second item in the note is a question.
PO 40722, line 2: 24 gear pump seals, part GP-2210. I couldn't match this line. The supplier page has two seal lines, GP-2210 and GP-2210-B, and neither shows our PO line number. Both show 24 units. I haven't picked one. Which one is ours?
The worker records both possible matches and leaves the delivery estimate unverified. Renee can find the right supplier reference on the order confirmation. Until she does, the line stays on the questions list. The worker doesn't treat GP-2210-B as a substitute part, and nothing on the order changes.
Other matched lines keep their estimated dates and check times in the comparison too. A date on or before the requested date is still a supplier estimate.
Where your system already does this
Check what you have first. An ERP or supplier portal may already show purchase order lines, delivery schedules and history. Oracle's supplier-view documentation shows lines and schedules, with separate viewing and change privileges. If your suppliers all send their schedules into your system and someone reads the late-delivery report each week, you may not need anything else. A clean tracking spreadsheet is also enough for a short list that one person maintains.
The check becomes worth delegating when suppliers live on separate sites, each shows a schedule in its own way, and someone has to read them one by one. Other tools can do parts of that work, and some vendors sell supplier follow-up for each order line as a service. A Midpoint worker can take on the weekly comparison and return it where the purchasing team works. Tell it how often to check and where the results go.
What the worker needs
- The list. Attach a dated export of the open lines: supplier, PO number, line number, part, quantity, requested date and the quantity received so far.
- The sources. Name which supplier pages or exports the worker may read. Use a view-only login where the supplier offers one, because reading dates needs no permission to change an order. If a supplier has no view-only login, start with an export they send you.
- The limits. Read only. No changes to orders or receipts, and no messages to suppliers. Supplier follow-up and purchasing decisions stay with your team.
- What it asks about. A line it can't match, or a page it can't read, comes back as a question. Existing sheet values stay unchanged.
A worker with its own computer and browser can read supplier pages the way a buyer does, which matters when a supplier has no export. If you also watch what suppliers charge, the same read-only approach works for comparing prices over time.
Try it on this week's open lines
Share the dated open-line export and the receiving record. Connect the needed apps or save authorized view-only supplier logins. The worker matches supplier, PO and line references, sets up the comparison and returns the file in your private purchasing channel or ticket. Start with:
Compare the open lines in the attached export with the supplier delivery schedules on the pages I've shared. For each delivery, show its quantity, requested date, supplier estimate and shipped quantity. Keep what we've received in its own column, as our receiving record shows it. Show which quantities are due after the requested date, with supplier, PO, line, part, units, source links and check times. If you can't match a line, mark the estimate unverified and ask me. Don't change orders and don't contact suppliers.


