Built for a client

Inventory and Dispatch System

Stock, dispatch and sign-off stop living in three different places

A B2B inventory and field dispatch system covering goods-in, serial-level stock, job assignment, on-site reporting and closure. Where every unit went and where every job stands are both answerable questions.

Type: B2B management system
Scope: System design
Full stack
Deployment
Monitoring
Industry: Equipment installation and repair

Dashboard showing pending jobs, total stock and technician workload (demo data) — Fig.1Dashboard showing pending jobs, total stock and technician workloaddemo data

The challenge

Installation and repair work scatters information by its nature: the stock is in the warehouse, the job is in a chat thread, and the progress is in a technician's head. Asking where a particular unit is today means asking three people. Month-end reconciliation is the worst part, because nobody remembers how a job from three weeks ago was finally settled.

025 key points

What we built

Stock tracked down to the serial number
Not just quantities but individual units and where each one went, so a repair call can start from who installed this exact machine and where.
The whole path from dispatch to closure
Create, assign, report from site, close - with a record behind every state change, instead of scrolling back through a chat thread.
A separate deployment per client
One codebase, each client running their own database and service in full isolation. One client's problem cannot reach another, and one client's request never forces a change on everybody else.
A fully managed option
One client's instance runs on our hardware, exposed through an encrypted tunnel, so they need no server of their own and never touch certificates or updates.
Monitored after delivery, not just before
The client's production health checks and remote maintenance tunnel are both monitored, so an outage reaches us before it reaches their phone.