Loyalty cards and programmes

Create Cegid Retail Y2 loyalty cards and show programme names, points, stored value, and expiry on wallet passes.

The connector creates loyalty cards in Cegid Retail Y2 and reads card details, programme names, and point balances for wallet passes. This keeps Apple Wallet and Google Wallet loyalty passes aligned with Cegid data.

Real-world examples

• A customer enrols at the till and receives a loyalty pass carrying their card number and current balance.

• A purchase adds points in Cegid, and the balance on the pass follows.

• A card is issued online with no store attached, using a configured default store.

Creating a card

A loyalty card is created by adding the corresponding step to the enrolment flow, after the step that creates the customer. The card is created against the store the customer is being enrolled at, and the flow can be configured to ignore the store the end-user's session carries and use a fixed default instead, which is useful for online enrolment where no real store applies.

Two Cegid prerequisites decide whether creation succeeds. The store must belong to the relevant loyalty campaign, and it must be open. Where a closed store is used, the connector retries once against the configured default store before failing.

Reading loyalty data

Cards attached to a customer are read on demand, filtered to those that are active and not closed. Where Cegid reports which programmes are available at the store, the list is further narrowed to cards belonging to those programmes, so that a card from an unrelated programme does not appear on a pass.

The following values are made available for pass templates.

Field	Contains
loyalty.programName	The name of the loyalty programme the card belongs to.
loyalty.points	The point balance, with trailing zeros removed.
loyalty.activationDate	When the card was activated.
loyalty.expirationdate	When the card expires.
loyalty.amount, loyalty.currency	Stored value, where the programme carries a monetary balance.

loyalty.expirationdate is spelled entirely in lower case, unlike the fields around it. This is a known inconsistency; templates must use the spelling exactly as shown.

The card identifier itself is written onto the pass as y2.loyaltyCardId.

When a card is deactivated

A pass carries the identifier of the loyalty card it represents. If that card is subsequently deactivated in Cegid, reads against it fail, and Cegid reports that the programme is not associated with a campaign defined for the store. That message is misleading, because the underlying cause is the card rather than the campaign.

The remedy is to clear the loyalty card identifier from the affected pass, so that the next read resolves the customer's current card instead.

FAQ

A new store cannot create loyalty cards. What is missing?

The store is almost certainly absent from the Cegid loyalty campaign. Adding it there resolves it; no change is needed in The Wallet Crew.

Why does a pass show no points immediately after a purchase?

Either loyalty caching is holding a recent response, described in Advanced configuration, or the wallet has not yet requested an update. Business notifications shorten the second delay.

Can a customer hold several loyalty cards?

Cegid permits it. The connector reads the active, non-closed cards and narrows them to programmes available at the store, so what appears on a pass depends on the programme configuration.