Rebuilding the search index after catalog data changes
Key Takeaway
Changes to products, the catalog, or store configuration don't reach shoppers until the search index is updated.
The Commerce search index makes products in a B2B Commerce store searchable and lets shoppers see products on search and category pages. Updating the index, also called rebuilding it, brings your changes to shoppers. You can run a manual update, turn on "Automatic Updates", or create a new index through the Webstore Search Indexes API.
When to update the index
Update the search index before you activate a B2B Commerce store. Update it again after any change to the store configuration or product catalog.
Update the index whenever you change or remove any of these:
- Product or product attribute fields marked searchable, sortable, or filterable
- Values of product fields marked searchable or filterable
- Products in the store's catalog and their translations
- Categories, the category hierarchy, category names, and their translations
- Languages in a store or catalog and their translations
- Products in an entitlement policy
- Product variation grouping
- Sorting rules
- Your org's geolocation
- Names of custom fields on the
Product2object
Price changes are the main exception. If you only modify price books or price book entries, you don't need to update the index, unless you have a sorting rule based on price.
Ana and Ben each lower the price of a helmet by editing a price book entry. Ana's store has no sorting rule based on price, so she doesn't need to update the index. Ben's store has a sorting rule based on price, so he does need to update it.