PWA and retail operations Case study
Jeweltime
The shop floor needed something that behaves like an app: installable, fast on a phone, and usable while a customer is standing there. It reads the catalogue from the existing WooCommerce database and keeps its own record of customers, orders and inventory.
The business problem
Retail staff needed an app-like workflow for catalogue browsing, assisted ordering and internal admin tasks.
What I delivered
- A production-oriented PWA web app using PHP, MySQL and Vanilla JavaScript.
- Installable PWA behaviour, offline-aware caching and web push notifications.
- Kavenegar OTP/SMS integration and a WooCommerce database read layer for products, prices, stock and media.
Technical approach
- Built a practical operations app rather than a decorative website.
- Kept the stack lightweight and understandable for ongoing support.
- Connected catalogue, ordering and admin workflows around retail use cases.
Result and evidence
The system supports catalogue browsing, assisted ordering and internal workflows with ongoing technical support.
Commercial value
The project demonstrates end-to-end product thinking across frontend, data access, notifications and operational usability.
Readable implementation brief
implementation_brief {
project: "Jeweltime"
context: "PWA and retail operations"
problem: "Retail staff needed an app-like workflow for catalogue browsing, assisted ordering and internal admin tasks."
delivered: "A production-oriented PWA web app using PHP, MySQL and Vanilla JavaScript.; Installable PWA behaviour, offline-aware caching and web push no"
evidence: "The system supports catalogue browsing, assisted ordering and internal workflows with ongoing technical support."
value: "The project demonstrates end-to-end product thinking across frontend, data access, notifications and operational usabili"
}What this project shows
The dual-database model is the decision worth discussing. WooCommerce stays the source of truth for catalogue and media; everything operational lives in the app's own schema rather than being forced into postmeta.
Building it as a PWA rather than a native app was a delivery choice. It reaches every device the staff already carry, and updating it does not involve an app store.