> 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-9-19.md).

# 3.9.19

Release Date: December 20, 2021

## Store Manager

### New Ship option and Shipped status for purchase orders

Starting with release 3.9.19, there is a new **Ship** option for purchase orders. This option becomes available after a purchase order moves to **Released** status. After you ship a purchase order, it moves to the new **Shipped** status. Using **Ship** is an optional business workflow. You can continue to move purchase orders directly from **Released** to **Received** status.

### New Import and Export options for purchase orders and transfers

Starting with release 3.9.19, you can import or export item information in the **Items** tab for purchase orders, transfers in, and transfers out.

### Reconcile item movement as part of calculation of physical inventory count

Starting with release 3.9.19, any item movement (such as sales, returns or exchanges, transfers in, or transfers out) that occurs after a physical inventory count starts will be automatically reconciled when the count is calculated.

{% hint style="info" %}
The reconciliation of item movement with the physical inventory count is performed automatically in the database after the customer clicks **Calculate**. No further action or inputs are required by the customer.
{% endhint %}

## Store Manager and Central Manager

### New setting to prevent changes to shipped purchase orders

Starting with release 3.9.19, there is a new option **Do not allow to make changes to purchase order when shipped** to prevent changes to purchase orders that have shipped. This option is available under **Setup** | **Inventory/Purchasing** | **Order Setting** on the **Global Option** tab.

{% hint style="info" %}
For stores managed by Central Manager, this order setting option must be defined in Central Manager and synchronized to the applicable stores.
{% endhint %}


---

# 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-9-19.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.
