Commerce / Client project
Keep every laundry order moving.
A customer and staff workflow for registering orders, tracking cleaning status, and closing the loop when laundry is ready for collection.
- Project
- H2 Laundry
- My role
- Backend and application developer
- Scope
- Laundry ordering, customer records, pickup status, staff processing, and returns
- Built with
- PHP 7.4, PDO, MySQL, Bootstrap
- Period
- 2016–2020 · repository activity
- Project status
- Historical work
Engineering focus
Staff order queue
The PHP/PDO staff area joins customers, packages, and orders so operators can search work, see cleaning and payment states, inspect totals, and mark returns or completion.
Customer self-service
Separate customer sessions provide order registration, order history, pickup status, and a dashboard for collected versus waiting laundry.
Client project for a laundry service. The screenshots are of the real PHP application running locally after importing and scrubbing its historical schema; all names, phone numbers, addresses, credentials, dates, and order values shown in the captures are synthetic.
The full repository history runs 2016-11-28–2020-12-31; these are repository dates, not delivery dates. Current availability and maintenance of this historical application are unverified.
Keep every laundry order moving
A laundry service has two connected workflows. Customers need a clear way to see what they have sent, what is ready, and what has already been collected. Staff need one place to register orders, follow cleaning status, and close them when the customer returns.
H2 Laundry connects those views through a PHP and MySQL application. The customer area tracks orders and pickup state, while the staff area brings customers, inventory, payments, and order processing into one operational menu.
Give staff a practical order queue
The staff order view puts each order’s customer, cleaning state, payment state, date, total, and available actions in one table. That gives the operator a working queue for updating progress and handling returns instead of switching between separate records.
I contributed to the backend and application development. The project uses PDO for database access and Bootstrap for the server-rendered interface, with separate customer and staff sessions for the two sides of the service.
Keep the customer informed
Customers can sign in to see the total orders they have placed, which laundry has been collected, and which work is still waiting. Their order history keeps the same status and total information visible from the customer side.
These local captures use synthetic data created from the historical schema. No real customer names, phone numbers, addresses, passwords, or production activity are shown.
Working application
The workflow, in practice.
