Ocean freight software helps forwarders connect sea-freight rates, customer offers, bookings, documents and shipment updates. Evaluate FCL and LCL separately: FCL requires equipment, container and carrier-booking relationships, while LCL also needs the individual consignment, consolidation and destination-availability information relevant to its service. Test which records and events the product manages itself and which depend on a TMS, carrier, consolidator or other provider.
Answer in brief: Use one real FCL job and one real LCL job. Follow each from source rate to customer quote, booking handoff, document change and destination event. Check that the software distinguishes vessel arrival from cargo release or collection readiness.
What does ocean freight software do?
Ocean freight software organizes the commercial and operational information needed to manage sea shipments.
For a forwarder, that information may begin with a carrier tariff or customer enquiry and continue through quote approval, booking, transport documents, destination coordination and delivery.
Some products focus on a particular task, such as rate management or container visibility. Others provide a broader forwarding workflow. Identify which activities the proposed platform handles directly and which depend on your TMS, accounting system or external services.
A useful evaluation follows the shipment from its first pricing request to its final operational handoff.
Ocean freight software requirements: FCL versus LCL
Full container load and less than container load shipments require different pricing inputs and operational structures.
| Requirement | FCL considerations | LCL considerations |
|---|---|---|
| Pricing basis | Container size, type and applicable service conditions | Weight or measurement basis, minimums and tariff rules |
| Cargo information | Equipment requirements, cargo weight and loading constraints | Package count, dimensions, weight and handling requirements |
| Charges | Main carriage, terminal charges, documentation and applicable inland costs | Main carriage, consolidation, CFS handling, documentation and local charges |
| Shipment structure | Booking and container references | Individual consignments and their relationship to a consolidated movement |
| Operational handoffs | Container collection, gate-in, loading and destination collection | Cargo receipt, consolidation, deconsolidation and cargo availability |
| Exceptions | Equipment issues, rolled bookings and missed cut-offs | Cargo discrepancies, consolidation changes and delayed availability |
Confirm the actual tariff and service rules. The same charge label can have a different calculation basis or inclusion depending on the supplier.
Test FCL And LCL As Separate Workflows
| Workflow | Ask the vendor to demonstrate | Evidence to record |
|---|---|---|
| FCL rate eligibility | Select a container type, port pair, validity period, commodity condition and movement scope | Source tariff, applicable charges, exclusions and reason an ineligible option is rejected |
| FCL booking relationship | Relate the customer quote to carrier booking, container and shipment references | Which system creates each record and how changes are synchronized |
| FCL changes | Replace a rolled sailing with a new service or update equipment availability | New schedule source, customer impact, cost review and named owner |
| LCL rating | Apply weight/measurement rules, minimums, CFS and relevant origin and destination charges | Calculation basis for each line and what remains estimated |
| LCL consolidation | Link the individual customer consignment to the consolidated movement where the workflow requires it | House and master references where applicable, plus which party supplies updates |
| LCL availability | Distinguish vessel arrival, deconsolidation, holds, release and collection readiness | Event source, timestamp, remaining conditions and owner of next action |
Do not assume a quoted LCL total includes all destination services or that a reported vessel arrival makes cargo available for collection. Coverage of carrier and consolidator data varies by provider and integration.
Connect the ocean-freight workflow
Software should preserve the relationship between the customer request, quoted service and operational shipment.
| Stage | Information to capture | Check before proceeding |
|---|---|---|
| Customer enquiry | Ports, movement scope, cargo, equipment and required dates | Are the shipment requirements complete? |
| Rate selection | Carrier or agent, routing, charges, validity and restrictions | Is the rate applicable to this shipment? |
| Quote preparation | Sell price, inclusions, exclusions and expiry | Have the commercial terms been reviewed? |
| Booking handoff | Accepted quote, parties, cargo details and references | Are the booking requirements and service conditions confirmed? |
| Shipment execution | Documents, transport legs and milestone updates | What is confirmed, estimated or still outstanding? |
| Destination coordination | Discharge, availability, release and collection information | Which conditions remain before collection? |
| Completion | Delivery evidence and final cost information | Are outstanding charges and operational actions resolved? |
An accepted quote does not, by itself, establish confirmed carrier space or equipment. Keep commercial acceptance and booking confirmation distinct.
Manage ocean freight rates with their conditions
An ocean freight rate is more than a price between two ports. Its applicability can depend on equipment, commodity, customer eligibility, routing, validity and additional charges.
A useful rate record should preserve:
- Exact origin and destination.
- Supplier and service reference.
- FCL equipment or LCL calculation basis.
- Currency and charge units.
- Included and excluded charges.
- Effective dates and applicable booking or sailing conditions.
- Routing and transshipment information where provided.
- Restrictions, remarks and approval status.
Keep the original source available when interpreting an ambiguous condition. A blank charge field should not automatically be treated as an included or zero-cost service.
For detailed evaluation of pricing systems, see our freight rate-management software comparison.
Compare Ocean Offers With Different Charge Scope
Hypothetical evaluation: Two FCL offers appear for the same port pair and container type. One displays a lower ocean linehaul but leaves destination terminal charges outside the quoted scope. The other displays a higher linehaul with a different set of included charges and an earlier validity end date.
Ask the system to show the currency and unit of every charge, the original rate source, local charges, routing, validity and conditions. Normalize the offers to the same movement scope before presenting them to the customer. If a destination charge cannot be established, label it as unconfirmed instead of treating a blank field as zero.
For a deeper rate-system comparison, link to the freight rate management software comparison. Keep this guide focused on ocean-specific consequences of selecting and handing off a rate.
Compare contract, spot and connected rates consistently
Carrier contracts, agent quotations and API responses may describe different service scopes. Normalize the comparison before selecting the lowest displayed price.
Check whether each option covers the same equipment, ports, inland movements and local charges. Confirm that the relevant rate remains valid for the intended shipment.
A connected rate source can improve access to information, but available services and update frequency depend on the provider and integration.
Explore VelocityOS rate management for the product workflow.
Prepare ocean freight quotes with a clear scope
A customer should be able to understand what the offer covers and what remains subject to confirmation.
Include the movement scope, equipment or cargo basis, routing assumptions, applicable charges, exclusions and quote expiry. Identify estimates clearly, particularly when destination costs or inland arrangements remain unresolved.
For LCL, preserve the tariff basis and minimum charges. For FCL, identify the container type and any conditions that affect equipment or service availability.
When an offer changes, issue a clearly identified revision. Keep the accepted version connected to the booking handoff so operations can see what was agreed.
See freight quote management for templates, pricing controls and customer-offer workflows.
Use shipment visibility to identify the next action
Ocean shipment visibility should help the team understand what happened, what is expected next and who needs to act.
| Reported event | What it can establish | What it does not establish by itself |
|---|---|---|
| Container gate-in | The container reached the reported terminal handover point | Confirmation that it loaded on the planned vessel |
| Vessel departure | A departure was reported for the relevant service or shipment | Final delivery timing |
| Transshipment update | Progress through an intermediate connection | Confirmation of every onward connection |
| Vessel arrival | Arrival at the reported destination milestone | Cargo availability or release |
| Discharge | The container was reported unloaded | Completion of customs and carrier release requirements |
| Cargo availability or release | A particular collection or release condition has been met | Completion of all other holds or delivery arrangements |
Track event sources and timestamps. Separate estimated dates from actual events, and investigate missing updates before assuming the shipment has stopped moving.
Event-based visibility does not imply continuous GPS positioning of the cargo.
For the detailed workflow, see freight tracking and exception management.
Check What An Ocean Milestone Actually Confirms
Ask the vendor to display a real event feed for one of your shipping lines and identify its source, event time, location, shipment or container reference, and whether the event is planned, estimated or actual. Then test a transshipment change. Does the record update the next expected connection and notify the responsible team, or does it only display an altered ETA?
Also test the distinction between vessel arrival, discharge, customs status, carrier release, cargo availability and final delivery. None of these should be inferred solely from a different event. If LCL availability comes from a consolidator rather than the carrier feed, show how that source enters the record. DCSA’s container-shipping standards provide useful terms for discussing event definitions, but standards adoption does not guarantee that a particular carrier feed or shipment is covered.
Coordinate ocean-freight exceptions
An exception needs a responsible person and a next action.
For a rolled booking, confirm the revised service and assess the effect on the customer’s requirements. For a missing document, identify the document owner and the deadline it affects. For delayed cargo availability, establish the outstanding condition before arranging collection.
Keep the operational response connected to the shipment:
- Verify the source information.
- Identify the affected milestone or requirement.
- Assign responsibility.
- Record the next action and review time.
- Communicate confirmed information.
- Close the issue when its resolution is established.
Additional charges should be investigated against the applicable terms and supporting records. An arrival delay alone does not determine responsibility for every resulting cost.
Worked example: one FCL shipment through the software
The following example is hypothetical and does not represent a current carrier rate or schedule.
A customer requests a 40-foot dry container shipment from Shanghai to Barcelona, with separate onward delivery to an inland address.
| Step | What the team records | Why it matters |
|---|---|---|
| Define the request | Ports, delivery address, cargo, equipment and required timing | Establishes the complete service scope |
| Compare options | Carrier offers, routing, validity and local-charge coverage | Prevents comparison of unequal offers |
| Prepare the quote | Selected service, customer price, exclusions and expiry | Makes the commercial offer understandable |
| Confirm the handoff | Accepted version and booking requirements | Connects the offer to execution |
| Review an ETA change | Source, revised milestone and operational impact | Supports a useful customer update |
| Coordinate collection | Availability, required releases and inland arrangements | Avoids treating vessel arrival as collection readiness |
| Complete the record | Delivery confirmation and final cost review | Supports operational and financial closure |
The software evaluation should demonstrate these relationships, including what happens when an ETA or cost changes after the original quote.
Worked Example: An LCL Shipment With Delayed Availability
Hypothetical scenario, not a carrier schedule or live VelocityOS record: A customer requests LCL service from an origin CFS to a destination CFS. The cargo consists of six cartons. The consolidator’s tariff uses a weight-or-measurement basis and a minimum charge, with separate origin and destination items under the agreed scope.
- Build the offer: Capture carton count, dimensions, gross weight, CFS locations, tariff basis, minimums, local charges, exclusions and expiry. Label any destination amount that still needs confirmation.
- Accept and hand off: Preserve the agreed version and identify the individual consignment and consolidated movement references where applicable. Confirm the booking details separately.
- Follow the movement: A vessel arrival event is received. The shipment record does not mark the cartons as ready for collection on that event alone.
- Handle the exception: The destination CFS reports that deconsolidation or release is pending. Record the source, condition, expected next update and owner; inform the customer using confirmed information.
- Complete the job: Confirm cargo availability, collection or delivery and any final charge adjustments against the agreed scope.
In the demo, ask who supplies each update and whether the software handles the consignment relationship directly or receives it from the TMS or consolidator.
Ocean Freight Demo Scorecard
Score each test demonstrated, requires configuration, requires another system, or unsupported:
- Show FCL and LCL rates with their distinct calculation bases, conditions and validity.
- Compare two FCL offers with different local-charge inclusions.
- Rate an LCL consignment with a minimum charge and a separate CFS item.
- Preserve the customer quote, accepted version and operational booking confirmation as distinct records or states.
- Link the carrier booking, container and shipment references used for FCL.
- Show the individual consignment’s relationship to an LCL consolidation where applicable.
- Identify which system owns shipping instructions, transport documents and their revisions; demonstrate a correction.
- Display a real event with source and timestamp; test a rolled booking or delayed LCL availability.
- Show TMS and accounting handoffs, including failed-sync recovery and costs for required feeds or modules.
Ask the provider to demonstrate with your ports, carriers, consolidator, tariff and representative documents. Record coverage by partner and trade lane rather than assuming that a logo establishes the required integration.
Where VelocityOS fits alongside an ocean-freight TMS
VelocityOS’s published workflows connect rate management, quoting and operational visibility. The division of responsibilities depends on the implementation.
A forwarder may retain its TMS for shipment execution while using connected workflows for pricing, customer offers and access to selected updates. Define the authoritative system for shipment records, documents and financial information before implementation.
Review what VelocityOS can sync when planning the connection.
For a broader decision about retaining or replacing an operational system, use the transportation management software buyer’s guide.
Review the workflow using your own shipment
Bring a representative rate file, customer enquiry and ocean shipment to a demonstration. Include an exception, such as a revised booking, missing charge or delayed release.
Confirm the supported workflow, integration scope and information sources. Measure the effort needed to prepare an accurate quote, coordinate the handoff and resolve the exception.
See how VelocityOS Rate Management organizes rate sources and how Quote Management turns the selected scope into a customer offer. Ask the team to demonstrate your ocean carrier and LCL consolidator connections.
Frequently Asked Questions
FCL workflows need equipment, container and carrier-booking information. LCL workflows also need the applicable measurement basis, minimums, consignment and consolidation relationships, CFS charges and destination availability conditions.
No. Discharge, release, customs and CFS or terminal availability can be separate events. Check the conditions for the particular shipment and the source of each status update.
It depends on the provider and the work your TMS currently owns. Check bookings, documentation, customs-related data, financial records and integrations in a live demonstration. VelocityOS describes connected rate, quote and visibility workflows; confirm the implementation scope before deciding which system remains authoritative.
Compare the same equipment or LCL cargo basis, movement scope, routing, validity and charge inclusions. Keep missing or estimated origin and destination charges visible before choosing a customer-facing price.