September 26, 2026 · 5 min · Inventory and logistics

Lire en français

Odoo dropshipping: keep control from supplier to customer

A supplier ships an order straight to your customer: your warehouse never handles the goods, but your team still owns the commercial follow-up. For an Odoo project in Belgium or France, dropshipping requires clear responsibility for confirming delivered quantities and resolving discrepancies. This Odoo Enterprise guide proposes a way to prepare that workflow with purchasing, sales and finance.

The functional dropshipping flow

Odoo documentation describes a Dropship route. The product needs to be configured for sales and purchasing, with a vendor. The flow links the sales order to a vendor request for quotation; confirming that request as a purchase order creates the associated dropship transfer.

We recommend checking this path in your test database before migrating an entire catalogue. Record the product reference, selected supplier, final delivery address and expected lead times. Having a purchase order does not prove that the customer has received the goods.

A pilot that exposes discrepancies

Fictional Underside example: a distributor sells 12 chairs to a business customer. The supplier must ship them to a branch whose address differs from the billing address. It delivers 8 chairs, promises the remaining 4 for the following week, and the customer then requests cancellation of the balance.

Our acceptance test starts by tracing the purchase and related movements from the sale, recording only the quantity actually delivered, and handling the outstanding balance according to the agreement with the supplier. The expected result is an explainable history: 12 ordered, 8 delivered and 4 cancelled. Ask finance to check the effect on invoiceable quantities under the chosen policies, without assuming that a commercial cancellation cancels every linked document.

Define delivery evidence before automating

These are project controls proposed by Underside. Test them with actual user permissions. Include a case where the supplier changes the address or date after confirmation: teams should know which record to correct and how to preserve the decision history.

Prepare migration and interfaces

For an Odoo migration in Belgium or France, separate open orders awaiting shipment from completed deliveries awaiting invoicing. We recommend reconciling sales, purchases and available evidence at order-line level. Importing historical orders without this distinction can lead staff to repeat a purchase that has already been fulfilled.

If the supplier sends confirmations through an interface, define a stable reference and a duplicate-handling rule. Our test scenario includes the same message arriving twice, a quantity exceeding the order and an unknown reference. Rejected messages should reach an identified owner with a recovery procedure. A shipping notification and proof of receipt should remain distinct.

Underside’s analysis: measure follow-up quality

We recommend starting with one reliable supplier and a small product range. Track orders without a confirmed date, deliveries without evidence and unresolved quantity discrepancies. This is a proposed monitoring approach to implement using your tools, not a standard dashboard promised across all versions.

Evaluate standard configuration before developing an interface. For an existing Odoo customer, a pilot can establish the requirements without immediately changing every workflow. Continue with our guides to returns and credit notes and Odoo data migration.

Official source and scope

Functional basis: Odoo 19 dropshipping documentation. Check the screens and modules in your installation. This guide is not a new product announcement; the scenario, controls and migration advice are Underside’s analysis.

Back to blog