n8n workflows by department 4 min

Supplier delays: spot them before the customer does

An n8n supplier tracking workflow reads open orders every day, compares the promised delivery date with what has been confirmed or shipped, chases the silent supplier and warns the buyer, then the salesperson, as soon as a delay threatens a customer order. The buyer keeps the negotiation and the choice of a fallback.

Contents6
  1. 01Why delays are discovered too late
  2. 02What the workflow watches
  3. 03Linking the delay to the customer who is waiting
  4. 04What stays with the buyer
  5. 05What the history teaches you
  6. 06Frequently asked questions

A supplier delay almost always follows the same script. The order is placed, the date is promised, then nothing. Nobody checks that the confirmation has arrived, or that the goods have been shipped. On the expected day, the goods are missing, and it is the customer who calls to ask about their own order. The buyer learns about the delay when there is no room left to act.

The delay itself cannot always be avoided. Finding out about it late can. This article is part of the n8n workflows: what each department can automate series, purchasing and logistics sections.

In short

  • Every supplier order has a promised date, recorded somewhere.

  • The workflow checks every day whether the confirmation and the shipment have arrived.

  • A silent supplier gets an automatic reminder, before the date.

  • A delay that affects a customer order warns the buyer and the salesperson.

  • Negotiation and the fallback stay human.

Why delays are discovered too late

The buyer follows dozens of open orders. They cannot check each one every day, and they rely on silence: no news is good news. Yet a supplier’s silence is often the first sign of a problem. The confirmation that never comes, the missing shipping notice the day before the promised date: these signals exist, but nobody reads them in time.

What the workflow watches

Tracking a supplier order

  1. The order

    The promised date is recorded in the ERP or the purchasing spreadsheet.

  2. The confirmation

    Without an acknowledgement within a few days, an automatic reminder goes out.

  3. The shipment

    As the date gets closer, the workflow looks for the shipping notice.

  4. The alert

    If nothing is in sight, it warns the buyer and the salesperson involved.

The daily check relies on the n8n schedule trigger. The workflow reads open orders, compares them with the messages received from suppliers (emails, portals, carrier tracking), and sorts each order: on track, to watch, late.

Reading supplier messages is where a language model can help. A supplier rarely replies in a fixed format: they write “delivery moved to next week” in the middle of an email. The AI spots the new date and suggests it; the buyer confirms it in one click before it replaces the promised date.

Linking the delay to the customer who is waiting

An isolated alert

  • The buyer knows an order is late

  • They do not know which customer is affected

  • The salesperson hears about it from the customer

A linked alert

  • The buyer sees the customer orders affected

  • The salesperson is warned at the same time

  • The customer gets a new date before asking for it

This is the real gain. A supplier delay only matters because of what it holds up for the customer. When the ERP links the supplier order to customer orders (as Odoo and Dolibarr do for stocked products), the workflow knows who to warn. Without that link, you need at least a shared reference, entered with the order. For the customer side, see shipping updates sent to the customer.

What stays with the buyer

The workflow alerts, it does not negotiate. Calling the supplier, getting a partial delivery, finding a fallback with another supplier, deciding whether to warn the customer straight away or wait for confirmation: these choices require knowing the relationship, the margins and the priorities. The article AI in operations and logistics covers this split between tooled anticipation and human decision.

Tracking delays also works better with a clean purchasing circuit. With tracked purchase requests, every order has its promised date from the moment it is created, and nothing escapes the check.

What the history teaches you

After a few months, the workflow has recorded, for each supplier, the gap between promised date and actual date. This record, drawn from your own orders, is a solid basis for negotiation, and an objective criterion for choosing between two suppliers. It stops you judging on the last incident, which sticks in the mind more than twenty deliveries on time.

To set up this tracking on your ERP or purchasing spreadsheet, our n8n automation offer starts with today’s open orders and the suppliers that cause problems.

Frequently asked questions

Do suppliers need to change their habits?

No. The workflow reads what suppliers already send: confirmation emails, shipping notices, carrier tracking links. Some suppliers have a portal or an API, which it queries directly. The others keep writing as before. The only reasonable request to make is that they quote your order number in their messages.

What about a supplier who never confirms?

The workflow chases them automatically, then warns the buyer once the set time has passed. The history then shows whether this silence is usual. That is useful for the relationship: you can ask the supplier for a systematic confirmation, or take it into account when choosing suppliers. The workflow makes the problem visible; the decision stays with the buyer.

Does this tracking make sense without an ERP?

Yes, as soon as supplier orders are recorded somewhere with a promised date: a shared spreadsheet is enough. The workflow reads that spreadsheet as it would read an ERP. The link with customer orders will be more manual, through a shared reference, but the alert before the date remains the main gain.

Sources

  1. Schedule Trigger, n8n documentation (new tab)docs.n8n.io
Source 1

Schedule Trigger, n8n documentation

Read on docs.n8n.io(new tab)

Jim · founder of Brain Plus AI

Also in n8n workflows by department

  • Practical guide5 min The topic guide

    n8n workflows: what each department can automate

    Accounting, sales, HR, support, purchasing, marketing, logistics, management: every department has tasks that travel from one tool to another. Here, department by department, are the n8n workflows that save time, and those that are not worth the effort.

  • Practical guide4 min

    Purchase requests: an approval circuit in n8n

    Without a circuit, a purchase request is approved in a corridor and discovered on the invoice. An n8n workflow gives a single entry point, clear approval thresholds and a record, even without an ERP.

  • Practical guide4 min

    Shipment tracking: update the customer before they call

    After an order, a large share of customer service requests ask a single question: where is it? An n8n workflow sends the good news at the right time, and above all the bad news before the customer finds it out.

WhatsApp