> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/cug-57.00/cug-57.00-es/referencia-de-usuario-de-commander-57.00/resumen-de-estaciones-de-trabajo-pos.md).

# Resumen de estaciones de trabajo POS

Los dispositivos Verifone Point of Sale (POS) suelen usar Verifone Commander como servidor.

## Verifone C18

Verifone C18 es el POS integrado más potente de Verifone para tiendas de conveniencia, con una funcionalidad y versatilidad incomparables. La interfaz de usuario de Verifone C18 está diseñada para cajeros que atienden a clientes que desean una experiencia sin fricciones. La brillante pantalla de alta definición resulta agradable a la vista. Con unas impresionantes 18,5 pulgadas, ofrece un amplio espacio para todas las necesidades de venta.

<figure><img src="https://content.gitbook.com/content/ptSeunKXxgbdlNcg3Lkc/blobs/1cYg3LVsAjVuwhb42A8H/image.png" alt=""><figcaption><p>Verifone C18</p></figcaption></figure>

### Selector de aplicaciones

La pantalla POS de Verifone C18 puede colocarse en Home (orientada al cajero) o Flip (orientada al cliente) y puede orientarse para mostrar las aplicaciones en modo horizontal o vertical en las posiciones Home y Flip.

Esta capacidad de hardware facilita la ejecución de múltiples aplicaciones orientadas al cajero y al cliente en orientaciones vertical y horizontal.

{% hint style="info" %}
*Consulte la documentación de referencia para el usuario de App Selector para obtener más información sobre esta función.*&#x20;
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/cug-57.00/cug-57.00-es/referencia-de-usuario-de-commander-57.00/resumen-de-estaciones-de-trabajo-pos.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.
