Qohira — E-Commerce Manual Payment
Production e-commerce untuk client nyata — manual payment verification, real-time inventory, admin dashboard. 16 produk, 6 orders, 5 users aktif.
Context
A commerce workflow where the important layer was not style alone, but order verification and admin clarity.
Project at a glance
Full-stack e-commerce platform untuk client ritel yang butuh toko online dengan alur pembayaran transfer bank. Problem: konfirmasi pembayaran manual via chat WA, data pesanan tersebar, tidak ada notifikasi otomatis. Solution: customer upload bukti transfer → admin verify di dashboard → auto email + web push notification. Type-safe end-to-end dengan tRPC + Prisma ORM.
What this case helps prove
The challenge
Client butuh toko online dengan alur pembayaran manual (transfer bank) dan verifikasi oleh admin sebelum pesanan diproses
The response
E-commerce platform dengan manual payment verification flow — customer upload bukti transfer, admin konfirmasi via dashboard, notifikasi otomatis via email & web push
Why it mattered
Dipakai client nyata — admin dashboard aktif untuk kelola produk & pesanan
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.
Kelola produk & pesanan
Before
Chat WA manual, data tersebar
After
Dashboard terpusat — produk, pesanan, stok
Verifikasi pembayaran
Before
Cek rekening manual via WA
After
Customer upload bukti → admin verifikasi di dashboard
Notifikasi
Before
Manual chat satu-satu ke buyer
After
Auto email + web push saat status berubah
“Sekarang semua pesanan dan konfirmasi bayar masuk satu tempat, gak perlu cek WA terus.”
Pemilik Toko
Client Qohira
Key highlights of the build
16 Products, 6 Orders
Data nyata dari production database — dipakai client aktif
Manual Payment Flow
Upload bukti transfer → admin verify → order confirmed otomatis
Push Notifications
Web push + email alerts untuk order baru & status update
Impact that stayed visible
What the system includes
Technology stack
Frontend
Backend & API
Services & Integrations
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.