Situation
UMKM in Riau needed a digital system to replace rental and sales records kept in books, which were prone to human error and difficult to trace when items went missing or were damaged.
BACKEND / WEB / SYSTEM DESIGN
PROJECT / 02
Operational Platform for UMKM
A centralized platform for UMKM rental, sales, inventory, transaction history, and booth location management in Riau.
PROJECT OVERVIEW
A clear project story: situation, task, action, then result.
UMKM in Riau needed a digital system to replace rental and sales records kept in books, which were prone to human error and difficult to trace when items went missing or were damaged.
Bring rental, sales, inventory, and item history into one system, while making responsibilities clear for each user role.
We built a Node.js, Express, and TypeScript backend with a relational database, REST API, and Role-Based Access Control (RBAC). It supports transaction management, inventory, rental history, and booth location monitoring.
The system brought rental and sales workflows into one place, with access managed across three user roles: Director, Division Head, and Customer.
03 / PRODUCT GALLERY · 02 SCREENS
Use the arrows, dots, or swipe to browse the project screens.

WARUNG UMKM RIAU / HERO SCREENSHOT
IMPLEMENTATION DETAILS
The key decisions behind the implementation.
Node.js and Express expose REST endpoints for operational workflows.
Business rules remain separate from transport and persistence concerns.
PostgreSQL supports inventory, rental, sales, and booth data.
RBAC defines what each operational role can manage.
EVIDENCE & METRICS
06 / WHAT I LEARNED
The project reinforced the value of clear backend boundaries when one system has several operational workflows. Keeping the service and repository layers distinct made the system easier to reason about.