European Commission TRACES System: Registration and Use for African Exporters

TRACES NT is the European Commission's digital certification and pre-notification platform, managed by DG SANTE under the Official Controls Regulation (EU) 2017/625, and it sits at the centre of nearly every compliance process already covered throughout this series.

Despite how central this single platform is to virtually every product category covered elsewhere in our broader EU import requirements coverage, few resources actually walk through the registration and day-to-day usage mechanics in practical, step-by-step detail. Most compliance guidance simply assumes an exporter's EU importer will handle the entire TRACES relationship, which leaves African exporters with limited direct visibility into a system that governs so much of their own trade.

Understanding how to actually register and operate within this system directly, rather than relying entirely on an EU importer's own account, gives African exporters genuine visibility and control over their own compliance status.

This visibility matters in ways that go beyond simple convenience. An exporter who can log into their own account, check the status of a specific certificate, and confirm exactly where a submission sits in the approval process is far better positioned to catch a problem early than one waiting entirely on updates relayed secondhand through an importer who may not check the platform as frequently or as carefully as the exporter's own business genuinely needs.

What follows walks through exactly how to register, the platform's underlying operator-and-user structure, which specific parties in a trade relationship actually need their own account, and the practical troubleshooting steps that resolve the most common registration delays.

Reading through each section in sequence builds a genuinely complete, practical understanding of this platform from first login through to ongoing day-to-day use, rather than a fragmented set of tips that leaves important structural context missing.

EU Login First: The Mandatory Gateway

Before touching TRACES NT itself, every user needs an EU Login account, the European Commission's single authentication service used across multiple EU digital platforms.

This first step is worth completing carefully and correctly the very first time, since a rushed or incomplete EU Login setup at this stage tends to create knock-on complications for every subsequent step covered throughout the rest of this guide.

This gateway requirement is worth completing well before any actual shipment deadline looms, since account creation and verification take genuine time, and rushing this initial step under time pressure is precisely when avoidable errors creep in. Once an EU Login account exists, the same credentials work across other Commission platforms too, making this a worthwhile one-time investment rather than a system-specific hurdle.

Two-factor authentication, while an extra step compared to a simple username and password, exists specifically because of what this platform actually controls — certificates and pre-notifications determining whether real, physical shipments of food and agricultural products can legally enter the EU. Treating this security requirement as a reasonable, necessary feature of a system with this level of consequence, rather than an unwelcome inconvenience, is the right mindset for approaching the entire registration process.

Operators vs Users

TRACES NT distinguishes clearly between an Operator, representing a specific company or business entity, and a User, the individual person accessing the system on that company's behalf, and understanding this structure matters directly for how registration actually works.

This might initially seem like an unnecessary layer of complexity, but it exists precisely because real companies involve multiple employees over time, and a system tied to a single individual's login credentials would create genuine, avoidable fragility every time staff changed roles or left the organisation entirely.

This Operator-versus-User distinction is worth understanding clearly from the outset, since confusion here causes genuine registration delays. An individual employee changing roles within the same company doesn't need an entirely new Operator profile created — they simply need their own personal User account linked to the existing company Operator profile instead.

This structure also matters directly for staff turnover and organisational continuity. Because the Operator profile represents the company itself rather than any single individual, a business doesn't lose its accumulated TRACES history, certificates, or registration status simply because a specific employee who originally set up the account leaves the company. New staff members can be granted their own User access linked to the same, continuous Operator profile, preserving institutional knowledge and compliance history that would otherwise risk being lost with a departing employee's personal login credentials.

Understanding which specific activities a company's Operator profile actually holds is worth reviewing periodically, particularly for businesses whose role in the supply chain has evolved over time. A company that started as a simple exporter but has since taken on freight forwarding or consolidation responsibilities for other smaller producers may need to add these additional activities to their existing Operator profile, rather than assuming their original registration automatically covers every function they've since taken on.

Who Actually Needs an Account

A genuinely comprehensive range of parties across a trade relationship need their own TRACES account, and confirming exactly who in a specific transaction actually requires one avoids both unnecessary registrations and dangerous gaps.

Mapping out every party in a specific trade relationship against this table, rather than assuming registration is purely a concern for whichever single party happens to be most familiar with EU compliance processes, ensures no genuinely necessary account gets overlooked.

The inclusion of non-EU exporters and establishments in this list deserves specific emphasis, since many African exporters assume this entire system is purely an EU-side importer responsibility. TRACES supports users across more than 90 countries specifically because the platform is designed for direct participation from exporting countries, not solely from within the EU itself. An African exporter who registers directly gains genuine visibility into their own certificates and consignment status, rather than depending entirely on secondhand updates from an EU importer's own account.

This point is worth stating even more directly: an African exporter who has never registered in TRACES themselves is not thereby exempt from the system's requirements — they are simply operating with less direct visibility and control over a process that governs their own shipments regardless of whether they've personally engaged with the platform. Registering directly converts this from a background process managed entirely by someone else into a genuine, transparent part of an exporter's own operational toolkit.

Freight forwarders and customs brokers acting on behalf of an African exporter deserve particular mention here too, since their ability to submit notifications on a client's behalf doesn't eliminate the value of the exporter also holding their own direct account. A broker submitting on an exporter's behalf still operates within the exporter's own Operator profile in most arrangements, meaning the exporter retains ultimate visibility into what's being submitted under their company's name, provided they've set up their own access to check it directly rather than relying purely on the broker's own assurances.

