Quick answer
A manual loyalty adjustment should explain what changed, why it changed, and which staff member was responsible. A useful control lets staff correct a genuine mistake promptly while preserving enough evidence for a different person to review it later. Begin with named access and a short exception process, not a complicated approval chain for every normal sale.
Manual correction is not automatically evidence of misconduct. Wrong amounts, missed scans and customer-service exceptions happen. The purpose of an audit trail is to distinguish those cases from unexplained changes and prevent the same error from recurring.
Decide which actions need review
List the adjustments your team can make: adding missed progress, correcting an amount, reversing an error, honoring a disputed reward or issuing a goodwill benefit. Define the evidence and approval needed for each. A receipt-backed correction and a discretionary gift should not look identical in a weekly report.
Keep routine earning separate from exceptions. If a manager approves every ordinary stamp, the process will slow checkout and encourage workarounds. Instead, set a clear escalation rule for unusual value, missing evidence or repeated corrections on the same account.
Give people their own permitted access
Boomerangme's manager-profile documentation lists permissions for activities such as viewing operations, editing customers and making accruals. Its manager transaction section provides activity details. These are relevant controls to test, but a role label does not establish that your preferred approval workflow is built in.
Use a named account for each staff member wherever your setup supports it. A shared login makes an activity record much less useful because it identifies the account rather than the person at the counter. Follow the staff-seat guide and test the actual permissions before assigning live work.
Use reason codes that explain the event
A brief note can be more useful than a vague comment such as “manager change.” Agree a small set of reasons and an evidence reference.
| Reason | Useful supporting detail |
|---|---|
| Missed qualifying purchase | Receipt reference and eligible amount |
| Entry correction | Original operation and corrected value |
| Approved goodwill benefit | Approver and promised benefit |
| Reversal | Related original operation and reason |
Avoid placing unnecessary personal information in a transaction note. The Reward Scanner guide documents comments during the transaction flow. Confirm which notes your staff can see and which are visible to customers before using them for internal explanations.
Review exceptions against evidence
Suppose a hypothetical shop records twelve manual changes in a week. That number alone says little. Eight might be receipt-backed corrections after a scanner outage, while four could have no explanation. The useful review separates the causes instead of treating all twelve as suspicious or all twelve as acceptable.
Compare adjustment records with the underlying sale, stated program rules and any earlier correction. Check whether the same event was corrected twice by different staff during a shift change. Our shift-handover guide helps carry unresolved cases forward without issuing a second benefit.
The export documentation lists transaction fields that can support review, with availability varying by card type. A spreadsheet review is an operating process you create; this guide does not claim a native two-person approval system or automated fraud verdict.
Respond proportionately to a pattern
An increase in adjustments may indicate an unclear earning rule, poor training or a connector problem. Ask staff what happened and inspect the evidence before drawing conclusions. If one product repeatedly produces corrections, fix its eligibility configuration or instructions.
Restrict review records to people who need them. Correct legitimate customer balances without publicly blaming an employee or exposing customer history. Where an unexplained event remains material, follow your established management process rather than treating software activity as a complete investigation.
Questions about adjustment controls
Does every adjustment need owner approval?
Choose controls that reflect the value and available evidence. Routine receipt-backed corrections may need a different process from discretionary benefits or unexplained changes.
Does a transaction log prove who physically performed an action?
It identifies the recorded account or device context. Shared credentials and other operational factors can limit what you can conclude about a person.
Can Boomerangme automatically approve every exception for us?
The cited sources establish permissions and transaction information, not your full approval policy. Test the controls and define the remaining review responsibilities.
Explore a manageable control process
Bring three realistic exception cases to a trial: a missed scan, a duplicated correction and a discretionary benefit. Explore Boomerangme to check how its documented records and permissions fit your staff process.
Sources & further reading
- Boomerangme manager profileDocumented permissions and manager transaction information.
- Boomerangme customer and transaction exportsExport fields, including operation, note and manager where applicable.
- Boomerangme Reward Scanner workflowDocumented transaction comments and reward processing.
Sources reviewed .
Numerical examples are illustrative unless a cited source states otherwise.
