Laura Gilmour

Loyalty card entity includes card type, but not blocked date or replacement card number. Adding these fields to the loyalty card entity would inform enrolment and card maintenance reporting over time and assist in fraud behaviour reporting.

Manual loyalty adjustments gives the ability for the user to add in comments when making a loyalty points adjustment on a customer loyalty ID. This produces data quality issues, inconsistencies with reasons & potential fraud risks. By including a 'reason for adjustment' picklist in addition to the comment field, this allows for the user to select from a defined list of reasons why the loyalty points were manually added or removed, based on business scenarios / requirements list.

The reason code field could then be on all default views and extended to Loyalty reward point transaction : RetailTransactionLoyalty & Loyalty transaction : RetailLoyaltyCardRewardPointTransacti entities enabling further points and reason code reporting allowing for follow on process, training and program improvements.

To enable reporting and automation of customer updates, it would be helpful if the Customer V3 data entity could be extended by Microsoft to include the 'Block customer for loyalty enrollment' boolean.