The platform
Visibility you can act on, not a dashboard you have to interpret.
Freight goes wrong quietly — a vehicle that never left, a route that changed, a POD that never arrived. The platform exists to make each of those loud, early, and attributable.
- Modules
- 10
- Architecture pillars
- 04
- Command centre
- 24×7
- Sub-billing codes
- ∞
Platform mission
- 01
Total transport network visibility
- 02
Movement & operations planning
- 03
Flexible delivery execution
- 04
Ultimate consumer experience
Modules
Ten modules, one record.
Each module writes to the same trip record. That is the whole design: nothing is re-entered, so nothing disagrees at reconciliation.
Visibility · Driver / provider app · Billing · Dispatch management · AVL · Optimisation
Vendor onboarding
Operators, vehicles and drivers are onboarded through an automated flow with compliance documents captured up front.
User management
Role-based access across your organisation, your divisions and our operations desk, scoped to what each user is allowed to see.
Order management
Indents become orders with commodity, lane, quantity and window attached — one record that carries through to the invoice.
Routing, assignment & dispatch
Automated route planning and vehicle deployment, with the Vehicle Placement Request module sequencing what loads next.
Track & trace
Continuous GPS tracking through transit, so the position of every vehicle on your lane is a lookup rather than a phone call.
Geo-fence
Routes are geo-fenced from the physical survey. Entry and exit are logged automatically at both ends of the trip.
Alerts & visibility
Route deviation, or a stop beyond its permitted window, raises an alert without anyone having to notice it first.
Electronic proof of delivery
POD is captured on a touchscreen tablet at the unloading point and syncs to the server on confirmation.
Invoicing & billing
Billing runs off the confirmed trip record under your billing code hierarchy, protected against manual alteration.
Financial settlements
Operator payouts are settled on time against delivered trips — the mechanism that keeps supply committed to your lane.
Architecture
Built to be extended, scoped to be trusted.
A platform architecture of core microservices against their own databases — which is what makes it possible to change one part of the operation without stopping the rest.
Microservices based
- Platform-based architecture
- Core microservices connected to micro databases
- Flexibility to scale and adapt
- Rapid build-to-deploy cycle
Identity & privacy
- Role-based session authentication to prevent misuse
- Data security profile with one-way hashing
- Audit trail with access log management
Safe & secure
- 24×7 command centre
- Driver and vehicle compliance
- SOS management practices
Automation at core
- Automated onboarding
- Automated route planning and vehicle deployment
- 24/7 visibility and tracking with exception alerts
- Flexible and configurable
Visibility
Three questions the portal exists to answer.
These are the three questions that decide whether a plant trusts its transporter. Each one is a lookup in the portal rather than a phone call to a driver.
- Where are the trucks right now?
- Customers sign in with their own credentials and see the exact position of every vehicle on their account, tracked live through transit.
- What has been delivered?
- A running summary of goods delivered, backed by the electronic POD confirmed at each unloading point.
- What is scheduled next?
- The Vehicle Placement Request module sequences the vehicles to be loaded and dispatched — including vehicles due back from trips during the working day.
- Trip management & driver assignment
- Recurring trips & live tracking
- Billing management
Routes are geo-fenced from the physical survey. A deviation, or a stop beyond its permitted window, raises an alert automatically.
ePOD & settlement
The delivery closes the invoice.
Proof of delivery is captured at the dock and becomes the billing event. There is no second version of the trip to reconcile against.
- 01
POD captured at the dock
As goods are delivered, proof of delivery is generated and confirmed electronically at the unloading point on a touchscreen tablet.
- 02
Synced on confirmation
Once confirmed, the POD updates automatically to the APJ server. Delivery and billing status are visible to you in real time.
- 03
Billed under your code hierarchy
Each customer is identified by a unique billing code, with any number of sub-billing codes beneath it for locations, divisions, branches, consignees or product categories.
- 04
Scoped to the right people
Managers see the sub-billing codes for the divisions they run; finance sees the complete view across every code.
The platform carries safety and security protocols that protect the record from manual alteration — which is what makes the billing accurate rather than merely fast.
Next step
See it against your lane.
The fastest way to judge a logistics platform is to point it at a corridor you already run. Send us one, and we will show you what the trip record would look like.
- What to send
- Lane, commodity, monthly volume
- What comes back
- A dispatch plan and a TAT model
- Also for
- Fleet operators seeking sustained volume
Operating across 46 locations · 4 zones