
Healthcare group
36Retail ops · Case study
Mobile stock-take app — barcode scan, variance flags, and offline-friendly sync. We delivered the staff pwa as a live conversion surface for accurate counts.
01The delivered site
The layout we shipped for this project — desktop first, with a phone view where we have one.

02The brief
What we were hired to fix
Stock Check needed a staff pwa that did one commercial job: accurate counts. Mobile stock-take app — barcode scan, variance flags, and offline-friendly sync.
The constraint was not “more pages”. It was a retail ops audience who would leave if the next step was vague. We treated that as the brief, not a later optimisation.
We shipped a finished staff pwa — copy, layout and conversion path — so the team could run accurate counts from a URL they own.
03What we delivered
We built Stock Check as delivered work, not a concept. Structure, proof and the accurate counts path were designed together, then implemented as a maintainable front end.
Every block on the page has a job: explain the offer, show evidence, and move a real person to accurate counts. If it did not do that, it did not ship.
Pick, pack, route, count or onboard — we start from the job on the floor, not a module catalogue.
Status, exceptions and the next action on one screen. Colour is for flags, not decoration.
Warehouse, drivers, suppliers and desk staff see the same job, not three versions of the truth.
New locations, routes or job types slot in without replacing the desk they already learned.
04Outcomes
Visitors can complete accurate counts without a sitemap. The action sits where the offer is.
Stock Check reads as a retail ops staff pwa — not a reused template with the logo swapped.
The same structure takes a new offer, SKU or workflow without starting again.
—More work
Next step
A short call with the person who would run it — not a sales script.