Air Cargo Management Software
Keep the shipment connected to the aircraft that carries it.
Manage cargo requests, consignments, shipment records, piece information and flight allocations in one cargo-operator workspace. Follow what has been accepted, assigned, held, offloaded and deliveredwith the operational flight close by.
A booking is only useful when the cargo moves
An accepted request creates work for sales, handling and operations. Teams need to know the weight, dimensions, origin, current station, allocated flight and cargo statenot just an invoice number.
Built around the way you work
Each capability is part of the connected FlightStratix workspace.
Requests and consignments
Record customers, shippers/consignees, commodity, route, weight, volume and special handling information.
Piece-level records
Track piece details, chargeable weight and shipment status; receive, accept, hold or release cargo as the documented workflow allows.
Flight allocations
Assign eligible pieces to cargo flights, support split allocations and record offloads when plans change.
Handling and export records
Review tracking events and produce supported shipment data exports including ONE Record-style JSON-LD or XFWB files where configured.
From start to finish
Cargo shipment management from acceptance to delivery
A cargo booking should remain traceable through acceptance, allocation, loading and delivery.
A shipment record with the right details
Capture customer, shipper and consignee, origin and destination, commodity, pieces, dimensions, weights and handling instructions. Display total and chargeable weight, current station and associated flight allocations.
Piece-level allocation to flights
Allocate particular pieces to eligible flights from the shipment's current station. A shipment can be split across several flights and allocations can be offloaded when plans change. This is distinct from a general airfreight forwarding database.
Operational acceptance and holds
Record receipt, acceptance for carriage, holds, hold releases and arrival delivery as managed events. Staff can inspect shipment statuses and piece-level movements in the same system used for cargo flight planning.
Relevant cargo documents and interfaces
Attach dangerous-goods declarations to relevant shipments, issue NOTOC from the flight plan where required and export core shipment information as ONE Record-style JSON-LD or Cargo-XML XFWB. Exports are not claims of certified third-party transmission.
The cargo record behind a booked consignment
Capture the shipment in a form operations can use
A shipment record holds the customer, shipper, consignee, origin/destination, commodity, pieces and their dimensions and weights. It displays both the total weight and chargeable weight, plus special-handling information. For cargo teams, the value is in retaining the detail of what was accepted for carriage rather than keeping only an AWB reference and estimated total weight. Customer quotations and shipment records remain connected to the flight-allocation workflow without being confused with the actual operated flight.
Put acceptance, holds and deliveries on record
The cargo workflow supports receipt of pieces, acceptance for carriage, holds and releases, cancellation of eligible shipments and delivery at the arrived station. Staff can view the shipment's status, current station, allocations and recorded events together. When a handling exception occurs, the record identifies which consignment and which pieces are affected instead of requiring a search through flight remarks and email.
Allocate pieces to flights with visible constraints
The user chooses eligible flights from the shipment's current station over the available booking window. Specified pieces can be allocated to one flight or split across multiple flights, and allocations can be offloaded where needed. Once linked to a flight load plan, the shipment allocation is managed through its own workflow rather than editing the plan item as an unrelated block of cargo. This maintains the relationship between customer's shipment and physical planned load.
Maintain ULD and dangerous-goods context without inflated claims
ULD records store codes, serviceability and movement history; pieces can be associated with a ULD. Dangerous-goods declarations record UN number, shipping name, class, quantities and acceptance decisions, with a NOTOC workflow tied to the flight's current load. These are useful operational records. The current references do not establish live barcode-scanner integrations, certified regulatory classification or a complete warehouse management platform, so the page should not promise those capabilities.
Connect cargo sales, capacity and flight control
Cargo quotations use rate cards and charge types such as freight, fuel surcharge, security, handling and charter. Capacity tools show remaining space on cargo flights; load planning checks compartment fit and release conditions. The Cargo Ops platform runs the aircraft and crew side of the operation. Readers should be able to move naturally from this page to cargo booking, cargo load planning and the Cargo Ops platform.
Keep shipment, flight and status in one workflow.
Make allocation decisions against the shipment
Review the shipment details and the flight it is intended to travel on before confirming the operational allocation. Keeping both records accessible helps the team understand the effect of a change to the cargo or the movement.
Connect shipment and load planningRecord events where the next team can find them
A useful shipment status needs a recorded event and enough context for the next coordinator. Keep event updates connected to the shipment record rather than treating an email update as the only operational history.
Explore shipment event tracking- Accept requestRecord the cargo enquiryComplete
- Create shipmentBuild consignment recordComplete
- 03Record piecesWeights, dimensions, detailsIn review
- 04Allocate flightAssign to eligible flightsPending
- 05Update statusTrack cargo movementsPending
- 06Close deliveryComplete the shipmentPending
See it in context
A shipment split between two departures
A customer books a multi-piece consignment, but one flight lacks sufficient available capacity. The planner allocates a subset of pieces to the first eligible flight and the remainder to another. The shipment record retains both allocations, current status and movements. Cargo operations then reviews each relevant load plan independently before flight release; no one should infer that the entire consignment departed solely because one aircraft took off.
An operational example
A shipper sends six pieces that are accepted at the departure station. Four pieces are allocated to the first flight and two to a later service. Operations can see each allocation, record what actually loads, and update delivery events as the pieces move through the operation.
Where it fits in FlightStratix
Frequently Asked Questions
Is this software for freight forwarders or for airlines?
This page focuses on cargo aircraft operators and their shipment-to-flight records. A freight-forwarder ERP or customs platform is not evidenced by the references.
Can one shipment be placed on multiple flights?
Yes. The source reference describes allocation of specified pieces to eligible flights and split allocations.
Are industry export formats certified end to end?
The code includes ONE Record-style JSON-LD and XFWB exports; partner interoperability and certification were not established in the source review.
Can one shipment move on multiple flights?
Yes. The Cargo Shipment workflow allows piece-specific allocation to more than one eligible flight.
Is this a cargo airline system or freight-forwarder software?
It is primarily for airlines and freighter operators managing operational flights and cargo movements. It should not be advertised as a complete freight-forwarder ERP.
Explore FlightStratix solutions
Connect cargo records to the freighter operation.Book an Fx Cargo Ops demo.
Book a 30-minute walkthrough tailored to your operation.