A flagged TRACES establishment code has one of two root causes: your data is wrong, or the approval is wrong. Diagnosing which one first saves the supplier call you did not need to make.
Start with your own data
Check these before contacting anyone:
- Whitespace. Codes pasted from PDFs and emails carry invisible characters.
- Transposition. Two swapped digits produce an unrecognised number that looks correct at a glance.
- Column alignment. Merged cells shift values into the wrong fields, so a valid country lands in the activity column.
- Age. Codes reused from a previous order may have been correct then and not now.
If the raw source document and your file disagree, the problem is yours. Fix and re-run.
Then read the flag type
Different flags mean different things, and the fix follows the type. An unrecognised number points at data or a delisting. A country mismatch usually points at a supplier operating from a different site than assumed. An activity category mismatch means the establishment is approved, but not for what you are importing. The published guidance on flagged TRACES establishment codes separates these cases clearly.
Resolution paths
- Confirm the correct approval number with the supplier.
- Correct the typo in your own records.
- Source from an approved establishment where the current one no longer covers the product.
Then re-validate. A fix that has not been re-checked is an assumption.
The rule that matters
Never ship with an unresolved flag. Overriding a flag does not clear the goods; it just moves the discovery to the border, where it costs more and takes longer to fix.
Top comments (0)