Key points at a glance
- Every row needs a stable product or variant identifier.
- Document column names, units and allowed values.
- Report import errors separately and never discard them silently.
Build an importable template
Use keys such as SKU, GTIN or internal ID, stable field codes, explicit units, language and country codes, and a defined format for dates and multiple values.
Map and validate
Map each column to a target field and validate required values, types, ranges and references before showing which records were created, updated or rejected.
Make updates repeatable
Reuse the same keys for later imports and keep import, expert review and public release as separate steps; a pilot can later move to CSV, JSON, XML or an API.
Frequently asked questions
Can an existing workbook be imported unchanged?
Sometimes, but most files need one-time mapping or cleanup to establish unique identifiers and consistent values.
Are imported values published immediately?
They should remain a draft until an explicit approval creates a public passport version.
Official sources
Applicable legal acts and official publications govern legally relevant decisions.
As of: 17 August 2026. This guide provides general information and is not legal advice or a compliance guarantee.
Turn product data into a controlled product passport.
Import existing data, validate completeness and publish approved versions through a stable QR address.