State the purpose
Record programme, customer purpose, enrolment source and market.
Workflow blueprint
A loyalty program for retailers should make its customer purpose explicit
A page-specific review aid, not a universal product or compliance claim.
Keep purchase event, membership, consent, reward rule, redemption and customer correction separate for a Mauritius launch.
TL;DR — Keep purchase event, membership, consent, reward rule, redemption and customer correction separate for a Mauritius launch.
Trace the event
Relate purchase, item, points rule, expiry and adjustment reason.
Review the message
Keep consent, channel, campaign, opt-out and customer response distinct.
Close the correction
Assign privacy, consumer, tax, promotion and support questions.
Page-specific decision aid
Retail loyalty purpose map
A customer purpose, consent, purchase event, points rule, adjustment, redemption, message and correction map.
- ✓Consent has a stated purpose
- ✓Points events keep their source
- ✓Redemption is not cash settlement
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Programme and customer identity
- ✓Consent and purchase source
- ✓Points and redemption history
- ✓Privacy and support owner
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow