Multi Modal Freight Management Software 2026: One Platform for Air, Ocean, and Ground

A multi modal freight management system (FMS) handles air, ocean, and ground shipments by holding every modal leg on one shipment record, issuing a single house bill (HB/L for ocean legs, HAWB for air legs) that references the master bill of each leg, stitching carrier, terminal, AIS vessel, and trucking telematics data into one milestone stream, and letting the ops team switch modes mid shipment (ocean to rail intermodal, air to ground last mile, ocean to air routing change) without opening a new file. That model is the reason forwarders have moved from three single mode systems (one for ocean, one for air, one for ground) to one consolidated FMS: the cost is the double entry, the missed handoffs, and the blind visibility spots that a split stack produces, not the software licence itself.

This 2026 update covers what changed since the original July 2026 version: an explicit walk through of the three named modal handoffs (air to ground, ocean to rail intermodal, air to last mile trucking), a rewritten unified tracking section that names each data source the platform stitches, and a sharpened section on how one house bill and one master bill carry every leg of a door to door move. Sections on booking, cost allocation, integrations, and evaluation criteria are intact from the July version and remain the practical selection framework.

What Is Multi-modal Freight Management Software?

Multi-modal freight management software is a system that quotes, books, tracks, invoices, and reports on shipments that use more than one transport mode (ocean, air, road, or rail) on a single shipment record. The defining test is not whether the software supports all three modes as separate modules. It is whether a door to door move that crosses modes stays on one shipment number with each leg as a leg attribute, and whether the tracking, cost, and document views reflect the whole move rather than the mode in isolation.

How Multi-modal Differs from a Single Mode TMS

A single mode TMS (ocean only, air only, or ground only) manages one transport type in depth: FCL and LCL bookings for ocean, MAWB and HAWB for air, dispatch and driver settlement for ground. It typically does not model a shipment that crosses modes. A forwarder using three single mode systems handles a door to door move by opening a booking in the ocean system, a second booking in the ground system for drayage, and a third booking in the air system for a last mile, then reconciles the three by hand into a customer invoice.

A multi-modal FMS collapses those three bookings into one shipment record with three legs. The customer sees one status timeline, one invoice with per leg cost breakdown, and one milestone stream. The ops team sees one file to close instead of three to reconcile.

What Counts as a Multi-modal Shipment

A multi-modal shipment is any move that uses more than one transport mode between origin and destination. The four most common patterns:

• Ocean plus trucking. Truck pickup to origin port, ocean main leg, drayage to destination consignee.
• Air plus trucking. Truck first mile to origin airport, air main leg, truck final mile to destination consignee.
• Ocean plus rail plus trucking. Truck pickup to origin port, ocean main leg to a US or EU port, rail bridge inland (IPI in the US, feeder rail in Europe), truck final mile.
• Air express plus trucking. Air express main leg (integrator like FedEx, UPS, DHL Express), truck final mile if the express carrier does not deliver to the door.

How Multi-modal Freight Management Software Handles Air, Ocean, and Ground Shipments

The practical answer to "how does an FMS handle multi-modal shipments across air, ocean, and ground" is that each mode has its own booking, document, and milestone model, but all three sit under a shared shipment header on the same record.

Ocean Shipments

Ocean legs carry FCL or LCL booking data, container numbers, seal numbers, vessel and voyage, terminal identifiers, and master and house bills of lading (MB/L and HB/L). The FMS captures the booking against the shipment record and the ocean carrier as the leg carrier.

Air Shipments

Air legs carry MAWB and HAWB numbers, flight number and date, dimensional weight and chargeable weight, and airport codes at origin and destination. The FMS captures the booking against the same shipment record with the air carrier as the leg carrier.

Ground Shipments

Ground legs carry dispatch data, driver and truck ID, pickup and delivery appointments, and either an LTL PRO number or an FTL trip number. The FMS captures the dispatch as a leg on the same shipment.

The Shared Data Model

All three legs share a common set of shipment header fields: shipper, consignee, commodity, incoterm, references (PO, SO, HB/L, HAWB), and totals. The mode specific fields sit under each leg. That shared header is what lets an ops manager pull one document pack, one invoice, and one milestone report for the entire move, regardless of how many mode transitions it contains.

How Multi-modal Booking Works in an FMS

Multi-modal booking is one screen with mode as the first field. The user picks the mode, the system loads the mode specific booking form (FCL, LCL, MAWB, HAWB, or dispatch), and the shipment record captures the leg. For a door to door move, the user adds each leg in sequence: origin pickup as leg 1 (ground), ocean main as leg 2, destination drayage as leg 3 (ground). Each leg gets its own carrier and its own booking reference; the shipment number stays constant.

