One QR per Shipment. eFTI-Aligned Customs Data on Every Pallet.
Per-shipment QR carrying origin, HS code, CBAM embedded emissions and an EUDR due-diligence statement. Public scan for the dock, authority-key scan for customs — same generator, two views.
Demo shipment QR generated
In the live build, this QR would resolve to a unique shipment ID. Today, it points at our demo record.
Bulk CSV upload is gated to logged-in accounts
Bulk generation processes a CSV manifest (one row per shipment) and returns a ZIP of print-ready QR labels — public pallet QR plus authority-key sleeve QR per row. Designed for daily-cutoff forwarders moving hundreds of shipments per day.
This path requires a logged-in account because each shipment row writes a persistent record to your organisation's tenant.
Sign in to access bulk generation →How It Works
Enter shipment basics
Origin and destination country, carrier and ETA at minimum. The public pallet QR exposes only these fields plus the auto-generated shipment ID and eFTI reference.
Add customs payload (optional)
Eight-digit HS code, CBAM embedded emissions in kg CO₂e, EUDR commodity flag, supplier name and geocoordinates. These ride in the authority-key view and never appear on the pallet label.
Print the pallet QR and the customs sleeve
Download both QRs in print-ready PNG or SVG. The public QR goes on the pallet label; the authority-key QR stays on the manifest sleeve travelling inside the customs documentation pouch.
Scan at every cross-border touchpoint
Carriers scan the pallet QR for handoff confirmation. Customs and CBAM auditors scan the authority QR for the full eFTI envelope. Both scans land in your scan-analytics surface.
EU Regulatory Context
eFTI (EU 2020/1056)
Member-state authorities are obliged to accept electronic Freight Transport Information from 21 August 2025 onwards. The eFTI common data set defines what an authority must accept; this QR is one of the practical surfaces for delivering it.
CBAM (EU 2023/956)
Quarterly reporting of embedded emissions for iron, steel, aluminium, cement, fertiliser, hydrogen and electricity imports since October 2023. Financial liability — surrendering CBAM certificates against imported emissions — starts January 2026.
EUDR (EU 2023/1115)
Per-shipment due-diligence statement for cattle, cocoa, coffee, palm oil, rubber, soy and timber. Geolocation polygon of production land is mandatory. Enforcement from 30 December 2025; SMEs from 30 June 2026.
Why one QR, not three
eFTI is the envelope; CBAM and EUDR are structured fields inside it. One scan resolves all three contexts — no separate portals per regulation, no separate barcodes per audit.
Frequently Asked Questions
What is a cross-border logistics tracking QR?
It is a 2D barcode generated per shipment that carries — directly or via lookup — the eFTI common-data-set fields a customs officer, carrier or auditor needs at a border or hinterland checkpoint. A public scan exposes routing data (origin, destination, carrier, ETA, eFTI reference); a separate authority-key scan exposes the sensitive customs payload (HS code, supplier identity, CBAM embedded emissions, EUDR due-diligence statement).
Which EU regulations does this support?
Three. (1) Regulation (EU) 2020/1056 on electronic Freight Transport Information (eFTI), obliging member-state authorities to accept digital freight info from August 2025. (2) The Carbon Border Adjustment Mechanism (CBAM, Regulation (EU) 2023/956) — quarterly reporting since October 2023, financial liability from January 2026 for iron, steel, aluminium, cement, fertiliser, hydrogen and electricity imports. (3) The EU Deforestation Regulation (EUDR, Regulation (EU) 2023/1115) — enforcement from December 2025 for cattle, cocoa, coffee, palm oil, rubber, soy and timber.
Why two QRs per shipment instead of one?
Commercial-sensitivity. The pallet label is visible to every dock worker, third-party carrier and competitor at any cross-dock. Putting HS code, supplier name and CBAM emissions there leaks your supplier network. The public QR exposes only safe-to-share routing data; the authority-key QR — printed on the customs sleeve travelling with the manifest paperwork — unlocks the regulated payload. Officers scan the sleeve, not the pallet.
What happens when I generate a shipment in the demo?
In this demo build, every shipment resolves to /logistics-info/DEMO-SHIP-001 regardless of input. Real shipment IDs require a logged-in account and ship in the next release — that includes bulk CSV upload, authority-key generation, and per-shipment scan analytics.
Will I need to register with EU customs to use this?
The QR generator itself imposes no registration. To lawfully import goods into the EU you must hold an EORI number and lodge declarations through national customs portals (e.g. Germany's ATLAS, France's DELTA, Italy's AIDA). The QR supplements those lodgements with a scannable surface — it does not replace them. Same principle applies to CBAM declarations (lodged quarterly via the CBAM Registry) and EUDR due-diligence statements (lodged via the EU Information System for Deforestation Regulation).
Does the QR work without a smartphone or internet?
The scan requires a smartphone camera (every Android and iOS device since 2018 has native QR support) and an internet connection to resolve the landing page. For offline customs workflows we recommend printing the shipment code and the eFTI reference in human-readable text beside the QR — the standard practice on multimodal CMR consignment notes.
Is this free?
The single-shipment generator is free with no sign-up. Bulk CSV upload, the authority-key dual-view gating, and GS1 SSCC / EORI integration are enterprise add-ons that require a logged-in account.
Compliance note. qrsansar.com is not a customs broker, freight forwarder, CBAM declarant or EUDR-registered operator. Generated QRs supplement, not replace, the lodgement obligations owed by the importer of record under eFTI, CBAM and EUDR. EORI registration, CBAM Registry access and EUDR Information System enrolment remain the operator's responsibility.
Privacy. In demo mode, no shipment data leaves your browser. When real shipment persistence ships in the next release, data is stored in your organisation's tenant only and is governed by your account's data-retention policy.