Retrieve export data by MRN and transfer every item into NCTS

For export followed by transit, Declarium receives the export MRN and retrieves the export data made available through the intended ATLAS workflow. House consignments and goods items are transferred in a structured way into the preparation of the transit declaration. This creates a reliable NCTS dataset without operations teams having to enter every export item again.

• Retrieve export data using the MRN
• Transfer available export data at item level
• Prepare a complete NCTS transit declaration

The interface between ATLAS Export and ATLAS Transit turns a comparison that was often performed manually into a system check. ATLAS compares the commodity code, goods quantity or net mass, and country of destination. It also checks the transit declaration type, customs status, procedure code, export status, and correct export references.

• Compare commodity code, net mass, and destination country
• Check transit type, customs status, and procedure code
• Confirm that the export status permits onward movement under transit

Some workflows compress several export items into one transit item, for example by using the first item's commodity code and the total weight or value of the entire shipment. That model does not reproduce the referenced export declaration one to one. Under the automated comparison, missing items, different commodity codes, or an inconsistent net mass can therefore prevent acceptance or release.

• Do not compress several export items into one aggregate item
• Map every NCTS item to the correct export item
• Handle item order and references in a controlled way

The workflow starts with the export MRN. Through the intended process, the export consignment is presented for onward movement under transit and ATLAS provides the exit data. Declarium processes the response, creates the matching house consignments and goods items, adds the required previous-document references, and makes the resulting dataset reviewable before further processing.

• Receive the export MRN and workflow context digitally
• Process export data from the ATLAS response
• Prepare house consignments, goods items, and previous-document references

The export declaration already contains core goods data needed again for the subsequent transit procedure. Declarium uses this existing data source and transfers the relevant items into the NCTS workflow in a controlled way. Operations teams no longer need to copy commodity codes, weights, destination countries, and item numbers from documents or emails.

• Less manual copying from export documents, PDFs, or customs software
• Lower risk of typing errors and swapped items
• One consistent data basis for export and transit

For export followed by transit, the export declaration is referenced as previous document N830. In NCTS Phase 5, one house consignment generally corresponds to one previous export declaration and must contain its goods items completely. If the item order differs, the original export item number needs to be mapped explicitly. Declarium prepares this structure transparently in the data workflow.

• Reference the export MRN on the correct house consignment
• Map goods items one to one to the export declaration
• Represent different item orders unambiguously

The solution is particularly relevant when an exporter or customs agent prepares the export declaration, while the subsequent transit procedure is handled by a freight forwarder, authorised consignor, warehouse, or 3PL. This handover is exactly where broken data flows, missing item details, and time-critical questions often occur.

• Freight forwarders and carriers handling export followed by transit
• Authorised consignors and warehouses with NCTS workflows
• Exporters, shippers, and 3PLs with shared responsibilities

Companies can begin with a controlled MRN handover and managed workflow. For recurring volumes, export data retrieval can later be integrated into TMS, WMS, ERP, or other operating systems. Status, questions, MRNs, and documents remain visible in a structured process.

• Controlled start with existing MRN and shipment data
• Later REST API integration for recurring volumes
• Return status, errors, and documents to operational systems

Even with automated data transfer, professional exceptions can occur, such as an export status that does not permit transit, an incompatible transit type, or an actual shipment that changed after export acceptance. Declarium makes questions and errors visible so they can be resolved before departure or release instead of stopping the movement at customs.

• Plausibility checks before further processing
• Clear questions for status and procedure conflicts
• Traceable exception handling instead of unresolved email threads