The Four CHED Types Explained

The Common Health Entry Document, referenced throughout our EU border inspection posts and organic import regulations guides, actually comes in four distinct types, and confirming which one applies to a specific consignment matters directly for correct submission.

Treating these four types as genuinely distinct document categories, rather than four minor variations on a single form, is the correct mental model for approaching submission accurately the first time.

CHED-A covers live animals, CHED-P covers products of animal origin, CHED-D covers food and feed of non-animal origin subject to increased official controls — directly relevant to many of the high-risk categories covered in our EU cashew nut, sesame seed, and green bean guides — and CHED-PP covers plants, plant products, and plant propagating material specifically, already referenced throughout our organic certification coverage.

Confirming the correct CHED type before submission, rather than assuming a general familiarity with "the CHED" covers every product category identically, avoids a genuinely avoidable submission error. Each type carries its own specific data fields and validation requirements, and selecting the wrong one at the outset means restarting the submission process entirely once the error is caught.

For most African agricultural exporters covered throughout this broader series — whether shipping fresh produce, dried herbs and spices, or organic-certified crops — CHED-PP and CHED-D are the two types most likely to apply directly, since these cover plant products and non-animal-origin food and feed respectively. Confirming which of these two specifically governs a given product, particularly for processed or dried goods that might sit at the boundary between categories, is worth clarifying directly with a customs representative or the relevant control body before assuming either type automatically applies.

This categorisation also connects directly to the increased-controls framework already covered throughout our cashew nut, sesame seed, and fresh herb guides. Products listed under that framework's stricter requirements generally submit through CHED-D specifically, with the additional health certificate and analytical test report requirements already covered in those guides layered on top of the standard CHED-D submission itself.

Choosing a Border Control Post

During initial registration, economic operators must select a specific Border Control Post they wish to be associated with, a step worth understanding correctly to avoid an unnecessary registration constraint.

This step trips up more new registrants than almost any other single decision point in the entire process, precisely because the underlying flexibility isn't always obvious from the registration interface alone.

This initial BCP selection is required for registration purposes specifically, but it doesn't lock an operator into using only that single entry point going forward. Once registered, any Border Control Post can actually be used for a given shipment, provided that specific BCP is designated for the relevant product category, already covered in detail in our EU border inspection posts guide. This flexibility matters directly for exporters whose shipping routes might reasonably vary between Rotterdam, Hamburg, or another entry point depending on the specific buyer and season, since the initial registration choice doesn't need to anticipate every future routing decision with total precision.

This flexibility is worth understanding clearly precisely because the opposite assumption — that registering with one specific BCP somehow commits an operator to that single port permanently — could otherwise lead an exporter to delay registration unnecessarily while trying to predict their entire future shipping strategy in advance. Registering promptly with whichever BCP seems most likely for an initial shipment, understanding this choice can be revisited freely for future consignments, removes this unnecessary hesitation from the registration process.

Exporters working with the Netherlands as a primary EU gateway, a pattern already covered extensively in our dedicated Netherlands guide, should confirm which specific Dutch Border Control Post best matches their product category during this initial registration step, understanding that this choice reflects a practical starting point rather than a permanent, binding commitment.

When Your Request Sits "Pending"

A role request or new registration sitting in pending status is one of the most common points of confusion for new TRACES users, and understanding the correct response matters directly for resolving it efficiently.

This confusion is entirely understandable given how unfamiliar the platform can feel to a genuinely new user, and normalising this as a routine, expected part of the process rather than a sign something has gone uniquely wrong helps put the situation in proper perspective.

A pending status simply means the relevant approver — either the operator's own internal administrator or the competent authority responsible for that specific request — hasn't yet actioned it. The correct response is contacting that approver directly to confirm and expedite the request, not resubmitting a duplicate application, since duplicate requests genuinely create confusion and further delay rather than resolving the original wait. This same discipline of confirming status directly with the responsible party, rather than repeating an action and hoping for a faster outcome, mirrors the same practical patience already recommended in our EU customs clearance guide's discussion of selectivity outcomes and processing timelines.

Building a habit of following up proactively, rather than simply waiting indefinitely for a pending request to resolve itself, is worth adopting from the very first registration attempt. A polite, direct message to the relevant administrator or competent authority, referencing the specific request and its submission date, typically moves things along far more effectively than either silent waiting or the well-intentioned but counterproductive instinct to submit the same request again in case the first attempt was somehow lost.

This same principle extends to every subsequent interaction with the platform, not just initial registration. A CHED submission sitting unreviewed, a role request awaiting approval, or a certificate pending verification all benefit from the same direct, patient, but persistent follow-up approach rather than either passive waiting or duplicate resubmission, both of which tend to slow the process down rather than speed it up.

Frequently Asked Questions

TRACES NT sits at the operational centre of nearly every EU compliance process this series has covered, from customs clearance and organic certification through to the border control post system governing physical entry. Registering directly, understanding the platform's Operator-and-User structure, and knowing exactly how to resolve a pending request without creating further delay are the practical skills that turn TRACES from an intimidating, opaque system into a genuinely manageable, routine part of exporting African produce into the EU. Building genuine familiarity with this single platform, once, pays dividends across every subsequent shipment and every other compliance area already covered throughout this broader series, since so much of it ultimately routes back through the same underlying digital infrastructure.