Skip to content
Procurement & supply chainFor every industry

Catch supplier delays before they hurt

Every open purchase order in view: you see which customer order a delay hits, and the reminder is already drafted.

Today

A single missing part is often noticed only when assembly stops. Buyers chase suppliers by phone without knowing which delay really matters. The list of overdue lines is long, and everything on it looks equally urgent.

An example

Talwerk Antriebstechnik has 140 overdue order lines. The agent shows the 6 that block customer deliveries this month, among them GH-160 housings for a gearbox order due on 28 November. Reminders for those 6 are ready first.
Fictional company, typical workflow.

Your data, wherever it lives

Today purchase orders, project BOMs and customer orders sit in the ERP, order confirmations and shipping notices arrive as PDFs by e-mail or through supplier portals, and production progress sits in the MES. demi reads, understands and links them per order line through to the customer order, with your rights. From the long list of overdue lines, the AI shows in minutes the few that put a customer date at risk, drafts the reminder, and your buyer approves it.

Where the data lives today

  • ERP
  • E-mails
  • PDFs
  • Web & portals
  • MES
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the ERP, e-mail, MES and portal. demi replaces nothing and ties every order line, with its confirmation and shipping notice, to the project BOM, production order and customer order. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Buyers see their suppliers, project managers see their projects. A reminder goes out only once the responsible buyer approves it, and it is recorded.

  3. 3 · ActIntelligence Layer

    The agent ranks overdue lines by their impact on customer orders, derived from recorded links rather than estimates, and drafts reminders and expedite requests. It alerts the affected project manager, citing the purchase order and the job.

How it runs

  1. 1

    demi reads confirmed dates and shipping notices from e-mail and portals.

  2. 2

    Every open order line is linked to its customer order.

  3. 3

    Overdue lines are ranked by their impact on customer dates.

  4. 4

    The agent drafts the reminder, and the buyer approves it.

  5. 5

    The project manager sees at once which date is at risk.

What changes

  • Critical delays handled first

  • Fewer assembly stops

  • Less chasing by phone

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+240 hfreed per year

Assumptions and calculation

demi shows which customer order a delay hits and writes the reminder; you send it.

10 min → 6 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

300 open purchase orders × 10 min × 40% × 1.0 (manual) × 12 months = 14,400 min = 240 h

Value per year, before demi costs

Freed per year+240 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€15,600

gained per year

240 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi know which delay matters most?

From the links in your data: order line, production order, customer order and its delivery date. A delay that breaks a customer date goes to the top, one with buffer further down. Where a link is missing, demi shows that instead of guessing.

Can it read shipping notices and date updates from suppliers?

Yes, from e-mails, PDFs and supplier portals. demi matches new dates with the purchase order. demi writes back only after approval. So the dates in the system are current without anyone retyping them.

Does demi send reminders on its own?

No. The agent drafts the reminder or expedite request with order number, line and confirmed date. The responsible buyer sends it, and every reminder is recorded.

Are project managers informed?

Yes. When a delay hits a project, the project manager sees the affected line, the new date and the customer order. They see only their own projects. Prices and terms stay with purchasing.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases