Setting Up eCMR Document Generation in Your TMS

Spain's Dirección General de Transporte Terrestre isn't waiting for the rest of the EU to catch up. From 5 October 2026, the electronic Documento de Control Administrativo becomes mandatory for all road transport in and through Spain, and any shipper running lanes through the peninsula needs a working eCMR setup in the TMS well before that date, not the week before. This walkthrough covers the actual TMS integration and eCMR configuration, from certified platform credentials to the driver-side signature capture, plus what breaks when a field is missing and how you fix it.

What eCMR Actually Replaces, and Why This Is a Shipper Problem Now

An eCMR is the digital version of the CMR consignment note, the document that has recorded the transport contract between shipper, carrier and consignee since the 1956 convention. eFTI is something else entirely. Per the Open Logistics Foundation, the eCMR is a document for road freight transport, whereas the eFTI Regulation covers all modes of transport. eFTI is the plumbing that lets national authorities accept whatever digital freight data you're already generating, road, rail, air or sea. Spain's DCA rule sits in between the two. New guidance from the Open Logistics Foundation confirms other transport documents, such as eCMR, may be used as a DeCA, provided they contain all legally required information according to Art. 6 FOM/2861/2012, and separately, no separate DeCA is required where transport information is provided through the eFTI framework under Regulation (EU) 2020/1056. In plain terms: a correctly configured eCMR, wired into a certified eFTI platform, clears both the Spanish deadline and gets you ahead of the EU-wide one. That EU deadline isn't abstract either. From 09 July 2027, authorities in EU Member States must accept freight information electronically when a business provides it through a certified eFTI platform. If your TMS still spits out a PDF that someone prints and hands to a driver, you're building technical debt against a hard date.

Before You Touch the TMS: Your Prerequisites Checklist

Don't open the admin panel until you have these lined up. Missing any one of them turns a two-week rollout into a two-month one.

• An account with a certified eFTI/eCMR service provider (TransFollow, Fretlink, or a native module from your TMS vendor) with production and sandbox API credentials.
• Confirmation of the document format your destination country's inspectors actually accept. For Spain specifically, the document must be in PDF/A format and accessible online, and if you're using the QR-code verification method, you need a domain registered in advance with the authorities, not just a QR code slapped on the PDF.
• A decision on signature capture method per lane. TransFollow's mobile capture, for example, supports touchscreen signature with photo, geolocation, and timestamp, plus advanced signature via OTP or QR for maximum authenticity. Pick the level that matches your risk on that corridor, not a blanket default.
• Master data cleaned up: consignor/consignee addresses, goods descriptions, ADR flags for dangerous goods, and a driver mobile app rollout list with device IDs.
• Confirmation your provider is UN/CEFACT-aligned. Most certified platforms, TransFollow included, are compliant with UN/CEFACT standards and ready for eFTI regulations, which matters because your field mapping in step 2 below depends on it.

Connecting Your TMS to a Certified eCMR/eFTI Platform

Sinari's implementation team frames this correctly: integrating eCMR into your TMS is a simple four-step process, starting with mapping existing flows. Here's that logic expanded into the seven steps you'll actually run through as a shipper-side admin.

