Trade War

Romania's freight code requires traders and hauliers to divide responsibility

Romania's RO e-Transport rules separate declaring a shipment from carrying it. Importers and EU buyers need to identify the responsible trader, while hauliers continue to dispute technical obstacles.

The law 18 November 2026

For companies sending goods into Romania, hiring a haulier does not automatically transfer responsibility for declaring the shipment in RO e-Transport. Logistics operator Gopet's explanation of 6 March 2026 distinguishes the trader's declaration from the carrier's duties to supply vehicle-position data and give the driver the shipment's UIT identification code.2

The declaration follows the transaction

Gopet identifies the import-declaration consignee for imports, the Romanian buyer for intra-EU acquisitions and the Romanian supplier for intra-EU deliveries among the responsible parties. Warehouse operators also have duties in specified storage and regrouping operations. The relevant role must be established before dispatch, rather than inferred from which business pays the freight invoice.2

The official procedure approved on 17 June 2024 explains why international traders cannot look only at lists of high-risk products. It covers the defined international road-goods operations regardless of the goods' nature, alongside the domestic high-fiscal-risk regime. The Romanian text says:1

indiferent de natura acestora

regardless of their nature1

The vehicle and consignment thresholds still matter. The order covers vehicles with a maximum technically permissible mass of at least 2.5 tonnes carrying a relevant consignment exceeding either 500 kilograms gross weight or 10,000 Romanian lei in value. The alternative thresholds should not be confused with a requirement to exceed both. The procedure excludes VAT when determining value and counts necessary packaging in gross weight.1

ANAF's published questions and answers illustrate the allocation of responsibility through older, specifically high-risk-goods examples. Where a Romanian buyer purchases from another EU state on delivered-duty-paid terms, the Romanian beneficiary declares even though the seller arranges transport. In the corresponding ex-works outbound example, the Romanian supplier remains the declarant. These examples explain responsibility; their older high-risk framing is not the complete scope of today's international regime.3

Ports, warehouses and data must match the journey

UNTRR’s transit explanation distinguishes a through-journey from an import cleared for Romanian delivery. In the latter case, it says monitoring starts after clearance for the journey to the unloading point. Pure transit without unloading or clearance in Romania is different. The route and customs treatment therefore matter alongside the identity of the commercial parties.5

In consolidated loads, the official procedure requires codes corresponding to the qualifying consignments. One truck is not necessarily represented by one code. That distinction affects how traders and carriers reconcile the vehicle's documentation before departure.1

Transporters say implementation remains troublesome. In its submission published on 21 July 2026, UNTRR reported connection failures, delayed recognition of codes and difficulties using foreign mobile-data services. It also described unresolved vehicle-storage scenarios where cars can leave a Romanian warehouse under a different transaction from the one initially reported. Those are the association's complaints, not findings that the declaration duties have disappeared.4

UNTRR requested a government-business working group to refine procedures and either effective positioning applications or reconsideration of the positioning requirements. The unresolved question is whether authorities will publish workable procedures and technical fixes for those cases, allowing the reported movement to match the commercial transaction without repeated manual intervention.4

Sources

  1. ANAF and Romanian Customs Authority. Ordin nr. 1.337/1.268/2024 [Order 1,337/1,268/2024]. 17 June 2024Romania's camp · legislation · in Romanian
  2. Gopet Romania. RO e-Transport 2026: obligații, cod UIT și ce trebuie să știe companiile [RO e-Transport 2026: obligations, UIT code and what companies need to know]. 6 March 2026Industry camp · logistics company · in Romanian
  3. ANAF. Întrebări și Răspunsuri RO e-Transport [RO e-Transport questions and answers]. Accessed 18 November 2026Romania's camp · government · in Romanian
  4. UNTRR. UNTRR a sesizat M. Finanțelor privind problemele RO e-Transport [UNTRR notified the Finance Ministry about RO e-Transport problems]. 21 July 2026Industry camp · trade association · in Romanian
  5. UNTRR. RO e-Transport se aplica la tranzit? [Does RO e-Transport apply to transit?]. 4 April 2025Industry camp · trade association · in Romanian

All articles