AI Supplier Management: Track Prices, Lead Times, and Risk

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Supplier Management: Track Prices, Lead Times, and Risk.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Supplier Management: Track Prices, Lead Times, and Risk.

AI reads your supplier invoices and order confirmations to build a line-by-line price history, compares each delivery date with the date you ordered to measure real lead times, and flags risks: prices rising beyond what you agreed, deliveries slipping, heavy reliance on one supplier, and notices of trouble. You keep a simple supplier register; AI fills it in and checks it monthly.

The hard part isn't the AI, it's matching. Suppliers rename products, change pack sizes and split one line into two between invoices. If "Coffee beans 1kg x12" becomes "House blend 10 x 1kg" and nobody links them, your price history breaks at exactly the moment the price per bag went up. A short mapping table, described below, fixes most of it.

Follow me on Instagram@sagnikteaches

Start with a supplier register, not a tool

Before any AI, list your suppliers in one sheet. Most small businesses have 10 to 40 that matter. For an illustrative 22-room boutique hotel, the register has 14 rows and these columns, shown with one filled-in row:

Connect on LinkedInSagnik Bhattacharya
ColumnLaundry supplier (example row)
SuppliesWashing of own linen and towels
Annual spendAbout $16,500
Share of that category100%
AlternativesTwo quoted last year; one is a hire service
Price termsPer item, fixed for 12 months from 1 October
Contract end and notice30 September; 60 days' notice
Promised lead timeBack within 48 hours
Measured lead timeFilled monthly (see below)
Delivered on time and in fullFilled monthly
Risk scoreFilled quarterly
OwnerHead housekeeper

The price terms and contract dates usually come from the quote or contract. If you went through a proper comparison when choosing the supplier, as in comparing supplier quotes side by side, most of this is already written down. A chat assistant can fill the rest from the documents: upload the contract and ask it to extract the price terms, review clauses, notice period and renewal date, with the clause number for each so you can check.

Subscribe on YouTube@codingliquids

Price histories built from invoices

Every invoice already contains the data. The job is getting line prices out and into one table. For a few dozen invoices a month, upload them to a chat assistant on a business plan once a month with a fixed format:

Extract every line from these supplier invoices into a table:
supplier | invoice date | invoice number | product as written | pack size |
quantity | unit price | line total
Copy text and numbers exactly as printed. If pack size isn't stated, write UNKNOWN.
Do not calculate anything. List any invoice you couldn't read fully.

Then paste the rows into a price-history sheet, one tab per supplier. For higher volumes, invoice-reading tools and accounting software extract the lines automatically; AI invoice processing for supplier bills covers those. A lightweight automation also helps: a two-step Zap on Zapier's free plan (100 tasks a month) can save every invoice attachment from a supplier's emails into one folder, so nothing is missed at month end.

The mapping table. Add a second tab listing every way each product has appeared on an invoice, and the one name you'll use:

As written on invoiceYour product nameUnits per pack
Coffee beans 1kg x12House coffee, 1 kg bag12
House blend 10 x 1kgHouse coffee, 1 kg bag10
Espresso Blend 1KG (case)House coffee, 1 kg bagUNKNOWN: ask supplier

AI is useful for proposing these matches ("which of these invoice lines look like the same product?"), but check each one. Two lines that look alike can be different grades at different prices.

Price creep: the rises nobody announced

With a price history per product, AI can flag changes. Ask it monthly to compare each product's latest price per unit with the previous invoice and with the agreed price, and to list anything that rose. Two illustrative finds from the hotel's first three months:

A pack-size change. The breakfast supplier's coffee went from a case of 12 bags at $186 to a case of 10 bags at $165. The case price fell by 11%, and nobody looked twice. Per bag, it rose from $15.50 to $16.50, an increase of about 6.5%. Only the mapping table's units-per-pack column made that visible.

An unannounced rise. The laundry's per-item price for bed linen went from $0.62 to $0.66 on the December invoice, although the quote fixed prices for 12 months. That's $0.04 on about 15,000 items a year, or $600, and it would have continued unnoticed. One email quoting the fixed-price clause reversed it and produced a credit note.

A sample output from the monthly check (illustrative):

PRICE CHANGES THIS MONTH (per unit, vs previous invoice)
Laundry  - Bed linen item   $0.62 -> $0.66  (+6.5%)  CONFLICTS with fixed price to 30 Sep
Produce  - Free-range eggs  $0.31 -> $0.34  (+9.7%)  no price terms on file
Produce  - Butter 250g      $2.10 -> $2.02  (-3.8%)
Coffee   - House coffee 1kg $15.50 -> $16.50 (+6.5%) pack size changed 12 -> 10

