-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inaccurate Insufficient Stock Error in Checkout Flow: Unable to place multiple order for the same product #1175
Comments
Hi supreetha789, I have an extra question if the shipping/billing addresses for these orders the same? I mean the country. |
Hi @szczecha |
supreetha789 I am having trouble reproducing your issue.
channel A:
shipping A:
product
variant:
By following the steps, I can create a second order. |
@szczecha The only difference I can spot in the configuration is that Allocation strategy: Prioritize warehouses by sorting order. |
@supreetha789 Ok, I think I reproduce the issue but with diffrent quantities. Variant:
Thanks for reporting |
We are currently experiencing an issue in the Saleor version 3.17.2 checkout flow related to the creation of orders. Specifically, when attempting to create an order for a product that has a previously placed but unfulfilled order, the system returns an "insufficient stock" error, even when there is available stock according to the Checkout create response.
Steps to Reproduce:
Expected Behavior:
The system should allow the creation of a new order for a product, as long as there is available stock according to the Checkout create response.
Actual Behavior:
An "insufficient stock" error is encountered, despite the availability of stock in the Checkout create response.
Screenshots:
Environment:
Saleor Core Version: 3.17.2
Additional Information:
This issue does not occur when there is no previous order for the product, and the Allocation is 0.
Note:
We have a single channel and a single warehouse in our configuration.
The text was updated successfully, but these errors were encountered: