> 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/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-charges.md).

# Cargos

Este tema describe cómo configurar cargos.

Los cargos son tarifas que su tienda paga por cosas como los gastos de entrega de proveedores o las transferencias entre tiendas. Estos cargos solo son aplicables a pedidos de compra y transferencias.

1. Haga clic en **Configuración**.
2. Expandir **Inventario/Compras**.
3. Haga clic en **Cargos**.
4. Haga clic en **Nuevo**.
5. En el **Código** campo, introduzca un código único que identifique el cargo.
6. En el **Descripción** campo, introduzca un nombre o descripción para el cargo.
7. En el **Descripción ext.** campo, introduzca cualquier información descriptiva adicional para el cargo.
8. De **Código de impuesto**, seleccione cualquier impuesto que se aplique al cargo.
9. (Solo para el Administrador central) En el **Grupos de tiendas** pestaña, seleccione los grupos de tiendas que utilizan este método de envío.
10. 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/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-charges.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.