Updating ETA and tracking changes
How to change a shipment's ETA, what gets logged, and why the history matters.
Updated Apr 18, 2026
ETAs change. Weather, port congestion, and customs delays all push dates around, and your team and your customers need to stay in the loop. ImportOps records every ETA change on a shipment so you always have a clear answer when someone asks what happened and when.
Before you start
- You need Shipments edit permission.
- You're on the shipment detail page.
Where to update
Two options:
- Update ETA in the action bar. A compact sheet with only the ETA fields, designed for this job.
- Edit shipment when you want to update ETA alongside other fields.
What you record
- The new ETA date.
- A short summary of why it changed (for example, "delayed by port congestion" or "brought forward, vessel on early approach").
What gets logged
Each change writes an entry to the ETA history with:
- The previous ETA
- The new ETA
- A timestamp
- Your summary
You see the full list on the shipment detail page under ETA history, newest first.
Why the history matters
- Your team shares one source of truth. Nobody has to remember who changed what.
- When a customer asks "has the ETA slipped again?", you can answer with specifics.
- Reporting and handovers become painless because the sequence of changes is already written down.
What your customers see
The ETA on a customer's tracking page (when it's enabled) always reflects the shipment's current ETA. The history itself stays internal.
Was this helpful?