One place for a transport company to work: quote, order, trip, own fleet and subcontractors, cost, settlement and invoice. Data flows both ways with the ERP.
Sample screens. All names and figures are fictional.
The problem
A transport operation comes apart in four places.
Orders, shipments and freight run on phone calls, email and spreadsheets. Nobody sees the work from end to end.
Disconnected systems
Data sits across the TMS, spreadsheets, the ERP and message groups, and none of them talk to each other.
Settlement by hand
Fuel, rent, bonuses and deductions are worked out manually, which leaves room for errors and leaks.
Cut off from the ERP
Invoices, accounts and payments are entered a second time, then reconciled.
No traceability
Who changed what, and when? Without approvals and an audit trail, nobody owns the answer.
How it works
One order, from first price to final invoice.
Follow one sample order on one record, step by step.
01
Price it with the margin in view.
The pricing engine builds the freight from the customer’s tariff: base rate, stops, excess kilometres and fuel index. The estimated margin sits beside the total.
Tariffs per customer and project
A quote under the margin threshold goes to approval
02
The approved quote becomes the order.
Customer, route and freight carry over. Load, appointment and documents go onto the same card, so one record holds the commercial, load, route and document layers.
Several load items and partial delivery in one order
Custom fields, tags and reference numbers
03
Assign the trip, set the stops.
The order gets a vehicle and a driver, from your own fleet or a subcontractor, in the same flow. Stops go in sequence with their appointment windows.
Six trip types, from full truckload to cross-dock
04
Follow it stop by stop.
Each stop holds its pallets, its window and its proof of delivery. When a truck waits at a stop, the exception stays on that stop.
Partial delivery, stop by stop
Waiting, short delivery and route deviation are logged as exceptions
05
Close the trip and see its profit.
Fuel, tolls, driver allowance, handling and maintenance collect on the trip. When it closes, freight minus cost gives the trip profit.
All of the trip’s costs on one record
06
Match the invoice, send it to the ERP.
The invoice links to its trip and goes to the ERP. The status of the e-Fatura, Türkiye’s electronic invoice, comes back to the same record. An invoice with no match waits for a person.
Sample screens. All names and figures are fictional.
Modules
A day’s work, screen by screen.
Freight, stops, excess kilometres and fuel index come from the tariff. The margin moves with every line, and a quote under the threshold goes to approval.
Prices, orders and settlements pass through a defined chain. One inbox holds what is waiting for you, and a role matrix sets who can read, write or approve.
Sample role set-up. Permissions are set by module and action.
Details
All the details.
Overview
Fewer trucks running empty. Dispatchers who don’t live on the phone.
Shippers and carriers plan and execute on one screen: loads tendered by rule, routes optimised under real driver and dock constraints, live status from the driver app — built for fewer empty miles, fewer phone calls, and a freight audit that closes itself.
Why it exists
Why it exists
Freight coordination still runs on phones and spreadsheets.
A tender is a call-around. A status update is a call to the driver. A freight invoice is a spreadsheet reconciled a month later, if anyone gets to it. Every handoff between shipper, carrier and driver loses data, and every gap costs miles that never appear on a report because nobody was measuring them.
Order & Supply Management puts shippers and carriers on one shared layer — tendering, planning, execution and settlement — so the network optimises as a network rather than as a set of private plans. The shipper tenders to a structured carrier network. The carrier fills backhauls from network demand. The driver updates status in three taps. Finance settles against the rate that was agreed. One record, both parties, no re-keying.
The measurable core: empty miles, loads per week and on-time rate are the three numbers the platform is built to move, and each one is reported against a baseline taken from your own lane history before go-live, so your target comes from your network rather than from a brochure.
Modules
Modules
Six modules, one load record.
Every module reads and writes the same load record, so the tender that was awarded, the plan that was driven, the status the receiver saw and the invoice that was paid are one fact — not four systems to reconcile.
01
Tendering & marketplace
Structured tenders replace call-arounds. Lanes go to your contracted network first, with terms on record; marketplace capacity is optional headroom. Offers, awards, declines and reasons are logged, so allocation is a rule you can read rather than a memory of who answered the phone.
Contracted networkAwards by ruleMarketplace
02
Route & load planning
Optimisation under real constraints: driver hours, dock windows, equipment types, weight and axle limits. The output is a plan a dispatcher can keep, because it is built within those limits. That leaves less reason for the overrides that teach an organisation to ignore its TMS.
Constraint-trueBackhaulConsolidation
03
Execution & tracking
Live status and ETAs from the driver app and telematics, with exceptions raised by rule before the customer calls. The phone calls the platform makes unnecessary are the point; the exception board is what dispatchers look at instead of a call log.
Live ETAExceptionsTelematics
04
Settlement & freight audit
Every load is rated against the contracted rate, accessorials are validated against evidence, and disputes are structured and paid on one trail. Freight audit becomes a report rather than a quarterly project, because differences between rated and paid are visible as they arise.
Rated vs paidAccessorialsDisputes
05
Driver app
Offline-first mobile designed for drivers: three taps for a status update, large targets, and it works in a yard with no signal and syncs when it finds one. Proof of delivery and document capture happen at the dock, not at the office on Friday afternoon.
Offline-firstThree tapsPOD capture
06
Network analytics
Service per lane and carrier for shippers; loaded-mile and revenue per vehicle for carriers. Both sides read the same execution record, so the conversation is about decisions, not about whose numbers are right.
ScorecardsUtilisationShared record
Features
Features
What it does, in detail.
01
Plans that survive contact with the dispatcher.
Many route optimisers produce a beautiful plan that ignores the fact that the driver is out of hours at 14:00 and the receiver only accepts deliveries before noon. Dispatchers override it, and soon the organisation has learned to ignore the system. Our optimiser takes the constraints as inputs — hours-of-service, dock windows, equipment compatibility, weight and axle limits — and searches for consolidation and backhaul within them. The saving it reports is one you can actually drive.
Backhaul matching across the whole network, not just your own orders
Multi-stop consolidation with dock-window and hours-of-service checks
Re-plan on disruption, with the reason for each change shown
Baseline measured before go-live so the saving is comparable
02
Exceptions raised before the phone rings.
Execution is where visibility products usually stop at a dot on a map. We treat it as a stream of events — check-in, loaded, departed, ETA revised, arrived, delivered — from the driver app and from telematics. Rules watch that stream and raise an exception when a dock window is at risk, a POD is missing or a load has gone quiet. Dispatchers work the exception board; everyone else reads the status the platform already knows.
Status from three taps in the driver app or automatically from telematics
ETA recalculated on movement, with dock-window risk flagged to both parties
Receivers see the same ETA the shipper sees — no separate customer call
Every exception carries who was told, when, and what they decided
03
Rated, proven and paid on one trail.
If freight audit still runs on spreadsheets after go-live, the loop never closes: the rated plan and the paid invoice drift apart and nobody notices until the year-end review. On Order & Supply Management every load is rated at award time against the contracted tariff. The carrier’s invoice is matched to that rating automatically; accessorials must cite evidence — a waiting-time stamp, a photo, a signed document — and any difference becomes a structured dispute with an owner and a clock.
Contracted rates and accessorial schedules held per carrier and lane
Automatic match of invoice to rating; only differences need a human
Disputes with evidence, owner and deadline — closed on the record
Settlement files to the ERP through governed contracts, not re-keyed
By role
By role
One platform, four seats.
Shipper
The logistics manager stops chasing.
Tenders go out by rule, awards come back on the record, and the board shows every shipment with an ETA the receiver can also see. The day is spent on exceptions and on carrier allocation decisions with data in them — not on status calls.
Contracted network first, marketplace as headroom
One board, every shipment, exceptions first
Scorecards per lane and carrier for the next allocation
Carrier
The dispatcher plans with the network’s demand.
Tenders arrive in the portal. Loads on the board show backhaul opportunities along the planned route. Assignments respect the driver’s remaining hours, and the plan on the screen is the plan the driver has in hand.
Backhaul demand visible along your own routes
Hours-aware assignment
Paperwork arrives from the app, not from the cab on Friday
Driver
Three taps, and it works in the yard.
Check-in, loaded, delivered — each one tap, each with a large target. Proof of delivery is a photo and a signature at the dock. If there is no signal, the update queues and syncs when there is.
Offline-first; updates queue without a signal and sync when it returns
POD and documents captured at the dock
Piloted with real crews on real routes before rollout
Finance
Rated versus paid reconciles itself.
Every invoice matches to a rating made at award time. Differences are disputes with evidence and an owner. Accruals come from the platform, not from an estimate, and the settlement file posts to the ERP through a governed contract.
Invoices settled against contracted rates
Accessorials require evidence
Days from POD to payment tracked per carrier
Architecture
Architecture
Reference architecture.
Surfaces
Shipper portalCarrier portalDriver app (offline-first)Public API
Major fleet telematics feeds for automatic status and ETA
WMS & yard systems
Dock schedules and appointments in both directions
Customs & documentation
Cross-border document providers with the audit trail kept on the load
Identity
Carrier users under their own tenant
Power BI & data warehouse
Event ledger exported for your own analytics
Rollout
Implementation
From assessment to a measured result.
01
Assessment & baseline
Your lane data, carrier list and last quarter’s invoices. We model the empty-mile and freight-cost opportunity and record the baseline the result will be measured against.
02
Network onboarding & pilot lanes
Contracted carriers onboarded to the portal — we run onboarding as a product function with its own metrics. First tenders on pilot lanes.
03
Execution & driver pilot
Driver app piloted with real crews on real routes. Telematics connected. Exception rules tuned on live traffic until dispatchers stop looking at the phone.
04
Settlement live & expansion
Rating and freight audit switched on for pilot lanes, ERP contracts live, then lanes and carriers added by template.
05
Operate & measure
We operate the platform and report the result against the baseline, with service levels and reporting rhythm agreed with you according to your needs. The saving is real only if it is comparable.
FAQ
Frequently asked questions
No — single-side value stands alone. A shipper gets structured tendering, visibility and freight audit with its existing carriers; a carrier gets hours-aware planning and portal paperwork. Network effects — backhaul matching, shared ETAs — compound as counterparties join.
Through modern APIs and webhooks. A carrier on the API and a carrier on the portal look identical to the shipper.
Assessed on your lane data before commitment. Empty miles, cost per lane and on-time rate are baselined from your own history, the target is modelled from that, and the platform reports against it regularly after go-live, at a rhythm agreed with you.
Offline-first mobile designed for drivers — three taps, large targets, works in a yard with no signal. Pilot routes with real crews test it before rollout.
Major ERPs through governed integration contracts — orders in, settlement and accruals out. Major telematics providers feed status and ETA automatically. For anything else a connector can be built, with the scope agreed with you according to your needs.
Both. It runs as a managed service on our infrastructure, or inside your own perimeter where regulation or cross-border rules require it — the same platform, with availability targets and service levels agreed with you according to your needs.