Skip to content
Warehouse, shipping & traceabilityElectronics & SensorsMetal & MachiningPlastics & PackagingAutomotive Suppliers

Check delivery call-offs without retyping

New call-offs are compared with the last version, and you see jumps and shortages as they arrive.

Today

Automotive customers publish call-offs and delivery schedules in many portals and formats. Changes are transferred by hand, often days later. A quantity jump gets noticed when the material is already short and only a special shipment will help.

An example

At Arnstein a customer raises the call-off for bracket HT-7711 in PA6 GF30 for week 47 from 2,400 to 6,000 pieces. The agent flags the jump, shows stock for 3 days and alerts production planning before the call-off is approved.
Fictional company, typical workflow.

Your data, wherever it lives

Call-offs and delivery schedules arrive today by EDI, from many customer portals or as PDFs and spreadsheets by e-mail; orders, stock and the last version sit in the ERP, free capacity in the MES. demi reads, understands and links them per part and call-off version, with your rights. The AI compares each new call-off with the last version in seconds instead of someone retyping it days later, and customer logistics decides what to accept.

Where the data lives today

  • Web & portals
  • PDFs
  • Office files
  • E-mails
  • ERP
  • 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 customer portals, ERP, MES and e-mail. demi replaces nothing and matches EDI messages, portal exports and e-mailed call-offs against schedules, orders, stock and capacity; every call-off is tied to its previous version. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Customer logistics confirms changes before they are applied, and planning is notified of relevant jumps. Every update is recorded.

  3. 3 · ActIntelligence Layer

    The agent takes quantities and dates exactly as they appear in the call-off and calculates the difference from the previous version exactly. It reports jumps above your thresholds together with stock and free capacity.

How it runs

  1. 1

    A new call-off arrives by EDI, as a portal export or by e-mail.

  2. 2

    demi reads it and compares it line by line with the last version.

  3. 3

    The agent flags jumps and checks stock and capacity.

  4. 4

    Customer logistics confirms; demi holds the updated schedule ready to write back after approval.

  5. 5

    If there is a shortage, planning gets the case with all the figures.

What changes

  • No more retyping of call-offs

  • Jumps caught on arrival

  • Fewer special shipments

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

+200 hfreed per year

Assumptions and calculation

demi compares schedules with the last release and warns of jumps; you decide what gets taken over.

10 min → 5 min per case

How does it run today?

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

How we calculate

200 delivery schedules × 10 min × 50% × 1.0 (manual) × 12 months = 12,000 min = 200 h

Value per year, before demi costs

Freed per year+200 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$13,000

gained per year

200 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

Which portals can demi read?

demi reads EDI messages directly and portals through their exports, whether file, spreadsheet or PDF. If a call-off comes by e-mail, the attachment is read too. For each customer it is set out which field goes where.

How does demi detect a jump?

The agent compares every line with the previous version, week by week and day by day. You define what counts as a jump, per customer or part, in absolute terms or as a percentage. It also shows whether the change falls inside the binding production or material release period.

Does demi apply changes automatically?

As far as you decide. You can, for example, let small changes within set limits go straight in and always confirm jumps. Every update is recorded with before and after.

What happens if a call-off exceeds capacity?

Planning gets the case with stock, open production orders and free capacity. If you want, the agent drafts a reply to the customer that customer logistics reviews and sends. The customer hears early, not on the delivery day.

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