1. Map existing flows first. Before touching any config screen, document where consignment notes are created today and by whom. Sinari's own methodology starts by asking where and by whom consignment notes are created and completed, what data is involved, and to whom they are transmitted. Do this on paper before you do it in the TMS.
2. Register the provider connection in your TMS admin panel. Generate API keys from your eFTI provider (TransFollow or equivalent) and register the endpoint in the TMS's integration or document module. Keep sandbox and production keys in separate config profiles.
3. Configure the data exchange and field mapping. This is the stage where you define data format and field mapping between your TMS shipment record and the provider's schema. The aim of this stage is to configure data transmission within the eCMR solution and guarantee the smooth flow of information. Map consignor/consignee blocks, transport dates, goods description, weight, and the dangerous-goods indicator explicitly, don't rely on default field auto-matching.
4. Set the document trigger. Decide whether the eCMR draft generates on tender acceptance or on dispatch confirmation. Most shippers pick dispatch, since that's when the goods description and load details are final.
5. Configure driver-side signature capture. Push the eFTI provider's mobile app or QR/OTP flow to the driver device list from your prerequisites step. Set the signature level (advanced vs. basic) per lane risk, higher-risk cross-border lanes get advanced.
6. Run a controlled test phase. Sinari calls this a test phase carried out within a controlled perimeter, with a few partners and volunteer employees, which enables you to identify areas for improvement before scaling up. Run three to five real shipments end-to-end, not dummy data.
7. Flip on production for one pilot lane, then scale. Roll the project out on a larger scale and measure results, for example by tracking letter entry times or dispute rates, before adding more carriers or lanes.

How You Know the Integration Actually Worked

You'll know quickly, not weeks later. The signed eCMR should land in your TMS document history within minutes of delivery confirmation, with no manual upload. The shipment status should flip to "delivered" via the webhook callback without a dispatcher touching the record. If you're still exporting a PDF and emailing it, the callback loop isn't configured, go back to step 3. Spot-check a handful of signed documents against your provider's public verification portal to confirm the signature and timestamp match what the driver captured on the road. TMS-integrated eCMR also pays for itself faster than most teams expect: the European Commission's own figures, cited by Sinari, put the savings at up to €6.21 per consignment note, for a total estimated saving of €2.3 billion across the transport sector. If your admin history isn't showing signed documents flowing in automatically, you're not capturing any of that.

The Failure Mode: Held at the Border With an Incomplete eCMR

This is the one that gets a truck parked at a border checkpoint. Under ICS2's Entry Summary Declaration rules, which run in parallel to your eCMR/eFTI setup, if the data is incomplete or suspicious, customs authorities can issue a "Do Not Load" notification, which for road transport effectively translates to a "Do Not Proceed" order. And the practical consequence is blunt: a truck that arrives at the border without a successfully processed ENS will be held, resulting in significant delays, potential fines, and a cascading failure of the delivery schedule. For eCMR specifically, three things cause this: the dangerous-goods flag wasn't set at tender creation, the driver's app was offline at pickup so the signature never captured a geolocation stamp, or the signature level configured for that lane doesn't meet the destination country's inspection rules. Build a pre-transit validation rule into your TMS that blocks dispatch if any required eFTI field is null, and keep a documented fallback paper-CMR procedure for lanes you haven't cut over yet. Don't rely on the driver to notice a blank field on a phone screen at 5am.

Rollout Notes for Multi-Country Fleets

Don't flip an EU-wide switch. Country readiness is a patchwork right now. Even within the ICS2 timeline that runs alongside eFTI, ICS2 version 3 became mandatory across all transport modes on the 3rd of February 2026, but a handful of states negotiated more runway, with an operator readiness assessment for the June 2026 road deadline in Croatia, Latvia, Poland, Romania, and Slovakia. Build a per-country toggle in your TMS config, not a single global flag, and brief dispatch and drivers explicitly on which lanes are eCMR-only versus still paper-backed. A driver who doesn't know the rule changed on a specific corridor is your next incident report.

Where Cargoson and Peer Platforms Fit

Most shippers aren't building eCMR from scratch, they're connecting an existing TMS or multi-carrier platform to a certified provider. Here's how the landscape breaks down for evaluation purposes.

Where a specific eCMR feature isn't publicly documented, treat that as a question for your account team, not an assumption in either direction.

Next Steps

Pick one lane into Spain, or one high-volume EU corridor, and run the seven-step sequence above as a pilot before October. Get your provider credentials and field mapping done this month, run the sandbox test next month, and hold the production flip for a single carrier relationship you trust to flag issues fast. The 2027 EU-wide deadline gives you runway, the Spanish DCA deadline doesn't. Treat this as the forcing function it is.