Loadline Co-pilot
Reads the orders, trips, tickets and payments a clerk would open — read-only — then does the typing.
For African manufacturers
Prove what left the gate and what customers received. The difference gets a name, a truck, and a trip number.
Trip KDC 789Z
Shipment journey
5 stages · 5 completed
Order delivered
5.0 from Embakasi Distributors
Settlement · KDC 789Z
Order settled
Raised with the order, signed at supply, reconciled on its own
KES 1,284,500
0 exceptions raised
Nothing reached the accounts queue, because nothing needed a human.
The co-pilot, the connector layer, the app everyone on a load works in, and your storefront — one tenant, one set of records, no export step between them.
Reads the orders, trips, tickets and payments a clerk would open — read-only — then does the typing.
The weighbridge indicator, your ERP and the database under it, the PBX, the map, the banks and the tax authority — all behind one connector interface, every payload stored as it arrived.




The gate clerk, the rep, the driver, the accounts desk and the customer — everyone a load passes through, writing to one trip record.
TRIP KDC 789Z
Embakasi Mills to Kariobangi · dispatch 4471
29 000
gross kg
12 000
tare kg
17 000
net kg
Gracegate clerk
Aminasales rep
Josephdriver
Faithback office
Embakasi Traderscustomer
Every plant gets a shop: M-Pesa checkout, an eTIMS receipt on every sale, and delivery the customer can follow to the geofence — off the same catalogue the desk sells from.
Invoice, order, delivery, payment: five pages of one console, and every checkpoint writes an append-only event.
A dispatch console, played through five checkpoints of one order for the demo tenant: trip KDC 789Z, Nairobi plant to Embakasi Distributors on 24 March 2026. Each checkpoint opens a different page of the console.
Tonnes across Weighbridge 1 this week, out of the gate against signed for at the door: Mon: 214 tonnes out the gate, 211 signed for; Tue: 268 tonnes out the gate, 262 signed for; Wed: 241 tonnes out the gate, 240 signed for; Thu: 292 tonnes out the gate, 286 signed for; Fri: 317 tonnes out the gate, 309 signed for; Sat: 168 tonnes out the gate, 168 signed for.
Days to pay over the last thirty days, against 14-day terms: Embakasi Dist., 14 invoices, 2 days inside 14-day terms; Ruaraka Traders, 9 invoices, 5 days inside 14-day terms; Kitengela Millers, 6 invoices, 3 days past terms (chasing); Athi River, 4 invoices, 21 days past terms (chasing); Nakuru Cereals, 11 invoices, 4 days inside 14-day terms.
Invoice, order, delivery, payment: five pages of one console, and every checkpoint writes an append-only event.
Order to cash
Trip KDC 789Z · 5 stages · 5 completed
5 events · append-only
Weights come off the indicator, orders off the geofence, payments off the rail. Nobody re-keys anything, so nothing drifts.
eTIMS invoices are signed inside the statutory window, even the ones created offline. An outage delays a submission; it never loses one.
Every checkpoint writes an append-only event. Shrinkage stops being a month-end argument and becomes a trip you can open.
13 modules
Today it is a book at the gate, a phone call from the road and a spreadsheet reconciled at month end. Pick a department to see what replaces each part.
tolerance ±0.5% or 50 kg, whichever is greater
Today
The gateman reads the indicator through the window and writes the weight in the book. It is typed into the spreadsheet at the end of the shift, and a short load is argued about the following week.
weighbridge_book.xlsx
With Loadline
Gate-in to gate-out with the weighbridge read over its JSON API, so weights are captured, never typed. Out-of-tolerance loads are held until a supervisor overrides with a reason that stays on the record.
tolerance ±0.5% or 50 kg, whichever is greater
geofence 200 m · free pass on approval
Today
The rep phones the order in from the road, or writes it on a pad and reads it out that evening. Nobody can say whether he was standing at the customer's gate or at home.
call to the office, 17:40
With Loadline
Geofenced order capture on the rep's phone, online or offline. The order is taken at the customer's premises, and a supervisor grants a temporary free pass when a route genuinely needs one.
geofence 200 m · free pass on approval
no manual re-keying from the plant floor
Today
The plant prints the production order and walks it to the office, where the quantities are keyed in a second time. Stock is correct once a day, briefly.
production_order.pdf
With Loadline
Production machines read through their available APIs: production-order information retrieved automatically and posted into stock and dispatch planning as it happens.
no manual re-keying from the plant floor
every approval on the record
Today
A requisition is a paper chit that walks between three desks for signatures, and reaches the ERP about a week after the stock left the store.
requisition chit #0412
With Loadline
Requisitions with their approval chains, stock movements, and postings into your ERP through the connector layer, in the order the events actually happened.
every approval on the record
proof of delivery, geofenced
Today
The manifest is a printed sheet on the dashboard. “Where is my lorry” is answered by phoning the driver, who is driving, and asking him to guess.
manifest, printed at 06:00
With Loadline
Drivers carry the manifest with the route on a map. Customers watch the truck against their own geofence on a public tracking link, and nobody phones the driver.
proof of delivery, geofenced
Operations5
The physical loop: the gate, the bridge, the plant floor, the store and the road. Everything that moves a kilogram, recorded where it happened rather than typed up afterwards.
queued durably, submitted with retries
Today
One person retypes the day's invoices into the eTIMS portal, in a batch, whenever the line is up. If she is on leave or the link is down, the statutory window closes on them.
eTIMS portal, retyped
With Loadline
Invoices signed and control-numbered inside the statutory window, even the ones written offline. A rail outage delays a submission; it never loses one.
queued durably, submitted with retries
webhooks signature-verified, replays idempotent
Today
M-Pesa confirmations are read off a phone and matched to orders against a bank statement at month end. Two people spend three days on it and still close with a variance.
statement_march.pdf
With Loadline
M-Pesa and bank payments verified before a shilling is recorded, then matched to orders automatically. Only the genuine exceptions reach the accounts queue.
webhooks signature-verified, replays idempotent
Finance2
The statutory window and the bank. Invoices signed and control-numbered on time, and every shilling matched back to the order that earned it.
credit-checked at order time
Today
The customer emails an order to whoever answered last time. Credit is checked by walking to accounts, and the price is whatever the last invoice happened to say.
Fwd: order — please confirm
With Loadline
Registered business customers log in, see the catalog at their negotiated terms, and place orders that arrive in dispatch already credit-checked at the moment they were placed.
credit-checked at order time
order → dispatch → doorstep, one chain
Today
Walk-in buyers pay at the counter and leave with a handwritten receipt. The sale reaches the books when somebody carries the book upstairs.
receipt book, carbon copy
With Loadline
A public storefront with M-Pesa checkout, an eTIMS receipt on every sale, and the delivery tracked to the buyer's geofence like any other order.
order → dispatch → doorstep, one chain
calls recorded against customers
Today
The phone rings on a desk with no screen attached to it. The customer repeats his order number twice, and the call is remembered only by whoever picked it up.
sticky note on the monitor
With Loadline
Your existing PBX driven over its JSON API. Calls are made and answered with the account's order history already on screen, and every one is logged against the customer.
calls recorded against customers
queued, retried, never silently dropped
Today
A clerk types the same “your order has been dispatched” into WhatsApp from her own number, when she remembers, for the customers who complain loudest.
WhatsApp, personal number
With Loadline
SMS, email and WhatsApp on order, dispatch and delivery events, through pluggable gateway connectors that report back whether the message actually arrived.
queued, retried, never silently dropped
Commerce4
Every door an order can arrive through — the portal, the counter, the phone on the desk — and the message that follows it out.
kg, attributed
Today
Shrinkage is a number argued over in the monthly meeting, built by hand from the spreadsheet, attributed to nobody in particular and acted on by nobody at all.
monthly_variance_v3_FINAL.xlsx
With Loadline
Shrinkage by driver, vehicle and route. Fraud signals from recorded evidence, not anecdotes. The report your CFO has been asking the ERP for.
kg, attributed
every run logged: what it read, what it sent
Today
A clerk opens four screens, copies the figures into an invoice, and emails it before lunch. What she noticed while she was in there stays in her head.
four tabs and a calculator
With Loadline
It does the desk work: reads the orders, trips, weighbridge tickets and payments, drafts the invoice, and sends it on the channel the customer already uses. What it noticed comes back as a flag — a route drifting, an account past its terms.
every run logged: what it read, what it sent
Intelligence2
What the records already know, read back to you: shrinkage with a name on it, and the desk work done before lunch.
Loadline Co-pilot
Close a month, place an order, settle a refund. Ask in plain English and it does the desk work — then shows you every record it opened, and stops short of anything that moves money.
month-end · Kagio Millers
The console is a web app. Nothing to install, nothing to update on twenty machines — sign in and the yard is on the screen.
Installable from the address bar; the last pages you opened stay readable offline.
Access your work from the road with the rep's app and the driver's app — built for the field, and built to keep working with no signal at all.
Every manufacturer on Loadline gets a storefront: M-Pesa checkout, eTIMS receipts on every sale, and delivery your customers can track to the geofence.
loadline.africa/shop — a live render, not a screenshot.
Weighbridges, plant, your PBX, messaging gateways, the banks and your ERP — one interface, every payload stored as it arrived.




