> 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/cegid.md).

# Cegid

Cegid provides point-of-sale and retail management software. The Wallet Crew connects to Cegid Retail Y2, Cegid Retail Live Store, and Cegid UR.

Cegid provides retail management and point-of-sale (POS) software for store operations and customer transactions. Connecting Cegid to The Wallet Crew links Apple Wallet and Google Wallet passes with the customer records, loyalty balances, and transaction history used in store.

Three Cegid products are supported, and each has a separate configuration. **Cegid Retail Y2** is the primary connector. It reads and writes customer profiles, loyalty cards, vouchers, and sales documents through Y2 web services. **Cegid Retail Live Store** opens a The Wallet Crew enrolment form within Cegid's POS application. **Cegid UR** is a distinct product with its own connector and configuration.

<details>

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

* A customer enrols at the till, the profile is created in Cegid Retail Y2, and a loyalty pass is issued to Apple Wallet or Google Wallet within seconds.
* A purchase updates the loyalty balance in Cegid, and the points shown on the pass follow without the customer reopening anything.
* A store associate opens a customer record in Live Store and completes a Wallet Crew enrolment form without leaving the point-of-sale screen.
* A brand reports on wallet adoption from Cegid itself, because the connector writes the installation state back into a Cegid customer field.

</details>

### What the Cegid Retail Y2 connector covers

| Capability                   | What it does                                                                                         | Where it is documented                                                                                            |
| ---------------------------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Customer profiles            | Creates and updates customer records from an enrolment form, and reads them back to populate passes. | [Fields mapping](/connectors/pos/cegid/customer-data-and-loyalty/cegid-retail-y2-fields-mapping.md)               |
| Loyalty cards                | Creates loyalty cards, and reads card details, programme names, and point balances.                  | [Loyalty cards](/connectors/pos/cegid/customer-data-and-loyalty/loyalty-cards-and-programmes.md)                  |
| Vouchers and stored value    | Reads gift cards, gift certificates, deposits, and loyalty certificates attached to a customer.      | [Receipts and vouchers](/connectors/pos/cegid/customer-data-and-loyalty/receipts-vouchers-and-sales-documents.md) |
| Receipts and sales documents | Reads sales documents and generates receipt PDFs for wallet journeys.                                | [Receipts and vouchers](/connectors/pos/cegid/customer-data-and-loyalty/receipts-vouchers-and-sales-documents.md) |
| Advisors and stores          | Reads the store catalogue and salesperson lists, for layouts that display an advisor.                | [Scripting reference](/connectors/pos/cegid/developer-reference/scripting-reference.md)                           |
| Real-time events             | Receives Cegid business notifications so wallet data refreshes after activity in store.              | [Business notifications](/connectors/pos/cegid/events-and-operations/business-notifications.md)                   |

### Choosing what to set up

Every wallet journey backed by Cegid starts with the Cegid Retail Y2 connector, because that is what reads and writes the customer record. Configuring it is covered in [Configure the Cegid Retail Y2 connector](/connectors/pos/cegid/setup-and-configuration/connect-with-cegid-retail-y2.md), and the Cegid-side groundwork that has to be in place first is listed in [Cegid-side prerequisites](/connectors/pos/cegid/setup-and-configuration/cegid-side-prerequisites.md).

Beyond that, two decisions shape the rest of the setup. The first is whether stores need their own Cegid credentials. Most brands run a single connection, but a brand whose stores each have their own Cegid web-service user needs the arrangement described in [Connections and stores](/connectors/pos/cegid/setup-and-configuration/connections-and-stores.md). The second is whether the default field mapping is sufficient. It rarely is, so [Customise the mapping](/connectors/pos/cegid/customer-data-and-loyalty/customise-the-mapping.md) should be read as part of the initial implementation rather than as an advanced topic.

{% hint style="info" %}
These pages describe the connector as it behaves for any Cegid Retail Y2 user, whatever the commercial route in. Nothing here assumes a particular contractual arrangement between the brand, Cegid, and The Wallet Crew.
{% endhint %}

### Page guide

| Area                                                                                                        | Read it for                                                            |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| [How the Cegid Retail Y2 connector works](/connectors/pos/cegid/how-the-cegid-retail-y2-connector-works.md) | The data flow, system of record, and wallet-pass refresh model.        |
| [Setup and configuration](/connectors/pos/cegid/setup-and-configuration.md)                                 | Cegid preparation, connections, settings, rate limits, and caching.    |
| [Customer data and loyalty](/connectors/pos/cegid/customer-data-and-loyalty.md)                             | Customer mapping, loyalty cards, receipts, vouchers, and stored value. |
| [Events and operations](/connectors/pos/cegid/events-and-operations.md)                                     | Business notifications, troubleshooting, and operational procedures.   |
| [Developer reference](/connectors/pos/cegid/developer-reference.md)                                         | Scripting, supported helpers, APIs, and data structures.               |
| [Cegid Retail Live Store](/connectors/pos/cegid/livestore.md)                                               | The external customer form in Cegid's point-of-sale application.       |
| [Cegid UR](/connectors/pos/cegid/cegid-ur.md)                                                               | The separate Cegid UR connector.                                       |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/connectors/pos/cegid.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.