Define vendor-managed inventory through replenishment authority, shared stock evidence and responsibility for exceptions. Decide separately who owns the goods and who may propose or commit a replenishment. Then demonstrate the selected software records against that agreement, including a disputed count and a proposed order that still needs an authorised decision.
Start with the operating arrangement the parties actually intend. Write who supplies stock information, who reviews it, which goods and locations are included and what action each person may take. Keep those responsibilities clear before configuring shared reports or automatic rules.
Who owns the stock and who controls replenishment?
Stock ownership and replenishment authority answer different questions. A business can agree a replenishment process without changing who owns each item. If consignment is part of the proposed arrangement, document that choice explicitly and have the appropriate business owners review its operating and accounting implications.
Odoo’s consignment guide describes one software workflow. Odoo consignment requires its setting to be enabled. The documented consignment receipt uses matching Receive From and Assign Owner fields. Inspect the intended owner and receipt context in the demonstration rather than treating warehouse presence as proof of ownership.
The documented consignment workflow starts with manual receipts. Record what that means for the proposed receiving process and who is responsible for entering the agreed evidence. A receipt route and a purchase approval route should each have a clear purpose in the operating design.
Consignment stock has an owner column in the stock-on-hand report. Odoo excludes the consignee’s consignment products from its Stock Valuation report. These are documented product behaviours to check in the selected configuration; the business’s actual ownership and accounting decisions require their own approved basis.
Which stock evidence should be shared?
Choose the information needed for the replenishment decision: relevant item, location, unit, observed quantity and any agreed forecast context. Record when the information was produced and which movements it includes. A recipient should be able to distinguish a physical count from a forecast or another calculated view.
Agree how the parties handle a disputed record. Ask who checks the source, who may correct it and how the corrected information reaches the next decision. Keep the original observation and explanation understandable so a replenishment proposal does not silently rely on a number whose meaning has changed.
Review access at the level of the actual requirement. A partner may need a defined stock view without needing unrelated customer, staff or commercial information. Ask the selected system to demonstrate the intended recipient and permitted actions before describing the sharing arrangement as implemented.
| Agreement question | Record to define | Acceptance evidence |
|---|---|---|
| Which goods are included? | Items, locations and ownership scope | Sample report matches the agreed scope |
| What does the quantity mean? | Count or forecast basis and date | Recipient explains the source and interpretation |
| Who proposes replenishment? | Named role and supported route | Proposal reaches the intended reviewer |
| Who commits the action? | Authority and approval requirement | Software behaviour matches the agreed responsibility |
| What happens to a discrepancy? | Review and correction owner | Corrected evidence is traceable to its reason |
This original agreement worksheet keeps the software demonstration tied to the parties’ responsibilities. Add actual contractual and accounting requirements with the appropriate owners rather than inventing terms for the article.
How should replenishment rules be reviewed?
Odoo’s reordering-rule documentation gives a concrete automation example. Odoo reordering rules use minimum and maximum forecasted-stock quantities. Have the stock owner explain the basis for the configured quantities and the forecast being used.
A triggered Buy-route reordering rule creates a request for quotation. A Manufacture-route rule can create a manufacturing order instead. Inspect the selected route and resulting record in the proposed configuration. A business agreement about who may commit an action must be matched to the actual record and workflow created.
A reordering rule can use an automatic or manual trigger. Manual replenishment lets users review forecasts before selecting Order. Choose the trigger through the agreed authority and review process, then demonstrate what happens to the sample item. Keep the decision distinct from a general desire to “automate stock.”
Use the operation’s approved evidence to set any reorder quantities or other numerical limits. The right values depend on the actual agreement and demand context. Retain their source and owner so a later reviewer knows who can change them and why.
How should exceptions remain owned?
Include a delayed update, a disputed count and an item outside the agreement in the requirements discussion. Ask which person sees each exception and what information they need before acting. A shared dashboard needs an operating response when its data is uncertain or incomplete.
Keep replenishment proposals distinguishable from completed receipt. The reviewer should be able to identify what was suggested, what was authorised and what actually arrived through the chosen record path. Verify the selected system’s support for those relationships instead of assuming a generic inventory menu covers the whole arrangement.
Agree who reviews the configuration when the partnership changes. New items, different locations or a change of authority can alter which rules and views remain appropriate. Keep those changes in the handover record so the software does not continue applying an outdated arrangement.
Original disputed-count replenishment exercise
Prepare a fictional shared-stock arrangement for a sample consumable in a separate test environment. Define the intended owner, permitted location and replenishment reviewer. The exercise follows a disputed count into a reviewed proposal and the resulting authorised action.
First, produce the agreed sample stock view and ask the recipient to explain its quantity basis and date. Compare the displayed item, location and ownership context with the written scope. Retain any mismatch before triggering a replenishment proposal.
Next, introduce an approved sample correction to the quantity evidence. Ask the responsible owner to follow the review route and explain the change. Inspect the information used by the replenishment rule afterwards so the proposal can be assessed against the intended input.
Then demonstrate the configured route and trigger. Identify the resulting record, the person who may act on it and the evidence of any approved next step. Include an out-of-scope sample item and record how the intended arrangement handles it.
Finally, review the worksheet with the stock and agreement owners. Resolve unsupported sharing, authority and exception requirements before planning wider use. Retain the product version, configuration and decision evidence with the operating agreement’s review material.
For wider scope, see business systems and software development. Get started with your stock-sharing scope and replenishment authority questions.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.