Sale Coupon Multi Use Currency
Bridge module between sale_coupon_multi_use and sale_coupon_multi_currency.
Updates constraint to not allow changing program currency if multi-use coupon is already in use.
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Prevents changing the currency of a coupon program once multi-use coupons have already been generated from it.
This module is a small bridge that combines two other coupon features: multi-use coupons and custom currency on coupon programs. It adds one automatic check on the coupon program screen.
- When a user tries to change the currency of a coupon program that is marked as multi-use and that already has coupons generated, Odoo blocks the change and shows an error message: "Currency can't be changed when there are Multi Use coupons already."
- The check runs automatically whenever the currency field is saved, so no manual action is needed.
- It applies to the
sale.coupon.programmodel, which is the screen where promotions and coupon programs are configured. - The rule only triggers when both conditions are true: the program is set for multi-use and coupons already exist for it. If no coupons have been created yet, the currency can still be changed.
This protects the consistency of already-issued coupons, because their value is tied to the currency that was active when they were created. The module installs automatically when both dependency modules are present.
Models and fields (1)
- sale.coupon.program · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 13.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 13.0
Confirmed on 2026-11-03 in branch 13.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.