Importer requirements come first
CBAM entered its definitive regime on 1 January 2026. Ask the importer or declarant to confirm the goods in scope and issue the current data fields for the transaction. Record the responsible contact and reporting period. Do not reuse a transitional-period template without checking its suitability for the present request.
Sources:[1]
Product identity and processing route
Connect the requested goods to the order description, grade and standard, form, size, delivery condition, quantity, and origin information. Record heat or lot references where they help reconcile the goods. The importer or its adviser should confirm the customs classification; a steel grade or MTC by itself does not settle CBAM scope.
Each processing step on its own line
List the producing installation and downstream operations relevant to the request, with the operator for each. Distinguish steel production, heat treatment, stock removal, machining, and any coating process. Have the declarant confirm the calculation treatment of those steps under the applicable method rather than adding their data to a total without a defined basis.
Data availability has to be checked per RFQ
Ask each record holder which inputs are available, their units and period, calculation version, supporting files, and expected delivery date. JOTAIN can coordinate the order, mill, and processing information with the responsible parties. Keep missing data and verification status visible, and obtain the declarant's instructions before using any permitted alternative or default.
Is CBAM data required for this order?
Identify the importer, goods description, proposed CN code, origin, customs arrangement, quantity basis, and declaration owner before requesting data. Commission resources guide reporting but do not classify a shipment; advisers should confirm scope before the declarant issues targeted fields.
Fields to confirm with the importer
| Review step | Required input | Responsible reviewer | Release condition |
|---|---|---|---|
| Goods scope | Goods description, proposed CN code, origin, importer, quantity basis | Declarant with customs or legal adviser | Scope and classification basis recorded |
| Operator data | Installation identity, production period, methodology, calculation version, evidence index | Non-EU operator and declarant data contact | Fields complete or gaps clearly accepted |
| Actual-data verification | Verifier identity, accreditation context, covered installation and period, report reference | Declarant and verification reviewer | Required verification available and matched |
| Declaration package | Registry-ready fields, product reconciliation, default-value decision, approvals | Authorised declarant | Final submission basis approved by declarant |
A request that can be updated and audited
Use one controlled template with field definitions, statuses, units, evidence links, and a contact. Log corrected calculations, installations, periods, reports, and quantities. Reconcile order and shipment identifiers, and preserve the declarant's rationale for gaps or permitted defaults.
RFQ example
Item: Steel bars, [grade / standard / edition], [size], [condition], [quantity]
Customs details: Proposed CN code [buyer entry], origin [state], EU importer [entity], authorised declarant [entity / contact]. Buyer or declarant to confirm classification and applicability.
Template: Respond in CBAM-SB revision [x] using the field definitions and status values supplied by the declarant.
Installation data: Identify the relevant non-EU operator, installation, production period, calculation method and version, and supporting-file index.
Product records: State the ISO 10474 document type and the heat or lot, bundle, invoice, and shipment references used to match the data to the goods.
Verification: For actual data, state the verifier and report reference, installation and period covered, accreditation context, and registry availability. Mark pending items accurately.
Missing data: Do not estimate. Mark the field unavailable, operator pending, verifier pending, not applicable, or declarant review required; add the responsible person and target date.
Changes: Notify the declarant of corrected calculations, changed operators, periods, goods identifiers, or reports before the final deadline.
Supplier role: Provide source data and corrections. The importer or declarant remains responsible for CBAM compliance and customs classification.Questions buyers ask
What should EU buyers send for a CBAM-related steel bar data request?
Send destination market, importer role, product form, grade standard, size, quantity, delivery condition, mill-origin requirement where applicable, processing route, certificate needs, and the requested data format.
Can JOTAIN declare CBAM approval for a steel bar order?
No. JOTAIN can coordinate buyer data requests where applicable, but regulatory responsibility, accepted format, and importer reporting requirements should be reviewed by the buyer or importer.
How should buyers describe CBAM-related data requests?
State destination market, importer requirement, product scope, mill route, processing route, document expectations, timing, and any embedded-emissions data request. Avoid treating data coordination as a certification claim.
RFQ checklist
- Destination market and importer or declarant role
- Product form, grade standard, equivalent grade, and HS or CN code if already determined
- Diameter, length, quantity, and delivery condition
- Mill-origin and heat number requirements where applicable
- Processing route to be reviewed before order release
- Certificate, inspection, and traceability document requirements
- Requested data format, reporting period, and submission timing
- Packing, shipment documents, and buyer reference requirements
- Identify the EU importer, authorised declarant, representative, and accountable internal reviewer.
- Have qualified advisers confirm goods scope and CN classification before supplier outreach.
- Use the current declarant-issued template, field definitions, allowed statuses, and deadlines.
- Identify each non-EU installation operator and the calculation period requested.
- Separate product traceability references from installation calculations and verification reports.
- Require verifier and report scope details only where actual-data verification is applicable.
- Prohibit invented values and route default-value decisions to the authorised declarant.
- Maintain a revision log and reconcile the final package to shipment and registry records.
References
Inquiry support
Planning the packing and document set?
Send the drawing or RFQ with the grade, size, condition, processing, inspection, quantity, and destination. We can flag open points before quotation.