> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/work-with-customers/customers-purchase-history.md).
# Look up a customer's purchase history
{% hint style="info" %}
You must have the **Allowed to view and edit all customers** permission to look up a customer's purchase history.
{% endhint %}
1. Look up the customer. Refer to [**Look up customers**](/readme-1/work-with-customers/customers-looking-up.md) for more information.
2. Tap **Customers** | **Display History**.
3. On the **Purchases** tab, review the customer's purchases.
Items that have been purchased by the customer are listed on separate lines. Items that were purchased together in one transaction share the same transaction number (shown in the # column).
A summary of the customer's purchase history displays at the top of the screen. It shows the date of the customer's last purchase, the total number of visits (where they made a purchase), the total of all purchases made at the store, any savings from sales or discounts, and any vouchers they have redeemed.
{% hint style="success" %}
Click on the heading of any column to sort the purchases by the column. For example, it might be helpful to sort purchases by **Date**, by transaction number (**#**), or by **Description**.
{% endhint %}
4. (Optional) Tap the transaction number to view the purchase receipt in the journal.
{% hint style="info" %}
You must have the **Allowed to review printed Journals** permission to view journal entries.
{% endhint %}
5. Tap **Cancel** to exit the Customer screen.
---
# 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://docs.rmhpos.com/readme-1/work-with-customers/customers-purchase-history.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.