Why architecture comes before data collection
Product-pass data must be collected, but also remain addressable, versioned and role-based over time. ESPR Article 10 connects the data carrier to a persistent unique product identifier; the concrete data scope depends on the applicable delegated act.
A reliable architecture separates product identity, evidence, access rights and publication logic. Teams can then add product groups later without rebuilding every passport.
Architecture decisions in the project
Nulara reviews which identifier level, resolver strategy and API structure fit your product portfolio.
- Identifiers: Model, batch or serial level; GTIN, GLN or other eligible identifiers in connection with existing systems.
- Data carriers: QR code, GS1 Digital Link or other data-carrier options depending on product, packaging, label and scan context.
- Access rights: Public, authority, partner and internal data views with traceable roles and approvals.
- Versioning: Changes to evidence, material data and required fields remain auditable instead of being overwritten.
Consulting outcome
- Target architecture for product identity, resolver and data objects
- Mapping between ERP, PLM, PIM, QMS and Nulara
- Role and access concept for product-pass data
- Integration plan for APIs, uploads and supplier data
Sources and next steps
Data architecture consulting combines regulatory requirements with technical standards for identifiers and credentials.
Nulara deep dives
- GS1 Digital Link - Identifier and resolver foundations for DPP access.
- JSON-LD / Verifiable Credentials - Structured, verifiable product-pass data for systems and evidence.
- Traceability - Use case for batches, serial numbers and event data.
Primary sources
- GS1 Digital Link standard - Official standard for GS1 identifiers as web URIs.
- W3C Verifiable Credentials Data Model 2.0 - Technical framework for verifiable digital evidence.
DPP data architecture FAQ
- Is GS1 Digital Link mandatory?
- Not universally. GS1 Digital Link is a practical standard when GS1 identifiers are already used. The right choice depends on product group, data carrier and delegated act.
- Can Nulara keep existing ERP or PLM systems in place?
- Yes. The architecture work is designed to connect existing systems and structure product-pass data as a compliance layer instead of migrating everything.
- When should APIs be planned?
- Once the data objects, roles and update processes are clear. Before that, APIs often become point exports rather than reliable product-pass infrastructure.