Operations · Order & Supply Management

Freight under control, not under negotiation.

Structured tendering, live visibility and audited settlement for shippers — logistics run from a system, not a phone log.

For shippersWhat it covers
01Awards by rule, with the reasons kept.
02One board, exceptions at the top.
03Freight audit that runs itself.
04Scorecards that change the next award.
How it runs
  1. Baseline & lane selection
  2. Carrier onboarding
  3. Pilot lanes live
  4. Freight audit & ERP
  5. Operate & report
Why it exists

Freight spend is known; the cost per lane is not.

A shipper’s logistics desk usually knows its freight spend to the nearest million and its actual cost per lane to nobody’s satisfaction. Tenders go to whoever answers. The status of a load is a call to the carrier, who calls the driver. The freight invoice arrives weeks later with accessorials nobody can verify, and it gets paid because auditing it would take longer than the difference is worth.

Order & Supply Management for shippers replaces that with a system. Lanes are tendered to your contracted network with terms on record and awards made by rule. Every shipment is live on one board, with exceptions raised before the customer calls. Invoices are matched to the rate agreed at award, and accessorials must cite evidence. The desk spends its day on decisions, not on chasing.

On managed lanes the platform reports on-time rate, status calls avoided, invoices settled against contracted rates and freight cost per lane — each against the baseline recorded from your history before go-live. Your existing carriers run first; marketplace capacity is optional headroom. The platform overview covers the shared layer both sides use.

Features

What it does, in detail.

01

Awards by rule, with the reasons kept.

Configure how a lane is awarded once — contracted priority, lowest landed cost, service score or a weighted mix — and the platform applies it to every tender. Carriers respond in the portal. When a preferred carrier declines, the platform records why and moves down the waterfall you defined. When you renegotiate next year, the acceptance and decline history is the evidence, not a recollection.

  • Waterfall, broadcast or spot tender modes per lane
  • Marketplace capacity only where you switch it on
  • Tender response time and acceptance rate per carrier
  • Award rule changes versioned, with who changed what
Lane has a contracted carrierOffer at the contracted rate, with a time limit to accept
Declined or timed outOffer to the next carrier in the waterfall
Waterfall exhaustedBroadcast to the approved network
Service score below the lane thresholdExclude from broadcast this quarter
02

One board, exceptions at the top.

The shipment board is not a map with dots. It is a list of every load in flight, sorted by what needs a decision. Dock window at risk, POD missing, load gone quiet for two hours — each is raised by a rule you configured, with the parties already notified and the options shown. Loads that are on plan stay quiet, so planners can focus on the ones that need a decision.

  • ETA recalculated on movement, from app or telematics
  • Receivers accept a revised window inside the platform
  • Silence is an exception: no update for N hours raises a flag
  • Every exception records who was told and what was decided
03

Freight audit that runs itself.

The rate is fixed at award. The invoice is matched to it automatically when it is uploaded. Where the two agree, the invoice is approved without a person touching it. Where they differ, the difference is itemised — a waiting-time accessorial, a detour, a fuel-surcharge mismatch — and becomes a dispute with evidence attached, an owner on both sides and a deadline. The result is a freight-cost figure finance can check.

  • Every invoice checked against contracted rates
  • Accessorials require a stamp, a photo or a signed document
  • Accruals and settlement files post to the ERP by contract
  • Dispute ageing and recovery reported per carrier
  1. 01Invoice received
  2. 02Matched to award rate
  3. 03Difference itemised
  4. 04Approved or disputed
  5. 05Paid

Freight audit path

04

Scorecards that change the next award.

Every tender response, pickup, delivery and claim writes to the carrier’s record. On-time percentage, acceptance rate and claims per hundred loads are calculated per lane and per carrier and refreshed continuously. When you want service to count against price, the scorecard feeds the award rule directly — so a carrier who declines late or delivers late sees fewer tenders in later rounds, and knows why.

  • On-time, acceptance, response time and claims per lane
  • Regular business reviews from the record, not from a slide
  • Service weighting in award rules, if you choose it
  • Same figures the carrier sees in its own portal
