Skip to content
Quality, standards & complianceWaste & Recycling

Assign waste codes and keep the register

Codes and declarations come as a proposal, and the register fills from actual movements.

Today

Waste codes, declarations and registers take expert knowledge and careful paperwork. Mistakes lead to rejected loads and trouble with the authority. The register is often pieced together afterwards from weighbridge tickets and spreadsheets.

An example

A new customer of Wertora Recycling describes its waste as "oily filter cake". The agent proposes two possible waste codes, requests the missing analysis and drafts the declaration once the waste officer has confirmed a code. The first delivery of 8.4 t then appears in the register on its own.
Fictional company, typical workflow.

Your data, wherever it lives

Today customers describe their waste by e-mail, analyses and permits arrive as PDFs, consignment notes sit in the electronic tracking portal, weighing data in the weighbridge database, orders in the ERP and the register often in a spreadsheet. demi reads, understands and links them per waste stream and customer, with your rights. The AI proposes the waste code with its reasoning and keeps the register with every delivery rather than after the fact, and the waste officer confirms.

Where the data lives today

  • E-mails
  • PDFs
  • Web & portals
  • Databases
  • ERP
  • Office files
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, portal, spreadsheets and e-mail. demi replaces nothing and links orders, analyses, waste descriptions, permits, accompanying documents and weighbridge data per waste stream and customer. demi only writes back after approval.

  2. 2 · PermitPermission Layer

    The waste officer confirms every classification. Authorities receive only released records, and every confirmation is recorded.

  3. 3 · ActIntelligence Layer

    The agent proposes codes from the official waste catalog with its reasoning and keeps the register exactly from weighbridge data and accompanying documents, not by estimate. It flags contradictions between code, analysis and permit, each with its source.

How it runs

  1. 1

    Take in the customer's waste description and analysis

  2. 2

    Propose a code with reasons and request missing data

  3. 3

    Have the waste officer confirm the classification

  4. 4

    Draft the declaration from the order

  5. 5

    Update the register from weighbridge data and accompanying documents

What changes

  • Fewer classification errors

  • A register kept from actual movements

  • Less paperwork for the team

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 proposes the waste code, drafts the declaration and keeps the register; you check.

20 min → 12 min per case

How does it run today?

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

How we calculate

60 waste declarations × 20 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 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

Does it decide waste codes on its own?

No. The agent proposes codes from the official catalog and backs each proposal with the description and the analysis. Your qualified person sets the classification, and that confirmation is recorded.

Can it keep the register automatically?

demi updates the register from the recorded movements: weighbridge data, accompanying documents and orders. Every entry links to its record. The agent flags inconsistencies, such as a weighing without accompanying documents, instead of covering them up.

How are permits checked?

Your permits are stored as data, with the allowed codes and quantities per plant. The agent checks every new classification and every delivery against them and reports when a code is not covered.

Do we need new software for this?

No. Your data sits in your ERP, the authority portal, spreadsheets and e-mail; how it gets to demi, we clarify in a conversation. demi writes back only after release, and your routines stay the same.

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