> 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/es/releases/old/3-9-11.md).

# 3.9.11

Fecha de lanzamiento: 16 de agosto de 2021

## **Store Manager y POS**

### Evitar cambios en la unidad de medida en el POS

A partir de la versión 3.9.11, las tiendas pueden evitar que se cambie la unidad de medida en la caja registradora seleccionando la **No permitir editar la unidad de medida en la pestaña de inventario** opción en la **Propiedades extendidas** pestaña:

<div align="left"><figure><img src="https://1556792658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2FdIRM2JZpfVUkuG2H2fcv%2FRMH-store-item-inventory-ext-prop-uom.png?alt=media&amp;token=7b5c27ce-e189-4f59-a011-a09a09fa0792" alt=""><figcaption></figcaption></figure></div>

### Mostrar información de WAM en la pantalla de inicio de sesión del POS

A partir de la versión 3.9.11, solo para clientes del Reino Unido, la pantalla de inicio de sesión del POS ahora mostrará el número de certificación WAM del cliente, el nombre del archivo DLL (RetailHero.POS.WAM.UK.DLL) utilizado para gestionar la funcionalidad de WAM para clientes del Reino Unido y la suma de comprobación utilizada para detectar errores en la transmisión o el almacenamiento de datos en Store Manager y POS.


---

# 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/es/releases/old/3-9-11.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.