> 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/products/reason.md).
# Reason
### **Overview**
The Reason section is used to create and manage reasons that can be selected during the ordering process. These reasons can be used when items are marked as Gift or Comp. You can add new reasons, edit existing reasons, delete reasons, and change the order in which reasons are displayed.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------ | ------------------------------------------------- |
| Reason List | Displays the reasons configured in the system. |
| Search | Used to search for a specific reason. |
| Add Reason | Used to add a new reason. |
| Edit Reason | Used to modify the details of an existing reason. |
| Delete Reason | Used to remove a selected reason. |
| Change Sort Order | Used to change the display order of the reasons. |
| Close | Closes the Reason section. |
### **Working**
#### **Add Reason**
1. Select "Add Reason".
2. Enter the required Reason.
3. Enter the Alias Name, if required.
4. Enter the Sub Group, if required.
5. Select the required Group Code.
6. Select "Save" to add the reason.
#### **Edit Reason**
1. Select the required reason from the Reason List.
2. Select "Edit Reason".
3. Update the required reason details.
4. Select "Save" to save the changes.
#### **Delete Reason**
1. Select the reason you want to remove.
2. Select "Delete Reason".
3. In the confirmation message, select "Yes" to delete the reason.
#### **Change Sort Order**
1. Select "Change Sort Order".
2. Adjust the order of the reasons as required.
3. Save the updated order.
### **Use Case**
* Record the reason when an item is provided to a customer free of charge.
* Provide products as complimentary items or goodwill gestures for customers.
* Document the reason for offering an item free of charge as part of customer service recovery.
* Manage products given at no charge as part of promotional offers or special campaigns.
* Maintain a clear reason when products are provided as Gift or Comp with management approval.
* Track why specific items were provided without charging the customer.
* Provide staff with predefined reasons to select during the ordering process instead of entering explanations manually.
* Organize multiple Gift or Comp reasons so staff can quickly identify and select the appropriate option during order processing.
### **Notes**
* Enter the Reason before selecting "Save".
* Alias Name, Sub Group, and Group Code can be configured when adding a reason, based on the required setup.
* Select the required reason before using "Edit Reason" or "Delete Reason".
* Verify the reason details before selecting "Save".
* Deleting a reason requires confirmation.
* Use "Change Sort Order" to organize the reason list according to your requirement.
* Create appropriate reasons so users can select the correct reason during the ordering process.
---
# 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/products/reason.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.
.png?alt=media)
