RIGI24 · CUSTOMER LOYALTY

What Features Should Customer Loyalty Software Have? A Guide to Selecting and Introducing Rigi24 Loyalty Features

This article provides a comprehensive checklist for selecting customer loyalty software and explains how Rigi24 Loyalty's modules handle membership, points, tiers, rewards, entitlements, QR, branch scope, expiration, and integration.

Updated: 2026-10-10

When a business decides to launch a customer loyalty program, choosing the software usually starts with a simple checklist: Does it have points? Does it offer discounts? Does it have a customer card? Does it provide reports? But the difference between a showpiece tool and a reliable system lies precisely in the details that are less visible in short demos. Should customer loyalty software only "add points" or "display a coupon"? Or should it be able to audit point transactions, prevent double redemption of rewards, manage branches, control expiration dates, generate secure IDs for digital cards, and synchronize with the business’s main payment process in real time?

If Loyalty is to enter real operations, the answer is clear: the system must be more than a digital discount card. A Reward is financial; even if it takes the form of a gift or points, it ultimately affects business costs and the customer’s received value. For this reason, the software should be as simple for the customer as it is precise and controllable behind the scenes.

This article provides a comprehensive checklist for selecting loyalty software and simultaneously explains how the Loyalty module in Rigi24 is designed with membership logic, points, tiers, rewards, entitlements, QR, branch scope, expiration, and integration. The goal is not just to introduce features; it is to understand exactly what problem each feature solves.

1. Customer Membership; a Foundation That Should Not Be Underestimated

Every loyalty club starts with membership. The system must know if the customer is a member, whether the membership is active or suspended, when they joined, and when their last activity was. If membership is just a tick on the profile, many processes become ambiguous down the line.

Membership must be connected to the business’s actual Customer, not that each module creates a separate version of the same person. This is particularly important in a multi-module platform. If a customer has one ID in the CRM, another in the Restaurant system, and a third in Loyalty, unified reporting and experience gradually become difficult.

Rigi24 uses a shared Business + Customer model. Loyalty is built on this identity. Therefore, membership is linked to the existing customer, and the history of points, tiers, and rewards belongs to that same person. This architecture helps ensure the loyalty club is not an isolated island separate from the rest of the system.

2. Point Ledger; Why Is Point Balance Alone Not Enough?

Some systems only keep a number called “current points.” This method is simple, but if a customer asks, “Where did these 480 points come from?” or a manager wants to know why the balance changed, an accurate answer is difficult.

A professional system must have a ledger; that is, each increase or decrease in points should be an independent record with reason, time, and event key. Registration might grant a welcome bonus. A restaurant purchase might create new points. Redeeming a reward reduces points. Expiration can also have a separate transaction record.

In Rigi24, every Point event is recorded as a Ledger. In addition to the point amount, Balance After, event type, description, and Event Key can be stored. The Event Key is important for Idempotency; if an event is resent due to a Retry, the system should not award points again.

These details may not be visible to the end customer, but they are crucial for financial assurance and support. If a customer claims their points have decreased or they received a reward twice, a thorough investigation is nearly impossible without the Ledger.

3. FIFO and Point Expiry Management

If points have an expiration date, the next question is: Which points should be spent first when redeeming? Suppose a customer has 100 older points expiring in ten days and 200 new points valid for six months. If the system randomly consumes the new points first, the older points may expire later, causing the customer to feel unfairly treated.

FIFO means First In, First Out; older points, if still valid, are spent first. Rigi24 uses Allocation to consume Points so that it is clear exactly which Credit Lots a Debit consumed. This design is also important for Reversal. If a Redeem is canceled, the system needs to know how much from which Lot can be returned and must not mistakenly revive points that expired in the meantime.

This level of control ensures that Cancellation and Expiration are consistent with point accounting.

4. Tier; Membership Level is More Than Just a Nice Badge

Tier is one of the most important tools in designing Loyalty. Bronze, Silver, Gold, or VIP can create a sense of progress, but if they are just badges, their value is limited. The level should have a clear logic, and its benefits should be explainable.

In Rigi24, Tier can have point thresholds, discount percentages, and point multipliers. For example, a Silver customer might have a different point earning multiplier compared to the base level. This structure allows a business to provide greater benefits to long-term customers without manually deciding each time.

