Prepare EU Declarations of Conformity and Technical Documentation

When one document draws on several sources

An EU declaration of conformity may look like a manageable template once it is finished. In a company, however, the required information rarely sits in one place: it may be spread across product master data, orders, technical data sheets, supplier documents, messages and ERP exports.

The difficult part is not just filling in a PDF. First, someone has to determine which information belongs to which variant and order, whether units are consistent and whether each statement is supported by a source or an approved text block.

Alpino AI structures this preparation workflow. The result is a traceable draft for review, not an automatic legal approval.

What Alpino AI prepares

Depending on the document type and the approved rule set, the solution can:

• read information from PDFs, messages, forms and ERP exports,
• combine product, order and packaging data in one consistent schema,
• structure predefined required fields such as product name, variant, dimensions, material, quantity or packaging function,
• flag missing information, inconsistent units and contradictory values,
• keep the origin of each field traceable to a document, system and version,
• store the rule-set and template version used and
• create a document draft from an approved template for technical review.

If a value is missing, the field stays open. The solution does not invent a technical fact just to make a template look complete.

A clear workflow for recurring documentation

A useful process consists of six defined steps:

1. Define the document type and rule set: Which declaration or technical document should be prepared? Which template, required fields and approved text blocks apply?
2. Load the sources: Orders, product master data, technical PDFs, messages and ERP data are assigned to the relevant case.
3. Extract and structure the information: Relevant values are captured, normalised and linked to their source.
4. Run plausibility checks: Missing required fields, contradictions, unclear variants and unsupported statements are made visible.
5. Create the draft: The reviewed information is transferred into the approved template; the rule-set and version remain documented.
6. Review and archive: The responsible person adds information, corrects the draft, approves it and signs it. Only then is the final PDF archived.

What the PPWR means from 12 August 2026

Regulation (EU) 2025/40 on packaging and packaging waste (PPWR) generally applies from 12 August 2026. This does not mean that every requirement applies in the same way to every package on the same day. The relevant scope, the company’s role in the economic chain and later application dates or supplementary acts need to be checked for each case.

For packaging covered by the relevant obligations, Article 15(2) refers, among other things, to the conformity assessment under Article 38 and the technical documentation in Annex VII. Once conformity has been demonstrated, the EU declaration of conformity must be drawn up under Article 39; Annex VIII sets out its structure.

Who must issue the declaration and which records must be kept depends on the company’s role, the type of packaging and the supply chain. A general statement such as “the packer is always responsible” would therefore be too broad.

The technical and legal assessment remains with the responsible company or a qualified professional appointed by it. Alpino AI can make the required information easier to find, structure and version.

Which European SMEs may benefit

This use case is particularly relevant for SMEs across Europe that regularly prepare technical or packaging-related documentation:

• printing and packaging businesses,
• technical manufacturing and machine or plant engineering,
• component manufacturers,
• companies with many product variants and supplier documents and
• importers or manufacturers with supply chains across Europe.

The industry label alone is not decisive. A pilot makes sense when recurring documents draw on several sources and the company has a clear review and approval process.

What the solution explicitly does not do

Alpino AI does not provide legal advice as part of this workflow. The solution:

• does not legally classify a product automatically,
• does not decide which legal basis or standard applies,
• does not invent missing values, test reports or sources,
• does not independently confirm conformity,
• does not grant automatic legal approval and
• does not replace the responsible person’s signature.

You receive a traceable document draft with sources and open points. Technical assessment, approval and responsibility remain with the company.

How to start with a pilot

One document type, one approved template, a defined rule set and 10–20 historical or new test cases are enough to start. Together, we define required fields, data sources, checks and approval roles.

The pilot can then measure preparation time, clarification requests, missing information and corrections before approval. Only once this limited workflow works reliably should you add more variants, document types or system integrations.

Regulatory status and sources

The legal notes on this page reflect the research status of 12 August 2026. They do not replace an individual legal or technical assessment.

• Regulation (EU) 2025/40 on EUR-Lex – in particular Articles 15, 38 and 39 and Annexes VII and VIII
• European Commission: New EU rules on packaging enter into application on 12 August 2026
• ZSVR: What changes from 12 August 2026

If you want to assess a recurring documentation workflow in your company, book a 30-minute initial conversation.