LakuPOS — Kasir & Warehouse System
Production POS & warehouse system untuk client ritel nyata — barcode scanning, QRIS payment, multi-outlet inventory sync. DDD architecture dengan E2E tests.
Context
A real retail operations surface that had to work for cashier flow, stock movement, and multi-outlet reality.
Project at a glance
Full-stack Point of Sale dan Warehouse Management System yang dibangun untuk client ritel nyata. Problem: client butuh sistem kasir yang handle multi-outlet, barcode scanning, dan QRIS payment dalam satu aplikasi — sebelumnya pakai Excel terpisah per cabang. Solution: POS tablet-optimized dengan 3 mode barcode scan (USB/camera/upload), real-time stock sync antar outlet, dan QRIS auto-generate. DDD architecture dengan Playwright E2E dan Jest unit tests.
What this case helps prove
The challenge
Client butuh sistem kasir yang bisa handle multi-outlet, barcode scanning, dan QRIS payment dalam satu aplikasi
The response
Full-stack POS dengan DDD architecture, real-time inventory sync, dan tablet-optimized UI
Why it mattered
Client aktif — sistem kasir harian untuk multi-outlet retail
Before and after, in clearer terms
The point of this section is not decoration. It is to show the operational shift in terms the client team can immediately recognize.
Checkout process
Before
Manual hitung + ketik ulang
After
Scan barcode → auto-add ke keranjang
Stok antar outlet
Before
Excel terpisah per cabang
After
Real-time sync + transfer antar outlet
Pembayaran QRIS
Before
Manual cek rekening
After
QRIS auto-generate, verifikasi otomatis
“Sistem kasirnya enak banget, bisa scan barcode langsung dari kamera. Stok antar outlet auto sync.”
Pemilik Toko
Client LakuPOS
Key highlights of the build
Kasir dengan Barcode Scanner
3 mode scan: manual/USB scanner, kamera, dan upload gambar barcode
Multi-outlet & Stok Transfer
Kelola stok real-time per cabang dengan transfer dan stok opname
DDD & Clean Architecture
Codebase production-grade dengan layered architecture, E2E & unit tests
Impact that stayed visible
What the system includes
Technology stack
Frontend
Backend & API
Integrations & Tools
Architecture & Testing
If this kind of operational shift is what you need, start from the problem.
The fastest useful next step is not asking for a random feature list. It is clarifying what feels weak today, what friction the team still carries, and what a cleaner first version should solve.