Readymade

Work Freight brokerage

One system for loads, carriers and the money between them

A load management platform for a freight brokerage: loads, carriers and partner brokers in one place, with payables, receivables and branch reporting built on the same records.

Sector
Freight logistics
Our part
Product architecture, API and data model, Integrations, Dashboard, Infrastructure and delivery pipeline
Built with
TypeScript, React, AWS Lambda, Aurora PostgreSQL, Amazon Cognito, AWS CDK

See how it works

An interactive demo with sample data. Click through it to follow the flow.

Dispatch Loads board Sample data
8 loads
Load Route Pickup Carrier Status Rate
Antwerp → Lyon Mon 9 Jun North Line Transport In transit €2,300
Rotterdam → Milan Tue 10 Jun — Available €3,100
Hamburg → Warsaw Tue 10 Jun Baltic Freight Co. Delivered €1,750
Liège → Barcelona Wed 11 Jun Iberia Road Partners In transit €2,900
Ghent → Munich Thu 12 Jun — Available €1,980
Brussels → Paris Thu 12 Jun Seine Logistics Delivered €1,150
Duisburg → Vienna Fri 13 Jun Danube Haulage In transit €2,650
Zeebrugge → Turin Mon 16 Jun — Available €3,400

LD-3108: Antwerp → Lyon

Created by dispatch

  1. Load created
  2. Carrier assigned
  3. Picked up
  4. In transit
Broker receivable
€2,300
Carrier payable
€1,850
Margin
€450

Open balances by branch

  • Branch North €18,400 €14,900
  • Branch Central €12,700 €10,300
  • Branch South €9,600 €7,900
Interactive demo with sample data. A simplified recreation of the dashboard to show how loads and money connect — not the client's interface or data.

The starting point

A freight brokerage runs on many moving parts: loads to cover, carriers and partner brokers, documents, and money owed in both directions. Teams in several branches need the same picture, each with their own permissions, and the numbers in accounting have to match what happened on the road.

What we were responsible for

Readymade built the platform end to end: architecture, the API and data model, the dashboard teams work in, authentication and permissions, integrations, cloud infrastructure and the delivery pipeline.

What we built

  • Loads, carriers and brokers

    Records with status transitions, comments and files for loads, carriers, outside brokers and licences, shared across branches and teams.

  • Money in both directions

    Payment orders, carrier payables, broker receivables and office expenses, with billing reports per branch built on the same load records.

  • A loads board fed from outside

    External loads arrive through an authenticated ingest API, and freight exchange searches are cached and refreshed on a schedule.

  • Teams and permissions

    Branches, teams and a role-permission matrix, with sign-up, login and password recovery flows.

Why it was hard

  • Many roles, one source of truth

    Dispatch, accounting and management see the same records through different permissions.

  • Money tied to operations

    Payables and receivables have to follow load status changes exactly.

  • A large API, deployed safely

    Each API route runs as its own function, defined in infrastructure code and promoted from development to production through a gated pipeline.

The result

The platform covers load management, accounting flows, external load intake and team permissions, with development and production environments and automated deployment.

  1. Load enters Created by dispatch, ingested from outside, or found on an exchange.
  2. Carrier assigned Carrier and partner broker linked to the load.
  3. Load in progress Status changes, comments and documents.
  4. Money settled Payables and receivables follow the load.
  5. Branch reporting Billing reports per branch from the same records.
How one load moves through the platform. Schematic; no client data.

Working on something similar?

Tell us about it. The form will note that you came from this case.

Discuss a similar project