Skip to main content
GullySystem
Logistics

Order Management for Road transport companies

Keep a carriage booking connected to the goods received, the movement instructions and the party responsible for freight.

CRM

Does this function belong in your operation?

For booking offices that accept and manage goods transport work. A referral passed to an independent carrier without operational responsibility needs a different process.

A consignor or authorised account representative asks the transport office to accept a consignment under stated carriage terms.

Treat the order as a carriage booking, with consignor, consignee and freight payer recorded separately. The booking needs package details, origin and destination, the agreed collection or delivery arrangement and the accepted freight basis. Physical receipt, loading and destination handover are later events. A request to change the consignee or split a load should preserve the original instruction and identify who accepted the change. This is consignment coordination, not a sale of the goods being carried.

Bring the records the workflow depends on.

  • Consignor, consignee, freight payer and the person authorised to change instructions.
  • Origin and destination branches or addresses, sender-declared cargo description and package counts, with observed receipt counts kept separately.
  • Accepted freight basis and the booked collection or delivery arrangement.
  • Goods-acceptance decision and any unresolved information or commercial hold.

Outputs to check

  • Carriage booking with instruction history and separate consignor, consignee and payer identities.
  • Consignment progress showing physical receipt, movement and destination handover evidence.
  • Unfulfilled quantities, changed instructions and approved billing references.

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. Separate enquiry from acceptance

    Record the proposed consignment and rate, then retain the actual acceptance before treating it as an operating commitment.

  2. 2. Confirm the instruction

    Identify the freight payer and collection or delivery method, including who accepts changes to the consignee or destination.

  3. 3. Record goods receipt

    Compare the packages actually received with the booking and retain differences rather than marking the entire consignment received.

  4. 4. Link movement and handover

    Attach loading, transfer and destination evidence to the consignment reference without equating branch arrival with final delivery.

  5. 5. Reconcile the booking balance

    Keep unreceived, undelivered, cancelled and disputed portions distinct while passing only accepted charge lines to billing.

Who uses the module, and who approves?

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

Booking clerk

Captures the consignor’s instruction and the exact commercial version accepted by the responsible parties.

Branch supervisor

Resolves count differences and instruction changes before releasing the affected portion to dispatch or destination staff.

Freight accounts reviewer

Checks the billing customer against the accepted payer arrangement and preserves any unresolved charge dispute.

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.

Fewer packages arrive

Record the actual accepted count and ask the authorised sender to resolve the booking balance.

Consignee is changed after loading

Retain the original instruction and the authorised amendment; pass the change to the branch currently responsible for the goods.

Booking cancelled after receipt

Keep custody and any return instruction open until an authorised handover is recorded; cancellation alone does not remove goods from the branch.

Payer declines to-pay freight

Keep the collection and charge dispute visible and refer release decisions to the responsible operator under the accepted terms.

Can this work independently?

Entered bookings can stand alone with a consignment reference and evidence from branch registers. Trip records and handover reports supply actual events; accounting owns invoice and payment status. Goods eligibility and operating release decisions remain with the operator. No CRM, goods stock ownership or automatic carrier connection is assumed.

Systems and records it connects with

  • Vehicle and trip management: relate loaded consignments to the actual movement manifest.
  • Service reports: reference branch receipt, attempted delivery or consignee handover evidence.
  • Invoice management: pass the approved freight payer and charge references, not the goods invoice value.

Configure, test and introduce the workflow.

  • Trace a booking from counter acceptance to destination release using actual slips and branch references.
  • Rehearse short receipt, changed consignee and cancellation after goods arrival, including who owns the resulting custody decision.
  • Reconcile opening consignments against physical branch records and accepted billing terms before choosing the operating start.

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.

  • A counter enquiry remains distinct from an accepted consignment.
  • A partial physical receipt does not mark missing packages received or loaded.
  • A changed consignee preserves the earlier instruction and identifies the authorising party.
  • Cancelling a booking does not close unresolved custody or create an assumed refund.
Road transport companies

How the business operates.

A booking clerk accepts goods at the origin branch, but the destination office needs the same consignment details before releasing them. This scope covers goods transport businesses that operate or directly manage own or hired vehicle movements between booking points. It includes part-load consolidation and full-load jobs where those services are actually offered. A consignment, its vehicle movement and its destination handover need separate records. Brokerage-only introductions, passenger services and a standalone warehouse contract are outside this operating model. Software requirements should follow the operator’s actual branch responsibilities and freight terms.

Booking counter

Record the consignor, consignee, package description and freight payer before accepting a carriage instruction or changing its terms.

Branch dispatch

Build the movement manifest from physically received consignments, noting package differences and the vehicle responsible for each leg.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Consignment reference with origin and destination branches, consignor, consignee and separate freight payer.
  • Sender-declared cargo description, alongside package counts actually observed at acceptance, loading, branch receipt and final handover; sealed contents remain distinct from external counts.
  • Movement manifest identifying consignments, vehicle, driver or hired operator and each transfer point.
  • Freight basis, payer arrangement, accepted extra services and the version of the booking instruction.

Operational bottlenecks to check

One booking crosses several records

A consignment reference needs to survive a changed vehicle, split loading and a destination branch’s separate local register.

Arrival mistaken for delivery

Goods held at the destination branch are still awaiting release; a branch arrival message is not consignee acknowledgement.

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. Accept the carriage instruction

    Capture goods information and the operator’s service decision, then distinguish accepted freight terms from an unaccepted counter quotation.

  2. 2. Receive and load consignments

    Record physical receipt and loading counts; a booking remains unreceived until the goods are actually handed over.

  3. 3. Move between responsible branches

    Link consignments to the actual trip and preserve transfer evidence when another vehicle or branch takes custody.

  4. 4. Record arrival and release

    The receiving branch checks its count, resolves release instructions and records collection or door delivery under the booked service.

  5. 5. Reconcile freight and exceptions

    Compare approved charges, invoices and collection evidence while retaining open shortages, disputed delivery acknowledgements and unpaid balances separately.

Industry reports to connect with

  • Consignments received but not loaded, with the branch and recorded hold reason.
  • Manifest-to-arrival count differences and the person following each custody exception.
  • Destination goods awaiting authorised collection or actual door-delivery evidence.
  • Freight billed, collections referenced and disputed balances by the responsible account or branch.

Questions before implementation.

When should road transport companies consider order management?

For booking offices that accept and manage goods transport work. A referral passed to an independent carrier without operational responsibility needs a different process. A consignor or authorised account representative asks the transport office to accept a consignment under stated carriage terms.

What should we bring to the requirements discussion?

Bring anonymised examples of Consignor, consignee, freight payer and the person authorised to change instructions.; Origin and destination branches or addresses, sender-declared cargo description and package counts, with observed receipt counts kept separately.; Accepted freight basis and the booked collection or delivery arrangement.; Goods-acceptance decision and any unresolved information or commercial hold. 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. Keep a carriage booking connected to the goods received, the movement instructions and the party responsible for freight. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

No sale or ownership transfer of cargo is recorded by this booking alone. Customs clearance, transport permissions, automatic dispatch, goods-value collection and delivery commitments require separate scope.

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. A counter enquiry remains distinct from an accepted consignment. 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