Skip to content

Purchasing and supplier follow-up

This playbook covers purchasing and supplier follow-up, which a distributor calls replenishment: placing purchase orders, checking supplier acknowledgments and chasing the lines that are late. It describes the work today, what our forward-deployed engineers build and who does what at each level of the autonomy ladder.

The ERP’s planning run produces a list of suggested purchase orders: from MRP at a manufacturer, from reorder points at a distributor. A buyer reviews the list and adjusts it for what the ERP does not know, such as a supplier’s real lead time, a price break or a truck that is not yet full. Then the buyer releases the purchase orders, and they go to suppliers by email as PDFs.

Then the follow-up starts. The supplier sends back an order acknowledgment, usually another PDF, with their own dates, quantities and prices. The buyer is meant to compare it with the purchase order and update the promise date in the ERP. Later the buyer exports the open purchase order report to Excel, sorts it by due date and emails or calls suppliers one by one to ask where things are.

This is where it goes wrong.

  • Acknowledgments pile up unread. The ERP keeps showing the date you asked for, not the date the supplier promised.
  • Planning, the production schedule and customer promises are built on those dates. The shortage is discovered at the dock or at the machine.
  • An acknowledged price that differs from the purchase order goes unnoticed until the invoice fails to match.
  • Chasing takes the hours a buyer would otherwise spend on sourcing and negotiating.
  • Who really answers at each supplier, and which supplier always runs a week late, is in the buyer’s head.

The work touches buyers, the planners and schedulers who depend on the dates, receiving and AP. The workflow owner is typically the purchasing manager.

  • Screens: an open-order view of every open purchase order line, with the date requested, the date acknowledged, the last contact with the supplier and what they said. A view that shows a supplier’s acknowledgment beside the purchase order, with the differences marked.
  • Queues: acknowledgments to check, fed from the purchasing inbox. Lines due for a follow-up. Exceptions for the buyer: date slips that put a job or a customer order at risk, price differences and quantity changes.
  • Rules: when a line gets a follow-up, such as no acknowledgment after an agreed number of days, a due date coming up on a long-lead item or a line past due. Which contact to write to, and how many times before the buyer takes over. How far an acknowledged date or price may differ from the purchase order before a person must see it. For purchase orders: approved suppliers, agreed prices, pack sizes and minimums.
  • Integrations: reads of purchase orders, receipts, planning suggestions and the demand each line supports. Write-backs: update the promise date on a purchase order line, so planning sees real dates, and, at the higher levels, release a purchase order.
Level What the agent does What people do
Level 0 (Recorded) Nothing yet. Buyers record each acknowledgment and each follow-up on a screen, not in a personal spreadsheet: the date confirmed, who was contacted and what they said.
Level 1 (Assisted) Reads supplier acknowledgments and replies and pulls out the dates, quantities and prices. Shows where they differ from the purchase order. Drafts follow-up emails for late and unacknowledged lines. Summarizes what changed since yesterday. The buyer sends the emails, updates the ERP and releases purchase orders as before.
Level 2 (Prepared) Prepares each promise-date update and each follow-up email in full. Prepares purchase orders from the planning suggestions, with quantities rounded to pack sizes and minimums. The buyer approves every update, every email and every purchase order.
Level 3 (Supervised) Sends routine follow-ups to suppliers on its list, inside its time windows. Updates a promise date when the supplier’s date is within the agreed tolerance. Releases purchase orders for repeat items from approved suppliers at the agreed price, under an amount limit. Buyers handle the exceptions: slips that cause a shortage, price and quantity changes, supplier questions. They spot-check a sample.
Level 4 (Autonomous) Owns follow-up and keeps the purchase order dates true. Buyers set the rules for who is chased, how often and when a person takes over. They audit a sample.

Treat this as two workflows with two ceilings.

  • Follow-up and date-keeping can reach Level 4. A wrong follow-up is a polite email sent a day early or to the wrong contact. That is cheap, visible and easy to correct. A wrong date in the ERP costs more, so a date change that puts a job or a customer order at risk still goes to a buyer.
  • Releasing purchase orders commits money. Level 3 with tight limits is a realistic ceiling for repeat items at agreed prices, and Level 2 is a fine place for it to stay.

Sourcing, negotiating, choosing a supplier and deciding to pay for expedited freight stay with your buyers at every level.

When the agent emails a supplier, it sends from an address your IT team sets up for this workflow, under a name and signature the workflow owner decides.

Exception Who it usually goes to
The supplier confirms a later date, and the material is needed for a job or a customer order Buyer, with the planner or scheduler
The acknowledged price differs from the purchase order Buyer
The acknowledged quantity differs: a pack size, a minimum or a partial shipment Buyer
No reply after the agreed number of follow-ups Buyer, by phone
The supplier replies with a question or a problem: a discontinued part, a substitute, a missing drawing revision Buyer
One line will arrive on several dates Buyer or planner
A reply that cannot be tied to a purchase order Buyer
A request to expedite that costs money Purchasing manager
  • Open purchase order lines with no acknowledgment, and lines with a promise date in the past.
  • How often the supplier’s date, quantity or price differs from the purchase order, by supplier.
  • Follow-ups sent and answered, and how many rounds each line took.
  • Promise dates in the ERP against the dates material arrived.
  • Shortages seen in advance against shortages found at the dock or the machine.
  • Price differences caught at acknowledgment against those caught at the invoice.
  • Hours buyers spend on follow-up.

These are things to measure, not targets. The threshold for each level is set with the workflow owner and written down before that level starts.