●  Restaurant ordering & operations platform · full source code for sale

The command centre
for a restaurant's whole service.

Online ordering, phone and counter intake, kitchen stations, printing with recovery, rider dispatch and live capacity control: one system, designed by a restaurant owner who ran a 17-person delivery kitchen in Rome.

Open the live demo → Request the data room

Demo staff access: open the demo and use the one-click portals, or go to /login and tap KITCHEN DEMO, RIDER DEMO or ADMIN DEMO. No password. Demo data only.

demo.centrocommand.com/intake
Centro Command order intake screen: phone, counter and web orders with menu grid and cart
Customer menu on a phone
~190,000lines of TypeScript
10-job CIon every change: unit, browser, DB replay, security
PostgreSQL 17row-level security on Supabase
Next.js 16React 19 · Node.js 24
Two doors, one system

Customers order on the restaurant's own channel. Staff run service from one screen.

Direct ordering means no marketplace commission on every order and the customer relationship stays with the restaurant. Behind it, every station sees the same live state.

Customer storefront of the demo pizzeria
Customer side

Web ordering for delivery and takeaway

Complex menus with variants, modifiers, combo steps, half-and-half and bulk rules. Allergen gate, alcohol age check, delivery zones and live order status.

Staff station picker: control room, intake, kitchen, oven, fryer, rider
Staff side

One login, every station

Control room, intake, kitchen, oven, fryer and rider dispatch, each with its own screen and role. The order state is always confirmed by the server, never guessed by a device.

Inside the command centre

Built for the 8 pm rush, not for a slide deck.

Every screen below is a real capture of the live demo, with demo data.

Intake

Phone, counter and web orders in one place

Staff take phone and walk-in orders on the same menu and pricing engine the website uses, so a phone order and a web order are the same object in the kitchen.

  • Delivery or takeaway, customer and address in one form
  • Cash, card on delivery, online card and Satispay as payment methods
  • Orders go straight to the kitchen stations
/intake
Intake screen
Kitchen display

Stations, courses and expo

Kitchen, oven and fryer each get their own display. Tickets age live and turn red when they pass the promised time, so the late order is the one everybody sees.

  • Per-station queues with clear next actions
  • Courses and expo for dine-in service
  • Kitchen capacity and dispatch timing
/cucina/forno
Oven station kitchen display with order tickets
Printing

ESC/POS printing that survives a dead printer

Every ticket has a durable print ID. If no printer picks it up, the ticket is held and flagged with a one-tap reprint, and every reprint is audited. Tested on an Epson TM-T20III.

/cucina · print recovery
Print recovery panel listing held tickets with reprint buttons

The screen flags tickets no printer has collected, with reprint.

Capacity

Open, close and promise a real ETA

The owner sees pizzas in progress, saturated slots and riders available, and can close online ordering with a reason or let the system reopen automatically.

/admin/termostato
Capacity screen with site status, ETA and manual override
Dispatch

Riders and deliveries

Ready orders, riders in the zone and deliveries on the road, with the amount each rider has to collect. Riders log in with their own role.

/rider
Rider dispatch screen
Also in the package

Dine-in and the parts buyers ask about first.

Live in the demo

Dine-in module

Floor plan, table orders and open table bills run in the live demo. Also in the source code, disabled in the public demo: bar tabs, bill transfer, split bills, guest bill by QR, reservations, cancellations and the cash drawer.

Payments

Stripe integration in test mode: the buyer connects their own live account. Cash and card on delivery are handled as payment methods.

Privacy & integrations

GDPR retention and erasure built in. A plugin lifecycle for integrations, so new providers plug in without touching the order core.

Built by an operator
Designed around the problems of a real Saturday-night service, not around a feature checklist.
Himu Sheikh, founder · Rome · LinkedIn →

About 15 years in food service: restaurants, takeaway, fast food and delivery, in almost every role from order taking and the kitchen to ownership.

As owner of a delivery and takeaway pizzeria in Rome he ran a team of 17 and designed the menu, the dough and the service workflow. The rush hours, the lost kitchen tickets, the printer that stops at the worst moment and the rider who leaves without the right order are the problems this software was designed around.

Centro Command is now offered as a complete codebase to a team that will take it to market: a software house for restaurants, an agency that needs its own ordering product, or a restaurant group that wants to own its stack.

Engineering

A codebase you can audit.

Every change runs a 10-job CI: unit and browser tests, the full database replayed from zero twice, and security scans. Row-level security on every table, database-upgrade safety checks and a plugin lifecycle for integrations.

Next.js 16React 19TypeScriptSupabasePostgreSQL 17 + RLSNode.js 24StripeESC/POSGitHub Actions
Data room, ready before you ask
ARCHITECTUREsystem design
CODEBASE_MAPwhere everything lives
INSTALLfrom zero to running
RESTOREbackup and restore
ENV_VARSconfiguration
COST_PER_VENUErunning cost
FEATURE_STATUSwhat is done, what is not
LICENSESdependency licence inventory
FAQ_TECHtechnical questions
HANDOVERtransfer checklist
The deal

Exclusive ownership of the source code, domain included.

One-time acquisition
€6,900 EUR

Full, exclusive ownership of the Centro Command source code and the domain centrocommand.com. The founder keeps only a narrow licence to use it in restaurants he owns.

Start the conversation →See the demo
Included in the transfer
  • GitHub repository transfer with full history
  • Database migrations and setup scripts
  • Data room: architecture, install, restore, licences
  • Written codebase map and walkthrough
  • 14 days of written handover support after transfer
  • Seller licence: kept for the seller’s own restaurants only — no resale, sublicensing or SaaS
  • Domain centrocommand.com
  • Payment before transfer: bank transfer (SEPA), Wise or Escrow.com
FAQ

Straight answers.

Is it running in restaurants today?

Not yet. Centro Command is sold as a complete codebase with a live demo and a data room. It was designed from the daily operation of a real delivery pizzeria, and the printing path was tested on real hardware (Epson TM-T20III).

Who is it for?

A software house or agency serving restaurants that wants its own ordering and kitchen product, or a restaurant group that wants to own its stack instead of paying per-order commissions.

What is not included?

Certified Italian fiscal (RT) integration, offline mode, multi-tenant SaaS and store-published mobile apps. These are listed openly so the price reflects exactly what is delivered.

Which languages does it support?

English and Italian. The demo opens in English, with Italian one click away, from the customer app to the staff console.

Can I review the code before buying?

Yes. After a first written exchange you get the data room, including the written codebase map. The full repository is transferred after payment.

How does payment and transfer work?

Payment first, by bank transfer (SEPA), Wise or Escrow.com; payment and escrow fees are on the buyer. Then the GitHub repository, migrations, data room, domain and written codebase map are transferred, followed by 14 days of written handover support.

See it working, then talk to the founder.

Open the live demo → founder@centrocommand.com