Published: 15 November 2026
Choosing tipper truck software is one of the most consequential decisions a South African fleet operator will make. The wrong choice means you are stuck with a system that cannot handle weighbridge tickets, cannot track per-tonne costs, and cannot produce the evidence RTMS auditors need. The right choice gives you a single platform that ties every load, every driver, and every vehicle together.
This guide gives you twelve questions to ask any vendor before you sign. For each question, we explain why it matters for tipper and side-tipper operations, and what a good answer looks like. Whether you run a ten-truck coal haulage operation in Mpumalanga or a fifty-vehicle interlink fleet serving Richards Bay, these questions will separate the software that actually works from the systems built for general logistics.
Why Do Tipper Operators Need Specialised Fleet Management Software?
Generic fleet management software SA operators often consider was designed for courier vans and light delivery vehicles. Tipper operations are fundamentally different.
You deal with payload variability on every load. A side-tipper carrying chrome ore from a Limpopo mine faces different weight constraints than the same trailer carrying coal to Eskom. You need software that understands the difference between a 34-tonne interlink combination and a 56-tonne PBS-approved rig.
You face stricter compliance requirements. The RTMS scheme requires documented evidence of load management, driver behaviour, and vehicle maintenance. General fleet software rarely produces RTMS-ready reports.
Your billing is more complex. While a courier company bills per delivery, you might bill per tonne, per load, or per kilometre. You need software that captures weighbridge data and converts it to accurate invoices without manual spreadsheet work.
Question 1: How Does the System Handle Weighbridge Tickets Per Load?
Every tipper operation lives and dies by weighbridge data. You need to know the tare weight, the gross weight, and the payload for every single load. This is not optional.
What to ask: "Show me how a weighbridge ticket is captured for a single load, from the moment the truck crosses the scale to when that data appears in a report."
What a good answer looks like: The system should accept weighbridge data through multiple channels. This might include manual entry by a driver on a mobile app, electronic import from a weighbridge system with an API, or OCR scanning of printed tickets. The data must link automatically to the correct vehicle, driver, and trip. You should be able to view payload by vehicle, by driver, by route, and by customer.
T-ERP's Fleet Management module ingests weighbridge data from any source that exposes sufficient API data and ties it to the right vehicle, driver, and trip. Manual entry is available for sites without electronic weighbridges.
Red flag: If the vendor cannot show you a working weighbridge workflow, walk away.
Question 2: Can You Bill Per Tonne, Per Load, and Per Kilometre?
Tipper contracts vary wildly. You might have one customer who pays R45 per tonne delivered, another who pays R2,800 per load regardless of weight, and a third who pays R28 per kilometre.
What to ask: "Show me how the system calculates an invoice for a customer who pays per tonne, using actual weighbridge data from the last week."
What a good answer looks like: The system should let you set up different rate structures per customer or per contract. When you generate an invoice, it should pull actual tonnage from weighbridge records, actual distances from GPS tracking, or actual load counts from trip records. The invoice should be auditable, meaning your customer can trace every line item back to a specific load with a timestamp.
T-ERP's Freight Invoicing module supports per-tonne, per-load, and per-kilometre billing. It links weighbridge data to trips and generates invoices with full audit trails. For more on this topic, see our guide to automated invoicing for freight.
Red flag: If billing requires exporting data to Excel and doing calculations manually, the system will cost you hours every week.
Question 3: How Does the System Track Payload Against Legal Limits?
Overloading fines in South Africa are severe. According to the Road Traffic Management Corporation, a 5% overload on a truck-trailer combination attracts a fine of R2,500. At 10% over, you are looking at R5,000. Beyond 15%, the fine escalates rapidly and the vehicle can be detained.
What to ask: "If a driver loads 10% over the legal limit, how quickly does the system alert someone, and who gets the alert?"
What a good answer looks like: The system should compare every weighbridge reading against the registered GVM or the PBS-specific limit for that vehicle combination. If the payload exceeds the legal limit, an alert should go to the fleet manager and the driver within minutes. The system should also flag repeat offenders so you can address the root cause.
T-ERP compares weighbridge data against vehicle-specific limits stored in the Fleet Management module. Overload alerts go to designated managers via push notification and email. For a deeper dive into overloading risks, read our overloading fines schedule guide.
Red flag: If the system cannot store legal limits per vehicle combination, you will have to check every load manually.
Question 4: Does the System Support Trailer and Interlink Combinations?
Most tipper software assumes one truck equals one asset. In reality, you might run truck-tractors with multiple trailer combinations. A single Scania R460 might pull a side-tipper one week and a flatdeck the next.
What to ask: "Show me how you track a truck-tractor that uses three different trailers over the course of a month, and how you report on each combination separately."
What a good answer looks like: The system should treat the truck-tractor and each trailer as separate assets with their own maintenance schedules, licence renewal dates, and cost tracking. When you create a trip, you should be able to select the specific combination. Reports should show utilisation, costs, and revenue per combination, not just per truck.
T-ERP's Fleet Management module tracks truck-tractors and trailers as separate assets. You assign combinations per trip, and reporting breaks down performance by combination. This is essential for interlink operators running mixed fleets.
Red flag: If the vendor treats a truck-trailer as a single unit, you will never know which trailer is costing you money.
Question 5: How Does the System Track PrDP and Medical Certificate Expiry?
The National Road Traffic Regulations require every driver operating a goods vehicle over 3,500kg GVM to hold a valid Professional Driving Permit. PrDPs expire every five years, and drivers must also hold a valid medical certificate.
What to ask: "Show me the report that lists every driver whose PrDP or medical certificate expires in the next 60 days."
What a good answer looks like: The system should store expiry dates for every driver credential, including PrDPs, medical certificates, and EC licences. It should generate automated alerts at configurable intervals, for example 90 days, 60 days, and 30 days before expiry. The system should prevent you from assigning a driver to a trip if their PrDP has expired.
T-ERP's Driver Management module tracks all driver credentials with automated expiry alerts. Dispatchers cannot assign drivers with expired PrDPs to trips. For the full requirements, see our PDP South Africa guide.
Red flag: If credential tracking is a separate spreadsheet or a manual process, someone will miss an expiry.
Question 6: Does the System Support SMR and Kilometre-Based Service Plans?
Standard maintenance recommendations (SMR) from manufacturers specify service intervals by hours or kilometres. A Volvo FH might need an oil change every 60,000km, while a Bell ADT working on a mine haul road needs service every 250 hours.
What to ask: "Show me how you set up a maintenance schedule for a truck that needs service every 40,000km and a separate schedule for an ADT that needs service every 250 engine hours."
What a good answer looks like: The system should allow you to define service schedules based on kilometres, engine hours, or calendar time. It should pull actual odometer readings from telematics or manual entry and trigger work orders automatically when service is due. You should be able to see a maintenance calendar that shows upcoming services for the entire fleet.
T-ERP's Fleet Maintenance module supports km-based, hour-based, and calendar-based service schedules. Work orders generate automatically when thresholds are reached. For practical guidance, see our preventive maintenance fleet guide.
Red flag: If the system only supports calendar-based scheduling, you will either over-service low-utilisation vehicles or under-service high-utilisation ones.
