One weekly rhythm, zero chasing.
A batch goes on sale, orders arrive as requests, and you decide what you can actually make.
Put a batch on sale
List what you're making this week — sizes, packs, and how many you can make. Set when orders close and when they're ready. Mark it weekly and next week builds itself.
Customers pre-order
They open your shop page, pick pickup or delivery, and check out as guests — no account, no app. On the pay-at-handover flow every order waits in your queue until you approve it.
Make it, label it, hand it over
Your picking list totals every item, and your recipes turn that into ingredient quantities. Print labels or packing slips, mark orders ready, and take cash or e-transfer at handover.
A store takes the order. Shop asks you first.
Every ecommerce platform is built on one assumption: the thing is already in a box, so the sale is finished the second the customer clicks. Small-batch food breaks that assumption. You don't have forty samosas in a box — you have a Saturday morning, a pair of hands, and a number you're willing to promise. Shop is built the other way round.
Approval is the order's first state — not a plugin, not a workaround. Stock, email and the customer's tracking page are all built around it.
Everything between “who ordered what” and the handover.
Catalog with variants
Photos, categories, six-packs and sizes — one product, many ways to buy it.
Batches with cutoffs
Set how many you can make, an order cutoff that walks back from the ready day, automatic weekly rollover, and skip-a-week when you're away.
Guest checkout
Name, phone, email, pickup or delivery. That's it. Customers never download anything or make an account.
Order approval & cash book
A queue of waiting orders, accept or decline in one tap, payments and refunds recorded against the order.
Picking list & ingredients
"40 samosas" becomes "3.2 kg potatoes" — recipes turn the day's orders into a shopping list.
Labels & packing slips
Thermal or laser labels with a QR the customer can scan to see their order; structured print, not a screenshot of a web page.
Customer emails you control
Placed, confirmed, declined, ready, on its way, paid — edit every subject and body, or switch one off.
Your look
Logo, colours, hero, theme, fonts, your story — a shop page that looks like your brand, on your own subdomain.
If you can only make so many, the order has to be a request.
Shop is for people who sell what they make, in batches, to their own customers — not for a warehouse. If the real constraint is a morning and a pair of hands, a receipt is the wrong first step and a request is the right one.
Shop is onboarding small makers by invitation while pricing is finalised. Tell us what you make and we'll set you up.
Talk to usSell what you make.
Pay for the size you are.
Weekly drops, pre-orders and pickup — plans scale with your staff and customer-email volume. Annual billing saves you two months. No setup fees, ever.
Shop pricing is being finalised.
Small makers are onboarding by invitation right now — home cooks, sweet shops, caterers, snack makers, preserve and pickle makers. Tell us what you make and we'll set you up with a plan that fits — no setup fee, cancel anytime.
Talk to usTo go live in minutes, your shop provides the following:
Prices in CAD. *WhatsApp messaging fees, custom-domain costs, payment processor fees, and SMS notifications billed separately or at cost. Automated daily backups are not available in the Starter plan; manual backups are available for download at any time. Annual billing is paid upfront. Cancel monthly plans any time; annual plans are non-refundable mid-cycle. WhatsApp notifications are subject to the terms of your chosen provider (Zernio, Meta, or Twilio).