Product Data Across EU Systems: What Can Be Reused and What Must Stay Separate

A practical matrix for reusing product data across DPP, SCIP, EPREL, EUDR, EPR, PPWR, customs, Safety Gate and technical documentation.

Last verified: 3 September 2026

LinkedIn X Email

Navigate this page

Overview
The cross-system product data matrix
The ten-question reuse test
A field-reuse matrix for the values businesses see most ofte
Why "one source of truth" is too crude
System-by-system boundaries that matter
The operating model: govern once, transform deliberately, su
Minimum provenance to keep with a reusable value
Direct answers
Primary official sources
Keep exploring

There is no single EU product database that makes the others disappear. The same physical product can legitimately appear in a DPP, SCIP, EPREL, an EUDR due-diligence statement, an EPR producer register, customs records, technical documentation and other systems because those records answer different legal and operational questions. The opportunity is still substantial. A business should not collect the same stable identity or evidence-backed fact from scratch for every system. The practical rule is:

Reuse a value only when the object, granularity, definition, unit, time basis, actor, evidence and purpose match. Keep the system-specific legal record and its identifier separate.

This page is the cross-system map. It does not replace the pages that own each regime or field.

The cross-system product data matrix

System / record	What it mainly describes	Typical level	Data that may be reusable	What must stay system-specific	Canonical next page
Digital Product Passport	Product information required by the applicable DPP legislation	Model, batch or item, as law specifies	Product identity, operator data, classification, evidence-backed attributes	Required field set, access rights, DPP identifier, publication and lifecycle rules	What does not map cleanly into a DPP
DPP Registry	Registration/indexing metadata for the passport	DPP identifier linked to the relevant product level	Unique identifiers and associated metadata	Registry status and central registration record	What the DPP Registry records
SCIP	Articles/complex objects containing Candidate List substances above the relevant threshold	Article and component hierarchy	GTIN/EAN, catalogue/part numbers, classification, substance identity where equivalent	SCIP notification, component/substance structure, ECHA-specific submission lifecycle	DPP vs SCIP
EPREL	Energy-labelled product model and its public/compliance information	Model	Supplier identity, model ID, brand/trademark, GTIN where present, equivalent performance facts	EPREL registration, access layer and product-group-specific energy-labelling record	DPP vs EPREL
Safety Gate	Corrective measures concerning dangerous products	Safety event / measure linked to identified products	Product and operator identifiers used to resolve the affected product	Alert, risk/corrective-measure event and authority workflow	GPSR work towards a passport
EUDR Information System / due-diligence statement	Due diligence for relevant commodities/products and their production geography	Statement/transaction context plus production plots	Operator identity/EORI, HS classification, product description, some origin data where semantically equivalent	Due-diligence statement, plot geolocation, risk assessment and submission reference	EUDR
Textile EPR producer registers	Producer registration in each relevant Member State	Organisation x jurisdiction x scheme	Legal entity, contact data, national IDs, CN codes	Registration number, jurisdiction, PRO relationship and scheme status	Registrations that gate a listing
PPWR packaging information	The packaging as its own regulated object	Packaging type/component, sometimes linked to packaged product	Operator identity and shared data-carrier infrastructure	Packaging composition, packaging compliance and packaging-specific information	PPWR packaging facts
Customs / CN / TARIC	Classification and declaration of goods for customs/tariff/statistical purposes	Goods / declaration / consignment context	CN/HS classification where the same nomenclature and version are required	Customs declaration, tariff measures, transaction/consignment data	When the commodity code changes
Technical documentation	Evidence that a product complies with applicable EU product rules	Product/model/design and applicable conformity scope	Test results, design facts, declarations, risk evidence and document references	The controlled technical file, authority access and retention obligations	Technical file to governed product data
Battery passport	Battery model plus information specific to the individual battery	Model + individual battery	Identity, model data and evidence that can map to other DPPs	Battery-specific passport fields, access classes and individual lifecycle information	Battery DPPs
PIM / ERP / PLM / commerce platform	Internal commercial, engineering and operational data	Whatever the business system was designed to manage	Often the starting point for identity, variants, supplier, weight and classification	It is not itself evidence that an EU regulatory submission or DPP requirement has been met	The product data you already have

