DEV Community: John Hall

Integrating T1 and T2 Data into Your TMS and ERP

John Hall — Tue, 22 Sep 2026 07:08:08 +0000

The three data sets that must sync

Three data sets need to stay in step across your customs, TMS and ERP stack. Shipment level customs status. Guarantee usage and remaining headroom. Proof of arrival and discharge for every transit movement.

If any one of them drifts, the audit trail falls apart.

Mapping T1 and T2 to your data model

Model the declaration type as an attribute of the consignment, not the shipment. A single trailer can carry both T1 and T2 consignments. Store the Union status evidence at the consignment level too, so the audit trail is intact if the goods are separated later. The T1 and T2 transit document guide illustrates why the consignment is the right unit.

Keep the discharge signal flowing back

The most overlooked integration point is the return leg. Once the destination office discharges the movement, that signal has to write back into the TMS and ERP so the guarantee headroom is released and the audit trail is closed.

Want to see the end to end flow? Watch a demo.

Integrating NCTS and CDS Into One Operational View

John Hall — Mon, 21 Sep 2026 07:29:08 +0000

The point of integration is not to hide the difference between NCTS and CDS. It is to surface it in one place.

Model each system as a service

Two endpoints. Two schemas. Two audit trails. Any integration that pretends otherwise creates silent drift. The NCTS and CDS operational comparison sets out the field-level differences worth respecting.

Bind them at the consignment level

Shipment identifiers, GMR references and product records live above the two systems. That is where the join belongs.

Present a unified queue

Operators do not need to know which platform is talking. They need to know what is blocking discharge or clearance.

Route corrections to both endpoints

A single amendment action, two API calls under the hood.

Report on both, together

Discharge times and clearance times belong on the same dashboard.

Ready to see a unified operational view? Watch a demo.

Integrating NCTS5 Filing With Freight Systems

John Hall — Fri, 18 Sep 2026 07:21:37 +0000

Why integrate at all?

Integrated filing removes duplicate data entry between transport management systems, warehouse systems and customs software. It also cuts rejection rates by using validated master data.

Integration points

Consignor and consignee master data from CRM or TMS
Commodity codes from product masters or ERP
Guarantee data from finance or treasury systems
Route and office data from routing engines ## Data mapping

Map commercial invoice lines to goods items. Map shipping units to house consignments. Map the top-level movement to the consignment record. For the full NCTS declaration workflow, review how each mapping supports the IE015 message.

Message handling

Send IE015 to the office of departure. Parse the returned MRN and store it against the movement record. Handle functional error responses at the field level.

TAD distribution

Once the TAD is issued, distribute the PDF and MRN barcode to drivers, subcontractors and third-party portals through your integration layer.

Want to see NCTS5 integration ready out of the box? Watch a demo.

Integrating NCTS Phase 5 With Your TMS and ERP

John Hall — Thu, 17 Sep 2026 07:28:04 +0000

The point of integrating NCTS with a TMS or ERP is not to move messages. It is to keep MRN state, guarantee state and shipment state in sync so no one has to reconcile them by hand.

The three canonical objects

The MRN. The anchor for every transit event.
The guarantee. A running balance of committed amounts.
The shipment. The business object the rest of the company cares about. The Movement Reference Number in transit guide sets out how the MRN is issued and how it moves through the offices.

Integration checkpoints

Declaration submission. Enforce guarantee headroom check at TMS side before calling NCTS.
Release. Persist the MRN and TAD reference on the shipment record.
Transit. Append every office-of-transit notification to the MRN timeline.
Destination. Mark shipment as discharged only on the NCTS discharge message.

Common failure modes
Duplicate MRNs from retry loops without idempotency keys.
Guarantee state drifting between TMS and NCTS.
Discharge received but not written back to the shipment.

What good looks like

One source of truth for every open MRN. Alerts on age and on guarantee headroom. Zero manual reconciliation at week end.

Bring NCTS, guarantees and shipments into one workflow. Watch a demo.

Integrating TMS, WMS and Customs for UK Transit in 2026

John Hall — Wed, 16 Sep 2026 07:56:48 +0000

The integration problem

Most operations run three separate systems: a TMS for movement, a WMS for inventory, and a customs platform for declarations. UK transit customs only works when those three share a common reference set.

Shared references that make the join

A shipment identifier, an EORI, a commodity code and an origin flag are the minimum shared fields. Add the export MRN, transit MRN and GMR once they exist, and the join becomes deterministic across systems. A field-level view is in this UK-EU freight compliance walkthrough.

Event triggers that keep systems in sync

Customs events — declaration accepted, transit MRN issued, GMR committed, arrival notification received — should trigger status changes in the TMS and stock releases in the WMS. Missing event wiring produces the classic "phantom pending" shipments that survive long after the truck has cleared.

FAQ

Can these integrations be built without APIs?
File-based integration works but adds latency. Event-driven APIs are strongly preferred for GVMS gate order.

Which system should own the primary shipment ID?
Whichever system creates the shipment first — usually the TMS. Every downstream system references it.

Ship customs as an event stream. Watch a demo with iCustoms.

Integrating with HMRC's NCTS Phase 5 Trader Test Application

John Hall — Tue, 15 Sep 2026 07:52:50 +0000

Why the test app exists

The Transit Test Application is HMRC's trader-facing sandbox. It accepts IE015 submissions without touching live movements and returns the full NCTS 5 message range so your integration can rehearse both success and rejection paths.

Access

Access is via Government Gateway with credentials tied to an authorised EORI. Getting user assignment right inside the organisational account is what unblocks a first-week go-live.

The wider context is in the iCustoms NCTS 5 testing environment guide.

What to rehearse

Happy path: IE015 → IE028 → IE029.
Rejection path: IE015 → IE056 with field pointers.
Refusal path: IE015 → IE051 or IE055.
Arrival: IE007 → IE043 → IE044 → IE045. ## Ship without surprises

Watch a demo to see a pre-integrated NCTS 5 platform.

Integrating TSS AI with the Rest of Your Trade Stack

John Hall — Mon, 14 Sep 2026 07:40:03 +0000

Why integration decides ROI

Standalone TSS AI leaves value on the table. The wins compound when extraction, ERP, freight, and reporting share the same product and declaration records.

Product master integration

Send your product catalogue in. Pull enriched records out. Match on a stable ID, not a description. The reuse layer only pays off when catalogue changes flow in near real time. This is why source-data hygiene is non-negotiable, as the manual customs work reduction article explains.

Freight and transport document ingestion

Wire your freight forwarder feeds into the extraction queue. Push transport documents automatically. Reduce email-based handoffs.

ERP write-back

Push confirmed declaration data back to finance. Landed cost, duty accruals, and origin records all belong in the ERP.

Reporting

Expose a read-only reporting API. Volumes, rejection rates, correction reasons, and audit events all belong in your BI stack.

Identity and authorisation

Single sign-on plus role-based permissions is table stakes. Auditors will ask.

Webhooks for events

Submission, acceptance, rejection, and status change events should fire webhooks. Do not scrape screens.

Compliance boundaries

UKIMS status, EORI, and other authorisation records stay under the trader's control. The platform stores them. The trader owns them.

Talk integration with us. Watch a demo.

Integrating TSS Into a Freight Forwarder Tech Stack

John Hall — Fri, 11 Sep 2026 06:55:33 +0000

What integration actually touches

A working TSS integration for a forwarder touches four systems: the client onboarding record, the product master, the operational booking system, and the finance ledger that tracks payment routing per client.

Client onboarding record

Onboarding produces the signed data specification, EORI, UKIMS position, and commercial terms. These become configuration inputs to every downstream module.

Product master per client

Products belong to clients. Sharing a global master across traders is where data cross-contamination begins. This Northern Ireland customs software walkthrough lists hard client data separation as the first of six multi-client software requirements.

Booking system as the trigger

The booking triggers the declaration, not the other way round. Movement references cannot be built until customs data exists, so the booking system needs the declaration status back on the same record.

Finance ledger and payment routing

TSS lets agents facilitate payments. Finance needs visible routing per client per declaration, so month-end reconciles without spreadsheet archaeology.

API vs portal, per lane

Repeat lanes go to the API. Ad-hoc, new-client, or unusual movements go to the portal. Integration design accepts the mix rather than forcing a single channel.

Retention and offboarding

Data retention arrangements when a client departs are a contract question that the integration must honour. Build the export path before it's needed.

See a full-stack TSS integration walkthrough. Watch a demo.

Integrating TSS with Your ERP: What to Get Right First

John Hall — Thu, 10 Sep 2026 10:12:00 +0000

The integration is not one system, it is two

A TSS API project is really an ERP-to-TSS integration. The TSS side is well documented. The ERP side is where every project spends its time.

Establish the source of truth

Product data, party data and consignment data each need one authoritative home. If the ERP does not currently own them, the integration will drift within weeks. The TSS integration analysis puts this first for a reason.

Map fields to specifications

Every TSS field needs an ERP field or a computed value. Where a computed value is used, document the logic and version-control it.

Design for two-way traffic

Submissions go out. Responses come back. Both need to update the ERP so the audit trail is complete on one side.

Handle exceptions without breaking the ERP flow

Rejected submissions should not corrupt ERP records. A separate exceptions area, tied back by reference, keeps the ERP clean.

Keep the portal available

Hybrid coverage matters even after a full integration. Controlled goods, new suppliers and unusual movements often still route through the portal.

See a TSS-to-ERP integration with hybrid portal fallback. Watch a demo.

Integrating TSS Software With Your ERP, WMS and TMS

John Hall — Wed, 09 Sep 2026 07:45:35 +0000

Most declaration errors are data problems in disguise. The value of TSS software depends on whether it can reach the data you already hold.

Assess the source systems first

