EU Food Import Controls Monitor (Reg 2019/1793) avatar

EU Food Import Controls Monitor (Reg 2019/1793)

Pricing

from $20.00 / 1,000 watchlist item checkeds

Go to Apify Store
EU Food Import Controls Monitor (Reg 2019/1793)

EU Food Import Controls Monitor (Reg 2019/1793)

Checks a watchlist of commodity/origin-country pairs against EU Regulation 2019/1793's consolidated import-control annexes. Reports CN code, hazard, inspection frequency and conditions, with explicit change states (FIRST_SEEN, UNCHANGED, FREQUENCY_CHANGED, ADDED, REMOVED). No personal data.

Pricing

from $20.00 / 1,000 watchlist item checkeds

Rating

0.0

(0)

Developer

Pavel Staurouski

Pavel Staurouski

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Share

Checks a watchlist of commodity/origin-country combinations against the EUR-Lex consolidated text of Commission Implementing Regulation (EU) 2019/1793 (temporary increase of official controls and emergency measures governing the entry into the Union of certain food and feed of non-animal origin from certain third countries).

What you get

One record per watchlist item per matched annex entry: which annex it comes from (Annex I = temporary increase of official controls, Annex II = special conditions due to mycotoxin/pesticide/microbiological/Sudan-dye/plant-toxin risk, Annex IIa = suspension of entry), the CN code (with the "ex" qualifier and TARIC sub-division preserved exactly as published), product description, origin country (and dispatch country, where the annex states one separately), hazard, inspection frequency, and the resolved text of any footnoted special condition - not just a bare superscript number.

Every record also carries an explicit state: FIRST_SEEN, UNCHANGED, FREQUENCY_CHANGED, HAZARD_CHANGED, CONDITIONS_CHANGED, ADDED, REMOVED, NOT_LISTED, INVALID_INPUT, or FETCH_ERROR. A failed fetch always produces an explicit FETCH_ERROR record per watchlist item, never a silent "no change" - and never touches your previously-saved comparison state, so the next successful run still compares against the last known-good snapshot.

What it does not do

No legal advice, no certification. This is a documentation tool over the EU's own documentation-tool consolidated text (EUR-Lex's own disclaimer: "has no legal effect"; the authentic version is the Official Journal). No personal data: entries are about commodities, countries and chemical/legal references, never contact names or signatories.

Why you might need this

An import-compliance manager, customs broker, or supplier-quality team sourcing a specific commodity from a specific third country needs to know immediately when that exact combination's inspection frequency rises, a special condition is added, or the commodity is suspended outright. Missing one of these changes means a consignment arrives at the border control post cleared for the old frequency and gets pulled for the new, stricter one anyway, with demurrage and storage costs accruing while customs re-checks it, or outright rejected if the commodity was suspended since the last time anyone read the annex by hand. The Commission issues an amending regulation roughly every 4-8 weeks in practice, which is too often to re-read the whole consolidated annex manually before every shipment.

Input

{
"watchlist": [
{ "cnCode": "1202 42 00", "originCountry": "Argentina" },
{ "productKeyword": "betel leaves", "originCountry": "Bangladesh" },
{ "cnCode": "0802 51 00", "originCountry": "United States" }
]
}

Each watchlist item needs originCountry (full name or ISO-2 code, e.g. "Argentina" or "AR") plus at least one of cnCode (matched against the published CN code; an "ex"-qualified annex entry is matched as a prefix in either direction) or productKeyword (case-insensitive substring match against the published product description). If both are given on one item, both must match.

Sample output

{
"entryId": "II-1|1|BD|14049000|Foodstuffs containing or consisting of betel leaves (Piper betle) (Food)",
"annex": "II-1",
"annexLabel": "1. Food and feed of non-animal origin referred to in Article 1(1), point (b)(i)",
"rowNumber": "1",
"originCountry": "Bangladesh",
"originCountryCode": "BD",
"dispatchCountry": null,
"dispatchCountryCode": null,
"productDescription": "Foodstuffs containing or consisting of betel leaves (Piper betle) (Food)",
"cnCode": "ex 1404 90 00",
"cnCodeNormalized": "14049000",
"cnCodeIsEx": true,
"taricSubdivision": "10",
"hazard": "Salmonella",
"frequencyPercent": 50,
"frequencyRaw": "50",
"specialConditions": [
"Foodstuffs containing or consisting of betel leaves (Piper betle) including, but not limited to, those declared under CN code 1404 90 00.",
"The sampling and the analyses shall be performed in accordance with the sampling procedures and the analytical reference methods set out in point 1(a) of Annex III."
],
"matchedVia": "originCountry",
"consolidatedAsOf": "2026-06-30",
"sourceUrl": "https://publications.europa.eu/resource/consolidation/2019R1793%2F2026-06-30.ENG.xhtml",
"watchlistItem": { "productKeyword": "betel leaves", "originCountry": "Bangladesh" },
"matchState": "UNCHANGED",
"changedFields": [],
"checkedAt": "2026-10-08T11:27:31.749Z"
}

This is a real record from a live run against the current consolidated text: a 50% physical/identity check frequency on betel leaves from Bangladesh, with both special-condition footnotes resolved to their full text rather than left as a bare superscript number.

Change tracking across runs

Run this Actor on a schedule. Each watchlist item's last-seen snapshot (hazard, frequency, special conditions) is stored per Actor, so every subsequent run reports exactly what changed since the last one, not just the current state.

Pricing

Pay per run started, plus per watchlist item checked (not per matched row - a single item can legitimately match several annex rows, e.g. a broad keyword against several CN codes under one country). See the Pricing tab for exact rates.