DEV Community: iCustoms

Workflow Design for a High-Volume TSS Operation

iCustoms — Fri, 28 Aug 2026 07:04:55 +0000

When you move dozens of loads a day from GB to Northern Ireland, TSS becomes a workflow engineering problem.

Split the flow into three phases

Before movement: confirm route, assemble goods and party data, settle at-risk, choose declaration route.
At submission and port: safety and security data, TSS customs entry, movement reference and vehicle match.
After arrival: supplementary declaration and record-keeping.

Ownership per step

Model each step with a named actor. This TSS workflow guide lays out the split cleanly: traders own goods and at-risk, carriers own safety and security, hauliers own the movement reference.

Trigger points

Kick off the customs entry as soon as the shipment is booked, not the day of movement. The reference-cannot-precede-entry rule turns short lead times into blockages.

Instrumentation

Log every stage transition with a timestamp. If you can't see where a movement is stuck, you can't fix it in time.

If you'd like to see how iCustoms operationalises this workflow end-to-end, watch a demo.

The GB to NI Customs Workflow, System by System

iCustoms — Thu, 27 Aug 2026 08:32:10 +0000

Here is a clean trace of a standard GB to NI road movement across the four HMRC systems.

Step 1: Trader submits movement information

A single entry captures the goods, value, procedure, transport and route. This is the source of truth for everything downstream.

Step 2: TSS validates and routes

TSS enriches the entry, checks it against reference data, and sends structured payloads out.

Step 3: CDS returns the customs decision

The declaration is filed and returns a decision on duty, procedure and clearance status. CDS is the answer to "what did customs decide about these goods".

Step 4: ICS2 receives safety and security data

Safety and security data goes to ICS2 before the goods arrive. This is a separate obligation from the customs declaration.

Step 5: GVMS bundles references into a GMR

GVMS packages the declaration references into a single Goods Movement Reference. The driver presents the GMR at check-in. The Goods Movement Reference explained view covers what causes rejection.

Step 6: Vehicle embarks

When the vessel departs, the movement moves to embarked status. That triggers the automated downstream processes.

Practical takeaway

Every step depends on clean data at Step 1. That is where engineering effort pays back.

Ready to see this workflow in a working product? Watch a demo to walk through iCustoms.ai with a live agent.

TSS vs Direct CDS: Two Customs Workflows Side by Side

iCustoms — Tue, 25 Aug 2026 06:55:28 +0000

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

Workflow A — Through TSS

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

Workflow B — Direct to CDS

Subscribe to CDS (EORI, Government Gateway, UTR, business address, NI number for sole traders).
Connect to CDS through customs software or a customs intermediary.
Build the declaration.
Submit into CDS.
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.

The GB to NI Movement Workflow, Step by Step

iCustoms — Mon, 24 Aug 2026 07:18:16 +0000

The 10-step shape

Every GB to Northern Ireland movement follows roughly the same sequence:

Confirm the route (GB to NI)
Gather goods detail: commodity code, description, quantity, weight, value, origin
Establish at-risk status (may the goods move on into the EU?)
Check whether UKIMS or another simplification applies
Work out which declarations the movement needs
Enter the information into TSS
TSS submits to the relevant systems
Complete any movement reference the carrier needs at the port
Customs and safety & security processing take place
Goods travel and arrive ## Where teams get stuck

Steps 2 and 3 cause the most delay in practice. Commodity code errors at step 2 cascade into every later step, while getting at-risk status wrong at step 3 affects the duty position for the whole movement. Resolve both before step 6.
Full walkthrough: TSS for GB to NI movements

At risk vs not at risk

Goods that may go on to the EU are treated as at risk. Goods meeting the relevant conditions can be treated as not at risk, most relevantly, goods authorised under UKIMS moving in for sale or final use in Northern Ireland.

Building a repeatable process