By role

Three seats on the shipper side.

Logistics manager

Decisions, not chasing.

Tenders go out by rule and the board shows what needs a decision. The week is spent on lane strategy, carrier allocation and the exceptions that genuinely need a person.

  • Tender waterfalls per lane
  • Exception board with parties already notified
  • Scorecards for allocation and regular reviews
Customer service

The ETA the customer already has.

Receivers see the same ETA the platform calculates, and accept a revised window inside it. The late-delivery call becomes a notification the customer has already read.

  • Receiver-facing tracking links
  • Revised windows accepted on the record
  • POD available to the customer the moment it is captured
Finance

A freight-cost number you can close on.

Every invoice is matched to a rating fixed at award. Accruals come from the platform, disputes carry evidence, and the settlement file posts to the ERP.

  • Rated versus paid reconciled continuously
  • Accessorials with evidence or not at all
  • Cost per lane, per carrier, per customer
Architecture

How the shipper side connects.

Your systems
ERP (orders, accruals)WMS / yardCustomer portalBI
Shipper surfaces
Order intakeTender engineShipment boardFreight auditScorecards
Shared layer
Load recordEvent ledgerCarrier networkDriver app
Compare

Phone log versus platform.

Tendering
Status
Receiver ETA
Freight invoice
Carrier review
ERP
01Phone, email and spreadsheet
TenderingCall-around; whoever answers
StatusCall the carrier, who calls the driver
Receiver ETACustomer calls you
Freight invoicePaid; audited quarterly if at all
Carrier reviewAnecdote and a slide
ERPRe-keyed both ways
02Order & Supply Management
TenderingStructured tender, award by rule, history kept
StatusLive from app and telematics; exceptions raised by rule
Receiver ETAReceiver sees the same ETA and accepts revised windows
Freight invoiceMatched to award rate automatically; disputes with evidence
Carrier reviewScorecards from the record, feeding the next award
ERPOrders in, accruals out, by governed contract
Implementation

From baseline to a measured result.

01

Baseline & lane selection

Last quarter’s loads, rates and invoices; a measured cost baseline per lane and the pilot lanes chosen for the highest, most verifiable saving.

02

Carrier onboarding

Your contracted carriers onboarded to the portal. We run onboarding as a product function — it is the pacing item.

03

Pilot lanes live

Tenders, execution and the shipment board on pilot lanes. Exception rules tuned on real traffic. First scorecards.

04

Freight audit & ERP

Rating and invoice matching switched on; accruals and settlement files posting to the ERP. Lanes expanded by template.

05

Operate & report

Results reported regularly against the baseline, at a rhythm agreed with you: cost per lane, on-time, status calls, dispute recovery. Expansion to further lanes and carriers as the numbers earn it.

FAQ

Frequently asked questions

Ideal — the platform runs your existing network first; marketplace capacity is optional headroom you switch on per lane, or never.
Orders in, settlement and accruals out, via governed integration contracts — major ERPs included. The ERP stays the ledger; the platform runs the moves.
That is agreed with you according to your needs: carrier network onboarding is the pacing item, and we run it as a product function with its own metrics.
They need to respond to tenders and update status — in the portal or through the driver app.
Against a baseline we record before go-live, per lane, using your own history. Your target is modelled in the assessment and the platform reports against it regularly after go-live, at a rhythm agreed with you.
Yes — receiver-facing tracking with the same ETA the platform uses internally, revised windows accepted on the record, and proof of delivery shared the moment it is captured.

See it on your own data.

A guided demo with an engineer who operates the platform — walked through on your lanes and your carriers, not a canned deck.

✓ No pitch deck✓ Reply from an AI-native engineer✓ Written follow-up