The "no price terms on file" note is the useful nudge: produce prices move constantly, which is normal, but it shows you have no agreement to hold them to. Decide which suppliers deserve one.

Which rises to challenge, and how to word it

Not every price change deserves an email. A rule of thumb keeps the monthly check from turning into an argument with every supplier:

  • Under 3% on a product with no fixed-price terms: note it and move on. Watch for the same product rising three months running.
  • 3% to 10%, or any rise from a supplier with review terms: ask for the reason and when the next review is due.
  • Over 10%, any rise that conflicts with agreed terms, or a pack-size change that hides a rise: challenge it, and if it isn't explained, get a comparison quote.

AI drafts these emails well if you give it the facts and the tone. A template:

Draft a short, friendly email to [supplier] about a price change.
Facts: [product], invoice [number] dated [date], price per unit changed from
[old] to [new]. Our agreed terms: [quote or "none on file"].
Ask them to [confirm the reason / apply the agreed price and issue a credit note].
No accusations. Under 120 words. Sign off as [name, role].

An illustrative result for the hotel's laundry query:

"Hello, a quick query on invoice 4471 dated 3 December. The bed linen price is shown as $0.66 per item; our quote of 12 September fixed it at $0.62 until 30 September next year. Could you check and, if it's an error, send a credit note for the difference on this and any other December invoices? Many thanks, [name], Head Housekeeper."

Specific, polite and impossible to misread. The credit note arrived within a week.

The yearly cost of creep nobody notices

Small rises feel too minor to chase, which is exactly why the annual total is worth working out once. The hotel's first quarter of monthly checks turned up three rises it hadn't agreed to or noticed:

  • Laundry: $0.04 per item on about 15,000 items a year, so $600.
  • Coffee: $1 more per bag through the pack-size change, on about 25 bags a month, so $300 a year.
  • Eggs: $0.03 per egg on about 9,000 eggs a year, so $270.

That's $1,170 a year from three products, before counting anything else on the invoices. Only the laundry rise broke an agreement, and only that one was reversed outright. But the egg rise prompted a comparison quote from a second farm, and the coffee change led to a conversation that brought back the 12-bag case at the old per-bag price. None of these would have happened if the invoices had simply been paid.

Lead times you can actually plan with

Suppliers quote lead times; deliveries reveal the real ones. To measure them you need two dates per order: when you ordered and when it arrived. Order dates are in your sent emails or purchase orders; delivery dates are on delivery notes or in your receiving records. AI can pull both out of an email export or photos of delivery notes. For turning delivery notes into stock updates automatically, see whether AI can read delivery notes and update stock.

Run the numbers for a hypothetical members' club and its drinks wholesaler, which promises delivery within two working days. Over a quarter, the club placed 26 orders:

  • Median lead time: 3 working days.
  • Four in five orders arrived within 5 working days.
  • Longest: 6 working days, in the week before a public holiday.

If the club's reorder points assume two days, it will run short roughly every other order. Planning on five days, with a note to order early before holidays, fixed the bar's recurring Friday shortages. That measured figure is what belongs in your stock planning; how AI inventory forecasting works shows where lead time enters the reorder calculation.

On time and in full: counting what actually arrived

Late is one failure; short is another. A delivery that arrives on time with three of the ten lines missing, or with substitutions you didn't agree to, causes as much trouble as a late one. The measure most businesses use is "on time and in full": the share of deliveries that arrived by the promised date with everything ordered.

AI can compare each delivery note against the matching order and list the differences. For the hotel's first quarter (illustrative):

SupplierDeliveriesOn timeIn fullOn time and in fullCommon problem
Produce3895%79%76%Substitutions without asking
Laundry5290%98%88%Late on Mondays
Drinks1283%92%75%Split deliveries
Cleaning supplies6100%100%100%None

The produce supplier's 79% in-full figure started a useful conversation: substitutions were happening because the hotel's order arrived after the supplier's cut-off time. Moving the order 90 minutes earlier solved most of it. Without the numbers, the conversation would have been "you keep getting our orders wrong", which rarely gets anywhere.

A simple supplier risk score

