Under the EU’s definitive CBAM methodology, steel producers’ product classification and embedded emissions calculations are linked to the eight-digit Combined Nomenclature (CN) code. The CN code is used by steel mills, processors, monitoring and reporting teams, verifiers, and EU importers to determine the applicable functional unit and production process.
CN codes set limits on production-process classification
The European Commission’s CBAM Q&A says an installation cannot normally establish more than one production process for the same CN code. It also states that certain groups of steel products must be combined into a multifunctional production process when they differ only in size or shape while using the same precursors in the same proportions.
The approach is designed to prevent splitting one physical production process into separate reporting categories to obtain more favourable emissions intensities. For mills producing multiple widths, thicknesses, or product forms on the same line, the requirement affects how emissions monitoring is applied across marketed grades.
While CBAM may not permit a separate emissions calculation for every stock-keeping unit in a commercial catalogue, differences can still matter when they involve CN code changes, different precursor routes, or a genuinely distinct production-process boundary. Companies are expected to identify those distinctions accurately rather than combining products for administrative convenience.
Verified emissions values influence import costs
For steel suppliers and EU buyers, classification decisions form part of the current-law compliance framework rather than a voluntary carbon-accounting choice. 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 are expected to be kept distinct from emissions values calculated under CBAM when their boundaries differ. The quality of verified data can also have financial consequences for pricing and contract discussions.
Where actual emissions values are available and permitted, they may preserve benefits associated with cleaner feedstock or production routes. Where rules require default values, calculations may be less favourable, particularly as default mark-ups increase during the definitive phase.
Suppliers that can quantify potential cost differences in euros are positioned to explain the value of verified data in price negotiations and long-term contracts compared with suppliers relying on general low-carbon claims.
Product master data links customs classification to MRV
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 the emissions calculation because they may affect the applicable functional unit, production-process mapping, and benchmark.
The verifier is expected to trace a reported tonne from the CBAM declaration back to the relevant production process using documented records rather than relying on manual interpretations of commercial product names. Incorrect classification can create both financial and compliance risks if calculations are too broad or too narrow relative to what the methodology permits.
EU buyers are therefore likely to require more than an emissions figure. They need information on classification choices, process boundaries, and supporting evidence behind values reported by suppliers.
Contract governance covers changes in production inputs
Supplier governance is described as part of the steel monitoring, reporting and verification system. Purchase contracts should specify the producing installation, reporting period, 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 are presented as a mechanism for buyers to review operational implications before they affect reporting or contractual settlements.
Cross-functional CN-code controls for Western Balkan processors
For Western Balkan steel processors using legacy enterprise resource planning 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.
The same product master data can affect customs treatment, embedded-emissions calculations, applicable free-allocation adjustments, and an importer’s certificate exposure. Errors or inconsistencies can therefore affect multiple parts of the compliance process beyond MRV reporting alone.
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, with changes recorded and reviewed before they feed into annual emissions reporting.
Decision files connect CN codes to verified tonnage
A practical test described in the methodology 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, the decision file should link the CN code, relevant precursors, process boundary, production records, and verified emissions value. It should also identify who approves assumptions and specify alternative treatment if preferred approaches cannot be substantiated.
The methodology highlights that establishing fallback in advance may prevent discovery of actual exposure only when a verifier, customs authority, or authorised CBAM declarant challenges a calculation. It also notes that customs classification and carbon accounting are increasingly interconnected under CBAM.
An incorrect CN code is therefore not only a customs issue; it can also affect emissions calculations and resulting carbon costs.