Loadline

For African manufacturers

Close the loop on shrinkage.

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

  1. Order placedMar 24 · 06:28Embakasi Distributors
  2. DispatchedMar 24 · 07:04Nairobi plant · gate 2
  3. LoadedMar 24 · 07:51Weighbridge 1 · 17,000.0 kg
  4. In transitMar 24 · 08:20Mombasa Road
  5. Delivered & reconciledMar 24 · 11:38Signed for at the gate · in full

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

  1. Invoice raised06:20INV-4482 · raised with the order
  2. eTIMS signed11:52Control number 0042213887 · at supply
  3. Payment matched14:06M-Pesa QHX7 · matched to the order

0 exceptions raised

Nothing reached the accounts queue, because nothing needed a human.

Everything the yard runs, on one set of records.

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.

Loadline Co-pilot

Reads the orders, trips, tickets and payments a clerk would open — read-only — then does the typing.

orderstripsticketspaymentsWhatsAppemailco-pilot
writes
drafts the invoicesends itflags what it noticed

Integrations

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.

SAPWhatsAppM-PESAKenya Revenue Authority
Equity BankKCB BankOpenFreeMapPostgreSQLSageAsteriskMicrosoft SQL ServerAvery Weigh-Tronix

All users

The gate clerk, the rep, the driver, the accounts desk and the customer — everyone a load passes through, writing to one trip record.

tenant · embakasi-mills

TRIP KDC 789Z

Embakasi Mills to Kariobangi · dispatch 4471

5 writers

29 000

gross kg

12 000

tare kg

17 000

net kg

  1. Gracegate clerk

    weigh-intareticketpricing
    web
    GK
  2. Aminasales rep

    ordersprice listdispatch
    android
    AM
  3. Josephdriver

    delivery notephotoscustomers
    android
    JK
  4. Faithback office

    invoiceeTIMScredit notegate
    web
    FN
  5. Embakasi Traderscustomer

    tracksigncost
    portal
    ET
tenant · kariobangi-millersno row of it is reachable from here

Your storefront

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.

One loop. Five checkpoints.

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

  1. Invoice raisedMar 24 · 06:20INV-4482 · KES 1,284,500The invoice is written first and is what starts the job. Lines, terms and the customer's credit are settled before a bag moves.Invoice raised · INV-4482 · KES 1,284,500 · Embakasi Distributors · 14-day terms
  2. Order placedMar 24 · 06:28Embakasi Dist. · 500 bagsThe order opens off the back of the invoice, written at the customer on the rep's phone, inside the geofence, online or offline.New order · 500 bags maize flour off INV-4482 · Amina N. on the rep app
  3. DispatchedMar 24 · 07:04Nairobi plant · gate 2 · bridge 1The load plan is built and the truck booked onto the weighbridge. Out-of-tolerance loads are held at the gate until a supervisor signs.Trip dispatched · KDC 789Z · gate 2 · Joseph Kimani · weighbridge 1 at 07:40
  4. DeliveredMar 24 · 11:38Signed at the gate · in fullConfirmed inside the customer's geofence and signed for on the driver's phone. The eTIMS control number is issued at supply.Truck arrived · 42 m inside a 200 m fence · signed by D. Otieno · in full
  5. PaidMar 24 · 14:06M-Pesa QHX7 · matched in fullThe M-Pesa payment arrives with the invoice number on it and reconciles itself. What does not match goes to a queue with a name on it.M-Pesa received · QHX7RT2K9L · KES 1,284,500 · matched to INV-4482 automatically

5 events · append-only

A new standard for the yard. Nothing typed twice, nothing argued at month end.

01

Captured, never typed

Weights come off the indicator, orders off the geofence, payments off the rail. Nobody re-keys anything, so nothing drifts.

02

Compliance is not a project

eTIMS invoices are signed inside the statutory window, even the ones created offline. An outage delays a submission; it never loses one.

03

The difference gets a name

Every checkpoint writes an append-only event. Shrinkage stops being a month-end argument and becomes a trip you can open.

13 modules

Everything your business needs.
Nothing it doesn’t.

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.

Dispatch & Weighbridge

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

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.

Loadline Co-pilot

It does the desk work. You check it.

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.

Reads
Orders, trips, weighbridge tickets and payments, pulled read-only. The same records a clerk would open — and it does not guess at the rest.
Writes
Invoices drafted and delivered on the channel the customer already uses, WhatsApp or email, with the copy on file.
Flags
A route drifting, an account past its terms, a payment that will not match. Raised for you, never posted on its own.
Loadline Co-pilot

month-end · Kagio Millers

Close out August for Kagio Millers and send them the invoice.

  • Reading past orders14 orders since Juneorders
  • Working out weekly volume42.5 t / week, steadytrips
  • Pricing the products6 SKUs at contract ratesprice list
  • Drafting the invoiceINV-4482 · KES 1,284,500eTIMS

Kagio Millers took 42.5 tonnes a week through August (source: trips) — steady against July, with maize flour 50kg making up just over half of it. I priced the six SKUs at their contract rates (source: price list) and drafted the invoice. One thing worth your eye: route 4 variance is drifting, +1.8% over six trips.

INV-4482

KES 1,284,500 · eTIMS signed

Sent 08:43 · delivered

read 1,462 records · nothing posted
Follow-up questions

Open on desktop

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.

Download on mobile

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.

Your products, sold online.

Every manufacturer on Loadline gets a storefront: M-Pesa checkout, eTIMS receipts on every sale, and delivery your customers can track to the geofence.

  • B2B portal with credit terms for wholesalers
  • Public shop for walk-in buyers
  • Orders flow straight into dispatch
Visit the shop

loadline.africa/shop — a live render, not a screenshot.

One connector layer

Plugs into everything you already run.

Weighbridges, plant, your PBX, messaging gateways, the banks and your ERP — one interface, every payload stored as it arrived.

  • Kenya Revenue Authority
  • M-PESA
  • KCB Bank
  • Equity Bank
  • WhatsApp
  • Africa's
    Talking
  • Asterisk
  • Avery Weigh-Tronix
  • Production
    MES
  • SAP
  • Sage
  • OpenFreeMap

…and 40+ more behind the same interface.

No data leaves KenyaRaw payloads kept verbatim

Built for how Africa trades.

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.

One platform, every African market

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.

Cross-border by default

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.

Every rail money moves on

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.

Offline-first, not offline-tolerant

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.

Precise locations

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.

Automations that hold

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.

Every market's tax clock

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.

Priced in local currency

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.

Get started. Pay when it pays.

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.

Free

Run one yard and watch the loop close.

$0/ month

Get started
  • One site, one user
  • Dispatch and weighbridge, end to end
  • Orders, deliveries and proof of delivery
  • No card, no sales call
  • No co-pilot on this tier
Most popular

Team

The whole yard, and a co-pilot the team shares.

$100/ month

Get started

Everything in Free, plus:

  • Up to 5 users, shared across the workspace
  • 50,000 co-pilot tokens a month
  • Every module: Tax (eTIMS), Pay, Trade, Stores, Insight
  • Offline-first rep and driver apps
  • Top up tokens on demand

Custom

More sites, more seats, and the controls your CFO will sign.

Custom

Talk to us

Everything in Team, plus:

  • Unlimited users and sites
  • Connectors: ERP, weighbridge, PBX
  • Volume token pricing with a monthly spend cap
  • Invoicing and custom billing terms
  • Dedicated onboarding and a ready-to-sign DPA

Prices in USD, excluding VAT. Connectors and additional sites are quoted per integration.

Bring one yard. We'll close its loop.

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