The platform
A logistics company that built its own software.
Most couriers buy a tracking system and operate around it. We built ours around how the work actually runs, which is why custody, exceptions and reporting behave like one thing instead of three.
What you get
What your team logs into, and what runs behind it.
Your team gets a portal, proof of delivery and reporting. Our dispatchers get the console that makes those three worth trusting. All four read the same record, so there is nothing to reconcile between them.
What you use
Your team answers its own questions
Raise collections, follow progress and pull proof of delivery without calling us. It is the same event stream our operations works from, presented as a progress path rather than a log.
Capabilities
What the platform actually does.
Real-time shipment visibility
A scan at a branch counter reaches your team in seconds. Status is derived from recorded events, not typed in by someone reconciling a sheet at end of day.
Electronic proof of delivery
Recipient name, signature and GPS position captured on the delivery event. Retrievable against the item for as long as you need it.
Barcode & QR scanning
Every movement is a scan. Delivery is blocked unless the scanned barcode matches the assignment, so the wrong item cannot be signed off at the right address.
Apps for drivers and clients
Our riders use an app we built, which keeps working when the signal drops. Your team just uses a browser. Nothing to install and nothing to maintain.
Secure document handling
Access to shipment detail is scoped to your organisation. Public tracking shows milestones only; addresses, contacts and proof of delivery stay behind a login.
Reporting that reconciles
On-time and first-attempt rates by route, client and period, taken from the same scans our operations team works from, so a service review and a dispatch screen never disagree.
The custody chain
What gets recorded, and when.
Each step records a status against the item. These are the real ones, so you will recognise them when you open the portal.
- 01COLLECT
A rider collects it from your counter
Your collection happens on a fixed route at a time you can plan around. The rider scans each item in front of you, and from that moment the record has their name on it. No paper docket to lose.
- 02HANDOVER
When it changes hands, both riders confirm
Work gets passed between riders during the day. The one receiving it taps to accept before it counts, so there is never a gap where the item belongs to Era Baru in general and nobody in particular.
- 03INBOUND
It gets scanned into the sorting centre
Everything is scanned in on arrival and then scanned onto its onward route. If something turns up that we have no outbound record for, we catch it there rather than sending it on and finding out later.
- 04DISPATCH
It goes out on a numbered manifest
Every run leaves with a manifest, and those numbers can never be reused, so two runs can never both claim the same consignment. Outstation legs move between our hubs the same way.
- 05EPOD
The rider scans it again at the door
If the barcode does not match what they were sent to deliver, the app will not let them close it. They take the recipient’s name and signature, and the phone stamps where it happened.
- 06AUDIT
And it is all still there months later
Every scan, handover and problem stays attached to the item. So when someone asks what happened to a particular consignment back in March, we look it up instead of asking around.
Technical questions
The ones procurement asks.
Did you build this or license it?
Built in-house. Dispatch, the driver app, the client portal and reporting are one system developed and operated by us, which is why changes your operation needs do not wait on a vendor roadmap.
Can it integrate with our systems?
You can import collections in bulk against your own reference numbers, and that reference stays with the order right through to the printed document. Anything deeper we scope per client, so tell us what you run.
What happens if a rider loses signal?
Capture is designed to tolerate it. The scan, recipient and photo are taken on the device and submitted when connectivity returns; the event keeps the time it actually happened.
How is our data separated from other clients?
Access is scoped per organisation at the data layer, and the public tracking page on this site can only ever return stages and status. Never names, addresses or our own notes.
Tell us what you need moved.
Tell us your volumes, where you need collecting from and where it has to go. We will come back with a schedule, a service level and a price.