Custom software for the notification dossier and submission per market
A notification to the poison centres asks for your product in someone else's terms. Your colour name has to become one of fourteen colours, your packaging one of a fixed list of types and sizes, and your application one of roughly 250 categories in the European product categorisation system. That translation is the real work, and it is rarely recorded anywhere.
What a notification asks of you
Annex VIII to the CLP Regulation sets out the harmonised information for the notification under Article 45. It goes through the ECHA submission portal to the bodies the Member States have designated for this purpose, and is used by the national poison information centres in an emergency. So it is not an archiving obligation but information that has to work in an acute situation.
Different provisions apply to the composition depending on the type of ingredient. Ingredients of concern are subject to different rules than other hazardous ingredients, and different again for ingredients not classified as hazardous. This means a single formulation is queried in three different ways.
On top of that, a considerable part of the dossier consists of data that does not come from your formulation database. The use must be specified with the European product categorisation system, which has roughly 250 categories. For packaging there is a fixed list of types and sizes to choose from. For colour there are fourteen options, and your own names have to be translated into them.
A notification is also never finished. Resubmission is required if the product identification changes, including the UFI code, if the hazard classification for health or physical hazards changes, or if new information becomes available about the hazardous properties. If you don't keep track of this, you end up with a dossier that slowly drifts out of step with the product.
How we build this
The core is the dossier per market. One product may have been submitted differently in different Member States, in a different language and sometimes with different packaging, and each of those submissions has a life of its own.
Your own colour, packaging and application are linked once to the fixed choices in the format, with the reasoning alongside.
Product identification, composition per ingredient category, toxicological information and the data on physical form.
Which Member State, which language, which version and which status. A submission is only complete once it has been accepted.
If the identification, the classification or the knowledge about the hazardous properties changes, the system flags which submissions need to be resubmitted.
What the software actually does
The mapping between your own data and the fixed options carries the whole thing. What else you need depends on the number of markets and the number of products.
Mapping tables that persist
Which of your colour names belongs to which of the fourteen options, and which packaging belongs to which type. Once decided, always the same.
EuPCS category per product
Choosing the right one from roughly 250 categories is a decision. We store that decision with its justification, not just the outcome.
Composition per ingredient category
Ingredients of concern, other hazardous ingredients and unclassified ingredients are each requested differently.
Tracking submissions per member state
Which country, which language, which version, which status. Without that overview, you cannot say where you are and are not covered.
Resubmission alerts
A changed identification, a changed classification or new information about the properties leads to a task, not to an assumption.
History per submission
What was submitted where and when, and with which data. When an authority asks a question, that is the only usable answer.
Who we build for
Who builds the dossier differs per company. Four situations.
Regulatory affairs
They handle the submissions and get stuck on translating between their own data and the prescribed options.
Product managers
They change a packaging or a trade name and don't always know that it affects a submission.
Exporting formulators
For them, each country is a separate submission, and things go wrong in the overview across those countries.
Smaller producers without a dedicated department
They do this on the side and benefit most from a system that remembers the mapping.
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 being extended, categories are being revised and member states set their own requirements. Option lists, mapping tables and fields should be configurable rather than hard-coded.
Why Appfront
The mapping is the work
Your colour to fourteen options, your packaging to a fixed list, your use to hundreds of categories. We record those choices instead of making them again every time.
A submission is not a document but a status
Submitted, accepted, or awaiting a response from a member state. Without that distinction, you don't know where you stand.
A change elsewhere affects your dossier
An adjusted packaging or a changed classification is a small decision for a product manager and a new submission for your dossier.
We don't do the notification for you
The responsibility stays with you. We build the dossier that lets you carry it.
Security and privacy
A notification file contains full compositions, which is the most commercially sensitive thing a formulator has. We set access per role and per product, show a product manager the product's appearance without the recipe, and log every view. Integrations to your existing software run through secure connections.
For this topic, the reliability of the moment is the point. A dossier that was altered afterwards without a trace no longer shows what was submitted when the product went to market. We record versions immutably with a timestamp and the person responsible, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.
Frequently asked questions about poison centre notifications
Via the ECHA submission portal to the bodies that the member states have designated for this purpose. The national poison information centres use that information in an emergency.
The European Product Categorisation System, used to indicate the use of a mixture. It has roughly 250 categories, and choosing the right one is a decision that should be traceable.
Because the format has fourteen colours and your own names don't map onto them. You need to make that translation once and then apply it consistently.
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.
This page covers the dossier and submission per market. Issuing and monitoring UFI codes per formulation is covered on our page on PCN and UFI software.
It differs per type of ingredient. Ingredients of concern are subject to different provisions than other hazardous ingredients, and different again for ingredients not classified as hazardous.
Do you know in which countries this product has now been submitted?
Take one product and look up, per Member State, which version was submitted, in which language and with what status. If that remains a search through mailboxes, your coverage is an assumption. We build this as a standalone application and as part of a broader project to build software.