Methodology and data sources

Which sources we use

The basis is the consolidated EU regulation versions published on EUR-Lex. A consolidated version merges the original act with all later amendments into one text, so it reflects the legal state in force on a given date.

EUR-Lex publishes consolidated versions with a delay, usually a few weeks after the amendments enter into force. Within that window we read the amending act in the Official Journal, and it is its date that appears with the result as the source version date. This way the database runs ahead of the consolidated text, not behind it.

• RussiaCouncil Regulation (EU) No 833/2014. Status as of the version of 24/07/2026. Text on EUR-Lex
• BelarusCouncil Regulation (EC) No 765/2006. Status as of the version of 24/07/2026. Text on EUR-Lex
• North KoreaCouncil Regulation (EU) 2017/1509. Status as of the version of 17/12/2025. Text on EUR-Lex
• IranCouncil Regulation (EU) No 267/2012. Status as of the version of 01/08/2026. Text on EUR-Lex
• Iran (military support to Russia)Council Regulation (EU) 2023/1529. Status as of the version of 01/08/2026. Text on EUR-Lex
• Crimea and SevastopolCouncil Regulation (EU) No 692/2014. Status as of the version of 25/02/2025. Text on EUR-Lex
• Donetsk, Luhansk, Zaporizhzhia and Kherson oblastsCouncil Regulation (EU) 2022/263. Status as of the version of 25/02/2025. Text on EUR-Lex
• TARIC as a supplementWe use the EU integrated customs tariff (TARIC) as an auxiliary source, to confirm the scope and correctness of CN codes. The regulations themselves remain the binding source for the scope of sanctions. TARIC.

How we build the database

We extract CN codes from the regulation annexes and then normalize them to a uniform form stored in the cn_code_norm field (no spaces or separators). The search matches in an exact mode and by prefix, because the acts list not only 8-digit codes but also 4-digit positions covering whole groups of goods.

We assign each position a set of fields:

• status, that is whether and how the code is restricted,
• regime (one of Russia (833/2014); Belarus (765/2006); North Korea (2017/1509); Iran (267/2012); Iran (military support to Russia, 2023/1529); Crimea and Sevastopol (692/2014); Donetsk, Luhansk, Zaporizhzhia and Kherson oblasts (2022/263)),
• the annex where the position appears,
• the article that is the legal basis,
• exemptions and derogations (for example art. 3k),
• the source version date.

Data quality

Every position carries a data quality label shown with the result. "Verified" means the position was checked against the act text on EUR-Lex. "To review" means it is still waiting for that check. The figures below come straight from the database.

• To reviewThe "TO REVIEW" badge on a single result means a match by a shortened code (for example a 4-digit position) or a position that is still under verification. Always confirm such a result on EUR-Lex.

How we check that the data is current

Every day we compare the database with the consolidated texts of the regulations in the Official Journal of the EU and with announcements of the EU institutions on sanctions, entry by entry. Every difference is reviewed before it reaches the database: we publish changes only after review, as a new data release.

The date next to "Data checked against EU sources" is the moment of the last complete comparison. If the latest comparison did not cover all sources, we show the date of the last complete one, not today.

Data updates

EU sanctions packages are released every few weeks and each can add or change CN codes and articles. The database is continuously monitored and updated after every change to the regulations. The binding text remains the act on EUR-Lex, which we link from every result.

What the tool does not do

• It is not legal or customs advice.
• It does not replace EUR-Lex, it refers you to the binding regulation text.
• It does not cover screening of sanctioned persons and entities. That is a separate mechanism run independently.

Frequently asked questions