Custom software for Poison Centre Notification and UFI management
A UFI belongs not to a product and not to a brand, but to a formulation. That sounds like a detail until something in the composition changes: then it isn't a single label that needs updating, but a chain of formulation, notification, label and safety data sheet that has to be brought back into line.
What Annex VIII requires of you
Anyone placing a hazardous mixture on the market must notify the poison centres. That notification goes through the European Chemicals Agency's portal in a prescribed format. It includes the trade name, the UFI, classification and labelling, toxicological information, and the composition of the mixture with concentrations or concentration ranges.
The UFI itself is a unique code of sixteen alphanumeric characters in four blocks, preceded by the letters UFI and a colon. The code contains a check digit, so a typo gets noticed. The code must appear on the label; for industrial use and for unpackaged mixtures, it may be placed on the safety data sheet.
The obligation was phased in: for consumer and professional-use mixtures the date was the start of 2021, for industrial use the start of 2024. Companies that have been supplying for years therefore have a portfolio of notifications of different ages, made by different people.
The effort lies in the changes. If a component is added, replaced or removed, or a concentration falls outside the stated range, a new UFI and therefore a new notification is needed. A supplier changing the UFI of an ingredient mixture also affects your dossier. That is exactly the kind of link that gets lost in a spreadsheet.
How we build this
The core is the formulation, not the article. One formulation can be on the market under several trade names and in several packagings, and they share the same UFI as long as the composition stays the same.
Components, concentrations and ranges are kept together. The trade names, packagings and markets the mixture is supplied to hang off that.
Every formulation has a UFI. The system records which code belongs to which version, so an old pack on the shelf remains traceable.
If a component changes or a concentration falls outside the range, the system flags that a new code and a new notification are needed.
The data the portal asks for is assembled from your own sources, so you don't have to compile it by hand for every notification.
What the software actually does
The formulations register carries the whole. What else you need depends on your range and on whether you also buy in mixtures to process yourself.
Versioned formulations
Every change to the composition creates a new version. That way it stays clear which code belonged to the product delivered last year.
UFI register
Which code was issued, for which formulation, since when, and where it is published: on the label or on the safety data sheet.
Alert on composition change
Adding, replacing or removing a component, or a concentration outside the range, triggers a notice that action is needed.
Tracking ingredient mixtures
If a supplier changes the UFI of a mixture you process, that affects your own notification. We keep track of that dependency.
Prepare the submission
The data for the notification is assembled from your formulations and classifications, ready for submission via the portal.
Overview per market
Which mixtures have been notified where, and for which use. With a portfolio of any size, this is the overview that is missing.
Who we build for
Who manages this differs per company. Four situations.
Formulators
They change compositions most often and so are the first to run into new UFIs and renewed notifications.
Importers and distributors
Anyone placing a mixture on the market under their own name has their own obligation, even if the formulation comes from someone else.
Regulatory departments
They safeguard consistency between classification, label, safety data sheet and notification. That is the same truth in four places.
Smaller producers without a dedicated department
With a limited range, the task falls to someone who does it on the side. What matters most then is that the system warns you rather than someone having to remember.
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 submission format is revised, use categories are tightened and classification rules change. Fields, ranges and validations should be configurable rather than hard-coded.
Why Appfront
The code belongs to the formulation
Not to the article number and not to the brand. We model that relationship explicitly, because that is where most errors arise.
A change is an event
An amended recipe is not a minor correction but a trigger. We turn it into an alert rather than a note.
What was delivered yesterday counts too
Products with an older code are still on the shelf. The register keeps track of which code belonged to which period.
We don't submit anything for you
The notification remains an action and a responsibility of your organisation. We make sure the data matches your own records.
Security and privacy
A formulation register contains the recipes of your products, which is highly confidential business information. We set access per role, give production different visibility from regulatory, and record who has viewed which composition. Integrations run through secure connections to your existing software.
For this topic, what matters is that the data is reliable at the moment it counts. A composition that is adjusted after the fact, once a notification is already under way, makes the file unreliable. We record changes immutably, with a timestamp and the person responsible, and 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 PCN and the UFI
When a component is added, replaced or removed, or when the concentration falls outside the stated range. If a supplier changes the UFI of a mixture that you process, that also affects your own code.
On the label. For industrial use and for mixtures that are not packaged, the code may be stated on the safety data sheet. The marking consists of the letters UFI in capitals, a colon and the code.
Sixteen alphanumeric characters in four blocks, with a built-in check. That check is why a wrongly retyped code gets noticed instead of silently carrying on.
For mixtures for consumers and for professional use it applied from early 2021, for industrial use from early 2024. As a result, many companies have notifications of different ages side by side.
Yes, and that is usually the point. The formulations already exist somewhere; the aim is to avoid a second list of compositions that deviates from the first. See our approach to custom software.
Yes. Checking the code on a label is covered on our page about the UFI app.
Do you know which UFI belongs to last year's batch?
Take a product whose recipe has been changed at some point and look up which code was on the label at the time. If that takes more than a few minutes, that is the gap. We build this as a standalone application and as part of a broader software development project.
If you also need to handle submission per market, look at PCN dossier software and the app for packaging and appearance data.