Monday, September 16, 2024
2 changes · saas-17.4
Resolved issues and error corrections
Point of Sale sessions can now open correctly even when stored orders reference products that were not initially loaded, such as after a product category change. This prevents checkout history or pending order data from blocking store staff from starting or resuming a sales session.
Original PR description
Before this commit, changing a product's category, causing it to not load, would result in errors when loading orderlines from IndexedDB due to undefined product_id. This fix ensures missing products are loaded when retrieving orders from IndexedDB. opw-4185964 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where serial-tracked products fulfilled by another company could be recorded in a shared customer location, blocking the selling company from using the same serial number. Inter-company fulfillment now uses the proper transit location and company partner records, helping sales and purchasing flows complete correctly across companies.
Original PR description
**Current behavior:** Using a second company to fulfill a dropship order for a lot-tracked product has an issue where the lot will be placed in the 'customers' location by the fulfiller, preventing…
**Current behavior:**
Using a second company to fulfill a dropship order for a
lot-tracked product has an issue where the lot will be placed in
the 'customers' location by the fulfiller, preventing the seller
from using the lot (as it already exists in this shared
location).
**Expected behavior:**
The lot should be usable by the company actually selling the
product.
**Steps to reproduce:**
*Having a companyA and companyB*
1. Create a product tracked via serial with a dropship route
companyA and buy route on companyB
2. Enable inter-company sale and purchase generation and
auto-syncing
3. Create a sale order form companyA to a customer for the
product
4. Confirm the sale order and purchase orders in companyA
5. Confirm the purchase order in companyB for the product from
the vendor defined on the product, assigning a serial
number and validate the receipt
6. Confirm the sale order and validate the delivery
7. Assign the lot to the purchase order from companyA and try to
validate the picking -> see that you can't use it because
a quant with the lot already exists in the customer
location
**Cause of the issue:**
The 'customer' usage location is company agnostic, so both have
access to it- the lot can't be created there by companyA as it
is already there from companyB.
**Fix:**
For procurement of a sale order which is fulfilling another
company's purchase order, strictly enforce the use of the
inter-company transit location and the partner record of the
respective company.
opw-4163612