An important note is to separate Lifetime Value from the current balance. A customer may redeem their points, but this does not mean their value history is lost. Tier should be calculated based on a clear policy and stable data.

5. Reward Catalog; Reward is Not Just a Discount Percentage

A common mistake in simple software is to limit Rewards to just a "10% discount." In reality, businesses have different needs. A restaurant might give a free dessert. A salon may offer a free side service. A store might provide store credit. Another business may deduct a fixed amount from a purchase.

In the Rigi24 model, four main types of Benefits are considered for Rewards: Discount, Gift, Free Service, and Store Credit. Discount can be either Percent or Fixed. Free Service can keep a Snapshot of the service, and Store Credit can have a remaining balance.

Reward variety helps businesses use benefits that are more reasonable in terms of profit margin instead of giving perpetual discounts. Sometimes a gift with a low actual cost to the business holds high perceived value for the customer.

6. Snapshot; Why Should History Not Change with Today’s Edits?

Assume today a Reward called "10% Autumn Discount" is issued. One month later, the manager edits the same Reward and changes its amount to 15%. Should the previously issued reward suddenly become 15%? In many scenarios, the answer is no.

This is why business systems use Snapshots. At the time of Redemption or Billing, important information such as the Reward name, type, amount, tier, and discount value is saved within that event. Later, if the original definition changes, the past financial record remains unchanged.

Rigi24 uses Snapshots during Reward issuance and Restaurant Billing. This is very important for audits and dispute resolution.

7. Entitlement; the difference between "Redeeming" and "Actual Consumption"

When a customer spends points, a Reward may be granted to them. However, this reward is not necessarily consumed immediately. For example, a customer spends 100 points and receives a Benefit that is valid until tomorrow. This Benefit must have an independent status.

Rigi24 has the concept of Entitlement for this. Entitlement can be Issued, Used, Cancelled, or Expired. This distinction allows the system to differentiate between the "right to use" and the "actual use."

If software immediately considers a Reward as Used upon Redeeming points, real scenarios like purchase cancellation, changing the customer's mind, or using the reward at a later time will not be managed correctly.

8. Atomic Consumption; a Reward must be consumed only once

Suppose a customer presses the payment button twice, the internet connection drops and reconnects, or requests arrive simultaneously from two devices. Without concurrency control, a Reward might be used twice.

The consumption of a Benefit must be Atomic. This means that the validity check, usage registration, and status changes must be reliably performed within a single Transaction. In Rigi24, this logic is implemented in the LoyaltyRewardEntitlementService, and Usage Key is used for Idempotency.

These technical details may not be visible to businesses, but at a real scale, precisely these details prevent losses and disputes.

9. Reversal; what happens if a transaction is canceled?

A good Loyalty software does not only handle successful paths; the reversal process must also be designed. If a Reward has been Redeemed but the Benefit has not yet been consumed and the operation is canceled, what happens to the points?

Rigi24 has Reversal logic for Cancellations. Point allocations are checked, and the valid amount is returned to the original Lots. If any part of the points expired during the interim period, the system must not revive them against the Policy.

Also, Reward Stock is corrected if possible, and a Reversal Ledger is created for audits. The goal is that cancellations are as traceable as the initial purchase.

10. Expiration; expiration must be Server-Side

Relying on browser JavaScript for expiration is a mistake. If expiration dates are not controlled on the server, the user can keep an old page open or send requests directly. Expiration must be implemented in the data model and backend services.

Rigi24 has a scheduled command for expiring Loyalty Benefits and updates the Entitlement status based on actual dates and rules. Point Expiration is also synchronized with the Ledger and Remaining Points.

A professional system must be able to explain what expired, when, and what effect it had on the balance.

11. Branch Scope; Multi-Branch Customer Loyalty Club

For multi-branch businesses, Loyalty without Branch Scope can cause problems. A campaign might be executed only in one branch, or a Reward might only be available at a specific branch due to inventory limitations. Conversely, some points should be shared across the entire brand.

Rigi24 Loyalty Branch Assignment allows control over the activation of the club and the validity of Benefits across different branches. When redeeming a Reward in a Restaurant, Branch Compatibility is also checked.

