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

# 3.9.18

Release Date: December 6, 2021

## **Central Manager, Store Manager, and POS**

### New character limits for serial and voucher numbers

Starting with release 3.9.18, you can enter up to 50 characters for serial numbers and voucher numbers. In previous releases of Retail Management Hero you were limited to 20 characters for serial numbers and voucher numbers.

The database schemas of Central Manager and Store Manager have been updated and they now support 50 characters for serial numbers and voucher numbers. This change is automatically available to customers who install, migrate to, or upgrade to the 3.9.18 version of Retail Management Hero.

The following tables and columns in the Central Manager database were updated:

* Serial.SerialNumber
* Serial.SerialNumber2
* Serial.SerialNumber3
* Voucher.Number
* VoucherOnline.VoucherNumber

The following tables and columns in the Store Manager database were updated:

* Serial.SerialNumber
* Serial.SerialNumber2
* Serial.SerialNumber3
* Voucher.Number

{% hint style="info" %}
If you have an offline database configured for POS, you must run either the Z report or ZZ report to upgrade the offline database.
{% 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 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/releases/old/3-9-18.md?ask=<question>&goal=<endgoal>
```

`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.