The command center for vehicle movement.
Proselver Trident is the operations platform for driving new vehicles from manufacturing plants to dealerships — and on to end customers — with verified dispatch, live execution, and document trails you can prove.
No credit card. Built for dispatch teams, operations controllers and customer coordinators.
Latest movement
TRD-48921
Coastal plant → JHB dealer
The three prongs
One platform. Three operational pillars.
Every vehicle movement inside Trident flows through the same operational engine — so nothing falls between spreadsheets, WhatsApp threads, or a missed phone call.
Control
Capture every movement order in one place. Per-customer fields, brand limits, confirmation gates and role-based access are built in — so you control exactly who can book what, and which checks run before a truck moves.
Dispatch
Plan, assign and release in one pass. Allocate drivers, check license and PDP validity, and generate a verified collection note the moment the truck is ready.
Deliver
Track execution from collection to delivered. POD uploads, QR-verified collection notes and status timelines give customers the visibility they used to chase by email.
Why it matters
Fewer missed calls. Cleaner handovers. Verified delivery.
Vehicle movement operations live and die on information: who is confirming the unit, which driver has been assigned, which document is missing, which vehicle left the plant. Trident makes that information the single source of truth — not an email thread.
See it in your environmentReal operational control
Every order, confirmation, assignment and document is auditable against a movement — not a person.
Faster dispatch decisions
See who is confirmed, who is not, which drivers are clear to collect, and which orders still need intervention.
Cleaner document handling
POs, collection notes and PODs live on the movement record. Customers pull their own. You stop being the inbox.
Customer-specific workflows
Some OEMs insist on confirming each vehicle before dispatch. Standard accounts skip it. Both supported by default.
Built for operations
Everything the control room actually uses.
No bloat. No deprecated modules you have to pretend aren't there. Just the seven capabilities dispatch teams rely on every shift.
Order intake
Receive, capture and validate movement requests from OEMs, dealers and internal controllers.
Dispatch planning
Planning queue with customer, route and readiness visibility. Nothing ships that isn't ready.
Driver allocation
Assign by location, license class, PDP validity and current availability — not by memory.
Collection notes
Generated on demand. Driver ID, cellphone, chassis, location, reference — signed by a verifiable QR.
POD & documents
Customers access their own documents. You stop emailing attachments. Everything is on the record.
Customer workflows
Per-account configuration. Confirmation-gated and standard workflows, side by side.
QR verification
Every collection note carries a signed QR. Scan it, see the movement. No more forged paperwork.
Driver expiry tracking
License and PDP expiries surface at the right time — before a driver is assigned to a vehicle class they can't legally move.
Developer impersonation
Test every role end-to-end with a safe impersonation banner. No shadow accounts. No risky logins.
How it works
Four steps. No heroics.
A controller can move an order from intake to collection in under two minutes. Customers can see exactly where it is without calling you.
-
01
Receive the movement
An OEM, dealer or internal controller captures the order. Brand, route and reference are validated against the account.
-
02
Confirm & plan
For accounts that need it, the customer dispatcher confirms readiness. Operations plans the movement and assigns the controller.
-
03
Allocate & release
A driver with valid license and PDP is allocated. A collection note with QR verification is generated.
-
04
Execute & deliver
Statuses update through collection, in transit and delivered. POD is uploaded. The customer sees it live.
Customer workflows
Different OEMs. Different rules. Same platform.
Some customers need to confirm a vehicle is physically ready before anyone dispatches. Others don't. Trident supports both as first-class workflows — configured on the account, not hardcoded in logic.
- Per-account workflow type — standard or confirmation-gated.
- Customer dispatchers scoped to a specific plant, depot or branch.
- Brand-level access limits per customer — no irrelevant options in the order form.
- Confirmation exceptions handled gracefully: vehicle missing, damaged, not ready.
Standard account
Dealer-originated orders · direct dispatch
Confirmation-gated account
Requires customer confirmation before dispatch
Plant-side customer dispatchers confirm the vehicle is physically ready — or flag it as missing, damaged, or not ready — before dispatch proceeds.
Proof, not promises
Every movement leaves a verifiable trail.
A collection note is not a piece of paper. In Trident, it's a signed record tied to a driver, a vehicle, a location, and a scannable QR code — so the person receiving the vehicle can confirm it's real in a second.
-
QR verification
Scan the note — a public verification page confirms the movement, driver and destination match.
-
Document record
POs, collection notes and PODs attach to the movement — not to a person's inbox.
-
Audit trail
Every status change, assignment and confirmation is timestamped against the user who did it.
Collection Note
TRD-48921
Issued
16 Apr 2026 · 09:42
Driver
Thabo Molefe
ID 8501015123081 · 082 123 4567
Vehicle
6x4 Truck Tractor
VIN ••••••••••7291
From
Coastal plant
Eastern Cape
To
JHB dealer
Johannesburg
Scan to verify
proselver.co.za/verify
Ready when you are
Put your dispatch under one roof.
We'll stand up a private instance of Proselver Trident, configure your accounts and workflows, and run your first movements alongside your team.
Control • Dispatch • Deliver