Identify where party data, product data, commodity codes and shipment data actually live. Usually that is ERP for products and parties, WMS for movements and TMS for transport documents.

Look for real connectors, not "we can integrate"

Ask which of your specific systems the vendor connects to today, in production, at another customer. For a working framework, see this Trader Support Service integration guide.

Handle supplier documents realistically

Supplier invoices are the messiest input. The right tool treats OCR as a stage in the pipeline, not a magic step, and asks a human when it is not sure.

Own the mapping

Data mapping is usually a bigger cost than the licence. Budget for it.

Map iCustoms against your current stack. Watch a demo.

Integrating TSS, GVMS and CDS Data in One Ops View

John Hall — Tue, 08 Sep 2026 07:23:21 +0000

The integration problem

Three systems own different parts of the movement. TSS owns the declarations and MRNs. GVMS owns the vehicle-facing GMR. CDS owns the declaration format. Ops teams need one view.

What to pull from where

From TSS: movement status, MRNs issued, declaration references, authorisation flags relevant to GMR automation.
From GVMS: GMR status, check-in status, embarked status, inspection notifications.
From CDS: underlying declaration state and MRN validity. ## The join keys

MRNs join declarations to a GMR. Vehicle and trailer registration numbers join the physical movement to the GMR at check-in. EORI joins the trader across TSS and GVMS, and is required in the EIDR entry for XI-prefixed references.

An operational view of the same joins is in this TSS and GVMS integration walkthrough.

Status transitions to expose

gmr_built → checked_in → embarked → inspection_status_known. Each transition is a notification opportunity, especially inspection status after embarkation.

Where the integration usually breaks

Trailer swaps that happen outside the customs system and never make it into the GMR update flow. Design the integration to accept trailer changes as a first-class event.

Bring TSS, GVMS and CDS data into one workflow. Watch a demo.

Integrating ENS Filing With TMS and Customs Systems

John Hall — Mon, 07 Sep 2026 08:15:13 +0000

The integration case

ENS data lives in three systems: the TMS (transport), the customs stack (declarations), and ICS2 (safety and security). Without integration, each is rekeyed and each is a mismatch risk.

TMS side

Pull booking, mode, vehicle, and routing data from the TMS into the ENS builder. Store the returned Movement Reference against the booking so it is available for port check-in. The ENS submission requirements guide covers the full field set.

Customs side

Under the simplified customs route, supplementary declarations auto-generate from ENS data. That means the ENS is the upstream source of truth. Bad ENS = bad supplementary.

ICS2 side

Handle acknowledgements, Movement References, and rejections through structured message handling, not manual email flows. This matters most for volume lanes.

Sync rules

One source of truth per consignment.
Corrections applied upstream, cascaded down.
XI EORI resolved at booking, not submission.
Description library shared across TMS and customs. ### What to test

Test rejection handling, mismatch scenarios, and correction flows before go-live, not after.

Integrate ENS with the rest of your customs stack — Watch a demo.

DEV Community: John Hall

Integrating T1 and T2 Data into Your TMS and ERP

The three data sets that must sync

Mapping T1 and T2 to your data model

Keep the discharge signal flowing back

Integrating NCTS and CDS Into One Operational View

Model each system as a service

Bind them at the consignment level

Present a unified queue

Route corrections to both endpoints

Report on both, together

Integrating NCTS5 Filing With Freight Systems

Why integrate at all?

Integration points

Message handling

TAD distribution

Integrating NCTS Phase 5 With Your TMS and ERP

The three canonical objects

Integration checkpoints

Common failure modes

What good looks like

Integrating TMS, WMS and Customs for UK Transit in 2026

The integration problem

Shared references that make the join

Event triggers that keep systems in sync

FAQ

Integrating with HMRC's NCTS Phase 5 Trader Test Application

Why the test app exists

Access

What to rehearse

Integrating TSS AI with the Rest of Your Trade Stack

Why integration decides ROI

Product master integration

Freight and transport document ingestion

ERP write-back

Reporting

Identity and authorisation

Webhooks for events

Compliance boundaries

Integrating TSS Into a Freight Forwarder Tech Stack

What integration actually touches

Client onboarding record

Product master per client

Booking system as the trigger

Finance ledger and payment routing

API vs portal, per lane

Retention and offboarding

Integrating TSS with Your ERP: What to Get Right First

The integration is not one system, it is two

Establish the source of truth

Map fields to specifications

Design for two-way traffic

Handle exceptions without breaking the ERP flow

Keep the portal available

Integrating TSS Software With Your ERP, WMS and TMS

Assess the source systems first

Look for real connectors, not "we can integrate"

Handle supplier documents realistically

Own the mapping

Integrating TSS, GVMS and CDS Data in One Ops View

The integration problem

What to pull from where

Status transitions to expose

Where the integration usually breaks

Integrating ENS Filing With TMS and Customs Systems

The integration case

TMS side

Customs side

ICS2 side

Sync rules