The integration problem
Three systems own different parts of the movement. TSS owns the declarations and MRNs. GVMS owns the vehicle-facing GMR. CDS owns the declaration format. Ops teams need one view.
What to pull from where
- From TSS: movement status, MRNs issued, declaration references, authorisation flags relevant to GMR automation.
- From GVMS: GMR status, check-in status, embarked status, inspection notifications.
- From CDS: underlying declaration state and MRN validity. ## The join keys
MRNs join declarations to a GMR. Vehicle and trailer registration numbers join the physical movement to the GMR at check-in. EORI joins the trader across TSS and GVMS, and is required in the EIDR entry for XI-prefixed references.
An operational view of the same joins is in this TSS and GVMS integration walkthrough.
Status transitions to expose
gmr_built → checked_in → embarked → inspection_status_known. Each transition is a notification opportunity, especially inspection status after embarkation.
Where the integration usually breaks
Trailer swaps that happen outside the customs system and never make it into the GMR update flow. Design the integration to accept trailer changes as a first-class event.
Bring TSS, GVMS and CDS data into one workflow. Watch a demo.
Top comments (0)