> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/item/item-return-code/creating-item-return-codes.md).
# Creating Item Return Codes
Item return codes are unique identifiers that identify and categorize the reason behind item returns. They provide a concise and standardized way to document why a customer is returning an item. Creating item return codes involves entering the name and the item return code. Once an item return code is created, you can select the code when processing item returns.
{% hint style="info" %}
To create an item return code, go to **Menu > Admin > Item > Item Return Code**
{% endhint %}
To create an item return code, you'll start by identifying the most common reasons for item returns within your business. This may involve the reason provided by the customer on a recent return, analyzing past return data, conducting customer surveys, or collaborating with your sales and customer service teams.
### Item Return Codes Fields
* **Name:** This field allows you to enter a clear and descriptive name for the return reason.
* **Item Return Code (R Code):** This field allows you to assign a short, unique code that represents the return reason. This code is typically an abbreviation or acronym derived from the name.
After entering the name and the code for the return reason, click "Save" to create the item return code.
### Item Return Code Examples
* **Customer Satisfaction (CS)** - Covers returns due to customer dissatisfaction with the product or service.
* **Damaged Goods (DG)** - Denotes returns caused by faulty or damaged products.
* **Wrong Item Ordered (WIO)** - Indicates that item is returned because the customer ordered wrong item.
---
# 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://docs.xorosoft.com/xoroerp-1/admin/item/item-return-code/creating-item-return-codes.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.
