If you are the engineer being asked to sign off on a TSS tool, the marketing decks will not help. Six technical checks will.
1. Submission API surface
Which declaration types are live in production today: ENS, simplified frontier, supplementary, full frontier? Does UKIMS internal market movement work end to end? Can port movement references be created programmatically?
2. Validation contract
What checks run pre-submission, and can they be triggered independently of submission? A useful walk-through of validation depth sits in this iTSS automation guide.
3. Throughput and back-pressure
Batch limits, per-declaration item caps, rate limits, and behaviour under the 10th-of-month spike.
4. Error contract
Structured error codes, remediation hints, webhook or queue delivery, and idempotency on retry.
5. Integration surface
File pickups, ERP connectors, OCR handoff, and clean interfaces for supplier invoice ingestion.
6. Audit export
Full history export as machine-readable data, not just PDFs, retained for the periods your movements require.
Test the API surface against your workload. Watch a demo.
Top comments (0)