Quick Overview
Carrier contract management software helps freight forwarders organize negotiated rates, amendments, validity dates and conditions for quoting. VelocityOS supports this work through centralized rate data, version control and pricing governance. Define approval responsibilities, renewal procedures and integration scope so teams know which rates are ready to use.
Turn negotiated terms into usable pricing data
A signed agreement or supplier spreadsheet is only the starting point. Pricing teams need to know which rates apply, what the charges include and whether an amendment changes the original offer.
Bring contract rates into a controlled workflow that connects the supplier source with the information used by sales and operations.
Keep these details together:
| Contract information | Why it matters |
|---|---|
| Carrier, agent and contract reference | Identifies the source and agreement |
| Version or amendment reference | Distinguishes the current terms from earlier records |
| Origin, destination and routing | Defines where the rate applies |
| Mode, equipment and service | Prevents selection of an unsuitable rate |
| Commodity and customer restrictions | Identifies eligibility conditions |
| Effective dates and expiry | Establishes the applicable pricing window |
| Surcharges and accessorials | Preserves the complete charge structure |
| Review and publication status | Shows whether pricing is ready for use |
Keep the source agreement available for reference. Structured pricing fields should preserve its conditions and highlight anything requiring interpretation.
Control contract versions and amendments
VelocityOS’s rate-management workflow supports multiple rate versions and audit history, helping teams trace changes to the information behind a quote.
Use a consistent process when a carrier issues an amendment:
- Identify the agreement and version being changed.
- Record the amendment source and effective conditions.
- Compare the affected rates, charges and restrictions.
- Review unresolved differences.
- Approve the replacement pricing before publication.
- Retain the previous version for historical reference.
An amendment may affect only selected lanes or charges. Avoid replacing unaffected terms simply because a new file has arrived.
For the wider pricing workflow, explore VelocityOS rate management.
Manage effective dates, expiry and renewal
Contract dates need to reflect the conditions under which a rate can be used. Depending on the agreement, applicability may depend on booking, cargo receipt, departure or another specified event.
Record the relevant date basis rather than relying on a generic expiry field alone. Base freight and individual surcharges may also have different validity periods.
Plan renewal reminders around the work required
Assign an owner to review approaching expiries and obtain updated terms. Allow time for supplier discussions, data preparation and approval before replacement rates are needed.
Define:
- When the responsible person should be notified.
- Which agreements or rate groups require review.
- What happens if replacement pricing has not arrived.
- Who approves renewed rates.
- How sales teams are informed of changes.
Confirm whether reminders will run in VelocityOS or a connected task or CRM system during implementation. Receiving a reminder does not extend a rate’s validity.
Preserve surcharge and accessorial conditions
A base rate cannot explain the complete cost of a shipment. Additional charges may apply by lane, equipment, weight, volume, shipment or service event.
| Charge detail | What to record |
|---|---|
| Supplier description | Original charge name and reference |
| Standardized category | Internal classification used for comparison |
| Calculation basis | Per container, kilogram, shipment or other unit |
| Currency and minimum | Applicable currency and minimum-charge rule |
| Inclusion | Included in another charge or separately payable |
| Applicability | Relevant lane, service, equipment or condition |
| Validity | Effective period and amendment reference |
Standardizing a charge name should not remove its original meaning. Charges with similar labels may have different inclusions or calculation rules.
Keep unresolved or missing charges visible until they are clarified.
Apply lane, commodity and customer rules
A negotiated rate may be limited to a specific port pair, equipment type, commodity, customer account or service arrangement.
Retain these conditions alongside the rate so the pricing team can check eligibility before an offer is prepared.
For each restricted rate, establish:
- The conditions that make it applicable.
- Which fields are checked automatically.
- Which conditions require manual review.
- Who may approve an exception.
- How the decision is recorded.
A commercially attractive rate should remain unavailable for a shipment that does not meet its conditions unless an authorized alternative has been confirmed.
Review and approve rates before publishing
Uploading a file should begin the review process. It should not automatically make new contract pricing available to every quoting user.
Use the following approval model when configuring the workflow:
| Stage | Purpose | Responsible role |
|---|---|---|
| Received | Register the supplier file or update | Procurement or pricing |
| Prepared | Map rate fields and preserve source conditions | Rate administrator |
| Checked | Investigate missing information and conflicting values | Pricing reviewer |
| Approved | Confirm the commercial interpretation and permitted use | Authorized approver |
| Published | Release the approved rates to the intended users | Authorized publisher |
| Superseded or expired | Retain history while ending routine use | Contract owner |
These are recommended workflow stages; their implementation depends on the configured system.
Require human approval before publishing imported or AI-extracted contract rates. Confirm who can upload, approve and publish, and test that users cannot bypass the agreed controls.
Compare carrier offers before procurement decisions
Carrier contract management supports procurement by making offers easier to compare on the same basis.
Before selecting an option, align:
- Movement scope and routing.
- Equipment or cargo requirements.
- Charge inclusions and exclusions.
- Currency and calculation basis.
- Validity and service conditions.
- Relevant capacity or allocation commitments.
- Restrictions and unresolved information.
A lower base rate may carry additional charges or conditions that change the decision.
Software can organize the evidence for freight rate negotiation, including previous terms and amendment history. Negotiation outcomes and supplier commitments still require confirmation by the responsible commercial team.
Use the freight rate procurement checklist to prepare comparable supplier offers before approval.
Import spreadsheets and connect approved rate sources
VelocityOS supports rate ingestion through spreadsheets and configured integrations. The available data depends on the source and connection.
Spreadsheet ingestion
Prepare supplier files for mapping into consistent rate fields. Review location identifiers, equipment, units, currencies and dates before publication.
Check duplicate records and conflicting versions. Preserve supplier notes that cannot be represented accurately in a structured field.
See the rate-sheet upload guide for the preparation workflow.
API-connected rates
Keep API-sourced rates identifiable by provider, retrieval time and applicable conditions. An API response should not silently overwrite a negotiated contract record.
Agree which source takes precedence when information differs and how changes reach the pricing team.
Confirm authenticated access to negotiated rates, supported fields and update behavior for each connection.
Keep a traceable history behind each quote
When a customer or operations team questions a charge, pricing should be able to identify the rate source and version used.
Define the history your process needs to retain:
- Source file or connected provider.
- Import and amendment references.
- Changes to rates or conditions.
- Reviewer and approval record.
- Publication date.
- Relationship to the customer quote.
Verify these records during implementation, including how they can be retrieved or exported.
Connect approved pricing with quote management so the customer offer reflects the reviewed rate conditions.
Example: a surcharge amendment before renewal
The following scenario is hypothetical.
A carrier sends an amendment affecting a surcharge on selected lanes. The main contract remains active, but the revised surcharge applies under a different effective condition.
| Step | Pricing-team action |
|---|---|
| Identify the amendment | Match the supplier update to the correct agreement |
| Determine the scope | Identify affected lanes, equipment and applicable dates |
| Prepare the revision | Update the charge while retaining unchanged contract terms |
| Review open offers | Assess which quotes require commercial review under their terms |
| Approve publication | Confirm the interpretation before releasing revised pricing |
| Preserve the record | Retain the original version and amendment history |
| Plan renewal | Track the main contract’s separate renewal deadline |
This workflow prevents a single amendment from being treated as an unexplained replacement of the entire agreement.
Review your carrier contract workflow with VelocityOS
Bring a representative contract rate sheet, an amendment and a customer quote to a demonstration.
Review version handling, validity conditions, charge mapping and approval responsibilities. Confirm renewal reminders, publication controls and connected-system requirements for your implementation.
Measure the time required to prepare and approve a revision, resolve exceptions and identify the source behind a quote.