Mark the order ready only after staff confirm the intended goods, quantity and collection location under the business’s approved process. Keep stock reservation, payment state and customer notification distinguishable. The test should show how a missing item or late substitution changes the collection promise before a message invites the customer to travel to the store.
Understand the decision
A website accepts an order for store collection, but the final item is on a display that staff cannot locate immediately. The shared stock figure is positive. The review should demonstrate how the store confirms physical readiness and who communicates an exception instead of relying on the original availability count.
Work through the requirements
- Confirm physical goods at the collection location
- Resolve substitutions or missing items
- Send readiness only after approved confirmation
| Record or decision | Why it matters |
|---|---|
| Collection order | Identifies the customer and pickup location |
| Preparation evidence | Records actual goods set aside |
| Readiness notification | Reflects the confirmed collection state |
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
An online reservation is not proof that goods are ready at the counter. Avoid sending readiness messages from a generic paid status unless the business has demonstrated the physical preparation and exception process behind that signal.
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 ↗