Most TRACES NT tickets fall into four buckets. Working through them in order saves a lot of guessing.
1. Access problems
TRACES NT uses EU Login with two-factor authentication. Old TRACES Classic credentials do not exist, because the Commission decommissioned that platform in 2022. If someone cannot sign in, check whether they have an EU Login at all before checking anything else. Access itself is free.
2. Wrong document type
Four CHED types cover different goods: CHED-A for live animals, CHED-P for animal products, CHED-PP for plants and plant products, CHED-D for non-animal food and feed. A form that will not accept your product line is usually the wrong type rather than a bug.
3. Code and detail mismatches
Establishment codes must match official lists exactly. Certificate numbers and consignment details are entered by hand, so compare against the source document character by character before assuming a platform fault. Most border holds trace back here. The background on why this remains manual is set out in this explainer on why TRACES Classic was retired.
4. Obsolete references
If an internal system, template or supplier form still refers to the CVED, it is describing a document that has not been in use since the Classic shutdown. Fix the template, not the submission.
Escalation note
Before raising anything externally, capture the CHED type, the exact field, the source document value and the entered value. That short record resolves most cases without escalation.
See how iCustoms flags mismatched codes before they become holds: watch a demo.
