Skip to content
Quality, standards & complianceFood & Beverage

Keep your allergen matrix up to date

If a supplier changes a detail, you see right away which label, line or customer is affected.

Today

Allergen information has to be right for every product and every line. Today recipes, supplier specifications and customer requirements sit in spreadsheets and e-mails. When a supplier changes a statement, it often surfaces only on the label or in a complaint.

An example

At Tarvina a spice supplier adds a "may contain traces of sesame" statement. The agent flags six products from the SN snack range, two customer specifications that exclude sesame and the cleaning plan for line 3. The head of quality reviews the list and approves the new matrix.
Fictional company, typical workflow.

Your data, wherever it lives

Today recipes sit in the ERP and PLM, supplier specifications arrive as PDFs by e-mail, the allergen matrix is a spreadsheet, customer specifications sit in folders and cleaning plans in the QM system. demi reads, understands and links them per raw material and product, with your rights. The AI spots a changed statement on the day it arrives instead of at the label and shows the affected products and lines, and the head of quality releases the new matrix.

Where the data lives today

  • ERP
  • PLM
  • PDFs
  • E-mails
  • Office files
  • Folders & drives
  • QM system
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, PLM, spreadsheets and e-mail. demi replaces nothing and carries each raw material with its valid specification into every product that uses it, with lines, cleaning plans, customer specifications and complaints. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Quality owns the matrix and approves changes. Customer specifications are visible only to the account team, and every approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent compares new specifications with the approved version, updates the matrix and shows the affected products, labels, lines and customer requirements, each with its source. Status comes only from documented specifications: a missing one shows as “unknown”, never as “allergen-free”.

How it runs

  1. 1

    A new or changed specification arrives by e-mail, portal or file share

  2. 2

    The agent compares it with the approved version and flags every allergen change

  3. 3

    It lists the affected products, labels, lines and customer specifications

  4. 4

    Quality reviews and approves the updated matrix

  5. 5

    Goods receipt and complaints are checked against the approved matrix

What changes

  • Allergen data backed by documents

  • Supplier changes caught at once

  • Customer requirements checked before shipping

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 keeps the allergen matrix from documented specs and flags each change; you assess it.

30 min → 18 min per case

How does it run today?

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

How we calculate

40 specifications × 30 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 96 h

Value per year, before demi costs

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

+€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

How does demi detect supplier changes?

Every incoming specification is compared with the last approved version for the same raw material, whether it arrives by e-mail, portal or file share. Changed allergen and trace statements are flagged. Until quality approves, the old matrix stays in force and the change is listed as open.

Does it take cross-contact on lines into account?

Yes. demi knows which products run on which line and which cleaning plan applies there. When an allergen is new to a line, the agent shows the products that follow it and the cleaning plan that needs updating. The risk assessment stays with your team.

Can it match complaints to customer specifications?

Yes. A complaint is linked to the product, the batch and the customer specification. The agent shows which specifications applied when the batch was made and whether it met the requirement. That tells you quickly whether the cause is a raw material, a line or the labelling.

What happens when a specification is missing?

The raw material shows as "unknown" in the matrix, never as "free from". The agent drafts the request to the supplier and follows it up until the specification arrives.

Which systems does allergen and specification management need?

Your recipes and raw materials live in the ERP or PLM, supplier specifications in a folder, and they arrive in a mailbox. demi takes existing allergen spreadsheets as a starting point. Nothing is replaced, and approved changes are written back.

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