Friday, October 11, 2024
4 changes · saas-17.4
Resolved issues and error corrections
The point of sale now ignores loyalty cards linked to archived loyalty programs when loading a customer. This prevents outdated loyalty data from stopping order validation, helping store staff complete sales normally.
Original PR description
Before this commit, loading a partner could inadvertently fetch a loyalty card associated with an archived loyalty program, preventing order validation. This commit ensures loyalty cards from archived programs are not loaded, thus preventing validation issues. opw-4246931 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Self-ordering now shows product prices using the active pricelist, preventing customers from seeing incorrect amounts. This helps ensure displayed prices match the business’s pricing rules during the ordering process.
Original PR description
Before this commit, the pricelist was not considered when displaying product prices in the self-ordering, leading to incorrect pricing information. This commit ensures that the pricelist is correctly applied. opw-4190268 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects how Belgian payroll declarations handle asbestos contributions, commission reporting, and fixed-term contract end dates. It helps payroll teams submit more accurate statutory declarations and reduces the risk of reporting corrections.
Rental orders now correctly calculate delivery transfer quantities when warehouse picking uses a sub-location of stock. This prevents mismatched demand on outgoing transfers after rental order quantities are changed.
Original PR description
**Current behavior:** Using 2 step delivery and modifying the route so the pick action's src location is a child of lot_stock will result in the move not being found by the Procurement mechanism,…
**Current behavior:** Using 2 step delivery and modifying the route so the pick action's src location is a child of lot_stock will result in the move not being found by the Procurement mechanism, which can lead to inaccurate quantity being encoded on transfers created from rental orders. **Expected behavior:** Transfer quantity should match sale order line quantity. **Steps to reproduce:** 1. Enable 2-step delivery in the warehouse 2. In the 2-step delivery route, change the src location of the pick action (pull rule) to be a sub-location of WH/STOCK 3. Enable rental transfers in settings 4. Create a new rental order, add a product, confirm the order 5. Add some quantity to the order line and save 6. Look at the generated out-going picking's moves -> the demand is wrong **Cause of the issue:** The original move created when confirming the order, before editing the order line quantity, is not found when the additional move is created for the modified quantity. Existing outgoing moves are expected to have a location_id (source location) of WH/STOCK (warehouse.lot_stock_id), ours will have a location_id of some sub-location. **Fix:** Check all child locations of lot_stock (which includes lot_stock itself) when aggregating outgoing moves. opw-4178446