Automate supplier PO acknowledgements and ETA tracking, with a buyer on every change
Updated · By Ecomsellertool editorial team
To automate purchase order acknowledgement and ETA tracking, log every PO the moment it is sent and start a clock. Rules chase suppliers who have not confirmed, compare each confirmation with the PO line by line, and hold any change to quantity, price or ship date for a buyer. Each new ship date becomes an arrival ETA that updates receiving and flags SKUs that would run out first.
- This recipe covers the stretch between a PO being sent and the goods being received: confirmations, changes, ETAs and chasing.
- The X12 standard has separate transaction sets for a purchase order (850), the seller's acknowledgment (855), a ship notice (856) and buyer- and seller-initiated PO changes (860 and 865).
- Shopify's purchase order help says to mark a PO as Ordered after your supplier confirms, and that the change cannot be undone (checked October 19, 2026).
- QuickBooks Online shows a PO as Overdue when its due date passes without the items received, and drafts a reminder you can edit and send; POs need the Plus or Advanced plan.
- Xero lets you update a purchase order's delivery date as things change, and shows which orders are sent, filled, billed or still open.
- In this recipe rules detect every change, an AI model only reads supplier emails into fields, and a buyer accepts or rejects anything that differs from the PO.
The step map: who runs each step
Trigger: A purchase order is sent to a supplier; after that, every supplier email, EDI acknowledgment or ship notice about that PO, plus a daily check of open POs.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | When a PO is sent, the workflow logs it as Sent with the PO number, supplier, lines, prices and requested ship date, and starts the acknowledgement clock for that supplier. | Rule |
| 2 | Supplier replies to the PO thread, portal updates and EDI 855 acknowledgments or 856 ship notices are collected and tied to the PO number. | Rule |
| 3 | For email and PDF replies, an AI model reads the confirmed quantity, unit price, ship date and any comment per line into fields with a confidence score. It never accepts a change. | AI model |
| 4 | Rules compare each confirmed line with the PO: quantity, unit price, currency, ship date, SKU or substitute. Lines that match are marked Confirmed; any difference sets the PO to Changed by supplier with both values shown. | Rule |
| 5 | A buyer accepts or rejects each change, or answers the supplier, and the accepted values are written back to the PO in your purchasing system. | Person |
| 6 | Every confirmed or revised ship date is turned into an arrival ETA with the lane's transit and receiving days, and the ETA slip is calculated against the date the plan was built on. | Rule |
| 7 | Suppliers who have not confirmed, POs whose ship date has passed with no ship notice, and ETAs that slipped past your tolerance get a reminder or an alert on a fixed schedule. | Rule |
| 8 | The new ETA updates expected receipts for the warehouse or 3PL and the open-PO dates your reorder plan reads, and SKUs whose stock now runs out before the goods land go to the buyer. | Rule |
6 rule steps · 1 AI model step · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Accepting or rejecting a change to quantity, unit price, currency or ship date
- Substitute SKUs, split shipments and short shipments the supplier proposes
- Escalating a supplier who stays silent after the last reminder
- SKUs whose new ETA lands after they run out: expedite, buy elsewhere or slow sales
- Cancelling a PO or a line
Which tools can run it
- Your accounting system's own PO tools, such as QuickBooks Online's overdue reminders or Xero's delivery date, for a few suppliers
- Zapier, Make or n8n reading the PO inbox with an AI step and writing to a PO tracker sheet, for steady volume with email-only suppliers
- An EDI provider for 855 and 856 messages, when large suppliers already trade on EDI
- Custom code on your accounts, for many suppliers mixing email, portals and EDI, with ETAs feeding receiving and replenishment
Systems it connects
- Purchasing system, ERP or Shopify purchase orders
- Shared PO inbox (email and PDF replies)
- EDI 855 and 856, or supplier portals
- QuickBooks Online or Xero
- Warehouse, 3PL or prep center expected receipts
- Replenishment plan or reorder sheet
- Slack or email for alerts
Build size: Medium
Each check is simple; the work is tying every reply to the right PO line and keeping one clean status per PO across email, portals and EDI.
A purchase order that has been sent is not stock on the way. Between the two sit the supplier's confirmation, the changes it brings, a ship date that moves twice, and a buyer who learns about the delay when the warehouse asks where the goods are. This recipe automates that stretch: from the moment a PO is sent until the goods are received. It starts where our low-stock alerts and draft purchase orders recipe ends, and every decision that changes what you buy stays with a buyer. It is one page of our automation library.
Which statuses should a purchase order move through after it is sent?
This table is the core of the build, and you can run it today from a spreadsheet. Each row is one state of an open PO, the rule that puts it there, what the workflow does on its own and who acts. The day counts are illustrative; set your own per supplier and write them down, because the rules apply them exactly.
| PO state | Rule that sets it | What the workflow does | Who acts |
|---|---|---|---|
| Sent | PO emailed, uploaded to the portal or sent as an EDI 850 | Logs PO number, lines, prices, requested ship date; starts the acknowledgement clock | Nobody yet |
| Awaiting acknowledgement | No reply tied to the PO after the supplier's reply window (for example 2 business days) | Sends a polite reminder in the same thread, with the PO attached | Nobody yet |
| No response | Still no reply after the second window (for example 4 business days) | Alerts the buyer with the PO, both reminders and the supplier contact | Buyer calls or escalates |
| Confirmed | Every line matches the PO on quantity, unit price, currency and ship date | Marks the PO confirmed, sets the arrival ETA, updates expected receipts | Nobody |
| Changed by supplier | Any line differs: fewer units, a new price, a later date, a substitute SKU | Holds the PO with old and new values side by side; nothing downstream changes yet | Buyer accepts or rejects each change |
| Partly confirmed | Some lines confirmed, others not answered or back-ordered | Confirms the answered lines, keeps chasing the rest as a separate clock | Buyer decides on back-orders |
| Ship date due | The confirmed ship date is today or tomorrow | Asks the supplier for the ship notice, tracking or booking reference | Nobody yet |
| Late to ship | The ship date passed with no ship notice (EDI 856, packing list or tracking) | Alerts the buyer, recalculates the ETA from today and flags SKUs at risk | Buyer chases or expedites |
| In transit | Ship notice or tracking received | Sets the ETA from the ship date plus the lane's transit and receiving days; tells the warehouse what to expect | Nobody |
| ETA slipped | A new ETA is later than the planned arrival by more than your tolerance (for example 3 days) | Recomputes stockout risk per SKU and sends the at-risk list | Buyer decides: expedite, split, buy elsewhere or slow sales |
| Received | The warehouse, 3PL or prep center reports the receipt | Closes the tracking clock and records actual lead time for each leg | Receiving differences go to the person who handles them |
| Cancelled | A buyer cancels the PO or a line | Stops reminders, removes the units from the open-PO position | Buyer only |
Two states do most of the work. Changed by supplier is where money and dates move, so it always waits for a person. ETA slipped is where stockouts start, so it always says which SKUs are affected, not only which PO.
How does a supplier's confirmation get checked against the PO?
Line by line, field by field. The confirmation can arrive four ways, and the workflow treats them the same once the fields are read.
| How the supplier replies | How the fields are read | What to watch |
|---|---|---|
| Email reply or PDF | An AI model reads quantity, price, ship date and comments per line, with a confidence score | Low confidence or totals that do not add up go to the buyer as unread, never as confirmed |
| Supplier portal | A scheduled export or API call | Portals often show a status without line detail; ask for the line export |
| EDI 855 acknowledgment | Parsed by your EDI provider into fields | Line-level accept, change or reject codes map straight to the table above |
| Phone or chat | The buyer records it on the PO | The workflow logs who entered it and when |
The X12 transaction set list names the 850 purchase order, the 855 purchase order acknowledgment, the 856 ship notice and manifest, the 860 buyer-initiated change request and the 865 seller-initiated change acknowledgment or request (checked October 19, 2026). Most small suppliers will never send these. They are still a useful model: an acknowledgment, a change and a ship notice are three different events, and your tracker should keep them apart even when they all arrive as email.
Once fields are read, the checks are plain rules. Quantity confirmed against quantity ordered. Unit price and currency against the PO. Confirmed ship date against requested ship date. SKU against the supplier item code on your product master, so a substitute shows up as a change rather than a match. A supplier who writes "confirmed" above a table with a new price has not confirmed your PO.
How do you turn a new ship date into an ETA, and when does a slip matter?
Every confirmed or revised ship date becomes an arrival date the warehouse and the reorder plan can use. Measure transit and receiving from your own past receipts per lane, not from the forwarder's quote.
Arrival ETA = confirmed ship date + transit days for the lane + receiving days at the destination
ETA slip (days) = new arrival ETA − arrival date the plan was built on
Days short = (new arrival ETA − today) − days of cover on hand and already inbound
A slip on its own is not an emergency. A SKU with 90 days of cover can absorb a two-week slip. The third formula is the one that decides who gets an alert: when days short is above zero, the SKU will run out before the goods land. Here is how it reads for an illustrative PO; the numbers are examples, not client data.
| SKU (illustrative) | Days of cover today | Old ETA | New ETA | Days until new ETA | Days short | What happens |
|---|---|---|---|---|---|---|
| Tumbler 20 oz | 41 | Day 30 | Day 44 | 44 | 3 | Sent to the buyer as at risk |
| Lid set | 70 | Day 30 | Day 44 | 44 | 0 | Logged; no alert |
| Straw pack | 12 | Day 30 | Day 44 | 44 | 32 | Sent to the buyer first |
Days of cover here counts stock in every location plus units already in transit from earlier POs, the same position the reorder point uses. When a SKU is short, the choices are the buyer's: ask the supplier to ship that line first, split it by air, buy a top-up elsewhere, or let ads ease off it, which is what our inventory-aware ad spend page covers.
What does the workflow update when an ETA changes?
Three places, and only after any supplier change has been accepted. First, the open-PO date in your purchasing system, so the next reorder run counts the units on the right day. Second, expected receipts at the warehouse, 3PL or prep center, so receiving staff and dock slots match reality. Third, the actual lead time per leg once goods arrive, which keeps future reorder points honest. Our replenishment page explains why lead time has to be measured leg by leg.
Where those dates live depends on your tools. Shopify's purchase orders help says to mark a PO as Ordered after your supplier confirms, and receiving happens on a linked inventory transfer. Its guide to creating purchase orders adds that marking as Ordered cannot be undone, while most PO details can still be edited afterward (both checked October 19, 2026). That makes "mark as Ordered" a natural step to tie to an accepted confirmation.
QuickBooks Online's purchase order article says POs are available only on the Plus and Advanced plans, shows a PO as Overdue when its due date passes without the items received, and drafts a reminder you can edit before sending. Xero's purchase orders page says you can update a PO's delivery date as things change and see which orders are sent, filled, billed or still open (both checked October 19, 2026). If you have a handful of suppliers and these built-in tools cover your POs, they are the better choice.
What should stay with a person?
Anything that changes what you are buying or what you will pay. The workflow chases, reads, compares and recalculates; a buyer accepts a lower quantity, a new price, a later date or a substitute. A buyer also decides what to do about a SKU that will run out before its goods arrive, and when a silent supplier needs a phone call rather than a third email. The model only turns emails into fields. It never marks a line confirmed on its own judgment, and low-confidence reads come to a person unread.
Which tool should run it?
| Level | Fits when | What to know |
|---|---|---|
| QuickBooks Online or Xero on their own | A few suppliers, POs already raised there | Overdue reminders and delivery dates exist, but no line-level check of confirmations and no link to stock |
| Zapier, Make or n8n with an AI step and a tracker sheet | Steady volume, suppliers who reply by email | Our Zapier vs Make vs n8n comparison covers the trade-offs; log every run so a missed email shows up |
| An EDI provider | Large suppliers already trade on EDI | Covers 855 and 856 cleanly; email suppliers still need the other path |
| Custom code on your accounts | Many suppliers mixing email, portals and EDI; ETAs feeding receiving and replenishment | Can run on Ecomsellertool Growth OS beside the reorder plan and inventory flows |
Once goods for FBA arrive at your prep center, our FBA inbound shipment from an approved PO recipe builds the inbound plan. When the supplier's invoice for the same PO arrives, our supplier invoices to bills recipe matches it to the PO and the receipt before anyone pays it.
Who builds this for ecommerce brands?
Ecomsellertool builds purchasing workflows like this on your own accounts and systems. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. We start with how each supplier replies today and where your POs, receipts and reorder plan live, then build the tracker, the checks and the alerts. Send a project brief below, or read how our workflow automation service works.
The building blocks are work we have shipped:
- Lead times and purchase orders in one inventory module. For Cutting Edge we built Asinwiser, an Amazon tool whose inventory module forecasts stock needs from sales velocity, lets users adjust vendor lead time, outbound lead time and days of stock, and creates purchase orders inside the platform.
- Updates that arrive as events, not overnight. For Beezboard we used SQS for real-time updates on order activity, the same event-driven pattern this workflow uses for supplier replies and ship notices.
You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you.
Get this workflow built
Send us your version of this workflow
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
What is a purchase order acknowledgement?
It is the supplier's reply that accepts your purchase order and confirms what it will ship: quantities, prices and the ship date. It can be an email, a PDF, a portal update or an EDI 855 message. Until you have it, the PO is a request, not a commitment, so your plan should treat its dates as unconfirmed.
How do I track supplier ETAs automatically?
Log each PO when it is sent, collect every supplier reply against the PO number, and turn each confirmed ship date into an arrival ETA by adding the lane's transit and receiving days. A daily check then flags POs with no confirmation, ship dates that passed without a ship notice, and ETAs that slipped past your tolerance.
How long should I wait before chasing a supplier who has not confirmed a PO?
Set it per supplier from how fast they usually reply, then write it down so the rule applies it exactly. For example, a brand might send a first reminder two business days after the PO and alert the buyer after four. These numbers are illustrative; time zones, holidays and the supplier's own habits matter more than any default.
Should the workflow accept a supplier's changed ship date or price?
No. A change to quantity, price, currency or ship date changes what you are buying, so the workflow shows the old and new values side by side and a buyer accepts or rejects it. Only accepted values update the PO, the ETA and the reorder plan.
What is an ETA slip and why does it matter?
It is the number of days the expected arrival moved from the date your plan was built on. A slip only matters if the SKU runs out before the new date, so the workflow compares the new ETA with each SKU's days of cover and sends the ones at risk of a stockout to the buyer first.
Do I need EDI to automate PO acknowledgements?
No. Most smaller suppliers confirm by email or PDF, and an AI model can read those replies into fields for rules to check. EDI makes the data cleaner when large suppliers already use it, through the 855 acknowledgment and 856 ship notice, so many brands run both side by side.