Where a mature FMS separates from a single mode tool is in how leg templates carry through. A "China to US door to door" template pre populates leg 1 as ground pickup in Shanghai, leg 2 as ocean from Shanghai to Long Beach, leg 3 as rail from Long Beach to Chicago, and leg 4 as ground final mile. The ops team edits the carrier and rate per booking; the leg structure is reused.

House Bill and Master Bill Across Modes

The house bill and master bill are the two document layers that anchor the shipment inside the freight system: the master bill is the contract between the forwarder and the underlying carrier (ocean line for ocean, airline for air), and the house bill is the contract between the forwarder and the shipper.

Parity Between HB/L and HAWB

An ocean shipment issues a Master Bill of Lading (MB/L) from the ocean carrier and a House Bill of Lading (HB/L) from the forwarder. An air shipment issues a Master Air Waybill (MAWB) from the airline and a House Air Waybill (HAWB) from the forwarder. The two document sets are parallel in structure: both name shipper, consignee, notify party, commodity, and total weight and volume, and both reference the underlying master. A multi-modal FMS lays out HB/L and HAWB in identical fields on the shipment record so ops staff move between them without a mode specific screen.

One House Bill, One Master Bill, All Modal Legs on One Record

A door to door move that combines an ocean main leg with an air express last mile issues one HB/L (for the ocean leg) and one HAWB (for the air leg) against the same shipment record. Both house bills reference the shipment number and both carry the master bill of the underlying carrier. When the customer asks "what document do I hand to my broker for the ocean leg", the ops team pulls the HB/L; for the air last mile, the HAWB. Both live in the same document pack under the shipment.

For shipments where the same container moves cross mode (ocean to rail intermodal is the most common), the container number is the join key on top of the shipment number. The MB/L covers the ocean leg, the rail bill of lading covers the rail leg, and both reference the same container. The shipment record shows one row per document with the leg it belongs to.

Why the Shared Document Layer Matters

The single house bill plus single master bill per leg model matters for two reasons. First, customs filings (ISF for US ocean imports, ACAS for US air imports, ICS2 ENS for EU imports) are keyed to the house bill; if the house bill fields are inconsistent across legs, the filing gets rejected. Second, invoicing to the shipper is one invoice per shipment with per leg cost breakdown, and that only works if the document pack is unified.

The Six Core Capabilities of a Multi-modal Freight Platform

The buyer evaluation of a multi-modal FMS reduces to six capabilities. Every mature platform has all six; the differences are in depth and integration count.

1. Unified shipment record across modes. One shipment number, mode as a leg attribute, ocean and air and ground legs on the same file.
2. Cross mode booking on one screen. FCL, LCL, MAWB, HAWB, and dispatch bookings created from the same interface without leaving the shipment.
3. Stitched tracking from carrier, terminal, AIS, and trucking sources. One milestone stream per shipment, sourced from every data provider on every leg.
4. Per leg cost lines feeding one landed cost view. Buy and sell cost captured per leg and per carrier, aggregated for the shipment invoice and margin report.
5. Mode switching on the same record. Routing changes replace the leg carrier, master bill, and cost lines without opening a new shipment.
6. Unified document pack. HB/L, HAWB, commercial invoice, packing list, and any customs filings live under one shipment with the leg they belong to.

Modal Handoffs Across Air, Ocean, and Ground

The three most common cross mode handoffs are air to ground, ocean to rail intermodal, and air to last mile trucking. A fourth (ocean to air routing change) is less frequent but is the test case that separates a real multi-modal FMS from a system that only bolts three single mode modules together.

Air to Ground: First Mile and Final Mile Trucking

