Create T1, T2, T-Docs, and T-Documents with less manual customs work
Declarium helps prepare transit procedures from operational shipment, goods, and transport data. Instead of manually collecting information from emails, PDFs, Excel files, and TMS or WMS exports, the relevant data is processed in a structured way and made usable for the transit workflow.
- Prepare T1, T2, and NCTS transit data digitally
- Return T-Docs, T-Documents, MRNs, status, and references into operations
- Less manual transfer between transport, warehouse, customs, and customer service
The operational problem: transit data is scattered
NCTS workflows rarely fail because of one missing field alone. The problem is usually that item, package, value, route, and party data sit in different places. Declarium brings this data into a controlled process, checks completeness, and makes missing or contradictory information visible before it becomes an operational risk.
- Bring shipment, package, goods, value, and route data together
- Make missing information visible early as a question
- Less coordination between dispatch, warehouse, customs teams, and freight forwarders
Create, monitor, and close transit procedures digitally
A transit procedure does not end with document creation. Operationally relevant steps include acceptance, MRN, T-Doc or T-Document, transit accompanying document, status, arrival, closure, and possible questions. Declarium returns this information in a structured way so teams know which transport is in which status.
- MRNs, status, T-Docs, T-Documents, and further documents for operations teams
- Visibility for acceptance, arrival, closure, and exception cases
- Documented questions instead of unclear email threads
Start with upload, email, or files instead of a large IT project
Companies do not have to begin with a full system integration. Declarium can receive transit workflows through email, upload, Excel, CSV, PDF, or structured files. When volume and process maturity increase, the customer system can later integrate into the Declarium API.
- Quick start with existing documents and files
- Later API integration by the customer team or integration partner
- Status, MRNs, T-Docs, T-Documents, and further documents returned to operations
For freight forwarders, hauliers, importers, exporters, and 3PLs
Declarium is a fit when transit appears regularly in operations: for freight forwarders, hauliers, industrial companies, traders, fulfillment providers, and 3PLs. The relevant question is not only the customs procedure, but how quickly teams can turn transport data into a reliable transit case.
- Freight forwarders and hauliers with recurring transit movements
- Industrial and trading companies with warehouse or border workflows
- Fulfillment, warehouse, and 3PL setups
Classify T1 or T2 correctly
NCTS is the digital system for transit procedures. T1 is typically used for non-Union goods, while T2 is used when Union status needs to be proven during a movement. Declarium does not stop at terminology; it supports the operational workflow: receive data, prepare the process, and return documents and status.
- T1 for non-Union goods in transit
- T2 for Union goods when customs status needs to be proven
- Operational execution instead of procedure definitions only
NCTS Phase 5 and rising data requirements
With rising data requirements, it is not enough to copy transit data into a form at the end of the process. Declarium supports an upstream data workflow that makes completeness, plausibility, and questions visible before transport and customs teams are under time pressure.
- Structured transit data instead of manual follow-up work
- Plausibility checks before further processing
- Clear questions for missing or contradictory data
Do not lose exceptions in daily operations
Transit workflows become critical when a declaration is not accepted, data is missing, a status is unclear, or a procedure is not closed properly. Declarium supports clear question and exception workflows so these cases do not disappear in inboxes or individual transport files.
- Questions for missing transit data
- Visibility for errors, status, and closure
- Documented clarification of exception cases
When Declarium is a fit
Declarium fits especially well when T1, T2, or NCTS transit is not an occasional special task but a recurring part of logistics, warehousing, import, export, or fulfillment. The greatest value appears where data is scattered, status is missing, and manual coordination slows the process down.
- Recurring T1, T2, or NCTS transit workflows
- Several data sources, countries, locations, or operations teams
- Need for MRN, status, T-Document, and archive visibility
