> 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/fr/hardware/zebra.md).

# Zebra

Zebra fabrique des lecteurs de codes-barres et du matériel de scan mobile, et The Wallet Crew s’y intègre pour le scan des cartes Wallet en magasin.

Zebra fabrique des lecteurs de codes-barres, des ordinateurs mobiles et des imprimantes largement utilisés dans le commerce de détail et la logistique. Connecter le matériel de scan Zebra à l’équipe Wallet permet au personnel de lire les passes Wallet d’une marque avec les appareils déjà utilisés sur le terrain.

{% hint style="warning" %}

### État de la documentation

La documentation détaillée pour l’intégration Zebra n’est pas encore disponible.

Pour plus d’informations, [contactez The Wallet Crew](https://www.thewalletcrew.io/contact) pour discuter du périmètre, de la configuration et de la disponibilité de l’intégration.
{% 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.thewalletcrew.io/connectors/fr/hardware/zebra.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.