> 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/open_sales_lines_and_open_purchase_lines.md).

# Open Sales Lines

Review all open sales lines across customers and documents for follow-up and planning.

The '**Open Sales Lines'** pages help you see, sort, and filter your open sales activity across all document and line types.

{% hint style="warning" %}
**Prerequisites**

Open sales documents exist.
{% endhint %}

### Viewing Open Sales Lines

1. Search for **Open Sales Lines** and select the appropriate link.
2. The non-editable list displays sales lines across all document types (**Quote, Order, Invoice, Credit Memo, Blanket Order, Return Order**) and Line Types (**Comment, G/L Account, Item, Resource, Fixed Asset, Charge (Item)**).

The list is intended as a place to view, in more detail, all open sales line activity. It can be used, for example, to check which lines are above or below a certain **Margin %** (see also [Margin Check on Sales Lines](https://kb.bevica.com/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/checking_sales_line_margins.md)).

Lines are removed from the list when the line is deleted or its document deleted on invoicing.

### Customer Card

The following filtered lists are available from the card ribbon; Navigate, **Documents** option.

* Open Sales Lines
* Open Reservation Sales Lines


---

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