All projects

Client Project · 2026

Inventory Management System

Device and stock tracking for a WiFi service business — modems, cables, and equipment managed across regions serving 1000+ active clients.

Inventory admin dashboard — regional stock summary
On this page

Project Overview

Project type
Client Project
Year
2026
Role
Full-stack — solo, including deployment & handover
Status
Live · used in daily operations
Stack
Next.js · TypeScript · Prisma · PostgreSQL · Tailwind CSS · PWA · Vercel

The Problem

The client runs a WiFi service business with 1000+ active clients. Equipment — modems, patch cords, fiber and LAN cables — was tracked in notebooks and memory across several regions.

Nobody could answer basic operational questions: what's in stock, what's out in the field, which client is holding which device, or how much cable is actually left on the reel.

My Responsibilities

  • Data model for items, regions, stock movements, modem registry, and client allocations
  • Admin dashboard — summary, per-item stock, status distribution, meter-unit analytics
  • Stock in / out / inter-region transfer flows
  • Excel export and editable stock tables
  • Installable PWA setup for field use
  • Deployment and handover

Core Workflows

01

One dashboard per region

The admin opens to a regional summary — registered items, total stock, deployed units, remaining — plus a per-item stock chart, a status donut (safe / critical / empty), and separate analytics for meter-unit items like cables.

02

Record stock in, out, and transfers

Stock movements are first-class actions: Barang Masuk (in), Barang Keluar (out), and Kirim Barang (send between regions). Every movement is recorded — nothing is just edited in place.

03

Track devices to clients

The modem registry (Daftar Modem) and movement history (Arsip Riwayat) answer which device went where and when — per client, per region.

04

Used from phones in the field

The panel is an installable PWA — staff add it to their phone's home screen and work from it on-site. A public mode allows read-only viewing without an admin session.

The same panel on phones — summary, stock chart, and the stock data table with Install App prompt.
The same panel on phones — summary, stock chart, and the stock data table with Install App prompt.

System Architecture

Frontend

  • Next.js App Router — dashboard, movement flows, registry
  • Installable PWA — the panel behaves like a native app on staff phones

Backend

  • Route handlers for stock movements, registry, and reporting
  • Excel export for the stock data table

Data

  • PostgreSQL with Prisma — items, regions, stock movements, modems, client allocations
  • Two unit models: per-unit items and meter-tracked items (fiber & LAN cable)

Deployment

  • Deployed on Vercel with a custom domain, handed over running

Key Engineering Decisions

Stock is derived from recorded movements

In, out, and transfers are stored as events, not edits to a counter — so current stock is computed from history, and the audit trail (Arsip Riwayat) exists by design, not as extra work.

Two unit models — units vs meters

A modem is counted; a cable reel is measured. Meter-unit items get their own analytics (total / used / remaining in meters) instead of being forced into piece counts.

Region-scoped stock with first-class transfers

Every item belongs to a region, and moving stock between regions is a real operation — which is what makes per-region summaries trustworthy.

Challenges & Solutions

Challenge

Equipment constantly moves — to the field, to clients, between regions — so a simple stock number was always wrong.

Solution

Recorded every change as a movement with a destination, and derived current stock and per-client holdings from that log.

Challenge

Cables aren't countable items — 'we have some FO cable' means meters, not units.

Solution

Modeled meter-tracked items separately with their own totals, so cable stock reads as length used and remaining.

Validation & Testing

  • Cross-checked recorded stock against physical counts per region
  • Tested in / out / transfer flows, including inter-region sends
  • Verified PWA installation and daily flows on the phones staff actually use

Outcome & Current Status

The system is live and used in daily operations for a business serving 1000+ clients — replacing notebook and memory tracking with a single panel.

Stock levels, device locations, and cable lengths are now queryable facts instead of estimates.

What I Would Improve

  • Serial-number or barcode scanning for individual devices
  • Low-stock alerts per region before items hit critical
  • Technician-level roles so field staff see only what they carry

Next project

Rysee