How Restro fits together

Five concepts explain almost everything in Restro. Learn these and the rest of the product reads naturally.

#Restaurant

Your account. It owns your brand, your menu, your customers, and your team. Every restaurant has a subdomain — yourname in yourname.tryrestro.com — which shows up in dashboard URLs and in the API.

#Branch

A physical location. A restaurant has one branch or many. Branches carry their own:

• Address, timezone, and currency
• Opening hours and busy/closed status
• Prices — the same menu item can cost differently in different branches
• Stock levels
• Delivery zones
• Staff assignments

Because so much hangs off the branch, most screens in the dashboard have a branch selector. If you only have one branch you can safely ignore it.

#Menu

Categories hold items, items carry prices and customizations, and recipes tie items to the ingredients they consume. See Menu & inventory.

#Channel

Where an order came from. Restro ships three sales channels — Website, Mobile App, and Point of Sale — and you enable the ones you use in Settings → Channels. Reporting splits by channel, so you can see whether your own site is out-earning the counter.

#Order

The unit everything else revolves around. An order belongs to a restaurant, usually to a branch, sometimes to a customer, and always has a type and a status.

Types: pickup, delivery, dine_in.

Statuses: pending → confirmed → preparing → ready → delivering → completed, with cancelled reachable from most of them.

Payment statuses are tracked separately: unpaid, pending, paid, failed, refunded. An order can be completed and unpaid — that is a table that walked out — and Restro will not hide it from you.

#How the pieces move

A customer orders on your website. The order lands as pending. If they paid online, the payment provider confirms it and Restro flips it to confirmed and deducts the ingredients from stock. The kitchen display picks it up, moves it through preparing and ready, and a driver or a counter hand-off completes it. If you have webhooks configured, each of those transitions is pushed to your own systems in real time.