> 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_document_type_codes.md).
# Sales Document Type Codes
Set up sales document type codes for consistent processing and reporting.
Available on all open sales documents and copied to posted documents, use this field to categorise your sales for filtering and operational reporting, i.e. sample, FOC, special event, sale, or return. The field can also be used to manage functionality, see **Sales Identifier**, and set defaults, see **Default...** fields below.
{% hint style="warning" %}
**Prerequisites**
Set up sales order processing.
{% endhint %}
### Sales Document Type codes
To create Sales Document Type Codes:
* You can search for **Sales Document Type Codes** page using the  button
* From Bevica Setup, navigate to More Actions, Related, Operations
| Field | Note |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Code | Set a unique code for each type you want. |
| Description | Enter a description for the record. |
| Sales Identifier | • Blank: for information only
• Sample: See Samples/Free of Charge Stock
• Duty Transfer: for information only, see Paid Reserve - Transfer Duty Status
• Cellarage: See Paid Reserves Cellarage Invoicing
• Excellar: See Bevica Excellar Order Processing
• Commission: See Bevica Commission Sales
|
| Default Location Code | If this is set, when the document type is added to an order, it will change the Location code on the document. |
| Default Customer Price Group | If this is set, when the document type is added to a document, it will change the Customer Price Group Code. |
| Default Customer Disc. Group | If this is set, when the document type is added to a document, it will change the Customer Disc. Group Code. |
| Default Shipment Method Code | If this is set, when the document type is added to a document, it will change the Shipment Method Code. |
| Allow Zero Item Price | Set this to override any zero sales line price checking. See Checking Zero priced sales lines |
{% hint style="info" %}
**Note**
Select **Sales Document Type** code after entering the 'Customer No.' and 'Ship-to Code'. If not, the **Sales Identifier** defaults may be overwritten.
{% endhint %}
### Sales Documents
The **Sales Document Type** field is editable on all open sales document headers and visible on posted documents. When it's added to an open document, it is then copied to all lines on that document.
The Sales Document Type Code carries a level of validation linked with the Sales Identifier. If the Sales Doc Type is not linked to a Sales Identifier this can be added/removed without any validation. If there is a link to a Sales Identifier (EG, Excellar) Bevica will carry out a check on lines and/or linked documents before allowing remove/delete.
{% hint style="info" %}
**Note**
You can only apply one **Sales Document Type** per document, meaning all lines on that document share the same code.
{% endhint %}
See also [Purchase Document Type Codes](/documentation/guides/purchasing/purchase_document_type_codes.md)
---
# 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_document_type_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.