Skip to article
← Back to Blog
Marketing

Visit-Based vs. Spend-Based Restaurant Loyalty: Which Should You Choose?

By Fleksa8 min read•restaurant loyalty, loyalty programs, restaurant marketing

Should a regular earning one stamp per visit get the same reward as a guest placing a large order? Compare both loyalty models with a worked worksheet and practical checks for returns, channels and staff.

Choose visit-based loyalty when your main goal is to bring guests back more often and your typical orders are reasonably similar in size. Choose spend-based loyalty when order values vary widely and you want earning to reflect eligible dollars. Neither model is automatically fairer: each rewards a different behavior.

Before choosing software, write down what counts as a visit, what spending earns points, and what happens when an order is changed or refunded. Then run a few guest patterns through both models. The results can reveal whether your rules reward the guests and behaviors you actually want to encourage.

Define a qualifying visit and eligible spend

A visit-based program gives a guest credit for a qualifying transaction or visit, usually as a stamp or point. After a set number of credits, the guest earns a reward. A coffee shop might prefer this approach if its priority is turning occasional morning customers into regulars.

The word visit needs a precise definition. Is it one paid order, one guest party, or one transaction per customer per day? If a party of four pays on one check, decide whether one identified account earns credit or each person can earn it. If one guest splits an order into two transactions, decide whether both count. A clear rule prevents the counter team from having to settle these questions during a rush.

A minimum purchase can keep a very small transaction from earning the same credit as a typical meal. Set it with actual ordering patterns in mind: a threshold above the price of your common solo order may exclude the very guests you want to bring back. Also decide whether pickup and delivery orders qualify and whether an unpaid, canceled or refunded order loses its credit.

A spend-based program awards points according to eligible dollars. That can be useful for a restaurant with a wide range of order sizes, from a single lunch to a family dinner. Define the earning rate and what counts toward it. For example, you might choose to count menu items after discounts while excluding tips and delivery charges. Those are design choices, not universal rules.

Be specific about rounding. If a guest earns one point for every $10, does an $18 order earn one point with the remaining $8 carried forward, or is the remainder discarded? Does a partial refund reduce the point balance? A rule that sounds simple on a sign can produce surprising results when orders are small or frequently adjusted.

Keep earning separate from redemption. Earning determines how quickly guests make progress; redemption determines what they receive and what it costs the restaurant. Compare those reward costs separately before launching either model.

Run three guest patterns through a decision worksheet

The following example is hypothetical. Assume every order is paid and qualifies, with no discounts, refunds, tips or delivery charges included in the amounts shown. Under the visit model, each qualifying order earns one point. Under the spend model, each $10 of cumulative eligible spending earns one point, with any remainder carried forward. In either model, six points earn one reward; any points left after a reward remain available.

The table compares earning progress, not the cost of the reward. It uses three guests over the same period and assumes each order represents one qualifying visit.

Guest patternOrders and eligible spendVisit pointsSpend points
Frequent solo guest6 orders totaling $6066
Occasional family guest3 orders totaling $9039
One larger order1 order totaling $5015
Total10 orders totaling $2001020

The frequent solo guest reaches one reward under either model. The family guest has only three visit points but reaches one reward under the spend model, with three points left. The guest with one larger order has not reached a reward under either model, but is much closer under spend-based earning.

If the restaurant wants more frequent orders, the visit model gives a clearer reason to return: the family guest needs three more qualifying visits rather than merely more eligible spending. If it wants earning to track order value, the spend model is more consistent. In this sample, the $90 family guest earns more than the $60 solo guest under the spend model, but less under the visit model.

The totals also matter for planning. Ten visit points represent one reward reached across these accounts, with four points remaining. Twenty spend points represent two rewards reached, with eight points remaining. That does not mean two rewards have been redeemed, and it does not tell you their cost. The guests may redeem later, never redeem, or earn additional points first.

To use this worksheet for your own decision, replace the three patterns with common order types from your restaurant. Include a small frequent order, a typical order and a larger order. Apply your proposed minimum, earning rate and rounding rule to each transaction. Count both rewards reached and points remaining, then decide whether the resulting progress matches your goal.

Compare fairness, incentives and the counter explanation

