TraceMap — What It Is and When It Launched
On March 10, 2026, the European Commission launched TraceMap — an AI system combining RASFF and TRACES to detect food fraud. The first case involved contaminated ARA oil from China. Ukrainian exporters need to update VACCP/TACCP under FSSC 22000 cl. 9.2.
DG SANTE introduced the platform as the first tool that effectively stitches together the EU's two main food control systems. Until March 10, RASFF (alerts) and TRACES (electronic certificates for goods movements) ran as parallel data sources without automatic links. Now an AI layer over these databases finds anomalies in minutes rather than days.
EU Commissioner for Health Olivér Várhelyi summed up the logic: "We connect the dots that fraudsters try to hide," as quoted by Food Safety Magazine.
For a Ukrainian exporter to the EU this means one thing: documents that previously passed through the gap between databases now face automatic cross-checking. This is the most systemic event in European food safety in the first half of 2026, after the update to FSSC 22000 v7 food fraud requirements.
How TraceMap Actually Works
TraceMap does not replace existing systems — it adds an analytical layer over two data flows that have run in parallel for 22 years:
- RASFF (Rapid Alert System for Food and Feed) — operating since 1979. Records national authorities' notifications about unsafe products: contamination, adulteration, mislabelling. RASFF processed more than 5,000 notifications in 2025.
- TRACES (TRAde Control and Expert System) — running since 2003. Electronic certification of goods movements across EU borders: consignments, operators, CN codes, lot numbers, veterinary and phytosanitary certificates. Millions of consignments pass through TRACES annually.
Until 2026, a national inspector would receive a RASFF alert and manually search TRACES for which consignments could have caused it. This took days, often weeks, especially when the supply chain ran across several countries and processing tiers. The TraceMap AI component does three things automatically:
- Pattern matching — compares operator, country of origin, product type, and movement period with historical alerts to identify recurring scenarios.
- Network analysis — builds graphs of links between operators even if they have no formal common ownership. Detects shell companies, resellers, and indirect chains.
- Anomaly detection — flags deviations in volumes, routes, and documents from normal sector behaviour. Unusual combinations of countries of origin, atypical logistics routes, and abnormal lot sizes land in the red zone.
The result for a national authority is a graphical dashboard with automatic crosslinks: operator, consignment, certificate, historical RASFF alerts, potential impacted brands. According to DG SANTE, the system identifies "patterns in minutes rather than days." Access is granted to competent authorities of all 27 Member States and TRACES-associated countries (Norway, Switzerland, Moldova, Ukraine).
Critical for business: TraceMap is not public. An exporter will not see how their data is matched against other operators'. But they will see the consequences — faster queries from the EU client, broader questions from the inspector at the port of arrival, or in the worst case, a RASFF alert citing a specific consignment without warning.
First Verified Case — ARA Oil from China
The showcase that accompanied the launch involved infant formula in several EU countries. RASFF recorded toxic effects in consumers and linked them to contaminated raw materials — the press cited cereulide, a toxin produced by Bacillus cereus. Investigators had to trace the chain from the finished product back to the raw material that had passed through processing in two countries.
TRACES already held data on consignments of infant formula and raw ingredients. TraceMap matched the RASFF alert with shipments of arachidonic acid (ARA oil) — a component added to formula to bring it closer to breast milk. The system isolated a single Chinese supplier whose deliveries simultaneously entered the production chains of several European brands during the alert period. Network analysis showed that formally independent brand manufacturers shared a single risk point in one raw material.
Human investigators could have handled this — in 5–10 working days, provided national authorities shared unstructured data. TraceMap cut the time to a few hours. New Food Magazine describes it as a shift from reactive recall to proactive detection. Futurist for Food analysts put it more bluntly: "end of plausible deniability" — you can no longer say "we didn't know where it came from."
For Ukrainian suppliers of raw materials into EU production chains (especially oils, spices, dairy ingredients, honey, fish), the takeaway is direct: TraceMap can reach your consignment with one or two inspector clicks, even if your direct buyer sits two or three tiers away in the chain. And if one of your consignments matched in time and region with a RASFF alert in a neighbouring sector, you land in the can of correlation automatically.
What Changes for Ukrainian Exporters to the EU
Ukraine has had associated TRACES access through DCFTA since 2017 — meaning your export certificate data already flows into the system that AI TraceMap now analyses. Three categories of exporters will feel the change most acutely.
Exporters appearing in TRACES
Any inaccuracy in CN codes, series, or lot numbers between the export certificate and the actual consignment is now detected faster. A document could previously pass due to limited inspector time for manual checks — now AI cross-references with historical RASFF alerts.
In practice: walk through the TRACES certificate process and verify that the document fields match the consignment passport. Particularly — series, production dates, net weight.
Suppliers of raw materials into EU production chains
If your EU client triggers a RASFF alert, TraceMap can automatically trace it back to your delivery, even through two or three processing tiers. This makes partial-batch traceability and supplier verification (FSSC 22000 v6/v7 cl. 9.2) a matter of contracts, not paperwork.
In practice: document traceability at lot/batch level, not contract level. Keep cross-reference tables of lot ↔ supplier ↔ receipt date for each ingredient.
Manufacturers with elevated food fraud risk
Categories with high adulteration rates — honey, oils, spices, fish, dairy. Your VACCP/TACCP analysis must account for the EU buyer receiving an automated alert about a suspicious pattern before you have closed the current shipment.
In practice: update your BRCGS vulnerability assessment and VACCP/TACCP plans for the AI cross-detection scenario. Add the ARA oil case as a horizon scanning reference. Review how many tiers deep into the chain you actually document — for high-risk categories, less than two tiers of tier-2 supplier verification no longer covers the real RASFF investigation risk.
A separate risk block is relabelling and mixing consignments between export orders. Until 2026 such actions could disappear between the exporter's paper records and electronic TRACES — now AI will detect a discrepancy between the volume entering the warehouse and the volume leaving for the EU, even when the documents look tidy.
How to Link TraceMap to FSSC 22000 and ISO 22000
TraceMap does not change the wording of any standard — but it changes the real bar for compliance. What was previously enough for a CB auditor may now fall short for DG SANTE and the EU buyer.
- FSSC 22000 v6/v7 Additional Requirements — Food Defense and Food Fraud Mitigation. Gaps in VACCP/TACCP that were previously known only internally now become visible to DG SANTE through TraceMap. The CB auditor will now expect evidence that your plan accounts for AI cross-detection and a reactive horizon ≤ 4 hours.
- ISO 22000:2018 cl. 8.3 (Traceability) — the formal "one step up, one step down" requirement remains. But ISO 22000 traceability requirements are now effectively a minimum — TraceMap makes the entire chain visible, so the EU buyer will demand full lot-level traceability as a contract condition.
- BRCGS Issue 9 cl. 5.4 — vulnerability assessment + horizon scanning. The ARA oil case should be added to horizon scanning as a fresh example of AI-driven detection.
- IFS Food v8 cl. 4.20 — food fraud mitigation plan. Mock recalls now have a target ≤ 4 hours, not the 24 that was standard until 2026.
- HACCP — the foundational hazard analysis under HACCP remains the base, but VACCP and TACCP as overlays need review against the TraceMap scenario.
- IFS Food v8 cl. 4.20 — the food fraud mitigation plan must now include a documented response scenario for a TraceMap-driven alert from an EU client.
If you are unsure how to separate food fraud from food defense in your own plan, our piece on building VACCP/TACCP gives the basic structure. For verifying supplier certificates appearing in your TRACES chain, the guide on how to confirm a supplier's FSSC 22000 certificate is useful.
30-Day Audit-Ready Checklist for Exporters
A realistic diagnostic and gap-closure cycle is 30 working days. This timeline suits a mid-sized manufacturer with active TRACES records; companies with irregular exports move faster, complex multi-site operations move slower.
Week 1 — diagnostic (Days 1–7)
- Compile an inventory of all TRACES certificates over the last 12 months, broken down by EU recipient country.
- Reconcile lot numbers and CN codes in export certificates with actual consignments. Any discrepancy is a potential AI alert trigger.
- Identify which of your EU clients are RASFF-sensitive: product category (honey, oils, spices, fish, dairy) plus a recipient country with an alert history.
Week 2 — gap closure (Days 8–14)
- Update the VACCP/TACCP register for the TraceMap scenario. Add the scenario "EU client received a RASFF alert based on AI cross-detection of our consignment."
- Review supplier verification files (FSSC 22000 cl. 9.2 / ISO 22000 cl. 7.4) against valid certificates — no expired documents and no skipped ABS checks.
- Add the ARA oil horizon-scanning case to the food fraud assessment as an example of AI-driven detection.
Week 3 — mock recall (Days 15–21)
- Run a mock recall with a target ≤ 4 hours (previously 24). Include the scenario "RASFF alert from EU client → request for our shipment → traceback to raw material supplier."
- Document it: timeline, responsibilities, notification scheme, list of documents for the regulator.
- Record the gap between actual time and the 4-hour target — that becomes the task list for the next cycle.
Week 4 — review + audit prep (Days 22–30)
- Internal audit against updated procedures (HACCP, VACCP, TACCP, traceability, supplier verification).
- Prepare a package for DG SANTE / RASFF investigation: consignment timeline, raw material certificates, mass balance, lab evidence health-check.
- Update training records for everyone involved in TRACES, shipments, and recall response.
Mid-CTA: If the procedures sound paper-only and you are not confident the mock recall will run in 4 hours, book a diagnostic traceability audit focused on the TraceMap scenario.
How Ekontrol Can Help
We have been supporting projects on preparation for European food safety audits since 2018 — from HACCP implementation to FSSC 22000 v6/v7. For TraceMap readiness we offer four distinct cooperation formats:
- Diagnostic audit — 2–3 weeks, gap report with a prioritized list of procedures (TRACES, VACCP/TACCP, traceability) that need rework for the TraceMap scenario.
- FSSC 22000 implementation — full cycle from HACCP plan and food fraud assessment to certification audit prep with a strengthened food defense / food fraud block.
- Audit support — assistance during certification, surveillance, or DG SANTE / RASFF investigations: working with the auditor, responding to queries, closing nonconformities.
- Annual support — supervision, documentation updates, mock recall drills with a target ≤ 4 hours.
For companies in the food industry and agriculture sector, we recommend starting with a diagnostic audit so you do not invest resources in reworking processes that are not actually critical to the TraceMap scenario. For a broad overview of the 2026 regulatory context, see our audit and compliance guide for 2026.
Sources
- European Commission, DG SANTE, "TraceMap" — food.ec.europa.eu/food-safety/acn/tracemap_en
- Food Safety Magazine, "EU Launches AI Traceability Platform" (10.03.2026) — food-safety.com
- New Food Magazine, "European Commission launches AI TraceMap tool" — newfoodmagazine.com
- Euronews / eunews.it — TraceMap launch coverage (10.03.2026)
- ISO 22000 (food safety management standard) — iso.org/standard/iso-22000
Need expert support implementing the changes covered above? Contact the Ekontrol team for a free consultation.
Tags

