The things bakers ask before they sign up

You do. Card payments go straight into your own Stripe account, not ours — we never hold your money, and it is not sitting in a balance waiting on a payout schedule we control. Refunds, disputes and payouts are yours, in your own Stripe dashboard.

At your order deadline, not at checkout. You set how far ahead each delivery round or pickup window closes; when it does, the card is charged the estimated total and the order locks.

If something sells short on the day, you record what actually went out and the difference is refunded automatically. Customers are never charged for bread they did not get.

One flat monthly price, with no per-order fees: Starter is $39, Growth $89 and Pro $179 a month, or two months free when you pay yearly. See pricing. There is no setup fee and you can cancel anytime. Standard card processing still applies, charged by Stripe directly to you.

No. The trial runs 14 days without one. You will need Stripe connected before you can take a real order, because that is where the money goes — but you can build your whole storefront first.

Your storefront pauses; nothing is deleted. Your products, customers and their standing orders are all still there when you come back. Data is kept for 90 days after a cancellation before it is removed for good.

Yes, and it costs you nothing to run. Set up a pickup window — Thursdays 4–6pm at the bakery — and customers order ahead and collect. They can order once, or set up a standing order that works on pickup exactly as it does on delivery.

The market itself is yours to run — BakeFleet handles delivery rounds and pickup windows. If you hold the same stall every week, make it a pickup window: Saturdays 8am–noon at the market, and customers order ahead and collect from your stall. You can cap how many orders each Saturday takes so you only bake what fits in the van.

A pickup window repeats every week, so if you only go some Saturdays, run it at the bakery instead. Either way it keeps its own order deadline, so a Saturday pickup can close on Thursday for baking while a weekday delivery round stays open until the night before.

Yes — delivery rounds and pickup windows side by side, each with its own days, deadline and fee. How many you can run at once depends on your plan.

Delivery is by weekly standing order only. A pickup window takes standing orders too, and one-off orders from anyone who just wants a loaf this week.

A customer picks what they want every week — single items, bundles or both — and how they want it. Each delivery is generated and charged separately at your deadline, so they are never billed for a month up front, and they can skip a week or pause entirely from their own account.

Set how many of each item you have for a given day and the storefront will not sell past it — including when two people check out at the same moment. Each delivery round or pickup window can also cap total orders per date.

One button pauses everything: no new orders, no standing orders generated, no cards charged. Your storefront stays up with a note saying when you are back, and you can set that date to resume automatically. Existing subscriptions are untouched and pick up where they left off.

On the plans that include it, yes — your storefront answers on orders.yourbakery.com and we handle the HTTPS certificate. You add two DNS records at your registrar and we show you exactly which, and which step is still outstanding.

Every bakery also gets a free address on our domain that keeps working regardless, so nothing breaks while DNS settles.

Yours. Your name, your logo, your colours, your photographs. Order emails go out under your bakery's name too — customers are not reminded that BakeFleet exists.

No. Setup asks where and when you deliver or where people collect, and for your first product. Custom domains are the only part that involves DNS, and that is optional and copy-paste.

It is your data. Orders and customers export as CSV whenever you want, and deleting your account removes it rather than archiving it somewhere.

BakeFleet supports Utah's cottage food disclosures. You can set the disclosure your rules require and it appears on your storefront and in the acknowledgment customers accept at checkout. Each order stores the exact wording that was agreed to, so it stays accurate even after you edit it later.

If you bake outside Utah, check your own state's cottage food rules. Which rules apply to you is yours to determine — we give you the place to put them, not the legal advice.

You set a rate per postal code and it is applied at checkout. Deliveries are taxed where the customer is; pickups are taxed where the customer collects, which is usually a different rate.

No. Every bakery is isolated — products, orders, customers, settings and uploads. It is the property we test hardest, on every model and every page, because it is the one that would matter most.