When two representatives quote different prices to the same customer, a wholesaler needs to identify the approved list and explain the exception before sending the offer. This article is about your own selling prices and quantity discounts for a Saudi wholesale business, not about what an Odoo licence costs. Odoo’s documentation presents pricelists as a way to suggest prices on sales orders 1, and Saudi VAT is then calculated on whatever net price you agree 2. If you are still shaping the project, the ToDoOps homepage explains how we approach Odoo application implementation.

What a pricelist does, and what it does not

In Odoo ERP, a pricelist proposes the price of a product on a sales order, and the salesperson can always override it on the order line. A rule can set a fixed price, apply a discount, or use a formula. Rules can carry a minimum quantity and validity dates, the pricelist has a currency, and it can be assigned to customers. If a product-specific rule and a product-category rule both match, the product rule takes priority.

A pricelist alone does not guarantee an acceptable selling margin. We analyse how you approve exceptions and whether mixed-product quantity aggregation is required, then test your licensed version, applications and permissions before deciding what needs customisation.

Decide who owns the price before you configure it

Our operational recommendation: name one owner for every price version. In many wholesalers this is the commercial manager, with finance consulted on the floor price and sales operations entering the changes. Settle three questions on paper first:

  • Version ownership. Who approves a new list, and from which date does it apply? Retire the old list with an end date instead of editing it in place, so earlier quotes stay explainable.
  • Rule conflicts. If a customer has a negotiated price and a quantity tier also applies, which wins? Write the order of precedence and test it on real products. The only precedence we take from the documentation is that a product rule beats a category rule.
  • Representative overrides. Because the price can always be changed on the order, the control is a process. What is the lowest price a rep may type without asking, and who answers when they ask?

Worked example (hypothetical)

All figures below are invented for illustration. A wholesaler buys a product at a net direct unit cost of 70 SAR and lists it at 100 SAR. A customer orders 20 units.

Scenario Unit price (SAR) Net revenue (SAR) Direct cost (SAR) Contribution (SAR) VAT 15% (SAR) Gross invoice (SAR)
Base price 100 2,000 1,400 600 300 2,300
10% discount 90 1,800 1,400 400 270 2,070
20% discount 80 1,600 1,400 200 240 1,840

Contribution here is net revenue minus direct cost, before overheads. A 10% discount cuts the unit price by 10 SAR but removes one third of the contribution (600 to 400). At 20%, only one third of the base contribution remains (200). That is why discount tiers need an owner who can see cost.

The VAT column is not revenue or profit. ZATCA’s 15% VAT guide gives 15% as the standard rate for standard-rated supplies, with zero-rated and exempt supplies as exceptions. VAT on a net price is net × 15%, VAT inside a tax-inclusive price is gross × 15/115, and tax is separate from commercial margin 2. So 1,800 × 15% = 270, and 2,070 × 15/115 = 270. Whether a given product is standard-rated is a question for your accountant.

Configuration, process, or customisation

  • Configuration: pricelists, fixed-price, discount and formula rules, minimum quantities, dates, currency and customer assignment. See the Odoo applications we work with.
  • Process, decided by your company: the price-list owner, override limits, approval by message or call, a reason log and a review rhythm.
  • Possible customisation, only after analysis: margin blocks, automated approval flows and quantity aggregation across mixed products. Our recommendation is to run the pilot first. If overrides turn out to be rare, you may need none of these.

Wholesale businesses differ by trade, and our industries page shows how we frame projects by sector.

Pilot the representative override

A hypothetical pilot: two reps, ten customers, one month. Whenever a rep changes the suggested price, they record the product, list price, typed price and reason in a shared sheet. Review the reasons weekly. Repeated reasons warrant reviewing the rule or commercial agreement; an isolated reason may need coaching or a documented exception. Only then decide whether anything needs customisation.

If you want to see ordering and stock flow before the pilot, the Odoo demo is limited to sales and inventory. It does not demonstrate pricelist setups or this pilot. For a preliminary estimate of effort, which is not a precise quote, try the calculators.

Acceptance checklist

  • A named owner for each price version, with written start and end dates.
  • Written precedence between customer price, quantity tier, product rule and category rule, tested on at least five real products.
  • Currency, validity dates and customers are correct on each pricelist.
  • A minimum-quantity tier gives the expected unit price on a single-product test order.
  • A mixed-product test order was run, and the result is recorded rather than assumed.
  • The override rule is written, and reps know whom to ask.
  • Finance confirms contribution is calculated before VAT.
  • Your accountant has reviewed invoice VAT for each tax category in the pilot.
  • The override log was reviewed after week one.

FAQ

Can a salesperson ignore the pricelist? Yes. As documented, the pricelist suggests the price and it can always be overridden on the sales order. Control comes from a written process, not from the list alone.

Does a discount rule protect my margin? Not by itself. The discount in this example changes the sales price; it does not itself enforce an acceptable margin. In the example, a 20% discount leaves 200 SAR of the original 600. Finance should set floors, and any hard block needs analysis of your configuration, permissions and possible customisation.

Will 10 units of product A and 10 of product B count as 20 for one tier? Do not assume so. Test it and record the result. If you need it, treat it as a requirement to analyse before anyone promises it.

Next step

To turn these points into a pricing-governance and configuration plan, start with the calculators for a preliminary estimate, which is not a precise quote. Then contact us with your current price lists and a description of how reps override them. You can read more about our approach on the ToDoOps homepage.

Source notes

[1] Odoo official documentation, version 19, pricelists page (pricing.html): suggested price that can be overridden on the sales order, rule types, minimum quantity, validity, currency, product-over-category priority and customer assignment. Reviewed in our internal evidence register.

[2] Zakat, Tax and Customs Authority (ZATCA), 15% VAT guide (VAT15.pdf), pages 8–9, checked 15 November 2026, with corroboration from the Authority’s published standard-rate information.