Custom app for the digital product passport
A product passport that only exists in a system is not a passport. It has to be attached to a physical item and still be retrievable years later by someone who doesn't know your system. That linking happens on the production line, in the warehouse or with the installer, usually with gloves on and without a reliable connection. That takes an app, not a screen.
Why the physical side is the hard part
The ESPR, Regulation (EU) 2024/1781, will soon require a digital product passport for each product group, reachable via a data carrier on or with the product. Which data it must contain will be set per product group in delegated acts that have not yet been published. What those acts do not change is the act itself: someone has to apply a code and link it to the right item.
That is exactly where it goes wrong. Printing a code is easy; linking it to the right serial number, the right production batch and the right moment is not. If that happens afterwards from a list, mix-ups occur that you only discover years later, when someone scans a passport and sees the wrong product.
The second half is just as practical. A passport is not created once and then forgotten. An engineer adds a repair, a recycler reads the composition, a returns department checks whether this item is yours. All of these moments are mobile, and many of them happen in places without coverage.
How we build this
The link between code and item is the core. If it is right, the rest is a matter of display; if it is wrong, every passport is suspect.
At the end of the line, at the packing table or at goods-in. We look at how many seconds there are, what someone is wearing and where it goes wrong when there is a rush. That shapes the design more than the regulation does.
A scan that hits the wrong item is worse than no scan. We build confirmation and checks into the moment itself, because correcting afterwards means a passport has already left the building.
The app works offline and synchronises later, with a visible status per item. An app that stalls on a poor connection gets bypassed on the floor, and then nobody links anything any more.
We test not only applying the code but also finding it again: someone scans a three-year-old product and must get the right passport. That scenario exposes errors that stay invisible during linking.
What the app actually does
The app does little, and that little must always work. Which components you need depends on where in the process linking and reading take place.
Linking a data carrier to an item
Scan the code and the serial number or batch, and the app records the link with a timestamp and the employee. When in doubt, it refuses instead of guessing, because a wrong link is something you only discover years later.
Reading the passport on site
Scan a product and see the passport as the relevant role is allowed to see it. An engineer sees components and repair history, a returns employee sees origin and warranty.
Working fully offline
Linking and reading carry on without a connection; the app synchronises when there is coverage again and shows per item whether it has been processed. In warehouses and factory halls this isn't a luxury but a prerequisite.
Capturing photos and condition
On intake, return or repair, you need an image of the actual condition. The photo is attached to the item and not to a separate file, so it stays with the passport.
Reporting deviations immediately
A code that cannot be read, an item without a passport, a batch that does not match. Reporting at the moment itself works; a note that is retyped later does not.
Adding events to the passport
Repair, component replacement, change of ownership. Every event comes with who, when and where, so the passport tracks the item's whole life and not just its factory settings.
Who we build for
Where the app is used differs greatly by position in the chain. Four situations.
At the end of the production line
This is where the passport is created and linked to the item. There is little time per item, and the mistake you make here travels with the product throughout its entire life.
Warehouse and distribution
At goods-in and goods-out it must be clear which item is going where and whether the passport goes with it. If your stock runs through an integrated warehouse system, the app connects to it rather than sitting alongside it.
Engineers and maintenance
Outdoors, in a technical room or on a roof. The engineer reads the passport to know which component is installed and adds what they have replaced. Working without coverage is more the rule than the exception here, just as with an inspection app.
Returns, refurbishment and second life
At intake, the first question is whether this item is yours and what has happened to it. The passport answers both, provided it can be scanned at intake and doesn't just sit in a system.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The app is the physical side of the passport register, not an administration of its own. Everything it records ends up in the same register, so there is no second source of truth.
Why Appfront
A wrong link is discovered years later
That is why we build confirmation into the moment of scanning, and the app refuses when in doubt. It costs a second and prevents a passport that points to the wrong item.
Without a signal, work must simply carry on
We build offline as the starting point, not as an emergency fallback. An app that stalls on a poor connection gets bypassed, and then the passport still doesn't exist.
One register, no second administration
The app writes to the same passport register as your office side, via integrations. Two administrations for the same item are guaranteed to drift apart.
Tested on retrieval, not just on application
We test the scenario in which someone scans an old item. That is what the regulation targets, and it is where systems tested only on production break down.
Security and privacy
On a mobile device, the risks differ from those in the office. A phone on a factory floor gets lost, is shared between shifts and goes outside. That is why we assign roles to the user rather than the device, limit the data stored offline to what is needed for the work at hand, and make sure a device can be disconnected remotely without disrupting anyone else's work.
The reading side calls for its own considerations. Part of the passport is public and is meant to be scanned by strangers; another part explicitly is not. In the app, that separation depends on the logged-in role, so a fitter sees more than a consumer using the same code. What the app records is also evidence: the photo, timestamp and employee should be immutable, because otherwise it isn't a life history but a story. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.
Frequently asked questions about the product passport app
Because linking and reading don't happen in one place. A fixed set-up can work at the end of the line, but not at goods receipt, with a fitter on site or on returns. One app that does the same thing at all those moments prevents each department from developing its own way of working.
The obligation per product group comes through delegated acts that have not yet been published, so no, it is not mandatory now. What does matter now is whether you can identify an item at all. If you can't, no list of fields will help you later, because you won't know which item the passport belongs to.
Usually yes, and that is often the cheapest route. If you already put a serial number or batch code on the product, the data carrier can be tied to that instead of you adding a second code. Whether that is allowed under the requirements for your product group will be set out in the delegated act; we build the integration itself so that you can switch carriers.
That happens with products that hang outside for years or go through a car wash. The app can then search by serial number or by batch, and link a replacement carrier to the same passport, recording that replacement. Without that route, a second passport is created for the same item, and that is the mistake you want to avoid.
Yes, but they see less. The regulation assumes tiered access: a consumer, a repairer, a recycler and a regulator each see a different part. The public view doesn't require an app; it simply opens in a browser. The app is for your own people, who see more and are also allowed to write data.
The app is the physical side, the registry is the administrative side. The two belong together and share a single data source. The registry side, with schema management, supplier data and access tiers, is covered on the ESPR software page.
Often yes, and that is usually preferable to a second app on the same device. A field service app already has the login, the roles and the offline functionality; scanning and linking are added as a component. Whether that is possible depends on how your current app is built.
That depends on the number of scan points, whether NFC is required and how demanding the offline functionality is. Linking and reading are usually quick to get working; photos, events and integrations with ERP or WMS cost more. We provide a well-founded estimate after the discovery phase.
Linking passports to products?
Go to the place where the code would be applied and count how many seconds you have per product. That number shapes the design more than the regulation does. We build this as a standalone app and as part of a broader custom app or custom software project.