When several guests pay one restaurant bill, the clearest loyalty rule is usually to award each member points on their own eligible payment. That makes the reward easier to explain and reduces the chance that one guest receives points for someone else’s spending. It only works well, though, if your system can identify each member and connect each payment to the right account.
Before buying loyalty software, decide what happens when that connection fails. A check-based award may be simpler at the register, while a manual allocation can handle exceptions. Both need clear controls. The right choice depends on your service flow, staff capacity, and what the vendor can demonstrate.
Set the rule before choosing the software
The owner or general manager should own the policy, with input from whoever trains servers and reconciles the POS. The decision affects more than the loyalty balance: it changes what staff must ask at checkout, what guests see, and who fixes an award when a payment or account is entered incorrectly.
Start by writing down what earns points. Is the eligible amount the food and drink subtotal, or another amount you define? What happens to a discount, a void, or a refunded item? Decide whether nonmembers’ payments earn anything and whether points are rounded for each payment or once for the entire check.
Keep payment and account identification separate. A card payment does not necessarily identify a loyalty member. Ask how a guest supplies an account, how staff match it to a payment, and what happens if two people use the same payment method. Also decide whether a guest can request a correction later and what proof staff need.
Document the rule in a short staff reference. For example: identify each member before closing the check, apply the agreed earning rule, and send disputes to the shift manager. The actual steps should match the product you buy. A rule that sounds fair but adds several screens to a busy checkout may not be practical.
Compare three allocation approaches
Points follow each payment
Under a payer-based rule, each member earns from their own eligible share. This is a good starting point when guests pay different amounts and can identify their accounts at checkout. It gives staff a straightforward explanation: your points follow your payment.
The tradeoff is that every payment needs a reliable account match. Rounding each share separately can also produce fewer total points than rounding the full check. If the software cannot assign different accounts to different payments, do not assume staff can achieve this result without an extra step.
Points follow the check
A check-based rule calculates one award for the eligible bill and gives it to the account selected for that check. Checkout may be simpler if the system handles only one loyalty account per check. But one guest can receive points on the other guest’s payment. That may be acceptable when the group chooses a recipient in advance; it is less suitable when each payer expects a personal reward.
Tell guests the rule before they pay, not after a dispute. Also decide who selects the recipient and whether the selection can be changed after the check closes.
Staff allocate the award
A manual rule lets an authorized employee distribute points according to your policy. It can address an unusual split or repair a missed account, but it adds work and creates room for inconsistent decisions. Set limits on who can make changes, what they must record, and whether a manager must approve an adjustment.
Manual allocation is a poor default if staff cannot see the original award or if corrections have no history. It is more useful as a controlled exception when the normal checkout flow misses an account or a refund changes the eligible amount.
Use a split-payment worksheet
The following numbers are hypothetical. Two loyalty members share one check with $50.00 in eligible spending. Member A pays $31.75 and Member B pays $18.25. Assume the restaurant’s policy awards one point per eligible dollar, with no bonus or redemption on this check. The eligible amount excludes tips, discounts, taxes, fees, and any other items outside the policy; none are included in these figures.
For the payer-based method, round each payment down to whole points. For the check-based method, round the full check down and award it to Member A. For the manual method, first calculate the 50-point check total, then allocate whole points in proportion to payment: round each initial share down and give the remaining point to the member with the larger fractional remainder. These are sample rules to test, not claims about any product’s settings.
| Method | Member A | Member B | Expected result |
|---|---|---|---|
| Payer-based | 31 points | 18 points | 49 points total; each payment is rounded down separately. |
| Check-based | 50 points | 0 points | 50 points total; A is the selected check recipient. |
| Manual allocation | 32 points | 18 points | 50 points total; A receives the remaining point because 0.75 is greater than 0.25. |
The one-point difference between payer-based and manual allocation comes from the rounding rule, not an extra payment. Check-based allocation produces the same total as manual allocation but gives the entire award to A. Choose which outcome you want before asking a vendor to reproduce it. Points are not necessarily a redeemable reward on their own; ask about the redemption threshold and eligible rewards separately.
Now consider a dispute in the same example: B says their account was not attached to their $18.25 payment. The server records the check reference, payment amounts, and the account B identifies, then asks the shift manager to review it. Under the payer-based rule, the expected final result is A with 31 points and B with 18.
The manager should first check whether B already received the points. If not, an authorized person can use the vendor’s supported correction process to add the missing 18, then record the reason and outcome. If the wrong account received those points, the correction also needs to remove the mistaken award where the system permits. Do not simply add points without checking the original transaction; that can leave a duplicate award.
For a refund or void, use the same discipline: determine the revised eligible amount, recalculate under the chosen rule, and record who made the adjustment. Ask the vendor whether an adjustment is automatic or requires staff action. A useful correction record includes the original check, the old and new balances or awards, the reason, and the employee responsible.
Run a vendor acceptance test
Give every vendor the same written scenario and expected results. Use a demonstration or test environment with simulated accounts and transactions. The practice must not trigger a real card payment, guest message, or courier dispatch. A simulated check is a software evaluation; it does not prove that a busy service team can use the workflow comfortably.
- Set up the rule. Ask the vendor to show how the eligible amount, point rate, account identification, and rounding are configured. Pass if the chosen policy can be represented and explained to staff. Fail if the result depends on a rule the vendor cannot show or if the required setting is unavailable.
- Enter the split. Use the $31.75 and $18.25 simulated payments and two test member accounts. Pass if the displayed awards match the method you selected in the worksheet. For payer-based allocation, that means 31 and 18 points under the sample rounding rule. Fail if the awards differ or staff cannot identify which payment belongs to which account.
- Try the exception. Simulate B’s account being missed. Ask an authorized test user to inspect the original award and correct it. Pass if the final balances match the policy without a duplicate award and the correction can be traced. Fail if staff cannot determine what happened or cannot reach the expected result using the available process.
- Check permissions and support. Ask who may adjust or reverse points, what appears in the adjustment history, and how support handles a correction staff cannot make. Pass if responsibilities and the route to resolution are clear. Fail if a correction depends on an unspecified workaround or no one can explain who acts next.
Record the screens or steps demonstrated, the outcome, and any setup or support work the vendor says is needed. Ask whether the same behavior applies across the ordering and payment channels you actually use. If it does not, decide whether staff can explain different rules without confusing guests.
After the simulated checks pass, consider a small live service pilot using your normal operating procedures and actual guest consent and transactions. Train the team on the chosen rule and review real exceptions with the shift manager. A pilot answers a different question from the simulation: can staff apply the demonstrated process during service?
Compare the loyalty workflow alongside your restaurant POS system and broader restaurant management software requirements. For the economics of the reward itself, use the loyalty reward cost guide; the points awarded on a check do not by themselves establish the cost of a reward.
Next, write down your preferred allocation and rounding rule, then compare it with Fleksa’s restaurant marketing automation. Ask Fleksa to demonstrate your split-payment and correction scenarios and confirm availability for your setup before deciding.
Frequently asked questions
Should each guest earn points on their own payment?
That is often the easiest rule to explain when both guests are members and pay different amounts. Confirm that your checkout can match each payment to the right account and apply your rounding rule.
Why can splitting a bill change the total points awarded?
If each payment is rounded separately, fractional points can be discarded more than once. Calculating and rounding the whole check can produce a different total. State the rule before checkout.
How should staff fix points sent to the wrong account?
Have an authorized employee review the original check and award, correct the mistaken allocation through the supported process, and record the reason. Check for an existing award first to avoid duplicating points.
