> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/ce/system-management/search.md). # Search Emporix Commerce Engine can keep an external search engine in sync with your catalog so products stay searchable on the storefront. Changes to products and related data (price, category, availability, and similar) drive the indexing. How those updates reach the search provider depends on the integration configuration. ## Integration paths You can connect Emporix to a search engine in one of two ways: * **Indexing Service** – You register a supported provider in Emporix. Commerce Engine builds index documents and sends create, update, and delete requests to the provider. Recommended when you use a supported native provider. * **Webhook-based search** – Emporix prepares `index-item` events and delivers them through the Webhook Service (typically by Svix) to endpoints you configure for any search engine. Use when you need custom payload transformation, a provider without native Indexing Service support, or a third-party engine. See the guides in this section to learn more about the search strategies:


Universal Search Connector	Conceptual overview of the webhook-based connector, its features, and the event flow to Svix.	/pages/N9hEuP71dLT6dQA7cEgp
Search Configuration with Webhooks	Enable webhooks and index-item events, choose a webhook strategy, and prepare Svix before provider setup.	/pages/9dQZPeEMaI1jxEtFLOca
Indexing Service	Native provider registration, secured and public endpoints, reindexing, and SPLIT vs MERGE strategies.	/pages/an7XIKOVlhlKw0VgCqmA
Algolia Search Provider	Svix endpoint and transformation setup for Algolia, plus Indexing Service document examples by strategy.	/pages/FWq2sumB8Ep73ic0jGiY
BatteryIncluded Search Provider	Native Indexing Service setup (recommended), optional webhook path, document schema, and BatteryIncluded portal search settings.	/pages/Q5vDLD8zroJ3I6atBO6L

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.emporix.io/ce/system-management/search.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.