> 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/user-guides/system-management/search.md). # Search Overview of Emporix search integration options and related documentation. 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.	Universal Search Connector
Search Configuration with Webhooks	Enable webhooks and index-item events, choose a webhook strategy, and prepare Svix before provider setup.	Search Configuration with Webhooks
Indexing Service	Native provider registration, secured and public endpoints, reindexing, and SPLIT vs MERGE strategies.	Indexing Service
Algolia Search Provider	Indexing Service setup for production, webhook testing, and document examples by strategy.	Algolia Search Provider
BatteryIncluded Search Provider	Native Indexing Service setup for production, webhook testing, document schema, and portal search settings.	BatteryIncluded Search Provider

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.emporix.io/user-guides/system-management/search.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.