> 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/reporting-and-analytics/reporting_in_bevica_-_overview/customeritem_sales_analysis.md).

# Customer/Item Sales Analysis

Analyse sales by customer and item, with drill-down to transactions.

Customer/Item Sales Analysis is an onscreen report displaying quantities and values for each item a customer has ordered. The screen can be used internally when analysing a customer or item's performance or by Salespeople when visiting customers to show them a summary of their purchasing activity. For every combination of item and customer, additional information displays, such as total quantities and amounts bought and credited.

Two versions exist:

* **Customer/Item Sales Analysis**: All the figures on this version are updated in real time, the figures coming from Bevica document pages, i.e., Sales Order, Sales Return Order, Posted Sales Invoices, Posted Sales Credit Memos, etc.
* **Customer/Item Sales Analysis - Item History**: If you have access to the **Item Sales History** add-on, this version includes any Item Sales History you might have imported. See [Item History (Sales)](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/item_history_-sales.md) for more details.

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

Items and customers have been set up.

Sales transactions have been created.
{% endhint %}

### Processing the report

Both Customer Item Sales Analysis reports can be found in three different ways:

* You can search for **Customer Item Sales Analysis** page using the ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2FRbFlcaA0l3VHxAggeMz_jP9c4JTlWNS4eg.png?alt=media) button
* You can open the page by accessing it from the **Customer List/Customer Card**
* You can open the page by accessing it from the **Item List/Item Card**

Accessing the report from the Customer List/Card will show you every item that a customer has bought.

If you access the report from the Item List/Card, it will show you every customer that has bought the selected item.

Whenever an item is added to a sales transaction, a record is created in the Customer/Item Sales Analysis page ready to start recording sales-related information; quantities and amounts outstanding, invoiced, and credited values are all recorded. You can drill down on each field to see more details.

{% hint style="success" %}
You can also use the Filter Panes' ‘**Filter totals by**’ to apply additional filters to the values, i.e., Date, Location Code, Variant Code.
{% endhint %}

{% hint style="info" %}
Note

**Qty. Shipped**, **Qty. Invoiced**, and **Amt. Invoiced (LCY)** are filtered to exclude paid reserve withdrawals and paid reserve duty transfers.
{% endhint %}

### Updating Item / Sales Analysis records

The normal process of processing sales orders should maintain Customer/Item Analysis records. If for any reason items are missing data, you can run a routine to update them from history.

Navigate to Bevica Setup, Actions, **Admin Centre** and **Populate Customer/Item Analysis**. Run this routine.

The routine interrogates all sales lines and posted sales invoice lines, so it can take a long time to run if no filters are used. Consider applying filters before running the routine.


---

# 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/reporting-and-analytics/reporting_in_bevica_-_overview/customeritem_sales_analysis.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.