Once a business has run this workflow a handful of times, the pattern becomes routine. The Trader Goods Profile helps here: it pre-populates commodity data for goods you move regularly, so step 2 becomes a lookup rather than a re-entry exercise.

Watch a demo

Building a TRACES Validation Workflow That Scales

iCustoms — Fri, 21 Aug 2026 07:11:05 +0000

Map Where the Code Lives First

Before writing any integration code, find out where the establishment code sits in your master data and which events touch it: supplier creation, purchase order, booking confirmation.

Three Workflow Patterns

Nightly batch re-validates the full catalogue after hours and produces a morning-ready report. Event-driven checks fire the moment a new supplier or PO is created and return a result in seconds. A pre-shipment gate blocks a booking at the TMS level while any code on the consignment is flagged red. This iTraces REST API supports all three without changing the underlying validation logic.

Combining Patterns

Most production workflows use more than one. Nightly batch catches drift across the whole catalogue; event-driven checks stop bad data at the point of entry; a pre-shipment gate is the last line of defence before goods move.

Where the Result Should Land

Route every validation result to the same place: a compliance dashboard and audit trail, regardless of which pattern triggered the check.

Designing for Failure

Decide upfront what happens when the API is unreachable. A gate that fails closed blocks shipments; one that fails open ships unchecked goods.

Watch a demo to see nightly batch and event-driven checks running side by side.

Add a Pre-Shipment TRACES Validation Step to Customs

iCustoms — Thu, 20 Aug 2026 07:56:12 +0000

Put the validation step before booking confirmation, not before departure. A pre-shipment TRACES validation check that runs at booking gives you time to swap a supplier or query an approval. Run it too late and the only options left are delay or risk. The step itself is small: validate every establishment code on the consignment, then act on flags only.

Definition

A pre-shipment validation step is a gate in your existing customs process that blocks progress while any establishment code is unconfirmed.

Designing the gate

Keep it boring and predictable.

Trigger: a new or amended consignment record.
Input: every approval number, plus country and activity.
Output: pass, flag, or unknown.
Rule: flags stop the booking, not the whole queue. ### Who touches it

Operations raise the consignment. Compliance handles flags. Nobody opens the portal for a code that passed.

Fitting it into the current flow

Most customs processes already have a document check and a declaration stage. Slot validation ahead of both, because a delisted establishment invalidates the paperwork you are about to prepare. Manual checking cannot sit here, since three to five minutes per code makes booking too slow, and the portal offers no bulk search or change alerts. Automated checking makes the gate cheap enough to keep, which is the shape of a TRACES validation workflow.

Handling exceptions well

Route flags to a named owner, not a shared inbox.
Re-run validation after any supplier amendment.
Record the decision, including overrides. Exception handling is where the freed time should go once manual effort drops by up to 80%.

FAQ

Does this slow bookings down?
No. Validation runs in seconds, so only flagged consignments pause.

What if a code is unknown rather than failed?
Treat unknown as a flag and confirm the country and activity before proceeding.

How is the step evidenced?
Each run leaves a timestamped record against the consignment.

Check how many hours your workflow could give back before the next booking. Watch a demo

Building an EU Establishment Approval Workflow That Doesn't Break at Volume

iCustoms — Wed, 19 Aug 2026 07:44:33 +0000

A one-off establishment check is easy. A workflow that holds up across hundreds of products and suppliers is a different problem.

Step one in the workflow: classification

Every check starts with an accurate commodity code, including for composite products. Get this step wrong and the rest of the workflow checks against the wrong rule entirely.

Step two: regulation mapping

Route the code to either Regulation (EC) 853/2004 or Regulation (EU) 1069/2009, depending on whether it's food or animal by-product material. This products requiring EU establishment approval breakdown lays out which chapters go where.

Step three: establishment lookup

Query the TRACES NT lists for the exporting country and activity. This is the step that doesn't scale manually once you're working across a full supplier catalogue.

Step four: re-validation trigger

Build a check that fires before every shipment, not once a year. Approval status changes without notice, and a stale check is worse than no check because it creates false confidence.

