Name, address and phone are merged into order emails, and the phone appears on the customer's confirmation screen so they know who to call to change an order.

How the storefront looks to your customers.

Menu typography

Menu search

Every bookable time slot is generated from these hours — closed days produce no slots, and ASAP shuts off when there isn't time to cook before you close.

Set a day's open and close to the same time to mean open 24 hours. A close time earlier than the open time means you trade past midnight (e.g. 5:00 PM – 2:00 AM).

To stop taking orders right now, use Order flow at the top of the page — that's the temporary pause. These hours are your standing schedule.

Which ways customers can receive their orders.

These prep times are the kitchen's lead time: the earliest bookable slot is never sooner than this, and ASAP switches off when there isn't time to cook before you close.

ZIP codes are enforced — checkout blocks delivery to an address outside the list. Radius is not: measuring distance needs an address lookup service, which this prototype has no provider for.

Let customers order ahead for a later time. Slots are built from your opening hours, so closed days and blackout dates are skipped automatically.

Two different cutoffs. Last bookable slot stops customers reserving the final minutes of service. Stop ASAP orders is last call — ASAP disappears once there isn't time to cook an order before you close, counting the prep time set above. Set it to 0 to allow ASAP right up until prep time runs out.

Stops a rush stacking more orders on one time slot than the kitchen can cook. Counts every order in the kitchen — ASAP, scheduled, and orders forwarded from DoorDash, Uber Eats or Grubhub. They all take up the same minutes, and the kitchen doesn't care which app the ticket came from.

Full slots show as Full and can't be picked; a day with no free slots disappears from the picker. Need to slow things down right now? Rush mode lives in the Orders tab — and in Order ATC — because it's something you reach for mid-service, not a setting you configure.

What you charge, and on what.

Whether delivery charges are taxable depends on your state — confirm with your accountant.

Any charge beyond the food itself — bag, packaging, service, small-order.

Add one, name it, set the amount. Nothing is charged until you add it, and no amount is prefilled: bag charges, in particular, are mandated in some places, banned in others, and set at different rates — use whatever applies where you trade. Tick Taxable only where the fee itself is taxed; that varies by fee and by jurisdiction, so confirm with your accountant. Fees are never discounted and never tipped on, and every fee is shown to the customer by name at checkout — hidden mandatory fees are illegal in a growing number of places.

The delivery fee is set in 10 · Delivery, alongside the delivery minimum and free-delivery threshold.

Tips go to your staff. They are calculated on the food, never on tax or fees.

A None option is always offered and can't be removed — a customer must be able to decline a tip.

How customers can pay at checkout.

Card entry is simulated — nothing is charged and no card data leaves the browser. Wire up a payment provider's hosted fields before taking real money.

Who actually moves the money. Section 6 decides what customers can pay with; this decides who processes the card.

That looks like a secret key. Never paste one here. Secret keys belong on a server that customers can't read — anything saved in this admin ends up in the browser. Use the publishable key (pk_…) instead.

The statement descriptor is what customers see on their bank statement, and it's printed on the refund email. If they can't recognise it, they call their bank instead of you — which is a chargeback. Max 22 characters.

Card checkout is still simulated in this prototype. Saving a processor here records the choice and shows the right branding at checkout, but no charge is attempted and no card data leaves the browser. Going live means swapping the storefront's card form for the processor's own hosted fields — which is also what keeps you out of PCI scope, because the card number never touches your page.

Alcohol, tobacco, anything requiring an ID. Off unless you sell it.

Show a highlighted row of items at the top of your storefront menu. Publishes live to the storefront.

Offer a few quick add-ons (a drink, a side, a dessert) in the customer's cart. Publishes live to the storefront.

Items already in the cart are skipped automatically, so customers only see things they haven't ordered yet.

The earn rate and reward catalog are program-wide — they're set once in Loyalty → Rewards and apply to every channel. This switch only decides whether online orders take part.

To the customer

To the restaurant

Add a recipient address, or these emails have nowhere to go.

Preferences are saved and drive the storefront, but no email is actually sent in this prototype — there's no mail server wired up.

Kitchen ticket

Get delivery-app orders onto the same screen as your website orders. Paste your forwarding address into each app's notification settings, and their orders appear in Order ATC.

Keep this private. Anything emailed to it becomes a live ticket in your kitchen. Don't publish it or use it as a contact address — only paste it into a delivery app's notification settings.

Connected apps

Tick Remits sales tax for any app that collects and pays the tax itself. Marketplace facilitators (DoorDash, Uber Eats, Grubhub) normally do — and if the box is wrong, your sales summary will report the wrong tax to remit.

Commission is optional. Leave it blank and the sales summary reports marketplace sales gross — the honest thing to do if you reconcile from each app's payout statement. Fill it in and the summary also shows an estimated payout. It can't know about promo fees, marketing spend or adjustments, so it will never match the statement exactly. A stale rate is worse than none: if you renegotiate, update it or clear it.

No live marketplace connection is wired in this prototype — the address and statuses are illustrative. Note that pausing orders in Order flow only stops your own storefront; delivery apps don't know about it, so you'd still pause inside each app.

Send customers a link, or drop the menu straight into your existing site.

Put a QR code on every table. Scanning it opens your menu with the table already selected — no pickup or delivery questions, and the order arrives in the kitchen tagged with the table number.

A message at the top of your menu. Holiday hours, a special, a delay, a closure — anything customers should see before they order.

Set up a code customers can enter at checkout for a discount. This is a prototype — codes here aren't yet wired to live checkout.