Problem
Customers phone the pharmacy to ask what is in stock, when it is open, and whether a repeat can be prepared. The answers exist, but they live with whoever is at the counter, so the same question occupies staff time several times a day. The website, where there is one, is a page of text that has not changed since it was built.
Our role
Design and build, including the content model the pharmacy maintains itself.
Approach
Products and services are structured records with their own pages, so a change to stock messaging or opening hours is an edit rather than a request to a developer. The refill journey is a request flow: the customer submits what they need, and the pharmacy decides how to handle it. It is deliberately not an automated dispensing path.
Contact and customer information pages sit alongside, and an administrative side with Supabase behind it lets staff maintain the content. No clinical records are modelled, because nothing in this project should be mistaken for a patient record system.
Outcome
The public pages and the administrative side are built. The refill flow is implemented, but handling of personal or health information has not been assessed, so it is described as a request form and nothing more.
Notes
No prescription information, customer records, or health details appear here. The refill journey must be reviewed before it is used for anything real.