Odoo 17 Discount Bug Fix
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted3 hours ago
We run Odoo 17 Enterprise for a distribution business and rely on a custom module that inserts a separate discount product line on every Sales Order. Lately, whenever I edit an existing order—especially when I add or remove a product—the discount line is sometimes inserted twice, inflating the total. I need the root cause isolated and corrected without disturbing any other Sales Order logic or our broader setup.
Key context
• The duplicate discount shows up only during edits, not when a fresh order is created or when it is confirmed.
• Discount logic is handled through that dedicated discount product/line, not percentage fields.
• Re-writing or replacing the module isn’t necessary; the goal is a targeted fix that keeps current workflows intact.
What I expect
1. Code review of the custom module to trace the double-application trigger.
2. Clean, well-commented patch that prevents the second discount line from appearing.
3. Regression testing on all typical order actions—create, edit (quantity change, product add/remove), confirm—to ensure totals remain accurate.
4. A short report summarising the cause, the changes made, and steps I can follow to deploy on staging and production.
I can provide SSH access to our staging server, the git branch of the module, and sample orders that reproduce the issue. Once your fix passes testing on staging, I’ll move it to production and close the project.
Key context
• The duplicate discount shows up only during edits, not when a fresh order is created or when it is confirmed.
• Discount logic is handled through that dedicated discount product/line, not percentage fields.
• Re-writing or replacing the module isn’t necessary; the goal is a targeted fix that keeps current workflows intact.
What I expect
1. Code review of the custom module to trace the double-application trigger.
2. Clean, well-commented patch that prevents the second discount line from appearing.
3. Regression testing on all typical order actions—create, edit (quantity change, product add/remove), confirm—to ensure totals remain accurate.
4. A short report summarising the cause, the changes made, and steps I can follow to deploy on staging and production.
I can provide SSH access to our staging server, the git branch of the module, and sample orders that reproduce the issue. Once your fix passes testing on staging, I’ll move it to production and close the project.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.