Case studyFood & pasalubong retail
Apo ni Lola
A mobile-first ordering page for Davao delicacies — QR payments, payment-proof uploads, admin approval and receipt automation.
- Ordering page
- QR payments
- Admin approval
- Receipt automation
- Project
- Apo ni LolaFood & pasalubong brand
- Industry
- Food & pasalubong retail
- Engagement
- Ordering page and order-management build
- Status
- Built
- Platforms
- Web app · QR payments · PrintNode
System map
Order flow
01Browse
- Products on mobile
02Order
- Order form
03Pay
- QR payment
- Upload proof
04Approve
- Admin approval
05Fulfil
- 80mm receipt via PrintNode
01Context
Apo ni Lola sells durian-inspired treats and pasalubong. I built a mobile-first ordering experience connected to the back office: customers order and upload proof of payment, the team approves, and receipt automation takes it from there.
Connecting a simple customer order flow to the back office that fulfils it.
02Problem
The shop needed a simple way for customers to order and pay, and a back office that moves an order forward only once payment is confirmed.
03My role
What I owned
- Ordering page and product management
- Order and client records with QR payments and payment-proof uploads
- Admin approval flow
- Receipt automation for 80mm thermal printing via PrintNode, only after approval
Platforms
Web app · QR payments · PrintNode
04Approach
- 01Order on mobileProduct browsing and a short order form designed for phones.
- 02Confirm payment firstQR payment and payment-proof upload; an admin approves before anything moves.
- 03Automate the receiptReceipt automation built around one rule: nothing prints on the 80mm thermal printer (via PrintNode) until payment is approved.
05System & deliverables
Delivered
- Mobile-first ordering page
- QR payments and payment-proof uploads
- Admin approval before fulfilment
- Receipt automation for 80mm thermal printing via PrintNode
06Evidence
Screenshots from the project and scope diagrams drawn for this portfolio. Select one to open it larger.
07Results & impact
- Built a mobile ordering flow connected to order records and payment proof.
- Structured fulfilment around one rule: nothing moves — or prints — until payment is approved.
No performance numbers are shown until they can be verified and shared — this section describes what was built, structured and tested.
08Lessons
- Automation should follow the business rule — here, nothing prints until payment is approved.