DEV Community: John Hall

Integrating TSS with Your ERP, WMS or Customs Platform

John Hall — Tue, 01 Sep 2026 07:21:39 +0000

Pick an integration surface

Do not scatter TSS calls across your codebase. Wrap them in a single service with a clear internal contract.

Map fields once

Field mapping between your source systems and the TSS specification is the highest-leverage work in the whole project. Do it once, do it properly.

Design for retries and idempotency

Network calls fail. Design your submissions so a safe retry does not create a duplicate declaration. The TSS API onboarding guide covers the operational side of this well.

Keep the test environment permanently wired up

You will need it for every release, not just the first one.

Want to skip half of this build? Watch a demo of iCustoms and see a pre-built TSS integration.

Integrating TSS Declaration Data With ERP and Freight Systems

John Hall — Mon, 31 Aug 2026 07:27:05 +0000

Declarations are only as accurate as your source systems

TSS declarations are only as accurate as the data feeding them. That data usually sits in your ERP, TMS and WMS — long before the customs form is opened.

The data map

ERP owns commodity codes, product master and origin. TMS owns carrier, port, mode and movement date. WMS owns consignment weight, packaging and lot detail. Customs tooling combines all three into ESD, SFD, supplementary, IMMI or Full Frontier records.

The exact field expectations per declaration are covered in this Northern Ireland TSS declarations explainer.

Integration principles

Pull commodity codes from ERP once, not per declaration. Push port and mode from TMS into route selection so inventory-linked ports trigger Full Frontier automatically. Push UKIMS status onto every trader record so IMMI eligibility is calculable at booking. Log every submission event back into ERP for month-end reporting.

Treat the deadline as an SLA

Treat the 10th-of-month supplementary deadline as an SLA between systems, not a manual reminder.

The result

Well-integrated declaration data means the customs system stops being where errors are discovered and becomes where correct data is submitted.

Want to see the integration prebuilt? Watch a demo of iCustoms.

Integrating ERP, WMS and TMS with TSS

John Hall — Fri, 28 Aug 2026 07:07:54 +0000

Most TSS pain isn't in TSS. It's in the gap between commercial systems and the customs workflow.

The data already exists

Goods descriptions live in the ERP. Movements sit in the TMS. Weights and locations live in the WMS. TSS wants a subset of all three.

Design the integration by direction

Push goods and party data from ERP into TSS. Push vehicle and container details from TMS. Push weights and packing details from WMS. Never let staff copy across.

The system view is set out in this TSS integration guide for GB-NI operations.

Handle the movement reference bottleneck

The reference is created after the customs entry lands. Model it as a callback, not a synchronous step.

Keep records where auditors look

UKIMS requires five years of retention accessible in the UK. Store the audit-ready record set in a UK-hosted system by default.

To see how iCustoms plugs into your existing ERP, WMS and TMS in production, watch a demo.

Integrating Your ERP with TSS, ICS2, GVMS and NCTS

John Hall — Thu, 27 Aug 2026 08:35:05 +0000

Building an integration between an ERP and the HMRC customs stack is a system-of-systems problem. Here is a stable shape.

Map to a single canonical record

Model the consignment once in your ERP. Every field that ends up in CDS, ICS2, GVMS or NCTS should trace to a canonical column with a documented format.

Route through TSS

TSS is the intended input layer. Push canonical records through it rather than trying to file to each backend directly. That gives you one contract to test against, not four.

Version your commodity codes

Commodity codes change. A versioned lookup table protects downstream systems from a code that was valid last quarter but not this one.

Reconcile after routing

Once TSS has fanned out to CDS, ICS2, GVMS and NCTS, pull back the identifiers each system returned and store them against your canonical record. This is what makes audits fast. The TSS and CDS integration guide covers the identifier map.

Instrument the seams

Log at each hop, not just at the boundary. When a check-in is rejected weeks later, the seam is where the answer lives.

Practical takeaway

