Custom UFI label and packaging verification app
A wrong code on a label is silent damage. It looks fine, it scans, and only when someone checks it against the file does it turn out to be the code from the previous formulation. On the shop floor, at the end of a production line or during repackaging, that is the moment when it can still be put right.
What needs to be right on the label
A hazardous mixture placed on the market carries a UFI: sixteen alphanumeric characters in four blocks, preceded by the letters UFI. The code contains a check digit, so a typing error stands out. What doesn't stand out on its own is a code that is valid in itself but belongs to a different formulation.
This happens more often than you might think. A formulation is changed, a new code is issued, and there is still a stock of labels from the previous round. Or a product is repackaged for another market and the packaging gets whichever label was closest to hand.
The code belongs on the label. For industrial use and for mixtures that are not packaged, it may appear on the safety data sheet instead. This means the check on the shop floor isn't always the same: sometimes you look at a label, sometimes at the document that travels with the product.
An app doesn't solve the management side. Formulations, code issuance and notification belong in the PCN software. What the app does solve is that someone on the shop floor can establish within a few seconds whether what is on this packaging matches what is inside.
How we build this
The app revolves around a single action: scan and get an answer. Anything that would need a form to fill in gets skipped on a production line.
The operator scans the batch code or the packaging. From that moment the app knows which formulation it is dealing with.
The UFI on the label is scanned or photographed. The built-in check catches a misread before anything is compared.
The scanned code is checked against the current code for that formulation. Green or red, with no intermediate steps.
If it doesn't match, the operator records it with a photo of the label. The report goes to whoever can stop the batch.
What the app actually does
The check at the line carries the whole solution. The rest depends on your production and on whether you also repack for third parties.
Scan and verify
The code on the label is compared with the code that belongs to this formulation. One action, one answer.
Misread check
The check digit built into the code catches a wrongly read character, so a misread is not reported as a deviation.
Works with gloves on
Large buttons, high contrast and scanning instead of typing. On a line, the number of actions matters, not the number of features.
Available without coverage
Coverage in a production hall or warehouse is patchy. The app works locally and syncs as soon as there is a connection.
Deviation with a photo
A photo of the label with the report, along with the time and the batch. That way you can see afterwards exactly what was on it.
Back to the file
What is reported on the shop floor lands with the formulation, so regulatory can see that something went wrong and where.
Who we build for
Who does the check differs from company to company. Four situations.
Operators at the labelling line
They see the labels go past and are the last people who can stop a wrong run before the batch leaves.
Quality staff
They take samples from a batch and want to record them without retyping them into a form afterwards.
Warehouse and dispatch
When repacking or re-sorting, labels and packaging that don't belong together come into contact. A quick check is worth the most there.
Contract packers
If you pack for several clients, you work with codes that aren't your own. What matters most then is that the source is unambiguous.
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
Codes, label formats and usage categories change. What gets scanned and what it is compared against should be configurable, not hard-coded into the app.
Why Appfront
A code that scans doesn't have to be correct
The built-in check only tells you the code was read correctly, not that it belongs to this mixture. That difference is the whole point of the check.
The shop floor is not an office
Gloves, noise and pace. We build for the number of actions that is achievable there, not for the screen that looks best in the office.
The source is not on the phone
What the code is compared against comes from the formulation register. A list someone once exported is not a source.
We don't approve your batch
Whether a batch may leave is a decision for your organisation. We make sure the finding is on the table in time and with evidence.
Security and privacy
An app that talks to the formulation register touches confidential recipes. That is why we never show the composition on the shop floor, only whether the code belongs to the batch. Access is controlled per role, what is stored locally on the device is encrypted and can be wiped remotely if a phone goes missing.
For this subject, what matters is reliability at the moment of the check. A check entered afterwards says nothing about the batch that was actually on the line. We record scans and reports immutably, with time, batch and person, even when synchronisation happens later, and we make a correction a visible correction. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about label checking
Whether the code on this packaging belongs to the formulation of this batch. The built-in check in the code also catches a reading error, but that says nothing about correctness in itself.
Yes. For industrial use and unpackaged mixtures, the code may appear there. The app can check against the document instead of the label.
Yes. The data needed for the comparison is stored locally on the device. Reports sync as soon as a connection is available again.
No. On the shop floor, the app only shows whether the code belongs to the batch. The composition stays in the register and is shielded per role.
The employee records it with a photo of the label and the batch details. The report goes to whoever can stop the batch; the app does not block anything itself.
We build that side separately. Formulations, issuing and submission are covered on our page about PCN software.
Would you notice right now if an old label were on it?
Take a batch of a product whose formulation has been changed at some point and compare the code on the packaging with the current file. If that takes longer than a minute, that check is not happening on the shop floor. We build this as a standalone app and as part of a broader app development project.