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

# Import Sales Lines

Import sales lines into sales documents for faster order entry.

Within Bevica, it is possible to import sales lines into a sales order using a simple csv template.

### Import Sales Lines Template

Create a csv file with the following columns. Do not create a header row.

| Field No. | Field Name      | Note                                          |
| --------- | --------------- | --------------------------------------------- |
| 1         | Item No.        | The item must exist in Bevica.                |
| 2         | Unit of Measure | The unit of measure must exist for that item. |
| 3         | Quantity        |                                               |

### Importing Sales Lines

Once you have created the file you can import this into a sales order:

{% stepper %}
{% step %}

### Step 1

Create a sales order and populate the header details such as customer, ship-to etc.
{% endstep %}

{% step %}

### Step 2

On the sales order select Actions, Functions, Import Sales Lines.
{% endstep %}

{% step %}

### Step 3

Select the file you have created to import it.
{% endstep %}
{% endstepper %}


---

# 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/import_sales_lines.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.