Online ordering and in-store pickup for shops and craftspeople.
Your products and prices on a site in your name: customers fill a basket, pick a pickup time and pay by card. In the morning you open the day's list, sorted by time, and every order on it is already paid.
Updated on
Demo: Maison Lebrun, a fictional bakery and pastry shop in Tours, built with Kubbler.
Your cakes and their prices
At the top of the home page, what you sell and for how much: the Paris-Brest at €26 for 6, €32 for 8, €38 for 10, collected on rue Colbert.
Ordering without a phone call
The "Choisir un gâteau" button opens the cake board: tap a size and it goes in the basket, then the customer picks a half-hour pickup slot, two days out at the earliest.
In the evening, on a phone
Plenty of cake orders are decided in the evening, phone in hand: the headline, the prices and the order button fit on the screen, with no app to install.
Today's orders
The shop's own screen: every paid order, sorted by pickup time, with the customer's name and phone number and the cake to bring out.
Maison Lebrun, a demo built with Kubbler.
Maison Lebrun is a fictional bakery and pastry shop on rue Colbert in Tours that makes its cakes to order. Its site takes cake orders paid online, and every morning the shop brings them out in order of pickup time.
7 products in the database, 2 or 3 sizes each, from €14 to €46
24 pickup slots a day, 48 hours ahead, 3 orders per slot at most
18 paid orders for Saturday 17 October, €646 taken
Maison Lebrun does not exist: the cakes, customers and orders are demo data, and Stripe payment is wired in test mode.
The whole site, page by page
Each thumbnail is a complete page of the demo, as a visitor sees it. On a computer, hover one to scroll through it.
One cake order, from basket to pickup shelf.
What your customer does on the site, step by step, and what you read of it in Kubbler at the same moment.
They choose from the board
Each cake with its photo, its sizes and their prices: fraisier for 8 at €30, Paris-Brest for 6 at €26. One tap on a size puts it in the basket.
You open the page in the Workshop
On the left, the home page's tree, section by section, from the hero to the cake board and the questions; on the right, the page as your customers see it. Change the headline or a photo, then publish.
They pick a pickup time
A fraisier for 8 and a Paris-Brest for 6, €56: they take Tuesday 20 October at 10:30. Only free slots are shown, and never less than 48 hours ahead.
You follow the order down to the database
In the Mechanisms view, the orderFlow block calls two routes: listSlots returns the free slots, submitOrder recomputes the price from the products collection, saves the order and sets up the payment.
They pay before coming in
Name, email, phone and a note for the pastry chef, "Joyeux anniversaire Louise", then "Payer 56 €". Card details go through Stripe and never touch your site.
The order lands in your table
One more row in the orders collection: customer, phone, cakes, total, pickup time, note, order status and payment status. It switches to paid once Stripe confirms.
Screenshots: the Maison Lebrun site, and the same project open in Kubbler with its demo data.
Saturday morning: 18 orders sorted by pickup time, all paid in advance.
At 6 am the pastry chef opens "Commandes du jour": the first order goes out at 7:00, the last at 18:30, and €646 is already in. The cakes come out of the kitchen in that order, each closed box is marked "Prête", then "Remise au client" at the counter. An order only reaches the list once it is paid, so every cake that leaves the kitchen has already been settled.
The day's total
Top right: 18 orders, 20 items and €646 taken, counted on paid orders only.
One row, one box
9:30, Nathalie Garnier, framboisier for 6 x2, €48, paid: the time, the name, the phone number and what goes in the box.
Ready, then collected
One button moves each order along, from "À préparer" to "Prête" to "Retirée", and the row is struck through once the customer has left.
What runs while you are at the oven, what stays in your hands.
Taking a card, hosting the site, showing the right legal notices: the work is the same for a bakery and a cheese shop, and Kubbler handles it. What you sell, your pickup times and your customers stay yours.
Our part
What has to work the day the first customer pays online, in place from launch and kept up to date by our team.
Card payment
The Payment brick takes each order in one go through Stripe, waits for Stripe's confirmation before marking it paid, then emails the customer a receipt.
Hosting in France
The site and its database run at OVHcloud, over HTTPS. The database belongs to your shop alone and is backed up automatically.
Legal pages and cookies
Legal notice, privacy, cookies and terms of sale sit at the foot of every page, and the banner refuses everything until the visitor has chosen.
Your part
What makes your shop: what you show, your pickup rules, your customers and your takings.
Your pages and photos
The headline, the photo of the Paris-Brest, the story of the shop, the opening hours on display: you change them in the editor, and the site shows them from the next publish.
Your pickup rules
48 hours' notice, half-hour slots from 7:00 to 19:00, three orders per slot, closed on Mondays: these rules live in the order block's routes, which you find in the Mechanisms view.
Your customers, your money
Orders and contact details stay in your site's database, and payments land in your own Stripe account: no platform sits between you and your customers.
Cake orders live in a notebook next to the till.
In a pastry shop, orders are taken at the counter in a spiral notebook, or over the phone in the middle of the lunch rush, receiver wedged against a shoulder. Size, day, time and the name to pipe on the plaque all have to be written down, and someone calls back when a word was misheard. In the evening, someone reads the notebook through to know what to bring out of the kitchen the next day.
At Christmas there are always a few yule logs nobody comes for: made, and never paid. An ordering platform takes the money for you, in exchange for a commission on every sale and your customers' contact details. A showcase website has lovely photos, then sends people back to the phone.
With Kubbler, you describe your shop, your cakes and your pickup rules, and the AI builds the site on the foundation our team keeps up to date: hosting in France, card payment through Stripe, cookies. The customer chooses, pays, and the order joins the day's list in its place by time. From the order button to the saved row, you can read what the site does at any moment.
What it costs
One project and 500 sparks a month, the budget that pays for AI generations. Packs can be added if you need more.
With your own domain: €44 excl. VAT a month.
No commitment. The domain name itself is paid separately.
See all pricesWhat to have ready
A list of what you sell, with sizes and prices.
Your pickup rules: minimum notice, hours, closing days.
One photo per product, even one taken on a phone on the worktop.
A Stripe account in the shop's name, to take card payments.
The shop's domain name, if it already has one.
Nothing else: no specification, no mock-up.
The questions we get asked.
Including the ones where the answer is "not yet".
The Starter plan is €29 excl. VAT per month, and hosting the site costs €5 excl. VAT per month on a kubbler.app address, or €15 excl. VAT with your own domain. Kubbler takes nothing from your sales; Stripe charges its own fees on each card payment. No commitment.
By card, in one payment, when they order: it goes through Stripe, into your own Stripe account, and payouts to your bank follow that account's schedule. Once the payment is confirmed, the customer gets an emailed receipt with the pickup time, and the order appears in your list for the day.
Not yet. The Maison Lebrun site only does in-store pickup at the chosen slot: no delivery address, no delivery fee, no round to plan.
Not yet. Card payment happens once, order by order: no subscription, no monthly direct debit, no payment in instalments. A regular customer orders again each week, and each order has its own payment.
Not yet: the site connects to no point-of-sale software. Orders paid online are in the day's list and in your Stripe account; counter sales stay in your till, as they do today.
Partly. Text, photos and headlines on the pages change in the editor, then you publish. Products and their prices are rows in the products collection: Kubbler shows them to you, read-only in production, and there is no screen yet to edit them yourself. For now, a new menu is prepared in the project and goes live with the next release.
Start with your menu, sizes and prices included.
In the Studio, you describe the shop, what you sell and your pickup rules: building the site starts from that description. You reread every page, connect your Stripe account, then put the site online in your name.