Air Cargo Shipment Tracking Software
Give customers a clearer answer to "Where is my cargo?"
Keep shipment status, current station, allocation and recorded movement events together. Fx Cargo Ops supports shipment records and a tokenised public tracking link so authorised recipients can view available updates without seeing the operator’s internal workspace.
Shipment status should not depend on one person's inbox
When cargo is received, held, allocated, offloaded or delivered, the operation needs a consistent record. A customer-facing tracking link makes recorded status easier to share.
Built around the way you work
Each capability is part of the connected FlightStratix workspace.
Status and current station
Review the shipment’s recorded location, state, pieces and history in the operations workspace.
Flight allocation visibility
See eligible allocations to flights, including split pieces and recorded offloads where applicable.
Public status link
Generate a token-based shipment tracking link and share a limited external view.
Export shipment data
Use documented JSON-LD / XFWB exports where a partner requires structured data, subject to interoperability testing.
From start to finish
Shipment tracking from recorded station and flight events
Give customers a useful status they can open without exposing your internal cargo workspace.
Shipment status with current station
See received, accepted, held, allocated and delivered states recorded against the shipment, with the current station and associated pieces. Customers see the information your team has recordednot a fictitious worldwide live-tracking feed.
Connect status to flight allocations
Inspect allocations of individual pieces to eligible cargo flights and offloads when plans change. Operations has a clearer answer to "which flight carried this piece?" than a single shipment-level booking line.
Share a scoped tracking link
Copy a tokenised public shipment link. The external view can expose the appropriate shipment progress without requiring a full company user account. Treat links as scoped access and do not publish internal cost or staff information.
Export shipment facts when needed
Cargo exports include ONE Record-style JSON-LD and Cargo-XML XFWB built from core shipment, piece and movement fields. This is export capability, not certified compatibility with every partner or automatic customs transmission.
What customers can trackand what the system records
Shipment status belongs to the consignment
A shipment record contains the current station, current status, pieces, flight allocations and recorded tracking events. The cargo team can receive pieces, accept them for carriage, place a hold, release a hold, record a delivery or cancel where allowed. These controlled operational actions produce more useful status information than a generic 'booked' label that remains unchanged throughout the movement.
A shareable tracking link is not a live GPS tracker
The system can generate a tokenised public tracking URL for a shipment. That allows a customer or authorised recipient to view the published tracking state without exposing the internal cargo-management interface. The information is based on recorded shipment events, not an assertion that physical cargo is being followed continuously through scanner feeds, airline network messaging or IoT devices. The marketing page should use 'shipment status tracking' rather than claiming worldwide real-time location telemetry.
A flight allocation isn't proof that cargo departed
Individual shipment pieces can be allocated to eligible cargo flights, split across flights and offloaded. The shipment record keeps that operational context so the team does not confuse a planned allocation with a completed physical movement. If only part of the shipment departs, the record can show the remaining pieces and subsequent processing rather than presenting the entire consignment as delivered.
Make export formats precise
The system supports ONE Record-style JSON-LD and Cargo-XML XFWB exports from shipment data. The implementation references core shipment, waybill, piece and event information; it does not establish a certified ONE Record API server, full IATA conformance or successful transmission to a particular airline or customs authority. Link external standards only from informative help content, not as badges implying certification.
Hand customer-service questions back to the source record
When a customer asks why a shipment has been held, staff should review the shipment status, hold/release events, station and allocations before responding. Connected shipment and cargo operations records give the team a consistent answer based on what has actually been entered. Explore Air Cargo Management for the internal shipment workflow and Cargo Ops for the flight context.
Give each status update a record behind it.
Follow recorded shipment events
Use the shipment history to review the events entered by your team and the operational context behind the current status. This provides a traceable handover without presenting a manually recorded update as a live location feed.
Explore shipment managementKeep the flight allocation within reach
When a customer asks about a shipment, its allocation and operational record help explain the next action. Keep booking and flight context available alongside event history so the team can answer from the same information.
Explore cargo booking- Receive piecesCheck in cargo at stationComplete
- Accept shipmentConfirm consignment detailsComplete
- 03Allocate to flightAssign to eligible flightsIn review
- 04Record eventsTrack offloads and changesPending
- 05DeliverComplete at destinationPending
- 06Share statusCustomer tracking linkPending
See it in context
A consignment is held at origin
A shipment has been accepted but a hold is recorded before flight allocation. The public tracking link reflects the recorded status; it should not show the goods as on board. After the hold is released, eligible pieces can be allocated and subsequent recorded events appear in the shipment history. The customer sees the status available in the application, not an invented live-location feed.
An operational example
A customer asks where a two-part consignment is. The cargo desk sees that one allocation reached its flight while the second part remains at the origin station. The team records the correct movement status and shares the shipment tracking link so the customer can check the updated record.
Where it fits in FlightStratix
Frequently Asked Questions
Is this real-time GPS tracking of cargo pieces?
No. The documented capability presents recorded shipment events and statuses, not sensor/GPS tracking of individual pieces.
Can customers view shipment progress?
Yes. The product includes a tokenised public tracking page based on the available shipment record.
Is this live GPS tracking for cargo?
No. It presents shipment progress and events captured in the FlightStratix cargo workflow.
Can a customer see shipment details without an internal account?
A tokenised public link is available to share appropriate shipment status externally.
Explore FlightStratix solutions
Make recorded cargo status easier to see and share.Book an Fx Cargo Ops demo.
Book a 30-minute walkthrough tailored to your operation.