Odoo Changelog — 2024-08-31

Saturday, August 31, 2024

3 changes · 17.0

Improvements(3)

Enhancements to existing features

[FIX] sale_stock_renting: allow visibility days and renting

Enterprise17.0sale_stock_rentingMedium

This fix enables better inventory planning for rental businesses by allowing the visibility days feature to work with rental orders. A new parameter lets users ignore rental returns in forecasts, making it easier to plan weekly stock replenishment and organize warehouse transfers. This requires careful lead time configuration to ensure accurate forecasting of subsequent rental orders.

Original PR description

The case: - I want to organise all my shop in order to be able to serve all the rental orders I planed for a week. And resupply the shop with different interwarehouse transfers The issue, rental…

The case:
- I want to organise all my shop in order to be able to serve all the rental orders I planed for a week. And resupply the shop with different interwarehouse transfers

The issue, rental orders create a retun picking directly and their forecast could easily reach zero. (even more on small renting period)

An existing solution:
Correctly set a small lead time on reordering rule in order to have a fix day in order to have the forecast. However it only works if people check the replenishment report everyday and don't have weekend. And if they use automatic RR they lose the control over the warehouse that should resupply the product.

Also they can't use the visibility days feature and plan for a week.

In order to allow a better planning and flexibility we add a small parameter to ignore the returns of rental order. That way the forecast ignore returns and allow visibilty.

BUT it's DANGEROUS. Because it means that outgoing after return won't be correctly forecasted. So the user have to use a small lead time. E.g. Global lead days = 70 days, do a rental order in 10 days (for a day) and another in 20 days. With the parameter enable, it will suggest 2 units. However it should be one since one is returned.

#rental#forecasting#inventory-planning#replenishment#visibility-days

[IMP] l10n_mx_edi_website_sale: payment way many2one field

PR #68902

Enterprise17.0l10n_mx_edi_website_saleMedium

This update adds a payment method selection field to the website checkout process for Mexican customers. This ensures that the required "Payment way" information is captured during purchase, which is mandatory for electronic invoicing compliance and helps prevent invoice cancellation requests due to missing information.

Original PR description

This commit adds the field `l10n_mx_edi_payment_method_id` to the website checkout, so that the customer can choose the correct option to be saved into the sale order and to fill the attribute in the XML.

Purpose:
In Mexican electronic invoicing, some fields are mandatory for signing an invoice. Now, on e-commerce, one field is missing to avoid requests to cancel invoices due to lack of information. This missing field is "Payment way" (l10n_mx_edi_payment_method_id).

This commit also restructures the placement of `t-if`/`div`s so that they appear in the right places and not generate empty divs.

task-id: 4064069

#Mexico#e-commerce#invoicing#compliance#checkout

[IMP] l10n_nz: Localization improvement

PR #62591

Enterprise17.0account_reportsl10n_nzMedium

This update enhances the New Zealand localization in Odoo by translating key terms and improving how tax information appears on invoices. Invoices will now be properly marked as "tax invoices" with clearer tax labels, making them more compliant with New Zealand requirements and easier for users to understand.

Original PR description

This commit brings out some more improvement to
the New Zealand localization.
It will mostly be about translating a few terms,
improving tax labels on invoices and mark invoices as "tax invoices".

Task id #3753652

#localization#New Zealand#invoices#tax compliance

The case: - I want to organise all my shop in order to be able to serve all the rental orders I planed for a week. And resupply the shop with different interwarehouse transfers The issue, rental orders create a retun picking directly and their forecast could easily reach zero. (even more on small renting period) An existing solution: Correctly set a small lead time on reordering rule in order to have a fix day in order to have the forecast. However it only works if people check the replenishment report everyday and don't have weekend. And if they use automatic RR they lose the control over the warehouse that should resupply the product. Also they can't use the visibility days feature and plan for a week. In order to allow a better planning and flexibility we add a small parameter to ignore the returns of rental order. That way the forecast ignore returns and allow visibilty. BUT it's DANGEROUS. Because it means that outgoing after return won't be correctly forecasted. So the user have to use a small lead time. E.g. Global lead days = 70 days, do a rental order in 10 days (for a day) and another in 20 days. With the parameter enable, it will suggest 2 units. However it should be one since one is returned.

This commit adds the field `l10n_mx_edi_payment_method_id` to the website checkout, so that the customer can choose the correct option to be saved into the sale order and to fill the attribute in the XML. Purpose: In Mexican electronic invoicing, some fields are mandatory for signing an invoice. Now, on e-commerce, one field is missing to avoid requests to cancel invoices due to lack of information. This missing field is "Payment way" (l10n_mx_edi_payment_method_id). This commit also restructures the placement of `t-if`/`div`s so that they appear in the right places and not generate empty divs. task-id: 4064069

This commit brings out some more improvement to the New Zealand localization. It will mostly be about translating a few terms, improving tax labels on invoices and mark invoices as "tax invoices". Task id #3753652