Power Zone Inventory Management System
An inventory system for an industrial equipment importer, tracking components from import through assembly to fulfilment.
The essentials
- Sector
- Industrial equipment / import and assembly
- Engagement
- Custom software build
- Services
- Custom Software, Data & Reporting
- Stack
- TypeScript, Next.js, PostgreSQL, Supabase
Status: Built for PowerZone and in daily use.
What changed for their team
fewer stock mismatches
Recorded counts now match what is physically on the shelf.
faster issue resolution
Discrepancies are traced to the movement that caused them instead of being hunted across files.
spreadsheets in the workflow
Every part, movement, and count lives in one system.
Figures reported by Power Zone from their own records after the system went into daily use. Approximate, and specific to this deployment.
What needed solving
PowerZone imports components, assembles them into finished units, and ships those units from more than one warehouse. All of that was tracked in spreadsheets, so the true position of stock was spread across several files and several people. Nobody could answer what was in each warehouse, what was still in transit, and what had already been committed to a customer, without stopping to reconcile by hand.
How we tackled it
We modelled the business as it actually runs, rather than fitting it to a generic inventory template. Components are tracked from the moment a shipment is raised, through receiving, through assembly into finished units, to the order that consumes them. Every stage is one place in one system, and each team only sees the modules their role needs.
The build
- A live view of stock by stage: in transit, received, assembled, and committed
- Assembly tracking that pairs components into finished units and keeps both counts honest
- Multi-warehouse transfers, so stock moving between sites is never counted twice
- Role-based modules, so receiving, assembly, orders, and fulfilment each have their own surface
- Spreadsheet export on every table, because the team still needs to hand numbers to other systems
Choices that mattered
Model the stages, not just the totals
A single stock number hides the thing that matters: whether a unit is in transit, on the floor, built, or already promised. Modelling each stage separately is what makes the totals trustworthy.
Beat the spreadsheet on its own terms
The system it replaced was a spreadsheet, so per-column filtering, sorting, and export had to be at least as good. Anything slower to use than the old way does not get adopted, however correct it is.
How we could help you
Let's build something that lasts
Tell us what you need. We reply within 24 hours and scope the work honestly, committing only to what we can ship.
Prefer to talk? Book a 30-minute intro call
