Hello all,
Posting in case I catch the eye of someone who has successfully implemented a B2B Commerce storefront in an org with Revenue Cloud and pricing procedures.
We are seeing inconsistent behavior with the standard Add to Cart button component that uses
from the Commerce Cart API.
Depending on whether the component invokes the API from the PDP or PLP or My List, and depending whether the product has a Product Selling Model associated, we get any number of results:
- It works, or
- Omnichannel inventory is not recognized, or
- We get a 400 error saying "Could not add cart item because: Can't find the requested best price." Note that Lowest List Price is disabled and we aren't in the EU.
This behavior is seemingly at random, there is no consistent pattern across the testing matrix. Note that calling the API via Postman also gets inconsistent results.
We had previously built a custom Add to Cart button using the
resource which was working excellently as a stopgap workaround, but it broke without warning in the early hours of Feb 10th, and now we're in worse shape than before.
It took us repeatedly escalating our client's Premier Support tickets since at least October 2025 just to get a human looking at this, and now we have a human support agent, a product operations director, our AE, and the AE's director trying to escalate this to product experts, but so far we've gotten 1 suggestion each from the R&D and Engineering teams, neither which have worked. We are unable to get a screenshare going and haven't heard back from either team in a week.
To save everyone time on suggestions we have tried:
- Auditing every setting line-by-line in the Commerce setup documentation
- Audited all the assignments, like entitlement policies, pricebook entries, buyer groups, product selling models, etc
- Bringing in our RCA expert to completely rebuild the client's pricing procedure using best practices
- Tried building a 100% OOB pricing procedure, product, pricebook, etc from scratch
- Ensuring Partial storage isn't above capacity
- Disabled "Displayable Fields" beta
- Toggled pricing strategy between Best and Priority
SFDC is logging a new IER and multiple teams are escalating it, so hopefully that gets us the right person who can ask the right questions on this thing.
In the meantime, if anyone has solved this in the past, please let me know what you did.
Thank you!
Hi @Akash Jagdish Gawai, per my original post, we have been engaging Support actively for 5+ months without a resolution. That's why I got on TC on 2/19/26.
