DELIVERY MANAGEMENT SOFTWARE · SOUTH AFRICA
See every delivery.
Run every driver.
All-in-one delivery management: every order and driver live on one screen,
live tracking for your customers, and driver pay settled to the bank file.
- del_01HXQ4T7courier_12IN TRANSIT
- del_01HXQ3R9courier_07AT THE DOOR
- del_01HXQ5K2—DISPATCHING…
- driver_03store_042AT STORE · 00:04:11
01 · WHERE THE MONEY LEAKS
A fleet run on spreadsheets
leaks quietly.
THE SPREADSHEET WAY
- Pay imported from CSV, month-end✗
- Cancelled trips silently dropped✗
- Guarantees paid on trust✗
- Presence asserted, not measured✗
- No audit trail on adjustments✗
- Reconciliation by hope✗
A shift guarantee is money paid for availability. If nobody can see whether the driver was actually there, the wage bill grows quietly — and nobody can say why.
THE JARVIS WAY
- Presence measured by the phone✓
- Attendance in minutes, not claims✓
- Payouts derived from ledgered events✓
- Guarantees gated on attendance✓
- Every action audited✓
- Ledger reconciles to zero✓
Nothing typed into a sheet. Every rand paid traces back to the trip or the shift that generated it.
If you pay drivers for availability, you should be able to see it.
02 · ONE SYSTEM, NOT SEVEN TOOLS
Retire the stack that
runs your drivers.
Dispatch on WhatsApp, shifts in a spreadsheet, payroll from a CSV, disputes from memory. Jarvis replaces the whole layer with one system — and everything it does is written down.
FLEET OPS TODAY
four tools · zero audit trail
FLEET OPS ON JARVIS
one system · everything ledgered
03 · THE ALL-IN-ONE PLATFORM
Your whole delivery operation,
in one system.
THE MANAGEMENT SYSTEM
For your operations.
Every delivery and every driver on a live map — where they are, what they're doing, updated by server push. Manual assignment when you want to override the engine, chat with drivers mid-delivery, and history with replayable route trails.
THE DRIVER APP
For your drivers.
Phone number in, SMS code, done — no passwords, signed in for weeks. Shift browsing and booking, live earnings, offers over a socket with push as backup, and support chat built in.
THE CUSTOMER TRACKING PAGE
For your customers.
A live tracking link with every delivery — the driver on a map, the ETA counting down. Your customers watch the order come to them instead of phoning you to ask where it is.
THE REPORTS
For your decisions.
Delivery history, attendance and reliability per driver, per-store and per-period reporting — and a payment package your bookkeeper can open on day one. Exportable, auditable, reconciled.
SCREENS FROM THE PLATFORM · DEMO DATA
Every driver on a live map.
Live, idle, on a trip, gone quiet — the whole fleet on one screen, updated by server push. Override the engine and assign by hand whenever you want to.
04 · ONE DELIVERY, END TO END
One delivery through your fleet,
created to reconciled.
-
01 · REQUEST
Your system says the word.
POST /v1/deliveriesfrom your stack — or a click in the dashboard. Pickup, dropoff, contact details. That's all we need. -
02 · QUOTE
Priced before it moves.
Fee, distance, ETA — returned in one call. fee: R ··· · 11.2 km · eta 34 min
-
03 · DISPATCH
Your longest-waiting driver gets the job.
An offer lands on their phone with a 30-second expiry. No response? It cascades to the next driver in your queue.
-
04 · PICKUP
Collected, confirmed.
The driver arrives at your store, collects the parcel, and marks pickup complete in the app. 14:02:11
-
05 · TRANSIT
Everyone can see it moving.
Location streams continuously. Your ops see the driver on the board; your customer watches a live tracking page.
-
06 · PROOF
Delivered means proven.
Time-stamped proof of delivery, behind a short-lived signed URL. 14:31:07 · POD captured
-
07 · SETTLE
The money side closes itself.
The trip generates a driver earning in a double-entry ledger. Payout runs produce the bank file, the accounting CSV, and per-driver invoices.
FEES SHOWN AS SPECIMENS · PRICING IS AGREED WHEN YOU COME ON BOARD
05 · THE QUEUE IS THE ALGORITHM
Fair to your drivers.
Legible to your ops.
Eligible drivers are ordered by how long they've been waiting; the longest-waiting driver gets the next job. Fairness is the explicit design goal — and because the rule is simple, every dispatch decision can be explained after the fact.
DISPATCH QUEUE · STORE_042
- 1driver_0700:14:32
- 2driver_1200:10:55
- 3driver_0300:07:11
- 4driver_2100:03:28
- 5driver_0900:01:04
offer expires in 30.0s
A phone that goes quiet is a driver that goes offline.
A driver whose phone hasn't checked in recently stops receiving offers — no flag can override reality. Ghost drivers can't hold up the queue.
Declining doesn't penalise you. Not responding does.
A driver who passes on a job keeps their place; one who goes silent moves to the back. Saying no is healthy. Going quiet is not.
Presence is measured, not claimed.
There is no "go online" button. At the store or on a trip means present — the phone's location says so, not the driver.
Every action is audited.
Manual reassignments, onboarding approvals, pay adjustments — each one written to an audit log with who, what, when.
06 · THE BACK OFFICE, HANDLED
Everything between
"new driver" and "paid driver".
Onboarding & KYC
A staged wizard — documents, background, vehicle, training, banking — with document capture and AI-assisted data extraction, so your team isn't retyping ID numbers. Approve, reject, rewind: all audited.
Shift scheduling
Build shifts per store, publish them to drivers' phones, duplicate a week in one click, and watch take-up live. Drivers book what suits them.
Attendance & reliability
Geofence presence turns shifts into minutes actually worked. Give-backs, no-shows, and a reliability score per driver — measured, not remembered.
Earnings, tips & guarantees
Per-trip rates you can override per store or per driver. Tips and bonuses land as itemised additions. Minimum-earnings guarantees per shift window — gated on the driver actually having been there.
Deductions & gear
Issue bags, jackets, phones — recover the cost in fixed instalments across pay runs. Every deduction itemised on the driver's statement.
Payout runs & bank export
Draft, approve, pay. The system computes what's owed, locks the earnings, and exports the bank EFT file, the accounting CSV, and per-driver PDF invoices — emailed out in one go.
WHAT YOUR DRIVERS GET
Know the shift.
Know the minimum.
Know the money.
Retention starts in the app. Drivers who can see their week before it starts — and their money while they earn it — stay. This is their side of Jarvis, exactly as it ships:
Shifts booked in advance.
They see the week's shifts in the app and book what suits them. They know when they're working before they leave home.
A quiet shift isn't an empty pocket.
Shifts can carry a guaranteed minimum — you set it. If the trips don't come, the guarantee is still there. They were there, and that counts.
Every rand, visible as it's earned.
Earnings build up in the app during the shift. Deductions are itemised line by line. Payday holds no surprises — for them or for you.
No games. Just the queue.
Longest wait gets the next job. Passing on an offer doesn't punish them. The phone knows who's at the store — there's no button to fight over.
NO PASSWORDS · OTP SIGN-IN · SIGNED IN FOR WEEKS · EARNINGS LIVE
07 · SETTLEMENT
Every rand, traceable
to the trip that earned it.
Trips, tips, guarantees, deductions — payout runs pull it all together, and one export gets you the bank EFT file, the accounting CSV, and per-driver invoices. Underneath it all: a double-entry ledger that reconciles — every period, every store.
JARVIS PRODUCES THE PAYMENT PACKAGE · YOUR BANK MOVES THE MONEY
MODE: TEST → MODE: LIVE
Ready to go live?
We onboard your fleet with you — drivers, stores, shifts and pay rules, set up together. You'll talk to the people who built the platform, not a sales layer. Your drivers, on rails.
SOUTH AFRICA · PRICED IN RAND · YOUR FLEET STAYS YOURS