Blog Information

• Posted By : Victoria Hodgson
• Posted On : Nov 11, 2026
• Views : 4
• Category : Soccer
• Description :

Overview

• 

  A CBD store completes a refund, hands the customer a receipt, and considers the return closed. Later, the customer questions their loyalty balance. Staff must determine whether points earned on the purchase were removed, whether points spent on a reward should come back, and whether anyone already made a manual correction.

  A useful audit connects these events to the original transaction. Start with the purchase and follow its history through the return, reward activity, and any subsequent adjustments. This gives employees a basis for explaining the outcome and deciding whether a correction is needed.

  When reviewing a CBD POS, use indicaonline.com/cbd as a starting point for evaluating the platform against your store’s workflow. Ask how staff can inspect transaction and loyalty records, and confirm the supported return behavior before promising customers an automatic points adjustment.

  Define the expected loyalty outcome first

  Write down the rules employees should apply when auditing returns. Identify which purchases earn points, how returns affect those earnings, and what happens when a customer used a reward on the refunded order.

  Include the treatment of partial returns, exchanges, and exceptions approved by a manager. Separate the store’s published policy from the software settings that implement it. If they disagree, document the gap and escalate it rather than improvising a customer-specific rule.

  Separate earned points from redeemed rewards

  Audit earned points and redeemed rewards separately. Removing points earned on a returned purchase and restoring points spent on a reward are different movements. Either may require investigation even when the other is correct.

  Record the expected outcome for each movement before checking the balance. This avoids treating a net change as proof that both actions happened correctly.

  Link the return to the original purchase

  Gather the original receipt, the return record, the relevant customer profile, and the available loyalty history. Check the transaction references and returned items so the audit follows the correct purchase.

  Confirm that the refund belongs to the same customer account that received the original points. If staff find duplicate profiles or an uncertain account match, resolve that identification problem before transferring or adjusting points.

  Check the transaction history before the balance

  A current balance combines activity from multiple events. The customer may have made another purchase, redeemed a reward, or received a service adjustment after the original transaction.

  Reconstruct the sequence relevant to the return. Note the balance before the affected activity, the recorded movements, and the resulting balance. Preserve unexplained differences for investigation.

  Review points earned on the returned items

  Compare the original earning entry with the returned products and the applicable program rules. For a partial return, identify which items the customer kept and which earning entries should remain.

  As a platform-specific example, LoyaltyLion’s documentation on refunds and returns describes automatic removal of points earned on refunded purchases, including partial removal for partial returns without a voucher. Its documented behavior provides a useful comparison, while your store should verify its own system and configuration. 

  Check any original bonus or promotional earning entries separately. Do not assume every points entry attached to the customer was generated by the returned purchase, or that today’s earning settings explain an older transaction.

  Investigate missing or repeated reversals

  Verify the recorded activity before correcting a suspected error. If the expected reversal is absent, check whether the return was completed and whether the relevant loyalty event reached the program.

  If points appear to have been removed repeatedly, compare the entries with successive returns and manual actions. Repeated entries may represent separate events; their transaction references should establish whether anything was duplicated.

  Check what happened to the redeemed reward

  Determine whether the customer used a reward on the original order. Record the reward type, its redemption history, and its current status alongside any restored points.

  A completed money refund does not establish the correct loyalty outcome. Reconcile the payment refund and reward movements against their respective records, keeping cash amounts and points clearly distinguished.

  Treat partial returns as a separate case

  For a hypothetical mixed basket, the customer returns a CBD topical but keeps another product purchased with the same reward. Staff should check how the program allocates that reward across the retained and returned items.

  The selected documentation illustrates why configuration matters: LoyaltyLion describes an optional feature for proportional restoration of redeemed points on eligible partial returns. That feature has eligibility conditions. Verify the actual setup rather than assuming every partial return restores spent points. 

  Also check whether the reward remains usable. An audit should account for the points outcome and the reward’s status together.

  Resolve exceptions without duplicating adjustments

  Review cases where the customer spent earned points before returning the purchase. Establish what the software recorded and what the store’s policy requires before deciding how to handle any resulting discrepancy.

  Check whether another employee has already issued a goodwill credit or manually restored points. Distinguish a service adjustment from a transaction correction. They may have different reasons, and an undocumented credit can obscure the original issue.

  Record why a manual correction was approved

  For each authorized correction, retain the linked purchase, return reference, reason, approving employee, and resulting points movement. Preserve enough history for another employee to understand the decision.

  Before applying the correction, check whether automatic processing is still pending. Assign a follow-up check if its status is uncertain so a later automatic event does not silently duplicate the manual action.

  Verify the result across sales channels

  If the store uses connected online and in-store systems, confirm that the account and transaction references match across them. Compare the available activity history and customer-facing balance using the systems’ documented processing behavior.

  Where results differ, gather the relevant references and timestamps for the person investigating. Avoid making unrelated adjustments in multiple systems to force agreement; identify where the missing or incorrect event originated.

  Give the customer a clear explanation of the confirmed result or the unresolved question. Keep personal information limited to what the investigation requires.

  Close the audit with a documented outcome

  Use a short completion checklist for each reviewed return:

  • The original purchase and customer account are confirmed.
  • The returned items match the refund record.
  • Earned points and redeemed rewards have separate outcomes.
  • Manual changes have a recorded reason and approval.
  • Any channel discrepancy has an assigned owner.

  Close the case when the evidence explains the result. If an issue remains, record the next action and who will verify it. Use recurring problems to update staff instructions or review program settings, then test the affected return scenario before relying on the revised workflow.