Find the original transaction and verify the business’s cross-channel return rule before processing the physical receipt and financial adjustment. Record condition and stock destination independently from refund authorization. Demonstrate the chosen payment route and reconciliation rather than assuming a store register can automatically refund any payment taken by an unrelated online provider.
Understand the decision
A customer brings an online order to a store that did not fulfil it, with one item missing its packaging. The cashier needs enough order evidence to act without unrestricted access to every customer record. The review should cover permissions, returned quantity and the financial handoff to the correct system.
Work through the requirements
- Locate the original order with appropriate access
- Inspect and classify the returned goods
- Use the approved cross-channel refund procedure
| Record or decision | Why it matters |
|---|---|
| Original transaction reference | Supports the return decision |
| Store return record | Captures physical condition and destination |
| Refund instruction | Identifies the authorized financial route |
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
Cross-channel returns involve policy, payment and inventory decisions that may not share one system. Do not promise universal refunds from any register; verify the actual provider, permissions and reconciliation process for the deployment being proposed.
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 Omnichannel 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 ↗Ecommerce order handling ↗Packaging ↗