A modern freight forwarder rarely moves cargo end to end on a single mode. A shipment quoted as ocean can involve trucking at origin, an ocean main leg, drayage at destination, and rail bridging in the middle. An air quote often involves a truck first mile to the airport, an air main leg, and a final mile ground delivery. Managing these shipments across separate systems for air, ocean, and ground is the largest source of double entry, missed handoffs, and blind spots in a forwarder operation.
Multi-modal freight management software solves this by holding the shipment on a single record from booking to invoicing, no matter how many modes touch it. The platform models each leg with the routing, carrier, milestones, and documents that mode requires, then rolls the legs up into one shipment view for operations, one status view for the customer, and one financial view for accounting.
This guide explains what multi-modal freight management software actually is, how it handles air, ocean, and ground shipments in one system, the booking model, the house bill and master bill logic across modes, the mode switching workflows a forwarder should look for, cost allocation for landed cost, and the return on investment against running separate platforms per mode.
Multi-modal freight management software is a platform that manages freight forwarding shipments across multiple modes of transport (air, ocean, and ground) inside a single shipment record and a single data model. Where a mode specific TMS handles only air, only ocean, or only trucking, a multi-modal platform holds every mode on the same record and lets a forwarder book, track, document, and invoice a shipment regardless of which mode or modes it uses.
The technical definition is a shipment centric platform where the shipment record is the primary entity, the mode is an attribute of the record (or of each leg within the record), and every downstream workflow (tracking, documents, billing, reporting) reads from that shared record. A forwarder does not open a different system to look up an air shipment versus an ocean shipment. The same record view, the same status timeline, and the same billing screen serve both.
A single mode TMS is optimized for one mode, typically trucking (truckload TMS) or ocean (NVOCC platform). It excels within that mode but forces the forwarder to keep separate systems for the other modes, then reconcile shipments across them at the customer or accounting level. That reconciliation is where operations lose time and money.
A multi-modal platform inverts the model. Instead of one mode per platform, one platform holds every mode, and the mode becomes a filter, not a system boundary. A shipment routed ocean with drayage at destination is one record. A shipment routed air with truck pickup at origin is one record. A shipment routed rail bridge in the middle of an ocean move is one record with three legs. Operations see the same shipment view no matter which combination of modes the shipment uses.
A multi-modal shipment is any freight forwarding shipment that uses more than one mode of transport between origin and destination. The most common patterns are ocean plus trucking (door to port to door), air plus trucking (door to airport to door), ocean plus rail plus trucking (inland North America and Europe intermodal), and air express plus trucking last mile. All four patterns share one operational feature: a single customer, a single quote, a single house bill of lading or air waybill, and multiple carriers across multiple modes.
The core question a forwarder asks about a multi-modal platform is how one system handles the operational differences between modes. Air, ocean, and ground each have their own booking workflow, milestone set, document set, and carrier connection type. A well built multi-modal platform models each mode natively while keeping the shipment record shared.
For ocean, the platform handles FCL and LCL bookings, master and house bill of lading generation, container tracking against SCAC and container number, and milestone events including cargo cut off, VGM cut off, gate in, loaded on board, ETD, ETA, gate out, and empty return. Ocean carrier and NVOCC integrations pull the milestones directly from carrier tracking feeds. Documentation includes bill of lading, arrival notice, delivery order, and container release. This is the workflow that dedicated Ocean Freight Management Software handles for both import and export lanes inside the same shipment record.
For air, the platform handles master and house air waybill generation, flight tracking against airline and flight number, and milestone events including received at origin, on hand for departure, uplift confirmed, ATD, ATA, arrived at destination, cleared customs, and delivered. Air carrier and consolidator integrations pull flight and AWB status. Documentation includes air waybill, cargo manifest, and dangerous goods declaration where applicable. On a multi-modal platform, air runs as its own mode on the same record structure as ocean, so a forwarder handling both modes uses the same booking screen and the same tracking timeline. This is the workflow that Air Freight Management Software handles inside the same platform.
For ground, the platform handles truckload and less than truckload bookings, pickup and delivery appointments, driver and equipment assignment, and milestone events including tender accepted, arrived at pickup, loaded, in transit, arrived at delivery, and delivered. Ground carrier integrations pull tracking from carrier APIs or ELD feeds where available. Documentation includes bill of lading, proof of delivery, and dray receipt for containerized ground moves. Ground on a multi-modal platform covers both standalone trucking shipments and the pre carriage or on carriage legs of an air or ocean shipment on the same record.
What ties air, ocean, and ground together is the shared data model. A shipment on a multi-modal platform has one shipment number, one customer, one consignee, one origin, one destination, one billing block, and one set of documents. What varies by mode is the leg structure: the routing carrier, the milestone codes, and the document types applicable to that leg. Because the shipment record is shared, a status change on any leg updates the customer view immediately, without an integration between separate systems.
The booking layer is where multi-modal either succeeds or exposes itself as a stitched product. On a true multi-modal FMS, one booking screen serves every mode. The operator picks the mode (or modes, for door to door), and the screen surfaces the correct fields, carriers, rate cards, and milestone templates for that combination. The customer, shipper, consignee, commodity, and quote data enter once and drive every downstream leg.
For ocean, the booking screen surfaces FCL container types (20GP, 40GP, 40HC, reefer, flat rack), LCL cubic meters and chargeable weight, sailing schedule search against the origin and destination port pair, and rate lookup against ocean contracts. For air, the same screen switches to gross weight and chargeable weight (whichever is higher), volumetric ratio, airline lookup by origin and destination airport, and rate lookup against air tariffs. For ground, the screen shows equipment type (dry van, reefer, flatbed, drayage chassis), pickup and delivery windows, and rate lookup against trucking contracts or spot lanes.
Multi-modal booking means one booking action can create a shipment that spans more than one mode. A door to door quote booked in a single flow attaches the trucking pickup, the ocean or air main leg, and the trucking or drayage delivery to one shipment number. There is no separate booking per mode. Operations, customer service, and accounting see the whole shipment on one screen from the moment it is booked.
The master and house bill logic is the same conceptually across modes but uses different document types per mode. A multi-modal FMS handles both, on the same shipment view, without a separate module per mode.
| Mode | Master Document | House Document |
|---|---|---|
| Ocean | Master Bill of Lading (MB/L) issued by the ocean carrier or NVOCC | House Bill of Lading (HB/L) issued by the forwarder to the shipper |
| Air | Master Air Waybill (MAWB) issued by the airline | House Air Waybill (HAWB) issued by the forwarder or consolidator |
| Ground | Master trucking BOL or dispatch order for the underlying carrier | House trucking BOL issued by the forwarder for the shipper leg |
On a multi-modal FMS, the shipment view unifies the master and house bill data regardless of mode. A single shipment record shows the HB/L number and the MB/L number for an ocean move, and on the next record it shows the HAWB and MAWB for an air move, using the same layout. When a forwarder consolidates multiple house bills onto a single master bill (typical on both ocean LCL and air consolidations), the platform links them with a many to one relationship on the same shipment table.
The practical benefit of unified MAWB and B/L on one shipment view is that a customer service rep looking up an air shipment and an ocean shipment for the same customer reads the two the same way. The document numbers change per mode, but the record structure, the party fields, the milestones, and the linked master bill relationship look identical. This is what lets a forwarder handling both air and ocean run one operations team instead of two.
Every multi-modal freight management platform should deliver these six capabilities against every mode it supports. If a platform advertises multi-modal but lacks one of the six, it is either a single mode TMS with a mode field added or an integration layer stitching separate systems together.
| Capability | What It Does Across Modes |
|---|---|
| Unified booking | One booking screen where the mode is selected and the platform surfaces the correct fields, carriers, and rate cards for that mode. |
| Cross mode tracking | A single tracking timeline that stitches ocean carrier milestones, air carrier milestones, and ground carrier milestones onto the same shipment record. |
| Mode agnostic documentation | Master and house documents (bill of lading for ocean and ground, air waybill for air) generated from the same shipment record without re entering shipper, consignee, or commodity data. |
| Consolidated billing | One invoice per shipment that captures every leg regardless of mode, with per leg cost breakdown for margin analysis. |
| Carrier integrations by mode | Ocean carrier and NVOCC APIs, airline and consolidator APIs, and ground carrier APIs feeding tracking, rates, and documents into the same shipment record. |
| Cross mode reporting | Margin, transit time, on time performance, and volume reporting sliced by mode, by lane, by customer, and by carrier from the same shipment table. |
The hardest workflow in freight forwarding is not the single mode shipment. It is the shipment that switches modes mid transit. A door to door quote often bundles trucking at origin, an ocean or air main leg, and trucking or drayage at destination. On separate platforms per mode, that shipment lives as three records with three sets of documents, three billing blocks, and no shared status timeline. On a multi-modal platform, it lives as one record with three legs.
An air freight shipment booked from an inland shipper to an inland consignee typically needs truck pickup to the origin airport and truck delivery from the destination airport. On a multi-modal platform, the shipment record holds the air waybill and the two truck bills of lading as three legs. The customer sees one status timeline. Operations dispatches the trucking legs from the same screen used to book the air.
An ocean container booked port to door needs drayage from the discharge port to the consignee door, with the empty container returned to the port after unload. On a multi-modal platform, the drayage leg attaches to the ocean shipment record, the drayage carrier gets the container release and dispatch from the same record, and the drayage milestones (gate out, arrived at delivery, delivered, empty return) roll into the shipment timeline.
An ocean container moving inland from a west coast US port to a midwest consignee uses intermodal rail for the main inland leg and drayage for the first and last mile. On a multi-modal platform, the shipment record holds the ocean leg, the rail leg, and the two drayage legs, each with the correct carrier and milestones, on the same shipment number.
Sometimes a customer or operations flags a routing change: a shipment quoted ocean must upgrade to air to catch a promotion window or recover from a delayed sailing. On a multi-modal FMS, the mode of the main leg is edited on the existing shipment record without opening a new file. The party and commodity data stay, the ocean carrier and MB/L are voided or marked cancelled, and the air carrier and MAWB are added as the new main leg. Cost lines from the ocean leg are closed and new air cost lines open on the same shipment for accurate margin capture. The customer sees the change on the same shipment number, not a new one.
The automation that makes mode switching workflows practical is triggered handoff. When an ocean container is confirmed gate out at the discharge port, the platform can automatically dispatch the drayage leg. When the air waybill is confirmed delivered to the destination airport, the platform can automatically release the final mile trucker. When a rail leg is confirmed loaded, the origin drayage leg can be marked closed. Building these triggers on a mode aware workflow engine is what Workflow Automation Software for Forwarders handles, so multi-modal shipments do not stall between legs waiting for a dispatcher to notice.
Landed cost is only accurate if every leg of a multi-modal shipment carries its own buy and sell cost, and the platform can roll those legs into one shipment total. On separate mode systems, the trucking cost sits in the trucking system, the ocean cost sits in the ocean system, and the landed cost calculation happens in a spreadsheet at month end, usually after margin has already been miscoded to a customer.
A multi-modal FMS models cost at the leg level. Each leg on the shipment carries a buy cost (what the forwarder pays the carrier) and a sell cost (what the forwarder bills the customer) for that mode. The shipment total rolls the leg costs into one aggregated view. Because the mode is captured on each leg, the platform can slice cost by mode within a shipment, by mode across a customer, or by mode across a lane, without an export to a separate reporting layer.
For landed cost calculation, the platform then attaches non transport charges (customs duty, insurance, handling, storage, demurrage, detention) to the shipment as additional cost lines. The landed cost is the sum of the leg costs plus the non transport charges, per shipment, exposed as a single field on the shipment record. When a customer requests a landed cost breakdown for a door to door move, the forwarder pulls it from the FMS without a spreadsheet build, because the shipment already holds the per leg and per charge detail.
The visible layer of a multi-modal platform is the shipment record. The layer that makes the shipment record possible is integrations. Every mode has its own carrier ecosystem, and a multi-modal platform is only as strong as its ability to connect to carriers across every mode without a bespoke integration project per carrier.
Ocean integrations cover container tracking APIs from major ocean lines, NVOCC systems, port community systems, and terminal operating systems for gate in and gate out data. Air integrations cover airline cargo APIs and consolidator platforms for AWB status and flight tracking, plus air waybill neutral generation via IATA e-AWB standards. Ground integrations cover trucking carrier APIs, dispatch platforms, ELD feeds where available, and drayage provider systems. Customs and compliance integrations cover ISF, AES, ACE, ENS, and mode specific pre arrival filings that ride on top of the shipment record.
Consolidating these integrations under one platform is the work that dedicated Freight Integrations Software for Forwarders handles, so the same shipment record drives ocean carrier tracking, airline AWB status, trucking dispatch, and customs filings without a forwarder rebuilding carrier connections per mode.
Evaluating a platform as truly multi-modal requires looking past the marketing. Any platform can add a mode field to a shipment record. The evaluation is whether every downstream workflow respects the mode.
Forwarders often reach a multi-modal platform after outgrowing a stack of single mode systems: one for ocean, one for air, sometimes a third for trucking, plus a shared accounting layer that reconciles them. The ROI comparison is not just license cost. It is the operational drag of running the stack.
| Dimension | Multiple Single Mode Platforms | Single Multi-modal Platform |
|---|---|---|
| Shipment record | One record per mode, per shipment | One record per shipment across every mode |
| Customer data | Re entered per system | Master customer file used by every mode |
| Tracking | Separate portal per mode | One tracking timeline per shipment |
| Documents | Generated per system, reconciled manually | Generated from shared shipment record |
| Invoicing | Invoice per mode, consolidated at accounting layer | One invoice per shipment, per leg cost breakdown |
| Reporting | Per system, then merged in a spreadsheet | One data model, pivot by mode, lane, customer |
| Onboarding a new mode | Buy and integrate a new platform | Enable the mode and connect the carriers |
The ROI shows up in three places. First, on operations: the time an operator spends on a door to door shipment drops because there is no re entry between the ocean leg system and the trucking leg system. Second, on customer service: the customer sees one status view across every mode, which cuts inbound status inquiries. Third, on finance: one invoice per shipment with a per leg cost breakdown surfaces margin per leg, so the finance team can see which mode of a door to door move is losing money.
A platform marketed as multi-modal that generates a separate shipment number per mode inside the same system is not truly multi-modal. Ask to see the shipment record for an ocean plus drayage move and confirm it uses one shipment number, one bill of lading structure, and one billing block. If the vendor shows a linked pair of records instead of one record with multiple legs, the platform is a mode by mode system with a link table on top, and the operational drag of double entry stays.
Cross carrier, cross mode tracking is the single most requested capability from customers of a multi-modal forwarder. The customer wants one dashboard that shows every shipment regardless of mode, with the current status and the next milestone. Building that dashboard on a stitched stack of single mode systems requires a middleware layer that pulls status per platform and reconciles it. Building it on a multi-modal platform means the shipment table already holds every status.
The underlying tracking model is the same across modes: a shipment has a sequence of expected milestones, each milestone has an expected time and an actual time, and each milestone maps to a carrier event feed. What varies is the milestone set per mode. Ocean uses gate in, loaded on board, ETD, ETA, gate out. Air uses received, on hand for departure, uplift, arrived, cleared, delivered. Ground uses tender accepted, arrived pickup, loaded, in transit, arrived delivery, delivered. The multi-modal platform normalizes these into a common event schema so the tracking timeline reads the same way regardless of mode.
For containerized moves that cross ocean and trucking legs (port to door drayage), the tracking stream stays continuous on the same container number. Ocean carrier events populate the ocean leg (gate in origin, loaded, ETA, gate out destination), and the drayage carrier events continue on the same container (drayage dispatched, arrived at consignee, delivered, empty return). The customer sees one milestone stream keyed to the container, not two disconnected trackings.
A forwarder handling more than one mode at real volume needs a platform where the shipment record, the tracking timeline, the documentation set, the invoicing block, and the reporting layer are all mode aware but shared. Running separate systems per mode is a growth cap disguised as an integration problem. A multi-modal platform removes the cap by unifying the operational core and letting each mode contribute its milestones, documents, and carriers to the same shipment.
The forwarders that succeed on multi-modal are the ones that treat mode not as a system boundary but as an attribute of the shipment. The forwarders that stay on separate systems per mode pay the price on every door to door move, every cross mode status inquiry, and every reconciliation between the ocean invoice and the trucking invoice.
Ship Faster. Scale Smarter. See how GoFreight lets forwarders manage air, ocean, and ground shipments on one shipment record, with cross mode tracking, unified billing, and mode switching workflows built in. Request a GoFreight Demo →
Multi-modal freight management software handles air, ocean, and ground shipments on a single shipment record with a shared data model. The platform models each mode natively (ocean with FCL and LCL bookings and bill of lading, air with master and house air waybills and flight tracking, ground with truckload and less than truckload bookings and driver dispatch) but stores all three on the same record structure. Operations sees one shipment view, the customer sees one tracking timeline stitched from every carrier feed, documents generate from shared shipper and consignee data, and one invoice per shipment breaks cost down per leg regardless of mode. Mode switching workflows handle shipments that use more than one mode, so a door to door quote with trucking plus ocean plus drayage lives as one record with three legs, not three separate records.
True multi-modal freight management software is a platform where one booking screen serves ocean, air, and ground, one shipment record holds every mode, and every downstream workflow (tracking, documents, invoicing, reporting) is mode aware but shared. GoFreight is built to this pattern, with FCL and LCL booking, master and house air waybill generation, truckload and less than truckload dispatch, and door to door shipments modeled as one record with multiple legs. The evaluation test is to book a shipment that uses more than one mode in the demo and confirm the platform keeps it on one shipment number, one document set, and one billing block.
Yes. A multi-modal FMS unifies the house bill logic across modes: the House Bill of Lading (HB/L) for ocean and the House Air Waybill (HAWB) for air both attach to the same shipment record, in the same layout, generated from the same shipper, consignee, and commodity data. When multiple house bills are consolidated onto a single master (typical on both ocean LCL and air consolidations), the platform links them with a many to one relationship on the same shipment table. A customer service rep looking up an air house bill and an ocean house bill reads them the same way inside the same record view.
When a shipment quoted ocean needs to upgrade to air (for a promotion window, a delayed sailing recovery, or a customer expedite request), a multi-modal FMS lets the mode of the main leg change on the existing shipment record without opening a new file. The party, commodity, and quote data stay, the ocean carrier and Master Bill of Lading are voided or marked cancelled, and the air carrier and Master Air Waybill are added as the new main leg. Cost lines from the ocean leg close and new air cost lines open on the same shipment for accurate margin capture. The customer sees the change on the same shipment number, not a new one.
A multi-modal shipment is any freight forwarding shipment that uses more than one mode of transport between origin and destination. The most common patterns are ocean plus trucking (door to port to door), air plus trucking (door to airport to door), ocean plus rail plus trucking (inland North America and Europe intermodal), and air express plus trucking last mile. All four patterns share one operational feature: a single customer, a single quote, a single house bill of lading or air waybill, and multiple carriers across multiple modes.
Yes. A multi-modal FMS unifies MAWB (Master Air Waybill) and MB/L (Master Bill of Lading) on the same shipment view by holding both document types on the same shipment table with the mode as an attribute of the record. A forwarder handling an air consolidation and an ocean consolidation for the same customer sees both shipments in the same list, with the same layout, and the master document number populated with either the MAWB or the MB/L depending on the mode. The unified view is what lets a forwarder run one operations team across air and ocean instead of a team per mode.
A multi-modal FMS models a door to door shipment that crosses modes as one shipment record with a sequence of legs. A shipment with ocean main leg, drayage from the discharge port to a consolidation hub, and air express last mile to the final consignee lives as one shipment number with four legs (origin trucking if applicable, ocean, drayage, air express). Each leg carries its own carrier, milestones, documents, and cost lines. The customer sees one tracking timeline stitched across every mode, one invoice with per leg cost breakdown, and one point of contact for status inquiries.
Multi-modal is the broadest term: any shipment that uses more than one mode of transport, whether the cargo transfers containers, is deconsolidated, or moves as loose freight. Intermodal specifically means the cargo moves in a single container that transfers between modes without being unloaded (typically ocean container to rail to truck). Combined transport is a European term for a multi-modal move where the main leg is rail or inland waterway and the pre carriage or on carriage is trucking, often with tax incentives attached. A multi-modal FMS supports all three by modeling the leg structure on the same shipment record, with the mode captured at the leg level.
A multi-modal FMS allocates cost at the leg level. Each leg carries its own buy cost (what the forwarder pays the carrier) and sell cost (what the forwarder bills the customer) for that mode. The shipment total rolls the leg costs into one aggregated view. For landed cost calculation, the platform attaches non transport charges (customs duty, insurance, handling, storage, demurrage, detention) to the same shipment as additional cost lines. The landed cost is the sum of the leg costs plus the non transport charges, exposed as a single field on the shipment record, so a customer requesting a landed cost breakdown for a door to door move gets it pulled from the FMS without a spreadsheet build.
Yes. A multi-modal FMS tracks a container across ocean and trucking legs as one continuous milestone stream keyed to the container number. Ocean carrier events populate the ocean leg (gate in origin, loaded on board, ETD, ETA, gate out destination), and the drayage carrier events continue on the same container (drayage dispatched, arrived at consignee, delivered, empty return). The customer sees one timeline for the container from origin gate in to empty return, not two disconnected trackings that a customer service rep has to reconcile.