Staff should be able to fix a loyalty balance when the evidence supports a correction, but no one should change points without a recorded reason and an approval rule. Decide who can request, approve, and apply a change. Then review the original balance, the adjustment, and the resulting balance against the supporting order or other record.
The right process should be quick enough for a guest issue during service and clear enough for a manager to reconstruct later. Before buying software, ask whether those steps can be enforced in the system or whether your team will need a separate approval log.
Define when staff may adjust points
A manual adjustment is a staff-initiated change to a guest’s points balance. It might correct eligible points that did not appear after an order, remove points added twice, or record a goodwill credit allowed by your policy. Those are different reasons, so give each one a clear label rather than putting every change under “customer service.”
For a correction, staff should be able to connect the request to a record. For example, a guest says an eligible order did not earn points. The employee checks the order, the account, and the program rules before requesting the missing points. A screenshot supplied by the guest may help locate the order, but it should not replace a check against the restaurant’s own records.
Contrast that with a request to “add some points because I visit often” when there is no order reference or approved goodwill reason. The employee should not invent a correction to satisfy it. They can explain that a manager must review the request, or offer another remedy under the restaurant’s policy.
Ask staff to collect only what is needed to make and verify the decision:
- The guest account identifier used in the loyalty system, checked against the order or account record.
- The order reference and date, when the adjustment relates to a purchase.
- The reason for the change, including whether it is a correction, reversal, or authorized goodwill credit.
- The balance before the change, points to add or remove, and expected balance afterward.
- The requesting employee, approver, and person who applies the change, plus the time of the action.
Keep sensitive guest details out of free-text notes when an account or order reference will do. Set a consistent way to store supporting evidence, and decide who may see it. Access to a guest’s contact details is separate from permission to send marketing messages.
Also define what points mean. A balance is not necessarily a reward the guest can redeem now. Check the program’s actual thresholds, expiration rules, and other conditions before telling a guest what a corrected balance will buy. The loyalty reward cost guide can help with the separate question of what rewards cost the restaurant.
Assign permissions and approval before service
Use roles rather than informal promises. The matrix below is a starting policy, not a claim about any software’s built-in permissions. Adapt it to your staffing and the size of adjustment you are willing to authorize at each level.
| Action | Front-line employee | Shift manager | Owner or designated reviewer |
|---|---|---|---|
| Request a change | Collect the account, reason, and supporting reference | May request a change with the same details | May request a change with the same details |
| Approve a routine correction | No | Yes, after checking evidence; not their own request | Yes, including requests from a shift manager |
| Apply an approved change | Only if access is granted and approval is recorded | Yes, after approval is recorded | Yes, after approval is recorded |
| Review the completed record | Provide clarification if asked | Check routine entries not approved by them | Review exceptions and entries requiring independent review |
The important separation is between the person asking for a change and the person deciding whether it is justified. If possible, a different person should also review completed entries. The approver may apply an approved correction under this example policy, but the record should identify both actions rather than treating approval as invisible.
For a small team, a second person may not be on site. Set a rule for when the employee must wait for remote approval and when the guest can expect an update. If the manager must both approve and apply a time-sensitive correction, have the owner review it afterward. That later review is a compensating control, not the same as independent approval before the change.
Write down a threshold for elevated approval that makes sense for your program, and include removals as well as additions. A large removal can harm a guest’s ability to redeem a reward; a large credit can create an unintended obligation. Also set a rule for corrections to an employee’s own account or an account belonging to someone close to them: route those requests to an independent reviewer.
Ask vendors whether permissions can distinguish requesting, approving, and applying a change; whether staff can edit a completed entry; and whether an owner can see who performed each action. If the system cannot enforce your chosen separation, decide whether a separate log and review process is workable before you buy.
Test the audit trail with a sample correction
In the following hypothetical example, a guest starts with 120 points. An eligible order should have earned 20 points, but those points are missing. The manager checks the order reference and confirms the correction. Adding 20 points produces a resulting balance of 140.
A useful completed adjustment record would read like this:
- Account: Guest account G-104; order reference O-218.
- Reason: Missing 20 eligible points for the referenced order; order and account checked.
- Request: Employee Alex requested the correction at 2:10 p.m.
- Approval: Shift manager Morgan approved it at 2:15 p.m. after checking the order.
- Application: Morgan added 20 points at 2:16 p.m.
- Balance: 120 before the change, plus 20 points, equals 140 afterward.
A reviewer should be able to follow that chain from the balance change back to the decision. The time and named actor matter: a note saying only “fixed points” does not show who made the change, why it was allowed, or whether the arithmetic is right. The resulting balance also needs to match the account history, taking any other recorded activity into account.
Before launch, ask the vendor to demonstrate the workflow in a test environment or with simulated records. Confirm that the practice does not change a real guest balance or send a guest message. Check whether the history shows the original entry, actor, time, reason, approval, and resulting balance. Ask how records can be searched or exported for review, who can alter notes, and what happens when access is removed from a departing employee.
A simulation checks the setup; it does not prove that a busy team will follow the process. If you run a live service pilot afterward, use actual requests under your approval policy, tell staff who handles exceptions, and review the records promptly. Do not create a real payment, guest message, or courier dispatch just to practice.
It is also worth checking how order records connect to the loyalty workflow. When comparing a restaurant POS system with your other tools, ask staff to show how they would find the relevant order without relying on a guest’s memory alone. If records sit in separate systems, specify which reference will connect them.
Review exceptions and correct errors without erasing history
Choose a review rhythm that fits the volume of adjustments. A manager might check entries after each shift during launch, then move to a weekly review once the process is stable. The owner or designated reviewer should periodically look across locations or shifts rather than relying only on the person who approved the changes.
Look for repeated adjustments to the same account, frequent changes just below your approval threshold, missing order references, changes made outside normal working hours, and entries where the requester approved their own work. A pattern is a reason to ask questions, not proof of misconduct. A system problem or unclear rule may also cause repeat corrections.
For each exception, compare the adjustment log with the supporting record and account history. Ask whether the reason was allowed, whether the right person approved it, and whether the final balance follows from the recorded transactions. Record the reviewer’s decision and any follow-up, including a deadline and owner for resolving an unclear case.
If an entry is wrong, preserve it and make a separately recorded correction rather than silently replacing the original. Link the new entry to the earlier one, explain what was wrong, identify the approver and actor, and show the balance before and after the correction. Ask the vendor whether its history retains both entries and how a reviewer can find the connection. If the software cannot do that, document the correction and its reference in your separate log.
Review access as well as transactions. Remove or change permissions when responsibilities change, and decide who can view adjustment notes. If your team uses restaurant marketing automation, keep the loyalty correction process distinct from campaign access: an employee who can fix a balance does not automatically need permission to send messages.
For your next buying conversation, bring the approval matrix and sample correction above. Compare the workflow with Fleksa, then confirm which permissions, history, and review steps are available for your setup before buying.
Frequently asked questions
Should every manual points adjustment require approval?
Set a written rule for every adjustment. You may choose different approval levels by reason or size, but the request, decision, actor, and resulting balance should still be recorded.
Can one employee request and apply a correction?
Your policy can allow that after a separate person approves it. If staffing makes independent approval impossible, define when a manager may act and arrange a later review by someone else.
What should happen if an employee adds the wrong number of points?
Keep the original record and make an approved, linked correction. Record why it was needed, who applied it, and the balances before and after, then check that the guest’s account history matches.
