A warehouse may hold goods that still belong to a supplier. For an Odoo project in Belgium or France, this requires a clear distinction between physical stock and ownership. This Odoo Enterprise guide proposes an acceptance testing approach for companies receiving consignment stock into their own premises.
What consignment tracking provides
Odoo documentation describes a consignment option in the Inventory application settings. It allows an owner to be assigned to received goods. Movement and stock-on-hand reports then help track those goods and their owner. Supplier-owned goods are excluded from the inventory valuation of the company holding them.
This functional principle does not define your commercial agreement. We recommend documenting separately when a sale must be reported to the supplier, how settlement works and how unsold goods are handled. Have purchasing and finance agree on these points before configuring automation.
Start with a simple, verifiable scenario
Fictional Underside example: a distributor holds 40 units it has purchased and receives another 100 units of the same product, owned by supplier A. The physical count covers 140 units, but the two groups must remain identifiable. A shelf label alone cannot preserve that distinction in the data.
Our acceptance scenario is to receive the 100 units, move some to another location, then deliver 15 units from consignment stock and return 10 to the supplier. The expected balance for that owner is now 75 units. Check quantities and references for each movement, and verify that the distributor’s 40 units remain correctly distinguished.
Preserve ownership throughout operations
- Receipt: check the supplier, owner, product and quantity before validation.
- Internal transfer: ensure that moving goods preserves their ownership information.
- Delivery: test stock selection when several owners share one product reference.
- Return: retrieve the original movement and the relevant owner.
- Count discrepancy: investigate the cause and obtain approval before applying a correction.
These checks are our proposed acceptance tests, not a promise of behaviour across every installed module. Run them with actual warehouse staff permissions and the barcode tools used on site. A successful administrator test is insufficient to validate everyday operations.
Migrate quantities without losing ownership
For an Odoo migration in Belgium or France, we recommend preparing inventory by product, location and owner, with lot details where relevant. Do not merge every quantity of a product into a single total. Reconcile the migration file with physical counts and supplier statements.
For a logistics interface, include ownership among the data that must demonstrably survive the transfer. Test a missing owner, an unknown supplier reference and a message sent twice. Define who handles rejected records and how corrections are tracked before allowing the flow to run unattended.
Underside’s analysis: assign the business decisions
We recommend starting with one supplier and one product family. Logistics validates movements, purchasing validates the supplier agreement, and finance validates valuation and settlement checks. A successful pilot lets these teams jointly explain a balance, a delivery and a return without maintaining a separate correction spreadsheet.
Evaluate standard configuration before commissioning custom development. An extension is justified only after identifying a specific requirement, such as exchanging statements with a supplier, and checking what the chosen configuration already covers. Continue with our guides to cycle counts and Odoo data migration.
Official source and scope
Functional basis: Odoo documentation on consignment stock, SaaS 19.3 branch. Check the screens and reports in your version before acceptance testing. This guide is not a new product announcement; the example, tests and migration approach are Underside’s analysis.
Use a real supplier flow to prepare your Odoo pilot with Underside.