Ask an Odoo implementation provider to demonstrate an order resembling your operation: an actual selling unit, insufficient stock, split delivery, a return and a collection requiring follow-up. Separate Sales and Inventory demonstrations may look organized; the order's movement between them reveals the fit of the proposed configuration.
Prepare a worksheet and name decision-makers from sales, warehouse operations and accounts. Establish what needs configuration, a process change or development, rather than copying every detail from old files without review.
Fictional data for one complete journey
Imagine a cleaning-products distributor selling an item by piece and carton, with twelve pieces per carton in this example. It has two warehouses, a salesperson and a collections employee. A customer orders ten cartons. Six are available for the first shipment. The customer later returns one carton from that shipment and pays part of the amount due under an arrangement approved by the company.
This is fictional, not an implementation outcome or proposed accounting policy. Prepare test customer, product, unit, stock-location and salesperson data. Real customer prices and balances are unnecessary to establish whether the provider understands the relationship between orders, movements and collections.
1. Before selling: customer and transaction unit
Define customers, branches, delivery addresses and account ownership. Can the invoice customer differ from the recipient? Who reviews duplicates? Explain purchase and sale units and their conversion, including who approves a ratio and corrects it before use.
The team needs a consistent meaning for “carton” across the order, stock and reports. Ask the provider to demonstrate the proposed configuration on the test item. A unit label in a spreadsheet does not establish the full meaning. Record differing packaging across products separately.
2. The order: a salesperson's permitted role
Define what sales staff can see, create and change, including price or discount approvals and exceptions. Will they use the standard system, an app or a portal? Do not assume a field app or offline operation is part of a general subscription or proposal. Specify them if required.
View the order through the salesperson's account and then the approver's. Observe what changes and whose action appears in the record. The aim is to understand workflow and accountability, rather than grant full administrator access to make a quick demonstration succeed.
3. Warehouse: where will available stock ship from?
Distinguish company-wide quantity from stock at a location able to ship. Who approves movement between the two warehouses and records receipt? Add lot or expiry requirements if relevant, and ask how the proposed solution covers and tests them.
Review opening stock preparation: units, locations, condition and reconciliation owner. Do not combine saleable, damaged and reserved stock into an unexplained number. Record excluded stock counts or cleanup tasks so they can be completed before operation.
4. Partial delivery: where does the remainder stay?
Ship the available six cartons and follow the remaining four. Odoo documentation describes a backorder flow for deferred quantities after partial shipment. Ask the provider to demonstrate the chosen configuration: the first shipment reference, what remains pending and what staff and any in-scope customer portal display.
Also discuss waiting for the full quantity if that fits your business policy. Stock shortages should not trigger an unexplained default decision. The choice affects communication, dates and warehouse work.
5. Return: what came back and in which state?
Include the returned carton from the first shipment. Link it to an appropriate reference and explain who inspects it and whether it becomes available stock or remains in a review location. Resale or replacement cannot be inferred from the word “return”.
Review effects on documents and collections with the accounts owner under approved company policies and configuration. A successful inventory movement does not establish correct financial treatment throughout. A short software demonstration cannot replace decisions belonging to business owners.
6. Collections: distinguish recording and matching
Where does the collections employee record a payment, under which permission, and how are document links and outstanding items shown? Odoo documents payment registration, document links and configuration-dependent behavior. Ask for the result in the proposed environment rather than relying on a single status color.
Clicking register does not mean money has actually moved or every matching step is complete. Ask the responsible team to explain the collection cycle, the reviewed record and the correction process without arbitrary changes that lose traceability.
7. An acceptance worksheet linking the processes
| Checkpoint | Demonstration evidence |
|---|---|
| Product unit | Piece and carton have consistent meanings in orders and stock. |
| Order and delivery | Ten ordered, six in the first shipment and four traceable pending cartons. |
| Return | The returned carton has a reference, condition, location and review decision. |
| Collection | The test payment, links and unresolved items are explained to the responsible employee. |
| Organizational handover | Configuration, data, roles, training, files and outstanding tasks are known. |
For commercial comparison, use the Odoo proposal scope guide. For integration inputs, see the integration discovery guide. When commissioning Odoo implementation for distribution, retain this worksheet among the deliverables used at acceptance.
Sources
Official Odoo 19 documentation sources on shipments and backorders and payments were read on 3 November 2026. The distributor scenario and worksheet are illustrative. No configuration or customization is guaranteed in every edition or plan, and no official partnership is established. The text was prepared with AI assistance and review of its information and sources.
