> 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/dineplan/backoffice/settings/department.md). # Department ## **Overview** The Department section is used to create and manage different service departments based on the restaurant's requirements. Departments can represent different service types, such as Restaurant, Take Away, Walk Through, or Drive Through. Users can create, edit, delete, and sort departments as required.

### **Screen Elements**

| **Screen Element** | **Description** | | ------------------ | -------------------------------------------------- | | Department List | Displays the departments configured in the system. | | Search | Used to search for a specific department. | | Add Department | Used to create a new department. | | Edit Department | Used to modify the selected department. | | Delete Department | Used to remove the selected department. | | Sort Departments | Used to arrange the department list. | | Close | Closes the Department screen. | ### **Working** #### **Create a Department** 1. Select "Add Department" from the Department List.

2. Enter the required "Department Name".

3. Select the required "Default Ticket Type" and "Default Menu".

4. Select the required "Ticket Creation Method", "Price Tag", and "Warehouse".

5. Enter the required "Group", "Code", and "Tag" information.

6. Enable "NonRevenue" if the department should be treated as non-revenue.

7. Select "Save" to create the department.

#### **Edit a** **Department** 1. Select the required department from the Department List.

2. Select "Edit Department".

3. Update the required information. 4. Select "Save" to apply the changes.

#### **Delete a Department** 1. Select the department to be deleted from the Department List.

2. Select "Delete Department".

3. A confirmation message appears asking whether to delete the selected department. 4. Select "Yes" to confirm the deletion or "No" to cancel.

#### **Sort Departments** 1. Select "Sort Departments".

2. The "Sort Departments" pop-up appears with the configured departments.

3. Drag and drop the departments to arrange them in the required order. 4. Select "OK" to save the new order or "Cancel" to discard the changes.

### **Use Case** * Departments can be created according to the restaurant's service requirements, for example: * Restaurant * Take Away * Walk Through * Drive Through * Configure separate service types such as Restaurant, Take Away, Walk Through, or Drive Through within the POS. * Manage different ordering channels separately when each service type has its own operational requirements. * Assign a default menu to a department so the appropriate menu is available for that service type. * Configure different ticket creation methods based on how orders are received and processed. * Apply different price tags when product pricing varies between service types or departments. * Associate a department with the appropriate warehouse when stock or product availability needs to be managed separately. * Configure non-revenue departments for service areas or transactions that should not be treated as revenue-generating. * Maintain and organize multiple departments so staff can select the appropriate service type while processing orders. ### **Notes** * Configure departments based on the restaurant's operational requirements. * Ensure the correct department name and settings are entered when creating a department. * Review the selected department before editing or deleting it. * Deleting a department should be performed only when it is no longer required. --- # 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/dineplan/backoffice/settings/department.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.