Ecommerce fulfilment should connect the order’s required items to the goods prepared, dispatched and reported delivered. Start with an item-and-quantity sheet and name the evidence required at each handover. Test a short pick and a partial dispatch in a separate environment so the team can explain what has physically happened and what remains outstanding.
A warehouse screen, a packed parcel and a customer delivery report describe different observations. Agree the meaning of each before selecting status labels. The next responsible person needs to know which items and quantities the record concerns, what evidence supports the state and who investigates a discrepancy.
The original fulfilment worksheet below uses a fictional order for sample items. Narrow software examples come from Odoo 18 Inventory and Odoo 19 ecommerce documentation, retrieved on 24 October 2026. Each example keeps its documented version. Wider planning belongs with online stores and business systems.
What should the warehouse receive from the order?
Write the order reference, item identifier, required quantity and unit on the worksheet. Identify which value came from the confirmed order and who can resolve an ambiguous product description. The receiving warehouse role should be able to identify the intended work without interpreting a customer’s informal message as the complete picking instruction.
Odoo 19 creates a delivery order after sales-order confirmation. Odoo 19 requires Inventory to process ecommerce deliveries. Its order-handling guide supplies a concrete example of the operational handoff. Ask how the proposed system connects the source order to the warehouse record and retain both identifiers.
Odoo 19 does not generate delivery orders for service or subscription products. Include product type in the requirement review where relevant. A missing delivery record may need a product-configuration explanation rather than a request to create warehouse work for every kind of sale.
For the fictional order, use Item A with three units and Item B with one unit. Record those illustrative quantities as the expected demand. Ask the warehouse reviewer to identify the actual sample goods and their units before assessing the system’s handling of a discrepancy.
How many operational steps does the workflow need?
Odoo 18 defaults incoming and outgoing shipments to one-step processing. Odoo 18 permits different numbers of steps for incoming and outgoing flows. Its one-step receipt and delivery guide shows why the warehouse configuration belongs with the demonstration evidence.
Odoo 18’s default one-step flow does not require Multi-Step Routes. Odoo 18 requires Multi-Step Routes to display the shipment settings on the warehouse form. Odoo 18 enabling Multi-Step Routes also activates Storage Locations. Preserve those qualifications when discussing the documented configuration; they should not become assumptions about another edition or application.
Choose operational handovers according to the work that needs control. If preparation and dispatch are carried out by different roles, write what each records and what the next person needs to receive. The original worksheet can assess those requirements even when the chosen software represents them differently from the Odoo examples.
| Handover | Proposed evidence | Exception to include |
|---|---|---|
| Order to picking | Order reference, item and required quantity | Ambiguous item or unit |
| Picking to packing | Actual prepared items and quantities | Short pick or wrong sample item |
| Packing to dispatch | Parcel reference and agreed contents | Partial dispatch or packaging discrepancy |
| Dispatch to delivery follow-up | Dispatch evidence and responsible contact | Uncertain or conflicting report |
| Outstanding work | Remaining item quantities and owner | Remainder loses its next action |
The table is an original operational brief. Assign the actual roles and expected evidence before conducting the proposed test.
What should a completed system movement establish?
Odoo 18’s documented delivery process moves a validated delivery order to Done. Odoo 19 instructs users to validate the delivery order after warehouse operations and shipment. These examples describe application-record steps; the business should still define what physical evidence its operators use to support those steps.
For the sample order, ask the reviewer to distinguish goods prepared from goods dispatched. Record the sample parcel and its contents alongside the relevant system movement. The person answering a customer enquiry should be able to identify the particular observation they are relying on.
Odoo 19 can send confirmation emails for completed delivery orders when enabled. Agree what such a message should communicate in the proposed operation. Keep the message’s meaning aligned with the underlying evidence so a dispatch update remains understandable alongside any later delivery report.
A delivery discrepancy deserves a named owner and a record of the conflicting information. The process should make it possible to investigate the affected parcel or item without changing the whole order to an unexplained final state. Write the next action and preserve the original observation for review.
Include a proposed substitution question if the operation might offer an alternative item. Identify who may approve it and which order information must be updated before preparation continues. In the fictional exercise, keep the originally requested item visible beside the proposed alternative so the reviewer can understand the decision and the resulting parcel contents.
Original short-pick and partial-dispatch exercise
Prepare the fictional order in a separate test copy with Item A requiring three units and Item B requiring one. Write the expected order and warehouse references on the sheet. Identify the picking, dispatch and customer-response roles, using invented data and a controlled physical or simulated test fixture.
First, run the complete preparation case and ask the reviewer to compare the sample items with the required quantities. Retain the actual observation and system record. Then create a short-pick case in which only two units of Item A are available in the fixture. The illustrative remainder is one unit of A; record how the configured workflow represents it and who investigates it.
Next, propose a partial dispatch of the prepared goods. Record the parcel reference, included items, quantities and outstanding work. Ask another colleague to reconstruct the state from the sheet and system records. Their explanation should identify what left, what remains and which role owns the remainder.
Then introduce a sample delivery report that needs clarification. Ask the customer-response owner which evidence they would consult and how they would record the uncertainty. Keep this branch separate from the original picking discrepancy so the investigation follows the right handover.
Finish by comparing the observed records with the written requirement for every stage. Capture configuration questions, unclear unit mappings and missing responsibilities separately. This creates an assessable fulfilment brief without relying on the appearance of a single order status.
For connected payment questions, see online payments. To discuss the warehouse handovers and evidence still needed, get started with the worksheet and representative item list.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.