When choosing Loyalty software, be sure to ask: Is the branch just a display field, or is it truly used in Validation? The difference between the two is very important in daily operations.

12. Digital Card and Secure QR

A digital card is excellent for fast customer experience, but its token should not be guessable or permanent without control. The software must be able to issue tokens, have proper hashing or encryption, rotate the card, and revoke it if needed.

Rigi24 Loyalty Card Service is designed for this exact cycle. The customer card can have a QR code, but security should not be sacrificed for convenience. If the customer’s QR image is published in an inappropriate place, it must be possible to rotate or revoke it.

For the business, this system must also be fast. The employee should not spend several minutes identifying each customer. QR is valuable because it reduces interaction time.

13. Discount Calculation Must Be Done in the Backend

One of the most dangerous mistakes is trusting the amount sent by the Frontend. If the browser says the Reward should give a 50 Lari discount, the server should not accept that exact figure without calculation.

In Rigi24, Reward Discount calculation is done in the Backend. The server checks the Discount type, amount, Base Amount, Currency, Branch, and Entitlement status, and then constructs the authorized amount itself. The Frontend only sends the user’s selection.

This principle is important for any financial software: the user interface is not trustworthy; the Source of Truth must be the Backend.

14. Preview and Final Amount Must Be the Same

A bad experience happens when the customer sees one amount on the Preview page and a different amount is calculated at final registration. Therefore, Preview must use the same Trusted Backend logic that the final Bill uses.

In the Rigi24 Restaurant integration, the calculation order is explicitly designed as follows: Subtotal, then Tier Discount, followed by Reward Base and Reward Discount, then Service Charge and Tax. The Preview result is compared with the Snapshot of the final Bill.

These details appear simple but if the calculation order is not clear, a difference of a few Lari on real orders quickly becomes a support issue.

15. Reservation Before Final Consumption

During the Restaurant flow, a Reward should not be marked as immediately Used upon selection. Instead, the Benefit is Reserved as active on the Bill so the customer cannot select the same Entitlement on another active Bill. Final consumption is done Atomically upon payment completion. If the Bill is Cancelled before completion, the Reservation is released.

This model is more suitable for real commerce than immediate consumption. The customer might change the Payment Method, the Bill might be cancelled, or the operator might fix a mistake.

In the future, when a Benefit is consumed directly across multiple channels, the same concept must also be applied Cross-Channel so the Reward is not reserved simultaneously in two Checkouts.

16. Reporting and Analytics; Loyalty Is Incomplete Without Measurement

Shopify emphasizes in its Loyalty Analytics guide that without appropriate metrics, it's impossible to understand what truly drives ROI. A system should at least provide the ability to extract and analyze Members, Points Earned, Redeemed, Reward Usage, Expiration, and Tier.

Having just the member count is not enough. Redeem rate, number of active members, Average Spend, Repeat Visits, and Tier comparisons are more important. If a specific Reward has been issued a thousand times but redeemed only five times, the reason should be investigated. Maybe the reward is not attractive, perhaps the rules are unclear, or maybe the points required for the Reward are excessively high.

17. Marketing Consent and Privacy

Joining a loyalty club does not mean automatic consent to receive all types of promotional messages. Consent must be separate and manageable. If the business operates in Georgia or other markets, it must comply with local data protection and marketing laws.

A good system should keep Marketing Consent independent of Membership. A customer can be a Loyalty member but opt out of receiving promotional messages. This distinction is important both for customer trust and Compliance.

18. Multilingual Support

In a market like Georgia, businesses may interact simultaneously with Georgian, English, Russian, Persian, Turkish, Arabic, Armenian, or Azeri-speaking customers. If cards, Rewards, or messages are limited to just one language, the experience becomes incomplete.

Rigi24 has a generally multilingual architecture, and interface sections are developed in multiple languages. For Loyalty, contextual upsell texts and restaurant-related parts are designed in multiple languages.

When choosing software, don’t just consider the number of languages; the quality of RTL support for Persian and Arabic, text length handling, and mobile experience are also important.

19. Mobile-Friendly and PWA

A loyalty club is not something only the manager behind a computer uses. Customers may show their card on a phone, and staff may verify it on a mobile or tablet. Therefore, responsive design is crucial.

Rigi24 provides a Web/PWA environment aiming to ensure that core operations are accessible without installing traditional software on every device. For Loyalty, the digital card and QR code must be readable and fast even on small screens.

20. Integration with Restaurant; A Practical Example of a Real Loyalty

A restaurant is one of the best examples to test the quality of a Loyalty Engine because it involves the customer, branch, order, discount, and payment. At Rigi24, a real flow has been tested up to the completed bill.

The scenario involved a member customer, Tier, percentage Reward, Benefit selection, preview of amount, bill registration, acknowledgment, presentation, and completion. Upon completion, the entitlement is used, usage recorded, order settled, and new points created based on the paid amount.

This scenario shows that Loyalty is not just an admin page; it must behave correctly in real transactions.

21. Contextual Upsell; When Loyalty Is Not Yet Active

Not all businesses adopt a loyalty club from day one. If the platform is modular, it is better that Loyalty is offered when a relevant context exists, not with annoying popups.

In Rigi24, Contextual Upsell is designed for sections such as Restaurant, Store, CRM, Customer Profile, Booking, Invoice, and Dashboard. When Loyalty is active, the offer is hidden, and when it is not active, the benefit of the club is explained at a relevant point.

This approach is better than random advertising because the manager sees the offer exactly where its connection to daily work is understandable.

22. Plan and Capacity; the software must be scalable

A customer club may start with 50 members and grow to several thousand. The software must seriously consider capacity, Branch Limit, and Plan Snapshot from the beginning. If everything is designed without limits, pricing and service control become difficult later.

In Rigi24 Loyalty, plans are defined based on Active Loyalty Customers and the number of branches. The contract keeps the Snapshot Plan at the time of creation so that later changes in the catalog do not unintentionally alter the previous contract.

This design is more important than a UI feature; it is the basis of stable SaaS.

23. Real trial before purchase

The best way to evaluate Loyalty software is not by looking at screenshots. The scenario should be executed: create a member, give points, define a Reward, redeem it, check expiration, and if you have a Restaurant, test a real payment flow.

Rigi24 offers a standard 15-day trial for paid modules, which can be extended up to a total of 30 days with managerial approval. Before the trial, it is better to define success criteria: how many real customers? how many Rewards? when do you review?

An exclusive article about Trial in Rigi24 explains how to turn this period into a real test, not just a menu walkthrough.

24. Security and Idempotency; an invisible but critical feature

The end user may never hear the word idempotency. But when the internet is weak or a button is pressed twice, this principle determines whether a Reward is consumed once or twice.

In Loyalty and Billing, Event Key, Usage Key, and Client Request ID are used to prevent unwanted repetition. Transaction and Lock help control concurrency at sensitive points.

If you seriously choose loyalty club software, don’t ask the vendor only about the panel appearance. Ask how Retry, Double Submit, and Concurrency are controlled.

25. Data Retention; the end of trial should not mean immediate data deletion

When the Trial or Subscription ends, shutting off access is not the same as deleting data. Professional SaaS must have a clear retention policy. The business may renew a few days later and all history should not be lost.

In Rigi24 Module Entitlement, Grace, Expiry, and Reactivation are not separate from the Core Commercial Flow. This causes Loyalty to follow the same standard business logic as other modules.

26. UX is more important for employees than the Feature List

A system may have 50 features, but if the cashier has to go through five pages to find a customer, Loyalty is practically not used. Daily operations must be short: identify the customer, see the status, select a valid Reward, and continue the main flow.

In the Restaurant UI, the Reward Selector only shows valid benefits; expired, cancelled, reserved, or branch-incompatible items are hidden. This is better than showing the user ten Rewards and then encountering an error after selection.

Frontend should hide Backend Complexity, not transfer it to the operator.

27. What should be checked before buying customer club software?

Before deciding, write a real scenario. For example: a customer enters the second branch, shows their QR code, has 320 points, receives a 100-point Reward, then pays an order of 87 Lari. Now, review the questions one by one: Does the system find the customer quickly? Is the Reward valid for the branch? Are points accurately deducted? What if the payment is canceled? What if the user submits twice? Can the Manager see the history?

