A product compliance management system tracks which rules apply to each product and holds the evidence that the product meets them. It also pushes the required information to every place the product appears. In the EU, that last job is now the hardest one. Product law regulates what sits on listings, packaging, QR codes and central registries, and the data has to match across all of them.
Enforcement is moving the same way. National authorities notified a record 4,671 Safety Gate alerts in 2025, 13% more than in 2024 and more than double the 2022 figure. Cosmetics made up 36% of alerts. Chemical risks were behind 53% of all notifications. Authorities also took 5,794 follow-up actions, and these include orders for online marketplaces to remove listings. The Commission's eSurveillance web crawler scanned over 1.6 million websites in 2025 and found more than 20,800 products that were already flagged in Safety Gate.
This article is for compliance and product data teams at manufacturers. It covers the EU rules that changed product data requirements and where PIM software fits in a product compliance management system.
Key Takeaways
- The GPSR already requires specific operator and safety data on every online offer. A listing without it can be ordered off a marketplace.
- The EU Digital Product Passport registry went live on 20 July 2026. Battery passports become mandatory on 18 February 2027, and ESPR product groups get at least 18 months after each delegated act. None had been adopted by mid-November 2026.
- PIM software fits model-level compliance data such as attributes, warning texts, certificates, and declarations. Serial numbers and batch traceability usually belong in ERP or MES.
- PIM supports a product compliance management system but doesn't replace QMS functions like risk assessment and corrective actions.
- Validation rules per market and channel stop incomplete listings before they go out.
What A Product Compliance Management System Has To Do
Most manufacturers already have the compliance data. It's scattered. Materials sit in PLM. Customs codes and country of origin sit in ERP. Test reports and certificates sit on a shared drive. The list of which product needs which warning lives in a spreadsheet that one quality engineer maintains.
A product compliance management system turns this into something you can query. It does five jobs.
It maps each product to the legislation that applies, usually through classification. A cordless drill sold in the EU falls under the machinery rules, EMC, RoHS and the Battery Regulation. Add Bluetooth, and the Radio Equipment Directive and the Cyber Resilience Act join the list.
It stores evidence with scope and validity. Test reports, certificates, declarations of conformity, supplier declarations, and safety data sheets each cover specific products. Each can expire or go stale.
It tracks change. A new supplier for a plastic housing can invalidate a REACH declaration. A firmware update can change a cybersecurity assessment.
It publishes. Labels, packaging, instructions, webshops, marketplace feeds, and soon passports all need the same verified values.
And it keeps history, so you can show what a listing said on a given date and which evidence backed it.
The first two jobs are compliance work. The other three are product data work, so PIM software ends up in the middle.
Our customers turn to us with a specific version of this problem. A certificate expires, or a substance lands on the REACH Candidate List, and nobody can quickly say which SKUs and sales channels are affected. Before, the answer meant cross-checking a spreadsheet against ERP exports and marketplace feeds. In projects we implemented, we modeled certificates and declarations as separate records linked to product families, with validity dates and the markets they cover. The impact question then becomes a saved search. It returns the affected variants and the channels they're live on.
The EU Rules That Changed Product Data Requirements
EU product law keeps moving compliance information off paper and into structured data. Each new act adds fields. Some also add new places where those fields must appear.
GPSR: Listing Data As A Legal Requirement
The General Product Safety Regulation (EU) 2023/988 has applied since 13 December 2024. It covers consumer products, and it also applies to products under sector laws for risks those laws don't address.
Article 19 of the GPSR sets the minimum information for any online or other distance-sales offer. The offer must show clearly and visibly:
- The manufacturer's name, registered trade name or trademark, plus a postal and electronic address.
- Where the manufacturer is outside the EU, the name, postal and electronic address of the responsible person in the EU.
- Information that identifies the product, including a picture, its type and any other product identifier.
- Any warning or safety information that goes on the product or with it, in a language consumers easily understand, as set by the member state where the product is sold.
Other GPSR duties also create data. Manufacturers keep technical documentation for 10 years after placing a product on the market. Products carry a type, batch or serial number. Accidents caused by a product go to the authorities through the Safety Business Gateway without delay. Online marketplaces had to register in the Safety Gate portal, and more than 1,200 had done so by the end of 2025.
For a PIM team, the Article 19 fields are mandatory attributes per channel and per member state. The warning text needs the most care. It has to match the physical label and exist in every language you sell in.
If a field is legally required on an online offer, your system should make it impossible to publish the offer without it.
In projects we implemented for manufacturers selling through marketplaces, the GPSR gaps sat more often in operator data than in product data. The responsible person was typed into a free-text field, differently for each channel. Warnings were buried in long product descriptions. We moved responsible persons and warning texts into their own records, linked to products and markets. A warning now gets translated once and reused on every product it applies to. Channel exports check the Article 19 fields and stop a feed that would go out incomplete.
ESPR And The Digital Product Passport
The Ecodesign for Sustainable Products Regulation (EU) 2024/1781 entered into force on 18 July 2024. It creates the legal framework for the Digital Product Passport (DPP). The data each passport must hold comes later, in delegated acts per product group.
The Commission's indicative DPP timeline sets out the sequence. The DPP Registry has been operational since 20 July 2026. The delegated act for iron and steel is expected in Q4 2026. Textiles, aluminium and tyres follow in the second half of 2027, furniture in 2028 and mattresses in 2029. After each act is adopted, companies get a transition period of at least 18 months. As of mid-November 2026, no product-specific ESPR delegated act had been adopted.
The mechanics are already defined. The economic operator gathers the required data and registers the passport. The full data stays with the operator or with a DPP service provider. A data carrier such as a QR code links the physical product to its passport. The registry issues a unique registration identifier, and customs can check it for imported goods. Access depends on the user's role, so consumers, repairers and authorities see different parts of the record.
Other laws carry their own passport rules. Under the Battery Regulation, passports become mandatory on 18 February 2027 for electric vehicle batteries, light means of transport batteries and industrial batteries above 2 kWh. The Toy Safety Regulation (EU) 2025/2509 applies from 1 August 2030, and for toys the DPP replaces the EU declaration of conformity. The Commission also lists construction products and packaging legislation as legal bases for passport requirements.
A passport combines two kinds of data. Model-level data covers material composition, recycled content, repair information, the declaration of conformity, and instructions. Item-level data covers serial numbers and production dates. Batteries add values like state of health. PIM software is the logical source for model-level data, and item-level data usually comes from MES or ERP. A battery passport exists per individual battery, so plan that integration before you choose a DPP service provider.
Your PIM should be the source of model-level passport data. It shouldn't turn into a serial number database.
PPWR: Packaging Gets Its Own Record
The Packaging and Packaging Waste Regulation (EU) 2025/40 has applied since 12 August 2026. Packaging must now carry a type, batch or serial number and the manufacturer's name and postal address, with an electronic contact where available. This can go on the packaging, in an accompanying document or behind a data carrier. Misleading labels and symbols are banned. Packaging also needs its own EU declaration of conformity and technical documentation.
The harmonized sorting label applies from 12 August 2028 or 24 months after the Commission's implementing acts enter into force, whichever is later. Those acts were due by 12 August 2026 and weren't adopted on time. So 2028 is now the earliest possible date.
Model packaging as its own entity, linked to products. A few packaging attributes on the product record stop working once one shipper carton holds several SKUs or one SKU ships in two pack formats.
CRA: Connected Products Get A Support Period
The Cyber Resilience Act (EU) 2024/2847 covers products with digital elements. Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents, including for products placed on the market before that date. The rest of the regulation applies from 11 December 2027.
From then, manufacturers must state the end date of the support period, at least the month and year, at the time of purchase. That's a product attribute. It has to reach every sales channel and possibly the packaging. Firmware versions and software bills of materials stay in engineering tools. The published support period and the link to the declaration of conformity belong in the PIM.
Product Liability Directive: History Becomes Evidence
The new Product Liability Directive (EU) 2024/2853 applies to products placed on the market after 9 December 2026. Software now counts as a product. National courts can order a defendant to disclose relevant evidence once a claimant shows a plausible claim.
So your product data history matters. You need versioned records and an audit log of who changed a warning and when. You also need to reconstruct a listing as it looked on a past date.
EUDR: Know Which SKUs Are In Scope
The EU Deforestation Regulation applies from 30 December 2026 to large and medium companies and from 30 June 2027 to most micro and small companies. Its scope follows the products listed in Annex I by customs code. A PIM can hold the CN code and flag which SKUs fall in scope. Geolocation data and due diligence statement references are batch-level supply chain data, and they belong in ERP or a dedicated traceability tool.
Omnibus IV And The European Product Act
On 9 June 2026, the Council and Parliament reached a provisional agreement on the Omnibus IV digitalisation package. It makes product documentation digital by default across around 20 product laws. Declarations of conformity and instructions can be provided digitally, and where a DPP is mandatory, that information is meant to be accessible through the passport. Check the final published text for application dates.
The Commission's 2026 work programme grouped reviews of the New Legislative Framework, the Market Surveillance Regulation and the Standardisation Regulation under the name European Product Act. At the time of writing, the merged proposal on the NLF and market surveillance was expected by mid-December 2026. Reporting on a leaked draft mentions a horizontal DPP framework with registration before products reach the market, plus a fee on imported products. Drafts change. Plan for the direction and wait for the text before you build anything specific.
How PIM Software Supports A Product Compliance Management System
PIM software holds the product master: attributes, classifications, variants, assets, translations, and channel outputs. Compliance data fits that structure if you model it on purpose.
Model compliance objects as entities. Regulations, certificates, declarations, responsible persons, warning texts, packaging, and substances each get their own records with relations to products. A certificate linked to a product family covers every variant in it. When the certificate expires, a scheduled check flags each linked product and each channel it's published to.
Let classification drive requirements. A product classified as a toy with a button battery triggers specific mandatory attributes and warnings. That logic belongs in classification rules, so it doesn't depend on someone's memory.
Validate per market and channel. A product can be complete for an internal catalog and incomplete for a marketplace listing in France. Measure completeness against the target, and block or flag exports when required fields are missing.
Control who edits what. Field-level permissions keep marketing from editing hazard statements. An approval workflow adds a second check on safety-relevant fields. A change to a warning creates a new version, and the old version stays retrievable.
Collect supplier data as data. REACH Article 33 obliges suppliers of articles to pass on information when an article contains a Candidate List substance above 0.1% by weight. That declaration should arrive as a record linked to the component, with a date and a source document. A PDF in an email thread can't be queried when the Candidate List grows.
Publish from one source. Marketplace feeds, webshop exports, label templates, instruction documents and API calls to a DPP service provider should all read the same approved values.
We develop AtroPIM, an open-source PIM built on the AtroCore data platform. Its data model is configurable, so certificates, responsible operators, warning texts, and packaging can be set up as entities with their own fields and relations to products. Field-level access control and configurable workflows handle governance. Action logs record changes, and the REST API passes approved data to shops and marketplaces. For passports, the Digital Product Passport module syncs approved data, with version history, to a public passport page that people reach by QR code or GS1 Digital Link.
PIM has limits here. It doesn't run risk assessments or manage corrective and preventive actions. Those belong in a QMS or a dedicated compliance tool. It also doesn't watch for new legislation. Someone has to turn a new delegated act into new attributes and rules, usually a regulatory affairs owner or an external service. The PIM then enforces what they define.
Some manufacturers run a dedicated product compliance platform next to the PIM. That setup suits large compliance teams that need case handling and supplier campaigns. The risk is two sources for the same attribute.
Decide which system owns each compliance field and sync it in one direction. Two editable copies of a warning text are how a label and a listing drift apart.
A Practical Data Model To Start With
Most projects we implemented start with a small set of entities and extend from there:
- Product and product family, with a classification that drives required fields.
- Regulation or standard, linked to classifications.
- Certificate and test report, with issuer, validity dates, and covered products.
- Declaration of conformity, versioned and linked to products and regulations.
- Responsible economic operator, per market.
- Warning text, as a reusable and translatable record.
- Packaging, with its materials and its own documentation.
- Supplier substance declaration, linked to components.
Start with one regulation and one channel. GPSR Article 19 on your highest-volume marketplace is a practical first scope, because the required fields are fixed and the gaps show up fast. Then extend the same entities to battery passports or packaging, depending on what you sell. The responsible operator and warning records you build for GPSR carry straight over.
Priorities Before The 2027 Deadlines
Four dates in the next 13 months create direct product data work. The Product Liability Directive applies to products placed on the market after 9 December 2026. The EUDR applies to large and medium companies from 30 December 2026. Battery passports become mandatory on 18 February 2027. The CRA applies in full from 11 December 2027.
If your current setup can't show what a listing said six months ago, fix versioning and audit history first. It supports your liability defense now and every passport later. Then close the GPSR gaps per channel.