CASE STUDY
Operations
Rumah Plastik Inventory and Stock Approval System
An internal inventory application for managing items and recording stock movements through Staff requests, Admin review, and a final decision by the Head.
TECHNOLOGIES USED
Laravel 10 / PHP / MySQL / Blade / AdminLTE / Bootstrap / Chart.js / DataTables
PROBLEM
Incoming and outgoing stock involves several roles. If quantities change as soon as Staff submit a request, the inventory can get ahead of the actual decision. Outgoing requests must also account for stock already requested but not yet finalized, so parallel requests do not rely on the same available quantity.
MAIN FEATURES
-
01
Three-role approval
Staff submit requests, Admins review them, and the Head decides on incoming or outgoing stock.
-
02
Stock changes after final approval
Inventory is updated only when the Head approves a request.
-
03
Outgoing-stock reservation
Requests awaiting a decision are counted so available stock is not allocated twice.
-
04
History and dashboards
Item movements, request status, and stock summaries can be reviewed by role.
-
05
Inventory data management
Admins manage items, categories, suppliers, and user accounts in one application.
IMPLEMENTATION
The Laravel application separates access for Staff, Admin, and the Head. Staff request incoming or outgoing stock; the Admin reviews, forwards, or rejects each request; and the Head makes the final decision. Stock changes only after approval by the Head. When an outgoing request is submitted, the system accounts for stock reserved by pending requests. Database transactions and row locking keep approval decisions and stock updates consistent. Admins can also manage items, categories, suppliers, and users, while dashboards and history pages show stock movements and request status.
PROJECT SCREENS
Open screen 01 at full size
Open screen 02 at full size
Open screen 03 at full size
Open screen 04 at full size
Open screen 05 at full size
Open screen 06 at full size
RESULT
Each request has a traceable status from submission through the final decision. Dashboards summarize stock and item movements, while history pages separate incoming and outgoing stock. Quantities change only after a request receives final approval.
Need an application for a similar workflow?
Tell me who will use it, how the current process works, and which features are required. I’ll review the requirements before discussing the technical solution.
Talk About a Project