Define which system owns the loyalty balance and how an approved refund affects the original earning or redemption event. Preserve stable transaction references and test partial returns. The interface should expose failed adjustments for review rather than assuming that completing the payment refund automatically updates an external loyalty service or preserves the intended customer balance.
Understand the decision
A shopper earns points on a promotional set and later returns one component. The loyalty platform and payment provider process different events at different times. The review should specify the commercial rule, the authoritative balance and the evidence needed when one adjustment succeeds but the other is delayed.
Work through the requirements
- Approve earning and redemption reversal rules
- Link adjustments to the original transaction
- Reconcile failed or partial loyalty updates
| Record or decision | Why it matters |
|---|---|
| Loyalty transaction key | Connects the sale and adjustment |
| Refund event | Records the approved financial change |
| Balance exception | Shows unresolved loyalty differences |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Payment completion and loyalty reconciliation are different outcomes. Do not claim they are automatically consistent simply because the systems connect; demonstrate the exact earning, redemption and partial-return rules that the business has approved for the chosen provider.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Beauty retail in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Point of Sale daily workflow and refunds ↗Lot numbers ↗Expiration dates ↗