Why one workflow beats five tickets
Trade teams that treat each TSS declaration as a separate ticket end up with orphaned data. A single workflow — with clear branches — removes that.
The workflow
Every GB→NI movement starts with an ESD from the carrier. Once the ESD is in, the trader branch begins. If UKIMS and non-Category 1, run the IMMI branch — one submission, pre or post movement. Otherwise, run the Simplified Procedure branch — SFD at movement, supplementary by the 10th of the next month.
Inventory-linked ports and airports for maritime and air movements branch to Full Frontier — four steps: safety/security, inventory claim, full declaration, duty payment.
If you want the reference for each branch, this TSS Simplified Procedure guide mirrors the same structure.
What to instrument
Track submission events per declaration type, not per movement. Alert on supplementary declarations still auto-populated after day 5. Alert on UKIMS-eligible movements running Simplified when IMMI would apply. Report on Full Frontier duty payments as a separate KPI from ro-ro.
Reliability payoff
Workflow clarity is the cheapest reliability upgrade you can make to a customs process.
Want the workflow prebuilt? Watch a demo to see the iCustoms TSS engine in action.
