Daily updates from Odoo
Wednesday, April 9, 2025
7 changes · master
Enhancements to existing features
The update removes or hides settings and features that only apply to certain regions, such as EU or SEPA-related options, when users are outside those regions. This makes Odoo screens clearer and reduces confusion by showing businesses only the options that are relevant to their country.
Original PR description
*= delivery_sendcloud. This **PR** enhances clarity for users by removing settings and features that are irrelevant to their region. Currently, certain elements specific to the EU or SEPA are displayed globally, which can confuse users in other regions where these features do not apply. By hiding these irrelevant elements, the interface becomes more streamlined, improving usability and aligning the modules more closely with user expectations. **task**-4356567 **Community PR**: https://github.com/odoo/odoo/pull/189315 **Upgrade PR**: https://github.com/odoo/upgrade/pull/6885
Website appointment bookings now reuse existing customer and sales lead information when possible instead of creating duplicates. Returning visitors are more likely to keep the same salesperson across bookings, improving continuity for customers and reducing clutter in the sales pipeline.
Original PR description
This commit introduces a mechanism to re-use leads and partners records when appointments are booked on the website. Indeed, before these changes, new partners and new leads were always created, leading to data duplication. This also allows us to re-assign the same salesperson when you book several appointments, easing the sales process and maintaining a single contact point. It was split in 3 different commits: - improve the appointment alert display -> Small UI tweaks - link public visitors and booked calendar events -> Similarly to what we do with event.registrations, which allows us to re-use the calendar.event partner record on subsequent bookings - auto-assign salesperson and re-use leads See underlying commits for details. task-4247031
Partner-specific internal instructions from stock picking records are now visible directly in barcode operations when they have been set. This helps warehouse teams see relevant handling guidance without leaving the barcode workflow, reducing missed instructions and extra navigation.
Original PR description
The partner-specific internal instructions displayed on the stock picking view are now also visible on barcode operations view (if such instructions were set by the user). Task ID: [4268689](https://www.odoo.com/odoo/project/966/tasks/4268689)
The Spanish chart of accounts and related balance sheet reports have been updated to align with 2024 legal requirements. This helps companies using Spanish localization keep their accounting reports compliant with current regulations.
Original PR description
This commit update the Spanish Charts of Accounts, to respect the 2024 legal requirements linked:https://github.com/odoo/odoo/pull/203974 task-4512619
Resolved issues and error corrections
Self-ordering now correctly shares one order when multiple guests scan the same table and choose to pay after the meal. This avoids duplicate or conflicting orders and gives staff and diners a clearer restaurant ordering experience.
Original PR description
When self ordering is setup with pay after meal, and two users scans the same table. The order is now shared between the two users. Taskid: 4489980 X-original-commit: 98f0534
This fixes an issue where completing a manufacturing order through the barcode app could record the full planned component quantity even when only part was actually consumed. Businesses will now see more accurate component usage and inventory records for completed production orders.
Original PR description
Current Behavior ================ When using barcode application, If only a partial quantity of a component is consumed in the production of the final product and the production is confirmed, the…
Current Behavior ================ When using barcode application, If only a partial quantity of a component is consumed in the production of the final product and the production is confirmed, the backend incorrectly reflects the full consumption of the component. Expected behavior ================= Only the consumed quantity of the component should be reflected in the backend, not the full quantity, when the final product is fully produced using a partial component. Steps To Produce ================ - Create a production order for 10 units of a final product, consuming 10 units of a component, and confirm the production. - In the barcode application, add 10 units of the final product and 5 units of the component. - In the backend, the component consumption still shows 10 units, even though only 5 were consumed. Issue ===== With the introduction of PR https://github.com/odoo/enterprise/pull/71776, New move lines were being created and linked to the production if the component's move had a quantity done less than the demand, even if the production was fully completed. Fix === Move lines will now only be created if part of the final product is produced. If the production is fully completed, no new move lines will be created. Task: [4558547](https://www.odoo.com/odoo/my-tasks/4558547)
Code cleanup and technical improvements
Customer recipients are no longer automatically added as followers when sending appointment, HR, and direct debit communications. This keeps followers focused on internal users while making customer recipients clearer and more intentional in messages and templates.
Original PR description
Since [1] customers are given as default or suggested recipients for communications. Both chatter and templates proposes them by default. Followers should now be mostly be internal users that want to receive news from a record while customers should be actively displayed and chosen. In this PR calendar mainly is updated. We know correctly use attendees when mailing events instead or relying always on followers and forced subscription. See also [2] and [3] that already worked on that specific issue. Task-4655022 [1] odoo/odoo#185240 [2] odoo/odoo#201514 [3] odoo/odoo#204326