DEV Community

Cover image for Troubleshooting Stuck TSS Movements
Kristi Hampson
Kristi Hampson

Posted on

Troubleshooting Stuck TSS Movements

When a TSS movement stalls, the root cause almost always sits in one of five places.

1. The commodity code is wrong or too shallow

Six digits where eight are required, or a code that doesn't match the description. Fix the master data, resubmit.

2. The at-risk position isn't defensible

No UKIMS, no evidence, or evidence that doesn't map to this shipment. Reclaim as at risk or delay until the paperwork holds.

3. Safety and security data has no owner

Ambiguity between trader and carrier is the classic failure. Assign ownership explicitly and audit it.

4. Movement reference vs vehicle mismatch

Trailer swap, different registration, missing container. Rebuild the reference against the actual vehicle before check-in, as covered in this TSS troubleshooting reference.

5. Reference built before customs entry

Impossible by design. If your system offers it, your system is lying to you.

If you'd like to see how iCustoms surfaces and resolves these failure modes automatically, watch a demo.

Top comments (0)