Getting supply chain data ready for the digital product passport means, first of all, knowing what data you have, where it lives, who owns it and how reliable it is. The software comes later. This checklist takes you through eight steps, from taking stock of your master data to choosing what to make public, with an eye on what the EU ESPR regulation requires.
Why start from the data
Regulation (EU) 2024/1781, known as ESPR, requires that for products covered by a delegated act the digital product passport holds data that is accurate, complete and up to date [1]. Which data, at which level (model, batch or individual item) and who can see it is set by the delegated act for each product group [1]. The list of possible data is in Annex III of the regulation: unique product identifier, GTIN, customs codes, conformity documents, instructions and warnings, manufacturer and importer details, operator and facility identifiers [1].
Even if the delegated act for your sector is not out yet, you already use this data: on labels, in technical sheets, in answers to customers abroad. Putting it in order now saves you time later.
1. Product master data
For each product, collect:
- trade name and internal code;
- GTIN, if you use one (the number under the barcode [3]);
- category and, if you export outside the EU or import, the customs code;
- composition or ingredients, with percentages where needed;
- unit of measure and sales formats;
- photos and an up-to-date technical sheet.
A tip: decide once and for all which code identifies the product across every file. If the same cheese is “CAC-01” in production and “Caciotta 500g” in accounting, you will have to rebuild the link by hand every time.
2. Suppliers and partners
- company name, VAT number, address;
- what each one supplies (raw material, packaging, contract processing);
- supplier certifications and their expiry dates;
- data contact: who sends you information on incoming batches.
ESPR refers to a unique operator identifier, a string that identifies a player in the value chain [1]. If your partners already have a GS1 GLN, which identifies companies and locations [4], note it down.
3. Sites and facilities
- plants, warehouses, collection points, with addresses;
- what each site is for (production, ageing, packing);
- main equipment, if it appears in the batch history (cold rooms or boilers, for example).
ESPR also provides for a unique facility identifier for locations in the value chain [1].
4. Batches and processing
This is usually where most of the gaps are.
- how a batch code is created and who assigns it;
- which incoming batches each outgoing batch comes from;
- the processing steps, with date, site and quantity;
- sales: where each batch goes.
Run a concrete test: take a batch sold last month and try to trace its history back to the raw materials. Note where you get stuck and why. Those points are your to-do list.
5. Documents and certifications
- product and process certificates, with issuing body and expiry date;
- laboratory analyses per batch;
- supplier declarations;
- safety data sheets, instructions for use, warnings.
For each document, note what it refers to: the whole company, a site, a product or a single batch. A company certificate and a batch analysis do not belong in the same place.
6. Who owns each piece of data
Fill in a simple table:
| Data | Who produces it | Where it is today | How often it changes |
|---|---|---|---|
| Product master data | Quality department | Shared Excel file | Rarely |
| Production batches | Production manager | Management system | Every day |
| Analyses | External laboratory | PDF by email | Per batch |
| Supplier certificates | Purchasing | Network folder | On expiry |
It serves two purposes: knowing whom to ask when data is missing, and understanding which data will need frequent updates (and is therefore worth loading automatically) and which once a year.
7. Formats: Excel yes, but tidy
Most SMEs start from Excel sheets, and that is a good starting point if you follow a few rules:
- one row per item: one product, one batch, one supplier;
- one column per field: no “500 g - organic - IT” in the same cell;
- no merged cells and no multi-row headers;
- dates in a single format (DD/MM/YYYY, for example) and numbers without units inside the cell;
- codes as text, so Excel does not strip the leading zeros from a GTIN;
- one sheet per table: products, sites, suppliers, batches.
If you have a management system, ask your vendor which exports are already available. The data is often there, but nobody has ever extracted it in this form.
8. Data quality: the minimum checks
Before loading anything:
- mandatory fields filled in;
- no duplicates (the same supplier written two ways);
- consistent codes across files (the batch you sold exists in production);
- plausible dates (no sale before production);
- documents not expired.
Wrong data in a public passport is worse than missing data: customers, distributors and authorities all read it.
Privacy, field by field
Not everything you record has to become public. For each field, decide:
- public: visible to anyone who scans the QR code (origin, production date, certifications);
- confidential: for you or for those with access rights (suppliers, prices, recipes, quantities).
ESPR itself provides that access to passport data can differ by type of party, according to the delegated act [1], and that customers’ personal data must not go into the passport without their explicit consent [1].
Watch out for personal data in the GDPR sense: operator names, signatures, data on small producers who are natural persons. The GDPR requires processing only data that is adequate, relevant and limited to what is necessary [2]. If a piece of personal data is not needed for the passport, leave it out.
Frequently asked questions
Do I have to wait for my sector’s delegated act to start?
No. Products, sites, suppliers, batches and documents are needed anyway. The delegated act will say which fields become mandatory and at which level [1].
Is Excel enough or do I need a management system?
Excel is fine for master data, as long as it is tidy. For day-to-day batches, a system that records processing as it happens, or an automatic link to your management system, works better.
What do I do if a supplier will not give me the data?
Put them on a list and ask for the data in a structured form, with the same template for everyone. Meanwhile, record what you have and note what is missing.
Is the GTIN mandatory?
ESPR lists it among the data a delegated act can require [1]. If you sell through large retail chains you already use it; for the passport QR code, read the guide on GS1 Digital Link.
How DPP helps
DPP imports master data from Excel with guided templates and row-by-row checks (Basic), as well as operational data such as batches and processing steps (Advanced); with Enterprise, data arrives from your management system via API. Every piece of data starts out private and you decide, field by field, what to show in the passport. See the pricing.