Skip to main content
GullySystem
Logistics

Business solutions for Freight forwarding companies

Explore software for work such as “Shipment scope, route and rate comparison”. Review each business function below, including when it fits and what to check before implementation.

Freight forwarding companies

How the business operates.

A freight forwarding company organises an agreed movement of goods through carriers and other service providers. The customer can be an exporter, importer or another forwarding agent. A shipment file needs the requested route, cargo details, responsibilities at each end and the parties paying each charge. Sea, air and inland legs share a commercial file but retain their own booking and handover evidence. Forwarding overlaps with air-cargo agency work; this broader workflow covers coordination across the modes and partners actually offered. Owning the cargo, operating transport and acting as a customs representative are separate responsibilities that must be established for each engagement.

Pricing and customer instructions

Compare carrier or co-loader offers against the same cargo and route. Record rate validity, currencies, included local charges and exclusions before issuing a customer quotation.

Shipment coordination

Arrange the accepted legs, retain partner confirmations and follow outstanding instructions. A requested sailing or flight remains planned until the responsible carrier confirms its booking.

Documentation and accounts

Keep instruction versions, bill references and payer details with the job. Match customer charges and provider costs separately, including costs received after the first invoice.

The records that hold the operation together.

  • Customer instruction with shipper, consignee, requesting agent, cargo description, package count, declared measurements, route and agreed responsibility for each leg.
  • Buying offer and selling quotation versions with validity, currency, charge basis, payer, inclusions, exclusions and recorded acceptance.
  • Shipment job with carrier booking references, house and master document links where applicable, instruction revisions and partner handover evidence.
  • Customer invoices, provider bills, approved adjustments, advances and agent statements linked to the shipment without merging separate parties’ balances.

Operational bottlenecks to check

A cheaper quote excludes a leg

Compare origin, freight and destination responsibilities before choosing an offer. Record which party must arrange and pay for a service outside the quoted scope.

A revised instruction misses a partner

Keep the superseded version and the recipient’s acknowledgement together. An internal correction does not prove the carrier or destination agent has applied the change.

Shipment completion precedes cost completion

List expected provider costs and received bills separately. Mark incomplete cost information clearly when reviewing the job rather than treating an early margin as final.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Define the movement

    Capture the actual contracting customer, cargo information and required origin and destination services. Identify any work needing a separately qualified or authorised provider before accepting scope.

  2. 2. Agree scope and price

    Check buying offers against the same shipment assumptions. Obtain acceptance of the selling quotation and record who can approve route changes, extra services and charges.

  3. 3. Request and confirm bookings

    Send authorised instructions to the chosen carriers and partners. Retain their responses, conditions and references; customer acceptance alone does not establish carrier space or equipment.

  4. 4. Review documents and handovers

    Link supplied instructions to the relevant draft and approved document. Record actual custody transfers from the responsible parties, retaining missing information and unresolved discrepancies.

  5. 5. Follow each transport leg

    Record dated evidence for departure, transfer, arrival and delivery where included. A revised transport plan changes the expectation; it does not prove that cargo moved.

  6. 6. Reconcile the file

    Compare agreed customer charges with billable events and provider costs. Keep unresolved invoices, claims and agent settlements visible even after the physical movement has ended.

Roles and responsibility boundaries.

Pricing executive

Checks the requested movement, seeks comparable buying terms and sends the approved selling quotation. Records assumptions that operations must resolve before booking.

Operations coordinator

Owns the shipment action list and records the source of each milestone. Escalates changed schedules, missing cargo information and unconfirmed onward arrangements.

Documentation executive

Checks supplied party and cargo details, sends drafts for authorised review and preserves corrections. Document issue and release remain subject to the issuing party’s authority.

Accounts reviewer

Checks billing responsibility, supporting cost records and customer receipts. Separates agent settlements, advances and disputed charges instead of treating every incoming amount as earned freight income.

Reports your managers need.

  • Jobs awaiting carrier confirmation, customer instruction or partner response, grouped by the next responsible person and required action.
  • Quoted and approved selling charges beside received and outstanding provider costs, with currencies and unresolved differences visible.
  • Open document corrections, missed milestones, customer disputes and agent settlement items by shipment and age.

Connections to scope

  • Carrier and agent portals, emails or agreed file exchanges can provide booking and movement evidence. Confirm access, identifiers and update ownership before proposing any connection.
  • Accounting handoffs need separate customer and supplier identities, currencies and adjustment references. A shipment record does not itself post entries, transfer funds or authorise document release.

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Map the actual service boundary

Review completed and open jobs across the modes the business offers. Identify the contracting party, operating carrier, documentation issuer and owner of every handover.

Prove revisions and exceptions

Trial a changed sailing, corrected consignee detail and late provider charge. Confirm that earlier instructions remain readable and each new commitment needs the right approval.

Reconcile opening files

Bring across open bookings, document tasks and balances with their evidence. Have operations and accounts check pending work separately before extending the agreed workflow.

Limitations to settle before implementation

  • Customs representation, cargo handling, insurance arrangements and specialist transport require their own agreed scope and responsible qualified parties. Recording a task does not confer that authority.
  • Carrier acceptance, official clearance, cargo release and transport performance depend on their responsible organisations. Software requirements must be checked against available capabilities and approved interfaces.
  • Goods remain the property of the relevant owner. Custody evidence and freight billing do not establish ownership or entitlement to collect the cargo’s sale proceeds.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Shipment scope, route and rate comparison
  • Carrier and partner booking coordination
  • Shipping instruction and document revision tracking
  • Transport milestone and handover follow-up
  • Customer billing and provider-cost reconciliation
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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