Elicon
← ALL REFERENCE ENGAGEMENTS
REFERENCE ENGAGEMENT
Logistics

Operations Platform for a Regional Logistics Operator

Replace a web of spreadsheets with one operational view, without stopping the business.

  • Next.js
  • Node
  • Postgres
  • Redis

Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.

THE SITUATION

The problem.

A logistics operator running the business from interlinked spreadsheets and a telematics portal nobody in dispatch opens. The engagement models the real operation in Postgres, ingests live vehicle positions, and gives dispatchers, drivers and owners each their own view — migrating the spreadsheets rather than abandoning them.

Every question about a shipment takes several tabs and a phone call, and month-end reconciliation produces numbers nobody fully trusts.

  • ·Cross-sheet formulas break silently, and nobody can say which sheet is authoritative.
  • ·Vehicle position and job status live in two separate systems joined by phone calls.

APPROACH

How we'd run it.

  1. 01Model shipments, legs, vehicles, drivers, fuel and incidents as real entities in Postgres.
  2. 02Ingest live positions from the existing telematics provider.
  3. 03Give each role its own slice: regional queues for dispatch, margin for the owner, today's jobs for drivers.
  4. 04Run old and new side by side until the new system is trusted.

ARCHITECTURE

What gets built.

Domain model

Shipments, legs, vehicles, drivers, fuel events and incidents as tables with real keys and constraints. Most spreadsheet chaos is a modelling problem; once a leg is an entity, many reconciliation questions answer themselves.

Migration pipeline

Repeatable importers per sheet with validation reports listing every failed row and why, run nightly against the live sheets so the database is never stale during transition.

Offline-tolerant driver views

Driver screens cache the day's assignments and queue updates locally, syncing when signal returns. A yard with no signal is the normal case, not an edge case.

DECISIONS

The trade-offs.

Run spreadsheets and the new system in parallel

A hard cutover on a business that cannot stop invites a rollback. Nightly re-imports let the new system be wrong for a day without losing a shipment.

TRADE-OFFA period of double entry for some fields, and importer maintenance during it.

Integrate the existing telematics hardware rather than replace it

It is installed, paid for and working. Replacing it adds cost and an installation schedule to a software project.

TRADE-OFFThe vendor's API limits and gaps are inherited and smoothed over rather than fixed.

Mobile web for drivers, not native apps

Mixed devices and no device management make native distribution more expensive than the feature itself.

TRADE-OFFNo background location and a weaker offline story, both mitigated with caching and queued writes.

STACK

Typical stack.

APPLICATION
Next.jsTypeScriptNodeTailwind
DATA
PostgresRedisTime-series positionsMigration importers
INTEGRATION
Telematics APIProof-of-delivery capture
OPS
DockerAutomated backupsRole-based access control

Work of this shape usually runs as Agent Ops Sprint →

SIMILAR PROBLEM?

Tell us what you're dealing with.

One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.

Talk to an engineer →