Why I Built It
This started as an early contract pitch. The basic idea was simple: one server owns the inventory, terminal clients connect to it, and staff can view, search, update, and save material records.
The public version uses sample data. I kept the workflow and removed the company-specific context.
System Structure
The operator picks an action, enters inventory details, and sends the request to the server.
The server handles the request, updates the inventory logic, and sends back a plain text response.
Locations and material records live in a map, then save to a local file.
Interactive Preview
This is a browser-safe preview of the Java prototype. It does not represent live inventory records. It shows the intended workflow using sample racks, bins, item names, quantity changes, and low-stock checks.
Preview data is temporary and generalized. It is included to show the workflow, not to represent any actual stock records.
| Rack | Bin | Item | Category | Qty | Minimum | Status |
|---|
What It Covers
- Client input, server handling, and inventory logic kept separate.
- Basic socket communication using object input and output streams.
- Inventory modeling with racks, bins, item records, low-stock checks, and quantity adjustment safeguards.
- Local file persistence for prototype data.
- A practical workflow based on real inventory tracking problems.
Next
Database
Replace file-based persistence with a database, indexed search, and deeper rack/bin location records.
Authentication
Add users, roles, permissions, and protected admin actions.
Audit Trail
Log every stock change, location change, and save event with user and timestamp data.
Web Interface
A browser dashboard for users to oversee inventory values and review user input.