CSRD, CBAM, Toll, eFTI: what each asks of a tender
Four European regimes now reach into freight procurement, and each asks for a different piece of lane data you either capture at tender time or scramble for later.
Freight procurement used to end at the award. Increasingly it does not, because several European regimes now depend on data that only exists cleanly at tender time. Capture that data while you are already handling lanes, carriers and volumes, and compliance becomes a by-product of the award. Miss it, and each regime turns into a separate retrospective project, reconstructing from invoices what you could have recorded once.
None of what follows is legal advice, and the specifics of each regime evolve. The point is narrower and durable: each regime asks for a particular slice of lane data, and the tender is where that slice is cheapest to collect.
Why compliance belongs in the tender
The data these regimes need — distances, modes, vehicle classes, carrier identities, the nature of the goods — is exactly the data a tender already assembles. Treating compliance as a downstream reporting task means gathering it a second time, from worse sources, months later. Treating it as part of the award means the lane you are already pricing carries the fields the regime will ask for. The work is the same; only the timing changes, and timing is the whole cost.
The four regimes, briefly
CSRD — emissions disclosure
The Corporate Sustainability Reporting Directive asks organisations to disclose the emissions associated with their activity, transport included. For a tender, that means each lane needs the inputs from which freight emissions are computed — distance, mode, and load basis — captured against the awarded carrier so the figure can be produced and, later, defended.
CBAM — carbon cost at the border
The Carbon Border Adjustment Mechanism attaches a carbon cost to certain goods imported into the EU, identified by their customs classification. Where a tender moves CBAM-affected goods, the relevant lanes need the classification captured so the exposure can be attributed rather than estimated after the fact.
Toll — road-charge attribution
Road tolls are a real and rising cost that a blended rate hides. Attributing toll to the lanes that incur it — using distance and vehicle class — turns a lump-sum surcharge into a line you can see, compare between carriers, and defend, rather than a number you accept because it arrived on an invoice.
eFTI — electronic freight information
The electronic Freight Transport Information framework concerns freight data being available in a structured, electronic form that authorities can accept. For procurement, the implication is upstream: the cleaner and more structured your lane and carrier data is at award time, the closer you already are to producing the electronic export the framework anticipates.
The same awarded lane — DE-Hamburg → FR-Lyon, a known distance, a known vehicle class, a known carrier — feeds all four regimes. Recorded once at the award, it produces the emissions input, the toll attribution, the CBAM flag where relevant, and a clean row for an electronic export. Recorded never, it becomes four reconstructions.
The field that is easiest to lose
Across all four regimes, the input most often missing at reporting time is the same one: a stable, accurate lane distance tied to a stable lane identifier. Emissions need it. Toll attribution needs it. Even the structured export the electronic framework anticipates reads more cleanly when distance is a recorded fact rather than a later lookup. Distance feels trivial at award time — it is just a number — which is exactly why it is not captured, and exactly why it has to be reconstructed, lane by lane, when four separate reports all turn out to need it. Record it once, against the awarded lane, and four regimes stop asking for it separately.
The same logic applies to the awarded carrier's identity, the vehicle class, and the goods classification where CBAM is in play. None is hard to record while the lane is in front of you. All are painful to reconstruct months later from invoices that were never designed to answer a compliance question. The pattern is consistent: the compliance-relevant fields are cheap at the award and expensive everywhere else.
Capture once, report many times
The unifying move is simple to state and easy to skip: capture the compliance-relevant fields as part of the award, not as a report you assemble afterwards. Configure what each lane needs while you are pricing it, and the regimes draw from one clean source instead of four scavenged ones. Any emissions or exposure figure that results should trace back to those inputs, so it holds up under the same scrutiny as the award itself.
There is a strategic reason to get ahead of this rather than wait for each demand to land. Compliance requirements tend to arrive with deadlines and to widen in scope over time, and a team that already captures the underlying lane data absorbs each new requirement as a configuration change rather than a project. A team that captures nothing meets each regime as a fresh scramble through old invoices. The difference is not effort at the point of reporting — it is whether the effort was quietly banked at the award, months earlier, when the data was in front of you and cheap to record. Preparation here is not enthusiasm for regulation; it is refusing to pay for the same data four separate times.
Compliance framed this way stops being a tax on the tender and becomes another thing the tender produces. You were going to record the lane anyway. Record it once, completely, and let four regimes read from it.