For procurement and operations managers

See which orders a late delivery holds up

Certant reads your supplier updates, purchase-order exports and site reports, then lists the recorded orders and sites that depend on the delayed delivery.

See it on your documents See how Strata works

Set up with you on a sample of your own records.

Delivery DN-4471 · Northline FastenersExample

Was due 9 Nov 2026. Supplier now states 23 Nov 2026.

Supplier update email · 4 Nov 2026 · attachment page 1

2 orders needed before the new date 1 site with no delivery data

The delay, the update it came from, and what was waiting on it.

The problem

A late delivery stalls other decisions

A supplier emails to say a delivery has slipped by two weeks. Someone then has to work out which purchase orders were waiting on it and which sites were expecting the stock, usually by searching three spreadsheets and an inbox.

While that search goes on, site managers keep planning around a date that has already moved.

The documents

What Certant reads

Records are linked on identifiers your team has reviewed, such as the order number and supplier code. Where two systems name the same supplier differently, the link waits for a person to confirm it.

Document	What it supplies
Supplier updates	Emails, notices and portal exports that state a revised delivery date.
Purchase-order exports	Order number, supplier, item, required-by date and destination site.
Site reports	What each site has recorded as received or still outstanding.

The result

Open the delay and its dependants

You get a list to investigate, and each row opens the record it came from.

Orders linked to delivery DN-4471Example

Order	Item	Site	Required by	Position	Source
PO-20318	M12 anchor bolts	Geelong depot	12 Nov 2026	Needed before the new date	Purchase-order export · row 214
PO-20341	M12 anchor bolts	Ballarat workshop	16 Nov 2026	Needed before the new date	Purchase-order export · row 239
PO-20377	Bracket kits	Geelong depot	30 Nov 2026	After the new date	Purchase-order export · row 262
PO-20402	Washers, assorted	Bendigo site	Not recorded	No delivery data	No October site report received

Two orders need the stock before the supplier's new date. Bendigo sent no site report for October, so its position is shown as unknown.

The approval

A person approves the follow-up

Certant drafts a follow-up to the supplier that names the affected orders and asks for a confirmed date. The draft waits in an approvals queue until a procurement lead reads it and signs off.

Nothing goes to the supplier before that approval. The record keeps who asked, who approved and what was sent.

Proposed follow-upExample

To: Northline Fasteners
Draft: "Your update of 4 November moves delivery DN-4471 to 23 November. Purchase orders PO-20318 and PO-20341 need this stock by 12 and 16 November. Please confirm the earliest date you can deliver those two lines."
Attached: the supplier update, two order rows

Waiting for approval · Procurement lead

Scope

What setup involves

This is a configured workflow. We set it up with you on a sample of your own supplier updates and order exports, and you see it run on that data before anything goes live.

Area	What to expect
Dependencies	Certant lists the dependencies recorded in your orders and site reports.
Dates	It works from the dates your supplier states. It doesn't predict delivery dates or suggest alternative routes.
Linking	Records join on identifiers you have reviewed. The same supplier held in two systems isn't merged automatically.