The restaurant network is made of restaurant nodes. A node may be a member restaurant hosted on this site or a restaurant’s own WordPress website. Both use the same plugin and the same mobile app, and in both the data belongs to the restaurant.
Two ways to join
| Open on this site | Use your own website | |
|---|---|---|
| Suits | Restaurants with no website that want to start at once | Restaurants with a WordPress site, or that want full control |
| How to start | Become a restaurant member, sign in to this site with the mobile app and create a restaurant | Install the connector once on your site; the mobile app does the rest |
| Menu address | This site’s address plus the restaurant’s code | The restaurant’s own domain |
| Where the data lives | On this site, separated by member: only you can manage your restaurants | On the restaurant’s own server |
| In the directory | Listed automatically in the restaurant directory | Listed after registering with the dish library |
What a restaurant node does
- a multilingual e-menu: guests scan and read with no sign-in, in their browser’s language;
- several menus and sections (lunch, dinner …), with serving hours per section;
- tables and QR codes: one code per table, so a scan identifies the table;
- optional add-ons: online ordering, loyalty and vouchers, stock, reports, purchase matching;
- importing dishes from the library and contributing your own back;
- publishing supply needs (off by default) for supply sites to read.
Details of the e-menu and the app are under E-menu and app; step-by-step instructions are in Getting started.
Guests’ data
Guests need no sign-in to read a menu and leave no personal information. The menu page records a small set of events anonymously (language switch, dish view, dwell, search and the like) to improve the menu; no names, phone numbers or device identifiers.