Ocean Freight Software for Forwarders: Features and Buyer’s Checklist

What is ocean freight software?

Ocean freight software is a broad category covering tools used to price, sell, organize and monitor sea freight shipments.

Some products focus on carrier rates and customer quotations. Others manage shipment execution, documentation and financial records. Visibility platforms focus on shipment events, estimated arrival times and exceptions.

A product may cover several categories, but it is important to confirm where its responsibilities begin and end.

Rate software, operational TMS or visibility platform?

These categories overlap. A platform may combine rate management, quoting and visibility while connecting to an existing operational TMS.

The buying decision should reflect the work your team needs to complete, rather than whether a product describes itself as an all-in-one solution.

Ocean freight features to evaluate

1. FCL and LCL rate structures

FCL and LCL require different pricing logic.

For FCL, check whether the software distinguishes container quantities, equipment types, trade lanes and charge bases. A charge per container should not be treated as a charge per shipment.

For LCL, ask the provider to demonstrate volume- and weight-based calculations, minimum charges and separate origin and destination fees.

For example, assume an LCL tariff explicitly charges on the greater of cubic metres or metric tonnes, with a one-unit minimum. A shipment measuring 4 m³ and weighing 1.5 tonnes would use 4 chargeable units under that tariff.

Treat this as a test case, not a universal rule. The system must apply the actual supplier’s basis, minimums and rounding.

2. Contract and spot-rate validity

A searchable rate is only useful if it applies to the shipment.

Check whether the software records:

• The carrier, agent or co-loader providing the offer.
• Contract or spot-rate references.
• Origin, destination, routing and equipment.
• Effective and expiry dates.
• The event that determines validity, such as booking or departure.
• Commodity restrictions and other conditions.
• Amendments and the version used in a quotation.

Ask what happens when a carrier changes a rate after a customer quote has been sent. The software should help the team identify affected work without silently rewriting the original commercial record.

3. Origin charges, destination charges and surcharges

Comparing base ocean freight alone can produce the wrong result.

Test whether the software distinguishes:

• Charges included in the base rate.
• Additional mandatory charges.
• Conditional charges.
• Unconfirmed amounts.
• Origin and destination local charges.
• Different currencies and exchange-rate assumptions.

Every amount should retain its charging basis: per container, shipment, document, weight or volume.

An unknown destination charge should remain visibly unconfirmed. Treating it as zero makes an incomplete offer appear cheaper.

4. Quote creation and margin controls

The customer quotation should preserve the service scope while keeping internal buy costs and profit calculations appropriately restricted.

Evaluate:

• Customer-specific pricing rules.
• Markup versus gross-margin calculations.
• Approval requirements for exceptions.
• Quote validity and exclusions.
• Currency conversion.
• Version history.
• Customer-facing documents and acceptance records.

VelocityOS documents quote templates, approval controls, structured cost breakdowns, PDF and link sharing, and quote-status tracking in its quote management offering.

5. Booking handoff and document responsibilities

A customer accepting a quotation is not the same as a carrier confirming space.

The handoff into operations should preserve the accepted quote and create a clear record of what still needs confirmation.

Check how the software transfers:

• Customer and shipment references.
• Cargo description, quantities and equipment.
• Selected routing and service.
• Buy costs, sell charges and exclusions.
• Requested dates.
• Booking status.
• Document deadlines.
• Ownership of outstanding tasks.

The team also needs to know who supplies, checks, submits and approves each document. Software can organize these responsibilities, but the responsible parties still need to review the information.

6. Shipment milestones and exception handling

A useful visibility workflow tells the team what changed and what to do next.

Evaluate how the software handles milestones such as booking confirmation, gate-in, loading, departure, transshipment, arrival and delivery, where data is available.

For each update, check:

• Whether it is planned, estimated or actual.
• The source and time of the update.
• Which shipment or container it relates to.
• Whether it changes an operational deadline.
• Who owns the follow-up.
• Whether the customer needs an update.

Do not interpret milestone visibility as continuous GPS tracking. Ask providers to demonstrate actual data coverage and how missing or delayed updates appear.

VelocityOS describes shipment visibility and team coordination through its operations tower. Confirm the event sources and coverage required for your carriers and lanes.

7. Integration with your existing TMS

Before selecting another platform, decide which system should own each record.

For example, your commercial platform may own quotations while the TMS owns the operational shipment record. Both systems need agreed references and update rules.

VelocityOS documents connections for rates, bookings, shipment updates and documents through its TMS integration. Confirm the exact objects, direction of exchange and implementation scope for your existing system.

Illustrative shipment: from carrier rate to customer quote to operations

The following shipment, prices and references are hypothetical. They demonstrate a workflow, not a live carrier offer or a claim that every step is automatically available in a particular product.

Assume a customer requests shipment of one 40-foot dry container of ordinary, non-hazardous goods from Shanghai to Jebel Ali.

The requested service covers the ocean movement and the listed terminal and documentation charges. Inland transport, customs clearance, duties, taxes, insurance and contingent charges are excluded.

Step 1: capture the supplier offer

The pricing team records the supplier reference, equipment, route, validity conditions and charge bases. It checks that the planned shipment qualifies for the offer.

Step 2: create the customer quotation

Assume the forwarder applies a USD 300 commercial markup.

Customer selling price = USD 2,350 + USD 300 = USD 2,650

The quote includes the service scope, selling price, validity, exclusions and terms. Internal buy costs remain available to authorized staff.

The customer accepts quote Q-1042, version 2. The acceptance is stored against that version.

Step 3: hand the accepted work to operations

Operations receives the cargo details, accepted quote reference, selected offer, charges and requested routing.

The team submits the booking request. The shipment remains awaiting carrier confirmation until a confirmation is received.

Once confirmed, operations records the carrier booking reference, schedule and relevant cutoffs. Document tasks are assigned to named owners.

Step 4: manage a schedule change

Suppose the carrier changes the planned departure.

The operations team checks:

1. Whether the updated departure affects rate validity.
2. Whether documentation or terminal deadlines have changed.
3. Whether the customer’s delivery requirement is affected.
4. Whether an alternative service is needed.
5. Whether revised charges require commercial approval.

The original accepted quote remains traceable. Any commercial revision is recorded separately rather than silently replacing what the customer accepted.

Buyer’s checklist for an ocean freight software demonstration

Ask each shortlisted provider to use your own sample shipments.

• Calculate one FCL and one LCL shipment.
• Demonstrate included, additional and unconfirmed charges.
• Reject or flag an offer outside its validity conditions.
• Apply a customer-specific selling rule.
• Show the approval process for a pricing exception.
• Transfer an accepted quote into an operational workflow.
• Distinguish customer acceptance from carrier confirmation.
• Assign document tasks and deadlines.
• Process a changed schedule or missing milestone.
• Demonstrate a failed integration and its recovery.
• Explain subscription, setup, rate-loading, connector and support costs.

For a broader comparison of pricing capabilities and providers, use the freight rate management software comparison.