Variation Products Not Showing on Salesforce B2B Commerce Storefront

Question

Hi Everyone,

I have created variation products in Salesforce Commerce Cloud and configured the Product Attribute Set. I have also configured the Price Book and Entitlement Policy.

However, my variation products are not appearing on the storefront under the assigned category. I have also updated the search index, but the products are still not visible.

Could someone please help me identify what configuration I might be missing and how to troubleshoot this issue?

Thank you!

#B2B Commerce Cloud #B2B Commerce #B2b Commerce Storefront

Asim Ansari · Accepted Answer

Hi @Pooja Wable https://trailblazers.salesforce.com/profileView?u=0054V00000HQGR1QAP Variation products almost always go missing on a B2B Commerce (Lightning) store because of how the parent and variants are set up, not because of a single missing switch. I haven’t seen your org, so treat this as a checklist in rough order of likelihood. Check in this order Category goes on the parent, not the variants. Assign only the Variation Parent to the category (Catalog → Category → Products). Variants shouldn’t be categorized, and the storefront shows the parent tile with attribute selectors. Also confirm that category’s catalog is assigned to your store ( StoreCatalog ). Parent and variant setup. Parent: Product Class = Variation Parent, IsActive = true , and the Attribute Set is assigned to the parent. Variants: each has a ProductAttribute record pointing to the parent ( VariantParentId ) with values for every attribute in the set. A missing or blank attribute value can silently drop the variant. Entitlement covers parent and variants. This is the most common miss. The policy must include the parent and every variant, be active, and be assigned to a Buyer Group. That Buyer Group must be assigned to the store, and the buyer’s account must be a member of it. Pricing on the variants. Each variant needs an active PricebookEntry in a price book assigned to the store and Buyer Group. The parent doesn’t need a price, but variants without one won’t display or purchase correctly. Search index. Run a full rebuild , not just an incremental update, and wait for it to finish. Changes to category assignment or entitlement often need the rebuild to appear. Publish and test as the right user. If your store is LWR, publish the site after changes. Test as an actual buyer in the entitled account (not as an admin or guest), since guest users need their own Buyer Group and entitlement. Quick diagnostic queries -- Parent is active, has the right class, and is categorized SELECT Id, Name, IsActive, ProductClass FROM Product2 WHERE Name = '' SELECT ProductId, ProductCategoryId FROM ProductCategoryProduct WHERE ProductId = '' -- Variants are linked to the parent SELECT Id, ProductId, VariantParentId FROM ProductAttribute WHERE VariantParentId = '' -- Entitlement covers parent AND variants SELECT PolicyId, ProductId FROM CommerceEntitlementProduct WHERE ProductId IN ('', '') -- Variants are priced SELECT Product2Id, Pricebook2Id, IsActive FROM PricebookEntry WHERE Product2Id IN ('') If the parent appears in the query results but not on the storefront, the problem is almost always entitlement or the index. If the parent shows but variants don’t, look at the ProductAttribute records and variant pricing. I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Asim Ansari · Answer

Hi  @Pooja Wable https://trailblazers.salesforce.com/profileView?u=0054V00000HQGR1QAP ,  Developer Edition is unlikely to be the cause. Its limits (data storage, user and license counts, API limits) would block store creation or record saves, not hide specific products. I haven’t verified current Developer Edition terms for Commerce, so check Setup → Company Information if you suspect a licensing issue. Since your store and catalog exist, I’d look elsewhere.     Commonly missed items (after the ones you’ve checked)   Entitlement policy flags.  On the policy itself, “Active” and “Can View Product” (and “Can View Price”) must be checked. Also confirm the policy is assigned to the Buyer Group ( CommerceEntitlementBuyerGroup ). Buyer Account.  The test user’s Account needs an active  BuyerAccount  record and must be a member of the Buyer Group ( BuyerGroupMember ). Without that, entitlement never applies. Store wiring.  The Buyer Group needs a  WebStoreBuyerGroup  record, and the price book needs a  WebStorePricebook  record. Buyer Group membership and store assignment are separate steps. Variant price book entries.  Each variant needs a Standard Price Book entry first, then an entry in your custom price book. All entries must be active. Variation attribute definition.  In the Product Attribute Set, the attributes must be marked as variation-defining, and every variant must have a value for each one. Variants missing a value are dropped silently. Variant status.  Every variant must be  IsActive = true . A parent with no active, entitled, priced variants may not render. Index state.  Confirm the rebuild finished (Setup → Commerce → your store → Search → check the last index status), not just that you triggered it. Rebuild again after any entitlement or category change. Publish.  If your store is LWR, publish the site after changes. If it’s Aura, publish via Experience Builder as well. Isolating the layer     Instead of guessing, check what the platform actually returns and compare:    Browser dev tools:  Open the category page as the buyer, check the Network tab, and find the call to  .../commerce/webstores/<webstoreId>/search/product-search  (or  /products ). If the parent is in the response but not rendered, it’s a storefront or component issue. If it’s absent, it’s entitlement, index, or category. Search by exact name:  If the parent appears in search but not in the category, the category assignment or catalog-to-store link is the problem. If it appears in neither, it’s entitlement or the index. SOQL:  Confirm  BuyerAccount, BuyerGroupMember, WebStoreBuyerGroup, CommerceEntitlementBuyerGroup,  and  WebStorePricebook  each return rows for your store, group, and account. Quick question to narrow it down     Does a plain (non-variation) simple product, set up with the same category, entitlement, and price book, show up? If it does, the problem is specific to the variation setup (attributes, variants, parent). If it doesn’t, the problem is in the shared wiring above (buyer account, store assignment, index)

Variation Products Not Showing on Salesforce B2B Commerce Storefront

B2B Commerce Cloud

相关学习

更多帮助