Tranches de Vie — an artisan bakery selling its bread online

E-commerce applicationTranches de Vie · Les 4 Sources · 2026 · Visit the siteRails 8 Hotwire Tailwind CSS Stripe PostgreSQL SMS

Tranches de Vie homepage — wood-fired breads and the next bake day

The homepage: bread, the wood fire, and the next bake announced in real time.

Bread catalogue with photos, variants and prices

The living catalogue: every bread, its sizes and prices — added to the basket in one click.

Basket with bake-day selection and production capacity gauges

The basket asks you to pick a bake day — showing the oven's remaining capacity, live.

Customer account page: orders, wallet and stats

The customer area, passwordless: sign-in by SMS or e-mail code, full bake-day history.

Prepaid wallet and SMS notifications toggled in one tap — “your bake is ready”.

Wallet page: balance, Bancontact top-up and transaction history

The bread wallet: top up with Bancontact, every order deducts itself.

Planned-orders calendar with products dragged onto bake dates

The calendar: regulars plan their bakes ahead, confirmed automatically at cut-off.

The context

Tranches de Vie is the artisan bakery of Les 4 Sources, in Belgium's Bocq valley: local flours, natural sourdough, long fermentations, and a wood-fired oven baking twice a week, on Tuesdays and Fridays.

The need

Taking pre-orders by hand no longer scaled: impossible to respect the bakehouse's real limits (oven, kneader, molds), to serve regulars who want their bread every week, or to chase payments. They needed an online shop that speaks the trade's language: the bake day.

The solution

A complete application, built with AI agents from architecture to deployment. Customer side: a living catalogue, a per-bake-day basket showing the oven's remaining capacity, online payment (Bancontact, card, Apple Pay), passwordless sign-in by SMS or e-mail code, a rechargeable prepaid wallet and a planned-orders calendar for regulars. Bakehouse side: a back office that plans production to the gram of dough, refuses what the oven can't hold, sends “your bake is ready” text messages, and goes all the way to financial reporting — Stripe fees, PDF invoices and revenue sharing between bakers.

The result

The bakery gets paid online, regulars plan their own bakes, and the baker opens the admin in the morning to know exactly how much dough to knead. All in production, used every week, baked over a wood fire.

The baker's back office

From order intake to baker payouts, the whole trade lives in the admin. The screenshots below run on a demo instance filled with fictional data.

A bake day sheet: day notes, order statuses, bakers on duty — Each bake day has its sheet: notes, order statuses, and who's baking today.

Capacity gauges: molds, kneader and oven in kilos of dough — Molds, kneader, oven: the app refuses any order the bakehouse can't hold.

Dough quantities required per flour type, computed automatically — The production sheet computes dough to the gram, flour by flour.

Orders list with fulfilment and payment statuses — Orders with their dual status: fulfilment (ready, picked up…) and payment.

Bake days list with orders and capacity percentage — Upcoming and past bake days, with their fill rate.

Customers list with SMS preferences, groups and wallet balances — The “eaters”: SMS preferences, discounted groups, wallet balances.

Products and variants management with prices — Products and their variants — sizes, prices, seasonal availability.

Reporting: revenue, average basket, Stripe fees and net revenue — Reporting: revenue, average basket, Stripe fees deducted to the cent.

Sales per product and top 10 customers — Sales per product and top customers — the baker knows what leaves the oven, and for whom.

Baker revenue report: gross margin, venue share, bakers' pool — All the way to revenue sharing: gross margin, venue share, the bakers' pool.

1 / 10

Have a similar project in mind?

See my pricing →