Skip to main content

Project case study

Atimonan Laundry Shop

A full booking and service-operations application covering customer scheduling, order status, payments, notifications, and staff administration, backed by Express, Supabase, Redis, and production deployment on Vercel.

Engineering case study by Jonas Viray, Full Stack Developer & AI Automation Engineer

Atimonan Laundry Shop | project by Jonas Viray

Overview

The application covers the full service lifecycle rather than stopping at a brochure site. Customers can create bookings, choose pickup or drop-off schedules, follow order progress, and use supported payment options, while staff work from a role-based admin area for bookings, pricing, pickup, delivery, and service status. React Vite handles the customer and staff interfaces, with Node.js and Express services, Supabase data, Redis and Upstash infrastructure, Docker-based development, and Vercel deployment supporting the production system.

engineering summary

Problem → Architecture → Contribution → Result

Problem
A local laundry business needed more than a marketing site: customers needed booking, order tracking, and payment options, while staff needed a structured way to manage bookings, pricing, pickups, deliveries, and service progress.
Architecture
The application uses React Vite on the frontend with Node.js and Express services, Supabase for application data, Redis and Upstash for supporting infrastructure, Docker for containerized development, and Vercel for deployment. The customer flow also integrates PayMongo checkout and role-based staff operations.
Contribution
Built the end-to-end customer and operations flow, including booking with pickup or drop-off scheduling, order lifecycle tracking, customer accounts, payment options, and the role-based admin workspace for bookings, staff, pricing, pickup, delivery, and reporting.
Result
The system turns a traditional laundry workflow into a trackable digital operation where customers can manage orders online and staff can coordinate service delivery from a shared application.

Related service: Product Engineering & Business Systems, API & Platform Integration Engineering, Deployment & Production Infrastructure

Public product-surface details below are included as scope context from the observed site or application. They are not presented as claims about business outcomes, revenue, approvals, health results, or other client marketing metrics.

Observed product surface

  • Online booking with pickup or drop-off date/time scheduling and available time slots
  • Order status tracking from booking through washing, ready, out for delivery and completed
  • Online payment via PayMongo checkout, or pay at the counter on drop-off/receipt
  • Sign-in with email/password, Google or Facebook; profile with address and avatar upload
  • Role-based admin: bookings, customers, staff, services/pricing, pickup and delivery management
  • Reports dashboard (flow overview, lifecycle funnel, customer activity) with PDF and CSV export

Public product areas

  • Home / hero
  • Services
  • Pricing
  • FAQ
  • Branches & Operating Hours
  • Customer dashboard
  • Admin workspace

Intended audience · Laundry customers in the Atimonan community, plus shop admin, cashier and delivery staff

Planning a system with similar complexity?

Send the requirements, current stack, and constraints. I'll outline how I would structure the system, where the main risks are, and what an implementation path could look like.

All work