01
Schedule
Today at the top: what is being delivered, and when to start baking. Orders from the site arrive here as cards you accept or dismiss in one tap. You can close an hour or a whole day on the site from here.
No magic, no jargon
You will never touch any of this. But you should know what you are buying, so here it is, without the jargon.
From her phone to your oven
On your site. She sees only the days and times you can actually bake for — full days are already closed.
The order opens in her WhatsApp, already written: products, quantities, delivery zone, total.
As a WhatsApp message, and as a card in your schedule. If the second ever fails, the first still arrives.
One tap. The customer record, the schedule entry and the sale are created together. Stock comes off.
The way you already do. No card gateway, no commission, no platform between you and her.
WhatsApp is what makes the sale, always. The rest saves you the typing — and if any of it ever breaks, the order still reaches you.
This is your customer’s side
Tap a few things, choose where and when. The order message writes itself as you go — that is exactly what lands on your phone, ready to confirm.
Your Bakery
What you sell
Serves 8 · order a day ahead
Mixed, baked the same morning
Serves 6
Warm from 8 a.m.
Where it goes
When
What lands in your WhatsApp
Add something, and the message starts writing itself.
A demo of your own site. Your products, prices, currency, delivery zones and opening hours are set once, for you, at setup.
A public site your customers use, and a private app only you can open. Between them, a database. There is no server in the middle — nothing to administer, nothing to restart, nothing that falls over at three in the morning. That is deliberate, and it is why the running cost stays low enough for a home bakery.
Public
Private
The app tells the site
prices, what is in each box, which days are full, which hours are closed
The site tells the app
orders placed, and how many people looked without ordering
The site can never create anything in your books. An order from the site arrives as a proposal, and it only becomes real when you accept it. That is a rule of the system, not a setting.
Six screens, and nothing else to learn
Built for someone who has never used business software, on a phone, with flour on their hands. Six tabs along the bottom. That is the whole thing.
01
Today at the top: what is being delivered, and when to start baking. Orders from the site arrive here as cards you accept or dismiss in one tap. You can close an hour or a whole day on the site from here.
02
Profit this month, and cash on hand today. Then what needs you, and what is running low with what to buy first. When you are busy it shows two numbers; when you are not, everything is one tap underneath.
03
Your ingredients in four families, folded away until you need them. Search, sort, and a clear count of what to buy. Stock comes off by itself as orders are accepted — you never type a subtraction.
04
Your menu, with the recipe behind each product. The recipe is what makes stock work, what deduces allergens for the site, and what tells you how many batches you can still bake.
05
Every sale, with the price frozen as it was on the day. A price you change today never rewrites what you earned last month.
06
What you bought, at what price. This is what turns "money came in" into "this is what I actually earned".
The part nobody else gives you
Most tools tell you what came in. That is revenue, and it feels wonderful. This tells you what is left after the flour, the boxes, the gas and the driver — and how much of it is money you actually have.
Every sale carries its real cost, taken from the recipe and the price you actually paid for the ingredients.
What is in the bank, separate from the value of stock you have bought but not yet sold.
Raise a price today and last month stays exactly as it was.
How many visits turned into orders, and which link brought them — without a single third-party tracker.
Tested, not hoped
More than nineteen hundred automated checks run before anything is released. They do not check that the code runs — they check that the answers are right.
Profit, stock, delivery fees, production limits, the order message itself.
Every guarantee here was verified by deliberately breaking the code it protects, and watching the check catch it.
If a change breaks one, either the change is wrong, or the rule changed — and then the check is rewritten to state the new rule, with the reason.
The whole database, automatically. And the restore has been run, not assumed.
Your business, your data
Your own site, your own app, your own database. Nothing shared or pooled with another business.
Access is by named account. Your customers never leave your setup.
None. Not analytics, not advertising pixels, not social widgets. This is verified by an automated check, not promised in a footer.
Products, recipes, customers, orders, sales history. And if you leave, I export the lot and hand it over.
Thirty minutes on WhatsApp and I will show you the private app, screen by screen, on the bakery it was built for.
Samer Amgira · Paris — La Défense