Consignment Stock in a Business App: In Your Warehouse Does Not Mean Owned by You
If your warehouse holds goods that still belong to a supplier, record who owns them separately from where they are stored. An ordinary product quantity is not enough when your own units and a supplier's units sit together. Before commissioning a consignment feature, agree how staff identify the owner on receipt, choose whose stock leaves, and explain the remaining balance.
This guide is about operational software requirements. It does not determine when ownership legally transfers, how a consignment agreement should be drafted, or what your accounts must recognise. Confirm those rules with the appropriate advisers before implementing them.
Start with ownership, not a special shelf
Odoo's consignment documentation describes suppliers letting a business store and sell products without buying them up front. Its receipt workflow assigns the supplying vendor as owner. This is a concrete product example, not evidence that every stock application supports mixed ownership.
For your brief, distinguish three questions: which product is this, where is it physically held, and whose goods are they? A lot number can identify a production batch without answering the third question. A storage location can identify a shelf without establishing ownership either.
Ask for ownership on the quantity-bearing record rather than only a note on the supplier profile. Otherwise two suppliers providing the same product can become indistinguishable once the quantities are combined.
Follow one owner's goods through the building
A useful hypothetical demonstration starts with your own goods and a supplier's goods under the same product code. Receive the supplier's quantity, move part to another shelf, then dispatch an agreed portion. At each step, staff should be able to explain which owner's balance changed.
These are proposed requirements, not documented automatic Odoo features. Decide whether staff explicitly select the owner or whether a reviewed allocation rule does so. If the preferred owner's stock is unavailable, the application should follow a defined exception rather than silently consume another owner's units.
Also specify what a correction means. Fixing a wrongly assigned owner on an unprocessed receipt is different from discovering that an already dispatched item was attributed incorrectly. Preserve the explanation and related movements; do not make a casual field edit rewrite the physical history without review.
Keep stock views and settlement evidence distinct
Odoo documents owner information in its stock-on-hand report. It also says vendor-owned consignment is excluded from the consignee's Stock Valuation report. Those statements describe Odoo's reporting model. They are not a universal accounting conclusion for your agreement or jurisdiction.
Ask your developer for clearly named views: goods physically held, goods owned by each party, and goods eligible for the particular operation. A report called “our stock” is ambiguous unless its definition is visible.
Separately define what information the supplier needs for settlement: the relevant outgoing movements, returns, agreed period and unresolved discrepancies. Do not treat a movement report as proof that a supplier invoice was checked or payment completed. The event that creates a payable obligation must come from your reviewed business agreement, not from a developer guessing what “sold” means.
Acceptance exercise
Use fictitious suppliers and products in the application acceptance tests:
- Hold the same product for your business and a supplier without merging ownership balances.
- Move the supplier's units between locations while preserving the owner.
- Fulfil an order using the explicitly agreed ownership-selection rule.
- Show what happens when only another owner's units remain.
- Return goods to the supplier without representing that as a customer sale.
- Correct an ownership error through the agreed review path.
- Reconcile an owner's opening position, recorded movements and remaining balance for the selected period.
Accept the feature when a staff member can explain those outcomes, not merely when an “Owner” dropdown exists. For a stock-workflow application discussion, bring a description of one ownership arrangement without confidential supplier documents.
Questions worth settling early
Does consignment need a separate warehouse?
Not necessarily as a software requirement. The important distinction here is owner identity. Whether your operation requires physical separation is a separate agreement, handling or professional-advice question.
Is owner tracking the same as lot tracking?
No. A batch answers a provenance question; an owner identifies whose quantity is being held. Your process may require both.
Can the app calculate what to pay the supplier?
It can be commissioned to prepare evidence and calculations under agreed rules. This article does not establish those rules or claim that stock ownership fields automatically provide settlement, accounting or payment functionality.