Where workflows commonly fail

Most breakdowns happen at step three, where teams either skip the activity-level check (approved for meat, not for by-products) or rely on a supplier's self-declared status instead of the official list.

Automating the workflow

Bulk validation against the TRACES database, with confidence scoring on classification, removes the two steps most prone to manual error.

Watch a demo to see this workflow running end to end.

The CHED Lifecycle as a State Machine: Five Transitions, One Final State

iCustoms — Tue, 18 Aug 2026 08:35:27 +0000

Why a state machine is the right mental model

The Common Health Entry Document process is linear, gated, and ends in a terminal state. That makes it a natural fit for a state machine, and modelling it that way exposes exactly where your team has control and where it does not.

The states

Drafting. The operator completes Part 1 in TRACES NT: consignment details, origin, health certificates and establishment approval numbers. Fully mutable.
Submitted. Lodged before arrival, ahead of the border control post's notice period. Still amendable while it remains on your side.
Under control. Documentary checks on all consignments, then identity checks matching seals and labels to paperwork, then risk-based physical checks with sampling.
Decided. The border control post writes Part 2: accepted, accepted with channelling, or refused. Terminal.
Referenced. The CHED reference is quoted in the customs declaration so the goods can be released. Walking through the CHED lifecycle workflow end to end makes clear how little of the process sits after submission.

The transitions that cost you

The drafting to submitted transition is where the notice period bites. Miss it and you are not in a failed state, you are in a waiting state, which is often more expensive.

The under control to decided transition is one way. Refusal branches to re-export, destruction, or supervised transformation, none of which are cheap.

Where to put your effort

Almost all recoverable error lives in the first two states. Build your checks there, not in exception handling. To see pre-submission validation applied to a live consignment, watch a demo.

Mapping the TRACES NT Workflow End to End

iCustoms — Mon, 17 Aug 2026 08:43:10 +0000

If you are building tooling around EU import compliance, it helps to draw the workflow before writing anything. TRACES NT has a predictable shape, and the failure points sit in known places.

The happy path

A source certificate arrives from the exporter or competent authority.
The operator signs in through EU Login with two-factor authentication.
The correct CHED type is selected: CHED-A, CHED-P, CHED-PP or CHED-D.
Consignment details, certificate numbers and establishment codes are entered.
Codes are checked against official lists.
The document is signed electronically and submitted.
The border control post records a decision, visible in real time. ## Where it breaks

Steps four and five are human, and they are the ones that generate holds. Under TRACES Classic the same information travelled on printed, signed and stamped paper, so errors surfaced late and slowly. TRACES NT surfaces them faster, but it does not prevent them. The wider context for how this workflow evolved is covered in this look at the TRACES NT document workflow.

Instrumenting the weak steps

Log the time between certificate receipt and CHED submission. Log every code correction. Two weeks of that data usually shows which suppliers, product lines or operators generate the rework. Then automate extraction for the fields that fail most often rather than trying to automate everything at once.

Reporting

Qlik Sense replaced QlikView in 2024 and supports flexible filtering, so operational metrics can be pulled from the platform side as well as your own.

See the extraction and validation workflow running end to end: watch a demo.

Mapping the End to End TRACES NT Workflow Before Your First CHED

iCustoms — Wed, 12 Aug 2026 07:53:37 +0000

The workflow in one view

Registration is stage one of a longer chain: EU Login, two-factor authentication, access request, organisation validation, first login, CHED preparation, pre-arrival submission, border control post decision, then results retrieval. Teams that map the whole chain before registering rarely get stuck at the handover points.

Stage one: gaining access

Registration is free. EU Login takes minutes, and organisation validation usually takes one to a few working days. Prepare a work email, exact organisation details, a mobile for two-factor authentication, and a decision on role type before you start. This TRACES NT onboarding process breakdown is worth reading alongside your internal runbook.

