> 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/store-manager/manage-employees/manage-commission-sales/setting-up-commission-sales-customers.md).

# Asignar representantes de ventas a clientes

Este tema describe cómo asignar un representante de ventas específico a un cliente.

Dependiendo de las políticas de su tienda, puede tener representantes de ventas específicos asignados para gestionar todas las transacciones de determinados clientes. Este sistema es común en tiendas donde los representantes de ventas se especializan en ciertos sectores o gamas de productos, o donde los representantes de ventas se pagan principalmente mediante comisiones por ventas.

Si selecciona un representante de ventas principal para un cliente, todas las ventas a ese cliente se acreditan a ese representante de ventas.

{% hint style="info" %}
Puede configurar Store Manager para exigir la selección del representante de ventas para cada transacción en el POS. Esto se define en Store Manager en **Archivo** | **Configuración** | **Reglas de la tienda**. En **Opciones de cliente**, seleccione **Requerir selección de cliente para ventas**.
{% endhint %}

1. Haga clic en **Cliente**.
2. Haga clic en **Clientes**.
3. Haga doble clic en la cuenta del cliente.
4. Haga clic en el **Opciones de cliente** .
5. Haga clic en el icono de búsqueda junto a **Representante de ventas principal** campo, seleccione el representante de ventas principal del cliente de la lista y haga clic en **Aceptar**.
6. Haga clic en **Guardar y cerrar**.


---

# 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/store-manager/manage-employees/manage-commission-sales/setting-up-commission-sales-customers.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.
