How SC Tracker works
SC Tracker proves that goods left one place and arrived at another, in the right quantity, untampered — and keeps a permanent, tamper-evident record of every step. Every delivery is a three-party sign-off:
The sender declares
Operations creates the handover: what's moving, how much, its value, and where it's going.
The receiver confirms
The driver confirms receipt on their phone — quantity, GPS location, a photo, and a digital signature.
A witness co-signs
An independent party co-signs. A cryptographic receipt is sealed into the audit ledger — it can't be edited later.
The console
Managers dispatch deliveries, register sites, invite drivers, watch the live board, and handle incidents at app.sctracker.africa.
The field app
Drivers receive their work, confirm deliveries with GPS & photo, report incidents, and log stops — online or off.
The same app, inside the depot
Site staff check trucks at the gate, count stock blind, put deliveries away, request write-offs and hand over shifts — each tied to their one site.
New in this edition
November 2026 · console and app updates arrive automaticallySign in for the first time
Your account was created for you. The first time, set your own password with the “Forgot password” link — no password is ever shared by email or message.
Set your password
- Open app.sctracker.africa and choose Forgot password.
- Enter your work email — a set-password link arrives in your inbox.
- Choose a password, then sign in.
Add your sites & warehouses
Every depot, warehouse, and project site is registered once — with its GPS coordinates. Those coordinates are what let SC Tracker geofence arrivals, audit routes, and spot unusual stops automatically. A project site must have GPS.
Warehouse → Add warehouse
- Give it a name and pick a Type — Depot, Hub, Cold store, Retail, or Site (project/construction).
- Tap Capture GPS on this device while you're standing at the site, or type the latitude & longitude.
- Save. A site won't save without coordinates.
Invite your team, drivers & site staff
Staff sign in with a work email; drivers, receivers, witnesses and site staff pair their phone with a one-time code. Everyone gets a role that decides what they see and can do.
Staff → invite a field party
- Go to Staff & Drivers and add the person's name.
- For a driver, the console shows a pairing code and QR — share it with that driver.
- A new or replaced phone: an Admin or Logistics Manager issues a new pairing code for the same person. Pairing the new phone retires the old one at once, and the new phone registers its own signing key. Anything the old phone had not yet sent stays on it and goes out if that person pairs it again.
- Only an Admin or Logistics Manager can change a field party's phone or mobile money details. The change is on the ledger, the other managers are alerted, and payouts to a number changed in the last 24 hours wait for approval by someone else.
- You can invite receivers and witnesses the same way.
- For a storekeeper or guard, choose the role Warehouse (storekeeper / guard) and pick their site. Each site party is paired to exactly one warehouse, and nothing they do in the app can touch another site (section 31).
Give each person a role
- Admin — full access, including Settings and the team.
- Logistics Manager — the whole operation, minus owner-only billing.
- Procurement Officer — purchase orders, suppliers, orders & financials.
- Warehouse Staff — inventory, warehouses, distribution, handovers, and Site Operations (read, and issue gate passes).
- Driver — their own work, GPS & custody, in the app.
- Warehouse (storekeeper / guard) — a field role, in the app: gate checks, counts, put-aways, write-off requests and shifts at their one site. The roster on Staff & Drivers shows which site each one is paired to. An Admin can give a warehouse manager all sites — the app then shows a Switch site button and what they record goes to the site shown.
- Auditor — read-only view of the evidence (custody, incidents, claims, forensics) for an insurer or external reviewer. An Auditor can also be named a tip handler (section 21).
Send out a delivery
A delivery to a customer or driver. From Chain of Custody → Initiate handover, keep the default External delivery mode.
Fill in the delivery
- Shipment, product, quantity, and estimated value.
- From a registered site, to the receiving driver (a paired field party).
- Add the customer's email (for a tracking link) and their WhatsApp / phone number.
- Attach a photo of the loaded goods — recommended.
The optional fields that add proof
- Seal number — the tamper-evident seal you apply at dispatch. The receiver must read it back when the goods arrive; a different number disputes the delivery automatically and files a claim.
- Receiver phone — for a receiver with an ordinary phone. They get a one-time code by SMS and confirm by text or USSD (section 10).
- Funder / programme — groups the delivery on the donor assurance report (section 22).
- Transporter payment on proof — the Kwacha amount paid to the driver's mobile-money wallet once the receipt is sealed, while Pay-on-proof is on (section 23).
Move goods between your own places
Moving stock from a warehouse to your own project or construction site — including materials the company bought for that site — uses Internal transfer mode. Same signed, witnessed custody trail, but received by your own staff, with no external customer.
Switch to Internal transfer
- Pick the destination site (it must have GPS — see section 2).
- Choose the receiving staff (e.g. the site manager) and a witness (e.g. the site supervisor) — both confirm on their devices.
- No customer details needed. The signed receipt is your internal proof of the movement.
Inventory & stock levels updated
Track what's in each warehouse — quantities, value, and expiry dates — and know that no stock figure can be quietly typed over. SC Tracker raises an alert before something runs low or expires, and every change to a quantity carries a reason, a name and, above a value you set, a second Admin's approval.
Inventory → stock by warehouse
- See every product's quantity and value per warehouse at a glance.
- Set a reorder level per item — stock below it is flagged low.
- Add an expiry date for perishables — the expiry watch warns you as the date nears, and pings the notification bell (“view stock”).
- A new product starts at 0 and is stocked by a goods receipt, a put-away or a transfer. Only an Admin may enter an opening balance — it is recorded as a labelled adjustment in their name.
Excel — load your list, or save it
- Import from Excel loads a whole product list in one go. Press Download the template, type one product per row under the headings, then choose the file. An .xlsx or a .csv file works, up to 500 rows at a time.
- SC Tracker checks every row first and shows what is ready, what is already on file and what needs fixing, with the row number. Nothing is added while any row is wrong, and nothing is added until you press the green button.
- A product that is already on file is skipped: an import never changes a quantity or a price that is there. An opening quantity in the sheet needs an Admin, exactly as on the form.
- The same button loads suppliers (Procurement) and vehicles (Fleet & Vehicles). Imported suppliers arrive awaiting vetting, like any new supplier.
- Export to Excel on Inventory, Suppliers, Fleet and Chain of Custody saves the list on screen as an Excel file. Your file is read on your own computer: only the rows are sent to SC Tracker.
Adjust — the only way a desk changes a quantity
- Adjust on a product asks for the new quantity and a reason (count correction, damage, expiry, found, data error, other with a note). The change and its value are shown before you confirm.
- Below your adjustment approval threshold (MWK 500,000 unless Settings says otherwise) it applies at once. At or above it, the quantity does not move until an Admin who did not request it approves — the request sits under Stock adjustments with Approve / Reject, and can be withdrawn with a reason.
- Stock at a depot that has storekeepers on the app is never adjusted from a desk: losses are a write-off, found stock a put-away, a disputed figure a blind count — all from the site (section 11).
- Every adjustment is written to the tamper-evident ledger. Large ones, repeated ones on the same product, write-downs and any self-approval are scored by Fraud Sentinel (section 16).
- A product with stock or history and a warehouse with stock or site staff cannot be deleted — the record stays.
Distribution → transfers that move stock
- New transfer: pick the source and destination warehouse and the lines from the source's stock — you cannot send what the source does not have.
- Dispatch when the vehicle is loaded: the lines leave the source and an outbound gate pass is issued for the guard; the quantity and value in transit show on the page.
- At a destination with storekeepers the transfer appears under Transfers arriving on their phone, and their put-away completes it. A store without site staff receives it at the desk — never the person who dispatched it.
- A short or different arrival is flagged and operations are told. A transfer on the road is cancelled only by an Admin, with a reason, and the stock returns to the source. A status is never set by hand.
Procurement & purchase orders updated
Raise purchase orders to suppliers, have them approved, receive the goods where they actually arrive, and match the supplier's invoice — with values in Kwacha. The same discipline that guards a delivery now guards a purchase: who approved what, who received it, and what was billed are three different people and three records that must agree.
Procurement → raise a PO
- Pick a supplier, add line items with quantity and unit price — the total is worked out for you. A supplier typed in for the first time is added to your vendor list as unvetted.
- At or above your approval threshold (MWK 5,000,000 unless Settings says otherwise) the PO goes to awaiting approval. Below it, mark it sent or email the PDF to the supplier.
- An overdue PO pings the bell (“view purchase order”). A PO that has left draft is cancelled with a reason, never deleted — the record stays.
Approval — a different Admin, and it sticks to the figures
- An Admin who did not raise the PO approves it. The approval records the total, the supplier and the lines it covered.
- Change any of those afterwards and the approval is voided — the PO goes back to the queue and nothing can be sent or received against it until it is approved again.
- A PO at or above the threshold cannot be approved, sent or received for an unvetted supplier. An Admin vets new vendors on the Suppliers tab (approve, or block for good).
Receiving — where the goods are, by someone else
- At a warehouse with site staff on the app (section 11), click Expect delivery: an inbound gate pass is issued from the PO lines. The guard scans it when the supplier's truck arrives and checks every line; the storekeeper puts the PO away on the phone, which writes the goods receipt. The desk cannot receive there.
- At a store without site staff, a colleague — never the person who raised the PO — records what arrived at the desk, with batch and expiry.
- A shortfall against the PO, or a delivery refused at the gate, is flagged to operations before any stock moves.
Invoices — the three-way match
- Record the supplier's invoice against the received PO. SC Tracker compares it with the goods receipt: within 2% is matched; otherwise a variance; the same number or amount again from that supplier is a duplicate.
- An Admin who did not record it approves or rejects it. A flagged invoice can only be approved with a written reason.
Fleet & vehicles updated
Keep every vehicle's details, documents and service schedule in one place, and put the two places fleet money leaks — fuel and garage bills — under the same checks as a delivery. SC Tracker warns you before insurance or a certificate of fitness expires, or a service falls due; it ties every fill to a truck, an odometer and a receipt; and it holds a repair bill until an Admin who did not record it approves it.
Fleet & Vehicles → register a vehicle
- Add the registration, make and type, and assign the driver — every reassignment is kept as history, and the assigned driver is whose fuel and trips the truck is reconciled against.
- Record insurance, COF / road-worthiness and service dates — each one is tracked; alerts ping the bell (“open fleet”).
- A vehicle with fuel, repairs, trips or documents on file is archived, never deleted — the record stays.
Fuel — every fill checked against the truck
- The driver logs litres, the odometer and a photo of the receipt in the app; the app shows them their truck's last reading and what it usually needs.
- SC Tracker works out this fill's consumption from the kilometres since the previous fill, compares the litres with the vehicle's own history, checks the odometer only went forward, and compares the odometer advance with how far the phone actually travelled.
- An odometer that goes backwards, kilometres the phone never travelled, more litres than the truck needs, or a missing receipt are flagged on the Fleet page and scored in Fraud Sentinel (section 16). The receipt is one click away.
Maintenance — a garage bill is a purchase
- The garage is a supplier on your vendor list (section 7); a new name starts unvetted and a blocked one is refused.
- A bill at or above your maintenance approval threshold (MWK 1,000,000 unless Settings says otherwise) waits for an Admin who did not record it, and does not count in cost per km until approved. The garage must be vetted first.
- A third repair of the same kind on one truck in 90 days, or a cost well above your usual, is flagged and needs a written reason to approve. Entries are cancelled with a reason, never deleted.
Vehicle trackers — the vehicle reports by itself
- Under Vehicle trackers, type the tracker's serial number or IMEI, choose the vehicle and press Register and issue key. The key is shown once: copy it into the tracker, or into the tracking platform it reports through.
- The tracker sends its position to the address shown on the page, with its key. The vehicle comes from the key: nothing in a message can change it. Revoke stops a key at once, and removing a vehicle from the register closes its tracker.
- A platform that forwards many trackers through one address uses a feed: register each tracker, then open a feed. A feed can only report for trackers you registered here.
- The vehicle appears on the live map with its number plate. A trip on which the driver's phone reported nothing is audited against the vehicle's own trail (section 12). Live detour alerts still come from the driver's phone.
- A tracker must be able to send a web request, or report through a platform that can. Many need a small adapter, so ask us before you buy. Vehicle trackers need GPS tracking on your plan.
Share the tracking link on WhatsApp
On any active external delivery, one tap opens WhatsApp with the customer's number and a ready-to-send tracking message. You send it from your own WhatsApp — no extra setup, no cost.
Tap “Share on WhatsApp”
- On the handover card, tap 🟢 Share on WhatsApp.
- WhatsApp opens with the customer's number and the message pre-filled — just press send.
- No phone number on file? WhatsApp opens and lets you pick the contact.
Confirm by SMS or USSD — for receivers without a smartphone
A receiver with an ordinary phone confirms a delivery by text or by dialling a USSD menu. Add their number when you initiate; SC Tracker texts them a one-time code, and when the goods arrive they reply with it. The result is the same signed receipt, witnesses, claims and alerts as a smartphone sign-off — the receipt simply records confirmed via SMS from +265 99•• ••• 567, one-time code verified instead of a device signature.
Initiate with a receiver phone
- Type the number in Receiver phone on the initiate form, or keep it on the receiver's Staff record once.
- The handover card shows the code's status; Resend code sends a fresh one — to a corrected number if needed.
- The code works only from the number it was sent to, locks after five wrong tries, and can be used once.
What the receiver sends
| Reply | Effect |
|---|---|
OK 482913 40 | Confirms 40 units received. Add the seal number after the quantity when the consignment was sealed. |
NO 482913 two bags torn | Disputes the delivery and files a claim with that reason. |
STATUS 482913 | Where the delivery stands. |
HELP | The instructions again. Chichewa INDE / AYI work in place of OK / NO. |
Site Operations — what happens inside each warehouse
Most losses happen inside the depot, not on the road. Site Operations is the office view of six things your storekeepers and guards do on their phones: gate passes and gate checks, the gate log, blind cycle counts, put-aways, write-offs and shift custody. Anything that does not add up becomes an incident on its own.
Set a site up
- Register the warehouse with its GPS (section 2).
- Invite each storekeeper and guard from Staff with the role Warehouse and pick the site (section 3).
- Add the site's stock lines in Inventory so counts, put-aways and write-offs have something to act on.
Gate passes & gate checks
- Issue a pass for every load leaving (or arriving): reference, vehicle, driver, seal, and every line with its quantity. Print the QR or let the guard look it up.
- Deliveries get their pass on their own. When a handover is initiated from one of your warehouses and that site has gate staff on the app, the exit gate pass is issued with it, written from the dispatch itself: product, quantity, vehicle and seal. The driver’s app shows it (Show gate pass), and the delivery card in the console carries it with a Show QR button. A driver cannot create one: only the office’s dispatch does. Purchase orders (Expect delivery) and transfers (Dispatch) issue theirs the same way.
- At the gate the guard scans the pass and reads back the vehicle, the seal and every line, then allows or refuses the exit. A pass works once.
- Any gap — expired pass, wrong vehicle, wrong or unread seal, a short or extra line — raises a Gate discrepancy incident: high if the goods still left, medium if the guard refused.
Blind cycle counts
- Schedule counts by product or at random, for a named counter or whoever the system picks. Two-person counts send the same line to two people independently.
- The counter sees the product, never the book figure, and is told only “recorded”.
- A variance of 2 % or more (your operator can tune this), or two counters disagreeing, opens a Stock variance incident attributed to the count — critical above MWK 1,000,000 of value by default.
Put-aways, write-offs & shifts
- Put-aways — the storekeeper receives a confirmed delivery, a supplier delivery on a purchase order or a transfer from another warehouse into stock; a put-away that differs from what was confirmed, ordered or sent is flagged. One put-away per delivery, and the only way stock arrives at a staffed site.
- Write-offs — damage, expiry, spoilage or theft is requested from the phone with a photo; stock moves only when an Admin or Logistics Manager approves, and the requester can never approve their own.
- Shifts — opened and closed with a checklist and photos; keys are handed to a named colleague who accepts them. A “not OK” on any check, or a shift still open after 14 hours, alerts operations. The checks are yours to set (Shifts → Opening and closing checklists → Edit, Admin or Logistics Manager): add, rename or remove items for the whole organisation or for one site, up to 20 per list; the app shows whatever you set. Nothing is removed quietly: the editor warns before a removal is saved, and every change is written to the ledger under your name, naming each item removed, added or reworded. Change history under the lists shows it. A removal also alerts Admins and Logistics Managers at once (bell, email, and phones with alerts switched on), naming the check and who removed it.
- Gate log — every vehicle and visitor in and out, with flags for no pass and refused exit.
GPS tracking, wallboard & route audit
See where your vehicles have reported from, watch operations on one board, and let SC Tracker flag trouble for you — trucks that leave the expected route, and trucks that stop too long where they shouldn't.
Live GPS tracking
- Open GPS Tracking to see each vehicle's most recent reported position on a map — as long as the driver's app is open with location switched on.
- On Android, a fix that comes from a fake-GPS app is flagged red — a sign of spoofing.
- Arrivals and departures at a site are logged from the GPS the app sends (geofenced) — a hands-free record of when a driver reached the site.
- A vehicle with its own tracker registered (section 8) shows on the same map as a number plate, whether or not the driver's app is open. Click the plate to trace its last 24 hours.
The live Wallboard
- Open Ops Wallboard for live trucks, active deliveries, and alerts.
- Tap ⛶ Fullscreen to fill a TV or projector at the depot.
- Route deviations and unusual stops show up as alerts shortly after they're detected. Every excursion off the route is now also an incident and a record on the Fleet page's Route watch that operations acknowledge. The driver's phone asks them at that moment — “we noticed you are off the expected route, is everything okay?” — with one-tap answers (section 30); road closed, roadblock, diversion, checkpoint or breakdown marks it justified, and the answer lands on the incident. The record closes when the truck is back on the route and opens again if it leaves a second time.
- Driver check-ins on the Fleet page show who was asked what, what they answered and how long they took. No answer within 10 minutes is escalated to you and opens an incident; “fuel” with no fill logged, the same excuse every trip, a rest at 2 a.m. or an answer only after escalation are scored in Fraud Sentinel. A stop drivers keep explaining as a checkpoint or a fuel station becomes a known stop nobody is asked about again.
- Fake GPS on a live delivery opens a high incident and a spoofing record the same way.
- Tracker dark — a truck on an active delivery that stops reporting for 20 minutes (by default) raises an alert, because a tracker switched off mid-route is itself a warning sign.
- Risk map — corridor hotspots built from anonymised incidents across SC Tracker, never naming an organisation, show on the GPS layer and the wallboard, so a route through a known trouble spot is briefed rather than discovered.
Trip audit & justified stops
- In GPS → Trip audit, compare a trip's expected route (blue) against where the truck actually went (green). How far off counts as a deviation is a setting per organisation and widens on long hauls.
- When road routing is unavailable, SC Tracker still watches the straight line to the destination with a wider allowance — a truck bound for another district is caught either way.
- An unexplained long stop away from any site is flagged — and the driver's phone asks them about those minutes. A logged reason (lunch, roadblock, breakdown) or a check-in answer records it quietly instead.
Cold chain
For goods that spoil when they warm up or freeze: vaccines, medicines, fresh and frozen food. Every fridge, freezer, cold room and reefer is registered with the safe range it must hold. Readings come from your storekeepers' rounds on the phone, each with a photo of the thermometer, or from loggers you register. Nothing is typed in at a desk, and whoever sends a reading cannot choose what counts as safe.
Set it up
- Safe ranges: you start with three profiles — Vaccines and medicines (2 to 8 °C), Chilled food (0 to 5 °C) and Frozen goods (−18 °C or colder). Each also sets how long a unit may sit outside the range before it is serious. Only an Admin changes them; widening a range is recorded as a loosening and alerts operations.
- Units → Register a unit (Admin or Logistics Manager): the name, what it is, the warehouse it stands in (or the vehicle, for a reefer), its profile and how many rounds a day. From then on it is watched.
- The storekeeper or guard paired to that warehouse finds the unit under Cold rounds in the app (section 33).
- Load sample data (top right) fills the page with five example units, their readings, rounds, loggers and two excursions, so you can see how it works before registering your own. Everything it adds is marked Sample, raises no alert, reaches no phone, and goes again with Clear sample data.
Rounds and readings
- Two rounds a day by default, morning (06:00 to 10:00) and afternoon (14:00 to 18:00). The storekeeper reads the display, types the figure and photographs the display. A reading without a photo is refused, and it can only be logged for a unit at their own site.
- A round nobody did while the site was open on shift is a missed round: operations are alerted. With no shift open it is shown as unattended instead, so a weekend does not flood you.
- A reading logged long after it was taken is marked late. Ten identical readings in a row by one person go to Fraud Sentinel: that is how a chart is filled in without looking at the fridge.
- Chart and readings on a unit draws its temperature against the safe range over 24 hours, 7 days or 30 days. The line turns red where it leaves the range, excursions are shaded, missed rounds are marked, and hours with no reading are left as gaps. Readings taken by hand are dots: click one to see the photo of the thermometer. Each excursion has a Chart of its own, with an hour either side.
Excursions
- One record per spell outside the range, however many readings it took: when it began, the worst temperature, how long, who was in charge (the shift holder, or the driver of the vehicle) and what they did about it.
- No news is bad news. If no in-range reading closes it within the profile's grace period, the excursion becomes serious on its own: an incident, an alert, a Fraud Sentinel flag. Freezing a freeze-sensitive product is serious at once.
- An Admin or Logistics Manager then decides what happens to the goods — release, quarantine or discard — with the reason on the ledger. Goods cannot be released while the unit is still out of range, and the site that was judged cannot decide.
- A spoilage write-off (section 11) shows the approver what the cold-chain record at that site says: the excursion behind it, or none at all.
Loggers, when you have them
- Loggers → Register: enter the logger's serial number and the unit it sits in. It gets its own key, shown once. The logger, or the gateway it reports through, sends readings with that key.
- The unit and the safe range come from the key. Nothing in the logger's message can change them, and a key cannot write to another unit.
- A logger that goes quiet is alerted: switched off, unplugged or moved, it records nothing. Revoke stops a key at once.
Cold deliveries
- On Initiate handover (section 4) choose the Cold chain profile and enter the temperature read at loading. The safe range travels with the delivery.
- The receiver must enter the temperature at receipt, as they read a seal back. Out of range, the delivery is marked, an incident is raised and operations are alerted. A delivery confirmed by SMS is marked “not read at receipt”.
Incidents, cases & emergencies
When a driver reports a problem — a breakdown, theft, accident, delay — it lands in Incidents and pings the notification bell. Open the case to work it as a conversation with the driver, right through to resolution. The system raises incidents of its own too — gate discrepancies, stock variances, seal mismatches — and emergencies arrive here with a siren.
Open the case & reply
- Click the bell alert (or the Incidents tab, grouped by driver) to open the case.
- See the report, photos and location, then assign it, post updates to the driver, and mark it resolved.
- The driver gets each update on their phone and can acknowledge the resolution — closing the loop.
Emergency alerts — duress and site threats
- A driver who is being robbed, hijacked or forced off route holds the red button in the app for two seconds. A critical duress incident is raised with their location and the active delivery; their phone stays silent.
- A storekeeper or guard holds the same button at the depot and it becomes a site threat for that warehouse. Operations can raise one too — 🚨 Raise site threat at the top of Incidents, pick the site, add a note.
- Every open console shows the alert at once. Switch on Alert sound & voice in Settings (per browser — ideal for the depot PC and the wallboard) and a siren sounds and the alert is read aloud, “Emergency. Chikondi Mwale reports a threat at Kanengo depot”, until someone acknowledges it. Managers are emailed; on-call numbers get an SMS when configured.
- Away from the screen? Switch on Phone & lock-screen alerts in Settings on your phone. Emergencies then arrive as a notification even when the browser is closed — a long vibration, the phone's alert sound, and it stays on the lock screen until you open it; a tap opens the incident. Android works straight away; on iPhone add SC Tracker to the Home Screen first (Share → Add to Home Screen). Use Send me a test to check the sound on your handset. Warehouse managers who oversee all sites also get these on the field app.
Insurance claims
When a delivery is disputed or arrives short, SC Tracker raises a claim automatically with the evidence attached — ready for your adjuster to review, decide, and record the settlement. Every step is written to the ledger.
Claims file themselves
- A dispute, or a quantity variance over your threshold, raises a claim automatically.
- The evidence is pre-attached — the photos, the receipt number, GPS, and the tamper-evident receipt hash.
Work it to settlement
- Open Insurance Claims, assign an adjuster, and investigate.
- Approve or deny, then record the payout — every transition is written to the audit ledger.
Fraud Sentinel
SC Tracker reads every operation as it happens — dispatches, fuel logs, invoices, PO approvals, stock adjustments, route deviations, gate passes, cold-chain overrides, logins — and scores anything that looks wrong. Each flag is explainable (it tells you why), carries an estimated Kwacha exposure, and is written to the tamper-evident ledger.
What it catches
- Amount spikes & drops — a fuel log, invoice or PO far outside the normal range for that activity.
- Duplicate invoices — the same invoice number and amount submitted twice.
- Fuel siphoning — fuel logged well over what the trip should use, especially if it repeats.
- Kickback pattern — the same officer approving the same supplier again and again.
- Route deviations and after-hours activity — late-night dispatches or stock changes, repeated.
- Cold-chain overrides, and any action by a banned actor.
What it does
- Scores the event and sets a severity — low → critical — with a recommendation: monitor, flag, freeze or boot.
- A critical score can auto-boot (ban) the actor; you can reinstate from the console.
- Tune the sensitivity in Settings — every threshold change is itself ledgered.
- Judge every flag — Confirmed, False alarm or Unsure, one tap under the flag (Admin or Logistics Manager). This is what Adaptive Defence learns from: a rule you keep confirming scores harder on its own, a rule that cries wolf becomes a proposal to quieten (section 17). Give each resolved incident an outcome the same way.
Adaptive Defence
People will always find a new way round a control. Adaptive Defence is how SC Tracker learns from what you confirm and what you dismiss, learns each depot's, driver's and supplier's own normal, looks for the classic ways round a control, and proposes the tightening that would have caught it. Everything it does is explainable, on the ledger and reversible with one tap — and it never loosens a control on its own.
What it learns from
- Your judgements: Confirmed / False alarm / Unsure on every Fraud Sentinel flag (section 16) and an outcome on every resolved incident (section 14).
- The field's answers to check-ins (section 30), and your own records: adjustments, purchase orders, garage bills, counts, put-aways, fuel, trips.
- Each entity's own normal — this depot's adjustment values, this truck's fuel per kilometre, this approver's speed — over 180 days. A jump above its own history is a finding, measured against itself, not a global number.
What it finds
- Structuring — adjustments, POs or garage bills kept just under an approval line by one person. Pairing — one approver tied to one supplier. Vendor churn, weekend dispatches that arrive short, repeat count gaps at a site, unanswered check-ins, fuel over-fills, a reviewer who closes everything as unsure, a rule that keeps crying wolf.
- Every finding names the control that should have caught it and comes with a proposal: lower that threshold from X to Y, put this depot on the watchlist with weekly blind counts, make this rule score harder.
Two lanes, your bounds
- Inbox: an Admin accepts or rejects each proposal. Accepting applies it and puts it on the ledger; Revert undoes it with one tap. A rejection is remembered as accepted risk for 90 days, so the same pattern is not proposed again.
- Auto lane (off until an Admin switches it on): SC Tracker applies a proposal itself the moment it is made — but only a tightening, and never below the floor you set for one step. A loosening is never automatic.
- Watchlist: heightened scrutiny, time-boxed. Sentinel scores the person harder, a driver's check-ins allow half the time, a supplier's POs need approval whatever the value, a depot gets three blind counts a week.
It tests itself, explains itself, and reports
- Explain on any finding writes it out in plain language: what happened, which control should have caught it and why it did not, why it matters, what to check by hand. With the AI connected it is written by the model and counts as an AI Investigator question; without, a rule-based summary.
- Self-test (weekly, or “Run self-test now”): a dozen ways an insider might beat your controls — split purchasing, adjustments just under the line, a steady fuel skim, detours inside the corridor, counts a little short every time — are evaluated against your current settings, never against live data. Each is blocked, detected (with the score it would get) or undetected; the undetected ones become findings and, where a setting would have caught them, proposals. Those proposals always wait for an Admin, even with the auto lane on, because a simulation is not evidence.
- Posture report: one signed PDF per month — flags judged and precision, what changed and who decided it, findings, the watchlist, rule calibration, self-tests. Its footer carries a public verify link, so an edited copy can be told from the original.
- Network immunity: which tactics other SC Tracker organisations are seeing this quarter, as anonymised counts only — never names or figures, and only once two other organisations have seen it. A tactic others tightened a control for arrives here as high. Switch it off in Auto lane if you prefer not to share.
AI Investigator
Ask about your operation in plain language — “which suppliers are overcharging?”, “show me risky drivers this week”, “what happened with SHP-4471?” — and get an answer grounded in your own data, with the records it used. It remembers the conversation, so you can keep digging.
Ask, then follow up
- Type a question; the answer cites the shipments, POs or anomalies behind it.
- Ask a follow-up — it keeps the thread, so “and last month?” just works.
- It reads your data to answer; it never changes anything on its own.
Forensic Investigator
Reconstruct the full, ordered evidence chain for any shipment, receipt, actor or case — every event in sequence, each with its ledger hash — and export it as a case file for an auditor, insurer or court.
Trace it end to end
- Search by shipment, receipt, person or case to pull its complete timeline.
- Each step shows who did what, where and when — with the hash that seals it.
- Because the chain is hash-linked, a single altered record breaks the chain and shows up immediately.
Verify a receipt
Every signed receipt can be checked by anyone — a customer, an auditor, an insurer — with no account. The verify page recomputes the hash chain, checks the digital signature against the signer's public key, and confirms the independent timestamp. If a receipt is genuine and unaltered, it says so; if a single character was changed, it fails.
Scan the QR, or open the link
- Each receipt carries a QR code — scanning it opens the public verify page.
- The page shows a green tick — Authentic receipt — and then the goods, place, time, sender, receiver and witnesses on record. An altered or forged code fails the check.
- Share the link with a customer or insurer so they can confirm it themselves.
- The page also shows the ledger anchor behind the receipt: a timestamp from an independent RFC-3161 authority and, once the hourly publication has caught up, the Bitcoin block it was sealed in — proof the receipt existed by that time that does not depend on our servers.
- Issued documents verify the same way: a donor assurance report at /verify/report/… and an EUDR due diligence statement at /verify/dds/…, both printed on the PDF (section 22).
Anonymous tip-off channel
Staff, drivers, agents and the public can report theft, fraud, bribery, safety problems and misconduct without giving a name — and still get an answer. Every organisation has its own channel, switched off until an Admin turns it on and names the people allowed to read tips.
Settings → Anonymous tip-off channel (Admin)
- Switch the channel On, set a short SMS / USSD code for your organisation and an escalation email (an auditor or funder).
- Name up to five tip handlers — the only people who can read a tip. Choose people a tipster would trust and who are unlikely to be the subject of a report; an external Auditor login can be one.
- Print the poster: the QR and link, the SMS code and the USSD option on one page for the depot wall. If a link leaks, Rotate link and reprint; tips already received are untouched.
No internet? SMS TIP KANENGO what you saw
or dial the USSD menu → 4. Report wrongdoing
What the tipster sees
- The poster link opens a plain page — no login, no cookie, no location. They pick a category, write what happened, add up to three photos (camera details, time and GPS are stripped before storage), and optionally where, when and a way to be reached.
- They get a receipt code such as SP6T-EPNM. It is the only way back to the report: with it they read the status and the outcome, see questions from the handlers and answer them — still anonymous. It cannot be recovered if lost, because nothing links it to a person.
- By phone: text TIP KANENGO what you saw, or dial the USSD menu and choose 4. Report wrongdoing. TIP STATUS KANENGO SP6T-EPNM reads the status back.
What a handler does — the Tip-offs page
- Open a tip (decrypted on the server; the opening is ledgered), send a question the tipster reads with their code, mark investigating.
- Open an incident — written in the handler's own words; the tip's text, photos and contact never leave the sealed record. The incident is then worked like any other.
- Escalate sends a notice (no contents) to the escalation email. Close with outcome tells the tipster what was found or done. A later message from the tipster reopens it.
Donor assurance report & EUDR due diligence
Two documents your funders and buyers ask for, assembled from custody data you already hold. Both are issued documents: the PDF carries an id and a digest, and anyone can check at a public link that SC Tracker really issued it — an edited PDF fails.
Chain of Custody → Donor assurance report
- Tag deliveries with a Funder / programme when you initiate them (section 4).
- Prepare a report: pick the programme and the period, Preview figures, then Issue PDF.
- The report states deliveries, verified deliveries, disputes, variances of 2 % or more, seal mismatches, phone confirmations, value declared and verified, claims and transporter payouts — and the integrity of the record itself: the ledger recomputed, every receipt recomputed, the anchors published in the period. Each delivery carries a receipt QR.
- Tips are counted (received, open, closed) and nothing else about them appears.
EUDR origin plots & due diligence statement
- From 30 December 2026 an operator placing coffee, soya, wood, rubber, cocoa, palm oil or cattle products on the EU market needs the geolocation of every plot the commodity was produced on, with a due diligence statement.
- On the shipment's card open 🌍 EUDR origin plots → Add plot: commodity, producer, district, area, harvest window, and a point (up to 4 ha) or a polygon (required above 4 ha). Points over 4 ha are refused; a polygon's measured area is checked against the stated one.
- Issue due diligence statement (PDF) bundles the plots, the whole custody chain of the shipment with receipt fingerprints and the risk checks — plots geolocated, polygons where required, one commodity, chain complete and verified, receipts recompute, no dispute or seal mismatch, producers identified. It concludes negligible risk only when every check passes.
- Plots GeoJSON is the file the EU Information System accepts.
Pay-on-proof — the receipt releases the payment
A sealed, witnessed receipt releases the transporter's payment to their Airtel Money or TNM Mpamba wallet through PayChangu. Honest, on-time confirmation becomes the thing that gets people paid — and nothing is paid without a receipt.
Set the rules (Admin)
- Pay-on-proof in the menu: switch it on, set the flat amount per delivery, the auto-approve threshold, the daily cap (MWK 500,000 by default) and who is paid — the receiver (the driver who took custody) or the sender.
- On Staff & Drivers, record each driver's wallet: phone number and operator.
- A delivery can carry its own amount on the initiate form; it overrides the flat amount.
How a payout runs
- Receipt sealed → one payout for that handover, never two.
- At or below the threshold it is approved and sent at once; above it, it waits for a second Admin — not the one who set the rules (four eyes). Over the daily cap, or with no wallet on file, it is blocked until you fix and retry.
- PayChangu's reference and status are stored and re-read until completed or failed; every change is on the ledger.
Data protection — the Malawi Data Protection Act, 2024
Drivers' locations, phone numbers and photos of receipts are personal data. Settings → Data protection (Admin) holds the tools the Act expects you to have, and everything done there is written to the ledger.
Exports, access and erasure
- Export everything — all your organisation's data as JSON, photos optional, for portability or an audit (one export per ten minutes).
- DPA pack — a PDF of your records of processing, sub-processors, security measures, retention, rights procedure, breach procedure and open items, generated from how your organisation is actually configured.
- Subject access — everything held about one party (driver, receiver, witness) as JSON, to answer an access request.
- Erase a party — removes their name and contact details, deletes location history, devices and codes. Custody records, receipts, signatures and ledger entries are kept for seven years under the legal-obligation basis — the ledger is tamper-evident and cannot be edited. A party on an open delivery cannot be erased until it closes.
Breach register — the 72-hour clock
- The moment a breach is discovered — a lost handset, a compromised account — Log a breach. Every Admin is alerted and the register shows the MACRA deadline, 72 hours from discovery.
- Contain first: remove the party on Staff (that revokes the phone's access at once) or deactivate the account. Then press MACRA notified now and, if the risk to people is high, People notified now; add notes; Close.
- The register and the ledger entries are your evidence of due process; the DPA pack lists any overdue notification as an open item.
Plans, trial & billing
A new organisation starts with a short free trial — enough to run a full delivery end to end. After that a plan keeps the service running. Pay monthly, or annually and get two months free. Pilot organisations are set up by us directly, so there's nothing to pay during the pilot.
Four tiers
- Starter — MWK 120,000/mo · 2 office users · up to 159 deliveries · 15 AI questions.
- Growth — MWK 350,000/mo · 5 office users · up to 550 deliveries · 100 AI questions.
- Business — MWK 900,000/mo · 25 office users · up to 2,000 deliveries · unlimited AI.
- Enterprise — unlimited, talk to us for pricing.
- Every plan has the core: signed handovers and receipts, the ledger, Fraud Sentinel, incidents and the emergency button, inventory, orders and the field app. Starter has 1 site.
- Growth adds Site Operations, Procurement, Distribution, Fleet, GPS tracking and check-ins, the customer tracking link, Cold Chain, Insurance Claims, the Forensic Investigator, analytics and scorecards, and Word copies of certificates. Up to 3 sites.
- Business adds Adaptive Defence, the Wallboard, Pay-on-proof, donor assurance and EUDR, the tip-off channel and the baseline monitor. Unlimited sites.
- A module your plan does not include shows a lock in the menu, and its page says which plan has it. Nothing is deleted when a module is locked. A free trial has every module open.
- Office users are console logins; drivers, storekeepers and guards on the phone app are not counted. When the seats are full, deactivate a user or move up a plan to add another.
See your usage
- Settings → Billing shows your current plan and how much of the month you've used.
- Upgrade or switch to annual there. Today we invoice you directly, in Malawi kwacha. Online payment by card and mobile money through PayChangu is being switched on.
Install the app & pair your phone
A one-time setup. After this, most updates arrive automatically over the air — only the occasional larger update needs a fresh install.
Scan to install
Point your phone camera at the QR code from your manager. It downloads the app — use Wi-Fi, it's a large file. Tap the downloaded file, allow “install from this source”, then Install.
scan → download → install
Enter your pairing code
- Open the app and type the code your manager gave you (or scan its QR).
- Your phone is now linked — you'll see your assigned work under My Work.
- Allow location and camera when asked — both are needed to confirm deliveries.
Confirm a delivery
When goods reach you, confirm receipt. This is the signed proof that you received them — in the right amount, at the right place.
My Work → tap the handover
- Leaving a depot with a guard? Tap Show gate pass under the handover and hold the QR up at the gate. The guard checks the load against it, and it works once.
- Check the product and enter the quantity you actually received.
- Tap to capture GPS and take a photo of the goods.
- If it is a cold consignment, read the thermometer and type the temperature you see. The app shows the safe range; a reading outside it is reported to operations.
- If the consignment was sealed, type the seal number you see on the truck — read it off the seal, don't copy it from paperwork. A different number disputes the delivery automatically.
- Sign and confirm. A witness co-signs, and the receipt is sealed.
Report a problem, log a stop — or call for help
Three actions on My Work keep operations informed, keep you in the clear, and get help to you fast.
🚨 Report incident
For a breakdown, theft, accident, or serious delay. Pick the type and severity, add a note, and attach a photo. It reaches operations instantly with your location.
⏸ Log a stop
Stopping for a while — lunch, rest, an overnight, a roadblock, refuelling? Tap Log a stop and pick the reason. This tells operations why you stopped, so your rest is not flagged as a suspicious delay.
🆘 HOLD for emergency
Being robbed, hijacked or forced off your route? Press and hold the red button for two seconds. Operations get a critical alert with your location at once — a siren on their screens, an email to managers, an SMS to the on-call number. Your phone stays silent, and it works without signal: the alert goes the moment you reconnect.
Follow up on what you reported
Everything you report has a home in My Incidents, where you can watch operations handle it — and confirm when it's sorted.
My Incidents → open a case
- See the conversation with operations — assignments, replies, status changes.
- Add your own updates at any time.
- When operations mark it resolved, tap Acknowledge resolution to close it.
When the app asks you something
Sometimes the app notices something about your work before anyone else does — a long stop, a route it did not expect, a count that does not match, a put-away that differs. Instead of only telling the office, it asks you, there and then. A quick honest answer takes one tap and keeps you in the clear.
What it asks about
- Drivers: “You have been stopped for about 40 minutes — is everything okay?” or “You are about 12 km off the expected route — is everything okay?”. Answer within 10 minutes.
- Storekeepers and guards: “Your count of Maize 50kg does not match our records — can you tell us anything that might explain it?” or “What you put away for SHP-2026-211 differs from what was sent — what happened?”. Answer within 30 minutes. The question never shows you the book figure.
- Nothing is assumed. A traffic jam, a police checkpoint, a fuel stop, a rest, a diversion, damaged stock set aside — these are normal, and saying so is all that is needed.
How to answer
- The card appears over whatever screen is open, or from a notification. Tap the answer that fits, add a note if you like, Send answer. If you are driving, pull over first — the card waits.
- Answer later hides the card for a few minutes. If you do not answer in time, operations are told and may call you; you can still answer afterwards, and it is recorded as late.
- Using Log a stop instead also answers the question — nobody is escalated for taking the old route.
- Your answer goes on the record, is sent even if you are offline at the time, and the office sees it next to the trip or the count.
“I am not safe”
Every card has this line at the bottom. If you are being robbed, hijacked or forced and cannot speak freely, tap it and confirm. To anyone watching your phone it looks like you answered the question; operations get a critical alert with your position at once, exactly like holding the red button.
Your site & your shift
Install and pair the app exactly like a driver (section 26). Because your manager invited you with the role Warehouse and your site, the app opens on your site's home screen instead of My Work. The site you are paired to is named at the top; everything you do is tied to it and recorded under your name.
The site home
- Six tools: Gate check, Gate log, Counts, Receive into stock, Write-off and Shift — plus Cold rounds where your site has fridges or a cold room, Report incident and the red emergency button.
- Everything works offline: actions queue and send in order when signal returns.
- Warehouse managers: if an Admin gave you all sites, the home screen shows your home site and a Switch site button. Pick the depot you are standing in — the tools, lists and everything you record then belong to that site, and the screen says so. Sync any waiting items before you switch.
Open and close your shift
- Open with the checklist — doors and gate were locked, seals on stock areas intact, alarm set and disarmed normally, no forced entry, stock area as it was left, CCTV and lights working — and a photo or two. A “not OK” tells operations immediately. Your office decides what the list asks, for the whole organisation or for your site; the app shows their wording.
- Close with the same checklist and photos, and hand the keys to a named colleague, who accepts them on their phone. The office sees who held the site at every hour.
- A shift still open after 14 hours is flagged as overdue.
🆘 HOLD for emergency at this site
A robbery or break-in in progress: hold the red button for two seconds. It raises a site threat for your warehouse — siren and spoken alert on every console, email to managers, SMS to the on-call number — with or without a GPS fix. Your phone stays silent.
Gate check & gate log
Nothing leaves without a pass, and the pass is checked against the truck — not the paperwork.
Gate check — scan the pass
- Tap Gate check and scan the QR on the gate pass (or type its code). The pass shows the vehicle, the seal and every line.
- Read back what you see: the registration on the truck, the number on the seal itself (don't copy it from the pass), and the quantity you count for each line. Add a photo and a note.
- Choose Allow or Refuse. The app tells you on the spot if anything differs; operations get an incident either way, and the pass cannot be used again.
Gate log — everyone in and out
- Log every vehicle and visitor: in or out, registration or name, company, purpose.
- Flag no pass when a load tries to leave without one, or refused exit — both reach operations as incidents.
Counts, put-aways & write-offs
Stock moves in three ways from your phone — and only these three. Everything else is a variance the system will notice.
Blind counts
- Counts lists what you have been asked to count — the product, never the book figure. Count it, enter the number, add a photo if you like, submit.
- You are told only that the count was recorded. If it differs from the books, the office investigates the stock, not you — the incident is attributed to the count.
- If it does not match, your phone may ask you a moment later whether anything explains it — damaged stock set aside, stock issued or received but not yet recorded, or you would like to recount. It never shows you the figure. Answer within 30 minutes; silence is escalated to the office (section 30).
Receive into stock (put-away)
- Pick the confirmed delivery that has just arrived at your site (the app lists the last three days), check the lines, add batch and expiry where they apply, and put it away. Stock moves.
- A supplier delivery on a purchase order and a transfer from another warehouse are listed too, with their gate-pass status — pick the one that has arrived and enter what actually came. The office cannot receive these from a desk at your site: your put-away is what writes the receipt and completes the order or transfer. A difference from what was ordered or sent is flagged to operations — and your phone asks you what happened while the goods are still in front of you: arrived short, damaged and set aside, still offloading, or a counting slip you will correct.
- Goods that arrive another way — a return, a local purchase — go in under Other with a reference.
Write-off request
- Damage, expiry, spoilage, theft or other: pick the product and quantity, write a note and take at least one photo.
- Nothing moves until an Admin or Logistics Manager approves it; you get the decision as a notification. You can never approve your own request.
Cold rounds
- If your site has fridges, freezers or a cold room, Cold rounds lists them with each one's safe range and what is due. Go to the unit, read the display itself, type the temperature and photograph the display. Do not copy the last figure.
- Do it at the unit, at the time. A reading logged later is marked late, and a round nobody did while you had the site open is reported.
- If the reading is outside the range, operations are told at once and the app asks what you did: closed the door, power is back, moved the stock, called a technician. Fix what you can, then log a new reading as soon as it is back in range. That is what ends the excursion.
More in the console
Beyond the day-to-day, the console carries a set of oversight and planning screens. They read the same custody data you've already captured — nothing extra to enter.
Your home screen
Live KPIs, today's deliveries, open incidents and the latest alerts in one view — where you land after sign-in.
Fulfilment flow
Customer orders, and inter-warehouse transfers that move stock for real — lines leave the source at dispatch under a gate pass and land when the destination receives them (section 6).
Trends & costs
Volumes, variances, fuel spend and on-time rates over time — to see where money and time go.
Per-driver record
Deliveries, on-time rate, variances, stops and flags for each driver — a fair, evidence-based picture.
What to watch
Highlights the shipments, routes and actors most likely to run into trouble, so you can act early.
Plan the run
Suggests efficient routes between your registered sites — the baseline the trip audit compares against.
Spot the drift
Learns your normal from your own activity — handovers, variances, disputes — and flags when today moves away from it.
Inside the depot
Gate passes and checks, the gate log, blind counts, put-aways, write-off approvals and shift custody — per warehouse.
Receipts that pay
Payouts to mobile-money wallets released by sealed receipts, with approvals, caps and a full history.
Handlers only
The desk for anonymous reports — visible only to the named handlers, never to the rest of the console.
It learns
Judge flags, see what the detectors found, accept or reject each tightening, watch who is under scrutiny — and switch on the auto lane within your bounds (section 17).
Tune & control
Fraud thresholds, variance limits, alert sound & voice, the tip-off channel, data protection, your plan and billing, and your profile — Admin-controlled, every change ledgered.
Offline & good practice
It works without signal
The driver app saves confirmations, incidents and stops on the phone and syncs automatically when signal returns. A banner shows anything still waiting.
Location, only when needed
Tracking runs automatically only during an active delivery and stops when the driver is idle — it protects the route audit without draining battery or data all day.
Updates come to you
Most updates arrive over the air — reopen the app to get them. Only the occasional larger update needs reinstalling.
GPS on every site
Register each depot and project site with its GPS. It's what makes geofencing, route audits and delay-flagging work automatically.
Put it on a screen
Run the Ops Wallboard fullscreen on a depot TV so the whole team sees live deliveries and alerts.
Nothing is editable
Every receipt, incident and update is sealed into a tamper-evident ledger. That permanence is the point — it's your evidence.
Read the seal, not the paper
Whoever reads a seal back — receiver or gate guard — reads it off the seal itself. A number copied from a document proves nothing.
Lock the app
Switch on Require unlock in the field app. If a phone is lost, remove the party on Staff — its access ends at once — and log it in the breach register.
Hear it, don't just see it
Switch on Alert sound & voice on the depot PC and the wallboard so a duress or site-threat alert is heard the moment it arrives.