> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/configure-pos-and-store-manager/merchandising/setting-up-reason-codes.md). # Reason codes Reason codes identify specific actions performed at the register, e.g., no sales, discounts, or returns. Reason codes are not required, but they are recommended. 1. Click **Setup**. 2. Expand **Merchandising**. 3. Click **Reason Codes**. 4. Do one of the following: * To add a new reason code, click **New**. * To edit an existing reason code, select it and click **Edit**. * To copy an existing reason code, select it and click **Copy**. You must enter a new **Description** and **Code**, but all other values are copied. 5. Enter information about the reason code.
FieldDescription
CodeA unique code, e.g., a number or abbreviation, that identifies the reason code.
DescriptionA description of the reason code.
TypeThe type of reason code, e.g., No Sale.
Start DateIf desired, select a start date for the reason code. Leave the field blank if you want the reason code to be active immediately.
End DateIf desired, select an end date for the reason code. Leave the field blank if you do not want to set an end date.
6. Click **Save And Close**. --- # 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.rmhpos.com/store-manager/configure-pos-and-store-manager/merchandising/setting-up-reason-codes.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.