Design for reconciliation, not just submission. That is the difference between an integration that scales and one that survives one audit.

Ready to plug an ERP into all four HMRC systems the clean way? Watch a demo to see the iCustoms.ai integration path.

Integrating Customs Software with TSS and CDS

John Hall — Tue, 25 Aug 2026 07:02:17 +0000

You can either treat TSS and CDS as two separate integrations, or as one pipeline with two exit points. The second approach ages better.

Understand the roles

CDS is HMRC's Customs Declaration Service. It processes UK import and export declarations. TSS is a free portal specifically for Northern Ireland movements that formats and submits data into CDS.

If you build customs software, CDS is where you certify. TSS is where many Northern Ireland movements pass through on their way to CDS.

Data model first

Design your internal declaration record to match CDS field structure. If your record is CDS-shaped, feeding it into TSS is straightforward, and feeding it into a direct CDS submission is a matter of connector configuration.

This TSS vs CDS explainer is a useful primer for engineers coming into the space for the first time.

Auth and identity

Plan for GB EORI, XI EORI, Government Gateway credentials, UTR and NI number handling. Different traders on the same platform will have different identifiers, and Northern Ireland movements often need both a GB and XI EORI.

Error surfacing

Rejections need to reach the operator with enough context to fix the source data — not just "TSS rejected" or "CDS rejected". Map error codes to human-readable prompts.

Volume considerations

Above a certain declaration volume, portal-based TSS filing becomes a bottleneck. Route those flows through direct CDS instead.

See a real integration between customs software, TSS and CDS. Watch a demo with iCustoms.

How TSS Connects to CDS, ICS2, GVMS and NCTS

John Hall — Mon, 24 Aug 2026 07:24:23 +0000

Four systems, one entry point

TSS doesn't replace any of the UK's core customs systems, it sits in front of them. Each downstream system does one job:

CDS (Customs Declaration Service): HMRC's system for customs declarations.
ICS2 (Import Control System 2): handles safety & security data, replacing the older ICS, used for movements into Northern Ireland from 31 December 2025.
GVMS (Goods Vehicle Movement Service): bundles declaration references into a single Goods Movement Reference for roll-on roll-off traffic.
NCTS (New Computerised Transit System): manages customs transit. ## Why this matters for integration planning

You give TSS the information once, and it feeds whichever of the four systems the movement requires. For a business building internal tooling around TSS, this means the integration point is TSS itself, not each downstream system individually.

The GMR dependency

For roll-on roll-off traffic specifically, the carrier needs a Goods Movement Reference before the vehicle can travel. GVMS builds that reference from declaration data already submitted through TSS, which is why declarations need to be complete before the vehicle reaches the port, not after.

Practical integration takeaway

If you're evaluating where to plug automation into a GB–NI customs process, TSS is the natural integration point: one submission surface, four downstream destinations, rather than four separate integrations to maintain.

Read the full breakdown on the guide to using TSS

Four systems, one entry point

TSS doesn't replace any of the UK's core customs systems, it sits in front of them. Each downstream system does one job:

CDS (Customs Declaration Service): HMRC's system for customs declarations.
ICS2 (Import Control System 2): handles safety & security data, replacing the older ICS, used for movements into Northern Ireland from 31 December 2025.
GVMS (Goods Vehicle Movement Service): bundles declaration references into a single Goods Movement Reference for roll-on roll-off traffic.
NCTS (New Computerised Transit System): manages customs transit. ## Why this matters for integration planning

Read the full breakdown on the guide to using TSS

The GMR dependency

Practical integration takeaway

Watch a demo

Connecting SAP or Dynamics to a TRACES Establishment API

John Hall — Fri, 21 Aug 2026 07:28:52 +0000

Why REST and JSON Matter Here

Standard REST endpoints with JSON responses mean SAP, Microsoft Dynamics, Oracle, NetSuite and most TMS or middleware platforms can connect without custom adapters.

The Two Questions That Matter

