.png)
Purchase order management is one of the most manual, error-prone workflows in a manufacturing or distribution operation. POs go out by email. Confirmations come back whenever the supplier gets to them. Approval chains happen in email threads. Delivery date changes arrive as one-line replies that nobody files consistently. By the time an order is received, there are four different places the PO status might live, and none of them fully agree.
This post walks through how to automate each stage of the PO workflow using n8n as the orchestration layer, with Retool for internal-facing approval interfaces and Google Cloud Functions for any custom business logic.
A standard purchase order workflow has four stages where manual work concentrates:
Most operations have manual steps at every one of these. Automating them in sequence produces compounding time savings. Automating even one stage delivers immediate ROI.
The manual version: A buyer creates a PO in the ERP or a spreadsheet template, emails it to a manager for approval, waits for a reply, and then sends it to the supplier once approved. For high-value POs, it might go to two or three people.
The problems are predictable: approvals sit in inboxes, approval chains are inconsistent, and there's no central record of what was approved, by whom, and when.
The automated version:
The trigger is a PO created or submitted for approval in the ERP. n8n picks this up via a webhook or a scheduled API poll of the ERP's pending-approval queue.
The workflow then applies routing logic:
For approval routing that requires a human interface, a Retool app provides a simple queue: the approver sees all pending POs, the key details, and approve/reject buttons. When they act, Retool writes back to the ERP via API, and n8n picks up the status change to continue the workflow.
For complex approval logic (tiered approvals, department-specific rules, escalation after a time threshold), a Google Cloud Function handles the routing decision and passes the result back to n8n.
What this replaces: Email chains, approval delays, inconsistent routing, and no audit trail.
What you get: A consistent, logged approval process with a clear interface for approvers and automatic escalation if approvals aren't acted on within a defined window.
The manual version: After approval, someone exports the PO from the ERP, attaches it to an email, and sends it to the supplier. Then they wait. A follow-up email goes out if there's no response. Confirmation arrives in an email that may or may not get filed back against the PO in the ERP.
The automated version:
Once a PO is approved (either auto-approved or manually approved in the Retool interface), n8n triggers the send step automatically:
For confirmation tracking, n8n runs a daily check against open POs that haven't received a confirmation within the expected window. Any PO without confirmation after a defined number of days triggers a follow-up notification to the buyer, plus an internal alert if the PO is flagged as critical.
When a supplier confirmation arrives, either via API response, email parsing, or a supplier portal webhook, n8n updates the PO status in the ERP and logs the confirmed delivery date.
What this replaces: Manual send, email follow-up, and the disconnected confirmation tracking spreadsheet.
What you get: A fully logged PO send and confirmation process. Every PO has a record of when it was sent, how, and when confirmation was received.
The manual version: The supplier emails to say a delivery date has changed. Someone reads the email, updates the ERP manually, and notifies the planning team. Except sometimes they don't, because it came in during a busy week and got buried.
Date changes that don't make it into the planning system cause downstream problems: production schedules based on wrong receipt dates, customer commitments that can't be met, expediting costs when the gap is discovered late.
The automated version:
For suppliers with APIs or EDI connections, n8n polls for order status updates on a defined schedule, compares against the confirmed delivery date in the ERP, and flags any changes automatically.
For suppliers that communicate by email, an email parsing integration (using n8n's email trigger combined with pattern matching or an AI parsing step) can detect date change language in incoming supplier emails and flag them for human review rather than letting them sit unread.
When a date change is detected:
What this replaces: Manual email reading, manual ERP updates, and the delayed discovery of date changes.
What you get: Delivery date changes surface immediately, go into the ERP in real time, and notify the right people before they affect downstream commitments.
The manual version: Goods arrive. Someone in the warehouse enters a receipt in the WMS or ERP, matching quantities against the original PO. Discrepancies get noted and someone follows up with the supplier. This often happens at day's end or not until the next morning, which means the inventory counts in the system are behind the physical inventory for hours at a time.
The automated version:
When a receipt is entered in the WMS, n8n triggers a reconciliation check immediately:
For multi-location operations, the receipt in one location triggers an inventory update across all connected systems simultaneously, not sequentially through a manual sync.
What this replaces: Delayed manual reconciliation, inconsistent discrepancy logging, and the lag between physical and system inventory.
What you get: Real-time inventory accuracy, immediate discrepancy alerts, and a complete receiving record tied to each PO.
Putting all four stages together, an automated PO workflow looks like this:
Reorder threshold reached in ERP
↓
Draft PO generated automatically
↓
Routing logic applied (auto-approve or route to approver)
↓
Approver acts in Retool interface (if required)
↓
PO sent to supplier automatically
↓
Confirmation received and logged
↓
Delivery date monitored; changes flagged in real time
↓
Receipt entered in WMS
↓
Reconciliation check runs automatically
↓
PO closed or discrepancy routed for follow-up
Each step happens without a person moving data between systems. People are involved at the decision points: approving a high-value PO, reviewing a discrepancy, handling a supplier relationship issue. The logistics of the workflow run automatically.
If you're starting from zero, don't try to automate all four stages at once. The highest-ROI starting point for most operations is the approval routing stage, because:
The second priority is usually the receiving and reconciliation stage, because the inventory accuracy improvement has direct downstream value for customer commitments and production planning.
Stages two and three (sending and date monitoring) tend to vary more by supplier mix. If most of your suppliers have APIs, those stages automate cleanly. If your supplier communication is primarily email-based, the email parsing approach requires more configuration.
Start where the volume and the pain are highest. Build that. Measure it. Move to the next one.
.png)
