Thanks to user feedback, B2B Edition for Stencil Themes (Legacy Experience) now lists every B3 container you can reposition with window.b3themeConfig.useContainers. Before this change, the Customizing page containers section pointed to a containers reference that linked back to the same section.
.container, .button.container, and .button.container--s suffixes mean, and notes that your overrides merge over the defaultsFor details, see Customizing page containers.
Cascading price lists, currently in open beta, now support up to five fallback layers per price list, up from one.
layers array on a price list is evaluated in order. When a price record is not found in the primary price list, each layer is checked in turn and the first match is used before resolving to the catalog price.layers on the create and update Price Lists API endpoints. No new endpoints are introduced.For details, see the Cascading price lists guide.
Fixes an issue in the B2B Edition Merchant Dashboard where increasing a quote line item’s quantity past its backorder threshold did not display the backorder message, showing only the available and backordered quantities.
For details, see the Quotes overview.
Cornerstone 6.22.0 adds a semantic search indication to the storefront search bar, introduces style overrides for the enhanced checkout theme, and includes product page fixes for option set rule messages and stock message styling.
semantic_search_enabled context; falls back to the standard placeholder otherwise. The new copy is localized for all supported languagesWe’re beginning to roll out a fix so creating, approving, or deleting a product review sends a store/product/updated webhook event when the review changes the product’s rating fields. You may notice changes in this area over the coming weeks.
store/product/updated for that product, matching the behavior you already see from the control panel.For the full list of events this webhook scope covers, see Product events.
Docs now includes a Catalog Enrichment section covering how to get good results from the AI enrichment tool in the control panel.
It complements the Catalog Enrichment support article, which documents the procedure. This section covers the decisions the procedure doesn’t make for you: writing brand guidelines, choosing purpose, keywords, and context, assessing source data, grouping products into batches, reviewing results at scale, and measuring impact.
For details, see What is Catalog Enrichment?.
Storefront customer sessions are single-active: signing a customer in again or signing them out invalidates every customer access token previously issued for that account, not just the session that triggered the change.
/login/token/{token}), the GraphQL Storefront API login and loginWithCustomerLoginJwt mutations, and flows built on them, such as a B2B Edition buyer portal sign-in. Sign-out invalidates the customer access token the same way.expiresAt is a latest-possible expiry, not a guaranteed lifetime — a customer access token can stop working earlier than its expiresAt value because the customer signed in again or signed out.customer field returns null, and customer-specific values such as customer-group pricing fall back to guest values. To make such requests return an explicit error instead, send the X-BC-Error-On-Invalid-Customer-Access-Token header with a value of true.null customer response as a signal to prompt the customer to sign in again.For details, see Customer session behavior.
Thanks to user feedback, the V3 Catalog Products documentation now explains that a product’s inventory_tracking value also controls whether the storefront restricts option selection to combinations that exist as variants.
variant tracking gates option-availability filtering — when the store’s out-of-stock option behavior (Settings > Inventory) is set to label or hide unavailable options, the storefront offers only the option combinations that map to a variant with stock greater than zero.none and product keep every combination selectable — regardless of which variants exist, so shoppers can select combinations that have no matching variant.variant tracking to hide non-existent combinations also hides or labels real variants once they sell out.For details, see the inventory_tracking field.
You can now list the storefront API tokens your API account has issued and revoke them by ID, without needing the token’s full JWT string. These operations are available for all three token families: storefront, private, and customer impersonation.
GET /storefront/api-token returns a paginated list of the tokens your API account issued. The JWT string is never returned; each entry includes a jti identifier, is_revoked and is_expired flags, and an optional name label.DELETE /storefront/api-token/{jti} revokes a single token using only its jti.POST /storefront/api-token/revoke-all revokes every active token your API account issued in that family.name - the token creation endpoints now accept an optional name label to help you identify tokens in the list.For private and customer impersonation tokens, swap the path segment to /storefront/api-token-private or /storefront/api-token-customer-impersonation. Revocation can take up to approximately 60 seconds to fully propagate.
For details, see Managing and revoking tokens.
The REST Management API’s Checkout Settings reference now documents every field the API returns, up from seven. The store-level schema covers all 21 fields, and the channel-level schema covers the 18 fields a channel can override.
checkout_type, guest_checkout_type, and guest_checkout_for_existing_accounts, with their accepted values.policy_consent, order_confirmation_contact_email, is_order_terms_and_conditions_enabled, order_terms_and_conditions_type, order_terms_and_conditions_link, and order_terms_and_conditions_textarea.custom_checkout_supports_data_hydration, should_redirect_to_storefront_for_auth, checkout_style_override, and checkout_style_override_sri_hash.support_b2b_settings, returned for stores where B2B checkout settings are enabled.null means a channel has no override and uses the store-level value, and each endpoint has request and response examples.For details, see the Checkout Settings reference:
