To separate new enrollment from repeat loyalty activity, report three things for the same month: members who joined, distinct members who placed an eligible order, and transactions placed by those active members. Then divide active members into those who joined during the month and those who joined earlier.
That split tells an owner whether a growing list is bringing in active guests or whether existing members are coming back. It also prevents a busy regular with several orders from looking like several different guests.
Decide what the monthly report needs to answer
Start with a decision, not a dashboard. If signups are healthy but few new members order, check whether staff explain the program clearly and whether guests understand how to use their membership. If returning activity is weak, examine the offer, ordering experience, and timing before adding another promotion.
Assign one person, such as the general manager, to own the monthly definitions and review. A shift lead can check whether staff mention the program at the right point in service. The person responsible for marketing can review any follow-up campaign and its send permissions. One owner should reconcile the final numbers so each shift is not using a different definition.
Service conditions matter. A counter-service restaurant with frequent short visits may need a quick signup process that does not slow the line. A restaurant with fewer visits may need a longer comparison period before treating a quiet month as a problem. Ask whether the report covers the order channels your guests actually use, and whether staff can identify members without adding friction at checkout.
Write down these definitions before comparing vendors:
- New enrollment: A distinct member account created during the month, whether or not that member orders.
- Active new member: A distinct member who joined during the month and placed at least one eligible order in that month.
- Returning active member: A distinct member who joined before the month and placed at least one eligible order during it.
- Repeat transactions: Eligible orders beyond the first eligible order per active member in that month. This is an order count, not a guest count.
Choose which completed orders qualify and how refunds, cancellations, and staff orders are handled. Apply the same rules across months. This report measures enrollment and activity, not reward redemption or the value of rewards guests can actually redeem.
Build a monthly worksheet that separates people from orders
The following figures are hypothetical. Eligible orders are completed member orders included under the restaurant’s chosen rules. Each active member is counted once, even if that person places multiple orders.
| Monthly measure | April | May | How to read it |
|---|---|---|---|
| New enrollments | 25 | 30 | Accounts created, including members with no eligible order |
| Active new members | 20 | 24 | New accounts with at least one eligible order |
| Returning active members | 12 | 18 | Earlier enrollees with at least one eligible order |
| Total active members | 32 | 42 | Active new plus returning active members |
| Eligible member orders | 45 | 60 | All qualifying orders from active members |
| Repeat transactions | 13 | 18 | Eligible orders minus total active members |
In April, five of the 25 new enrollees did not place an eligible order that month. The 32 active members placed 45 eligible orders, so 13 orders were beyond those members’ first orders. In May, six new enrollees had no eligible order, and 42 active members placed 60 eligible orders. The extra 18 orders do not tell you how many people ordered more than once: one person could account for several of them.
The owner’s decision in this example is to keep the signup process in place and examine what brought earlier members back: returning active membership rose from 12 to 18, alongside an increase in new enrollments. The manager should compare similar service periods and check for changes in hours, promotions, or channel coverage before crediting any one cause. If the question becomes how many individual members ordered twice or more, request that separate distinct-member count.
For the monthly workflow, the report owner exports or records enrollment and order data using the agreed date range. The shift lead flags service changes that could affect interpretation. The marketing owner checks campaign timing, then the report owner records the decision and compares the next month using the same rules.
Compare reporting approaches before buying
A vendor’s loyalty screen may show signups, points, or orders without providing the exact split above. Ask for a demonstration using your definitions, rather than assuming that a label such as “active members” means what you need.
- Built-in report: Ask whether it separates members by join date and counts distinct active people across your relevant order channels. This can reduce monthly staff work if the definitions fit. Check whether filters, locations, and historical periods are included in the quote.
- Export and worksheet: Ask for sample enrollment and order exports with a stable member identifier, order date, order status, and join date. A manager can then calculate the split, but someone must clean the data and protect access. Check export availability, format, and any associated charges.
- Manual tracking: Staff can maintain a small log where order volume is manageable, but duplicate entries and missed identifiers can distort the count. Consider the time needed each shift and whether asking guests to repeat information slows service.
For each approach, request an operational quote covering setup, recurring software charges, exports or reporting add-ons, and any other services needed for the workflow. Ask separately about payment processing charges if payments are part of the proposed setup; a processing quote alone is not the all-in operating cost. Staff time and exception handling may also matter even when they do not appear on the vendor’s invoice.
Fleksa describes restaurant marketing automation that includes campaigns, segmentation, and loyalty points for eligible orders. Ask which reports and exports are available for your setup and channels. For current plan details, consult Fleksa plans; pricing was checked in November 2026. Get a written quote for the configuration you are considering.
Run a distinct-member acceptance test
Use a sandbox or a clearly isolated sample dataset for the first check. A simulated order must not charge a card, send a guest message, or dispatch a courier. Ask the vendor to show the underlying sample records as well as the report output.
- Create a sample member who joined before the reporting month and has three eligible orders during it.
- Run the report for that month. The expected result is one returning active member, three eligible orders, and two repeat transactions attributable to that sample member.
- Add a sample member who joined during the month but has no eligible order. Expect one new enrollment, but no increase in active members or eligible orders.
- Add a newly joined sample member with one eligible order. Expect one new enrollment, one active new member, one eligible order, and no repeat transaction for that person.
Pass: The report or export supports those counts under the agreed rules, and the totals reconcile to the sample records. Fail: The three-order member appears as three active members, the inactive enrollee appears as active, or the output cannot distinguish new from earlier enrollees. Save the displayed filters, date range, report output, and sample records so the manager can repeat the check after setup changes.
Then test exceptions that could change a real month’s totals. What happens when an order is canceled or refunded? Can two accounts belonging to the same guest be merged, and how does that affect historical reports? Does an order without a member identifier stay out of the member count? Confirm the treatment you want and ask the vendor to show it; do not assume every system handles these cases alike.
If the vendor cannot produce the split, use an export-based worksheet if it contains the identifiers and dates needed. Assign one person to deduplicate accounts, apply order-status rules, and document corrections. If the necessary data is unavailable, a manual log may be the fallback, but treat its totals as incomplete when staff cannot consistently capture every qualifying order.
After simulation, a live service pilot is a separate decision. Agree on a short period, staff responsibilities, and how actual transactions will be handled. Review real operating results against the same definitions; do not use real guest contacts or payments merely to make the practice test work.
Turn the report into an operating decision
Review the worksheet alongside staffing and service notes. A rise in enrollment without a similar rise in active new members may prompt a clearer explanation at signup. A decline in returning active members may prompt a check of ordering friction or the relevance of an offer. Neither result alone proves why guests behaved a certain way.
If you use follow-up messages, distinguish having a member’s contact details from having permission to market to that person. Ask how the system handles audience selection, send controls, and reporting. Fleksa’s guides to loyalty and campaigns provide useful starting points for those conversations.
Bring your definitions and sample worksheet to a vendor conversation. Ask Fleksa to demonstrate the applicable reporting and export workflow, then compare the result and written quote with your current process.
Frequently asked questions
Is a new member automatically an active member?
No. Under this worksheet’s definition, a new member becomes active for the month only after placing at least one eligible order during that month.
Do repeat transactions show how many guests returned?
No. They count orders beyond each active member’s first eligible order in the month. Request a separate distinct-member count to learn how many people placed multiple orders.
What if a guest has two loyalty accounts?
The report may count two accounts unless the records are linked or corrected. Ask how duplicates are identified and whether merging accounts changes historical reports.
