Required from 5 October 2026 | A site running in under a week
DeCA2U issues the document for every consignment and has it stored before the vehicle leaves. An inspector opens it by scanning the code on the slip, without having to ask anyone for anything. Neither your systems nor your delivery note 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.
A site goes live scanning its own delivery note: no integration, and nothing of yours changes.
https://doc.deca2u.com/yQRjIVKxGsA4SqJoZDn_hw/8h86UiouAH2eZwOrS4di1Q.pdf
Article 6
This is the content of the document, and it is not yours to choose. A point is not always one value: c) and d) ask for two each.
What the DeCA is and what it has to meet: the eight points with the text of article 6, and what the rules require of the file.
How the consignment comes in
Not stages or tiers: alternatives, and one site can use all five on the same day. Whichever way it comes in, the document is the same and so is the record.
The operator scans the note you already print. Whatever is read is shown for confirmation, so no value reaches the document without somebody validating it. It is the quickest way to start: a site is running in under a week, which is how long we take to study your notes so the reading is as reliable as it can be.
Your system emails the note to an address of your own and the document issues itself. If the note carries a code and the rest matches your own data, it goes out with nobody touching it. If not, it waits in the tray with the attachment and the reason it stopped. Nothing to install: every system knows how to send a PDF.
For when there is no delivery note to scan, or the one there is will not do. Few fields per screen and large buttons, because it is filled in standing up, outdoors and often with gloves on.
Your system sends the consignment and gets the document back. It is the same route our own capture app uses, so it is available from day one.
The driver issues their own DeCA from their phone, at the sites you enable and for the hauliers they drive for. They activate it once from WhatsApp, with no username or password, and from then on they see the day's loads.
What shows up day to day
The site works offline: it prints the slip and the vehicle leaves. The moment the line comes back, everything is on record on its own. No consignment waits for the network.
Every day, every site: how many documents left, how long they took to publish and which were published late. A plant that stopped issuing shows up in the report before it shows up in an inspection.
Each haulier receives an invitation by email and can consult its documents for the twelve months they are kept. It is not added to the company's directory and needs no new account: it signs in with the identity it already uses or with a one-time code.
The platform includes six predefined roles and lets you create others. Each role determines what information is available and at which sites. Each haulier can access only its own loads.
The DeCA's QR the driver carries opens exactly the document a scan returns: the same file. The platform compares both fingerprints every time it issues.
When it issues, the DeCA's QR goes to the driver the note names. If you have no contact for them, it goes to the haulier.
The driver can ask for the DeCA over WhatsApp and it comes back in the same conversation. The channel never issues: it only returns what is already published.
One sign-in form, and your address decides which directory authenticates you: your people use what they always have. A haulier comes in as a guest, never enters your directory and needs none of its own.
The platform decides by what changes. A plate or the observations are corrected on the same document, and the QR the driver carries still opens it. The destination, the load or the day make it a different transport: a new DeCA is issued with its own QR, and the old one stays linked to it.
They scan the code and the document opens. No account, no password, no landing page. That is what the Resolution requires.
Scan the one you already print and nothing changes: you start without touching your systems. Or integrate, and we hand back the document's address so you can print its QR on your own note: one piece of paper instead of two.
A consignment can come in twice through two different channels, and that does not create two documents. If a code was handed over, the driver has it: it has to keep opening the same document.
Wired into your system, the document is issued with the consignment rather than as a separate step somebody has to remember. Keep the rules out of your operation: you comply without spending a second on it.
The two clocks
Two deadlines hang off the transport date. The twelve months bind: keeping the file longer is just as much a breach, and nobody comes to tell you. The seven days the rules permit rather than require, and we apply them.
Created and kept before the vehicle leaves, with its issue time. Issuing it afterwards is issuing it late, however well the date reads.
The Resolution allows closing it seven days after the service. It closes on its own, on the exact date, without anyone having to remember.
GDPR art. 5.1(e). It is destroyed on its own, at exactly twelve months. Keeping it too long breaches the rules as surely as losing it early.
First of all
It covers interior carriage of goods for hire and reward, with origin and destination in Spain, and cabotage. International transport crossing Spain is outside it and travels on convention documents.
That is carriage for hire and reward, and it is always inside. Every consignment leaves with its document.
Own-account carriage is outside only while all five conditions of art. 102.2 LOTT hold. Fail one and art. 102.3 puts it back under the public regime.
This is the one of the five that fails most often. The cost of the transport has to sit inside the product price; charging for it on its own puts you inside.
Who the DeCA binds: the five conditions of article 102.2 one by one, the four excepted transports, and who answers for what.
Pricing
An annual subscription by band of documents a year. Inside the band the fee is flat: go over the band and you keep issuing with no interruption.
Tell us how many consignments you run a year and we will tell you the band.
Nothing to multiply and nothing to watch at month end. The band is agreed once and the fee holds for the whole of it.
Every feature is in every band: none of them unlocks by paying more. What grows is the volume and the integrations. Go over it in a month and it is measured and reported, never refused: a commercial limit is not a reason to stop a consignment.
Tuning the reader to your own delivery notes is charged once, at the start, and never appears on an invoice again.
Before you sign
Four answers worth having in writing before you sign anything. Your advisers ask for the first and your legal department for the last; the other two are asked by whoever has to get the lorries out on the day something goes wrong.
On Microsoft Azure, in a European region, under a single provider. Each customer has its own partition and its own branding, and no data leaves the platform for a third party.
Public download is a separate service, with its own domain, its own rate limit and its own lifecycle. A mass inspection lands on it, and the application the operator issues from never notices.
A site holds the identifiers it is going to use before it needs them, so it composes the document and prints it without asking us anything. What was issued with no line uploads on its own when the line returns.
Record of processing, impact assessment, where the data sits and what happens after a breach. The data processing agreement is drafted and ready for your legal team to review.
Let us talk
We do not sell you a login and leave: we work with you until every consignment leaves with its document, site by site.
With those we place you in a band, give you a quote, and tell you whether scanning suits you, an API fits better, or we tune the reader to your own delivery note.
For your engineers
Four things an engineering team decides in five minutes, and one example call. The rest is in the reference.
No SDK to install and no format of our own to learn. If your system can make an HTTP call, it already knows how to talk to us.
Your system presents a header key. People sign in with an account from your own directory.
No route takes the tenant as a parameter, so a key cannot reach another customer's data.
Issuing returns the identifier, the public address and the hash of the published file.
curl -X POST https://api.deca2u.com/v1/documents \
-H "x-api-key: $DECA2U_KEY" \
-H "Content-Type: application/json" \
-d '{
"siteId": "V204",
"externalRef": "V204-40712",
"data": {
"contractualShipper": {
"name": "Conservas Bahía Norte, S.L.",
"taxId": "B36742180",
"address": "Rúa do Porto 22, 36202 Vigo"
},
"effectiveCarrier": { "name": "Transportes Vega Hermanos, S.L.", "taxId": "B99001122" },
"location": { "origin": "Centro logístico de Vigo", "destination": "Plataforma de Getafe" },
"goods": [{ "description": "Conserva vegetal en lata", "quantity": 12400, "unit": "kg" }],
"transportDate": "2026-07-15",
"vehicle": { "tractorPlate": "1234ABC", "articulated": false }
}
}'
const response = await fetch('https://api.deca2u.com/v1/documents', {
method: 'POST',
headers: {
'x-api-key': process.env.DECA2U_KEY,
'Content-Type': 'application/json',
},
body: JSON.stringify({
siteId: 'V204',
externalRef: 'V204-40712',
data: {
contractualShipper: {
name: 'Conservas Bahía Norte, S.L.',
taxId: 'B36742180',
address: 'Rúa do Porto 22, 36202 Vigo',
},
effectiveCarrier: { name: 'Transportes Vega Hermanos, S.L.', taxId: 'B99001122' },
location: { origin: 'Centro logístico de Vigo', destination: 'Plataforma de Getafe' },
goods: [{ description: 'Conserva vegetal en lata', quantity: 12400, unit: 'kg' }],
transportDate: '2026-07-15',
vehicle: { tractorPlate: '1234ABC', articulated: false },
},
}),
});
if (!response.ok) throw new Error(`DeCA2U answered ${response.status}`);
const { id, url } = await response.json();
import os
import requests
response = requests.post(
"https://api.deca2u.com/v1/documents",
headers={"x-api-key": os.environ["DECA2U_KEY"]},
json={
"siteId": "V204",
"externalRef": "V204-40712",
"data": {
"contractualShipper": {
"name": "Conservas Bahía Norte, S.L.",
"taxId": "B36742180",
"address": "Rúa do Porto 22, 36202 Vigo",
},
"effectiveCarrier": {"name": "Transportes Vega Hermanos, S.L.", "taxId": "B99001122"},
"location": {"origin": "Centro logístico de Vigo", "destination": "Plataforma de Getafe"},
"goods": [{"description": "Conserva vegetal en lata", "quantity": 12400, "unit": "kg"}],
"transportDate": "2026-07-15",
"vehicle": {"tractorPlate": "1234ABC", "articulated": False},
},
},
timeout=10,
)
response.raise_for_status()
issued = response.json()
using System.Net.Http.Json;
var http = new HttpClient { BaseAddress = new Uri("https://api.deca2u.com/") };
http.DefaultRequestHeaders.Add("x-api-key", Environment.GetEnvironmentVariable("DECA2U_KEY"));
var response = await http.PostAsJsonAsync("v1/documents", new
{
siteId = "V204",
externalRef = "V204-40712",
data = new
{
contractualShipper = new
{
name = "Conservas Bahía Norte, S.L.",
taxId = "B36742180",
address = "Rúa do Porto 22, 36202 Vigo",
},
effectiveCarrier = new { name = "Transportes Vega Hermanos, S.L.", taxId = "B99001122" },
location = new { origin = "Centro logístico de Vigo", destination = "Plataforma de Getafe" },
goods = new[] { new { description = "Conserva vegetal en lata", quantity = 12400, unit = "kg" } },
transportDate = "2026-07-15",
vehicle = new { tractorPlate = "1234ABC", articulated = false },
},
});
response.EnsureSuccessStatusCode();
var issued = await response.Content.ReadFromJsonAsync<Issued>();
var body = """
{
"siteId": "V204",
"externalRef": "V204-40712",
"data": {
"contractualShipper": {
"name": "Conservas Bahía Norte, S.L.",
"taxId": "B36742180",
"address": "Rúa do Porto 22, 36202 Vigo"
},
"effectiveCarrier": { "name": "Transportes Vega Hermanos, S.L.", "taxId": "B99001122" },
"location": { "origin": "Centro logístico de Vigo", "destination": "Plataforma de Getafe" },
"goods": [{ "description": "Conserva vegetal en lata", "quantity": 12400, "unit": "kg" }],
"transportDate": "2026-07-15",
"vehicle": { "tractorPlate": "1234ABC", "articulated": false }
}
}
""";
var request = HttpRequest.newBuilder(URI.create("https://api.deca2u.com/v1/documents"))
.header("x-api-key", System.getenv("DECA2U_KEY"))
.header("Content-Type", "application/json")
.POST(HttpRequest.BodyPublishers.ofString(body))
.build();
var response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
<?php
$payload = [
'siteId' => 'V204',
'externalRef' => 'V204-40712',
'data' => [
'contractualShipper' => [
'name' => 'Conservas Bahía Norte, S.L.',
'taxId' => 'B36742180',
'address' => 'Rúa do Porto 22, 36202 Vigo',
],
'effectiveCarrier' => ['name' => 'Transportes Vega Hermanos, S.L.', 'taxId' => 'B99001122'],
'location' => ['origin' => 'Centro logístico de Vigo', 'destination' => 'Plataforma de Getafe'],
'goods' => ['description' => 'Conserva vegetal en lata', 'quantity' => 12400, 'unit' => 'kg'],
'transportDate' => '2026-07-15',
'vehicle' => ['tractorPlate' => '1234ABC', 'articulated' => false],
],
];
$curl = curl_init('https://api.deca2u.com/v1/documents');
curl_setopt_array($curl, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: ' . getenv('DECA2U_KEY'), 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode($payload, JSON_UNESCAPED_UNICODE),
]);
$issued = json_decode(curl_exec($curl), true);
201 response:
{
"id": "8h86UiouAH2eZwOrS4di1Q",
"url": "https://doc.deca2u.com/yQRjIVKxGsA4SqJoZDn_hw/8h86UiouAH2eZwOrS4di1Q.pdf",
"publishedAt": "2026-07-15T06:31:02.144Z",
"publicUntil": "2026-07-22T23:59:59.000Z",
"pdfHash": "9f2c…",
"qr": "<svg xmlns=…>", // solo con ?qr=1
"externalRef": "V204-40712"
}