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

# 3.9.9

Release Date: July 16, 2021

## Store Manager and POS

### Print labels for blocked sales items in Label Wizard

Starting with release 3.9.9, you can print labels for blocked sales items. To do this select **Print labels for items that satisfy the following filter** in the Label Wizard and filter on any of the following fields: Block Sales, Block Sales Reason, Block Sales After Date, and Block Sales Before Date.

### Redeem vouchers at the register

Starting with release 3.9.9, if a customer presents an expired voucher at the register, a message displays on the screen to indicate the voucher is expired and the cashier has the option to continue and redeem the balance of the expired voucher or to not accept the expired voucher.

## Central Manager

### Use file export and import to update Worksheet 351

Staring with release 3.9.9, if you need to update item using **Worksheet 351: Update Inventory - Item Prices Cost (Regular)** in Central Manager, you can export the items to an Excel spreadsheet, make the changes in Excel, and then import the spreadsheet back into Central Manager.


---

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