Need a certification consultation?
Free Consultation
TraceMap — What It Is and When It Launched
On March 10, 2026, the European Commission launched TraceMap — an AI system combining RASFF and TRACES to detect food fraud. The first case involved contaminated ARA oil from China. Ukrainian exporters need to update VACCP/TACCP under FSSC 22000 cl. 9.2.
DG SANTE introduced the platform as the first tool that effectively stitches together the EU's two main food control systems. Until March 10, RASFF (alerts) and TRACES (electronic certificates for goods movements) ran as parallel data sources without automatic links. Now an AI layer over these databases finds anomalies in minutes rather than days.
EU Commissioner for Health Olivér Várhelyi summed up the logic: "We connect the dots that fraudsters try to hide," as quoted by Food Safety Magazine.
For a Ukrainian exporter to the EU this means one thing: documents that previously passed through the gap between databases now face automatic cross-checking. This is the most systemic event in European food safety in the first half of 2026, after the update to FSSC 22000 v7 food fraud requirements.
How TraceMap Actually Works
TraceMap does not replace existing systems — it adds an analytical layer over two data flows that have run in parallel for 22 years:
- RASFF (Rapid Alert System for Food and Feed) — operating since 1979. Records national authorities' notifications about unsafe products: contamination, adulteration, mislabelling. RASFF processed more than 5,000 notifications in 2025.
- TRACES (TRAde Control and Expert System) — running since 2003. Electronic certification of goods movements across EU borders: consignments, operators, CN codes, lot numbers, veterinary and phytosanitary certificates. Millions of consignments pass through TRACES annually.
Until 2026, a national inspector would receive a RASFF alert and manually search TRACES for which consignments could have caused it. This took days, often weeks, especially when the supply chain ran across several countries and processing tiers. The TraceMap AI component does three things automatically:
- Pattern matching — compares operator, country of origin, product type, and movement period with historical alerts to identify recurring scenarios.
- Network analysis — builds graphs of links between operators even if they have no formal common ownership. Detects shell companies, resellers, and indirect chains.
- Anomaly detection — flags deviations in volumes, routes, and documents from normal sector behaviour. Unusual combinations of countries of origin, atypical logistics routes, and abnormal lot sizes land in the red zone.
The result for a national authority is a graphical dashboard with automatic crosslinks: operator, consignment, certificate, historical RASFF alerts, potential impacted brands. According to DG SANTE, the system identifies "patterns in minutes rather than days." Access is granted to competent authorities of all 27 Member States and TRACES-associated countries (Norway, Switzerland, Moldova, Ukraine).
Critical for business: TraceMap is not public. An exporter will not see how their data is matched against other operators'. But they will see the consequences — faster queries from the EU client, broader questions from the inspector at the port of arrival, or in the worst case, a RASFF alert citing a specific consignment without warning.
First Verified Case — ARA Oil from China
The showcase that accompanied the launch involved infant formula in several EU countries. RASFF recorded toxic effects in consumers and linked them to contaminated raw materials — the press cited cereulide, a toxin produced by Bacillus cereus. Investigators had to trace the chain from the finished product back to the raw material that had passed through processing in two countries.
TRACES already held data on consignments of infant formula and raw ingredients. TraceMap matched the RASFF alert with shipments of arachidonic acid (ARA oil) — a component added to formula to bring it closer to breast milk. The system isolated a single Chinese supplier whose deliveries simultaneously entered the production chains of several European brands during the alert period. Network analysis showed that formally independent brand manufacturers shared a single risk point in one raw material.
Human investigators could have handled this — in 5–10 working days, provided national authorities shared unstructured data. TraceMap cut the time to a few hours. New Food Magazine describes it as a shift from reactive recall to proactive detection. Futurist for Food analysts put it more bluntly: "end of plausible deniability" — you can no longer say "we didn't know where it came from."
For Ukrainian suppliers of raw materials into EU production chains (especially oils, spices, dairy ingredients, honey, fish), the takeaway is direct: TraceMap can reach your consignment with one or two inspector clicks, even if your direct buyer sits two or three tiers away in the chain. And if one of your consignments matched in time and region with a RASFF alert in a neighbouring sector, you land in the can of correlation automatically.
What Changes for Ukrainian Exporters to the EU
Ukraine has had associated TRACES access through DCFTA since 2017 — meaning your export certificate data already flows into the system that AI TraceMap now analyses. Three categories of exporters will feel the change most acutely.
Exporters appearing in TRACES
Any inaccuracy in CN codes, series, or lot numbers between the export certificate and the actual consignment is now detected faster. A document could previously pass due to limited inspector time for manual checks — now AI cross-references with historical RASFF alerts.
In practice: walk through the TRACES certificate process and verify that the document fields match the consignment passport. Particularly — series, production dates, net weight.
Suppliers of raw materials into EU production chains
If your EU client triggers a RASFF alert, TraceMap can automatically trace it back to your delivery, even through two or three processing tiers. This makes partial-batch traceability and supplier verification (FSSC 22000 v6/v7 cl. 9.2) a matter of contracts, not paperwork.
In practice: document traceability at lot/batch level, not contract level. Keep cross-reference tables of lot ↔ supplier ↔ receipt date for each ingredient.
Manufacturers with elevated food fraud risk
Categories with high adulteration rates — honey, oils, spices, fish, dairy. Your VACCP/TACCP analysis must account for the EU buyer receiving an automated alert about a suspicious pattern before you have closed the current shipment.
In practice: update your BRCGS vulnerability assessment and VACCP/TACCP plans for the AI cross-detection scenario. Add the ARA oil case as a horizon scanning reference. Review how many tiers deep into the chain you actually document — for high-risk categories, less than two tiers of tier-2 supplier verification no longer covers the real RASFF investigation risk.
A separate risk block is relabelling and mixing consignments between export orders. Until 2026 such actions could disappear between the exporter's paper records and electronic TRACES — now AI will detect a discrepancy between the volume entering the warehouse and the volume leaving for the EU, even when the documents look tidy.
How to Link TraceMap to FSSC 22000 and ISO 22000
TraceMap does not change the wording of any standard — but it changes the real bar for compliance. What was previously enough for a CB auditor may now fall short for DG SANTE and the EU buyer.
- FSSC 22000 v6/v7 Additional Requirements — Food Defense and Food Fraud Mitigation. Gaps in VACCP/TACCP that were previously known only internally now become visible to DG SANTE through TraceMap. The CB auditor will now expect evidence that your plan accounts for AI cross-detection and a reactive horizon ≤ 4 hours.
- ISO 22000:2018 cl. 8.3 (Traceability) — the formal "one step up, one step down" requirement remains. But ISO 22000 traceability requirements are now effectively a minimum — TraceMap makes the entire chain visible, so the EU buyer will demand full lot-level traceability as a contract condition.
- BRCGS Issue 9 cl. 5.4 — vulnerability assessment + horizon scanning. The ARA oil case should be added to horizon scanning as a fresh example of AI-driven detection.
- IFS Food v8 cl. 4.20 — food fraud mitigation plan. Mock recalls now have a target ≤ 4 hours, not the 24 that was standard until 2026.
- HACCP — the foundational hazard analysis under HACCP remains the base, but VACCP and TACCP as overlays need review against the TraceMap scenario.
- IFS Food v8 cl. 4.20 — the food fraud mitigation plan must now include a documented response scenario for a TraceMap-driven alert from an EU client.
If you are unsure how to separate food fraud from food defense in your own plan, our piece on building VACCP/TACCP gives the basic structure. For verifying supplier certificates appearing in your TRACES chain, the guide on how to confirm a supplier's FSSC 22000 certificate is useful.
30-Day Audit-Ready Checklist for Exporters
A realistic diagnostic and gap-closure cycle is 30 working days. This timeline suits a mid-sized manufacturer with active TRACES records; companies with irregular exports move faster, complex multi-site operations move slower.
Week 1 — diagnostic (Days 1–7)
- Compile an inventory of all TRACES certificates over the last 12 months, broken down by EU recipient country.
- Reconcile lot numbers and CN codes in export certificates with actual consignments. Any discrepancy is a potential AI alert trigger.
- Identify which of your EU clients are RASFF-sensitive: product category (honey, oils, spices, fish, dairy) plus a recipient country with an alert history.
Week 2 — gap closure (Days 8–14)
- Update the VACCP/TACCP register for the TraceMap scenario. Add the scenario "EU client received a RASFF alert based on AI cross-detection of our consignment."
- Review supplier verification files (FSSC 22000 cl. 9.2 / ISO 22000 cl. 7.4) against valid certificates — no expired documents and no skipped ABS checks.
- Add the ARA oil horizon-scanning case to the food fraud assessment as an example of AI-driven detection.
Week 3 — mock recall (Days 15–21)
- Run a mock recall with a target ≤ 4 hours (previously 24). Include the scenario "RASFF alert from EU client → request for our shipment → traceback to raw material supplier."
- Document it: timeline, responsibilities, notification scheme, list of documents for the regulator.
- Record the gap between actual time and the 4-hour target — that becomes the task list for the next cycle.
Week 4 — review + audit prep (Days 22–30)
- Internal audit against updated procedures (HACCP, VACCP, TACCP, traceability, supplier verification).
- Prepare a package for DG SANTE / RASFF investigation: consignment timeline, raw material certificates, mass balance, lab evidence health-check.
- Update training records for everyone involved in TRACES, shipments, and recall response.
Mid-CTA: If the procedures sound paper-only and you are not confident the mock recall will run in 4 hours, book a diagnostic traceability audit focused on the TraceMap scenario.
How Ekontrol Can Help
We have been supporting projects on preparation for European food safety audits since 2018 — from HACCP implementation to FSSC 22000 v6/v7. For TraceMap readiness we offer four distinct cooperation formats:
- Diagnostic audit — 2–3 weeks, gap report with a prioritized list of procedures (TRACES, VACCP/TACCP, traceability) that need rework for the TraceMap scenario.
- FSSC 22000 implementation — full cycle from HACCP plan and food fraud assessment to certification audit prep with a strengthened food defense / food fraud block.
- Audit support — assistance during certification, surveillance, or DG SANTE / RASFF investigations: working with the auditor, responding to queries, closing nonconformities.
- Annual support — supervision, documentation updates, mock recall drills with a target ≤ 4 hours.
For companies in the food industry and agriculture sector, we recommend starting with a diagnostic audit so you do not invest resources in reworking processes that are not actually critical to the TraceMap scenario. For a broad overview of the 2026 regulatory context, see our audit and compliance guide for 2026.
Sources
- European Commission, DG SANTE, "TraceMap" — food.ec.europa.eu/food-safety/acn/tracemap_en
- Food Safety Magazine, "EU Launches AI Traceability Platform" (10.03.2026) — food-safety.com
- New Food Magazine, "European Commission launches AI TraceMap tool" — newfoodmagazine.com
- Euronews / eunews.it — TraceMap launch coverage (10.03.2026)
- ISO 22000 (food safety management standard) — iso.org/standard/iso-22000
Need expert support implementing the changes covered above? Contact the Ekontrol team for a free consultation.


