Publish a versioned programme card
State the audience, joining route, earning action, reward, expiry wording, channel and accountable programme owner.
Workflow blueprint
A small-business loyalty programme should be able to replay every reward movement
A programme history card, not legal consent, purchase verification, fair-value advice, fraud detection or guaranteed repeat business.
Keep the displayed promise, member reference, reported activity, rule edition, stamp or point movement, redemption and correction attributable.
TL;DR — Keep the displayed promise, member reference, reported activity, rule edition, stamp or point movement, redemption and correction attributable.
Record member events without rewriting them
Preserve reported purchases, paper-card imports, goodwill awards, returns and source identifiers as separate entries.
Evaluate a named rule edition
Show the input, applicable programme version, resulting movement and any pause caused by duplication or ambiguity.
Handle adjustments and exits visibly
Add a reasoned correction, suppression request or membership closure while retaining the original programme history.
Page-specific decision aid
A programme promise, member event, rule, stamp, reward, adjustment and exit replay card
The replay card follows a cafe member from an in-store offer through a paper stamp import, purchase report, reward issue, return, staff correction and marketing opt-out. It displays the wording and rule edition active at every movement without deleting the earlier balance history.
- ✓A receipt reference is not verified identity.
- ✓A rule result is not an unquestionable entitlement.
- ✓An opt-out is not automatic membership closure.
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.
- ✓Material programme wording retains its effective dates
- ✓Message opt-out and membership closure use different states
- ✓Reversed activity never disappears from reward history
- ✓Consent privacy valuation taxation purchase fraud profitability and compliance conclusions excluded
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