> 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/releases/old/3-51-6.md).

# 3.51.6

Release Date: August 9, 2024

## POS

### Two new filters available for looking up customers in POS

Starting with release 3.51.6, when you are looking up customers in POS, two new filters are available: **AR Accounts Only** and **Customer Alias**. To access these filters, tap **Customers** | **Lookup Customer** and tap **Find Customer**.

To look up customers with AR accounts, you must select the AR account filter and at least one other filter (such as Account Number, Last Name, First Name), then enter the search criteria. The search results are limited to customer records that match the search criteria and are connected to AR accounts.

<div align="left"><figure><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2F4WTnXYeFJicNHMJrkyfP%2F3-51-6-ar-accounts-only.png?alt=media&amp;token=e33807b6-cdaf-41f6-8d4a-9aab28b8c85e" alt=""><figcaption></figcaption></figure></div>

To look up customers by alias, you must select the customer alias filter and enter the search criteria. The search results are limited to customer records with aliases that match the search criteria.

<div align="left"><figure><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2FPZCIIBmKNCvNvScfocgy%2F3-51-6-customer-alias.png?alt=media&amp;token=4da877b6-a0b7-4d78-a786-954190d3a80e" alt=""><figcaption></figcaption></figure></div>

## Store Manager

### Export button available for completed purchase orders or transfers in/out

Starting with release 3.51.6, a new **Export** button is available when you complete purchase orders or transfers in/out. In previous releases, the Export button was only available when you created purchase orders and transfers in/out.

<div align="left"><figure><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2FokhLNDxiOW6PcuV8N29l%2F3-51-6-export-button.jpg?alt=media&amp;token=79b1e9f6-5191-4853-83d2-871a2e0e5c0d" alt=""><figcaption></figcaption></figure></div>


---

# 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://docs.rmhpos.com/releases/old/3-51-6.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.