This scenario is more valuable than a hundred features in a brochure because it shows whether the product really works in operation or not.

28. For which businesses is Rigi24 Loyalty suitable?

Rigi24 Loyalty is designed for businesses that have Customer Identity and repeat relationships and want to manage points, Tiers, and Rewards in a modular environment. Restaurants, cafes, stores, salons, service complexes, clinics, educational centers, and multi-branch businesses are natural examples.

If you only want a phone number list, Loyalty may be more than you need and the Core Customer Directory might be sufficient. If your main need is Follow-up and Task management, CRM has higher priority. If the main issue is retention and Reward, Loyalty is a more suitable tool.

This distinction is one of the advantages of the Modular model: you do not have to buy features that do not solve your problem.

29. Good software should allow the business to make changes

No Loyalty Program is perfect from day one. You may find after two months that a Reward is unpopular or the Tier Threshold is set too high. The software must allow program modifications but should not corrupt past History.

That is why Snapshot, Ledger, and Audit are important. You must be able to change tomorrow’s program and still know what happened yesterday.

30. The future of Loyalty is not just points

The market is moving towards Personalization and Omnichannel. McKinsey emphasizes in its research the combination of Loyalty Data, Pricing, and Personalization. However, this stage is valuable only if the foundations are correct. If Customer Identity, Consent, Ledger, and Reward Usage are inaccurate, AI or Personalization only accelerates mistakes.

For Rigi24, the logical path is the same: first a reliable Engine, then deeper Integrations and smarter features.

Summary

Good customer club software should not be chosen only by the appearance of the Dashboard or the number of Reward types. The real core is operational accuracy: correct Membership, auditable Ledger, FIFO, logical Tier, flexible Reward, Entitlement, Expiration, Reversal, Branch Scope, secure QR, server-side calculation, atomic consumption, and understandable reporting.

Rigi24 Loyalty is designed with this perspective. The goal is not just for the business to have a “digital point card”; the goal is to build an infrastructure that can grow in real operations and be placed alongside other modules on a shared Customer Identity.

If you still have questions about the core concept of Loyalty and why a business needs it, first read the article “What is a customer club and why does every business need it?” If you are ready to evaluate the product, run a real trial with your everyday business scenario and don’t just look at the Feature List.

Frequently Asked Questions

What is the most important feature of customer loyalty software?

A single feature is not enough. Correct customer identity, Points Ledger, controllable Rewards, and recording actual consumption are the four main pillars. Without these, reports and discounts are not reliable.

Is having a QR code necessary?

It is not absolutely necessary, but it is very useful for quick customer identification and digital cards. The token must be secure and able to be revoked or rotated.

Should Rewards only be discounts?

No. Gifts, Free Services, and Store Credit are often more attractive than general discounts in many businesses and more financially optimized.

What is the difference with a multi-branch system?

It should be able to control Loyalty and Reward credits across different branches and not rely solely on branch names in reports.

Why is the Ledger important?

The Ledger specifies where each point came from, where it was consumed, and what the balance was after each event. Without a Ledger, investigating discrepancies and auditing is difficult.

Should expiration be automatic?

Yes, if you have an expiration policy, the control must be server-side and scheduled, not just reliant on browser display.

Can Loyalty be used without CRM?

Yes. Loyalty and CRM are separate modules. However, using a shared Customer Identity ensures that if both are enabled, data is not scattered.

What is the best way to test the software?

Run a real scenario with Customer, Point, Reward, Redeem, Cancel, and Payment and then check the Database and UI results. The trial must simulate actual operations.

Suggested External Resources

Shopify — How To Create a Rewards Program That Drives Revenue: https://www.shopify.com/blog/create-rewards-program
Shopify — Customer Loyalty Analytics: https://www.shopify.com/blog/loyalty-analytics
McKinsey — Delivering greater value through loyalty and pricing: https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/members-only-delivering-greater-value-through-loyalty-and-pricing
McKinsey — Personalizing the customer experience: https://www.mckinsey.com/industries/retail/our-insights/personalizing-the-customer-experience-driving-differentiation-in-retail/