We have questions about the implementation options for our planned loyalty app for Clover. We currently have POS implementations for Micros, POSitouch, Verifone, and a browser-based “virtual terminal”.
We’ve noticed that the Loyalzoo app offers many of the features we are also targeting for Clover. It would be a great help for us to get insights as to which Clover APIs were used to create this app, and what merchant add-ons are required to support an integrated loyalty experience (such as Payments Plus, which seems to be required for Perka).
We are targeting these loyalty features:
Essential Functionality
- Identify patron via account number or mobile phone number
- Clerk sees patron name and rewards cash balance
- Patron can elect to use rewards cash balance to pay for all or part of sale
- Capture sale amount and tender amount (sale less redeemed rewards) and transmit via our API with patron id
- Patron can elect to use “comps” balance against pre-determined merchant item
Additional Functionality
- Clerk can add new patron (name, email, phone, even address)
- Clerk can transfer all value from one patron account to another
- Patron can elect to purchase memberships offered by loyalty program
- Patron can elect to purchase “comps” package offer by loyalty program
* "Comps" are an integer-based stored value in our system that can be configured by the merchant per their needs. For example, a bowling center could assign their comps type to "Games" to allow patrons to pre-purchase games, or to accrue games as a reward.
