RO e-Transport: How to obtain the UIT code in <30 seconds directly from WMS, without manual entry
The RO e-Transport system mandates the declaration of shipments before departure. Learn how WMS + SPV API integration completely eliminates manual data entry and penalty risks.
Cosmin Boruz — EDI Specialist & Helpdesk Lead · 2026-05-22 · 8 min · Logistics
RO e-Transport — the declaration that allows no delays
The RO e-Transport system requires any company operating in Romania to declare in advance, via the SPV (the Romanian tax authority portal), shipments of high-fiscal risk goods: >500kg or >10,000 RON per consignment, goods listed in Annex 1 GEO 41/2022 (vegetables, fruits, beverages, clothing, construction materials, metals), and all intra-community deliveries regardless of weight or value.
The declaration must be made before the vehicle departs. The operator receives a UIT code (Unique Transport Registration Code) which must accompany the goods during transit and be presented at any road inspection. Failure to declare results in fines between 5,000-100,000 RON and the confiscation of the value of the goods.
The typical manual workflow and why it fails
Most distribution and retail companies process e-Transport as follows:
1. The logistics operator marks the shipment in the WMS (Excel or local software).
2. A colleague opens the SPV portal and manually enters transport data (sender Tax ID, recipient, goods, CN code, vehicle, driver, departure time).
3. They wait for the UIT (1-5 minutes, sometimes experiencing timeouts).
4. They print the UIT and manually attach it to the delivery note.
5. They hand it over to the driver.
The problems:
15-45 minute lag between delivery preparation and actual departure.
Transcription errors: wrong CN code, quantities differing from the delivery note, last-minute vehicle updates.
Retries due to ANAF (the Romanian tax authority) rejection (inactive recipient Tax ID, invalid CN code).
FTE Cost: 0.5-1 employee dedicated solely to e-Transport in a company with >50 deliveries/day.
Penalty risk if the driver leaves without a validated UIT.
The automated workflow with Azuvio WMS + SPV API
The Azuvio WMS manages e-Transport directly at the source, synchronized with picking confirmation:
1. The operator confirms picking on a mobile terminal (scanning the pallet SSCC).
2. Azuvio automatically aggregates: sender Tax ID, recipient Tax ID (from the B2B order), goods + quantities + CN code (from PIM), vehicle + driver (from logistics planning), and estimated departure time.
3. The e-Transport XML is generated locally, with syntax validation.
4. It is sent via OAuth2 SPV API to ANAF (with automatic retries for rate-limiting).
5. UIT received in <30 seconds, saved to the shipment record + automatically printed on the delivery note.
6. The driver receives the delivery note with the integrated UIT — no extra manual steps required.
Real-time error management
When ANAF rejects a message (inactive recipient Tax ID, invalid CN code, inconsistent route), Azuvio:
Holds the shipment in a "manual review" queue (does not allow goods to leave without a UIT).
Notifies the operator on the terminal with the exact error message.
Suggests the correction (e.g., recommended CN code for that specific item based on history).
Retries automatically after the correction is made.
Zero risk of departing with a rejected UIT, zero risk of being blocked during road inspections.
Delivery note + UIT — a single document
Azuvio prints the delivery note with the integrated UIT + verification QR code (linking to SPV status) + supplier digital signature. Essentially, the driver receives a single document that satisfies both statutory reporting for delivery notes and e-Transport requirements. See also the delivery note glossary.
Measurable benefits
An FMCG distributor with 80 daily deliveries to retailers switched from a manual workflow to Azuvio's automated flow. After 18 months:
e-Transport generation time per delivery: reduced from 8-15 min to <30 sec.
e-Transport penalties: 0 (vs ~5,000-8,000 RON/month previously).
Dedicated staff: reduced from 1 FTE to 0 (existing operators just confirm picking as usual).
Rejection rate: <1% (vs 8-12% manual).
Conclusion
e-Transport should not be an additional task for the logistics operator. It must be an automatic side-effect of shipment confirmation — generated at the source, validated, submitted, and attached to the delivery note. This is how modern WMS systems function. See the complete ANAF Fiscal Hub, Azuvio WMS, and the ERP coexistence doctrine.