-
Notifications
You must be signed in to change notification settings - Fork 257
Incorrect Backorder Quantity Handling When Adding Same Product to Cart With Different Custom Options #3446
Copy link
Copy link
Open
Labels
Area: CatalogComponent: InventorySalesIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch
Description
Preconditions (*)
- Inventory Metapackage Version: 1.2.8-p3
- Product Type: Simple with Custom Options
- Advanced Inventory > Backorders = Allow Qty Below 0 and Notify Customer
Steps to reproduce (*)
- Create a simple product with custom options.
- Set product stock quantity to 10.
- Enable backorders: Catalog > Products > Advanced Inventory > Backorders > Allow Qty Below 0 and Notify Customer
- On frontend, add the same product to the cart twice, each with a different custom option. For each cart item, set quantity to 20.
Expected result (*)
Cart should show correct stock/backorder distribution per line item:
- First cart item:
- Qty ordered: 20
- Available qty: 10
- Backordered qty: 10
- Second cart item:
- Qty ordered: 20
- Available qty: 0
- Backordered qty: 20
- Total ordered qty: 40
- Total available qty deducted: 10
- Total backordered qty: 30
- Admin order view should also reflect correct split per item.
Actual result (*)
- First cart item shows:
- Remaining / backordered qty = 10
- Second cart item shows:
- Backordered qty = 30
- Instead of splitting based on remaining salable qty in stock, Magento assigns incorrect backorder calculation across cart items.
- After order placement, admin order item quantities also show incorrect backorder distribution.

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: CatalogComponent: InventorySalesIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch