> 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.md).
# Sales
Sales workflows in Bevica, including orders, returns, reservations, pricing controls, and notes.
The Sales Order function in Bevica comprises a number of transactions that, in combination, provide the ability to service your customers effectively.
### Document Types:
#### Sales Order
Sales orders are used to allocate stock and charge for services to a customer for delivery and invoicing. They contain all the information needed to manage the shipping of the goods to the correct address at the right time and invoice the customer appropriately. See [Working with Sales Orders](/documentation/guides/sales/working_with_sales_orders-1.md).
#### Sales Return Order
When the customer wants to return stock for credit, you create a return order. Items to be returned can be applied to the customer's original sale to properly allocate costs and also make sure they are not trying to return more stock than was purchased from you. See [Working with Sales Return Orders](/documentation/guides/sales/working_with_sales_orders-2.md).
#### Sales Quote
A sales quote can be created against a customer or prospect to display pricing and send a proposal document. They are also part of the CRM-related Opportunity Management process. Quantities on quotes do not impact item availability.
#### Sales Credit Memo
When the customer wants a financial credit without inventory movement.
#### Sales Invoice
When you want to invoice the customer for a service. It is best practice not to use Invoices for items.
#### Sales Blanket Order
Blanket orders are used when a customer has committed to purchasing large quantities or you want to track more closely an allocated quantity. Sales orders are created from blanket orders. Quantities on blanket orders do not impact item availability. A typical use of a blanket order might be where a corporate customer at Christmas wants to buy a large quantity of stock to be delivered to multiple recipients.
See also [Managing Blanket Orders](/documentation/guides/purchasing/managing_blanket_orders.md).
For more information from Microsoft on the blanket orders click [Work with Blanket Sales Orders](https://docs.microsoft.com/en-gb/dynamics365/business-central/sales-how-to-create-blanket-sales-orders).
#### Sales Archives
**Sales Archives** exist that can be used to take a snapshot of any sales document. They can be created manually or automatically if the option is set in **Sales & Receivable Setup**. For more information from Microsoft on archiving documents click [Archive Documents](https://docs.microsoft.com/en-gb/dynamics365/business-central/across-how-to-archive-documents).
For more information from Microsoft on Sales functions, click [Sales](https://docs.microsoft.com/en-gb/dynamics365/business-central/sales-manage-sales) or [Managing Receivables](https://docs.microsoft.com/en-gb/dynamics365/business-central/receivables-manage-receivables).
---
# 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.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.
