> For the complete documentation index, see [llms.txt](https://help.inventora.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.inventora.com/getting-started/sales/importing-sales-from-csv.md).

# Importing Sales from CSV

## How to Format Your CSV

### Line Items

* Each line in your CSV will be one line item
* **This means orders can span multiple lines**, with each line representing one line item in the order
* If an order has multiple line items, you will want to repeat the information other than the product name / SKU, quantity, and unit price
* We will use the first line with a particular Order Number to fill all the non-line-item related fields, but it is safest to just add the customer, shipping, etc. information to all the lines of that order

### Column Names

* These are the columns we support (<mark style="color:red;">**\***</mark> means required):
  * Sale Number<mark style="color:red;">**\***</mark>
  * Customer First Name
  * Customer Last Name
  * Company Name
  * Customer Email
  * Shipping Address Line 1
  * Shipping Address Line 2
  * Shipping City
  * Shipping State
  * Shipping Zip Code
  * Shipping Country
  * Product Name<mark style="color:red;">**\***</mark> - See [Line Items](#line-items)
    * Either Product Name or product SKU must be present, but you don't need both
  * Product SKU<mark style="color:red;">**\***</mark> - See [Line Items](#line-items)
    * If Product Name and Product SKU are both present, we'll try the SKU first
  * Product Quantity<mark style="color:red;">**\***</mark> - See [Line Items](#line-items)
  * Product Unit Price<mark style="color:red;">**\***</mark> - See [Line Items](#line-items)
  * Shipping (charged to customer)
  * Tax
  * Discounts
* **Note:** Column names do not have to exactly match the column names in Inventora. You will be able to match up the columns in your CSV with the Inventora columns when you import.


---

# 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://help.inventora.com/getting-started/sales/importing-sales-from-csv.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.