Capture on the line Photo per market variant Deviations reported immediately

Custom app for packaging and appearance data in the notification dossier

A notification to the poison centres requires the packaging type and packaging size from a fixed list, and a colour from fourteen options. The people who know exactly which packaging comes off the line for the German market, and what colour the product actually is, are not in the department that submits the notification.

Appfront
Live

Where the dossier and reality diverge

The notification format offers a list of different packaging types and sizes to choose from. For colour there are fourteen options, into which the company's own colour names have to be translated. This is not data from a formulation system but observations of a product.

Those observations are made where the packing happens. That is where you know which bottle is actually being used, whether the fill on the last run came out lighter, and which variant is going to which market. For the department that submits, all of that is hearsay.

Resubmission is mandatory if the product identifier changes, including the UFI code, if the hazard classification for health or physical hazards changes, or if new information emerges about the hazardous properties. So what changes on the line can carry through into a submission.

The reverse matters just as much. If a different pack is used on the line than the one that was notified, the dossier no longer matches what is on the market. That is the kind of discrepancy that can go unnoticed for months, until someone compares the two.

How we build this

The core is the market variant. One formulation can be on the market in different countries in different packaging and with a different label, and each of those variants has its own data.

1
Opening the variant

A code on the order or the pallet opens the right market variant, with the notified data alongside it.

2
Recording what is there

Pack type and size, colour and physical state, chosen from the same lists the format uses.

3
Comparing with the file

If reality differs from what was notified, that is immediately visible rather than coming to light in an audit.

4
Passing it on to regulatory

A discrepancy or a change goes, with a photo, to the person who manages the submission.

What the app actually does

Recording on the line carries the whole thing. What else you need depends on the number of markets and the number of pack variants.

Dropdown lists from the format

Pack and colour are chosen from the same lists the submission uses, so no translation step is needed afterwards.

Photo per market variant

An image of the pack as it leaves the door is the only thing that can later show what was actually there.

Comparison with the dossier

The notified data sits alongside, so a discrepancy stands out the moment it arises.

Physical state and colour

Observations of the product itself, recorded by someone who has it in front of them rather than from a specification.

Works without signal

Packing halls rarely have good coverage. The app works locally and syncs as soon as there is a connection.

Escalating a discrepancy

A pack that differs from the notified one goes straight to regulatory, with the photo and the time attached.

Who we build for

Who records this data differs per company. Four situations.

Packaging developers

They choose the pack and are the first to know when something changes, usually before regulatory hears about it.

Production managers

They see which variant is running and which market it serves, and notice when something different is being used.

Quality staff

Quality

Regulatory affairs

They submit and depend on what others have observed, usually through an email after the fact.

Not sure about a large project yet?

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 format is extended, dropdown lists are revised and variants are added. Lists, fields and markets should be configurable and not hard-coded in the app.

React Native or native iOS and Android Offline storage with sync Dropdown lists conforming to the notification format Barcode and order code scanner Photo with time and location Comparison with notified data Operation with work gloves Roles for production, quality and regulatory Integration with your notification dossier History per market variant

Why Appfront

The dropdown list belongs on the line

Whoever has the pack in front of them can choose it from the fixed list. Whoever describes it in an email leaves the translation step to someone else.

Colour is an observation

Fourteen options and a product you have to see. That is a job for the place where the product is, not for a specification sheet.

You only discover a difference if you compare

That is why we place what was notified next to it at the moment the data is recorded.

We do not submit the notification

That stays with you. We make sure the data you submit comes from the place where it originates.

Security and privacy

What is recorded on the line shows which variants you make for which markets and in what volumes. That is commercially sensitive, especially in contract packaging for third parties. We set access per role and per location, show an operator only the order they are working on, and log every time data is viewed. Whatever is stored locally on the device is encrypted and can be wiped remotely if a device goes missing.

For this topic, the reliability of the moment is the point. Packaging data that has been adjusted afterwards to match what was notified hides precisely the difference you wanted to find. We record observations immutably with time, place and person, even when synchronisation happens later, and we make a correction a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about packaging and appearance data

Because the notification format requires it: a packaging type and size from a fixed list, and a colour from fourteen options. That data does not come from a recipe system but from an observation of the product itself.

Because that is where you know which packaging is actually being used and what the product actually looks like. In the office, that is hearsay.

When the product identification changes, including the UFI code, when the hazard classification for health or physical hazards changes, or when new information becomes available about the hazardous properties.

Then the dossier falls out of step with what is on the market. The app places what was notified alongside it, so that difference stands out the moment it arises.

That is about verifying the code on the label against the dossier. We have a separate page for that, on the UFI check app.

In the notification dossier, where submissions are managed per market. We describe that on our page about PCN dossier software.

Is the packaging you notified the packaging on the line?

Take one market variant, walk to the packaging line and compare the type and size with what the dossier says. If it differs, it has been different for some time. We build this as a standalone app and as part of a broader app development project.

Edit content