TransitTrack
Stop switching between freight portals and project trackers. Parcels, vessels, and manual entries update on the Jira issue your team already uses.
FREIGHT-142 · Customs clearance
Package
In transit
ETA 15 Jun 2026
AIS vessel
At anchor
→ Melbourne
Shipments · 2 active
- Package tracking across 70+ carriers (FedEx, DHL, Australia Post, Sendle, and more)
- Ocean vessel tracking by MMSI, destination, ETA, port arrival, and delay detection
- Manual freight for containers and BOLs that APIs can't track
- Issue sidebar glance + full issue panel, status visible without opening the app
- Project-wide Freight movements tab with board and project filters
- Per-shipment notification rules, status changes, delays, customs, and fees
- Shippo webhooks + hourly poll post Jira comments and email assignees & watchers
- Authenticated JSON feed for external ops dashboards, no Jira login required
Key outcome
Freight status on the Jira issue itself, parcels, vessels, and manual entries update automatically so coordinators stop switching between portals.
Built for
Logistics coordinators, supply chain teams, and Jira Cloud admins who need shipment visibility tied directly to the work items they already manage.
Typical deployments
- Freight and customs clearance workflows
- Ocean cargo with AIS vessel monitoring
- Ops wallboards via JSON movements feed
Go deeper
- AIS vessel tracking surfaces destination, ETA, and port arrival, not live map coordinates
- Authenticated JSON movements feed for ops wallboards without Jira logins
- Shippo webhooks plus hourly poll fallback, comments and emails on status changes
- Per-shipment notification rules for delays, customs holds, and fees
Not in scope
No container or BOL API lookup, use manual freight entries. AIS depends on vessel transmission; Shippo tracking may incur per-number costs for non-Shippo shipments.