Adobe Live Search B2B configuration and resync runbook

2024-08-31 · Ben Williamson

When search "breaks" after down-sync

Category pages return empty facets. PLP filters disappear. B2B login-gated catalogs look like they lost half the catalog. The instinct is to blame Live Search. On B2B Adobe Commerce stacks, the pattern is more often: config scope flags wrong per website, then stale feeds amplifying the mistake.

This runbook is what I walk after pulling config into a B2B staging environment before declaring search broken.

Per B2B website checklist

Fix store-view scope flags before resyncing anything:

  • Design → Store View → Breeze: disable acceleration on account and password routes where login-gated B2B needs uncached responses.

  • General → Web: website restrictions aligned with login-gated B2B (not accidentally open while catalog rules assume logged-in buyers).

  • B2B features: shared catalog disabled when not in use; orphaned shared-catalog rules hide facets unpredictably.

The flag I most often forget: Breeze disabled paths on account routes. Resync does not fix acceleration caching a logged-out PLP shell.

After config changes: flush, reindex, resync

Run SaaS feeds in dependency order. Skipping attribute or scope feeds breaks downstream product documents:

bin/magento indexer:reindex
bin/magento saas:resync --feed productattributes
bin/magento saas:resync --feed products
bin/magento saas:resync --feed scopesCustomerGroup
bin/magento saas:resync --feed scopesWebsite
bin/magento saas:resync --feed prices
bin/magento saas:resync --feed productoverrides
bin/magento saas:resync --feed variants
bin/magento saas:resync --feed categories
bin/magento saas:resync --feed categoryPermissions

productattributes and scope feeds underpin everything else. If those timestamps are stale, product and category feeds look fine in admin while storefront facets lie.

Debugging mindset

Triangulate three signals before blaming the catalog:

  1. Magento indexer health (indexer:status, stuck working rows).

  2. SaaS feed timestamps in admin (fresh vs hours old).

  3. Storefront facet behavior on the specific store view, not default only.

Once all three agreed except facets on one website, the culprit was a scope flag on that website's store view, not indexer corruption. Resync after fixing scope cleared it.

Quick review

  • Breeze and website restrictions correct per B2B website?

  • Feeds resynced in dependency order after config pull?

  • Tested on the affected store view, not admin default?