Hazmat / DG Shipment Tracker

Because three documents must agree perfectly — the DG declaration, the SDS and the package marks — and any mismatch triggers re-inspection, re-documentation or rejection at vessel planning. The fix is upstream (a DG checklist before tender); the tracking job is catching the hold within hours, because a DG box parked at a terminal is paying hazmat-premium storage.

The constraint encoded in the un number / class field: the tracking risk is regulatory, not just logistical: a DG shipment held for paperwork sits in a bonded corner accruing charges while every re-inspection adds days. Generic trackers show where freight is; cargo-specific tracking shows whether the plan still works for what this freight IS — and that difference is where the expensive mistakes hide.

At the cargo's own tempo, not the carrier's reporting cycle. Hazmat / DG Shipments set their cadence by their risk clock — for time-critical variants that means same-day (sometimes same-hour) updates around the vulnerable milestones, relaxing only where the cargo genuinely can wait. A stale status on this board is a decision being made blind somewhere downstream.

No — storage is local to your device (localStorage), nothing uploads, which suits the commercially sensitive details this cargo type involves. Use CSV export deliberately when sharing is the point: claim files, customer reports, team handoffs. Private by default, shareable on purpose.