Technical connectivity is rarely the hard part. The real design questions are where the establishment code lives in your master data, and at which moments validation should gate the process. This TRACES compliance API connects the same way regardless of which ERP sits on the other end.

Middleware and TMS Considerations

If validation needs to gate a TMS booking rather than an ERP record, the integration point moves earlier in the process, at booking creation rather than supplier setup.

Documentation and Sandbox First

Confirm the Developers Hub documentation and sandbox access before committing to a go-live date.

One Integration, Multiple Checks

The same API access also covers document data extraction and HS code classification, so a single integration effort can support more than establishment validation alone.

Watch a demo to see the API connect to a sandbox ERP environment.

TRACES Validation Integration for Customs Workflows

John Hall — Thu, 20 Aug 2026 07:56:02 +0000

A TRACES validation integration should sit upstream of your declaration and document steps. Validate every establishment code as soon as the consignment data exists, then pass the result forward so declarations and documents are built on confirmed approvals. Doing it the other way round means preparing paperwork first and discovering a delisted code later, when the fix is expensive.

Definition

Integration here means one validation result, produced once, consumed by every downstream customs step.

The data flow

Keep the contract between steps simple.

Consignment data arrives with approval numbers, country and activity.
Validation returns status, flags and a timestamp.
Document processing reads the status before extraction is trusted.
Declaration filing reads the same status as a precondition. ### Why one result, not three

Repeated manual checks by different teams produce different answers on different days. A single validated record removes that drift.

Connecting the pieces

Intelligent Document Processing can pull supplier and establishment details from documents, iClassification handles HS codes, and declarations run across the UK, Ireland and 22 EU nations. Validation is the gate that keeps all of it honest, because a perfect declaration against a suspended establishment still fails at official controls. Continuous feeds by API make that gate cheap, and the wider case for TRACES validation integration is that it removes a manual handoff rather than adding a system.

What to expose downstream

Pass, flag or unknown, as a single field.
The flag reason, for triage.
The check timestamp, for the audit trail. That is enough for a declaration workflow to block, retry or continue without a human reading the portal.

FAQ

Where should validation run?
Before document processing and declaration filing, on the earliest consignment record.

What blocks a filing?
Any flag, including unknown, until someone reviews it.

Does this replace spot checks?
No, single-code searches still answer one-off questions quickly.

See how many hours your integration could hand back before the next declaration. Watch a demo

Connecting Classification and Establishment Validation Into One Compliance Flow

John Hall — Wed, 19 Aug 2026 07:47:35 +0000

Treating classification and establishment validation as separate systems creates a gap exactly where errors happen.

Why separation causes problems

If classification runs in one tool and establishment validation runs in another, someone has to manually pass the confirmed commodity code from one system to the next. That handoff is where mistakes get introduced, particularly for composite products.

What an integrated flow looks like

Classification determines the commodity code and flags whether it falls under Regulation (EC) 853/2004 or (EU) 1069/2009. That result feeds directly into an establishment lookup against the TRACES lists for the correct country and activity, without a manual re-entry step. This establishment approval for EU exporters overview shows how the two checks map to each other.

Connecting to documents and declarations

Classification and establishment checks feed the same consignment as your commercial documents and customs declarations. Keeping all of it, document data, HS codes, establishment status and filing, on one platform avoids reconciling the same shipment across five separate tools.

What this looks like at scale

Logistics providers running compliance across the UK, Ireland and multiple EU markets need classification and validation to run consistently across every filing, not configured separately per country.

The result

Connecting these steps closes the loop between the right code and the right list, before the shipment reaches the border, rather than discovering the gap there.

Watch a demo to see classification, validation and filing running from one platform.

Connecting the CHED to Your Customs Declaration Without Dropping the Reference

John Hall — Tue, 18 Aug 2026 08:39:12 +0000

Two systems, one consignment

Health controls and customs are separate processes with separate records. The Common Health Entry Document is filed in TRACES NT and closed by the border control post in Part 2. The customs declaration is a different submission entirely. The join between them is the CHED reference, and it is easy to drop.

