13 modules

Everything your business needs.

Grouped by the department that signs the order. Each one replaces a specific part of the book at the gate, the phone call from the road, or the spreadsheet reconciled at month end — and nobody pays for what they do not run.

Operations

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.

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.

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

Field Sales

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.

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

Production Integration

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.

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

Stores & Requisitions

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.

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

Delivery & Tracking

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.

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

Finance

The statutory window and the bank. Invoices signed and control-numbered on time, and every shilling matched back to the order that earned it.

Tax (KRA eTIMS)

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.

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

Payments & Reconciliation

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.

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

Commerce

Every door an order can arrive through — the portal, the counter, the phone on the desk — and the message that follows it out.

B2B Customer Portal

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.

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

Commerce

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.

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

Call Centre & PBX

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.

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

Messaging

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.

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

Intelligence

What the records already know, read back to you: shrinkage with a name on it, and the desk work done before lunch.

Insight

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.

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

Loadline Co-pilot

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.

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