A restaurant should allow households to share loyalty rewards only if it can explain who may use the balance, verify that person at redemption, and give staff a workable way to handle disputes. If your software cannot support those rules, individual accounts are usually the safer starting point.
Sharing can be convenient when several people place orders for the same household. It also means one person may spend rewards another person expected to use. Decide whether that tradeoff fits your guests and your service style before promising a shared balance.
Choose an account rule your staff can enforce
Start with the guest experience you want. An individual account gives each guest a separate balance and makes ownership relatively straightforward. The downside is that household members may earn rewards slowly across several accounts.
A shared account pools eligible earning and allows authorized people to use the same balance. That can make a reward available sooner, but the restaurant needs a way to distinguish an authorized member from someone who merely knows the account phone number.
A third option is to keep individual balances and offer a household benefit that does not require shared access, such as an eligible family offer. Ask whether your system can run the offer you have in mind and what conditions apply. Do not describe a promotion as a shared points account if guests cannot actually pool and redeem points.
Use the worksheet below to choose a starting rule. The best option depends on what the vendor can support and what your team can verify during a busy shift.
| Option | Guest benefit | Operating question | Starting decision |
|---|---|---|---|
| Individual balances | Each person controls their own rewards. | Can staff find the right account without exposing another guest's details? | Use when shared permissions cannot be verified reliably. |
| One shared balance | Authorized members can earn toward and use a common reward. | Can the system identify members and record who redeemed? | Consider when access, limits, and dispute handling are workable. |
| Individual balances plus a household offer | A qualifying group can receive an offer without pooling points. | Can the offer be applied consistently across the intended order channels? | Consider when a simple family benefit matters more than shared points. |
Write down the decision as a policy, not just a software setting. Define who can join, whether membership is limited, who can add or remove members, and whether every member can redeem. If the system only offers a single login shared among several people, decide whether that is acceptable; it may make later disputes harder to resolve.
Follow a shared balance from earning to redemption
Hypothetical example: A restaurant considers a shared account for two authorized adults, Ana and Ben. Its proposed rule awards one point per dollar of eligible food purchases, and 100 points can be redeemed for one $5 food discount. The discount is available only when the balance reaches 100 points and the order meets the restaurant's stated conditions.
Ana makes an eligible $60 purchase and earns 60 points. Ben later makes an eligible $40 purchase and earns 40 points. The shared account now has 100 points. Ben redeems them for a $5 discount on an eligible order, leaving zero points. Ana cannot also redeem those same points, even though she earned more than half of them.
Before the balance reached 100 points, the 60 points from Ana's purchase had a proportional reward equivalent of $3 under this example's rate. That did not mean Ana could redeem $3: the proposed rule required 100 points for the $5 discount. Make that distinction clear wherever guests see their balance.
For a simple cost check, the example includes the $5 face value of the redeemed discount. It excludes fixed software costs, payment processing, other variable order costs, and exception costs such as staff time or a replacement reward after a dispute. It is not an all-in operating cost or a forecast of what guests will redeem. Use your own quote and expected activity to assess the broader cost; the loyalty reward cost guide can help frame that calculation.
Now change the circumstances. What if Ana returns part of her purchase before Ben redeems? What if Ben redeems while Ana is placing another order? Ask the vendor how returns, adjustments, and simultaneous attempts affect the balance. Your terms should explain the result guests can expect, and staff should know whom to contact if the recorded balance does not match it.
Set access and dispute rules before launch
Choose a verification method that fits the risk and the pace of service. Ask the vendor whether each authorized member can have a distinct credential or whether the account relies on one shared login. Knowing a phone number or seeing a receipt should not automatically prove that someone may spend the household's rewards.
Keep contact access separate from marketing permission. A person authorized to redeem a reward has not necessarily agreed to receive promotional messages, and a household member should not automatically gain access to everyone else's contact details. Ask what each role can view or change, including phone numbers, email addresses, membership, and message preferences.
Give staff a short dispute path. For example, if Ana says she did not authorize Ben's redemption, the employee should avoid promising an immediate reversal or revealing Ben's personal information. Instead, record the account reference, date, amount, and the guest's explanation; check the available transaction history; and send the case to the designated manager. The manager can apply the restaurant's written policy on corrections or goodwill credits.
Decide in advance what happens when a member leaves a household, a credential is lost, or two members disagree about a balance. A shared account may treat all authorized redemptions as valid even if members later disagree. Say so plainly if that is your rule, and provide a route for reporting suspected unauthorized access.
Limit the information collected for a dispute to what your team needs to investigate. Set a response owner and a target for follow-up so the guest is not left repeating the story to each shift. Have a qualified adviser review contract or privacy questions where needed.
Ask vendors to demonstrate the workflow
Describe your intended policy before asking for a feature list. Show the vendor the two-person example and ask them to demonstrate enrollment, earning, redemption, member removal, and an adjustment. If a step requires staff to use a workaround, write down who performs it and how long the team expects it to take.
- Permissions: Can members have separate credentials? Who can add members, change contact details, redeem, or remove access? Is there a limit on members?
- Transaction history: Can a manager see the earning and redemption events needed to investigate a complaint? Can the history identify the person or credential used, and what can frontline staff see?
- Order coverage: Which order channels qualify for points and redemption? How are canceled orders, partial returns, and simultaneous redemption attempts handled?
- Guest terms: Where can guests see eligibility, reward thresholds, expiration rules, and the effect of sharing? Can the restaurant update those terms without confusing existing members?
- Data and messages: Can the restaurant manage each person's contact preferences separately, control campaign sends, segment guests appropriately, and export the records it needs?
- Costs and support: What are the quoted recurring and setup charges, transaction-related costs, and charges for changes or support? Which dispute tasks remain with restaurant staff?
Fleksa describes loyalty points for eligible orders alongside email and SMS campaigns, segmentation, promo codes, and gift cards in its restaurant marketing automation offering. Ask specifically whether the shared permissions and account history you need are available for your setup. Also check how the proposed rules would work with your restaurant ordering system and the rest of your restaurant management software.
Record a practical acceptance test
Before a live rollout, run a simulated check with vendor-approved test accounts and test data. Do not use a real card payment, send a guest message, or dispatch a courier. Confirm with the vendor how to prevent those actions before starting.
- Create a test household with two distinct authorized members, if the proposed setup supports them. Record how each person is verified and what contact information each can see.
- Simulate eligible purchases that should reach the chosen reward threshold. Check that the displayed balance and available reward match the written rule.
- Simulate one member redeeming the reward. Confirm the remaining balance and check that a second redemption cannot use the same points.
- Remove one member's access, then attempt a simulated redemption with that member's test credential. The attempt should be denied under the proposed policy.
- Present a disputed redemption to a manager. Check whether the available history supports the agreed investigation without exposing unnecessary contact details.
Record the expected result, actual result, staff action, and any unresolved question for each step. Accept a shared-account policy only when the demonstrated behavior matches the policy you intend to publish. If a necessary control fails, choose individual balances or revise the policy rather than asking staff to promise something the system cannot enforce.
A live service pilot is a separate decision. If the simulation passes, consider a limited rollout with trained staff, clear guest terms, and a manager assigned to review issues. Monitor real activity under your normal operating controls; a simulation alone does not prove the workflow will fit a busy service.
Next step: Write your household access and dispute rules on one page, then compare your marketing requirements with Fleksa's available workflows before choosing a rollout.
Frequently asked questions
Can two people use one restaurant loyalty account?
That depends on the restaurant's rules and the software's permissions. Define who may join and redeem, then confirm that staff can verify access and review relevant transactions.
Who owns points in a shared household balance?
The restaurant should explain how its program treats the balance and what happens when a member leaves or disputes a redemption. Do not assume every household member expects the same arrangement.
Should staff restore points after a disputed redemption?
Not automatically. Staff should record the complaint and refer it to the person authorized to review the history and apply the restaurant's correction or goodwill policy.
