Identity model
Define the product, batch, serial or component identity and how it remains unique across the required lifecycle.

Plan the physical identifier, product data, lifecycle events and system interfaces needed to connect manufactured items with trusted digital information.
The EU Digital Product Passport framework is intended to make specified product information accessible across value chains. Exact obligations, data fields and timing are set through product-specific rules, so manufacturers should avoid treating one generic QR-code project as a complete compliance solution.
Oxford Traceability focuses on the operational layer: creating a durable identifier, associating it with the correct product or batch, validating the carrier, exchanging data with production systems and retaining evidence that the right identity was applied.
A robust implementation connects four layers while keeping ownership, validation and change control clear.
Define the product, batch, serial or component identity and how it remains unique across the required lifecycle.
Select QR, Data Matrix, label, direct mark or RFID around product material, space, environment and expected life.
Map required data fields, sources, access rights, updates, retention and the service that resolves an identifier.
Create, apply, read back and record the identity at the correct manufacturing step with exception handling.
The technical project becomes clearer when regulatory interpretation, data ownership and line implementation are separated but coordinated.
Confirm whether the product is in scope, the relevant delegated act, required dates, identifier and data obligations.
Identify authoritative product, material, compliance, service and lifecycle information plus the system that owns each field.
Test mark or label durability, code size, contrast, verification grade and scanning across manufacturing and downstream use.
Integrate identity generation, line control, data services, read-back, commissioning evidence and ongoing change management.
Requirements vary by product, market and customer specification. Confirm the current rules that apply to your project.
Practical answers to common buying and implementation questions.
No. The EU framework is implemented through product-specific requirements and timelines. Manufacturers should confirm whether their product group is in scope and which delegated rules apply.
No. The code is a data carrier. A complete implementation also needs a stable identifier, trusted data, access rules, a resolving information service and production controls that apply the correct identity.
Often yes. Existing serial, batch, genealogy and product-information systems may provide useful foundations, but identifiers, data fields, access and retention still need to be mapped to the applicable requirement.
Yes. Projects can cover label or permanent-mark creation, barcode or RFID reading, verification, PLC handshakes, serialisation and interfaces to agreed product or manufacturing data systems.
Share the product group, target market, proposed carrier, identity level and current data systems. We will help define the marking, reading and integration workstream.