How to map product data for a digital product passport
Short answer
Choose a local CSV, XLSX or flat JSON product file, select its sheet/header, review and confirm suggested mappings, then correct records and inspect missing or conflicting values. Export the working data with provenance for the next preparation step.
- Choose a working profileUse the generic profile for basic product records or the battery preparation profile for chemistry and Wh capacity. These profiles are Utilumo working formats, not exhaustive product-specific legal schemas. Confirm the applicable legislation separately.
- Inspect the file structureSelect the intended XLSX sheet and header row. CSV row locations refer to parsed records with source-line information; JSON records retain their source keys/pointers. The importer handles one file at a time and applies visible size and row limits.
- Confirm every mappingSuggested mappings use heading aliases, not an external AI service. Reassign ambiguous columns or ignore irrelevant ones. Confirm before producing records. Unit-bearing fields need the stated units; the tool does not infer a scientific carbon calculation or verify certificates.
- Correct and export with contextFill missing values and resolve conflicting columns. Original sources remain attached to corrected values. Review duplicate identifiers before export. JSON retains structured sources; CSV contains source metadata and protects formula-like cells. Export an issue report for unresolved items.
Preparation is one part of the passport workflow
Under the ESPR, product-specific delegated acts determine DPP information and implementation requirements. Batteries have separate legislation: Article 77 provides the passport date of 18 February 2027 for LMT batteries, industrial batteries above 2 kWh and electric-vehicle batteries. A local working-data export does not provide ongoing hosting, access rights, identifiers or legal validation.