Export Structured Product Data for Digital Product Passports

Every document processed through SpecMake produces structured JSON internally — properties, values, units, and test standards organized into sections. The JSON-LD export takes this structured data and maps it to schema.org's Product type, the vocabulary that DPP systems and search engines already understand.

The mapping works like this: each extracted property becomes a PropertyValue with its name, value, unit, and the section it came from. Product identifiers — manufacturer, model number, GTIN, catalog number — map to their dedicated schema.org fields. The result is a file that any system expecting linked data can consume directly, without custom parsing or field mapping.

This is the same format used by EU Digital Product Passport infrastructure. Rather than building a separate DPP data pipeline, manufacturers can use their existing spec sheets as the data source — SpecMake handles the extraction, structuring, and format conversion.

DPP records need to identify the specific product they describe. SpecMake's extraction engine automatically identifies product metadata from the document: manufacturer name, model designation, catalog or article numbers, GTIN/EAN barcodes, and the document's own publication code.

The system distinguishes between product identifiers (what a customer orders) and document identifiers (the spec sheet's own part number). A Bosch Rexroth valve datasheet has a model number (4WRPEH 6), an ordering code (R901234567), and a document number — all different identifiers serving different purposes in a DPP record.

These identifiers flow directly into the JSON-LD output as schema:manufacturer, schema:model, schema:gtin, and schema:productID — the fields that DPP registries use to link documentation to a specific product.

The Ecodesign for Sustainable Products Regulation (ESPR) mandates Digital Product Passports for products sold in the EU market. The central DPP registry goes live in July 2026. Category-specific requirements follow:

• Batteries: Under the Battery Regulation (EU) 2023/1542, DPP required from February 2027. Includes capacity, cycle life, material composition, and safety data — much of which already lives in existing spec sheets.
• Construction products: Revised CPR requires structured, multilingual Declarations of Performance from January 2028. EN standard test data, fire classification, and mechanical properties must be machine-readable.
• Textiles, electronics, furniture: Delegated acts expected 2027–2028, with implementation windows varying by category. All will require structured property data linked to product identifiers.

The common thread: every DPP category needs the same foundation that SpecMake already produces — structured properties with values, units, and standards, linked to identified products, in machine-readable format.

The practical value is the workflow: upload a spec sheet you already have, and get back structured data in the format DPP requires. No manual data entry into a separate system. No mapping spreadsheets between your documentation and a compliance schema.

SpecMake's quality audit runs automatically on every upload, catching missing values and contradictions before they reach a DPP record. If your spec sheet says one thing in the summary and another in the data table, you want to know that before submitting structured data to a compliance registry — not after.

For companies managing product portfolios across multiple EU markets, the multilingual translation pipeline means the same structured data can be exported in any of 14 languages. DPP requirements include multilingual product information for the markets where products are sold — a single upload produces both the machine-readable data and the translated documentation.