> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/sales/sales_line_reason_codes.md).

# Sales Line Reason Codes

Use sales line reason codes for analysis, controls, and reporting.

Sales Line Reason Codes can be added to sales document lines to provide more granular reporting on why a particular line has been created. For example, an alternative item is delivered, to confirm a zero price, an item is sold as part of a bigger campaign/promotion, mis-pick corrections.

See also [Checking zero priced sales lines](/documentation/guides/sales/check_zero_priced_sales_lines.md).

![Sales line showing the Sales Line Reason Code field](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-8cf5839f87296fb985359e060b590efd9b72c366%2FI_MVGqa2mIaTFfSm3rzH4IlAaoXg-BlyBw.png?alt=media)

### Sales Documents

Sales Line Reason Code field can be edited on these pages' subform, it may be hidden by default.

**Documents**

* Sale Order
* Sales Invoice
* Sales Return Order
* Sales Credit Memo
* Sales Quote
* Sales Blanket Order

The Sales Line Reason Code field is available on the following pages for information/reporting:

**Documents**

* Open Sales Lines
* Posted Sales Shipment subform
* Posted Sales Invoice subform
* Posted Sales Credit Memo subform
* Posted Return Receipt subform
* Posted Sales Shipment Lines
* Posted Sales Invoice Lines
* Posted Sales Credit Memo Lines

**Entries**

* Item Ledger Entries

{% hint style="info" %}
Note

Use the Item Ledger Entry page in **Analysis mode** to report on the number of sales/returns in a month by Sales Line Reason Code.
{% endhint %}

### Managing Sales Line Reason Codes

To create and manage Sales Line Reason Codes navigate to Bevica Setup, Related, Operations, **Sales Line Reasons Codes**. Codes can be **Blocked** to hide them from sales line selection.


---

# 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://kb.bevica.com/documentation/guides/sales/sales_line_reason_codes.md?ask=<question>&goal=<endgoal>
```

`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.