How to read this matrix

May be reusable does not mean copy the field.

A value can move safely only after it passes the equivalence test below. The source record may also have access restrictions, legal-signature requirements or lifecycle rules that do not travel with the raw value.

The ten-question reuse test

Before one system feeds another, ask these questions in order.

Same object? Does the value describe the same product, component, material, facility, plot, packaging object or organisation?
Same level? Is it true at model, variant, SKU, batch, item, component, shipment or event level?
Same definition? Are the two systems asking the same semantic question rather than using the same label for different concepts?
Same unit and method? If it is measured or calculated, are unit, method, reference conditions and denominator compatible?
Same time basis? Is the source value current for the target product or period?
Same actor role? Is manufacturer, producer, supplier, importer or operator being used in the same legal sense?
Same jurisdiction and instrument? Does the value depend on a Member State, EU scheme, nomenclature year or sector-specific act?
Evidence strong enough? Can you show where the value came from and why it supports the target claim?
Access compatible? Is the source value public, authority-only, commercially sensitive or otherwise restricted?
Same lifecycle? What event makes the value stale, and who has to update each target system?

If any answer is no or unknown, the value is not ready for direct reuse. It may need transformation, evidence work or a separate record.

A field-reuse matrix for the values businesses see most often

Field	Reuse across systems	Main trap
GTIN / product identifier	Often reusable	One identifier can point to a different level than the target system expects
Model identifier	Often reusable at model level	It should not be promoted to item identity
Brand / trademark / commercial name	Often reusable	Commercial name is not a unique product identifier
Legal entity name	Reusable with role metadata	The same company can be manufacturer in one record and producer/importer in another
EORI	Reusable where that actor and context match	Do not attach one party's EORI to another legal role
HS / CN / TARIC code	Reusable with scheme/version	HS, CN and TARIC are related but not interchangeable strings; CN also changes over time
Country of origin / production	Depends	Customs origin, production country, facility location and EUDR production geography answer different questions
Factory / facility identifier	Depends	Facility identity is different from country of origin or plot geolocation
Weight	Depends on denominator	Net product mass, packaged shipping weight and regulatory net mass can differ
Substance identity	Depends	The substance can apply to one component rather than the whole product
Concentration	Transform with care	Range, basis and article/component scope must survive
Certificate / test result	Evidence candidate	A document can support a fact without itself being the fact
Regulatory registration number	Reference only	EPR, SCIP, EPREL and other record IDs are not interchangeable product attributes
Safety alert / corrective measure	Event record	A Safety Gate event should not be stored as a timeless product attribute

Why "one source of truth" is too crude

The phrase sounds clean and often produces bad compliance architecture.

There can be one governed business fact without there being one legal record.

Take an operator's legal name. The same controlled name may feed EPREL, EPR registration, a DPP and technical documentation. But those systems can still have different:

legal roles
jurisdictions
registration IDs
effective dates
submission statuses
evidence requirements
access rules.

A practical ownership model therefore separates:

1. The governed fact

The value the business maintains once, with a clear object and owner.

2. The evidence

The document, source system, supplier declaration or measurement that supports the value.

3. The regulatory record

The system-specific submission, registration, alert or passport record required for a legal purpose.

4. The published representation

The value rendered for the customer, recycler, authority or other audience with the access rules that apply there.

That is the cross-system extension of which system should own each product fact.

System-by-system boundaries that matter

DPP Registry is not the full passport database

The Commission's July 2026 launch material describes DPP data as decentralised. The central Registry registers each DPP's unique identifier and associated metadata.¹

That means registered in the DPP Registry and all product data stored by the Commission are not equivalent statements.

SCIP is not just a chemical reference field

SCIP records article or complex-object identity and Candidate List substance information, including concentration range and location/material context. Reusing a substance value means preserving that article hierarchy.²³

EPREL is the strongest live example of official once-only direction

