A useful loyalty programme should make returning to your shop worthwhile without making customers surrender unnecessary information or receive messages they do not want. Start with a clear reward, a reliable points ledger and a simple way to control communications. Collecting more phone numbers is not, by itself, evidence of a better customer relationship.
Our first recommendation is to discuss Bizman Sales and Inventory when loyalty needs to follow actual purchases, returns and customer balances. Ask BriskRetail to demonstrate the customer workflow you intend to operate, including opt-outs and refunds. This article does not claim that a particular Bizman edition already includes every loyalty, messaging or privacy function described here.
Commercial disclosure: BriskRetail offers Bizman. This is an affiliated implementation guide, with research checked on 23 October 2026 and qualified privacy review pending. It is not a legal opinion or a guarantee of regulatory compliance. All customers, points and naira values below are fictional.
COVER BRIEF — Original illustration, 1600 × 900. A minimal loyalty card, reward ledger and separate messaging preference. Alt text: “A customer can earn shop rewards while controlling marketing messages.” No identifiable customer profile or real phone number; artwork pending.
1. Decide what the programme is meant to improve
Choose a specific commercial aim: more repeat visits, a better experience for regular buyers or a reward for a particular eligible purchase. A programme with five overlapping offers is harder to explain and harder to reconcile than one understandable rule.
Define who is eligible, which purchases earn rewards, when points become available, how returns affect them and whether any exclusions apply. If points expire, explain the rule before enrolment and have it reviewed for fairness and applicable consumer obligations. Do not introduce a surprise expiry simply because the points balance became expensive.
Keep the distinction between a discount, loyalty points, a gift card and customer credit. They can all reduce the cash requested at checkout, but they represent different transactions and obligations. A refund owed to a customer should not disappear into an optional loyalty balance without an approved and lawful process.
Give the cashier a short explanation that matches the written terms. A customer should be able to understand the reward without reading a long privacy notice at the till. Provide the fuller terms and privacy information through an accessible route, and allow ordinary purchases without unnecessary profiling where the transaction does not require it.
2. Separate service contact, membership and marketing
A delivery phone number serves a different purpose from a promotional mailing list. An order enquiry does not automatically authorise repeated offers, and membership of a rewards scheme should not silently expand into every future marketing channel.
The Nigeria Data Protection Act, 2023 provides several lawful bases, rather than making consent the only possible basis for every activity. It also provides for withdrawal of consent and the right to object to direct marketing; marketing processing must stop following such an objection. Have a privacy professional review the basis for each proposed purpose.
The final NDPC GAID 2025, particularly Articles 16–17, addresses lawful-basis selection and reliance on consent. Its final official text was located through indexed passages; direct retrieval was restricted during this review. Detailed application and the current final instrument remain publication-review items. The earlier draft is not a substitute.
As an operating design, offer an explicit, separate marketing choice and keep evidence of it. Record the channel, the wording shown, the choice, its timestamp and later changes. An imported contact with no reliable permission history should not be marked as opted in merely to complete a spreadsheet column.
WhatsApp also has its own Business Messaging Policy, including expectations around permission and respecting opt-outs. Check the applicable product and messaging rules before launching a campaign. Platform policy and Nigerian law both need attention; satisfying one does not automatically settle the other.
3. Build a small customer-data map
For every field, ask what useful task it performs and who needs to see it. A customer identifier can link purchases without making the full contact record visible to every cashier. A delivery address may be necessary for a delivery, but unnecessary for a walk-in loyalty purchase.
| Data group | Intended purpose | Suggested access and review |
|---|---|---|
| Internal customer ID | Link the right account and transactions | Staff see only what their task requires |
| Chosen contact channel | Delivery, service or approved communication | Distinguish service use from marketing |
| Reward movements | Explain points earned, redeemed and reversed | Cashier views balance; adjustments need approval |
| Preference evidence | Record communication choices and objections | Campaign operator checks current status |
| Delivery details | Complete a specific delivery | Limit courier disclosure; review retention |
This is a preparation map, not a prescribed legal register or a Bizman import template. Add a purpose owner, lawful-basis decision, retention rule and recipients to the working version. Keep exceptions visible rather than placing every record under “customer service.”
The NDPC’s own privacy policy illustrates how an organisation can explain purposes and lawful bases separately. Its specific bases apply to the Commission’s activities, so do not copy them into a shop’s notice. Your description must reflect what your business actually does.
Avoid collecting a full date of birth for a simple birthday offer unless the purpose and necessity are justified. Consider whether a less precise optional field would suffice. Do not infer health conditions, religion or other sensitive characteristics from purchase history to create promotional segments. A pharmacy or another sensitive setting needs specialist review beyond an ordinary loyalty implementation.
4. Work out the cost before promising the reward
Suppose a fictional shop awards one point per ₦100 of eligible spend, and one point redeems for ₦1. That is a potential reward of 1% of eligible spend. This is an illustrative rule, not a recommended rate or a verified Bizman setting.
Loyverse’s official loyalty guide documents a percentage-based programme and the relationship between points and currency in its own product. It is a useful comparison for simple rewards, but you must check rounding, refunds, exclusions and currency behaviour in the exact system being considered.
Our example customer starts with 200 points. Assume eligible amounts are already defined by the shop’s approved rules and have no unresolved tax treatment.
| Event | Points movement | Resulting balance |
|---|---|---|
| Opening balance | — | 200 |
| Eligible purchase of ₦20,000 | +200 | 400 |
| Later redemption | −150 | 250 |
| Return of ₦5,000 from the earning purchase | −50 | 200 |
| Closing balance | 200 + 200 − 150 − 50 | 200 |
The points reversal belongs to the original earning sale. The return’s money refund is a separate calculation. Explain in the terms how a return is handled if earned points have already been spent and the remaining balance is insufficient. Do not let staff invent a negative balance or reduce a refund without an approved policy.
At programme level, ₦1,000,000 of eligible spend would create ₦10,000 of reward value under this example. If 60% were eventually redeemed, that would be ₦6,000 of redemptions. The 60% is a planning assumption, not measured customer behaviour. Do not immediately treat unredeemed value as profit; an accountant should decide how promises, expiry and expected redemption are recognised.
Include communication costs, staff time and fraud losses in the programme review. A scheme can increase sales while reducing contribution if it rewards purchases that would have happened anyway. Evaluate the cost alongside gross margin using the margin guide.
DIAGRAM BRIEF — Original ledger illustration, 1440 × 960. Earn, redeem and reverse entries linked to sale references. Alt text: “Loyalty points retain an audit trail through purchases, redemptions and returns.” Use only the fictional balances above; artwork pending.
5. Handle shared numbers, duplicates and returns carefully
A phone number is a contact route, not perfect proof of identity. Families may share a number, and numbers can be reassigned. If a cashier searches by phone and immediately reads out past purchases, the shop can disclose information to the wrong person.
Agree a proportionate account-verification process and give staff a safe escalation route. Avoid demanding excessive identity documents for a small reward merely because verification was not designed in advance. For an account with a larger balance, additional safeguards may be appropriate, but the business must justify and protect the information it collects.
Do not automatically merge two records because their names look similar. Review the accounts, preserve transaction references and log who approved the merge. If the software cannot reverse a mistaken merge, that is an important demonstration question. Customers should not inherit another person’s purchase history or debt.
Require approval for manual reward adjustments, especially a repeated pattern just below the approval limit. Review employee-linked accounts and refunded sales that still retain earned points. Investigate the transaction evidence before accusing anyone: duplicate imports and delayed sync can resemble abuse.
The Loyverse API reference exposes earned and deducted points in receipt data. That documents one way a system makes loyalty movements inspectable. Ask the Bizman team to show the equivalent operational evidence in the proposed setup; do not infer matching API fields or functionality.
6. Make opting out work across every sending route
Write a clear internal workflow for a customer who says “stop.” It should work whether the request arrives at the counter, through a message or through an email reply. Staff should not require the customer to find a different department just to express the same choice again.
First, record the request and the relevant account or contact after appropriate verification. Second, stop the affected marketing activity promptly. Third, propagate the change to any messaging service and pending campaign. Fourth, keep a minimal record sufficient to prevent accidental re-enrolment, under a reviewed purpose and retention rule. Fifth, confirm the outcome without including a new promotion.
| Opt-out test | Expected operating result | Evidence to retain |
|---|---|---|
| Customer replies before a scheduled send | Pending promotional message is suppressed | Request and queue outcome |
| Old customer file is imported later | Suppression is not overwritten | Import exception or preserved preference |
| A second branch prepares a campaign | Current choice applies there too | Shared preference check |
| Order still needs delivery contact | Necessary service message is separated from promotion | Purpose and content of message |
An unsubscribe is not automatically a request to erase all transaction records. Conversely, keeping a tax record does not authorise indefinite advertising. Separate those purposes and involve the privacy lead when the customer also asks for deletion or access.
Use test accounts to rehearse the process before a campaign. Do not send “test” promotions to real customers who have opted out. If preferences cannot be applied reliably across a spreadsheet and messaging platform, pause that campaign route until the gap is resolved.
7. Limit access and agree how records leave the business
Give cashiers the access needed to identify the account and complete the transaction. Restrict bulk exports, campaign creation and reward adjustments separately. A shared administrator password makes it difficult to explain who downloaded a customer list or changed a balance.
List every outside party that receives customer information: hosting provider, messaging service, delivery partner, support contractor and any reporting tool. Agree responsibilities, access, deletion or return of data and incident escalation in the relevant contracts. Have a specialist assess cross-border processing rather than assuming a cloud region or supplier promise settles the issue.
Set retention rules by purpose, with review dates and legal holds where required. A dormant marketing contact and an invoice supporting an unresolved dispute should not be deleted or retained under identical logic. Test how a deletion decision affects backups, exports and reimports so that removed data does not quietly return.
The NDPC FAQs discuss registration and compliance-audit questions under the current framework. Obtain a professional assessment of any registration, reporting, DPO or other obligations applicable to your business. This article does not infer an exemption from shop size or prescribe a fee from an unverified summary.
8. Evaluate Bizman around customer trust and usable records
Bring three workflows to the Bizman demonstration: a purchase earning points, a partial return after redemption and a marketing objection that must survive a later import. Include a shared-number scenario and a cashier who must not export the database.
Ask for written confirmation of which capabilities are standard, configured, integrated or unavailable in the proposed edition. If messaging occurs through an external service, identify which system owns the current preference and how changes reach the sender. A customer-management screen alone does not prove a compliant campaign process.
Bizman Sales and Inventory is our primary recommendation to investigate where the programme depends on sales and returns. Loyverse provides a researched comparison for simpler points mechanics. A shop that only needs a small manual reward scheme may reasonably start there, provided its records and customer choices remain manageable. A complex multi-brand programme may need a specialist loyalty service, with the additional integration and privacy work that introduces.
Request the full implementation and ongoing cost, including messaging, training, data cleaning and support. Prices are quote required. No supplier in this guide has been hands-on tested, and no product is presented as automatically compliant with the Nigeria Data Protection Act.
WORKFLOW BRIEF — Original flow, 1440 × 810. Enrolment choice → permitted service → reward → preference change → suppressed campaign. Alt text: “Marketing choices remain separate from purchases and loyalty balances.” No real message screenshots; illustration pending.
9. Measure useful repeat business without building unnecessary profiles
Review repeat visits, redemption cost, disputed balances, return reversals and opt-out handling. Compare similar periods and distinguish a price increase from more purchasing. A customer who spends more because every item costs more has not necessarily become more engaged.
If evaluating a campaign, use a proportionate, privacy-reviewed method and acknowledge selection bias. Members may already have been your most frequent customers. A before-and-after sales increase does not prove that the reward caused it, especially during a promotion or seasonal change.
Keep a complaint path visible and make it easy for staff to correct mistakes. Reliable service, accurate stock and fair handling of a return can matter more than another points multiplier. Loyalty software should support that relationship rather than becoming an excuse for unwanted contact.
Start with the Bizman product information, then request a scoped consultation using fictional or appropriately redacted sample data. Agree the reward rules and privacy decisions before importing the customer list. That gives the business a programme it can explain, cost and operate consistently.