To calculate a restaurant loyalty reward threshold, divide the points needed for a reward by the points earned per eligible dollar. Then divide that spending target by a typical eligible purchase and round up to a whole purchase. That gives you an estimate of how many purchases unlock the reward.
The estimate changes with check size, and real guests rarely spend the same amount every time. Before choosing a threshold, calculate it for small, large, and mixed purchases. Then check what the reward costs and whether your software applies points the way you expect.
Choose an earning rate and reward target
Start with three decisions: what counts as an eligible purchase, how points are earned, and how many points unlock one reward. Keep the first version simple enough to explain on a receipt or ordering screen.
For the hypothetical example throughout this guide, assume guests earn one point for every eligible dollar spent. A $5 reward becomes available at 100 points. We will also compare a 150-point threshold for the same reward. Assume points carry forward after redemption, purchases earn whole points, and the guest can use the reward on a later order.
Under those assumptions, the 100-point reward requires $100 in eligible spending. The 150-point reward requires $150. Those are spending targets, not necessarily the amounts a guest pays out of pocket. Decide whether tips, delivery charges, discounted items, gift card purchases, and other amounts earn points. The calculation only uses the portion your rules count.
For example, if an order totals $18 but only $15 qualifies, use $15 to estimate points. Do not build your threshold around the full check average unless the full check is eligible.
Also decide how fractional dollars work. Does the system award fractional points, round each purchase, or count only whole eligible dollars? A guest making many small purchases could reach a target later than expected if fractions are dropped on every order. Ask the vendor to show the actual calculation before you publish a promise.
Calculate purchases for different check sizes
With one point per eligible dollar, divide the threshold by the eligible dollars per purchase. Round up because a guest cannot complete part of a purchase just to satisfy the formula. The table shows what happens at both thresholds under the hypothetical rules above.
| Eligible purchases | 100-point reward | 150-point reward | What changes |
|---|---|---|---|
| $12 each | 9 purchases; $108 eligible spend | 13 purchases; $156 eligible spend | Four more purchases at the higher target |
| $25 each | 4 purchases; $100 eligible spend | 6 purchases; $150 eligible spend | Two more purchases at the higher target |
| Alternating $12 and $25, starting at $12 | 6 purchases; $111 eligible spend | 9 purchases; $160 eligible spend | Three more purchases at the higher target |
The mixed-purchase row is especially useful if a guest buys a small lunch on one visit and a larger family order on another. The first six purchases total $111, so the guest crosses 100 points on purchase six. After nine purchases, the total is $160, crossing 150 points. These are eligible purchase totals, not a prediction of a particular guest’s behavior.
Notice the overshoot. A guest spending $12 each time reaches the 100-point threshold with 108 points. If the reward uses 100 points and the remaining eight carry forward, the guest starts toward the next reward with eight points. If your system handles the balance differently, the next cycle will look different. Ask whether points are deducted when a reward is issued or when it is redeemed, and what happens to the remainder.
Purchase count is not always visit count. One party might place several eligible orders on one visit, or one order might cover several people. Use the unit your program actually tracks. If you want to say “earn a reward after about nine purchases,” check that the purchase size behind that statement is typical of the guests you want to reach.
Compare the threshold with reward cost
The lower threshold gives the hypothetical $12 guest access to a reward after nine purchases rather than 13. That is a meaningful difference in waiting time. But faster access also means a reward can be earned on less eligible spending.
Assume the restaurant’s incremental cost to provide one $5 reward is $2. This is a made-up cost assumption, not the face value of the reward or a vendor price. At the 100-point target, $2 divided by $100 is 2% of the threshold spending. At 150 points, $2 divided by $150 is about 1.33%.
Those percentages are reward-cost equivalents at the exact thresholds. They are not rewards a guest can redeem as cash, and they do not describe the full operating cost of the program. The example includes the assumed $2 variable cost per reward. It excludes fixed program or software costs, payment fees, marketing costs, and exception costs such as manual adjustments or disputed balances. Actual guest spending may also overshoot a threshold, as the table shows.
For this example, choose 100 points if the restaurant can accept the stated reward cost and wants a $12 guest to reach a reward in roughly nine eligible purchases. Choose 150 only if the lower reward-cost equivalent matters more than the extra wait. Neither choice proves that guests will return or redeem a reward.
Before committing, replace the $2 assumption with the cost of the reward you intend to offer. A discount on an order and a free menu item can have different costs and conditions. Consider whether a minimum purchase is required and how that affects the guest’s understanding. The reward cost guide covers that separate decision in more detail.
Also compare the complete operating quote, not just a processing fee or the cost of one reward. Ask which software, messaging, setup, and payment charges apply to your intended workflow. A low reward-cost equivalent alone does not make a program inexpensive to run.
Make the rules clear to guests
A useful guest explanation starts with the earning action and ends with the reward. For the hypothetical 100-point option, a plain-language draft is: “Earn one point for each eligible dollar. Get a $5 reward at 100 points.” Add the actual exclusions and redemption conditions wherever guests enroll or check their balance.
Be careful with a headline such as “Get $5 after four orders.” That is true in the example only for four $25 eligible purchases. Someone ordering $12 at a time needs nine purchases. A spending-based message is more accurate when order sizes vary.
Explain when points appear and what happens if an order is canceled or refunded. Tell guests whether a reward is applied automatically or must be selected, whether unused points carry forward, and where they can see their balance. If a guest must enroll before earning, say so before the first purchase rather than after it.
Keep eligibility rules consistent across staff training and guest-facing copy. If the program works differently for counter and online orders, name the participating channels. The loyalty documentation is a useful starting point for reviewing the workflow; confirm the settings available for your own setup.
Check the workflow before choosing a vendor
Give each vendor the same earning rate, threshold, reward, and purchase sequence. Ask them to demonstrate how the balance changes at every step. Focus on the ordinary path first, then ask about exceptions.
- Earning: Which order channels qualify? Can you exclude charges or discounted amounts? How are fractional points rounded?
- Thresholds: Can you set the target you want? Do extra points carry forward, and can a guest hold more than one available reward?
- Redemption: Is a reward issued at the threshold or selected later? Can staff see and explain the balance when a guest asks?
- Corrections: What happens after a cancellation, refund, duplicate order, or mistaken adjustment? Who can change a balance?
- Reporting and outreach: Can you see earned and redeemed rewards, export the information you need, and control which eligible guests receive a message?
Access to a guest’s contact details is separate from permission to send marketing. Ask how your team records and uses the guest’s communication preferences. If you plan to remind guests about rewards, review the available controls for campaigns alongside the loyalty workflow.
First, run a simulated sequence with test data. Check the calculated balance after each purchase, including an overshoot and a reversal. The simulation should not charge a real card, send a guest message, or dispatch a courier. If you later conduct a live service pilot, define its scope and staff responsibilities separately; actual orders and communications require normal operational controls.
Next step: Write down your eligible spending rules, reward cost assumption, and two candidate thresholds. Use a small and a large purchase sequence to check each one, then compare the relevant workflow and current availability with Fleksa’s restaurant marketing tools.
Frequently asked questions
How do I calculate purchases needed for a reward?
Divide the reward threshold by the points earned per eligible purchase, then round up to a whole purchase. If purchase sizes vary, add their points in sequence until the balance reaches the threshold.
Should I use a lower or higher points threshold?
A lower threshold generally makes the reward available sooner; a higher one requires more eligible spending. Compare the wait for your typical guests with the assumed cost of providing the reward and your other operating costs.
Does every dollar on an order earn loyalty points?
That depends on your program rules and software setup. Specify which amounts qualify, including how discounts and additional charges are treated, and confirm how the system calculates points.
