Official SpicyChef help, open to everyone.
The restaurant settings are where you keep your establishment's core configuration current: general
The Event logs give you a trustworthy history of what happened in the active restaurant: who changed
The Home dashboard is the landing screen for the active restaurant. It gathers a set of favourite
The team settings are where you manage who works in the active restaurant: invite new members, assign a
Notifications keep you aware of things that need attention in the active restaurant, such as a booking
The Booking Engine settings screen controls the public booking widget your guests use to reserve
The Guest communication screen is where you manage the emails your restaurant sends around a booking:
The Bookings screen is where you track every reservation for the active restaurant: who is coming,
The Guests screen is the directory of everyone who books at the active restaurant. Open a guest to see
Bundles and set menus let you sell several products as one priced offer. You define choice groups (for example a starter, a main, and a dessert) and how the bundle price is allocated across the components diners pick.
The catalog at /pos/catalog defines what you sell: products, prices, taxes, accounting categories, and accepted payment methods. It is the reference that every order and invoice draws from.
Guests scan the QR code on their table, read the menu in their language on their phone, and send dishes themselves. Their dishes join the table's order and reach the kitchen like any other dish, so your team keeps one order per table and takes payment as usual. Team members can still take orders at any time.
The invoices list at /pos/invoices and the receivables view at /pos/unpaid cover the life of a POS bill: finalize it as paid, or finalize it unpaid with a payer and a due date, then track what is still owed.
Two POS views let your team work as the kitchen or as a waiter, whatever their role. A waiter takes the order and taps Send to kitchen. The kitchen sees each batch as a ticket and marks dishes ready, and the waiter sees what is ready to pick up. Service stays the full register view for orders, invoices, and payments.
POS printing at /pos/printing produces kitchen and service tickets and customer receipts. It is an audited output channel that snapshots order, invoice, and correction data; it is not the fiscal source of truth.
POS reports at /pos/reports summarize activity for the active restaurant: sales and payment summaries built from finalized invoices and recorded payments, so you can read the day's takings at a glance.
A service session is the operational center of the POS. Run it from /pos/service: it groups the orders, table moves, and service context for one booking or walk-in from the moment guests sit down until settlement.
Record payments against a POS invoice and finalize it once the balance is settled.
The Content, Media, Template, Design, and Pages screens let you edit what your website says and shows. You fill in validated text and images inside a chosen template; you never edit template code. Media you upload — photos and files — belongs only to your restaurant.
The Website screen is where you manage your restaurant's public website from inside SpicyChef. Each restaurant has exactly one website, and everything you change here — pages, content, media, and domains — is prepared before it reaches your visitors.
Publishing turns your draft into the live website that visitors see, and the Domains screen controls the web address it is served on. Publishing is all-or-nothing: it only goes live after validation and a successful build.