Skip to main content
GullySystem
Logistics

Order Management for Freight and transport companies

Track the accepted freight-service commitment through actual carrier acceptance and cargo-event reconciliation.

CRM

Does this function belong in your operation?

Use for ordinary road freight commitments where customer instructions, actual carriage and billing need shared shipment references.

The authorised shipper or service buyer accepts a defined load movement or arrangement service.

A freight order is a commitment to transport or arrange transport for a defined load carried for others. Record the actual service responsibility, shipper declaration and acknowledged carrier instruction before tracking physical pickup. Partial receipt, altered quantities and changed destinations keep their own evidence and approval. Booking closure should identify remaining goods, documentation or account disputes without treating cargo as stock sold by the operator.

Bring the records the workflow depends on.

  • Shipper, consignee and actual service buyer with change authority
  • Declared load and handling-unit information with source
  • Accepted lane or spot-service terms and performing-carrier responsibility
  • Pickup instructions, carrier acknowledgement and event evidence

Outputs to check

  • Accepted freight order and versioned instruction history
  • Carrier acceptance and physical pickup or delivery references
  • Partial-load, missing-document and unresolved-account action list

Follow the order management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Record the accepted load

    Identify the service obligation and cargo reference. Keep declared units, dimensions and handling requirements distinguishable from actual observations.

  2. 2. Confirm the performing arrangement

    Record whether the business carries the load or the named outside carrier has accepted it. Retain unconfirmed equipment and site requirements as unresolved conditions.

  3. 3. Record actual pickup

    Link physical receipt or loading evidence and actual counts. A consignment number or issued booking document does not itself transfer custody.

  4. 4. Follow partial or changed work

    Retain the portion collected or delivered and the remaining load. Obtain the proper customer instruction and carrier decision for changed destinations or additional service.

  5. 5. Reconcile completion and open matters

    Match the delivery evidence with the accepted shipment and preserved exceptions. Pass proposed billing inputs while leaving missing units, documents and disputed charges assigned.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Freight booking coordinator

Keeps the accepted customer instruction and actual carrier acceptance aligned without assuming the same party owns both decisions.

Pickup and delivery evidence owner

Provides sourced cargo-event records and identifies observed differences from the declared or expected load.

Shipment reviewer

Reconciles partial progress and unresolved documentation before approving the recorded operational outcome.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Carrier has not acknowledged the load

Keep capacity pending and assign follow-up rather than describing the transport as arranged.

Only part of the declared load is collected

Record actual units and the remaining commitment with its authorised next action.

Consignee refuses or cannot receive freight

Preserve the attempted delivery and cargo custodian, obtaining a reviewed instruction before recording a different destination or return.

Actual cargo requires an unaccepted service

Hold the scope decision with the responsible parties rather than silently extending capability or updating the declared description.

Can this work independently?

Orders can be maintained from accepted shipper instructions and entered carrier records. Operational acceptance belongs to the actual transport provider; site and cargo requirements need the responsible review. Event reports supply evidence and accounts decides charges. Tracking and electronic document connections require separately supported scope.

Systems and records it connects with

  • Contract management: Applicable shipper terms and separate carrier confirmation.
  • Service reports: Actual cargo-event acknowledgements and exceptions.
  • Invoice management: Reviewed freight-service lines and approved changes.

Configure, test and introduce the workflow.

  • Trace a carried load and an arranged load, where both models occur, through actual acceptance and custody records.
  • Define sourced states for requested, accepted, collected, partially delivered and unresolved outcomes.
  • Test a partial pickup and refused delivery without converting a booking document into custody or a return instruction into completed return.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Order creation is separate from carrier acceptance and physical receipt.
  • Cargo carried for others is not recorded as the operator’s saleable stock.
  • Partial work preserves the remaining load and its decision owner.
  • Operational closure identifies unresolved custody or commercial actions.
Freight and transport companies

How the business operates.

A freight business accepts a shipper’s load requirement under a spot arrangement or lane agreement, then coordinates carriage and its supporting evidence. It can perform the movement as a carrier or arrange an identified carrier as a freight agent; the record must state which responsibility was actually accepted. Cargo carried for others is separate from the operator’s saleable stock, and shipment paperwork is separate from physical custody. This planning scope covers ordinary road freight booking, carrier confirmation, pickup and delivery evidence, and freight-service billing. It overlaps road transport and trucking where the business performs carriage. Special cargo, customs brokerage, storage and multimodal work require separately confirmed capability and obligations.

Shipper and rate agreements

Record the load, lane, service buyer and agreed charge basis. Keep the shipper’s accepted terms separate from the carrier’s supply terms when another business performs the transport.

Carrier and load coordination

Confirm the actual carrier and required vehicle or equipment against the accepted shipment. A request or available truck listing does not establish acceptance, site readiness or permission to handle the declared cargo.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Shipper, consignee and actual freight-service payer
  • Load request, lane and accepted service or rate-agreement version
  • Declared goods, handling-unit information and observed pickup references
  • Named performing carrier, acknowledged instruction and relevant equipment requirement

Operational bottlenecks to check

The carrier request is mistaken for acceptance

An agent tells the shipper capacity is arranged before the performing carrier agrees. Retain the acknowledgement and unresolved conditions before confirming that commitment.

Actual cargo differs from the declared load

Different unit counts, dimensions or handling requirements can change the service. Record the variance and authorised decision without certifying unseen goods or silently adjusting the original request.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Define the load and responsibility

    Identify the goods declared, locations and accepted service. State whether the business performs carriage or arranges another carrier, retaining unresolved cargo or equipment questions.

  2. 2. Confirm commercial terms

    Record the shipper’s accepted rate and payer arrangement. Where an outside carrier is used, obtain its separate accepted instruction without assuming the two agreements contain identical charges or obligations.

  3. 3. Review pickup readiness

    Confirm the actual carrier and relevant site information. Keep a booking document separate from physical arrival, accepted loading and goods receipt.

  4. 4. Follow actual cargo events

    Retain pickup and onward event evidence from its source. Record partial quantities, waiting or changed destinations without turning an update from the driver into automatic customer approval.

  5. 5. Reconcile delivery evidence

    Match acknowledged delivery to the shipment and keep missing units or condition concerns explicit. A signature with exceptions must not become an unqualified complete-delivery status.

  6. 6. Review bills and unresolved matters

    Bill approved freight services and reconcile carrier charges independently. Preserve customer claims, disputed extras and incomplete payment evidence after the physical movement ends.

Industry reports to connect with

  • Loads awaiting carrier acceptance or pickup information
  • Shipment events with unmatched units or missing acknowledgements
  • Delivery exceptions and unresolved customer or carrier action
  • Additional-service claims awaiting commercial review

Questions before implementation.

When should freight and transport companies consider order management?

Use for ordinary road freight commitments where customer instructions, actual carriage and billing need shared shipment references. The authorised shipper or service buyer accepts a defined load movement or arrangement service.

What should we bring to the requirements discussion?

Bring anonymised examples of Shipper, consignee and actual service buyer with change authority; Declared load and handling-unit information with source; Accepted lane or spot-service terms and performing-carrier responsibility; Pickup instructions, carrier acknowledgement and event evidence. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Track the accepted freight-service commitment through actual carrier acceptance and cargo-event reconciliation. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The freight order does not verify cargo contents, supply specialised handling capability or create customs, insurance and delivery commitments.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Order creation is separate from carrier acceptance and physical receipt. Use this check when reviewing the first working version.

Talk to us

Discuss order management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements