The 2026 compliance deadlines, and where the fields belong

Compliance regimes tend to arrive as a date and a reporting obligation. The date is the easy part to track. The harder part is that each regime asks for a field, and the field has to live somewhere in your data model before the deadline, or the deadline becomes a backfill.

Three regimes matter for retail import right now: CBAM, the UFLPA and the EUDR. They differ in scope, but they share a shape. Each wants a piece of evidence attached to a specific node in the supply chain, and that node is narrower than most systems record. Timelines move, so confirm the current dates against the official sources before you plan a programme around them.

The deadlines at a glance

• CBAM. In force for covered goods, with reporting obligations on embedded emissions.
• UFLPA. In force. Places the due-diligence burden on the importer for goods from a prohibited source.
• EUDR. Deforestation compliance expectations landing in December 2026, with geolocation and due-diligence statements for commodities in scope.

CBAM wants emissions, so the field belongs at the leg

The Carbon Border Adjustment Mechanism asks for embedded emissions by product and by movement. Emissions are a property of the leg, not the order and not the shipment as a whole. A sea leg, an air leg and a road leg have different intensities, and a single shipment can carry more than one. If your model only knows the shipment, you cannot answer CBAM without guessing, and a guess is not a report.

Stored at the leg, a CBAM figure for a shipment is a rollup of its legs. A what-if on a different mode is a recomputation, not a new spreadsheet.

UFLPA wants origin evidence, so the field belongs at the SKU line

The Uyghur Forced Labor Prevention Act puts the burden on the importer to show that goods are not from a prohibited source. That is a due-diligence obligation, and it resolves to origin evidence at the level of the goods themselves. Origin is a property of a SKU line. A country code on the order header is not enough, because one order routinely mixes origins across lines, and the header tells you only the dominant one.

EUDR wants plot geometry, so the field belongs at the raw material's line

The EU Deforestation Regulation asks for geolocation and due-diligence statements tied to the commodities in scope. The plot geometry belongs to the raw material, which means it attaches where the SKU line does, upstream of packing. Retro-fitting plot data onto historical shipments is a data-collection project against parties who have already moved on and have little reason to answer.

Why the node matters more than the report

Every regime above can be satisfied by a backfill, and every backfill is a project: find the parties, request the documents, reconcile the formats, then store the result somewhere that has no field for it. Building the field into the record while the goods are in transit costs a schema decision. Building it after costs a programme, and the programme gets harder every month it is deferred.

Compliance is not a report you produce at the end. It is data you capture at the point it is born, and the deadline only decides when you are asked to show it. The teams that will find 2026 cheap are the ones that decided where the fields live while the goods were still in transit.