All work
Multi-location retailBG5 weeks build · ongoing on retainer
Four stores, one operations app — used daily from week one.
Internal web app for a four-location optics chain: order entry, inventory, dispatch, and CRM in one place.
4 → 1
spreadsheets retired
100%
staff adoption in week one
0
stockouts after first month
Real-time
visibility across all locations
Challenge
The state we found.
Four stores, four spreadsheets, no shared inventory view. Orders for custom lenses (with parameters like sphere, cylinder, axis) were being typed into emails. Customer data lived in a different system from order data. Stockouts were a weekly surprise.
Solution
What we built.
A Next.js app with Supabase auth and role-based access. Staff can submit orders with all optical parameters, which auto-update the central inventory and create the customer record in the CRM. Admins see a real-time dashboard across all locations.
Architecture
// 7 steps · production
- 01Supabase schema: customers, orders, inventory, locations, users
- 02Role-based access: store staff (own location), admin (all locations)
- 03Order form with validation for optical parameters and supplier mapping
- 04Inventory auto-decrement on order confirmation
- 05Dispatch view with batched supplier orders
- 06CRM auto-creation of customer records linked to orders
- 07Admin dashboard with daily / weekly / monthly metrics per store
Stack
Next.jsSupabaseLovableTailwindAirtable
Next case study
Read nextPersonalized PDF vouchers, generated and delivered on order.
Final word
Book the call. Bring the bottleneck.
30 minutes. No deck. We either see the automation in your process — or we tell you it is not worth building.