Quick Overview
VelocityOS helps freight forwarders bring shipment milestones, operational exceptions and customer updates into a shared workspace. Teams can follow shipment progress, coordinate follow-ups and connect visibility with CRM and TMS workflows. Available events and update frequency depend on the connected systems, carrier coverage and integration setup.
Track Shipment Milestones from Booking to Delivery
Freight forwarders need to understand what has happened, what is expected next and which shipments require attention. Event-based tracking provides a record of shipment progress using updates from connected systems and operational teams.
The following milestones illustrate a forwarding workflow. Availability varies by transport mode, carrier, data source and integration scope.
| Milestone | What it tells your team | Follow-up to consider |
|---|---|---|
| Booking confirmed | A booking reference and planned service have been recorded | Verify routing, equipment and relevant cut-offs |
| Cargo received or terminal gate-in | Cargo or equipment has reached the reported handover point | Check readiness for the booked departure |
| Departure reported | The relevant vessel, flight or transport leg has departed | Review the onward schedule and customer update |
| Transshipment event | Cargo has reached or departed an intermediate connection | Check the connecting leg and any revised arrival estimate |
| Arrival reported | The shipment or carrying service has reached the reported destination milestone | Confirm discharge, handling and release requirements |
| Cargo available or release confirmed | A specific availability or release condition has been reported | Check remaining holds and collection arrangements |
| Delivery confirmed | Delivery completion has been reported | Check supporting documentation and close outstanding actions |
Vessel arrival does not automatically mean cargo is available for collection. Discharge, terminal availability, customs release and carrier release are separate milestones. A missing update should be investigated before concluding that a shipment has stopped moving.
For the wider relationship between rates, quotes and shipment events, see our ocean freight software guide.
Freight Tracking Solution
What You Can Manage With Velocity
- Ocean freight tracking
- Air freight tracking
- Multimodal shipment visibility
- Container and shipment milestones
- Departure, arrival, and delivery updates
- Exception alerts and follow-ups
- Customer status updates
- Internal operations workflows
- CRM and TMS-connected shipment data
Reduce Manual Tracking Work
Operations teams often spend hours checking carrier websites, searching email threads, and replying to customer status requests.
Velocity centralizes shipment visibility so your team can reduce manual checks, respond faster, and manage exceptions before they escalate. Teams that need wider control across active jobs can also use Velocity’s operations tower to manage shipment workflows, exceptions, and operational visibility.
Turn Shipment Exceptions into Assigned Actions
A tracking update becomes useful when the operations team knows what to do next. VelocityOS connects shipment visibility with follow-up ownership and team communication, helping forwarders coordinate responses to delays, missing information and delivery issues.
Use a consistent process: review the source update, assess the impact, assign an owner, agree the next action and communicate the confirmed information. Close the exception when the issue is resolved.
| Exception | What to verify | Typical owner | Next action |
|---|---|---|---|
| Departure not confirmed | Whether the shipment sailed, was rolled or has a missing event | Origin operations | Obtain confirmation and revise the shipment plan where necessary |
| ETA changed | Source, affected milestone and difference from the previous estimate | Shipment owner | Assess the effect on connections and delivery arrangements |
| Transshipment connection at risk | Actual arrival and confirmed onward booking | Operations or overseas agent | Verify the connection and available alternatives |
| Required document missing | Document status and the party responsible | Documentation team | Request the document and track completion |
| Cargo release delayed | Exact hold, release condition and responsible party | Destination operations | Resolve the outstanding requirement before arranging collection |
| Delivery confirmation missing | Delivery status and supporting evidence | Destination operations | Obtain confirmation or investigate the delivery issue |
For a wider view of shipment tasks, team responsibilities and escalations, explore the Operations Tower
To evaluate how AI interprets updates and prioritizes operational review, see our guide to AI freight visibility and exception management.
Understand ETA Sources and Tracking Freshness
An estimated time of arrival is meaningful only when its source and milestone are clear. A vessel arrival estimate, terminal availability estimate and final delivery appointment describe different points in the shipment journey.
When reviewing tracking information, check who supplied the estimate, when it was updated and which event it describes.
| Information source | What it can contribute | What to check |
|---|---|---|
| Carrier schedule or tracking feed | Planned movements, revised estimates and reported transport events | Exact event definition, latest update and shipment coverage |
| Connected TMS | Shipment references, operational milestones and recorded estimates | Original source and whether the information is estimated or actual |
| Agent or operations update | Local handling, release or delivery information | Confirmation time and the person responsible |
| Predictive ETA service, where integrated | A calculated arrival estimate | Prediction source, supported milestone and how it differs from the carrier estimate |
Update frequency depends on the source and connection method. A recently received message may describe an event that happened earlier, so distinguish the event time from the time the update was received.
Event-based tracking describes reported shipment progress. It does not imply continuous GPS positioning of the cargo. Treat an ETA as an estimate until the corresponding actual event is confirmed.
Give Customers Useful Shipment Updates
A useful customer update explains the latest confirmed milestone, any change to the expected timeline and the next action. Keep vessel arrival, cargo availability and final delivery clearly distinguished.
For example, if a carrier revises an arrival estimate, tell the customer which milestone changed, when the update was received and whether delivery arrangements need to be reviewed. Avoid presenting the revised estimate as a confirmed delivery date.
A digital freight portal can bring customer-facing shipment information and documents into the wider service workflow, subject to the configured access and integration scope.
Connect Tracking With Operations
Velocity connects shipment visibility with the wider freight workflow, from quote acceptance to booking, milestone tracking, exception management, customer updates, and delivery completion.
This gives sales, operations, customer service, and management teams a shared view of shipment progress. It also helps teams connect post-quote execution with quote management and customer handoff workflows.
Connect Freight Tracking with Your TMS and CRM
Freight tracking works best when shipment references, milestones and customer records remain aligned across systems. VelocityOS can exchange shipment and visibility information through configured integrations, with the exact scope determined by the connection method and the agreed system of record.
A common setup keeps the TMS as the operational record while making selected shipment updates available in VelocityOS and the customer-facing workflow.
| Data group | Example information | Integration decision |
|---|---|---|
| Shipment identity | Shipment ID, booking reference and relevant transport references | Define the identifiers used to match records |
| Milestones | Departure, arrival and delivery events | Select the authoritative source and map event meanings |
| Exceptions | Status flags and reason codes | Agree which system creates and updates the exception |
| Documents | Transport documents and proof of delivery | Define access permissions and synchronization scope |
| Customer context | Account ID and responsible contact | Match the shipment to the correct customer record |
Confirm synchronization direction for each data group. Some information may flow from the TMS to VelocityOS, while other records follow a different direction. API, webhook and connector capabilities depend on the systems involved.
See what Velocity can sync for the supported data groups and integration patterns.
Freight Tracking Solution
Benefits of Velocity Freight Tracking Software
- Faster access to shipment status
- Fewer manual tracking checks
- Reduced customer update emails
- Better exception visibility
- More consistent customer communication
- Improved team accountability
- Stronger shipment visibility across offices
- Better customer experience
Why Choose Velocity?
Velocity is more than a tracking tool. It helps freight forwarders connect shipment visibility with operations, customer communication, and internal workflows.
Use Velocity to replace manual tracking processes, reduce repetitive updates, manage exceptions, and deliver a more scalable digital freight experience. For teams that also need stronger pricing control, Velocity’s rate management tools help connect rates, quotes, shipments, and customer updates.
See Your Shipment Workflow in Action
Bring an example shipment and the systems your team uses today. Review how shipment references, available milestones, exceptions and customer updates would connect in your workflow. Confirm carrier coverage, update frequency and integration scope for your key lanes and transport modes.
Freight Tracking Software FAQs
Freight tracking software helps forwarders monitor shipment status, milestones, delays, and delivery progress from one system.
Carrier tracking links usually show limited shipment status. Velocity connects tracking information with operations workflows, exception management, and customer communication.
Yes. By centralizing shipment visibility and making updates easier to share, Velocity helps reduce repetitive status request emails.
Yes. Velocity supports shipment visibility workflows for ocean, air, and multimodal freight forwarding operations.
Operations, customer service, sales, management, and branch teams can all use freight tracking software to improve visibility and coordination.