The 2025 ESPR working plan names EPREL as an alternative digital system where equivalent information is provided. The Commission's June 2026 proposal would go further by interlinking EPREL and the DPP Registry and avoiding duplicate reporting of equivalent model information. The proposal remains ongoing at this page's verification date.⁴⁵⁶

Safety Gate is an event system, not a master product record

GPSR Article 25 defines Safety Gate as the rapid alert system for exchanging information on corrective measures concerning dangerous products.⁷

Product identifiers help resolve which product the alert concerns. The alert and corrective measure remain event records with their own lifecycle.

EUDR combines reusable identity with non-reusable due-diligence context

The EUDR due-diligence statement includes operator information, EORI where relevant, Harmonised System code, product description, quantity and production geography. Some identity/classification values may be reusable. Plot geolocation, due-diligence findings and the statement reference remain EUDR-specific records.⁸

EPR registration is about the producer in a jurisdiction

The 2025 amendment to the Waste Framework Directive requires textile producer registers in each Member State and specifies information including producer identity, official IDs and CN codes. Those underlying party/classification facts can be governed once. The registration number and Member-State scheme status are still separate.⁹

PPWR Article 12 expressly provides that, where Union law requires packaged-product information through a data carrier, one carrier is used for product and packaging information while the two remain distinguishable.¹⁰

That is a useful architectural precedent: one access point does not mean one regulated object.

Customs classification is reusable only with its scheme and date

The Commission describes the Combined Nomenclature as the EU's system for classifying goods for customs and trade statistics, with eight-digit CN codes. The nomenclature is updated annually.¹¹

A code copied without its scheme and applicable version is weaker than it looks.

Technical documentation is evidence infrastructure

EU guidance says manufacturers prepare technical documentation before placing a product on the market, keep it available for authorities and generally retain it for ten years unless product-specific law says otherwise.¹²

That technical file may be the best source for many DPP facts. It does not follow that the whole technical file should be copied into a public passport.

The operating model: govern once, transform deliberately, submit separately

For most businesses the target architecture can be expressed in three verbs.

Govern once

Maintain each stable fact at the level where it is true. Give it an owner, source, status and version.

Transform deliberately

When another EU system wants the fact, compare semantic definition, unit, object, granularity, access class and evidence. Record any mapping or calculation rather than silently copying the output.

Submit separately

Create or update the system-specific record with its own identifier, actor, jurisdiction and lifecycle. Only collapse the workflow where official law or system integration explicitly supports it.

This is a business-data architecture recommendation. It does not change which legal obligations apply.

Minimum provenance to keep with a reusable value

A reusable product fact should carry enough metadata to answer:

What is the value?
What object does it describe?
At what granularity is it true?
Who supplied or measured it?
What evidence supports it?
Which definition/method/unit applies?
When was it observed or verified?
What makes it stale?
Which systems has it been rendered or submitted into?
What transformation did each target apply?

If your architecture cannot answer those questions, reuse increases the speed at which an error propagates.

Direct answers

Can I use the same product data for multiple EU systems?

Yes, often. Stable identity, party, classification and evidence-backed facts are good reuse candidates. Reuse is safe only when the target system asks the same semantic question about the same object and level.

Does a DPP replace SCIP, EPREL, EPR or EUDR?

Not as a universal rule. Each relationship has to be established by the relevant EU law. EPREL currently has the clearest explicit move toward equivalent-data interlinking with DPPs, and that June 2026 amendment remains a proposal on this page's verification date.

Which system should be the source of truth?

Choose the source of truth per fact, not per regulation. A PIM may own the commercial model name, a PLM may own engineering composition, a technical file may own conformity evidence and an authority system may own the legal registration record.

Should I copy EU database exports into my DPP?

No, not blindly. Treat exports as source records. Map fields only after the reuse test and retain source, object, version and evidence.

Can one QR code serve product and packaging information?

PPWR provides a concrete case where one data carrier is used for packaged-product and packaging information while both remain distinguishable. The data carrier can be shared without merging the regulated objects.¹⁰

Keep exploring

Next question: Start with the system you already use. If that is SCIP, read DPP vs SCIP. If it is EPREL, read DPP vs EPREL.

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Check a product How a value is decided

Help someone else make sense of product passports.