A storefront, not a listing
Menu browsing, dish pages, cart and checkout designed for a single restaurant's brand, typography and palette. No marketplace ranking, no competitor next to the order button, no commission on each order.
Restaurant commerce platform
Platestead gives a restaurant its own website, its own domain and its own ordering system, then runs the software underneath: menus, pickup and delivery, payments, and a live link to the till.
restaurant.platestead.com or the restaurant's own domainA restaurant ordering platform built around independence. Each brand looks and behaves like its own business, because it is one: its own storefront, its own menu, its own customer list. Platestead is the layer that makes that practical to run.
Menu browsing, dish pages, cart and checkout designed for a single restaurant's brand, typography and palette. No marketplace ranking, no competitor next to the order button, no commission on each order.
Every restaurant runs as its own deployment: its own database, secrets, email sender and point-of-sale connection. One restaurant's data, traffic or integration outage cannot reach another.
All storefronts share one codebase. A fix or feature is built once, tested once and rolled out per restaurant, so small brands get software that keeps improving.
A restaurant gets a slug and appears at
slug.platestead.com, over HTTPS, ready to point its own domain at
later.
Categories, dishes, prices, photos and stock come from the admin, a setup file, or an import from the restaurant's existing point-of-sale catalogue.
Choose pickup, delivery or both, per location. Take card payments or let guests pay at the counter. Checkout, tax and fulfilment follow the restaurant's own setup.
Orders reach the kitchen through the point of sale, inventory stays in step, emails go out under the restaurant's own sender, and reporting is a question away.
Categories, dish options, prices per currency, availability and stock per location.
Guests choose which kitchen they collect from; the order is fulfilled, taxed and routed from exactly that location.
Courier delivery through DoorDash or Uber Direct, shown only when a restaurant actually delivers.
Card payments through Stripe, or settle at the counter for collection orders.
Square and Clover: catalogue and inventory in, completed orders out, per merchant and per location.
An optional chat assistant that answers from the restaurant's own menu and policies, and declines anything else.
Order confirmations and account email from the restaurant's own verified domain.
Revenue, order status and fulfilment performance, available in the admin or to an AI assistant through a read-only connector.
Server-rendered storefronts with per-page metadata, several languages and currencies, and image handling built in.
Containerised deploys, health checks, error monitoring and per-restaurant rollback.
Two storefronts run on Platestead today. Both are operated by Platestead as demonstrations of the platform rather than by outside restaurants, so you can click through the whole ordering flow without disturbing a real kitchen.
Platform deployment
A neighbourhood restaurant storefront: editorial homepage, full menu, pickup and courier delivery, card payments and a live point-of-sale connection. The reference deployment, and the one new platform work is proven against first.
Visit the LocalTable storefrontDemonstration deployment
A second brand on the same platform with a different look, its own menu in Indian rupees, pickup-only ordering and pay at pickup. It exists to show how a new restaurant is stood up: separate data, separate configuration, same software.
Visit the Ember & Fork storefrontPlatestead is assembled from proven pieces rather than a single black box, so a restaurant's data and integrations stay portable.
Spree Commerce on Rails for catalogue, orders, stock, tax and admin, with a dedicated database per restaurant.
A server-rendered Next.js storefront, themed per brand and configured per deployment.
Square and Clover, each restaurant connecting its own merchant account.
DoorDash Drive and Uber Direct for courier delivery where offered.
Stripe for card payments, under each restaurant's own account.
Resend for transactional email, Sentry for errors, per deployment.
If you run a restaurant, or build for one, and want a storefront the business actually owns, get in touch and we will walk through the platform together.
[email protected]