A bakery storefront that shares one source of truth with the bakery

The situation

A bakery selling in person needed a digital home that could also take orders — without becoming a second catalogue to maintain. Anything requiring products, prices, and availability to be entered twice would drift within a week, and the person keeping it current bakes for a living.

What we built

A storefront with an ordering flow that holds no product data of its own. Products, prices, images, capacity, and order state all come from BakeScope’s public API through a versioned contract; only brand and editorial content lives with the site.

That constraint is the whole design. Updating a price or marking something sold out happens once, in the back office, and the website follows. There is no sync step to forget.

How it runs

The site builds to static assets with a small server-rendered surface for the ordering path, and validates its content and its API contract at build time — so a mismatch between the storefront and the platform fails the build rather than surfacing as a wrong price on a Saturday morning.

Why it is here

This is also the proof that BakeScope’s public API works for a real consumer rather than only for its own management console. The bakery is the platform’s first tenant, and this storefront is what a tenant’s customers actually see.