Run one connected rehearsal covering store sale, online collection, shared-stock conflict, cross-channel return and day-end reconciliation. Use normal staff accounts and the actual proposed payment and integration arrangements. Acceptance should show both completed transactions and recoverable exceptions, with clear ownership when one channel remains available while another temporarily loses connectivity.
Understand the decision
A busy weekend produces interruptions rather than a neat sequence of isolated sales. Include a customer waiting at the counter and an online order that has not reached the store. The review should reveal what staff can safely do, what must wait and how the backlog becomes visible after recovery.
Work through the requirements
- Rehearse connected channel scenarios together
- Introduce a temporary connectivity interruption
- Reconcile stock customer obligations and payments
| Record or decision | Why it matters |
|---|---|
| Weekend scenario pack | Combines the interacting transactions |
| Recovery checklist | Defines permitted work during interruption |
| Channel close report | Explains each outstanding or completed obligation |
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
Separate successful demos for the store and website do not prove that the combined operation works. Acceptance should include the interfaces and shared-stock decisions between them, especially when staff need to resolve a customer problem during an interruption.
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 ↗