Skip to main content

Website MOQ & Pack Rules

Purpose​

Website MOQ & Pack Rules connects the Sales quantity engine to eCommerce. Product pages show minimum, increment and maximum guidance; carts are checked on the server, and blocking violations prevent payment readiness. It is a helper integration with no standalone configuration menu.

This guide follows the Odoo 19 source and a targeted Odoo 20 comparison. No website purchase or runtime test was performed.

Before you start​

The addon corvus_sale_quantity_rules_website requires both corvus_sale_quantity_rules and Odoo eCommerce (website_sale). Its manifest enables automatic installation when the dependencies are installed. No Enterprise-only dependency is declared. Use packages for the same Odoo major version and hosting that permits custom addons.

Configure policies in Sales MOQ & Pack Rules. A rule must match Website or All Channels, the website company, product, customer, pricelist and applicable date. A backend-only rule does not become a website rule by installing this bridge.

Access and setup​

The bridge adds no staff permission group. Rule management stays with Quantity Rule Manager, and customers use the normal storefront. Internal rule names and manager audit fields are not part of the customer guidance payload. Company, product and unit checks control whether guidance is returned.

Open Sales → Configuration → Sales Quantity Rules and prepare a suitable rule. Use Quantity Rule Simulator with Channel Website to inspect a representative customer's match. Then check the published product through the ordinary website editor and product workflow; this bridge adds no publication action.

Workflow​

  1. Visit the product page with the intended customer session and pricelist. A matching rule provides quantity guidance beside the quantity control and supplies its default, minimum, maximum and increment values.
  2. Select a product variant. In Odoo 19, the frontend refreshes the guidance from combination information and resets the input when the selected product changes. Plus and minus controls step by the configured increment within displayed bounds.
  3. Add a valid quantity to the cart. The server evaluates the requested quantity with the website rule. For Warning, it accepts the requested quantity and returns guidance. For Hard Block and Offer Round Up, it retains the previous line quantity, or zero for a new line, when the request is invalid. It does not silently accept the suggested rounded amount.
  4. Change the cart quantity to a permitted amount and review any message shown beneath the line quantity. Nonpositive updates pass through the native removal path so a customer can remove a line.
  5. Continue through the normal checkout. Odoo 19 performs another quantity check before the cart is ready to be paid. An unresolved blocking violation raises a message asking the customer to correct cart quantities. A current manager override from the base module is recognised by this final check.

Practice scenario​

In an authorised test website, configure the fictional “Harbor Ceramic Cup” with Website channel, Minimum 12, Quantity Multiple 6 and Hard Block. For a cart already containing 12, an attempted change to 13 should retain 12 and return the nearest valid quantity guidance. Changing to 18 should satisfy the quantity rule. This is a source-derived exercise; no checkout or payment has been executed.

Troubleshooting and limitations​

If product guidance is missing, check the active rule, website company, dates, customer/pricelist scope and compatible unit. Product-page guidance uses the current website user's partner, while the saved cart is evaluated against its order customer. Recheck the cart after changing customer details.

The server remains authoritative even if a browser control is bypassed. An incompatible unit yields a customer-facing contact message; a manager must fix the underlying rule. Offer Round Up still requires an explicit valid cart quantity. Native stock restrictions, product availability and payment requirements continue to apply.

This addon does not create a PO-reference field, approval portal, payment provider, independent rule editor.

Catalogue-qualified versions are Odoo 15, 16, 18, 19 and 20. Odoo 17 source is also present, but that pair is not catalogue-qualified. The workflow above is source-reviewed for 19.0; 15–18 workflows remain unreviewed here. In the targeted 20.0 comparison, checkout and payment readiness use blocking alerts instead of the Odoo 19 payment-readiness exception. Product guidance tracks both variant and unit, and frontend bounds preserve native minimum and stock ceilings. Use the matching version's package.

The Odoo 19 Live Test selector was checked against the live catalogue; no demo was launched. For purchase, use the Corvus apps catalogue and choose your exact version and required base module.