> 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-8.md).
# 3.51.8
Release Date: August 30, 2024
## Store Manager
### Import/export buttons available for received purchase orders and transfers in/out
Starting with release 3.51.8, **Import** and **Export** buttons are available for received purchase orders and transfers in/out.
The import file must contain the **Code**, **Qty Rcv**, and **Cost** columns. Items in the import file will only be imported if they match the items in the purchase order or transfer in/out. For example, if the import file contains three items (e.g., soccer ball, basketball, and football) but the purchase order or transfer in/out only contains one of those items (e.g., basketball), only the one matching item (basketball) will be imported.
{% hint style="info" %}
At this time, you can only use a decimal point (e.g.. 1.0) as a decimal separator for dollar amounts in the Cost column in the import file. You cannot use a decimal comma (e.g., 1,0) as a decimal separator.
{% endhint %}
If items are not imported, a log is generated that identifies the items and the reason. The log is saved under **C:\ProgramData\RetailHero\RMH Store Manager\Import PO**.
## Central Manager
### Improved performance for Worksheet 501
Starting with release 3.51.8, you can improve performance of **Worksheet 501: Request Full Inventory** by making minor changes to the **RMHCWorksheet.config** file. The config file is usually located under **C:\ProgramData\RetailHero\RMH Central Flash Server\Extensions**.
The default **WS501PageSize** parameter is 100. You can now change the WS501PageSize parameter to any number between 10 (minimum) and 1000 (maximum). Use a smaller page size to process a larger number of packages.
---
# 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-8.md?ask=&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.
