Digital product records are turning product data into board evidence.

Across eight days in July, two quiet official notices changed the practical meaning of product data for UK manufacturers.

On 20 July 2026, the European Commission said the Digital Product Passport Registry and testing environment were operational. On 27 July, the UK Government opened a call for evidence on digital product records policy, asking businesses how digital product records could affect goods sold in the EU, Northern Ireland and Great Britain.

The first statutory pressure point is specific. EU battery-passport rules apply from 18 February 2027 to electric vehicle batteries, light means of transport batteries and industrial batteries over 2 kWh. Other product groups will follow through product-specific measures and transition periods.

In brief.

• The EU DPP Registry became operational on 20 July 2026.
• The UK opened its digital product records call for evidence on 27 July 2026, with responses due by 21 September 2026.
• The first hard deadline sits with named battery categories on 18 February 2027.
• Great Britain's domestic route is still open, while EU DPP requirements apply in Northern Ireland under the Windsor Framework.
• The useful board action is an Evidence Spine Map: rule source, evidence field, owner, system of record and divergence point.

Why this is an evidence-control problem.

A Digital Product Passport is the EU's mechanism for attaching product information to a product through identifiers, data carriers and accessible records. The European Commission describes the Registry as part of a decentralised system: the Registry stores unique identifiers and metadata, while detailed product data is held elsewhere by the responsible economic operator or its provider.

That architecture matters. The product record is a chain of evidence, identifiers, systems and owners.

The UK call for evidence makes the same point from the other side. It asks businesses about product composition, supply-chain information, environmental information, repair and maintenance, end-of-life information, certification and unique identifiers. It also asks about IT integration, supplier-held data, interoperability and the possible impact of separate GB, NI and EU rules.

The board issue is whether the business can prove what the product is, what it contains, where the evidence came from and which route the product is being sold through.

The traceability lens.

We treated digital product records as a requirements traceability problem. That is a plain control method: map each rule to the evidence it asks for, the owner of that evidence, the system where it lives, the timing attached to it and any place where rules may diverge.

For this issue, five columns matter most.

First, rule source. A product may face EU Digital Product Passport rules, Northern Ireland application under the Windsor Framework, future Great Britain policy, sector regulation or a customer requirement that borrows from those standards.

Second, evidence field. The data may be composition, origin, material content, compliance certification, repair information, environmental performance, end-of-life handling or a unique identifier.

Third, evidence owner. Some evidence sits with engineering, quality, compliance, procurement, logistics or finance. Some sits with a supplier. Some may sit with a service provider.

Fourth, system of record. The current version may live in an ERP field, a quality file, a supplier declaration, a certificate library, a spreadsheet or a product-data platform.

Fifth, divergence point. The important question is where GB, NI and EU routes could ask for different proof, timing, carrier format or access control.

That is why waiting for every final rule can create its own risk. The specific obligation can remain open while the evidence trail is already ready to map.

What the official evidence says.

The UK Government is still gathering evidence before deciding the Great Britain domestic approach. The call explicitly asks whether the UK should prioritise a single interoperable data carrier, how separate GB and NI rules could affect businesses, and how separate GB and EU rules could affect exporters.

It also says EU DPP requirements will apply in Northern Ireland under the Windsor Framework. That creates a practical split for businesses that sell the same product family across Great Britain, Northern Ireland and the EU.

The EU side is moving from framework to infrastructure. The Commission says the DPP Registry is live. Ecodesign for Sustainable Products Regulation materials show product-specific obligations rolling out through delegated acts, with a general transition period of at least 18 months after those acts come into force. Battery legislation provides the first hard deadline.

The evidence points in one direction: the next useful board conversation is about evidence ownership.

A simple example.

Take a UK manufacturer selling one product family across Great Britain, Northern Ireland and the EU. The product contains a battery pack and several supplier-held material declarations. Quality owns compliance certificates. Procurement owns supplier declarations. Engineering owns composition data. Logistics owns route and market documentation. Finance owns the commercial case for keeping all three sales routes open.

Even while the final Great Britain rule is open, that business can ask a better question today:

Can we show, product by product, which evidence field is required, who owns it, which supplier it depends on, where the current version lives and which route could trigger a different requirement?

A missing answer is a product-data control gap, with software choice downstream.

What to put on the board agenda.

The useful first artefact is an Evidence Spine Map.

List the product families most likely to be touched by EU, NI or future GB digital record rules. For each, map the rule source, evidence field, internal owner, supplier dependency, system of record, date or trigger and confidence level.

The exercise does three useful things.

It separates near-term deadlines from broader readiness work. Batteries are immediate for the named categories. Other product groups need monitoring, with timing caveats kept visible.

It exposes handoffs. Product evidence rarely lives in one function. A future digital record can fail because supplier data is missing, quality certificates are stale, identifiers are inconsistent or the update cycle is ownerless.

It puts evidence control before software choice. A platform can help only when the business knows which evidence it is governing.

Red flags.

• Product evidence sits in local folders or supplier emails outside a governed source.
• Procurement holds supplier data, but quality or compliance owns the future declaration.
• The same product family is sold into GB, Northern Ireland and the EU with different internal records.
• Battery components or adjacent product lines are treated as a future issue before the 18 February 2027 scope has been checked.
• The regulation name is known before the evidence owner is named.
• IT is being asked to solve the problem before the commercial route and evidence owners are mapped.

The management test.

Digital product records are becoming a test of evidence control.

Before the UK consultation closes on 21 September 2026, a product business should know whether its product evidence is controlled well enough to answer different rules from the same governed spine.

The board question is simple: if a customer, regulator or importer asks for the product record tomorrow, who owns the proof?