Workflow blueprint

Restaurant loyalty needs evidence behind every balance change

A reward-review ledger, not a consumer identity platform, payment wallet, stored-value programme, fraud engine or marketing compliance service.

Preserve enrolment source, programme version, communication purpose, qualifying transaction reference, rule candidate, adjustment authority, redemption result, reversal, expiry and complaint resolution.

TL;DR — Preserve enrolment source, programme version, communication purpose, qualifying transaction reference, rule candidate, adjustment authority, redemption result, reversal, expiry and complaint resolution.
1

Register enrolment and programme version

Record the supplied contact, join channel, effective rules, communication purpose, restriction and unresolved identity question.

2

Create earning candidates from sources

Link the transaction reference, qualifying rule version, proposed points, import time and missing evidence without declaring eligibility.

3

Review redemption and adjustments

Preserve attempted use, available candidate, manager decision, reason, partial reversal and customer challenge as separate events.

4

Control expiry and communication choice

Keep expiry basis, notice reference, marketing opt-out, balance correction and final response under their responsible owners.

Page-specific decision aid

A restaurant loyalty enrolment, earning-source, rule-version, adjustment, redemption and expiry ledger

The ledger follows a diner from enrolment through a qualifying meal, late transaction import, changed rule, manager review, attempted redemption, partial reversal, marketing opt-out and final correction. Earlier balance states remain visible after every change.

  • Membership is not marketing permission.
  • A points balance is not proof of an eligible purchase.
  • A redemption candidate is not cash value.
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.

  • Every balance movement cites a source and rule version
  • Marketing choice remains separate from programme membership
  • Manual corrections never erase the prior calculation
  • Identity marketing law payments stored value tax fraud purchase eligibility points value and retention outcomes excluded

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