Coming into force
5 OCT 2026
Today5 days to go
The day it comes into force.
Required from 5 October 2026
Meet 5 October without changing how you work.
DeCA2U issues the control document for every consignment and has it stored before the vehicle leaves. It does so by reading the delivery note you already have, printed or received by email: neither your systems nor your paperwork change.
5 October 2026 No transition period, and no phase without sanction. Ley 9/2025, T.P. 8. Resolution of 5 June 2026, BOE-A-2026-12784.
This is what an officer opens They scan the code and the PDF downloads. No account and no password.
Fields
8 required
6 always2 where they apply
Two of them only where they apply.
Access
12 months
M1M6M12
Of access for the haulier.
Impact
0 changes
Delivery noteSystemsOperation
Your delivery note and your systems, as they are.
The obligation
The 4 main obligations
There is no grace period for a technical failure, no approved provider and no Ministry tool: every company needs its own application or a provider.
Native PDF
Generated from structured data. A scanned or photographed document is expressly invalid.
Resolution of 5 June 2026
Before the service
Created and stored before the transport begins, with the issue time recorded.
Resolution of 5 June 2026
One code per document
Every file has its own address, and the QR code travelling with the driver leads to it.
Resolution, section Tercero
Download with no credentials
Over TLS, straight to the file. If anyone shows a sign-in screen before the PDF, that address does not comply.
Resolution, section Tercero.2
How it works
Your delivery note already carries almost everything
We read it from there and fill in what is missing. Not one field of your paperwork changes, and not one line of your systems.
1
2
1
The code you already print
It carries six of the eight fields: shipper, consignment, date, goods and destination. A code either reads correctly or not at all, never wrongly.
2
The blocks the note prints
Sender, transport details, delivery place and goods are read off the paper in the same capture. That is where what no code carries comes from: the carrier and the plates, which exist in no system until the lorry reaches the weighbridge.
The operator confirms what was read, and the document is issued and published.
The platform
Issue, hand it to the driver and keep watch, without typing anything twice
Five ways to issue, the driver gets the document over WhatsApp or by email when it is issued and asks for it over WhatsApp whenever they need it, and the view of every site for whoever answers for it.
Five ways to issue
5 channelsScanning the noteOne photograph, or the PDF you already have: the code and the transport block are read off your own note.
Assisted formFor the port, the weighbridge and every load with no printed note.
Ingestion APIThe one our own application consumes. One key per system, revocable.
Email channelEvery site has its own address: forward the note to it and the document comes out of there.
Driver appThe driver issues their DeCA from their phone, at the sites you enable.
5 ways to share the DeCA
5 waysOver WhatsApp, when it is issued and when the driver asks for it
- When it is issued it reaches their WhatsApp on its own
- If they need it again, they ask with a message, a voice note or a photo of the note
- They get their QR code and the link to the PDF straight away
- You know whether it arrived and whether they read it
- No new application and no passwords
And four more ways
- Printed slipIt complies on its own, with no coverage either.
- Code on screenThe driver photographs it and takes it with them.
- EmailTo their mailbox or their company's.
- Link or shareFrom the operator's phone, to any app.
With no coverage, the lorry still leaves
Offline- Every site carries identifiers reserved in advance.
- It issues and prints with no line, with its master data on the device.
- What was issued uploads itself when the connection returns.
- The driver leaves with the printed slip, which complies with no coverage.
The eight fields of article 6
Minimum dataa)Contractual shipper
b)Effective carrier
c)Origin and destination
d)Goods and weight
e)Special authorisationOnly if the vehicle carries one
f)Date of transport
g)Plates
h)ObservationsOnly if a party asks for them
Not one datum more
Public- Only the eight fields: no prices, no customers, no driver.
- An opaque 128-bit address, unrelated to the delivery note.
- It closes after 7 days and is destroyed after 12 months.
Operational health metrics
Oversight- Which site has gone days without issuing, today and not at month end.
- How many times each document has been opened.
- An exportable audit trail, and their own access for your carriers.
Your documents, always available
ContinuityEvery 4 hA copy of all your documents, kept apart and replicated to another region.
30 daysA continuous copy of the database: we restore it as it was at any second of the last month.
3 data centresEvery document is stored in three at once, within the same region. If one fails, the others keep serving it.
Every monthPlatform health reports, both for issuing documents and for looking them up.
Retention
The platform applies both deadlines
Nobody has to remember to close a link or to delete a file.
Before the service
The document is created and stored before the lorry sets off.
During the service
The link has to answer: it cannot expire before the service ends.
Resolution, Tercero.2After 7 days
Public access may be switched off. The platform closes it on its own.
Resolution, Tercero.5After 12 months
The file is destroyed. Until that day the haulier can download it.
Resolution, Segundo.4The difference
From the delivery note to the DeCA without typing anything
DeCA2U reads the delivery note you already have, issues the document with nobody typing, and keeps it up to date. This is how the routine of every site changes.
Issuing a document
Without DeCA2USomebody types eight fields, a minute and a half per consignment, standing up and wearing gloves.
With DeCA2UOne photograph of the note and one confirmation on screen. The operator types nothing.
A site with no line
Without DeCA2UThe lorry waits for coverage to come back, or leaves with no document.
With DeCA2UIt issues and prints all the same, and what was issued publishes itself when the line returns.
A detail changes
Without DeCA2UThe paper the driver took this morning stops being valid.
With DeCA2UThe platform decides whether the same QR is enough, opening the corrected document, or a new DeCA with its own QR is needed.
Let us start with one site
It goes live scanning its own delivery note, with no integration and nothing of yours touched. We do the setup: sites and users, carriers and vehicles loaded, the reading tuned to your note templates, and the operators trained.
Issue. Comply. Forget.
The delivery note and the document shown on this page are the platform's own demonstration samples: they belong to no customer.