Restaurant & Online Ordering

Ember & Plate

A restaurant site where the order lands on the kitchen's board.

● Live DemoNext.jsSupabaseBilingual EN/FRKitchen dashboard

edben-restaurant.vercel.app/en

The Ember & Plate landing page shown in a desktop browser window.

Why it exists

Most restaurant websites stop at a PDF menu and a phone number. The guest reads, calls, and someone writes the order on a pad. Ember & Plate closes that gap in both directions: the guest builds their order on the site, picks pickup, delivery or dine-in, and the kitchen watches it arrive on a board it can actually work from.

From the table to the kitchen

A guest filters the menu, adds dishes with notes and quantities, and checks out as pickup, delivery or dine-in. The order appears on the kitchen board in the New column and moves through Preparing, Ready and Completed with one tap - no tickets, no phone, no transcription errors.

The Ember & Plate menu with the order drawer open, showing quantity steppers, a per-dish note and the subtotal. — What the guest builds

The Ember & Plate kitchen order board, with cards across the New, Preparing, Ready and Completed columns. — What the kitchen works

Most guests order from a phone

The menu, the category filters, the order drawer and checkout are built mobile-first rather than shrunk down. Dish photos stay large enough to sell the food, and the running order stays reachable with one thumb.

The Ember & Plate menu on a phone, showing the category filter row and a dish card with its discounted price and an add-to-order button.

The restaurant runs it itself

The Ember & Plate admin dashboard, with revenue, orders, pending orders, reservations and average order value tiles above seven-day revenue and order charts. — The manager’s dashboard. The day opens on one screen: revenue so far, order count, what is still pending and how many tables are booked, with the last seven days charted beside the dishes actually selling.

The Ember & Plate dishes table in the back office, with thumbnails, struck-through original prices, status badges and the availability toggle. — Dishes, prices, photos, categories, promo codes and opening hours are all editable in the back office, in both languages. Sell out of ribeye at seven? Toggle it unavailable and the public menu updates immediately.

Under the hood

The stack and the architecture decisions behind the platform.

Frontend: Next.js (App Router), dark-first design with a light theme toggle
Backend: Supabase (Postgres, auth, storage)
Ordering: Cart with per-item notes, pickup / delivery / dine-in, promo codes, tax calculation, pay on pickup
Kitchen: Order board with New / Preparing / Ready / Completed states, plus a list view with filters
Reservations: Party size, date and time-slot booking with special requests
Back office: 11 modules: dashboard, orders, dishes, categories, reservations, customers, promotions, reviews, analytics, settings and account
i18n: Full English and French across the public site and the admin