Fixed quote after a free call

Purchase order follow-up that keeps jobs on schedule

A job is only as on time as its slowest material. We build a workflow that reads open purchase orders from the ERP, asks suppliers to confirm, records promised dates, chases deliveries that are slipping against the job they feed, requests material certificates before receipt and gives buyers a daily at-risk list. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why late supplier deliveries surprise planning

Buyers place dozens of POs a week and then spend hours chasing: did the supplier confirm, is the date still good, will the certs come with the material. Answers arrive in different inboxes and are rarely updated in the ERP.

When a late delivery is found at the last moment, planning reshuffles and customers get bad news. Supplier emails are also where payment fraud starts, so any change to bank details needs a careful, human check.

What we build

What our purchase order follow-up includes

PO confirmation requests

New POs sent with a request to confirm price, quantity and date, with replies captured.

Promised dates recorded

Confirmed dates written back to the ERP where the API allows, or to a shared tracker.

Risk against job dates

Each open PO compared with the job or sales order it feeds, so buyers see which lateness matters.

Polite chasing

Reminders before and after due dates, then a task for the buyer to call.

Certificate requests

Material certs and CoCs requested before shipment and filed against the PO on arrival.

Bank-change hold

Any supplier email mentioning new bank details is held and flagged for phone verification.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    PO placed

    A new purchase order in the ERP triggers a confirmation request.

  2. 02 Automated

    Reply captured

    Supplier confirmations and promised dates are read and recorded.

  3. 03 Automated

    Risk checked

    Promised dates are compared with job dates and slipping POs are chased.

  4. 04 Office review

    Buyer acts

    Buyers call at-risk suppliers and agree recovery.

  5. 05 Estimator or quality manager decides

    Sourcing decisions

    Changing suppliers, expediting or accepting substitutes is decided by purchasing and operations.

How it behaves

How supplier chasing behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What suppliers see

  • A clear confirmation request with each PO
  • A polite reminder before the due date
  • Certificate requests ahead of shipment

What buyers see

  • A daily at-risk list linked to job dates
  • Promised dates recorded without retyping
  • Bank-detail changes held for a phone check

What the automation does

  • Sends requests and reads replies
  • Compares promised dates with job dates
  • Never changes payment details or places orders

Edge cases and fallbacks

Supplier replies with a partial shipment
Split dates recorded and the buyer alerted.
Reply is unclear
Sent to the buyer unsorted rather than guessed.
Email mentions new bank details
Held and flagged for phone verification.
ERP or mailbox outage
That day's run is retried and buyers are alerted.

Architecture

Supplier PO follow-up at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
ERP Open POs, jobs n8n schedule Daily check Supplier emails Confirm, chase Reply reading Dates, certs Buyer At-risk list PO tracker Dates, certs
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 Each day the workflow reads open POs and the jobs they feed from the ERP.
  2. 2 Suppliers get confirmation requests and reminders.
  3. 3 Replies are read for promised dates and certificates, and bank-detail changes are held.
  4. 4 Buyers get a daily at-risk list, and dates and certificates are recorded.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Supplier PO confirmations & delivery chasing project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Buying process, supplier mix, ERP PO data and certificate requirements.

  2. 02

    Design

    2 to 3 days

    Request wording, chase timing, risk rules and the bank-change rule.

  3. 03

    Build

    1 to 2 weeks

    Requests, reply reading, risk list, cert filing and ERP updates.

  4. 04

    Shadow run

    About 1 week

    Requests go to a test inbox while buyers compare against their own chasing.

  5. 05

    Launch

    1 to 2 days

    Switch on for the main suppliers first.

  6. 06

    Support

    Ongoing

    New suppliers and rule changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Your ERP API (Business Central, Epicor, SAP Business One, Katana) Microsoft Graph or Gmail API Claude, Gemini or OpenAI for reply reading SharePoint or Google Drive for certificates

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Buying process, wording and risk rules.

    $200 – $450

  • Build

    Requests, reply reading, risk list and cert filing.

    $500 – $1,250

  • Integrations

    ERP, mailbox and document storage.

    $150 – $400

  • Testing and shadow run

    Comparison with buyers' own chasing.

    $100 – $250

  • Launch and training

    Switch-on and buyer walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Supplier portal integrations may need a second workflow. AI usage and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; small per supplier reply.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Supplier bank-detail changes

IC3 recommends verifying changes to bank deposit information and phoning requesters before acting on emailed payment requests, with a second person approving transfers.

Source: www.ic3.gov

EU: certificates for CE-marked products

Manufacturers keep technical documentation and the EU declaration of conformity for at least 10 years after a product is placed on the market, so supplier certificates are filed where they can be found.

Source: europa.eu

EU and UK: supplier contacts

Supplier contact names and emails are personal data under GDPR and UK GDPR, used only for purchasing.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Supplier PO confirmations & delivery chasing questions, answered.

It asks suppliers to confirm each PO, records promised dates, chases deliveries that are slipping against the jobs they feed and collects certificates, so buyers only call when it matters.

Yes. We agree the wording with your buyers, and every message comes from your purchasing mailbox.

Where the ERP API allows updating PO lines, yes, after the reply is read. Otherwise dates go to a shared tracker linked to the PO.

Any reply mentioning new bank or payment details is held, flagged and never forwarded to accounts payable as an instruction. Your team verifies by phone using a number already on file.

It sits on top of your ERP's purchasing module rather than replacing it, adding the chasing and visibility most modules lack.

Share of POs confirmed within two days, on-time delivery by supplier, at-risk POs caught before the job date and certificates received before material arrives.

Free 20-minute call

Want this for your manufacturer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call