Retail · Live
Optician website and ERP-linked back office
A static rebuild of an optician group’s website, moved off Shopify, with about 180 pages, 20 journal articles and enquiries over WhatsApp. Staff edit the catalogue in an admin, and a back office pulls the frame catalogue from the store ERP every night so products on the site match stock.
- Client
- An optician group with several stores
- Status
- Live
- What it is
- Portals, Integrations, Internal tools
- Scope
- 180 pages moved off Shopify
What it does
The modules.
- Website
Collections by brand and shape, product pages, a journal, store pages and site search.
- Catalogue admin
Products, brands and filter values, with image upload and a publish button.
- ERP mirror
The frame catalogue pulled from the store ERP nightly, ready to turn into website products.
- Staff launcher
One sign-in for the back-office apps.
Built with
Integrations
What it connects to, and why.
- SE Store ERP API
Nightly pull of the frame catalogue
-
SupabaseCatalogue tables, staff sign-in and image storage
-
VercelHosting, the nightly sync and rebuilds when staff publish
-
WhatsAppProduct enquiries from every page
The story
Before and after.
Before
- A Shopify store the business did not need for checkout
- A website catalogue kept in step with the ERP by hand
After
- A fast static site with the same look, and enquiries by WhatsApp
- ERP frames mirrored nightly and published to the site from one admin
What success looks like
- Staff publish catalogue changes themselves
- What the website shows matches what the stores hold
What changed for the team
Store staff work in one back office; publishing the site is a button, not a developer request.
How we support it
More back-office apps are planned in the same launcher.
Care plans start at $50 a month.
Something similar
Want this, built around your tools?
A discovery call with the people who built it. You leave with a yes or no on fit and the first thing we would build.
Book the call