creekpos · SaaS / Online
Customer stamps and points · SaaS / Online
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Owner / cashier / customer
Required tools
Enabled customer loyalty tools. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Steps
- Configure the live loyalty scheme and redemption rules with owner permissions. Explain eligible visits/purchases rather than promising a reward for every event.
- Give the customer their supported card link or scan flow. The phone card shows current stamps and points balance; inspect the correct customer record before adding or redeeming value.
- After an eligible visit or purchase, verify the updated balance and reward state. Returns, voids and reversals must follow the loyalty rules rather than manually inventing visits.
- Apple Wallet and Google Wallet remain Coming soon and disabled. The live web card works without issuing a Wallet pass; no installation or automatic pass-update promise is made today.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Classic Desktop has its native customer/loyalty controls where enabled. Cloud phone cards and their server balance belong to the online loyalty workflow. Neither edition currently issues the proposed new Wallet pass.