Practical software guides
A cargo portal can coordinate release evidence; it cannot grant customs or terminal authority. Separate document receipt, authorised release and physical handover.
| Event | Evidence |
|---|---|
| Arrival recorded | Carrier reference; source and timestamp |
| Count/seal checked | Authorised observation; discrepancy retained |
| Document received | Issuer and revision; review status |
| Release approved | Actual responsible authority and approved scope |
| Handover | Recipient verification and matched receipt |
Keep capture time, system receipt time and any correction separately. Use an append-only audit trail with controlled corrections; “tamper evident” requires a defined threat model and tested controls, not a label on a table.
For a seal mismatch, hold the affected release and follow the approved authority’s escalation. Test a repeated event, a changed document and an unauthorised release attempt. Use supported terminal/customs interfaces rather than scraping credentials or duplicating official decisions. No cargo-volume result or operational deployment is claimed.