Risk here means "how much trouble would we be in if this supplier let us down or disappeared?" Score each supplier from 1 (low) to 3 (high) on five points, once a quarter:

  • Dependence: how much of that category it supplies.
  • Ease of switching: how quickly you could replace it (days, weeks, months).
  • Performance: its on-time-and-in-full record.
  • Warning signs: unexplained price rises, slower replies, staff turnover, notices about changes to service.
  • Contract exposure: long lock-ins, auto-renewals, data or equipment you can't easily take back.

Suppose a campsite scores its gas bottle supplier 3 for dependence (sole supplier), 3 for switching (bottles are brand-specific and deposits are tied to the supplier), 1 for performance, 1 for warning signs and 2 for contract exposure: 10 out of 15, the highest on its register. The plan B was modest: find a second supplier who could deliver in an emergency, and keep a two-week buffer of gas in peak season rather than one.

AI helps with warning signs by reading what you'd otherwise skim: supplier newsletters, terms-of-service updates and emails announcing "changes to our service". Ask it monthly: "From these supplier emails, list any announcement of price changes, service changes, new terms, closures or ownership changes, with the date and the exact sentence." It won't predict a supplier collapsing, but it will make sure you've read the notices they sent.

Software suppliers count too

Many small businesses forget that their booking system, email marketing tool and AI assistants are suppliers, often with more power over them than the laundry. Two real examples from 2026 show why. Clockwise, an AI calendar tool, shut down on 27 March 2026 and deleted its users' data rather than transferring it. OpenAI discontinued Sora, closing its web and app versions on 26 April 2026 and its API on 24 September 2026, so anyone who had built a workflow on it had to rebuild.

For each software supplier, add three columns to the register: can you export your data, in what format, and how often do you actually do it? One invented but typical holiday-let manager checked and found its channel manager (the tool that syncs bookings across listing sites) exported bookings but not guest message history. It now exports bookings monthly and saves key guest messages to its own drive. Renewal dates and notice periods for software contracts matter as much as for physical suppliers; tracking contract renewals with AI sets up the reminders.

A church office: renewals and a volatile price

Supplier management looks different where there are few suppliers but big contracts. Take a church office, invented for this example, with about nine regular suppliers: energy, heating oil, insurance, organ maintenance, photocopier lease, cleaning, grounds, waste and a payroll bureau. Price creep matters less here than two other risks.

The first is renewals. The photocopier lease renewed automatically for three years because nobody saw the 90-day notice window. The register now lists every notice date, and a calendar reminder goes to the treasurer 30 days before each one opens.

The second is heating oil, whose price moves from week to week. The office asked AI to tabulate every oil invoice for the last three years, showing litres, price per litre and date. The table showed that ordering in late summer rather than in the first cold week of autumn had averaged noticeably less per litre in two of the three years. That's a pattern worth acting on cautiously, not a promise: past prices don't guarantee future ones, but the data made a sensible default visible.

A monthly supplier review in about 30 minutes

Once invoices and delivery notes flow into the register, the monthly review is short. Upload the month's price history, deliveries and supplier emails, and ask for one summary:

Using the attached price history, delivery log and supplier emails for [month]:
1. Price changes per unit over 3%, and any that conflict with agreed terms.
2. Deliveries that were late, short or substituted, by supplier.
3. Lead times this month compared with each supplier's promised lead time.
4. Any supplier announcements of changes to prices, terms or service.
5. Contract notice dates falling in the next 90 days.
Give each item a one-line suggested action. Quote the invoice number or email date.

The hotel's owner reads the summary, checks two or three flagged items against the original invoices, and sends the emails that need sending. The first months take longer because of the mapping table; by month four it's a half-hour job. The quotes are the safeguard: if the AI flags a price rise but can't point to an invoice number, treat the flag as unconfirmed.

What stays with you

AI can measure suppliers; it can't manage the relationship. It won't know that the produce supplier went out of its way during a snowstorm last winter, or that the drinks rep will match a rival's price if asked in person. Use the numbers to make conversations specific, then have the conversation yourself. When a supplier's record is poor enough to replace, go back to a proper comparison and, if orders are routine, look at automating purchase orders and supplier emails for the new one.

Further reads

Sources: Zapier plan details; supplier-risk examples from Clockwise's shutdown notice and OpenAI's help notice on the Sora discontinuation (facts checked September 2026).

Want your supplier costs and risks tracked properly?

On a 1:1 call we'll set up a supplier register from your recent invoices, decide how prices and lead times get captured each month, and agree which risks deserve a plan B.

Book a 1:1 call with me