
Trainer & Knowledge Base Guide
Sthe Courier
Delivery Logistics Management Platform
Version 1.0 | July 2026
Document Classification: Internal, Training & Reference
Compiled by: Mr. Bandile Mathebula
Technical and IT Manager
| 1 | Platform Overview |
| 2 | System Architecture & Technology Stack |
| 3 | User Roles & Access Control |
| 4 | Delivery Management |
| 5 | Pricing & Billing Configuration |
| 6 | Customer Management |
| 7 | Driver Management |
| 8 | Driver App & QR/Barcode Scanner |
| 9 | Warehouse Management |
| 10 | Dispatch Dashboard |
| 11 | Billing & Financial Management |
| 12 | Accounting & Payroll |
| 13 | Staff Management |
| 14 | Customer Portal |
| 15 | Content Management |
| 16 | Notifications & Communication |
| 17 | Analytics & Reporting |
| 18 | Document Generation |
| 19 | Security & Compliance |
| 20 | Contact & Support |
This is your go-to guide for the Sthe Courier platform. Whether you're onboarding new staff, training drivers, or just need a quick refresher on how something works, this document has you covered. It's written for admins, managers, ops staff, finance teams, and anyone else who needs to get stuck into the system.
We've broken everything down module by module so you can jump straight to what you need. Each section explains what the module does, the key features, and how things work day to day. No fluff, just the stuff you actually need to know.
Sthe Courier is a cloud-based platform that handles the entire delivery process from start to finish. Booking, tracking, dispatch, driver app, billing, the lot. It brings three groups of people together in one place: customers who book and track their parcels, ops staff who keep things moving, and drivers out on the road doing the actual deliveries.
It runs on modern web tech, works on both desktop and mobile, and gives you real-time tracking, automatic pricing, QR and barcode scanning, warehouse management, billing, and proper reporting. Drivers get their own mobile app so they can manage everything from their phone while out on the road.
| Layer | Technology | What it does |
|---|---|---|
| Frontend | React + Vite + Tailwind CSS | The app itself, responsive and component-based |
| UI Components | shadcn/ui + Radix UI | Clean, consistent interface building blocks |
| Icons | Lucide React | All the icons you see throughout the app |
| State Management | TanStack React Query | Handles data fetching, caching, and live updates |
| Charts | Recharts | Dashboards and data visualisation |
| Maps | React-Leaflet | Dispatch map view and live driver tracking |
| Scanning | html5-qrcode | QR and barcode scanning through the phone camera |
| PDF Generation | jsPDF + html2canvas | Creates PDF documents right in the browser |
| Barcode/QR | jsbarcode + qrcode.react | Generates barcodes and QR codes for waybills |
| Backend | Base44 BaaS | Handles auth, database, integrations, and hosting |
| Payments | Paystack + Stripe | Online payments and wallet top-ups |
The platform's data is split across more than 25 entities, each one representing a core business object. Here are the main ones you'll come across:
| Entity | What it holds |
|---|---|
| Delivery | The core delivery record with tracking, waybill, route, pricing, and status |
| PricingConfig | Standard rate schedule per route, including base price, surcharges, and multipliers |
| CustomerPricing | Custom pricing overrides for specific customers on specific routes |
| AccountBilling | Customer account with credit limit, balance, and custom pricing overrides |
| AccountTransaction | Individual charges and payments on a customer account |
| Wallet / WalletTransaction | Prepaid wallet balance and full transaction history |
| DriverProfile | Driver registration, vehicle details, and approval status |
| WarehouseItem | Parcel tracking inside the warehouse, including bin assignment |
| Invoice | Invoices and quotes with line items and VAT |
| CustomerProfile | Customer business details, VAT number, and billing address |
| StaffProfile | Staff member details, department, and access level |
| Payslip | Employee payroll with UIF, PAYE, allowances, and deductions |
| AppNotification | In-app notification messages |
The platform uses role-based access control (RBAC) with row-level security (RLS) that's enforced at the database level. Every user gets a role, and that role decides what they can see, create, edit, or delete.
| Role | Access Level | What they can do |
|---|---|---|
| Admin | Full Access | Everything, across all modules. User management, system config, driver creation and approval, the works. |
| Manager | High | Operations management, delivery bookings, pricing config, dispatch, driver management, staff approvals. |
| Executive | High (Read) | Read access across everything, dashboards, financial reporting, content management. |
| Finance | Medium | Account billing, invoices and quotes, expenses, wallet management, transactions. |
| HR | Medium | Staff profiles, timesheets, payslip generation, staff approvals. |
| Staff | Standard | Delivery bookings, lodge entries, warehouse management, delivery operations. |
| Driver | Limited | Driver app access, their assigned deliveries, QR/barcode scanning, GPS tracking, status updates. |
| Customer | Self-Service | Book deliveries, track parcels, manage wallet, view statements and invoices, update profile. |
This is the heart of the platform. The Delivery Management module is where you book new deliveries, lodge historical entries, manage waybill numbers, track delivery status, and edit bookings after they've been created.
Staff and managers can book new deliveries through the Admin Book Delivery screen. Here's what the booking process covers:
Figure 4.1: The booking form where staff select a customer, configure the route, enter package details, and the price calculates automatically.
Sometimes deliveries happen before they're captured in the system. The Lodge Past Entries feature lets staff record those after the fact. You can do it one at a time through a form, or bulk import via CSV if you've got a stack of historical data. Lodge entries work the same way as new bookings, with customer selection (including manual entry), waybill numbers, and automatic pricing.
Every delivery has two key reference numbers:
| Field | What it is |
|---|---|
| Tracking Number | A unique ID the system generates (like ST12345678). This is what customers use to track their parcels and what the scanner reads. |
| Waybill Number | The customer's own reference number linked to the booking. Also scannable via QR or barcode. |
| Status | What it means | How it gets triggered |
|---|---|---|
| Pending | Booking created, waiting for confirmation | New booking |
| Confirmed | Booking confirmed and scheduled | Staff confirms it |
| Picked Up | Parcel collected from sender | Driver scans (Pick-Up) or manual update |
| In Transit | Parcel en route or sitting at the warehouse | Driver scans (Warehouse) or manual update |
| Out for Delivery | Final delivery attempt underway | Driver or dispatch updates it |
| Delivered | Successfully delivered to the recipient | Driver scans (Delivery) with proof photo |
| Cancelled | Delivery cancelled | Staff or admin cancels it |
Every status change gets logged in the delivery's status_history with the timestamp, new status, and any notes or proof photos. So you've always got a full paper trail of where the parcel's been and when.
Once a delivery is booked and confirmed, staff can still go back and edit the package weight. The system recalculates all the surcharges on the spot based on the new weight, so the pricing stays accurate even if the actual weight turns out different from what was first captured.
Staff can manually override the base charge on a booking without messing with the other surcharge calculations (fuel, VAT, per-kg, service multipliers). Handy for negotiated rates or special cases where the standard pricing doesn't quite fit, but you still want everything else to calculate normally.
The Pricing Management module is a flexible, multi-layered pricing engine that works out delivery costs based on route, distance, weight, service type, and customer-specific agreements. Pricing gets pulled from three tiers, checked in this order of priority:
The standard rate schedule sets the default pricing for each route (city to city). Each route config includes:
| Parameter | Default Value | What it means |
|---|---|---|
| Base Price | R180.00 | The flat base charge per delivery |
| Free Weight Cap | 10 kg | First 10 kg is included in the base charge |
| Price per kg (above cap) | R2.00 / kg | Every kg over the free cap costs extra |
| Fuel Surcharge | 38% | Added on top of the subtotal (base + weight charge) |
| VAT | 15% | Added on top of the total (subtotal + fuel surcharge) |
| Service Type | Multiplier | What it means |
|---|---|---|
| Standard | 1.0x (no multiplier) | Your standard delivery service |
| Scheduled | 1.2x | Pre-scheduled delivery |
| Express | 1.8x | Priority express delivery |
| Overnight | 2.2x | Overnight express delivery |
Here's how the total delivery price gets worked out, step by step:
You can set up custom pricing at two levels:
The Pricing Management module has a built-in Price Calculator that works out shipment costs in real-time based on route, service type, and weight. It pulls rates straight from the Standard Rate Schedule and any applicable custom pricing, so the price you see in the calculator is exactly what you'll get on the actual booking.
Figure 5.1: The Price Calculator showing a live cost breakdown for a Johannesburg to Durban shipment, including base price, weight charge, fuel surcharge, and VAT.
The Customer Management module is where you manage customer profiles, onboarding, documentation, delivery preferences, and recurring delivery schedules. Every customer is linked to the platform through their registered email address.
Each customer has a profile record with their business details: company name, registration number, VAT number, tax number, billing address, contact person, and industry. The preferred name field controls how the customer's name shows up on documents and statements.
New customers go through an onboarding process that captures their business or individual details, billing info, and whatever compliance documents are needed. The onboarding status gets tracked so you can see who's completed everything and who still has outstanding items.
Customers can upload compliance documents like ID documents, proof of address, company registration certificates, VAT certificates, tax clearance, bank statements, and signed agreements. Each document gets a review status (pending, approved, rejected) with a reason if it's rejected.
Customers can set up delivery preferences like preferred pickup and delivery time windows, special instructions, and default recipient details. These preferences auto-populate when booking, so regular customers don't have to type the same stuff every time.
Customers who send parcels regularly can set up recurring delivery schedules. The system stores the recurring config (route, package details, frequency) and can generate individual delivery bookings off the back of it.
Business customers can manage sub-accounts, which means multiple users or departments within a company can book deliveries under one billing account. Good for companies with multiple branches or departments that all share a central billing function.
The Driver Management module is where you register, approve, and keep an eye on drivers. Drivers are managed through DriverProfile records that capture their personal details, license info, vehicle details, and banking info for payments.
Drivers can sign themselves up through the Driver App onboarding flow, or admins can add them manually. Either way, all driver registrations need to be approved before the driver can use the Driver App and start getting delivery assignments.
| Approval Status | What it means |
|---|---|
| Pending | Waiting for admin review, can't access the Driver App yet |
| Approved | Active driver, can use the Driver App and get assignments |
| Rejected | Registration rejected, no access to the platform |
Admins can add drivers manually from the Drivers Management page. The Add Driver form captures the driver's full name, email, phone, ID number, license details (number, code, expiry), and vehicle details (type, make, model, year, registration, colour). Manually added drivers are created as Approved and Active straight away, so they're ready for assignment immediately.
| Category | Fields |
|---|---|
| Personal | Full name, email, phone, ID number, profile photo |
| License | License number, code (B, C, C1, EC, EC1), expiry date, license photo |
| Vehicle | Type (bike, car, van, truck), make, model, year, registration, colour |
| Banking | Bank name, account number, branch code (for driver payments) |
| Emergency | Emergency contact name and phone number |
Deliveries get assigned to drivers by storing the driver's name in the delivery's assigned_driver field. The Driver App filters deliveries so drivers only see the ones assigned to them. Approved drivers show up in the assignment dropdowns on the booking and dispatch screens.
The Driver App is the mobile-first interface drivers use out in the field. It gives them access to their assigned deliveries, the QR/barcode scanner for status updates, GPS tracking, check-in and check-out, route optimisation, scheduling, analytics, and chat with dispatch.
The scanner uses the phone's camera to read QR codes and barcodes printed on parcel waybills. There are three scan types, and each one updates different fields and records:
| Scan Type | Delivery Status | What else happens |
|---|---|---|
| Pick-Up | Status changes to Picked Up | Logged in status history, customer gets an email |
| Received at Warehouse | Status changes to In Transit | Warehouse item updated to "In Warehouse" with arrival date, customer gets an email |
| Delivery | Status changes to Delivered | Actual delivery date set, logged in status history, customer gets an email |
The scanner matches the barcode value against both the tracking number and the waybill number, so parcels can be scanned using either reference. After a successful scan, the system automatically refreshes all the related data across the platform, including dispatch dashboards, delivery lists, and warehouse records.
Figure 8.1: The scanner screen (left) with the three scan type buttons and camera viewfinder, and the confirmation screen (right) shown after a successful Pick-Up scan, including the option to snap a proof photo.
The Driver App picks up the driver's GPS location and updates it on the regular. The location data sits on the DriverProfile and shows up on the Dispatch Dashboard's map, so dispatch can see where all their drivers are in real-time.
Drivers can clock in and out of their shifts through the Driver App. Each clock-in/out creates a Timesheet entry with the clock-in time, clock-out time, total hours worked, and break duration. This feeds straight into payroll and payslip generation.
The Route AI feature suggests an optimised delivery sequence for the driver's active deliveries, cutting down travel distance and time. Drivers can check the suggested route and navigate to each stop through Google Maps.
The Schedule tab shows upcoming and scheduled deliveries. The Analytics tab gives drivers their performance numbers: total deliveries, completed count, active count, cancellation rate, and success rate. Handy for drivers and managers to track how things are going over time.
Drivers can chat with dispatch through the in-app chat panel. Messages are stored as Message entities and update in real-time, so drivers and dispatchers stay in touch while out on the road.
The Warehouse Management module tracks parcels inside the warehouse from the moment they arrive to when they get dispatched. Each parcel is recorded as a WarehouseItem linked to its delivery via tracking number and delivery ID.
Figure 9.1: The warehouse items table showing tracking numbers, customer names, assigned bin locations, and colour-coded status badges for each parcel.
| Status | What it means |
|---|---|
| Incoming | Parcel is expected at the warehouse but hasn't arrived yet |
| In Warehouse | Parcel is physically there and stored |
| Ready for Dispatch | Parcel is prepped and queued for outgoing dispatch |
| Dispatched | Parcel has left the warehouse and is on its way |
Each warehouse item can be assigned to a specific bin or shelf location (the bin_number field), so staff can find parcels quickly when it's time to dispatch them. The system tracks arrival and dispatch dates for each item.
The system can send alerts when parcels have been sitting in the warehouse past a certain threshold, so staff know to prioritise dispatch and nothing gets forgotten about.
The Dispatch Dashboard gives you a real-time view of all active deliveries and where your drivers are. Here's what you get:
Figure 10.1: The dispatch dashboard with an interactive map showing delivery location pins and live driver positions, alongside a sidebar listing active deliveries with their current statuses.
The Billing module looks after customer account billing, transactions, wallets, invoices, quotes, and statements. It handles both prepaid wallet payments and post-paid account billing with credit limits.
Each customer can have an AccountBilling record that sets up their billing config:
| Field | What it means |
|---|---|
| Account Number | Auto-generated ID (like STC-00123) |
| Account Status | Active, Suspended, or Closed |
| Pricing Plan | Standard, Business, Enterprise, or Custom |
| Credit Limit | The max outstanding balance allowed (default: R5,000) |
| Current Balance | What's currently outstanding and unpaid |
| Payment Terms | 7, 14, 30, or 60 days |
| Billing Cycle Day | Day of the month invoices get generated (default: 25th) |
| Custom Pricing | Per-account base price, per-kg rate, fuel surcharge, and discount overrides |
Figure 11.1: Account billing cards showing each customer's account number, pricing plan, current outstanding balance, credit limit, and payment terms.
Every delivery charge and payment on an account gets recorded as an AccountTransaction. Transactions have types (delivery charge, payment, credit, adjustment) and statuses (pending, invoiced, paid). When monthly invoices get generated, pending transactions get marked as invoiced and linked to the invoice.
Customers can keep a prepaid wallet balance. Top-ups go through Paystack or Stripe. Delivery charges can be deducted from the wallet, and each deduction gets recorded as a WalletTransaction. The wallet tracks total topped up, total spent, and current balance.
The platform generates proper invoices and quotes with line items, quantities, unit prices, VAT, discounts, and totals. Each invoice or quote includes client details, banking details, payment terms, and tracking/waybill references when linked to a delivery. Invoices move through statuses: draft, sent, paid (or overdue if it slips past the due date).
Customer statements summarise account activity over a billing period: opening balance, all transactions (charges and payments), and closing balance. Statements can be generated for individual customers, or customers can view their own in the portal.
The platform can automatically generate monthly invoices. On the configured billing cycle day, it collects all pending account transactions for each customer, creates an invoice, and marks the transactions as invoiced. You can trigger this manually or set it up to run on a schedule.
The Accounting module is where you manage business expenses, employee payroll, and financial reporting. It ties into the billing and staff management modules so you get one unified view of the finances.
Expenses get recorded with a category, amount, VAT, date, supplier, and receipt attachment. Categories cover fuel, vehicle maintenance, salaries, office, insurance, marketing, utilities, driver payments, warehouse, and other. Expenses go through an approval workflow: pending, then approved or rejected.
| Field | What it means |
|---|---|
| Category | Fuel, Vehicle Maintenance, Salaries, Office, Insurance, Marketing, Utilities, Driver Payments, Warehouse, Other |
| VAT | VAT amount calculated at 15% (you can adjust the rate per expense) |
| Receipt | Uploaded receipt image for audit purposes |
| Status | Pending, Approved, or Rejected |
The Payslip Generator puts together proper payslips for employees and drivers. Each payslip includes:
Payslips move through statuses: draft, issued, paid. The generator pulls from the employee's StaffProfile or DriverProfile to fill in personal and banking details automatically.
Figure 12.1: A generated payslip showing the employee's earnings (basic salary and allowances) alongside deductions (PAYE and UIF), with the net pay calculated at the bottom.
The Financial Dashboard gives you a bird's eye view of the business's financial health: revenue, expenses, outstanding balances, and profitability. It pulls data from deliveries, invoices, expenses, and account transactions all in one place.
The Staff Management module looks after internal staff profiles, timesheets, departmental structure, and task assignment. Staff members are linked to the platform through their registered email and assigned a department and role.
Each staff member has a StaffProfile record with:
| Field | What it means |
|---|---|
| Department | Admin, Marketing, Operations, HR, Finance, or Executive |
| Staff Role | Staff, Team Lead, Manager, Department Head, Executive, or Admin |
| Access Level | Read Only, Standard, or Full Access |
| Approval Status | Pending, Approved, Rejected, or Suspended |
| Employee ID | Internal employee identifier |
| Start Date | When they started working |
Staff clock in and out through the platform. Each session creates a Timesheet record with the date, clock-in time, clock-out time, hours worked, and break duration. Timesheet data feeds into payroll and payslip generation.
The platform supports six departments, each with its own dashboard and task management:
Tasks can be assigned to staff members with priority levels (low, medium, high, urgent), due dates, and statuses (pending, in progress, review, completed, cancelled). Tasks are department-scoped and visible to the person assigned, the person who assigned it, and management.
The Customer Portal is the self-service interface where customers can book deliveries, track parcels, manage their wallet, view billing statements, send messages, and manage their account settings.
| Feature | What it does |
|---|---|
| New Delivery | Book a new delivery with automatic pricing |
| Track Delivery | Real-time tracking by tracking number or waybill number |
| Wallet | Check balance, top up via Paystack or Stripe, see transaction history |
| Billing | View invoices, quotes, and account statements |
| Messages | Chat with Sthe Courier support staff |
| Account Settings | Update profile, business details, and delivery preferences |
| Recurring Deliveries | Set up and manage recurring delivery schedules |
Figure 14.1: The customer portal home screen where customers can book new deliveries, track parcels, manage their wallet, view invoices, send messages, and update account settings.
The Content Management module lets admins edit the text, images, and button labels on the public-facing website pages (Home, About, Services, Contact). Content is stored as ContentBlock entities, each identified by a unique section key. You can edit text, swap images, add videos, change button labels, and update URLs.
Changes made through the Content Management screen show up on the website straight away, so non-technical staff can update marketing content without needing a developer.
The platform keeps customers and staff in the loop through a few different channels:
| Channel | How it works |
|---|---|
| In-App Notifications | Real-time notifications in the portal, shown in the notification bell. Types: delivery update, payment, wallet, system, alert. |
| Automatic emails for delivery status updates, booking confirmations, and billing comms. Sent from admin@sthecourier.co.za and billing@sthecourier.co.za. | |
| WhatsApp notifications for delivery updates and customer comms (via backend function integration). |
Delivery status update emails include the tracking number, new status, and any notes or proof-of-delivery photos. Customer notifications fire off automatically when delivery statuses change, whether that's a staff member updating it manually or a driver scanning a barcode out in the field.
The platform has proper analytics dashboards for keeping tabs on operational and financial performance:
The platform generates professional, branded PDF documents for all the operational and financial workflows. Everything comes out branded as Sthe Courier with consistent formatting and layout.
| Document | What it's for | What's on it |
|---|---|---|
| Waybill | Parcel tracking document | Tracking number, waybill number, QR/barcode, route, package details, pricing |
| Invoice | Billing document | Line items, VAT, discounts, totals, banking details, payment terms |
| Quote | Price quotation | Same structure as invoice but with quote status |
| Statement | Account statement | Opening balance, transactions, closing balance, billing period |
| Payslip | Employee payroll | Gross pay, deductions, UIF, PAYE, net pay, banking details |
All PDFs include the Sthe Courier logo, company contact details, and professional formatting. Banking details are laid out on individual lines with bank name, account number, branch code, and account type. Documents can be downloaded straight from the platform or emailed to customers.
The platform uses row-level security across all critical entities. RLS policies are enforced at the database level, so users can only get to data they're actually allowed to see. Here are the key principles:
User authentication is handled by the Base44 platform, which looks after secure sessions, token-based auth, and email verification. Users join the platform through admin invitations and get assigned the right role for their job.
The platform includes a POPIA (Protection of Personal Information Act) compliance page, Terms of Service, and Privacy Policy. These spell out how customer and staff personal information gets collected, used, and protected, in line with South African data protection regulations.
Sensitive documents (IDs, licenses, bank statements) are stored securely and access-controlled. Document uploads by customers get reviewed and approved by admins before being accepted. All data is transmitted over encrypted connections.
| Department | |
|---|---|
| General Administration | admin@sthecourier.co.za |
| Billing & Accounts | billing@sthecourier.co.za |
For platform support, technical help, or account-related queries, drop a line to the right department above. For urgent operational issues, get hold of your assigned Sthe Courier account manager or dispatch team directly.
Sthe Courier, Delivery Logistics Management Platform
Methodology & Technical Functionality Document, Version 1.0, July 2026
This document is classified as Internal, Training & Reference. Distribution restricted to authorised personnel.