The point of integrating NCTS with a TMS or ERP is not to move messages. It is to keep MRN state, guarantee state and shipment state in sync so no one has to reconcile them by hand.
The three canonical objects
- The MRN. The anchor for every transit event.
- The guarantee. A running balance of committed amounts.
- The shipment. The business object the rest of the company cares about. The Movement Reference Number in transit guide sets out how the MRN is issued and how it moves through the offices.
Integration checkpoints
- Declaration submission. Enforce guarantee headroom check at TMS side before calling NCTS.
- Release. Persist the MRN and TAD reference on the shipment record.
- Transit. Append every office-of-transit notification to the MRN timeline.
-
Destination. Mark shipment as discharged only on the NCTS discharge message.
Common failure modes
Duplicate MRNs from retry loops without idempotency keys.
Guarantee state drifting between TMS and NCTS.
-
Discharge received but not written back to the shipment.
What good looks like
One source of truth for every open MRN. Alerts on age and on guarantee headroom. Zero manual reconciliation at week end.
Bring NCTS, guarantees and shipments into one workflow. Watch a demo.
