ATEX Zone Classification: Zones 0-2 and 20-22 Explained
ATEX zone classification explained: how zones 0/1/2 and 20/21/22 map to product attributes and why they matter for clean catalog data.
Supplier feeds for explosion-proof equipment arrive with zone data scattered across free-text descriptions, buried PDF certificates, and inconsistently coded attribute fields — one vendor writes “Zone 1,” another writes “Z1,” a third omits the zone entirely and lists only the equipment category. That inconsistency breaks matching, fragments catalog records, and makes it impossible for buyers or AI search to confidently specify a product for a hazardous location. Claro normalizes these safety attributes from source, resolves the supplier records that describe the same device, and writes clean, provenance-tracked zone and category fields back into your PIM or ERP so the catalog stays trusted as new feeds arrive.
Definition
ATEX zone classification is the European framework that ranks explosive-atmosphere areas by how often and how long a hazardous gas, vapor, mist, or dust cloud is present, so equipment can be matched to the risk of the location it operates in.
The framework divides hazardous locations into two families. Gas, vapor, and mist atmospheres use Zone 0 (present continuously or for long periods), Zone 1 (likely in normal operation), and Zone 2 (unlikely, and only briefly, in normal operation). Dust atmospheres use a parallel scheme: Zone 20, Zone 21, and Zone 22. The term comes from the EU ATEX directives, which govern both the equipment sold into these areas and the workplaces that operate them.
Each zone maps to an equipment category that a product must satisfy. A device certified to Category 1 may be installed in the most demanding zones (0 or 20), Category 2 covers zones 1 or 21, and Category 3 covers zones 2 or 22. On a product, this surfaces as an ATEX marking string alongside the equipment group, gas or dust grouping, temperature class, and protection concept. For a product-data team, the zone is not just a safety fact: it is a structured attribute that determines whether a buyer can legally and safely specify the item for a given site. See how to read an ATEX marking for a full walkthrough of the string format.
| Zone | Atmosphere type | Frequency of explosive atmosphere | Required equipment category |
|---|---|---|---|
| Zone 0 | Gas / vapor / mist | Continuously or for long periods | Category 1G |
| Zone 1 | Gas / vapor / mist | Likely in normal operation | Category 2G |
| Zone 2 | Gas / vapor / mist | Unlikely; only brief if present | Category 3G |
| Zone 20 | Combustible dust | Continuously or for long periods | Category 1D |
| Zone 21 | Combustible dust | Likely in normal operation | Category 2D |
| Zone 22 | Combustible dust | Unlikely; only brief if present | Category 3D |
Why ATEX zone data matters for catalog quality
For distributors, ATEX data is a compliance-critical attribute that must be exact, consistent, and provenance-tracked before it can be trusted downstream. When it is inconsistent, three things break: matching, enrichment, and AI search.
Matching breaks because identity resolution cannot confidently merge two supplier records for the same explosion-proof junction box if one carries a clean zone attribute and the other carries none. Deduplication then leaves split records and a fragmented catalog.
Enrichment stalls because normalizing zone values into a single canonical field — and deriving the implied equipment category from the marking — is the only way to fill gaps suppliers left behind and validate the values they did provide. The pattern is the same discipline applied to an IP rating or a NEMA enclosure type: take a heterogeneous safety attribute and turn it into a trustworthy, queryable spec.
AI search fails because when a buyer or an AI shopping assistant asks for a Category 2 device for a Zone 1 flour-handling line, the engine can only answer if records carry a clean, machine-readable zone attribute with a traceable source. Without it, search either returns no results or surfaces equipment that was never rated for that location.
Before and after: messy vs. trusted ATEX catalog data
| Before — messy supplier data | After — trusted catalog data |
|---|---|
| Zone stored as free text: 'Zone 1', 'Z1', 'Zn. 1', or missing entirely | Normalized to a controlled vocabulary field with Zone 1 canonical value |
| Equipment category buried in a long description string | Category 2G stored as a discrete, filterable attribute |
| Certificate reference absent or in a PDF filename | Certificate number attached as provenance on the zone and category fields |
| Same explosion-proof enclosure split across three supplier records | Single resolved entity with best attributes merged from all sources |
| AI search returns no match for 'Category 2 Zone 1 junction box' | Machine-readable zone and category fields return the correct product instantly |
Claro applies this normalization continuously. As new supplier feeds arrive, zone and category values are extracted, validated against the certified marking, and written back into your PIM or ERP with a source link — so every enriched value points back to the certificate it came from. See how Claro fills missing attributes with provenance for the underlying discipline.
Related
Glossary
How to Read an ATEX Marking
Decode the equipment group, category, gas/dust grouping, and temperature class in an ATEX string.
Glossary
IP Ratings Explained
The ingress protection scheme that often sits next to ATEX data on the same product record.
Glossary
NEMA Enclosure Types
The North American enclosure framework distributors cross-reference against ATEX and IP.
Comparison
ATEX vs. IECEx
How the European ATEX directives and the international IECEx scheme differ and when a product needs both.
Tool
ATEX Marking Validator
Check an ATEX marking string for valid group, category, and temperature-class syntax.
Tool
Attribute Coverage Analyzer
Find which products are missing safety attributes like zone, category, or IP rating.
FAQ
What is the difference between an ATEX zone and an ATEX category?
A zone describes the location: how often an explosive atmosphere is present there. A category describes the equipment: the level of protection a product provides. The two are linked by rule. Category 1 equipment suits Zone 0 or 20, Category 2 suits Zone 1 or 21, and Category 3 suits Zone 2 or 22. In a product record, store both so buyers can match equipment to a site.
What do Zone 20, 21, and 22 mean?
They are the dust equivalents of the gas zones. Zone 20 means a combustible dust cloud is present continuously or for long periods, Zone 21 means it is likely in normal operation, and Zone 22 means it is unlikely and only brief. They appear in environments like flour mills, grain handling, sugar processing, and powder coating.
How should ATEX zone data be stored in a product catalog?
Store the certified equipment category and the implied zones as separate, normalized fields rather than free text. Keep the full marking string for reference, and attach the certificate as the source of provenance. Consistent fields let you match, deduplicate, and surface the attribute in search and AI answers without re-parsing copy each time.
Is ATEX the same as IECEx?
No. ATEX is the European regulatory framework, while IECEx is an international certification scheme using the same underlying IEC standards and zone concepts. Many products carry both. In catalog data, treat them as distinct attributes that frequently co-occur, and normalize each so a buyer can filter on either.
Can I derive the ATEX zone from a product description?
You can flag a likely value, but you should never finalize a zone or category from marketing text alone. Compliance-critical attributes must be confirmed against the certified marking or certificate. Treat any value parsed from description fields as a candidate for review, not a verified fact.
Claro
See how Claro handles this in production
This concept is one piece of keeping a catalog trusted. See how Claro resolves identity, enriches missing attributes, and validates every update before it reaches your PIM or ERP.
Learn more