Skip to content
Warehouse, shipping & traceabilityMetal & MachiningPlastics & PackagingChemicals & Process IndustryAutomotive Suppliers+6

Trace batches and serial numbers

From raw material to customer and back, holds and recalls stay limited to what is really affected.

Today

When a defect or contamination turns up, the search begins: which batches went into what, and which customers received them? The answer is spread across ERP, MES and paper records and takes days. Holds and recalls end up too broad or too late.

An example

At Polivo Kunststoffverpackungen a supplier reports a contaminated lot of PP granulate. The agent finds 3 production orders for Ø 38 mm closures, 41 pallets in stock and 7 shipments to 5 customers. The quality manager puts the pallets on hold and approves the 5 customer notices.
Fictional company, typical workflow.

Your data, wherever it lives

Today goods receipts, production orders and shipments sit in the ERP, batch bookings in the MES, storage locations in the warehouse system, inspections in the quality system and some handovers only on paper records. demi reads, understands and links them into one genealogy per batch and serial number, with your rights. The AI traces a batch to the customer and back to the raw material in minutes instead of days, every link with its record, and quality decides on holds and recalls.

Where the data lives today

  • ERP
  • MES
  • QM system
  • Scans & paper
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, MES, QMS and WMS. demi replaces nothing and links raw-material lots, heats, resin lots, production orders, semi-finished goods, finished batches, serial numbers and shipments into one genealogy. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Quality and logistics see the whole chain; a customer only receives their own affected deliveries. Quality decides on holds and recalls, and every decision is recorded with role, time and reason.

  3. 3 · ActIntelligence Layer

    The agent follows the genealogy forward to the customer and back to the raw material and lists affected stock and shipments. It builds the chain only from recorded bookings, never by estimate, names the document behind each link and drafts the customer notices.

How it runs

  1. 1

    You enter a batch, a serial number or a raw-material delivery.

  2. 2

    demi builds the genealogy forward and backward from the bookings.

  3. 3

    The agent lists affected production orders, stock and shipments.

  4. 4

    Quality decides on the hold and the recall.

  5. 5

    Hold notes and customer notices go out only after approval.

What changes

  • Recalls scoped narrowly and quickly

  • Recall drills without a search party

  • Customers informed precisely

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

+96 hfreed per year

Assumptions and calculation

demi traces batch and serial number from raw material to customer and narrows it down; you decide on the hold.

2 h → 1.2 h per case

How does it run today?

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

How we calculate

10 trace requests × 2 h × 40% × 1.0 (manual) × 12 months = 96 h

Value per year, before demi costs

Freed per year+96 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

+$6,240

gained per year

96 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 systems does the trace need?

ERP and MES for orders and consumption, plus the WMS for bins and shipments and the QMS for holds. Where batches are still on paper, demi reads scanned records too. Nothing is replaced; demi only connects.

What if a link in the chain is missing?

Then the agent shows the gap instead of bridging it. If, say, the consumption booking for a raw-material lot is missing, you see which orders could be affected and which booking is absent. Quality decides whether to put more on hold as a precaution.

How fast is a full forward and backward trace?

With the bookings in hand, demi builds the genealogy for every request. Nobody has to pull lists from several systems any more. How solid the result is depends mostly on how completely production books its consumption.

Can demi run recall drills?

Yes. You pick any batch and the agent plays the recall through: quantity balance, affected customers, draft notices. The result is a report you can show in an audit. Nothing is sent during a drill.

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