An air shipment almost always has a truck first mile (shipper's dock to origin airport) and a truck final mile (destination airport to consignee dock). The FMS models each as a separate ground leg on the air shipment record. The first mile leg carries the pickup appointment, truck ID, and gate in time at the airport. The final mile leg carries the airport recovery time, the truck out gate time, and the delivery appointment.

A mature FMS pushes the airline "freight available" milestone into the dispatch tool automatically and adjusts the appointment window.

Ocean to Rail Intermodal: IPI and MLB Bridging

Ocean to rail intermodal is the North American IPI (Interior Point Intermodal) and MLB (Mini Land Bridge) pattern: the container arrives at Long Beach or Los Angeles by ocean, moves inland by rail on BNSF or UP, then a final mile drayage to the consignee (Chicago, Dallas, Kansas City are common inland points). The FMS models this as one shipment with three legs: ocean leg (Shanghai to Long Beach), rail leg (Long Beach to Chicago intermodal ramp), truck leg (Chicago ramp to consignee).

The join key across the three legs is the container number. The ocean MB/L covers the sea leg; the rail bill of lading covers the rail leg; the drayage dispatch covers the final mile. All three carry the same container number and the same shipment record. A mature FMS pulls rail milestone data from the rail carrier (departure from origin ramp, arrival at destination ramp) and from the intermodal marketing companies (IMCs) that manage the rail bookings, and it stitches those into the same milestone stream as the ocean AIS position and the drayage GPS.

Air to Last Mile Trucking

Air to last mile trucking overlaps with air to ground final mile but has a distinct pattern for air express shipments where the express carrier (FedEx, UPS, DHL Express) does not deliver door to door on the customer's account. The forwarder receives the freight at the destination hub, then arranges a truck final mile to the consignee.

The FMS handles this as an air leg (integrator to destination hub) followed by a ground leg (hub to consignee). The tricky part is that the integrator's tracking number stops at the hub, so the FMS needs to attach the final mile tracking to the same shipment record and expose both tracking streams to the customer portal. Otherwise the customer sees "delivered" on the express tracker and then a silent gap until the truck driver arrives.

Ocean to Air Routing Change (Mode Swap on the Same Record)

The fourth handoff is the routing change: a shipment booked as ocean gets rebooked as air mid transit because the vessel rolled, the ocean transit is now too long, and the customer needs the freight in market for a promotion. The FMS closes the ocean leg cost lines (ocean freight, terminal handling, drayage), opens air leg cost lines (air freight, airport handling, truck first and final mile), replaces the MB/L with a MAWB, and keeps the shipper, consignee, commodity, incoterm, and references intact.

The record is not duplicated; the shipment number and history stay constant. The margin report shows the ocean cost as sunk (or recovered via carrier claim) and the air cost as the actual leg cost, so the customer invoice and the margin variance both trace to the same shipment.

Mode Switching Automation

Rules can automate the mode swap on defined triggers: vessel rolled by more than N days, air rate below a threshold, customer flagged as time critical. The FMS surfaces the decision to the ops team with the cost variance pre calculated. Full automation (rebook without human review) is rare because the cost delta is material; assisted automation (surface the option, pre populate the rebooking) is standard on mature platforms.

Unified Multi-Modal Tracking: Stitching Carrier, Terminal, AIS, and Trucking Data Onto One Shipment Record

Unified tracking is the capability most forwarders evaluate last but that separates a working multi-modal FMS from a spreadsheet with tabs. The platform pulls milestone data from four provider types and merges them onto one shipment timeline.

The Four Data Sources

1. Carrier booking milestones (EDI or API). Ocean carriers (Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, Evergreen, and so on) publish shipment events via EDI 315 messages or via GraphQL and REST APIs. Air carriers publish CIMP FSU messages. Ground carriers publish LTL and FTL status via API. The FMS ingests all three protocols and normalises the event codes to one internal event dictionary.
2. Terminal feeds (gate moves, appointments, out gate). Ocean terminals (Long Beach Container Terminal, APM Terminals, DP World, Yusen Terminals, and so on) publish container gate moves either through direct API, through the port community system, or via terminal appointment platforms (eModal is the most common in the US West Coast). The FMS ingests the gate moves as terminal events on the ocean leg.
3. AIS vessel position. Vessel position feeds from AIS aggregators (MarineTraffic, FleetMon, VesselFinder) surface real time vessel latitude, longitude, speed, and ETA to the destination port. The FMS overlays AIS position on the ocean leg between the "Loaded on Vessel" and "Discharged from Vessel" milestones, so the customer sees the vessel move on a map instead of a status gap.
4. Trucking telematics. Drayage and final mile trucking data comes from truck fleet ELDs (Motive, Samsara, Geotab), driver mobile apps, or drayage TMS integrations. The FMS ingests location pings, appointment status, and proof of delivery scans as ground leg events.

How the Stitching Works

The join keys are shipment number (primary) and container number (secondary, for cross mode container moves). Every event ingested from a provider is tagged with the leg it belongs to and normalised to a canonical event name (Loaded on Vessel, Departed Origin, Arrived Destination, and so on). The shipment record surfaces one chronological timeline per shipment with the leg badge on each event.

The customer facing tracking page shows the same timeline in the shipper portal with the internal codes translated to customer language (Booked, Picked Up, At Origin Port, On Vessel, At Destination Port, Out for Delivery, Delivered).

Where the Stitching Breaks

Two failure patterns are common. First, mismatched event codes: two providers publish the same physical event with different codes ("VessDep" from carrier EDI vs "Departed" from the terminal feed), and the timeline shows the event twice unless the FMS deduplicates on time and location. Second, missing container number on the ground leg: if the drayage carrier does not attach the container number to the dispatch, the trucking milestone cannot be joined to the ocean leg, and the timeline breaks at the terminal out gate.

Mature platforms handle both by deduplicating on event name plus timestamp window and by making container number a required field on any ground leg booked against an ocean shipment.

Multi-modal Cost Allocation and Landed Cost

Cost allocation across modes is the second capability that gets evaluated on demo but that determines whether the platform's margin report is trustworthy in production.

Per Leg Cost Lines

Every leg on the shipment carries its own buy and sell cost lines: the ocean leg has ocean freight, terminal handling, and destination charges; the air leg has air freight and airport handling; the ground leg has line haul, fuel surcharge, and accessorials (chassis, detention, storage). Each cost line names the vendor (ocean carrier, airline, drayage provider), the currency, and the buy vs sell rate.

Landed Cost Aggregation

Non transport charges (duty, insurance, brokerage fee, warehousing) are attached as separate cost lines on the shipment header, not on a leg. The landed cost quote to the shipper aggregates every leg cost line plus every header cost line into one landed number per unit or per SKU. The margin report subtracts total buy from total sell across all lines to produce shipment margin, and rolls up to customer margin, lane margin, and carrier margin views.

Why This Matters for Multi-modal

On a single mode shipment, the landed cost calculation is straightforward: one carrier, one main freight cost, plus header lines. On a multi-modal shipment (ocean plus rail plus drayage), the landed cost has to aggregate three separate carrier costs, three sets of accessorials, and header lines without double counting terminal handling that both the ocean carrier and the drayage carrier bill for separately. The FMS resolves that by making the leg the cost aggregation boundary and the shipment the total roll up.

The Integrations That Make Multi-modal Actually Work

Integrations are what convert a multi-modal FMS from a spreadsheet with mode tabs into a working operations platform. The integration surface breaks into four categories.

Ocean Carrier and Terminal Integrations

• Ocean carrier booking and tracking APIs. Direct integration with the top 15 to 20 ocean carriers, plus INTTRA and GT Nexus for the smaller lines.
• Port and terminal feeds. Direct or PCS mediated feeds for the top 20 container ports globally; eModal, TOPS, and Advent for the US West Coast terminals.
• AIS vessel position provider. One or two of MarineTraffic, FleetMon, VesselFinder.

Air Carrier Integrations

• Cargo iQ or IATA ONE Record for air. Standardised milestone tracking across most major airlines.
• CIMP FSU message ingestion. Legacy air cargo messaging still in use by many airlines and GHAs.

Ground and Drayage Integrations

• LTL carrier APIs. The top 10 to 15 US LTL carriers for line haul and pickup dispatch.
• Drayage TMS partners. Native or API integration with common drayage platforms so the ocean out gate to consignee handoff is one workflow.
• Fleet telematics. ELD providers (Motive, Samsara, Geotab) for real time GPS on managed fleets.

Customs and Documents

• ISF, AES, and Japan AFR filing. Native filings for the US and Japan lanes that most Asia to US and US to Asia forwarders live on.
• CBAM and ICS2 pass through. Data capture at booking for EU import lanes; filing typically via customs broker partner.

How to Evaluate a Multi-modal Freight Management Platform

The buyer question is not "does it support all three modes" (every mature platform will nod yes on the demo call). The buyer question is a four part live test the ops team runs during the trial.

A platform that passes all four tests on the trial data set is a real multi-modal FMS. A platform that hedges on any of the four (usually the stitched tracking test or the mode swap test) is a multi-module tool with mode silos.

Multi-modal vs Multiple Single Mode Platforms: The ROI Case

The ROI case for consolidating three single mode systems into one multi-modal FMS lands in three places.

First, ops rekeying. A three system stack (ocean TMS plus air TMS plus ground TMS) forces the ops team to re enter shipment header data (shipper, consignee, commodity, references) into each system per booking. A consolidated FMS enters it once. On a mid market forwarder handling 500 multi-modal shipments per month, the rekeying saving is typically 40 to 60 percent of the ops team's data entry hours, redirected to exception management.

Second, integration cost. Every single mode system needs its own carrier, terminal, and telematics integrations; a consolidated FMS shares the integration layer across modes. The cost avoided is typically 20 to 30 percent of the annual integration budget, depending on carrier mix.

Third, customer facing surface. A three system stack produces three tracking pages, three invoice formats, and three customer support workflows. A consolidated FMS produces one branded customer portal with per shipment status across modes. The customer facing consolidation is what typically wins RFPs against forwarders still running split stacks.

How Multi-modal Shipment Tracking Works Across Carriers

Multi-modal shipment tracking is the customer facing view of the unified tracking data stitched across the four data sources. The shipper portal shows one timeline per shipment: booked, picked up at origin, at origin port or airport, on vessel or flight (with map view if AIS or flight position is available), at destination port or airport, out for delivery, delivered.

Where the shipment crosses modes, the timeline shows one badge per leg (Ocean, Rail, Air, Ground) with the carrier name on each. The customer clicks a leg to expand the underlying milestone detail (vessel and voyage for ocean, MAWB and flight for air, PRO or trip for ground). Notifications fire on defined milestone events (Arrived Destination Port, Out for Delivery, Delivered) via email, SMS, or webhook to the customer's own system.

The Bottom Line for Multi-modal Freight Forwarders

Multi-modal freight management software in 2026 is not a feature list debate. It is an architecture question: does the platform hold every modal leg on one shipment record, issue one house bill and one master bill per leg tied to that record, stitch carrier plus terminal plus AIS plus trucking data into one milestone stream, and support mode switching mid shipment without opening a new file. Platforms that pass those four tests are the ones forwarders consolidate onto; platforms that fail one or more of the four are the ones that get displaced when the split stack finally breaks under volume.

For forwarders still running three single mode systems, the practical next step is not a full replatform. It is the four part trial test on a consolidated FMS with a live door to door shipment: run the cross mode booking, the stitched tracking, the mode swap, and the landed cost roll up on a real customer file, and see whether the ops team completes the workflow in one system without touching the other two.

Frequently Asked Questions

How does freight management software handle multi-modal shipments across air, ocean, and ground?

Multi-modal FMS handles all three modes on one shipment record with a shared header and mode as a leg attribute. The system supports ocean with FCL and LCL bookings and MB/L plus HB/L documents, air with MAWB and HAWB, and ground with truckload dispatch or LTL PRO tracking. Every leg carries its own buy and sell cost lines, its own carrier, and its own milestone stream, all stitched into one shipment timeline. The output is one invoice per shipment with per leg cost breakdown, one document pack, and one tracking view for the customer.

How does an FMS stitch carrier, terminal, AIS, and trucking data into one shipment record?

The FMS ingests four data sources per multi-modal shipment: carrier booking milestones (via EDI 315 or carrier APIs), terminal gate moves (via port community system or direct terminal feeds like eModal), AIS vessel position for the ocean leg, and trucking telematics for the ground legs (ELD providers like Motive and Samsara or drayage TMS integrations). Every event is tagged with the leg it belongs to, joined to the shipment number and container number, and normalised to a canonical event name. The result is one deduplicated milestone stream per shipment, with a leg badge on each event and the vessel position overlaid on a map view for the ocean segment.

Can one FMS platform handle house bills for both air and ocean shipments in the same record?

Yes. A door to door move that combines ocean and air (for example ocean main leg with air express last mile) issues one HB/L for the ocean leg and one HAWB for the air leg, both tied to the same shipment record. Both house bills reference the shipment number and both carry the master bill (MB/L for the ocean carrier, MAWB for the airline) of the underlying carrier. The shipment record shows both documents in one document pack, so ops staff pull whichever is needed without switching systems.

How does the platform handle an air to ground handoff for first mile and final mile trucking?

The air leg carries the MAWB, flight number, and airport codes; the truck first mile and truck final mile each sit as their own ground legs on the same shipment record. The FMS pushes the airline "freight available" milestone at the destination station into the final mile dispatch tool automatically, so the driver appointment window opens when the freight is actually recoverable. Similarly on origin, the pickup appointment window closes at the airline cargo cutoff time. Both handoffs remove the manual watch on the airline import status that ops teams otherwise have to run in a separate browser tab.

How does ocean to rail intermodal work in a multi-modal FMS?

Ocean to rail intermodal is modelled as three legs on one shipment: ocean leg (Shanghai to Long Beach, MB/L and HB/L), rail leg (Long Beach to Chicago intermodal ramp, rail bill of lading), truck leg (Chicago ramp to consignee, drayage dispatch). The container number is the join key across the three legs. The FMS ingests rail milestone data from the rail carrier (BNSF or UP in the US) and from the intermodal marketing company that booked the rail leg, and it stitches those events into the same tracking stream as the ocean AIS position and the drayage GPS.

How does an FMS handle an air to last mile trucking handoff for express shipments?

Air express shipments that stop at a destination hub (rather than door to door delivery) get modelled as an air leg (integrator to hub) followed by a ground leg (hub to consignee). The integrator's tracking number covers the air leg; the FMS attaches the final mile drayage or trucking tracking to the same shipment record for the ground leg. The customer portal shows both tracking streams in one timeline so the customer does not see "delivered" on the express tracker followed by a silent gap until the truck arrives.

How do forwarders switch from ocean to air within a single shipment record when there is a routing change?

The mode swap keeps the shipper, consignee, commodity, incoterm, and reference fields on the record, then closes the ocean leg cost lines (ocean freight, terminal handling, drayage) and opens air leg cost lines (air freight, airport handling, truck first and final mile). The MB/L is replaced by a MAWB, the ocean carrier is replaced by the airline as the leg carrier, and the shipment number and shipment history stay constant. The margin report reflects the ocean cost as sunk (or recovered via carrier claim) and the air cost as the new leg cost, so the customer invoice traces to the same shipment.

What counts as a multi-modal shipment in freight forwarding?

A multi-modal shipment is any move that uses more than one transport mode between origin and destination. The four most common patterns are ocean plus trucking (drayage), air plus trucking (first mile and final mile), ocean plus rail plus trucking (intermodal), and air express plus trucking final mile. The defining feature is that the shipment lives on one record with each mode as a leg, not on separate shipments per mode that need reconciliation.

Which freight management software supports true multi-modal booking across air, ocean, and ground?

GoFreight supports multi-modal booking through a unified screen that handles FCL and LCL bookings, MAWB and HAWB, and truckload dispatch on one shipment record, so door to door moves stay as single records with multiple legs. The buyer test is whether the platform holds one shipment number across ocean, air, and ground legs with mode as a leg attribute (not three separate records), and whether the tracking, cost, and document views span all legs.

How does a multi-modal freight platform allocate costs across modes for landed cost calculation?

The platform assigns buy and sell cost lines per leg (ocean freight and terminal handling on the ocean leg, air freight on the air leg, drayage and accessorials on the ground legs), then aggregates them into shipment totals. Non transport charges such as duty, insurance, brokerage fee, and warehousing attach as separate lines on the shipment header, not on a leg. The landed cost quote to the shipper is the sum of every leg cost line plus header lines, per unit or per SKU, and the margin report subtracts total buy from total sell across the same source data.

Can multi-modal FMS software track a single container through ocean and trucking legs with one milestone stream?

Yes. Container number is the join key across cross mode legs on the same shipment. The platform ingests the ocean carrier's container events (Gate In, Loaded on Vessel, Discharged, Available at Terminal, Out Gate) and the drayage carrier's GPS pings and appointment status, then merges both into one milestone timeline keyed on container number. The customer sees the container move from vessel to yard to truck to consignee dock in one view without reconciling two systems.

What is the difference between multi-modal, intermodal, and combined transport in an FMS context?

Multi-modal is the broad term for any shipment using more than one transport mode. Intermodal is a subset that specifically means the same intermodal container moves across modes without cargo transfer (typically ocean to rail to truck). Combined transport is the European term for a move with a rail or inland waterway main leg plus truck legs at each end. All three sit under the same platform model: one shipment, multiple legs, mode as a leg attribute, container number as the cross mode join key where the same container moves.

Is there freight software that unifies MAWB and B/L in one shipment view?

Multi-modal FMS platforms hold Master Air Waybill (MAWB), House Air Waybill (HAWB), Master Bill of Lading (MB/L), and House Bill of Lading (HB/L) on unified shipment tables with mode as a record attribute. That model lets one operations team work across ocean and air on the same record without switching between mode specific screens, and it lets the customs filings (ISF, ACAS, ICS2) key correctly to the underlying house bill for each leg.

Keep Reading

• Common Challenges in Freight Forwarding Operations 2026: The Top 10 Ops Pressures
• Air Freight Software Solutions: 2026 Buyer Guide for Air Cargo Forwarders
• Freight Tracking Software Comparison 2026: Choose the Right Platform