QuestionQ42

VerifiedContent, CMS, and Storefront

A merchant uses a unified website that supports native Adobe Commerce B2B and B2C through a single store view.

The merchant wants B2B account features, such as negotiable quotes and credit limits, displayed in the site header on every page for logged-in users who belong to a B2B company account.

Each B2B company has its own shared catalog and customer group, while many customer groups for non-B2B customers change. The merchant requires that this not be linked to customer groups.

Which two solutions should the Architect recommend, considering public data and caching?

Choose two
Explanation

Adobe Commerce public-content cache variations should use HTTP Context variables, which form part of the public cache key and must represent a shared audience characteristic rather than an individual user. A boolean context value for B2B-company membership safely separates the cached header variants, while block logic can use that membership to render the B2B account features. This avoids tying the behavior to customer groups or using customer-session data as cached public output.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!