> For the complete documentation index, see [llms.txt](https://docs.madhype.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.madhype.io/online-ordering-system/for-chains/create-a-multi-location-restaurant-chain-dashboard.md). # Create a Multi-location Restaurant (Chain) Dashboard {% embed url="" %} ### Step-by-step instructions For multi-location restaurants, click on the extra options arrow next to the restaurant name in the restaurant admin panel to enable the multi-location dashboard: ![multi-location restaurants](https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8583%2Fdirect%2F1619699641801-1619699641801.png) Under the hood, a “parent” account representing the brand is created which groups all the locations together. Interface wise, the parent account is this dashboard: ![how to manage multiple restaurants under one dashboard](https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8583%2Fdirect%2F1621228254705-Chains+-+dashboard.png) The idea is simple: location specifics (like address, opening hours, delivery service etc) are managed by accessing each location, in the restaurant interface known today. Common settings (like menu and promotions) are handled at the chain level, from this parent account. This is how the account holder can set up: * [delivery zones](https://orderingsystem.helpjuice.com/dienstleistungen-und-offnungszeiten/edit-delivery-zones); * [opening hours](https://orderingsystem.helpjuice.com/services-and-opening-hours/how-to-set-up-restaurant-opening-hours); * [pickup](https://orderingsystem.helpjuice.com/services-and-opening-hours/how-to-enable-food-pickup-service) and [table reservation](https://orderingsystem.helpjuice.com/services-and-opening-hours/how-to-take-table-reservations) services. ### **Menu management** Here is how the menu sharing among locations works. In the dashboard, there is a section called Menus. Here, the account holder can edit the “master” menu and assign it to all the locations. This way, when the account holder makes – let’s say – a price change, they make it once and have it automatically propagated to all restaurant locations. ![multi restaurant ordering system](https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8583%2Fdirect%2F1619699875154-1619699875154.png) In case not all locations can function with one menu, the account holder can simply create multiple versions by duplicating an existing one or starting from scratch. Create as many menus as needed and assign the locations to the menus by dragging them to the right menu. ### **Promotions** Since the menus for multi-location restaurants are being managed at the chain level, so are the promotions. Note the dedicated Marketing tab in the chain dashboard: ![multi restaurant online ordering system](https://s3.amazonaws.com/helpjuice-static/helpjuice_production%2Fuploads%2Fupload%2Fimage%2F8583%2Fdirect%2F1619699641092-1619699641092.png) \ For each online menu, it is possible to create one or several promotions. To run multiple promotions at the same time, the Advanced promo module (paid service) needs to be enabled. The restaurant has full flexibility in establishing which location uses which promotions, meaning that they can have: * unified menu and promotions across all locations **or** * different promotions for each location **or** * anything in between. ### **Branded mobile app** The branded mobile app has been improved to work “in chain-mode” as well. All the locations get listed under the same app, allowing the food client to choose the location to order from. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.madhype.io/online-ordering-system/for-chains/create-a-multi-location-restaurant-chain-dashboard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.