Air freight software (also called air cargo software or air freight management software) is the operating system that runs a freight forwarder's air cargo business, from rate quoting through MAWB and HAWB documentation, e-AWB submission to airlines, air customs filing, milestone tracking, and per shipment accounting. The right platform for enterprise air forwarders in 2026 has to handle multi carrier and multi GSA relationships, IATA CASS settlement, Cargo iQ milestones, ACAS pre departure filing, and ULD level consolidation without forcing a separate air only tool bolted onto an ocean TMS. This buyer guide walks through the eight features that actually matter in an air freight FMS, the top air cargo software providers worth evaluating, the build vs buy decision for forwarders and airlines, and how the requirements shift between enterprise and mid market air forwarders.
Air freight management software is a purpose built system that runs the complete air cargo workflow for a freight forwarder or NVOCC. Unlike a generic transportation management system (which is often shipper focused and centered on truck load planning) or a warehouse system, an air FMS is built around the specific artifacts of air cargo: the Master Air Waybill, the House Air Waybill, air consolidations, IATA rate agreements, airline schedules, and airline settlement through CASS. It supports the full lifecycle from quoting a shipper against contract or spot air rates through booking a Master Air Waybill with the airline, pairing houses under the master, submitting e-AWB data via EDI or the ONE Record data standard, filing ACAS or ICS2 pre departure declarations, tracking Cargo iQ milestones from acceptance to delivery, and closing the shipment with a per file profit and loss statement.
The term overlaps with several adjacent categories. An air freight TMS usually refers to the same system, though shippers sometimes use "air freight TMS" to mean the transportation planning module inside a broader supply chain suite. AWB management software is a narrower slice, focused only on the documentation layer. A full air freight FMS covers the entire operational workflow, not just AWB printing.
See Air Freight Management Software for how GoFreight approaches air freight specifically, including both air export and air import workflows on a single cloud native platform.
These are the capabilities that actually matter when a forwarder is comparing air freight platforms in 2026. Any shortlist that skips one of these is missing a piece of the workflow that ops teams will end up doing in a spreadsheet.
Air rate management covers the storage, retrieval, and application of airline rates against a specific shipment. A production grade module has to handle IATA CASS settlement rates, TACT (The Air Cargo Tariff) published rates, negotiated contract rates per airline and per lane, and spot rates that operations quotes on the fly against carrier availability. The module needs class rates, general cargo rates, unit load device rates, and specific commodity rates alongside fuel and security surcharges that update on their own cadence.
The differentiator in 2026 is how the platform ingests contract rate sheets. Manual rate entry across dozens of airlines is unsustainable at scale. A modern air freight FMS either parses airline contract PDFs directly, ingests EDI rate feeds, or connects to airline rate APIs so ops can quote against live rates without swivel chair lookups. It also has to handle multi leg routings where a shipment moves on two or three airlines under one MAWB, with the correct rate combination applied per leg.
The Master Air Waybill is the contract of carriage between the forwarder and the airline. The House Air Waybill is the contract between the forwarder and the shipper. Pairing them correctly is the single most important documentation task in air freight. A real air FMS treats the MAWB as a container that can hold one or many HAWBs, tracks allocation by weight and volume, prevents overbooking, and produces both documents in the layout each airline and each country requires.
Beyond the printed AWB, the platform has to ship e-AWB data to the airline in real time. e-AWB (electronic Air Waybill) is the IATA data standard that replaces the paper AWB with an EDI or XML message. IATA reports that e-AWB is now used for more than 2 out of 3 shipments globally, and airlines increasingly refuse paper AWBs on major routes. Any air freight software evaluated in 2026 has to ship e-AWB as a built in capability, and forward looking platforms are already onboarding to ONE Record, which IATA named the preferred data sharing standard for air cargo effective 1 January 2026 and which now has more than 30 active pilots worldwide including Cathay Pacific, Turkish Cargo, Korean Air, Lufthansa, Schenker, and CHAMP.
Air consolidation is the practice of combining multiple House Air Waybills under a single Master Air Waybill to buy volume rates from the airline and pass margin to the forwarder. LCL air (less than container load, though "less than ULD" is more literal) is the standard revenue product for a general cargo forwarder. The FMS has to plan the build up, allocate cargo to unit load devices (LD3, LD7, PMC pallets, and the airline specific containers each carrier stocks), and track the ULD identifier through the airport handling process.
Enterprise air forwarders running gateways at JFK, LAX, ORD, LHR, FRA, SIN, HKG, and TPE need the consolidation workflow to handle overnight cutoffs, security screening records, and cargo build up documentation that airport ground handlers can read. A platform that only supports one HAWB per MAWB does not qualify.
Air cargo tracking is not a version of ocean container tracking. The milestone set is different, the update frequency is faster, and shippers expect visibility from tender through acceptance, transit, and proof of delivery within hours rather than days. The industry standard is the Cargo iQ milestone framework, which defines the events every airline reports (received from shipper, ready for carriage, freight on hand, departed, arrived, notified consignee, delivered) with standard status codes.
A production grade tracking module pulls milestones from carrier APIs where available, from IATA's Cargo iQ hub, from GHA (ground handling agent) systems at the airport, and from EDI status messages. It surfaces exceptions (missed uplift, off loaded, damaged, holds) as alerts so ops can react before the shipper calls. The module has to work at the HAWB level and the MAWB level, because the shipper cares about their house but the airline reports on the master.
See Customer Portal Software for Forwarders for how milestone data flows from the FMS into the shipper facing portal automatically, so tracking calls to the ops desk fall to near zero.
Air customs is a different set of filings from ocean. For the United States, ACAS (Air Cargo Advance Screening) is a mandatory pre departure filing that transmits shipment data to CBP as early as practicable but no later than prior to loading onto the US bound aircraft. CBP published the Enhanced ACAS interim final rule on 21 November 2025 (with corrections on 22 January 2026), which adds 5 new mandatory data elements at the lowest air waybill level, 12 conditional data elements where the shipper is not a verified known consignor, and 4 additional conditional data elements. CBP is exercising enforcement discretion for 12 months, with strict enforcement of the Enhanced ACAS data set beginning 21 November 2026. For imports, ACE e-Manifest is the electronic manifest submitted on arrival. For exports, AES filing runs on the same regulatory backbone as ocean AES but with air specific data elements. For Japan, AFR JP24 covers pre arrival filing for air cargo. For Europe, the transition to ICS2 (Import Control System 2) Release 3 completed on 1 September 2025, and ICS2 is now the sole EU system for safety and security ENS (Entry Summary Declaration) filings across air, maritime, road, and rail. Forwarders shipping to the EU file ENS data at the ULD and HAWB level for air moves. Limited temporary derogations for Poland, Romania, and Slovakia on road and rail extend into 2026, with ICS1 decommissioning by June 2026.
An air freight software platform that treats customs as a bolt on will slow the ops team down at every cutoff. A platform that natively supports ACAS, ACE e-Manifest, AFR JP24, and ICS2 filing from the shipment record removes the re keying and the risk of a rejected filing that misses the aircraft.
Enterprise air forwarders do not book one airline. They book eight, twenty, or fifty airlines across the lanes they cover, and they work with multiple GSAs (General Sales Agents) who represent airlines that do not have direct sales presence in a given market. Multi airline and multi GSA support means the platform can hold rate agreements, allocations, and settlement terms for every carrier and every GSA the forwarder works with, quote against the right combination for the shipment at hand, and settle each MAWB against the correct CASS billing statement.
For a mid market forwarder that only books three airlines directly, this is table stakes. For an enterprise air forwarder running gateways in North America, Europe, and Asia with a mix of direct carrier relationships and GSA relationships, this is the make or break architectural feature. If the platform forces one airline per shipment or one GSA per lane, the forwarder ends up managing everything else in a spreadsheet.
Air freight margins are tight and the surcharge stack is dense (fuel, security, war risk, dangerous goods, screening, terminal handling). A per invoice accounting model hides the margin variance between shipments. Per shipment accounting ties every buy rate (airline settlement, GSA commission, terminal handling, screening fee) and every sell rate (main freight, surcharges, house fees) to the specific shipment that generated them, so the forwarder can see which files made money and which files lost money in real time.
Multi currency handling is not optional. An air shipment quoted in USD to a shipper, booked on an airline that settles in EUR through a GSA that invoices in HKD is a normal file. The FMS has to hold each charge in its native currency, apply the correct FX at posting, and reconcile against the airline's CASS statement without a manual currency conversion.
See Freight Billing & Accounting Software for Forwarders for how GoFreight handles per shipment margin analysis with native QuickBooks Online integration and an open API for other ledgers.
Shippers moving air cargo expect visibility that matches an ocean tracking portal but at air speed. A branded customer portal gives the shipper a self service view of their own shipments, milestone updates as they arrive from Cargo iQ or the carrier API, and access to the AWB and the commercial documents (invoice, packing list, certificate of origin). It also lets the shipper download proof of delivery after uplift or after arrival.
The operational payoff is a sharp drop in inbound "where is my freight" calls. The strategic payoff is that a shipper with self service visibility is a shipper who does not shop the file to a competitor at renewal.
The air freight software category in 2026 has three tiers of platforms. Purpose built freight forwarding platforms cover ocean and air on one system. Legacy enterprise suites cover air as one module of a much larger portfolio. Air only tools focus on a narrow slice of the workflow (usually AWB printing or airline rate feeds) and are typically bolted onto a broader FMS.
This is a landscape sketch, not a head to head ranking. For the full multi platform comparison across ten TMS and FMS vendors including deep vendor profiles, see the Best TMS Software 2026 guide.
A recurring question from cargo IT leaders at regional airlines, freighter operators, and smaller carriers is whether custom building an air cargo platform makes more sense than buying a vendor product. The short answer for freight forwarders is that build almost never wins the three year total cost of ownership analysis. For regional airlines and freighter operators the math is different, but carrier cargo management systems still cover most of the workflow.
The build path for a real air FMS covers e-AWB messaging with dozens of airlines, ACAS filing against the CBP Enhanced ACAS data set, AFR JP24 for Japan, ICS2 ENS for the EU, CASS reconciliation, ULD allocation and airport handler documentation, Cargo iQ milestone ingestion, and per shipment accounting. Each of these is a multi month engineering project on its own, and the regulatory surface changes at least once a quarter. Buying the vendor platform moves the regulatory workload onto the vendor and puts internal engineering budget where it earns compound return: shipper facing customer experience and forwarder specific automation on top of the vendor API.
| Dimension | Build (Custom Development) | Buy (Vendor Platform) |
|---|---|---|
| Time to first production shipment | 18 to 36 months for a full air FMS | 4 to 12 weeks (cloud native) or 6 to 12 months (enterprise incumbent) |
| Upfront cost | Multi million dollar capital build, plus continuous engineering | Subscription only, no capital build |
| Ongoing regulatory work | Internal team owns e-AWB, ACAS, ICS2, AFR JP24 updates | Vendor ships regulatory updates as part of subscription |
| ONE Record readiness | Rebuild the pilot from scratch | Vendor pilots included on the roadmap |
| Fit for freight forwarders | Rarely justified at any volume | Standard answer for forwarders of any size |
| Fit for regional airlines and freighter operators | Sometimes justified for a genuinely unique fleet or lane structure | Carrier cargo management systems (IBS iCargo, CHAMP Cargospot, Unisys) still cover most of the workflow |
For a regional airline or freighter operator evaluating cargo IT at 5,000 or fewer shipments per month, start with a carrier cargo management system rather than a custom build. For freight forwarders of any size, buy the vendor platform and put engineering budget into shipper facing customer experience and forwarder specific automation on top of the vendor API.
The air freight platform decision looks different for an enterprise air forwarder and a mid market air forwarder. Both segments need the same eight features listed above, but the weight on each feature and the architectural requirements shift.
Enterprise air forwarders (200 or more employees, multi entity legal structure, multi country operations, direct relationships with 10 or more airlines plus a GSA network) need architecture first. The platform has to hold multiple legal entities on one tenant, work across offices and countries without file syncing or VPN setup, and expose an open API for the ERP endpoints, airline rate feeds, and customs filing hubs the enterprise already runs. Deep API surface is not a nice to have. It is the reason the platform survives in the enterprise stack for five years without a rip and replace.
GoFreight is architected for this segment. Multi entity and multi office run on one tenant, back office teams in one country work on the same live data as front office teams elsewhere, and the API layer supports accounting integrations (QuickBooks Online confirmed, others via open API), ERP integrations, and airline EDI including e-AWB. Coverage spans more than 1,000 forwarders across the United States, Mexico, Greater China, Taiwan, Singapore, Indonesia, Vietnam, Malaysia, Thailand, and Cambodia, with 97 percent of US ports supported. CargoWise is the incumbent alternative and remains the right shortlist entry when partners require CargoWise connectivity and the enterprise can absorb the 6 to 12 month implementation window plus the current per shipment pricing model.
See Freight Integrations Software for Forwarders for the carrier API, EDI, and customs filing connections that make the enterprise stack work end to end.
Mid market air forwarders (15 to 200 employees, one or two legal entities, three to ten airline relationships, mixed ocean and air volume) need faster onboarding, predictable subscription pricing, and a platform that does not force a migration when volume grows into enterprise scale. The wrong choice at this stage is a lightweight SMB tool that runs out of room in two years or an enterprise platform that takes 12 months to implement and never pays back the investment.
GoFreight is also the strongest mid market fit for the same reason it fits enterprise: the architecture is identical across tiers, so a mid market forwarder growing from 500 to 2,000 shipments a month stays on the same tenant with the same subscription model, and the ocean plus air unification means the team runs one system rather than a paper trail between two tools. Magaya is the alternative when integrated warehouse operations are a primary requirement.
If you are a head of cargo IT starting a vendor evaluation, this is where to start. Use this checklist when evaluating platforms. Ask each vendor to answer against your specific volume, lane mix, and integration set, not against a demo scenario.
The right air freight software becomes invisible. It quotes rates in seconds, prints AWBs that airlines accept the first time, files ACAS and AFR without a re key, and closes each shipment with a P&L line that ops and finance both trust. The wrong platform is a source of missed cutoffs, rejected filings, and margin leakage that only shows up at month end.
Match the platform to your operating model:
Ship Faster. Scale Smarter. See how GoFreight unifies air and ocean freight forwarding on one cloud native platform with e-AWB, ACAS, AFR JP24, and per shipment accounting built in. Request a GoFreight Demo →
Air freight software is a purpose built system that runs the complete air cargo workflow for a freight forwarder, from air rate quoting through Master and House Air Waybill documentation, e-AWB submission to airlines via EDI, air customs filing (ACAS, AFR JP24, ICS2 ENS), Cargo iQ milestone tracking, and per shipment profit and loss accounting. It is different from a generic transportation management system in that it covers the forwarder specific artifacts of air cargo (MAWB, HAWB, ULD allocation, CASS settlement) rather than the shipper specific workflow of carrier procurement and load planning.
A generic TMS is usually shipper focused and centered on carrier procurement, load planning, and truck routing. Air freight software is forwarder focused and centered on air specific artifacts: MAWB and HAWB pairing, IATA rate handling, e-AWB data submission, ULD build up, and CASS settlement. A shipper running their own freight can use a generic TMS. A forwarder booking on behalf of shippers, issuing HAWBs, and settling with airlines needs an air freight FMS.
The strongest MAWB and HAWB management platforms in 2026 are GoFreight, CargoWise, and Magaya on the unified freight forwarding side, and Riege Scope in the European air focused segment. All four treat the MAWB as a container that holds one or many HAWBs, track allocation by weight and volume, print AWBs in airline specific layouts, and submit e-AWB data via EDI. The choice comes down to enterprise fit, mid market fit, and whether the forwarder needs ocean plus air on the same platform.
Yes. GoFreight ships an air freight module covering MAWB and HAWB management, e-AWB data submission to airlines via EDI, AES filing for US air exports, AFR JP24 filing for air cargo entering Japan, and integration with airline rate and status feeds. The air module sits on the same cloud native tenant as the ocean module, so a forwarder running both modes works from shared customer, rate, and accounting data rather than two separate systems. See Air Freight Management Software for the full air module.
e-AWB (electronic Air Waybill) is the IATA data standard that replaces the paper Air Waybill with an EDI or XML message transmitted between the forwarder and the airline. e-AWB is not universally mandatory in law, but IATA reports that e-AWB is now used for more than 2 out of 3 shipments globally, and major airlines refuse paper AWBs on their busiest routes. Any air freight software evaluated in 2026 should ship e-AWB as a built in capability, not a plug in.
ONE Record is the IATA data sharing standard that succeeds legacy Cargo-IMP messages and provides a single, API accessible view of an air cargo shipment across the airline, forwarder, GHA, and customs. IATA named ONE Record the preferred data sharing standard for air cargo effective 1 January 2026 and reports more than 30 active pilots worldwide including Cathay Pacific, Turkish Cargo, Korean Air, Shandong Airlines, Lufthansa, CHAMP, Schenker, Riege, and PACTL. A forward looking air freight platform in 2026 should have an active ONE Record roadmap, even if EDI (Cargo-IMP or Cargo-XML) is still the day to day production standard for most carriers.
ACAS (Air Cargo Advance Screening) is a mandatory US CBP filing that transmits shipment data to customs as early as practicable but no later than prior to loading onto the US bound aircraft, so CBP can pre screen for security risk. CBP published the Enhanced ACAS interim final rule on 21 November 2025, adding 5 new mandatory data elements at the lowest air waybill level plus 12 conditional and 4 additional conditional data elements. Strict enforcement of the Enhanced ACAS data set begins 21 November 2026 after a 12 month enforcement discretion window. A production grade air freight software platform files ACAS directly from the shipment record without a separate broker tool, and it also files ACE e-Manifest on arrival for US air imports.
Ocean customs filing is centered on ISF (10+2) pre arrival, AMS manifest, and entry filing with slower cutoffs measured in days. Air customs filing is faster and pre departure oriented: ACAS is filed before the aircraft is loaded at origin, AFR JP24 is filed pre arrival for Japan, and ICS2 ENS is filed pre loading or pre arrival for the EU. Air freight software has to hit these cutoffs from the same shipment record, without re keying data that already exists in the AWB.
Air rate management stores and retrieves airline rates against the specific shipment being quoted. A production grade module handles IATA CASS settlement rates, TACT published rates, negotiated contract rates per airline and per lane, spot rates for one off quotes, class rates and general cargo rates, ULD rates for shipments booked as a full unit, fuel surcharges, and security surcharges. The differentiator in 2026 is how the platform ingests contract rate sheets: manual entry across dozens of airlines does not scale, so the platform either parses PDF rate sheets, ingests EDI rate feeds, or connects to airline rate APIs.
Yes, and unified ocean plus air on a single platform is the preferred architecture for most modern freight forwarders. GoFreight, CargoWise, and Magaya all handle both modes on one tenant, so the customer master, the accounting ledger, and the analytics roll up across ocean and air. Running ocean on one system and air on another creates duplicate customer records, reconciliation friction, and margin visibility gaps that show up at close.
CASS (Cargo Accounts Settlement System) is IATA's global airline settlement system that consolidates forwarder payments to multiple airlines into a single monthly statement per country. A production grade air FMS reconciles each MAWB against the CASS billing statement, flags variances (rate discrepancies, missing surcharges, incorrect volume), and posts the reconciled amounts to the accounting ledger without a manual re key. This is the accounting workflow that lives or dies on data quality upstream in the shipment record.
Implementation timelines vary sharply by platform category. Cloud native forwarder platforms like GoFreight go live in 4 to 8 weeks for a mid market forwarder with a standard integration set. Mid market traditional platforms like Magaya typically run 8 to 12 weeks. Enterprise platforms like CargoWise run 6 to 12 months or more, driven by per module configuration, custom integration, and third party implementation partners. The variance is driven by architecture, not vendor promises: a platform with pre built integrations and a bundled onboarding team goes live in weeks, and a modular enterprise platform takes months to years.
The top air cargo software providers in 2026 for freight forwarders are GoFreight, CargoWise (WiseTech Global), Magaya, Descartes, and Riege Scope. GoFreight leads on cloud native architecture, unified ocean plus air on one tenant, and per shipment accounting for enterprise and mid market forwarders. CargoWise is the long standing enterprise incumbent. Magaya fits forwarders running integrated warehouse operations alongside forwarding. Descartes anchors on the Air Messaging Gateway hub and paired customs products. Riege Scope has the strongest installed base among Central European air forwarders. IBS Software iCargo and CHAMP Cargosystems (Traxon, Cargospot) sit adjacent to the forwarder segment and are used primarily by airlines themselves. Rank a shortlist against your operating model rather than a single global leaderboard.
For freight forwarders, buying a vendor air cargo platform wins the three year total cost of ownership analysis in almost every case. Custom building an air FMS with native e-AWB, ACAS, AFR JP24, ICS2 ENS, ULD allocation, and CASS reconciliation runs 18 to 36 months and a multi million dollar upfront investment, and it needs a permanent internal engineering team to keep pace with IATA, CBP, and EU regulatory changes. Vendor platforms ship these integrations on day one and cover the ongoing regulatory work as part of subscription. Custom build only earns its keep for regional airlines or freighter operators with a genuinely unique fleet or lane structure that sits outside carrier cargo management systems like IBS iCargo, CHAMP Cargospot, and Unisys. For most freight forwarders, engineering budget is better spent on shipper facing customer experience than on rebuilding platform primitives that vendors already ship.
Sources: IATA e-AWB and Cargo iQ published penetration data, IATA ONE Record program documentation, CBP ACAS regulatory guidance, EU ICS2 release 3 rollout documentation, vendor published product documentation, and G2 and Capterra category ratings as of Q2 2026. Client confirmed capability details verified against internal product documentation.