Seeing this on a store of a customer using my app.
Get the same response from the API as those above, even using a clean theme using standard blocks.
Have tried:
Happens across all products. Very clean site with barely any apps installed.
The same here. It happens to one of my users.
I add the product as a bundle component and the cart API gives me 422. When I check the product stock, it’s available. The product detail page shows the product as not available. The add to cart button is disabled on the PDP.
When I check the available field of the product with liquid, it’s available. Therefore, the product shows as available in my bundle widget. I find it confusing and I don’t know what trigger this sold out.
Hi folks - no concrete update to share on this, but it is on our radar to address asap.
Hey @Liam-Shopify, this issue was raised back in December and now its almost 8 months. One of our extremely valued customer who migrated to Shopify (on the Plus plan) have been unable to use bundles and actually get the ROI on this migration purely because of this issue.
I believe it is fair to expect a lot more priority than this issue has been getting so far, and at least get a timeline. This experience has been extremely disheartening, as Shopify Partners this also reflects poorly on us because of the experience the brands we work with have to face.
I am confident that the issue should be relatively straight-forward to resolve, and all it needs is some attention. Can we hope to support the bundle of our customer well before BFCM 2025?
Thanks
Has anyone found a solution?
Still waiting for it to be fixed from the Shopify team though. would be happy to get this fixed before the BFCM season 
Unfortunately it’s still happening. This issue must be addressed ASAP considering the approach of November. It is indeed a surprise Shopify hasn’t taken any action considering the amount of apps and stores affected.
Is there a solution and can someone from Shopify give us an update on this bug?
I’m being reported this by a merchant, he even has the “Continue selling when out of stock” and the Ajax API /add.js returns 422.
Anyone knows what’s up?
There probably is a bug. However, just be sure to check that it’s not catalog restrictions.
The only times I’ve personally tried this have been with B2B catalogs trying to add a product that is not available in that specific catalog.
Thanks for flagging this again folks - unfortunately there’s no plan to address this gap in our API.
Interesting. Is it a known bug (or restriction/gap)?
Based on the thread it seems to pop up randomly; is there a definitive reason when it happens?
Can we get some details on what the gap is and what the recommended alternative is? Are liquid forms for add to cart reliable for adding in stock products?
I’ve also had merchants reporting this error message. When I’ve checked inventory history for the reported variants, inventory quantity has never dipped below zero within the timeframe the issue occurred.
One screenshot I was provided shows an empty cart state, along with the error message “The product X is already sold out.” error message which has been returned by the Shopify AJAX API.
That particular site in question does use line item properties, and I believe there is a third party app which does utilise cart transformation using Shopify Functions, but I am not currently able to reproduce this issue reliably, even when that app is invoked (insurance upsell that modifies the price of an existing line item).
At this point I suspect it is a bug on Shopify’s side. We’re going to have to add logging for this specific error so we can see just how widespread this is among actual customers using the storefront.
Merchants - quite rightly - are very concerned they are losing sales, especially during peak trading this time of year.
Quite concerned that this seems to have been an ongoing issue for many months with no resolution. Is there any clarification from Shopify that can identify the specific scenarios in which this happens and why it (perhaps) is considered an edge case not worthy of prioritisation?
This information would be helpful for partners to be able to relay back to worried merchants.
Is there any workaround for this issue? I have a bundle that has this issue. But I can’t reproduce it from my side, though a customer reported it to me.
The only workaround is to duplicate this product to replace the wrong one?