Glue module between sale_fixed_discount and sale_triple_discount. When both are used on the same line a warning will appear to alert the user that the fixed discount will take priority and it's recommended to only use one.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0This module adds a warning on sales orders when a line uses both a fixed discount and a percentage discount, and ensures the fixed discount takes priority in the calculation.
When you install this module, Odoo shows a warning message on the sales order form if any order line has both a fixed discount amount and one or more percentage discounts filled in. The warning appears as a yellow alert box above the order lines and is only visible in edit mode. It tells you that using both discount types at the same time is not supported, that the fixed discount will be used, and that you should remove one of the discount types to avoid confusion.
The module also changes how the discount is calculated on sales order lines. If a line has a fixed discount, that fixed amount is used to compute the discount percentage, overriding any percentage discounts. Lines without a fixed discount are left to the normal calculation.
This module is a compatibility layer between the fixed discount and triple discount features. It does not add new menus or reports. It only affects the sales order screen and the way discounts are computed on order lines.
Depends on
Models and fields (2)
- sale.order · extends an existing modelshow_discount_warning_label
- sale.order.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/sale-workflow.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.