A developer is investigating why a newly created product is not appearing for customers using the SaaS-powered Live Search. The developer has confirmed that the Partial Sync cron job has run successfu

Question

Options

• AScopes feed
• BSales Order feed
• CAdmin user feed
• DCustomer data feed
• ECatalog entity feeds

• A
  76% (39)
• B
  8% (4)
• C
  4% (2)
• D
  12% (6)

Explanation

For Live Search to display a new product, it must know where (store scope) and what (catalog data) to show - the Scopes feed (A) provides the website/store-view context that tells Live Search which storefronts a product belongs to, while the Catalog entity feeds (E) deliver the actual product attributes, categories, and pricing needed to index and display the product. Even though the Partial Sync ran successfully, if either of these foundational feeds has not been fully processed, the product remains invisible to the SaaS search engine. The Sales Order feed (B) is irrelevant because it handles transactional order data, not searchable product listings. The Admin user feed (C) and Customer data feed (D) are also incorrect - they sync backend user credentials and customer account information respectively, neither of which plays any role in product indexing or search display.

Memory tip: Think "Store + Catalog = Search" - Live Search needs the Scopes feed to know where to show products and the Catalog entity feeds to know what to show; everything else (orders, admins, customers) is outside the product discovery pipeline.

No community discussion yet for this question.