BUILD · 0032026webIN PROGRESS
The operational nervous system for pharmaceutical logistics in South Africa

HazchemPortal

One role-aware portal where Hazchem dispatches, clients see, drivers execute and SAHPRA compliance proves itself automatically.

Hazchem Portal is a single role-aware web platform for cold-chain pharmaceutical logistics. Operations dispatch and bill, clients (PBM, Kalapeng, Dely Road) see scoped live views of their own fleet and deliveries, drivers run their routes on a mobile layout, and every delivery produces a SAHPRA-ready evidence pack — ePOD, GPS trail and temperature certificate — without anyone needing to assemble it.

ROLE
Lead engineer & systems designer
TIMELINE
6 MO
TEAM
1
STATUS
IN PROGRESS

Problem

South African pharma logistics runs on trust signalled by paperwork: scanned PODs, emailed temperature spreadsheets, monthly invoices arriving with line items the client cannot verify. When something goes wrong — a missed cold-chain reading, a late delivery to a hospital pharmacy — the conversation starts after the damage is done, often via WhatsApp, with neither side holding the same evidence.

The brief was to make the evidence the interface: every claim the system makes must be backed by a timestamped record the client can download themselves, in real time, without needing to ask.

Approach

A single portal with eleven roles, one login, role-aware navigation and scoped data access. There is no separate "driver app" and no separate "client portal" — they are the same application showing different surfaces.

Built around ten functional pillars:

  1. Daily route manifest & dispatch
  2. Live GPS tracking via Cartrack
  3. Electronic Proof of Delivery (photo + signature + GPS + timestamp)
  4. Cold-chain temperature logging via LogTag, auto-generating PDF certificates
  5. Monthly transparent invoice (per-pharmacy-per-day, VAT-compliant)
  6. Client dashboard (live map, today's deliveries, MTD spend, exceptions)
  7. Exception reporting with WhatsApp escalation before the branch complains
  8. Driver execution flow (route, navigate, scan, capture, deliver, confirm)
  9. Pricing engine (zone × service multiplier × fuel clause, fully data-driven)
  10. Fleet & compliance register (vehicles, drivers, certificate expiries, alerts)

Design principles drove every trade-off:

  • Show, don't report. If it can be seen live on a map, it is not summarised in an email later.
  • The exception is the interface. On a normal day the dashboard is quiet; the moment something deviates, the system becomes loud.
  • Keyboard over clicks. Dispatchers use this for eight hours a day — fluency wins over discoverability.
  • Offline is not a bug for drivers. The driver flow survives a tunnel, a basement, a rural dead-zone.

Outcome

  • A single codebase serving Hazchem operations, multiple tenants and their drivers, with row-level scoping by tenant and by role.
  • Automated SAHPRA-ready evidence pack per delivery — no manual assembly, no end-of-month scramble.
  • Real-time exception escalation that beats the customer's complaint to the inbox.
  • A pricing engine clients can audit line-by-line, ending the monthly invoice argument.