DPP Data Architecture & Schema Guide for RMG
Technical specification for CIOs and ERP managers. Master SKU-level DPP data schemas, JSON-LD structures, GS1 Digital Links, and buyer portal integration.
The EU Ecodesign Mandate: Shifting from Flat Files to Live Data Streams
The EU Ecodesign for Sustainable Products Regulation (ESPR) fundamentally changes how garment manufacturers store, process, and transmit product data. Compliance is no longer about emailing PDF certificates or maintaining static Excel spreadsheets. European customs agencies and brand portals now require machine-readable, programmatically verifiable data streams at the individual SKU level.
From Flat Files to Linked Data
Legacy factory workflows rely heavily on disconnected PDFs, email attachments, and isolated ERP spreadsheets. These static formats break down under automated compliance checks. Modern European customs processing engines scan inbound shipments using automated data validation pipelines, not human reviewers reading paper docs. Converting raw operational data into machine-readable JSON-LD payloads ensures every attribute—from fiber origin to wash test results—is instantly parseable.
The Interoperability Requirement
Data cannot sit in a proprietary vacuum. EU customs systems demand cross-platform interoperability through strict adherence to standardized formats: W3C JSON-LD syntax and GS1 Web Vocabularies. Standardized schemas eliminate syntax mismatches across international borders, ensuring data flows into European brand portals without requiring custom payload translation middleware.
System Architecture Overview
Aggregating data across enterprise layers into a unified DPP compilation engine.
Feeds style definitions, base fiber compositions, Bill of Materials (BOM), and design specifications.
Supplies purchase orders, factory location IDs (GLNs), production lot/batch numbers, and assembly timestamps.
Pushes ISO lab test results, REACH SVHC declarations, and ZDHC chemical compliance certificates.
- Section 2: JSON-LD Data Schemas & Syntax Standards
- Section 3: Physical Data Carriers & GS1 Digital Link Architecture
- Section 4: Systems Integration Workflows (PLM, ERP, & QMS)
- Section 5: Data Security, Cryptographic Hashing & Access Control
- Section 6: Operational Implementation & Buyer Portal Interoperability
- C-Suite Strategic Mandate & Technical Action Matrix
SKU-Level Data Taxonomy & Standardized Attributes
Aggregating data at the broad style level no longer satisfies EU compliance standards. Customs officials and brand audit engines inspect individual finished goods. A red polo shirt in size Small produced in Batch A carries different wash shrinkage numbers and dye-lot batch IDs than the same shirt in Navy Blue produced in Batch B. Your system architecture must capture, format, and serialize data down to the Stock Keeping Unit (SKU) level.
Mandatory Data Categories
Building a compliant passport payload requires mapping five core data categories across your ERP, PLM, and laboratory databases.
- Global Trade Item Number (GTIN): 13-digit GS1 identifier mapped to the specific SKU.
- SKU Variant Identifier: Internal factory matrix code defining colorways, size parameters, and fit classifications.
- Factory Location ID: Global Location Numbers (GLN) or GADM codes pinpointing the physical facility where final assembly occurred.
- Production Batch/Lot Numbers: High-granularity identifiers tracing production runs back to specific cutting tables, sewing lines, and operational shifts.
- Fiber Percentages: Precise breakdown of material inputs (e.g., 95% Organic Cotton, 5% Elastane) verified against garment BOM.
- Tier-1 to Tier-4 Declarations: Origin tracking mapping garment factory (T1), mill/dyehouse (T2), spinner (T3), and farm/ginning facility (T4).
- Transaction Certificate (TC) Hashes: Cryptographic hashes or verification codes linking GOTS, OCS, or GRS certificates directly to material lots.
- Dimensional Stability (ISO 6330): Fabric shrinkage and distortion values recorded after 5, 10, or 20 standardized domestic wash cycles.
- Seam Tensile Strength (ISO 13935): Maximum force recorded before seam rupture, measured in Newtons.
- Abrasion Resistance (ISO 12947): Martindale wear breakdown thresholds confirming fabric longevity under repeated friction.
- REACH SVHC Declarations: Verification that Substances of Very High Concern stay below <0.1% w/w.
- Total Fluorine Caps: Analytical proof verifying total fluorine concentration remains below <10 ppm (zero intentional PFAS).
- ZDHC Verification IDs: Validated Level 3 Zero Discharge of Hazardous Chemicals credentials for all wet-processing mills.
Attribute Granularity: SKU vs. Style Aggregation
Style-level aggregation saves database storage but causes compliance failures during customs inspections. When a brand orders a style with three colorways—Garment-Dyed Black, Bleached White, and Enzyme-Washed Indigo—each variant uses radically different wet-processing chemicals and dye formulations.
Grouping these variants under a single style-level passport causes schema validation errors. Indigo wash processing alters tensile strength (ISO 13935) and dimensional stability (ISO 6330) compared to raw white cotton. The database schema must separate data attributes into style-level constants (design pattern, base fabric spec) and SKU-level variables (shade, shrinkage rate, batch number, TC hash).
| Attribute Level | Scope | Attributes Maintained | Compliance Outcome |
|---|---|---|---|
| Style Aggregation (Legacy) | Broad Design Model | Base fabric specs, design pattern, generic BOM. | ❌ Customs Schema Validation Failures |
| SKU Serialization (EU Ready) | Specific Colorway, Size & Batch | Exact GTIN, shade-specific chemistry, batch TC hash, lab test values. | ✔ Instant Clearance & Verification |
JSON-LD Data Schemas & Syntax Standards
Customs engines do not infer meaning from raw JSON key-value pairs. Standardizing payload definitions using W3C JSON-LD syntax and GS1 Web Vocabularies transforms arbitrary database records into semantically unambiguous, machine-readable data.
Context & Vocabulary Mapping
Every DPP payload starts with a @context declaration that maps local JSON keys to universally recognized URIs. A field like fiberComposition lacks semantic meaning to an automated customs parser without a reference point. Mapping attributes to
GS1 Web Vocabularies
and W3C Verifiable Credentials contexts eliminates structural guesswork.
"brand": "Apex" against linked ontology contexts prevents payload rejection caused by minor naming variations across factory systems and eliminates custom translation layers.
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://ref.gs1.org/voc/"
],
"id": "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6",
"type": ["VerifiableCredential", "DigitalProductPassport"],
"issuer": "did:web:dpp.factorydomain.com",
"issuanceDate": "2026-08-30T10:00:00Z",
"credentialSubject": {
"id": "https://dpp.factorydomain.com/01/08801234567896/21/BATCH99281",
"gtin": "08801234567896",
"sku": "TSH-BLK-COT-L",
"productionBatch": "BATCH99281",
"facilityGLN": "urn:gln:8801234567890",
"materialComposition": [
{
"materialName": "Organic Cotton",
"percentage": 95.0,
"tier4Origin": "BD",
"transactionCertificateHash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
},
{
"materialName": "Elastane",
"percentage": 5.0,
"tier4Origin": "CN",
"transactionCertificateHash": "8f4e2a3b1c9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f"
}
],
"physicalDurability": {
"iso6330DimensionalStability": -2.1,
"iso13935SeamStrengthNewtons": 245.0,
"iso12947AbrasionCycles": 15000
},
"chemicalCompliance": {
"reachSvhcPercentage": 0.02,
"totalFluorinePpm": 4.5,
"zdhcVerificationId": "ZDHC-L3-BD-2026-8812"
},
"circularityMetrics": {
"isMonomaterial": false,
"elastanePercentage": 5.0,
"removableTrims": true,
"pcrContentRatio": 0.0
}
}
}Validation Protocols (JSON Schema Draft 2020-12)
Malformed JSON payloads block customs clearance instantly. Implementing client-side and middleware validation via JSON Schema (Draft 2020-12) catches structural errors before data reaches public APIs. Validation logic must enforce strict type constraints, array limits, and numerical bounds.
A fluorine field passing 15.0 ppm triggers an immediate operational block by exceeding the <10 ppm limit.
Missing Transaction Certificate (TC) hashes or invalid GTIN formats halt the build pipeline before serialization occurs.
Physical Data Carriers & GS1 Digital Link Architecture
Connecting physical garments to cloud-hosted passport engines requires standardized web URIs and durable physical data carriers. If an optical scanner or RFID reader fails at an EU port, the entire shipment stalls. Physical encoding standards must guarantee fast readability from the factory floor to the end consumer.
URI Construction Standards (GS1 Digital Link)
Every garment requires a unique web-resolvable address replacing traditional web URLs with standardized GS1 Application Identifiers (AIs).
🔄 Dynamic HTTP Content Negotiation
Accept: application/ld+json receives standard JSON-LD schema instantly.
Data Carrier Selection & Physical Media
Encoding URIs onto physical media demands specific print parameters based on label location, substrate, and hardware.
GS1 Data Matrix
Care LabelsIdeal for woven satin or polyester care labels with extreme space constraints.
GS1 QR Code
Swing TagsPrinted on swing tags or main brand labels for direct consumer engagement.
UHF RFID Inlays
Automated LogisticsEPCglobal Class 1 Gen 2 (ISO/IEC 18000-6C) RAIN RFID tags operating at 860–960 MHz.
Wash Resistance & Scan Reliability Standards
Care label symbols must survive the full garment lifecycle against mechanical friction, hot water, and harsh detergents. Standard wax or wax-resin thermal ribbons degrade in under 10 wash cycles, breaking traceability.
Factories must mandate full-resin thermal transfer ribbons bonded to wash-resistant synthetic satin substrates (ISO 6330 compliant).
Printed 2D symbols must maintain an overall grade of Grade B (3.0/4.0) or higher after 50 industrial wash cycles at 60°C.
Systems Integration Workflows (PLM, ERP, & QMS)
Extracting data from isolated factory databases and assembling it into a compliant JSON-LD payload requires an event-driven integration architecture. Most RMG facilities run heterogeneous software environments: legacy SQL-based ERPs, cloud PLM suites, and standalone desktop QMS software. Systems integration transforms these disconnected operational silos into an automated DPP assembly line.
Data Extraction Architecture
Legacy ERP databases store operational records across disparate relational tables. Extracting compliance-ready datasets requires building dedicated staging views and Extract, Transform, Load (ETL) pipelines rather than querying live production databases directly.
Map master material tables (MARA), Bill of Materials (STPO), and POs (EKPO) directly to schema properties. Convert internal codes to standard GTINs.
Resolve inconsistent free-text inputs (e.g., "100% Organ. Cotton" or "Org Cot") to the standardized value "Organic Cotton" under GS1 vocabularies.
Pull ISO test results tied to specific fabric batches. Missing lab records automatically halt ETL execution and flag the SKU for manual verification.
API Gateway & Webhook Triggers
Static scheduled batch jobs introduce latency. Modern architecture leverages an event-driven publish-subscribe model managed by an API Gateway.
[Packing Station / Scan]
│ (Webhook: Goods Packed)
▼
[API Gateway] ──(Orchestrates Requests)──► [PLM Database] (BOM / Styles)
│ ► [ERP Database] (Lots / GLNs)
│ ► [QMS Database] (ISO / REACH)
▼
[DPP Compilation Engine] ──(Validates & Hashes)──► [JSON-LD Passport]packing_list_completed event.EU Central Information Register (CIR) Synchronization
Once serialized, the DPP engine registers the passport payload with EU Central Information Register (CIR) endpoints to grant customs clearance authority.
Mutual TLS (mTLS) with X.509 digital certificates and OAuth 2.0 bearer tokens issued by EU registry identity providers.
Pre-shipment submission to CIR staging endpoints for structural validation and GTIN/Serial uniqueness checks.
HTTP Status Acknowledgment Protocols
Handling Offline Supplier Nodes (Tier-2 & Tier-3 Integration)
Tier-2 dyeing mills and Tier-3 spinning partners often lack native REST APIs or modern ERP infrastructure. To avoid waiting for supplier IT modernization, implement a secure web-based Supplier Data Portal:
Sub-contractors upload Transaction Certificates (TCs), yarn origin declarations, and lab test reports via pre-validated templates.
In-browser schema validation catches incorrect ZDHC IDs or bad formatting instantly before data touches core databases.
Time-bound, single-use links tied to PO numbers mandate compliance upload before raw material deliveries are marked accepted in ERP.
Data Security, Cryptographic Hashing & Access Control
Exposing internal enterprise data to public web requests creates severe security risks. Unsecured endpoints leak supply chain networks, costing models, and fabric engineering secrets directly to commercial competitors. Your system architecture must grant full transparency to EU regulators while strictly protecting proprietary operational data.
Role-Based Access Control (RBAC) Architecture
Not all users require the same data access depth. Implement strict Role-Based Access Control (RBAC) at the API gateway layer using OAuth 2.0 scopes and JSON Web Tokens (JWT).
[Incoming Request]
│
▼
[API Gateway / Auth Engine]
│
├── Scopes: public:read ──► [Consumer View] (Basic Fiber Composition, Eco-Label, Care)
└── Scopes: customs:auth ──► [Regulator View] (Full ISO Lab Reports, Unmasked Batches, REACH IDs)scope: public:read
Smartphone scans from consumers query unauthenticated endpoints. Returns basic sustainability metrics, fiber breakdowns, care instructions, and end-of-life recycling guidance.
scope: customs:auth
EU customs agents present authenticated X.509 certificates via mTLS. Gateway returns unmasked objects including raw ISO lab reports, factory GLNs, and full REACH declarations.
Commercial Confidentiality & IP Protection
Disclosing exact Tier-3 yarn spinners or proprietary dye formulations exposes factories to disintermediation and IP theft.
Replace sensitive supplier identities with salted cryptographic hashes in public-facing schemas. Authorities verify the authenticity of a Transaction Certificate (TC) via hash matching without revealing vendor names publicly.
Convert exact fabric processing recipes into standardized compliance bounds. Log mandatory REACH SVHC status (<0.1% w/w) and ZDHC verification IDs rather than disclosing full chemical auxiliary formulas.
Cryptographic Data Integrity & Seal Generation
Finalized passports must remain tamper-proof once a shipment clears customs. Generate a SHA-256 cryptographic hash seal of the compiled JSON-LD payload immediately after factory packing validation:
[Compiled JSON-LD Payload] ──► (SHA-256 Hashing Algorithm) ──► [32-Byte Digest String]
│
(Appended to Header)10-Year Storage & Archival Architecture (EU ESPR Article 9)
Article 9 of the EU ESPR regulation mandates that every product passport payload remains active and retrievable for 10 years after product placement. Configure cloud storage buckets using Write Once, Read Many (WORM) policies.
Set retention policies (AWS S3 Object Lock / Azure Blob Immutable Mode) to Compliance Mode. Blocks all users—including root database admins—from deleting or overwriting stored JSON-LD objects during the 10-year window.
Move passports from Hot Storage to Cold Archival Storage (e.g., Amazon S3 Glacier Flexible Retrieval) after 365 days of inactivity while maintaining active resolution via edge caching.
Operational Implementation & Buyer Portal Interoperability
Deploying a Digital Product Passport infrastructure across an active garment factory requires a phased, risk-managed timeline. Attempting a single-stage system cutover across live production lines risks halting shipments. A structured 16-week implementation plan ensures that software pipelines, factory hardware, and external buyer APIs align before commercial production begins.
Phase 1: Systems & Schema Mapping
Weeks 1–4Initial execution focuses on auditing existing IT assets, identifying database gaps, and establishing data governance rules.
Map required EU ESPR attributes against ERP, PLM, and QMS fields. Identify missing datapoints early, such as absent TC hashes or missing ISO dye lot reports.
Enforce MDM rules to eliminate free-text entries in purchase orders. Standardize fiber naming, facility GLNs, and chemical test metrics across modules.
Define data requirements for Tier-2 mills and Tier-3 spinners. Issue standard template specs for the Supplier Data Portal to handle offline inputs.
Phase 2: Middleware & Carrier Integration
Weeks 5–10The second phase constructs the technical middleware layer and connects physical printing hardware on the factory floor.
Build REST APIs, webhooks, and extraction scripts. Configure the central DPP engine to compile attributes automatically upon packing events.
Install 300 DPI thermal transfer printers for satin care labels. Mount inline optical verifiers to grade GS1 Data Matrix symbols in real time.
Integrate UHF RFID encoder modules into carton packing lines to write GS1 Digital Link URIs to EPC memory banks during bulk packing.
Phase 3: Sandbox Testing & Buyer Portal Alignment
Weeks 11–16The final phase validates data pipelines end-to-end through simulated buyer portal submissions and customs agency sandbox environments.
Scan cartons, verify automatic JSON-LD payload creation, confirm SHA-256 hash seals, and check WORM cloud bucket archival.
Transmit test payloads to brand portals and mock EU CIR endpoints. Validate OAuth 2.0 authentication and status code acknowledgments.
Subject test labels to 50 industrial wash cycles (ISO 6330). Confirm post-wash Grade B (3.0/4.0) optical readability under ISO/IEC 15415.
C-Suite Strategic Mandate & Technical Action Matrix
Deploying an enterprise-wide Digital Product Passport infrastructure requires coordinated execution across executive, technical, and operational divisions. The following matrix outlines non-negotiable directives for key department leads to guarantee system compliance ahead of EU regulatory deadlines.
💻 CIO & IT Leadership Directives
Infrastructure & SecurityProvision cloud storage buckets configured with WORM policies for the ESPR Article 9 10-year data retention mandate. Upgrade edge compute hardware at packing stations for zero-delay serialization.
Deploy API gateways enforcing OAuth 2.0 authorization and Mutual TLS (mTLS) backed by X.509 digital certificates to lock down external communications with EU endpoints.
Map internal data tables to W3C JSON-LD and GS1 Web Vocabularies. Build compilation engines that apply SHA-256 cryptographic hashing prior to passport distribution.
🗄️ ERP Manager Directives
Data & Batch OperationsExtend legacy ERP database tables to capture compliance parameters. Add mandatory system fields for ZDHC verification IDs, REACH SVHC declarations, and Transaction Certificate (TC) hashes.
Enforce granular lot tracking across enterprise modules. Every production order must tie directly to specific cutting tables, dye lots, and sewing lines rather than generic style records.
Construct automated ETL staging views that extract parameters without locking transaction databases. Execute stress tests across packing webhooks to withstand peak-volume carton scans.
📦 Merchandising Lead Directives
Sourcing & ComplianceEliminate free-text entry across Bills of Materials (BOM). Force teams to select fiber names and material specifications directly from dropdown lists aligned with GS1 taxonomy.
Update supplier POs with binding data transparency clauses. Mandate that Tier-2 dyeing mills and Tier-3 spinners submit lab reports and TCs via the Supplier Data Portal before payment.
Audit physical ISO test metrics and chemical certificates prior to releasing orders for packing. Incomplete dataset submissions must automatically block variable-data care label printing.
Need Custom Implementation Strategy For Your Factory?
While these whitepapers provide universal frameworks, implementing them within your facility requires custom operational mapping. Schedule a technical consult to evaluate your enterprise readiness.
Book a Technical Consultation with Zahirul Islam →