Transit and T1 Dispatch

When you need a transit procedure

Transit procedures are required when goods are moved under customs supervision from one customs location to another without an import declaration having been submitted yet. Feronix supports you in opening, bundling the packages and generating the dispatch declaration as DETPDD XML. The goods are delivered to the Feronix warehouse, where Feronix handles customs clearance under its own EORI.

Which dispatch types Feronix supports

Dispatch type	Meaning
T1	External transit procedure (third country → EU)
T2	Internal transit procedure (within EU)
T2F	Special internal transit procedure
T	Mixed transit procedure (T1/T2)

Procedure types

Procedure	Meaning
create_new	Open a new transit
import_existing	Adopt an existing transit with MRN
onward	Onward transit with previous MRN

Processing variants

Variant	Meaning
normal	Standard procedure with presentation
authorised_consignor	Authorised consignor with corresponding authorisation

How to open a transit

1. Create transit order — open "Transit / T1" in the WMS or via API POST /warehouse/transit-orders.
2. Enter transit details — dispatch type (T1/T2/T2F/T), procedure type, customs offices, identity, security and goods location.
3. Select packages — select packages from one or more inbound deliveries that were delivered to the Feronix warehouse, in a tenant-secure manner and assign them.
4. Set house shipment key — when a HAWB or transport contract determines the grouping.
5. Generate outbound delivery — generate a new outbound delivery from exactly this selection.
6. Generate DETPDD — validate, XSD-validate and archive in the DMS.

What Feronix determines automatically

You do not have to fill in all fields manually — Feronix takes over:

• EORI and establishment of Feronix from the selected active customs identity (Feronix acts as declarant)
• Office of departure from the delivery configuration
• Holder and address from the client master data
• Total gross mass from delivery or item total
• Goods description, HS code, weights, packaging and number of packages from the linked shipments

What you must provide

• LRN — local reference of the dispatch declaration (1–22 characters)
• Office of destination — 8-digit customs office reference
• Security type — from the ATLAS code list
• For security types requiring a reference: GRN with access code and amount
• Sender BIN — if not stored in authorisation_data.bin

What Feronix checks before download

• EORI, establishment and BIN of Feronix (as declarant and representative)
• Customs offices and LRN
• Security and security reference
• Countries and weights
• Six-digit HS codes
• Packaging

Feronix then validates against the integrated official DETPDD.xsd. Business or schema errors return HTTP 422 with T1_XML_INVALID.

What you receive

• DETPDD XML (message E_DEP_DAT, root DETPDD, version D.1.23, EDI-IHB 10.2.7)
• Automatic DMS archiving of the export
• Outbound delivery from the transit package selection

Transmission to ATLAS

The transit is transmitted automatically via the ATLAS FTAM interface. Available functions include declaration, status query, release/MRN, rejection, events and the separate group for guarantees.

Additionally, the DETPDD XML file can be generated and downloaded. It is intended for manual upload to ATLAS or for transfer to a compatible ATLAS participant software. File generation does not send anything automatically to ATLAS.

Important limitation

Also available via API

POST /warehouse/transit-orders                      # Create transit order
POST /warehouse/transit-orders/{id}/packages         # Assign packages
POST /warehouse/transit-orders/{id}/outbound-shipment # Generate outbound delivery
POST /warehouse/transit-orders/{id}/xml              # Generate DETPDD
POST /warehouse/deliveries/{delivery_number}/t1-xml  # compatible: T1 XML for delivery