Square as catalog + payments source of truth
Anything that rings through the studio POS lands in the storefront automatically. Inventory stays single-source, payment provider is already wired for in-person + online.
Before / After · Case Study
Let's Go Paint — a pottery studio whose website finally talks to the register
- Painting & Trades
- Local Pro Services
The Seal Beach paint-your-own-pottery studio had a brochure website with manual booking — what sold at the counter and what happened online were two separate worlds. Now one site serves all four of the studio's web addresses, and whatever rings through the register in the studio shows up online automatically.
🔒letsgopaint.space
At a glance
What this rebuild covers.
Selling & payments
The studio's register is the single source of truth — anything rung up at the counter lands in the online store automatically, and one payments setup covers in-person and online.
Theme & color
All four web addresses render from the same site, each served its own brand variant by address — the studio's colorful, playful paint-studio feel stays consistent from one to the next.
Design
The rebuild was pinned to a fixed visual reference, so every section could be checked against a known target instead of drifting during the port.
Email
Email marketing runs off the same customer list as checkout and booking, so a booking guest and an online shopper are the same person to the studio.
Agents
A voice agent is wired to the studio's phone line, feeding calls into the same customer records as web inquiries.
The pixel diff
Overview, then the walkthrough.
Left: everything the legacy site shipped — frozen in place. Right: an auto-scrolling tour of the rebuild, from hero to booking. No slider to fight with.
🔒letsgopaint.com
This is everything the legacy site had to offer above the fold. No pricing, no calendar, no booking — the funnel ended at a mailto.
🔒letsgopaint.space
Auto-scrolls through the modern site so you can see the booking surface, the package grid, the pricing table, and the calendar inline — without leaving this page.
The four beats
Problem · Insight · Build · Outcome.
Scroll past the legacy frame. The four beats land in order. At the end, the modern site fades into the same window.
- 01 · Problem
Studio POS, no web pipeline.
The legacy site was a brochure. Booking was manual. POS sales didn't surface online; online inquiries didn't surface in the studio.
- 02 · Insight
Treat Square as the catalog database and bend the storefront to it.
Square is already where the studio runs day-to-day operations. The storefront reads from Square, not the other way around.
- 03 · Build
Headless Medusa + Square-backed storefront + multi-domain variants.
Same headless pattern as BMH and Buck Mountain. Phase 1 visual contract pinned to `storefront/public/lgp-modern-v1.html` so component ports compare against a known target.
- 04 · Outcome
A studio that runs online the same way it runs in person.
POS ring → storefront inventory update. Online booking → studio calendar entry. Email + voice + fulfillment all wired to the same Medusa customer table.
🔒letsgopaint.com
01 · Problem
Studio POS, no web pipeline.
The legacy site was a brochure. Booking was manual. POS sales didn't surface online; online inquiries didn't surface in the studio.
02 · Insight
Treat Square as the catalog database and bend the storefront to it.
Square is already where the studio runs day-to-day operations. The storefront reads from Square, not the other way around.
03 · Build
Headless Medusa + Square-backed storefront + multi-domain variants.
Same headless pattern as BMH and Buck Mountain. Phase 1 visual contract pinned to `storefront/public/lgp-modern-v1.html` so component ports compare against a known target.
04 · Outcome
A studio that runs online the same way it runs in person.
POS ring → storefront inventory update. Online booking → studio calendar entry. Email + voice + fulfillment all wired to the same Medusa customer table.
🔒letsgopaint.space
For the technically curiousHow it was done
- 01
Where it started
The legacy letsgopaint.com was a brochure — pretty pictures, limited booking handled manually, and a hard wall between the web and the studio floor. Sales through the in-store register never surfaced online, and online inquiries never surfaced in the studio. Meanwhile the brand had accumulated four domains (.com, .art, .space, .org) with no coherent strategy across them.
- 02
The insight
The studio already runs its whole day on its Square register — so instead of building a second catalog that someone has to keep in sync, treat the register as the catalog database and bend the storefront to it. The storefront reads from the register, not the other way around, and the payment rail that already handles in-person sales handles online sales too.
- 03
The rebuild
A custom storefront on our hosting platform, backed by our commerce engine and a managed database, with the register as the catalog and payment source of truth. All four owned domains collapsed into one storefront that serves a brand variant per host — one codebase, four faces. The first visual phase was pinned to a static reference page so every ported component compared against a known target instead of an evolving one.
- 04
What runs now
A ring at the register updates storefront inventory. An online booking becomes a studio calendar entry. Email marketing, shipping-label fulfillment, and a phone voice agent are all wired to the same customer table in the commerce engine, with privacy-friendly analytics over the top — the studio runs online the same way it runs in person.
Before
- Brochure site
- Manual booking
- POS disconnected from web
After
- modern web framework
- headless commerce engine
- managed database
- Square (catalog + payments)
- Klaviyo (email)
- Shippo (fulfillment)
- Synthflow (voice)
- Plausible (analytics)
What changed, with evidence
Multi-domain strategy collapsed into one storefront with brand variants
All 4 owned domains (.com, .art, .space, .org) render from the same storefront, themed per host — same pattern as the JP Taylor Group multi-tenant platform.