Fairness depends on what the program promises to recognize. A frequent guest may appreciate a visit model because showing up often matters, even when each order is modest. A guest buying for a family may prefer a spend model because a larger purchase earns more. Both views are reasonable. Decide which behavior matters more to your restaurant rather than trying to make every pattern produce the same result.

Look for incentives you did not intend. A visit rule with no minimum could encourage guests to split purchases. A high minimum could discourage a guest who normally buys one inexpensive item. Spend-based earning can make progress feel slow on small orders, especially if unused amounts are discarded rather than carried forward. It can also make a large one-time purchase earn much more progress than repeated small visits.

Test the explanation you would put on a counter card. A visit rule might read: “Earn one point per qualifying paid order of at least $10.” A spend rule might read: “Earn one point for every $10 in eligible menu purchases; remaining eligible dollars carry forward.” Each still needs accessible details about exclusions and adjustments, but a guest should understand the basic promise without a staff member doing a long calculation.

Give staff a short reference with the earning rule, minimum or exclusions, reward threshold, and the procedure for a missing or disputed credit. Include examples of a split check and a partial refund. Decide who can correct a balance and how that correction is recorded. If the answer requires a manager every time, factor that workload into your choice.

For a broader view of how loyalty fits alongside campaigns and customer data, see the related buying guide. Keep your immediate decision narrower: which earning rule will guests understand and your team apply consistently?

Check adjustments, identification and vendor limits

Once you have a preferred model, ask a vendor to show the exact workflow rather than relying on the label “loyalty.” A points program may not support the qualification, rounding or adjustment rules you want. Write down which rules are essential and which you could change without confusing guests.

  • Returns and changes: What happens to earned credit after a full refund, partial refund or canceled order? What happens if the guest has already used the points? Can staff see the adjustment and correct an error?
  • Guest identification: How does a guest identify the same account at the counter and when ordering directly online? What happens if the guest forgets their details or creates a second account? Can an authorized employee resolve duplicates?
  • Channel eligibility: Which order channels can earn and redeem under the proposed setup? If a channel does not qualify, how will you explain that before the guest orders?
  • Rule controls: Can you set a minimum, exclude selected charges, carry spending remainders and limit multiple credits in a day? Ask the vendor to demonstrate each rule you need.
  • Reporting and access: Can you see points earned, adjusted, redeemed and outstanding? Can you export the data you need, and what happens to account balances if you leave the service?
  • Messages and consent: Can guests check their balance without receiving promotional messages? How are marketing permissions recorded and controlled? Having contact details is not the same as having permission to market.

Fleksa describes loyalty points for eligible orders and offers restaurant marketing automation, including email and SMS campaigns. Ask which earning rules and order channels fit your setup. Its loyalty documentation and marketing loyalty FAQ are useful starting points for that conversation.

For a demonstration, use simulated accounts and orders to check a normal purchase, a split purchase and a partial refund. Confirm that practice transactions will not charge a real card, send a guest message or dispatch a courier. A simulation checks the configured rules; it does not show how the process works during a busy service.

If the simulation meets your requirements, consider a limited live service pilot with staff trained on the actual workflow. Explain the offer to participating guests, monitor disputed credits and record questions employees cannot answer quickly. Use real transactions only as part of that deliberately chosen live pilot, not as practice scenarios.

Next, choose your three representative order patterns, calculate progress under both models, and mark the rule changes you cannot compromise on. Compare your requirements with Fleksa and ask for a demonstration of the relevant workflow.

Frequently asked questions

Is visit-based loyalty better for a coffee shop?

It can be a good fit when the goal is more frequent visits and most orders have similar values. Check that the minimum purchase does not exclude a common single-item order.

Should tips and delivery charges earn loyalty points?

That is a program design decision. Define eligible spending explicitly, then ask whether the software can apply your chosen exclusions and show guests how points were calculated.

Can a restaurant use both earning models?

A combined approach is possible in principle, but it adds rules for guests and staff to understand. Ask vendors whether they support the exact combination you want, and calculate the resulting progress before adopting it.

Ready to grow your restaurant?

Explore how Fleksa can support ordering and operations in your restaurant.