Coupon Promotion Discount in Field Order Line Link
Bridge module between Sale Coupon Order Line Link and Sale Promotion Discount in Field
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Bridge module that links coupon promotions to sales order lines when the discount is stored in a field, so the promotion program is recorded on the affected lines.
This is a technical bridge module with no new screens or menus. It connects two other modules: one that links coupon promotions to sales order lines, and one that keeps the promotion discount in a dedicated field on the order line.
When Odoo applies a reward discount to sales order lines, the module extends the existing behaviour on sale.order. After the standard logic determines which lines receive the reward discount, it writes the promotion program onto those lines by setting coupon_program_id. This means each discounted line keeps a reference to the promotion program that generated it.
- No new menus, buttons, reports or settings are added.
- No new models are defined; it only inherits
sale.order. - The automatic behaviour is limited to tagging the affected order lines with the promotion program when a reward discount is applied.
Because the module contains only this small inheritance and no data files, its visible effect depends entirely on the two modules it depends on. It does not add checks, emails, scheduled jobs or default values on its own.
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/sale-promotion.
terminal Installation and usage
OCA documentation · Odoo 14.0Usage
Source · Odoo 14.0No action necessary, module works out of the box.
No verified information in OCA: Installation, Configuration.
Installation 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.