> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-2/e-menu/menu-timing.md).
# Menu Timing
The **Menu Timing** feature in the E Menu module is used to define the availability timing of menus for specific outlets. It helps control when a particular menu should be displayed and accessed during business hours.
### Steps to Create and View Menu Timing
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master2 > E Menu > Menu Timing**.
* The Menu Timing screen will appear.
Step 2: Click on the **Open** button to proceed.
Step 3: Click on the **Outlet** field and select the required outlet from the list provided.
* Ensure the correct outlet is selected before proceeding.
Step 4: Select the required **Menu Name** from the available list.
* Enter or select the required **Start Time** and **End Time** for the menu.
* Make sure the timing entered is accurate according to the outlet’s operating schedule.
Step 5: After entering all the required details, click on the **Save** button to successfully save the Menu Timing configuration.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/point-of-sale/point-of-sale-module/masters-2/e-menu/menu-timing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