Stage two: choosing the right document

Four CHED types route consignments differently:

CHED-A for live animals
CHED-P for products of animal origin
CHED-PP for plants and phytosanitary items
CHED-D for non-animal food and feed under increased controls Selecting the type is a data decision made upstream, usually from commodity classification, so build it into your product master rather than leaving it to whoever files.

Stage three: submission and response

Active accounts submit CHEDs before the consignment arrives, then access border control post decisions and check results. Health certificates and phytosanitary documentation are managed in the same place, and establishment lists supporting approvals are available for reference.

Where handovers break

The two weak points are role ambiguity between importer and broker, and single administrator setups that block new user approvals. Fix both during stage one and the rest of the workflow holds.

Find out how iCustoms shortens the steps between document arrival and CHED submission. Watch a demo.

Automating Establishment Code Checks Before Goods Move

iCustoms — Tue, 11 Aug 2026 07:32:59 +0000

Automating establishment code checks means validating every code against the official EU list on a schedule, not on demand at booking. The value is not speed. It is catching state changes you were never told about, because a supplier can be suspended or delisted mid contract with no notification to the importer.

Why on demand checking is not enough

A check at booking gives you a point in time answer. If the load ships two weeks later, that answer may be stale. Codes are mutable reference data with no push notification, so the only reliable pattern is periodic revalidation of your active supplier set plus a check immediately before departure.

What to automate, in order

Bulk revalidation: run the full supplier and code list against the official database rather than checking one at a time
Document data extraction: pull codes, quantities and seal numbers from certificates and invoices instead of re-keying them
Cross document comparison: assert equality across the certificate, invoice and CHED
Status dashboarding: surface product, supplier and code status with an audit trail Intelligent document processing removes the manual entry step where mismatches originate. Reported effort reduction on manual checking sits around 80%, and automated code validation against the official TRACES EU database runs at 99% accuracy. The guidance on automated establishment code checks follows the same sequence.

The alerting question

An automated check is only useful if a delisting reaches a human who can act. Route alerts to whoever can hold the booking, not to a shared inbox.

FAQ

How often should codes be revalidated?
Often enough that no active supplier goes unchecked between booking and departure.

Watch a demo to see bulk revalidation and document extraction running across an active supplier set.

The EUDR DDS Workflow as a Five-Stage Pipeline

iCustoms — Mon, 10 Aug 2026 08:44:37 +0000

Treat the Due Diligence Statement as a pipeline with five stages: collect, assess, mitigate, submit, reference. Each stage has an input, an output and a failure mode, which makes the whole thing easier to build and easier to monitor.

Stage by stage

Collect. Input: supplier records. Output: plot geolocation plus supporting evidence. Failure mode: incomplete coordinates. Assess. Input: country benchmarking and supplier evidence. Output: a risk position of negligible or non-negligible. Failure mode: undocumented reasoning. Mitigate. Input: a non-negligible risk. Output: either mitigation evidence or a decision to withhold the product from the market. Failure mode: proceeding without either. Submit. Input: a completed statement. Output: a reference number from the EUDR Information System. Failure mode: filing before data is validated. Reference. Input: the reference number. Output: a customs declaration that quotes it. Failure mode: a mismatch, which stops the consignment.

Instrument the pipeline

Each stage deserves a status you can query, because compliance questions arrive as questions about individual consignments. If your logistics team cannot answer "does this load have a valid reference" in seconds, the pipeline is not finished. A missing reference stops the load in the same way a missing health certificate does, and the five-step DDS filing process explains how each stage connects to the next.

Design for repetition

Statements are not one-off events. Sourcing changes, plots change and country classifications change, so make re-running a stage cheap.

FAQs

Can mitigation be skipped for low risk countries? Low risk allows simplified due diligence, but the assessment still has to happen.

Who owns the pipeline? Operators and traders both hold obligations, so ownership must be agreed contractually.

Watch a demo and walk through the workflow with iCustoms