Instaurant: the restaurant product

Written from the code, not from memory. Every feature below is one somebody can actually reach today; anything absent from this page is absent from the product.

The store type is restaurant (StoreFeatures::isRestaurant()), and it is what switches the restaurant-only surfaces on. Bookings are labelled Reservations and the booking button reads Reserve a Table. Products are labelled Menu.

Build a pizza: the visual pizza configurator

A full-screen visual builder (configurator block): a cover scene, the pizza on top of it, an ingredient panel, sizes and topping add-ons priced individually. The block carries its own catalogue in its settings rather than reading the product list, so a pizzeria can run the builder without modelling every combination as a product.

Is there a kitchen board? Yes, for a tablet in the kitchen

A live order screen at /admin/kitchen, with its data and status endpoints alongside it. It is designed for a tablet in the kitchen: it opens through a secret ?k= link that needs no admin login, so the pass does not have to hold an account or stay signed in on a shared screen.

Order status texts: preparing and ready

Moving an order on the board to preparing or ready texts the customer. The wording is fixed and templated: received, preparing, and ready for pickup. Self-gating, so it is a no-op where SMS is not available.

Can customers leave a tip? Yes, tipping and gratuity at checkout

Checkout accepts a gratuity. It is added on top of the total after discounts, never reduced by coupons or loyalty, rounded, non-negative, and capped as a garbage guard. Stored on the order as tip_total.

Scheduled orders: pickup or delivery later

Checkout accepts a future pickup or delivery time (scheduled_for). Only a real, non-past datetime is stored; anything else is treated as ASAP.

What it shares with the rest of the platform

Menu as products, cart and Stripe checkout, the smart chat, the booking engine for reservations, SEO, and the InCommand phone app.

What Instaurant does NOT have

No delivery-driver dispatch or routing. No table management or floor plan. No POS or till integration. No kitchen printer support: the board is a screen. No integration with delivery marketplaces. Say so plainly rather than implying it.

Where it lives

Master template: page 145 (/restaurant), which is a cinematic page and carries the configurator. Marketing page: 205 (/restaurant-software).