Skip to main content

POS/Checkout Capability

Purpose of this document​

This document provides details at the business, technical, and implementation levels for specific features within the ES Loyalty feature set. This document addresses a subset of functionality centred on POS/checkout capability.

POS prompts​

Ability to configure POS prompts (for example, email opt-in or email capture prompt, dollar amount away from a bonus offer, or contact call centre prompt). Execution depends on the client's POS capabilities.

Anonymous shopper prompts​

Ability to configure POS prompts for non-loyalty members (for example, displaying the points a member could have earned if they were enrolled in the loyalty program).

The objective of this feature is to present prompts to anonymous shoppers to inform them about points they could earn by scanning their loyalty card, thereby increasing the scan rate.

Only mass offers created in the Console are eligible for prompts to be presented to anonymous shoppers.

Receipt messaging on finalize​

Ability to configure receipt messaging (for example, point balance, base and bonus points earned, summary of completed offers, targeted offers pending, or "you could have earned" messages). Execution depends on the client's POS capabilities.

TBA

Returns claw back​

Ability to process returns and claw back base and bonus point earnings according to the adjusted transaction details. Execution depends on the client's POS capabilities.

  • Adjust Points in a Basket (with receipt) POS API request in Postman: in the Postman ES

Store and forward​

Ability to receive and process bulk transactions in the event that the connection between ES Loyalty and stores is temporarily offline. Execution depends on the client's POS capabilities.

If ES Loyalty and the client POS or e-commerce storefront lose connectivity, all finalised calls should be converted to store and forward (SAF) for forwarding at a later date. SAF cannot process redemptions; these are processed once connectivity is restored. SAF transactions still qualify for rewards, but the transaction date is backdated to when the offers occurred in order to maintain reporting accuracy.

  • Store and Forward (SAF) POS API request in Postman: in the Postman ES Loyalty workspace,

Email member lookup​

Ability to perform a member lookup and start a session using a unique member email address (as an alternative to member ID lookup).

TBA

  • Sets Email Address for Loyalty ID -- POS API request in Postman: in the Postman ES

E-receipts trigger​

Ability to inform the POS whether a member has opted into e-receipts so that the email process can be initiated.

TBA

  • Set Opt-In Status for Loyalty ID -- POS API request in Postman: in the Postman ES Loyalty

No-receipt return​

This request allows adjustments to be made when a transaction receipt is not available.

No-receipt adjustments or reversals do not reference an original transaction, so there is nothing to compare the reversal against and none of the original offers can be clawed back.

However, the following do apply:

  • Points are clawed back against base and base membership offers (not including frequency offers).
  • Relevant program contributions are clawed back and membership tiers adjusted, if applicable.
  • Relevant offer completions are clawed back.
  • There may be restrictions on how old a transaction can be for adjustments to still be allowed.

TBA

  • POS API No-Receipt Adjustment POST request -- Postman: in the Postman ES Loyalty
Last updated on