TSS vs Direct CDS: Two Customs Workflows Side by Side

Two customs workflows, same destination. Here is how they look on paper.

Workflow A — Through TSS

1. Register with TSS (EORI + business details).
2. Enter movement details in the portal.
3. Answer the at-risk goods questions.
4. TSS submits the declaration into CDS.
5. HMRC processes and returns the outcome.

Workflow B — Direct to CDS

1. Subscribe to CDS (EORI, Government Gateway, UTR, business address, NI number for sole traders).
2. Connect to CDS through customs software or a customs intermediary.
3. Build the declaration.
4. Submit into CDS.
5. HMRC processes and returns the outcome.

The direct CDS filing overview explains where each workflow saves time and where each one creates friction.

Where they diverge

TSS is designed for Northern Ireland movements and gives you built-in guidance. CDS-direct is designed for control and scale, but you own the tooling and validation.

Where they meet

Both routes end in CDS. The declaration processed by HMRC is CDS-shaped either way. That is why audit records and duty adjustments always trace back to CDS, not to TSS.

Which to choose

Northern Ireland movements at low/moderate volume: TSS.
High-volume filing, mostly outside Northern Ireland, or existing customs software in place: CDS-direct.
Mixed profile: run both, and route each shipment down the right lane.

See both routes running side by side inside one tool. Watch a demo with iCustoms.