> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/pos.md).

# Point of Sale (POS)

Connect POS systems to The Wallet Crew so wallet passes can be identified, validated, and updated from checkout and redemption flows.

POS systems are the operational source for checkout and redemption events. The Wallet Crew connects those systems to Apple Wallet and Google Wallet so passes stay usable at the moment of transaction.

## How POS integrations work

In a POS integration:

1. The POS remains the source of truth for transaction and redemption data.
2. The Wallet Crew maps identifiers and pass data to wallet-compatible payloads, so the pass can be identified at checkout or at a service counter.
3. Wallet updates reflect redemption events and status changes that matter at checkout or after redemption. Balances, eligibility, or usage counters can optionally be synchronized.

This keeps operational logic in existing systems while making wallet passes reliable in-store.

<details>

<summary><strong>Real-world examples</strong></summary>

* A retailer scans a loyalty pass at checkout, then refreshes the points balance.
* A gift-card redemption changes the pass balance immediately after payment.
* A service counter validates a membership pass before applying its benefits.

</details>

## Available POS connectors

Adyen and Shopify POS change what staff or customers see at the counter. Cegid links a POS system to pass data. The other systems in the table have no published documentation: [contact The Wallet Crew](https://www.thewalletcrew.io/contact) to discuss them.

| Connector   | Type                                                                              | Status         | Page                                                                       |
| ----------- | --------------------------------------------------------------------------------- | -------------- | -------------------------------------------------------------------------- |
| Adyen       | Customer-facing display: QR code on the payment terminal and beacon notifications | Documented     | [Adyen](https://docs.thewalletcrew.io/connectors/pos/adyen.md)             |
| Shopify POS | Scan a wallet pass in Shopify POS                                                 | Documented     | [Shopify POS](https://docs.thewalletcrew.io/connectors/pos/shopify-pos.md) |
| Cegid       | POS and retail data connector                                                     | Documented     | [Cegid](https://docs.thewalletcrew.io/connectors/pos/cegid.md)             |
| NewStore    | POS and order management                                                          | Not documented | [NewStore](https://docs.thewalletcrew.io/connectors/pos/newstore.md)       |
| Openbravo   | Retail commerce and POS                                                           | Not documented | [Openbravo](https://docs.thewalletcrew.io/connectors/pos/openbravo.md)     |
| Square      | POS and payments                                                                  | Not documented | [Square](https://docs.thewalletcrew.io/connectors/pos/square.md)           |
| TCPOS       | POS for retail, hospitality and leisure                                           | Not documented | [TCPOS](https://docs.thewalletcrew.io/connectors/pos/tcpos.md)             |

## POS systems not listed

For an unlisted POS, see [Choose an integration path](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md#choose-an-integration-path). A tenant-specific POS uses a [custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md). The responsibilities of each side are in [Wallet pass connectors](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md#responsibilities). Tenant scripting can call private APIs and apply proprietary mapping rules. Define the identifier, API contract, trigger model, and operational owner before implementation.

## FAQ

<details>

<summary><strong>What should be decided and validated first?</strong></summary>

Start with identifier strategy, redemption flow ownership, and update triggers. Test the scan path with production scanner hardware before rollout.

</details>


---

# 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.thewalletcrew.io/connectors/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.