…and 40+ more behind the same interface.
Fifty-four countries, a dozen mobile-money rails, patchy coverage and a different tax clock in every market. These are not edge cases to handle later — they are the shape of the product.
Borders, currencies, tax authorities and payment rails change; the yard does not. Loadline models the country as configuration — not as a fork — so a mill in Nairobi, Lagos, Accra or Kampala runs the same dispatch, the same geofences and the same audit trail.
Trade does not stop at a customs post. Multi-country tenants keep one customer list, one product catalogue and one set of books, with each site reporting into the fiscal regime it actually sits in.
Mobile money is how the continent pays — MTN MoMo, M-Pesa, Airtel Money, Orange Money and Wave — and it settles straight against the order, alongside the banks behind them. Webhooks are signature-verified before a unit of currency is recorded, and a replayed callback lands as the same payment, once. Kenya is live; the rest sit behind one connector interface.
Reps and drivers keep selling and delivering with no signal at all. Work queues on the device and reconciles when coverage returns — nothing waits for a bar of 4G.
Geofences are metres, not neighbourhoods, and the maths runs on the device. An order only happens at the customer's premises, whether or not the map ever loads.
Invoices, reminders and reconciliation run themselves, queued durably with retries. A downstream outage delays a job; it never loses one, and never blocks the yard.
Fifty-four countries, fifty-four fiscal regimes, each with its own deadline and its own idea of a valid invoice. Kenya's KRA eTIMS is live. Uganda EFRIS, Tanzania, Rwanda EBM, Nigeria FIRS and Ghana all sit behind the same connector interface, so a new market is a driver, not a rewrite.
Shillings, naira, cedis, rand, dirham — whatever your customers actually pay in. Local tax, local rails, support in your own timezone. No conversion at checkout, and no invoice arriving in the wrong denomination.
Run a yard on the free tier for as long as you like. The co-pilot and the rest of the modules start at one flat monthly price for the whole team.
Run one yard and watch the loop close.
$0/ month
Get startedThe whole yard, and a co-pilot the team shares.
$100/ month
Get startedEverything in Free, plus:
More sites, more seats, and the controls your CFO will sign.
Custom
Talk to usEverything in Team, plus:
Prices in USD, excluding VAT. Connectors and additional sites are quoted per integration.
We onboard a small number of design partners with a weighbridge, a loading bay, and a field sales operation. Pilots run on one site.
Get started