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

# Cegid UR

Understand The Wallet Crew connector for Cegid UR, including its customer and coupon capabilities, configuration, and mapping.

Cegid UR is distinct from Cegid Retail Y2. It has its own connector, configuration, and feature set. The two connectors should be evaluated and configured separately.

{% hint style="info" %}
This page is deliberately brief. For an implementation using Cegid UR, [contact The Wallet Crew](https://www.thewalletcrew.io/contact) to confirm the scope available.
{% endhint %}

### What it covers

The Cegid UR connector reads and writes customer records, and reads coupons attached to a customer. Where the Cegid Retail Y2 connector spans loyalty cards, vouchers, receipts, advisors, and business notifications, the Cegid UR connector does not.

### Configuration

Configuration is held in the tenant configuration store rather than on a connector page: the service address, the business unit and business function that identify the brand within the Cegid UR environment, an optional cache duration, and rate-limit settings.

{% hint style="warning" %}
Unlike the Cegid Retail Y2 connector, the Cegid UR rate limiter is disabled unless configured. Where the Cegid UR environment enforces a request ceiling, the limit should be set deliberately rather than left at its default.
{% endhint %}

Credentials are not stored in the configuration. Authentication is applied by a connection interceptor script that reads the key from the secret store, as shown in the [Scripting reference](/connectors/pos/cegid/developer-reference/scripting-reference.md).

### Customising the mapping

The Cegid UR connector exposes a mapper on the same pattern as Cegid Retail Y2, with methods named for UR rather than Y2. One difference matters: unlike the Y2 mapper, **either method may be omitted**, so a script that only needs to customise one direction can register just that one.

Cegid UR represents consents as a list of coded entries in which one code identifies the consent and a second carries the answer, with distinct values for yes, no, and not stated. Both directions of a mapping must use the same dictionary.

### FAQ

<details>

<summary><strong>Can a brand run both Cegid Retail Y2 and Cegid UR?</strong></summary>

They are separate connectors with separate configuration. Running both against one wallet programme is not a standard arrangement and should be scoped with The Wallet Crew.

</details>

<details>

<summary><strong>Does Cegid UR support business notifications?</strong></summary>

No. Wallet data refreshes when a pass is rebuilt, as described in [How the Cegid Retail Y2 connector works](/connectors/pos/cegid/how-the-cegid-retail-y2-connector-works.md); there is no equivalent real-time channel.

</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/cegid/cegid-ur.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.