Digital product passport: start collecting the data today

Data you can collect today for the digital product passport: batch or unit identity, production records, supplier documents, and bringing them into one source.

The part of digital product passport preparation you can do today is recording, at the time of production, the data the passport will rely on: the product's identity, which batch it came from, and which raw materials and facility it was made with. If this is not written down at the time, it cannot be reconstructed later. The format of the passport and the fields it must contain are set by the rules adopted for each product group; the data can start building up now.

In most organisations the discussion starts with the date it becomes mandatory. For preparation, the more useful question is which data could be produced retroactively once it does. A document can be prepared later. Which supplier a batch's raw material came from cannot be known if it was not recorded that day.

What groups of information does a passport carry?

They vary by product group, but the information can be grouped under four headings:

HeadingExample informationWhere it sits in the plant today
IdentityProduct, batch or unit number and a scannable data carrierLabel and production record
CompositionRaw materials, material ratios, recycled contentBill of materials, quality file
OriginProduction facility, batch, date, supplierProduction and purchasing records
Use and end of lifeMaintenance, repair, disposal informationUser manual, technical file

Identity is the heading everything else attaches to. Information held in the production record, the quality file and supplier documents cannot be carried into a passport unless it is linked to the number on the product.

What can be done today?

Decide the identity level and start numbering. Your label may carry only the product barcode today. Putting a batch or unit number on the label and into the production record creates the key that all other information attaches to.

Match production records to the number. Which batch was made on which date, on which line and with which raw material lots is already written down in most plants. What is missing is that this record sits in the same place as the number on the product.

Link supplier documents to batches. Analysis reports, certificates of origin and declarations of conformity mostly sit in folders or email attachments today. Under Annex III of the ESPR, a passport can include compliance documents such as the declaration of conformity, technical documentation or certificates; the product group's act decides which ones. Keeping these documents linked to the relevant batch from today makes the transfer easier when that day comes.

What happens if the data is scattered?

Most of the information a passport asks for already exists in the plant; the problem is that it is scattered. The same bill of materials is kept separately in the quality file, the supplier contract and the label approval, and the copies drift apart over time. The first task in preparing is to link what already exists to a single source before collecting anything new. Unlinked data gets compiled by hand when the obligation arrives, and has to be compiled again with every update.

At which product level should it be kept?

Whether the passport is kept at model, batch or unit level is set by the rules for the product group. The level at which you collect your own data is a decision you can make today:

  • Model level is enough for information that does not change across the same product.
  • Batch level is needed when raw materials or production conditions change from batch to batch.
  • Unit level is needed if recalls, repairs or hand-overs of individual products are to be recorded.

If the number structure is designed from the start so that it can extend to unit level, you can begin at batch level and move to units when needed.

When is the passport updated?

Some information changes over the product's life: repair, resale, recycling. If it is not decided up front who may update the record and how earlier versions are kept, the passport gradually drifts away from the product's actual state.

Identity and records in Tagvex

Tagvex gives each product, or each batch, its own number, and batch numbering can later move to unit level. The number fits into the existing label layout, every hand-over from line exit to dealer is collected in the same record, and records connect to ERP and warehouse systems through the API. That record can feed the identity and origin information of a passport; the passport's content and format are prepared separately under the applicable rules.

Sources

Meeting request

The right numbering level for your product is set through a needs analysis.

The first meeting reviews your product, sales channels and the risks you face, and recommends a suitable method.

Request a meeting