> 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-11-12.md).

# 3.11.12

Release Date: December 26, 2022

## **Loyalty Manager, Central Manager, Store Manager**

### New log in screen and new user role permissions

Starting with release 3.11.12, you must access Loyalty Manager through a log in screen. To log in, you must be either a central user or manager user who has the new permission **Allowed to access the Loyalty program** assigned to their role.

In Central Manager, you can assign this permission to central user roles under **Setup** | **People and Security** | **Central User Roles**. In Store Manager, you can assign this permission to manager user roles under **Setup** | **People & Security** | **Manager User Roles**. Click **New** or double-click an existing role, expand **Privileges** | **Loyalty Privileges**.

### Redeem loyalty reward coupons at any centrally-managed store

Starting with release 3.11.12, customers will be able to redeem loyalty reward coupons at any store managed by Central Manager. In previous releases, customers could only redeem loyalty reward coupons in the same store that issued the coupon.

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

Refer to [**Configure custom EAN-13 barcode formats**](https://docs.rmhpos.com/store-manager/manage-items/weighed-items/setting-up-ean-13-barcodes.md) for more information on setting up custom EAN-13 formats for countries where the prices of random weight items exceed $999.99.

## **POS Software Development Kit (SDK)**

### Enter discount reason code in chain of commands

Starting with release 3.11.12, when you are programming a chain of commands for **POS Task Pads** or **Custom Buttons**, if you enter a `{Reason Code}` parameter for an applicable **DiscountTransaction** command, the reason code is applied automatically to the transaction. If you do not enter a `{Reason Code}` parameter, the **Select Reason Code** screen displays and the cashier is prompted to select a reason code.


---

# 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-11-12.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.
