CN codes set limits on how steel processes are classified
The EU’s definitive CBAM methodology limits how steel producers classify products and calculate embedded emissions, including the ability to split the same physical production process into multiple carbon-reporting categories. For steel mills, processors, monitoring and reporting teams, verifiers and EU importers, the eight-digit Combined Nomenclature (CN) code is used to determine the applicable functional unit and production process.
The European Commission’s CBAM Q&A states that an installation cannot normally establish more than one production process for the same CN code. Certain groups of steel products must be combined into a multifunctional production process when they differ only in size or shape and use the same precursors in the same proportions.
These requirements are designed to prevent dividing one physical production process into separate reporting categories in order to obtain more favourable emissions intensities. For mills producing multiple widths, thicknesses or product forms on the same line, the approach affects how emissions are monitored across output.
While a commercial catalogue may list dozens of stock-keeping units, CBAM does not necessarily allow a separate emissions calculation for every marketed grade. Differences in CN code, precursor route or a genuinely distinct production-process boundary can be material, requiring accurate identification rather than administrative consolidation.
Verified emissions values can influence import costs
For steel suppliers and EU buyers, classification decisions operate within the current-law compliance framework rather than as voluntary carbon accounting. Importers need emissions values that can be defended in their CBAM declarations, while suppliers must retain records that an accredited verifier and the buyer can trace to the relevant installation and reporting period.
Commercial product-footprint claims should be kept distinct from the emissions values calculated under CBAM when their boundaries differ. The quality of verified data can also affect financial outcomes for suppliers and buyers.
Where actual emissions values are available and permitted, they may preserve benefits linked to cleaner feedstock or production routes. Where rules require default values, calculations may be less favourable, particularly as relevant default mark-ups increase during the definitive phase.
Suppliers able to quantify potential cost differences in euros may be better positioned to explain the value of verified data in price negotiations and long-term contracts than suppliers relying on general low-carbon claims.
Product master data links customs classification to MRV records
Steel plants are expected to maintain controlled product-to-CN-code master data connected to production orders, material recipes and output records. Changes in customs classification should trigger a review of emissions calculations because they may affect the applicable functional unit, production-process mapping and benchmark.
The verifier should be able to trace a reported tonne from the CBAM declaration back to the relevant production process using documented records. This tracing is intended to avoid reliance on manual interpretations of commercial product names.
Incorrect classification can create financial and compliance risks for both sides of the supply chain. An overly broad calculation may obscure benefits from a cleaner production route, while an excessively narrow division may produce an emissions intensity that CBAM methodology does not permit.
EU buyers are therefore likely to require more than an emissions figure. They need understanding of classification choices, process boundaries and supporting evidence behind supplier-reported values.
Contracts and governance address operational changes affecting emissions
Supplier governance is part of steel monitoring, reporting and verification (MRV). Purchase contracts should specify producing installation details, reporting period coverage, emissions-data format, verification requirements and procedures for correcting reported information.
If a supplier changes its production site, manufacturing route or precursor inputs without notifying the buyer, the emissions value applicable to delivered products may differ from assumptions used when commercial prices were agreed. Change-notification clauses can support compliance by giving buyers a mechanism to review implications before reporting or contractual settlements are affected.
For Western Balkan processors using legacy enterprise resource planning (ERP) systems, CN codes may be maintained primarily by customs or sales teams rather than engineering and production departments. CBAM increases the need for coordination between these functions because shared master data can affect multiple compliance elements.
The same product master data can influence customs treatment, embedded-emissions calculations, applicable free-allocation adjustments and importer certificate exposure. Errors or inconsistencies can therefore affect several parts of the compliance process across different teams.
Decision files connect CN codes with precursors and verified results
Companies are expected to establish cross-functional governance involving customs, production, finance and MRV teams. Each covered product family should have an approved CN code, defined process boundary, precursor map and responsible owner.
Changes should be recorded and reviewed before they feed into annual emissions reporting. A practical test described for compliance is whether a company can explain its reported result to both a verifier and a commercial manager using the same underlying records.
The compliance file should connect purchasing, production, customs and finance using routine industrial data, controlled assumptions and documented fallback procedures. At minimum it should link CN code selection, relevant precursors, process boundary definition, production records and verified emissions value.
The decision file should also identify who approves assumptions and specify an alternative treatment if preferred approaches cannot be substantiated. Establishing fallback procedures in advance is intended to prevent discovery of actual exposure only after challenges by a verifier, customs authority or authorised CBAM declarant.
Under CBAM, customs classification and carbon accounting are increasingly interconnected. An incorrect CN code is no longer only a customs issue because it can also affect emissions calculations and resulting carbon costs.