When a PCN update is required

The triggers for an update

Annex VIII lists a fixed set of changes that require a fresh submission update:

• the product identifier changes, including a new or amended UFI;
• the mixture's classification for health or physical hazards changes;
• new toxicological information becomes available on the mixture or its components;
• a component is added to, substituted in, or removed from the mixture; or
• a component's concentration moves outside what was originally declared.

That last trigger is where an update on its own is sometimes not enough — whether a composition change also calls for a brand-new UFI, on top of the update, depends on whether it stays inside the range or tolerance you originally declared. That distinction has its own set of rules; we work through it in full on when a new UFI is needed.

The deadline for an update

There is no fixed number of days written into Annex VIII for this — the rule is that an update has to be filed before the changed mixture is placed on the market, and more generally, without undue delay once the triggering change has happened. In practice that means an update is not something to batch up for a quarterly review: the moment a reformulated batch, a revised classification or a new piece of toxicological data is real, the clock is already running, and there is no grace period to point to if a market surveillance authority asks why the dossier on file does not match the product on the shelf.

What an update does not change

An update revises the existing submission — it is not a way to erase what was already declared. You cannot remove a market you have previously notified into just because the product stopped selling there, and you cannot withdraw a UFI once it has been assigned. Where the issue is not a real change to the product but a mistake in how it was originally described, that is handled differently again, through a correction of error rather than a standard update, since the underlying mixture on the market never actually changed.

An update also does not restart the dossier from a blank page. It is filed as a revised version of the previous submission, carrying forward everything that has not changed and replacing only the parts the trigger actually affects, which is part of why misreading a change as bigger than it is — treating a rebrand as if it needed a whole new dossier, for instance — creates more rework than the situation calls for.

Keeping track across many products

None of this is manageable from memory once a company is carrying more than a handful of notified products. What tends to fail is not the update process itself but the step before it — nobody flagging that a supplier substitution or a rebrand touches a product that already has a dossier on file, because the person handling the change has no reason to know the notification exists. An internal register tying every trade name and UFI to its submission is what closes that gap, and it matters more the further a company's original 2021, 2024 or 2025 filing recedes into the past and the less anyone still actively thinks about it.

The same register earns its keep beyond simple bookkeeping, too: a dossier that has silently drifted out of date is not a lesser problem than one that was never filed, since either way the record sitting behind the UFI on the shelf is no longer the product actually inside the pack.