Skip to main content

Warehouse Purchase Rules

Purpose​

Warehouse Purchase Rules adds a destination-warehouse condition to Purchase MOQ & Freight. A supplier can have different order minimums or freight terms for different warehouses, while the base app keeps the same threshold, warning, freight and approval workflow.

This is a helper integration with no separate top-level application or standalone configuration menu. It extends the base rule form and threshold analysis.

Before you start​

Use matching packages for corvus_purchase_vendor_order_rules and native Purchase/Inventory (purchase_stock). The helper declares both dependencies and is marked for automatic installation when the packages are available. No Enterprise-only dependency is declared.

Have an administrator configure the warehouses and their purchase receipt operation types. The destination used here is the warehouse belonging to the RFQ’s operation type. It is not inferred from a vendor address, delivery-address text or the user’s current warehouse preference.

This guide is based on the 19.0 source workflow, with selected comparisons of the other listed versions. No runtime test was performed for this guide.

Access and setup​

The base Vendor Order Rule Manager role maintains rules. Purchase users can review applicable thresholds and analysis within their existing access. This bridge adds fields, not new access groups; selecting a warehouse does not grant warehouse or company permissions.

Open Vendor Order & Freight Rules in Purchase configuration. On the rule form, Destination Warehouses appears after the destination-address field. Choose the warehouse or warehouses to which the rule applies, and keep the company consistent. Leave it empty when the rule should not restrict the warehouse.

Workflow​

  1. Create or open a base rule with its vendor, company, threshold and action settings. Add the intended Destination Warehouses and save.
  2. Open an RFQ for that vendor. Choose the native receipt operation type associated with the intended destination warehouse.
  3. Inspect Vendor Rule and Why This Rule on the RFQ. A scoped rule matches only when the operation type’s warehouse is included. The explanation includes the matched warehouse scope.
  4. Compare the effective rule with any broader company/vendor rule. A populated warehouse scope contributes to specificity, but a higher-priority competing rule still wins first.
  5. Follow the base workflow to resolve the minimum or freight shortfall, request any permitted exception and confirm the order.
  6. In Minimum Order & Freight Analysis, use Destination Warehouse and the Warehouse grouping. The bridge adds warehouse information to list, search, pivot and graph views.

Practice scenario​

In an authorised test database, fictional Cedar Supplies has a general minimum of 300. Create another rule with the same priority, the same vendor and a minimum of 500 for East Warehouse. An RFQ whose receipt operation type belongs to East should match the more specific rule; an otherwise identical RFQ for West should fall back to the general rule. Verify the selected rule and explanation before confirming either. This source-derived scenario was not executed.

Troubleshooting and limitations​

If the warehouse rule does not match, inspect the RFQ operation type and its warehouse first. Then check rule company, dates, vendor and every other configured scope. Warehouse matching is an additional condition; it does not replace the base conditions.

A warehouse-scoped rule does not match an operation type with no warehouse. For a direct-delivery workflow, configure and review the applicable base rule instead of assuming a destination address supplies a warehouse.

Changing the operation type can change the governing rule and current exception. Recheck the base threshold status before confirmation. This helper does not create warehouses, route goods or determine freight prices independently.

Qualified catalogue pairs are 15.0, 16.0, 18.0, 19.0 and 20.0. A 17.0 source package exists without a qualified live-demo pair here. The inspected bridge comparisons retain operation-type warehouse matching; older view definitions follow their native version. The base app has additional version differences.

Live Test — Odoo 19.0 · Choose your exact Odoo version in the Corvus catalogue.

Read Purchase MOQ & Freight for rule actions, managed freight, approvals and troubleshooting.