The failure this causes

A consignment can pass the documentary, identity and physical checks, be recorded as accepted in Part 2, and still not be released, because the customs declaration does not carry the CHED reference. Nothing is wrong with the goods. The two records simply have not been linked. Reading through the CHED and customs declaration integration step makes clear that this is treated as part of the same job, not a separate one.

Designing the handoff

treat the CHED reference as a required field on the customs declaration for any regulated consignment, not an optional one
pull the reference from the CHED record rather than re-keying it, since transcription is where digits get lost
validate the CHED type against the goods classification at the same point, so CHED-P and CHED-D confusion is caught once
keep both records under one consignment identifier internally, so the link is queryable after the fact ### Classification as the shared dependency

The CHED type follows the product, and so does the customs classification. iClassification determines HS codes across 32 or more countries, which lets the same classification decision drive both the CHED type and the declaration rather than being made twice by two teams.

Bring both submissions into one audited flow, and watch a demo to see the reference carried through automatically.

Integrating Customs Software Around TRACES NT

John Hall — Mon, 17 Aug 2026 08:47:16 +0000

TRACES NT is interoperable with customs IT and other EU digital systems, which is a real change from TRACES Classic and its limited external integration. If you are planning an integration, it helps to be precise about what connects to what.

The systems context

TRACES NT is a core component of IMSOC, the Information Management System for Official Controls, alongside iRASFF, ADIS and EUROPHYT. It operates under Regulation (EU) 2017/625. Your integration is joining an ecosystem, not a standalone application.

What surrounding software actually does

TRACES NT remains the official certification platform. Automation software around it extracts document data, validates establishment codes and files customs declarations, so information is accurate before it reaches TRACES. That is the useful division of labour: the Commission owns certification, your stack owns data quality. This boundary is described in this guide to TRACES NT and IMSOC integration.

Design considerations

Plan for EU Login and two-factor authentication in any user-facing flow. Model all four CHED types rather than the one your first customer needs. Keep an authoritative local copy of establishment code lists and refresh it, because stale reference data creates the exact error you built the integration to prevent.

Reporting side

Qlik Sense replaced QlikView in 2024 and offers flexible filtering, which is worth checking before you rebuild dashboards you could simply consume.

Scale reference

More than 5.4 million official documents in 2024 across 113,000+ users in 90+ countries.

See how iCustoms connects to your customs filing process: watch a demo.

Fitting TRACES NT Into an Existing Customs and Compliance Stack

John Hall — Wed, 12 Aug 2026 07:56:16 +0000

TRACES NT is one component, not the whole stack

TRACES NT handles sanitary and phytosanitary certification for animals, plants, food and feed under Regulation (EU) 2017/625. It does not handle customs declarations, document capture or master data quality. Planning where those responsibilities live is what makes the stack coherent.

Start with identity and organisation structure

Because access is granted per organisation, decide whether your broker files under their own registration or yours before anyone creates accounts. Getting this wrong produces duplicate organisations that need competent authority correction later. The TRACES NT operator registration guide explains the role choices that drive this.

The data feeding the certificate

CHED preparation depends on accurate consignment data. iCustoms Intelligent Document Processing extracts that data at 99% accuracy, reducing the manual re-keying that causes rejected notifications.

Validating establishment codes

Establishment approvals sit behind many CHED submissions. iTraces validates establishment codes against the official TRACES database, so you find a problem before the border control post does.

Filing across member states

Consignments rarely stop at one country. iCustoms supports EU customs filing across 22 EU nations, and logistics operators including Kerry Logistics, Ziegler and Woodside Logistics Group use these services alongside their own systems.

A practical sequence

Register on TRACES NT, confirm role and organisation at first login, connect document extraction to your CHED preparation, then validate establishment codes as a pre-submission check. Each layer catches what the previous one missed.

See how iCustoms connects document processing, establishment checks and EU filing in one place. Watch a demo.