> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/introduction.md).

# How the search works

How the search works, from your products through our search system to the results in your shop.

The plugin replaces the search of your Shopware shop with one that forgives typos, knows synonyms and ranks results by relevance. This page explains in plain words how your products get there, what happens during a search and how quickly changes take effect.

## The path of your products

There are three stations:

1. **Your shop** supplies the product data: titles, descriptions, prices, images, categories, properties.
2. **Our search system** receives this data, prepares it and stores it so that it can be searched in fractions of a second.
3. **Your customers** type a search term in the shop. The request goes straight to our search system, and the results appear in the search overlay and on the search results page of your shop.

Your shop does not have to calculate the search itself. This takes load off it, even with many visitors at the same time.

## Terms: data source and index

The product data of one sales channel and one language together form a **data source**. You can find it in the plugin dashboard under "Sources". From every data source our search system builds an **index**. Put simply, this is a directory of your products that can be searched very fast, much like the index at the back of a book.

For each data source you see, among other things, language, currency, number of products, the mode (Pull or Push) and the last and next indexing. If your shop offers several languages, you need one data source per language and an assignment to sales channel and language (see [Language assignment and subtitle](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/general-settings.md)).

## Pull and Push: two ways for the data

You decide how the product data reaches us during setup.

|              | Pull (default)                                              | Push                                                           |
| ------------ | ----------------------------------------------------------- | -------------------------------------------------------------- |
| How it works | Our search system fetches your product feed itself.         | The plugin in your shop sends the products.                    |
| Requirement  | The feed address is reachable from outside without a login. | Shopware's background processing runs permanently.             |
| Suited for   | Live shops                                                  | DEV and stage environments that cannot be reached from outside |

A **product feed** is a file with all products of your sales channel, similar to a Google Shopping feed. The wizard creates it for you as a sales channel of type "Product comparison". More on this on the page [Installation and setup](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/installation-and-setup.md).

## Daily indexing

During reading in, called **indexing**, your products are completely processed again. This happens automatically once a day. With Pull you set the time in the "Sources" area (field "Automatic indexing (time)"). The run starts within 15 minutes after this time. If you leave the field empty, automatic indexing is off. With Push the daily sync runs through Shopware's scheduled tasks.

You can also read in again yourself at any time: the button "Re-import product data" in the card of the data source starts a complete run. This is always possible, unless the data source is locked by InsightSearch or a run is already in progress.

Depending on the number of products, indexing takes a while. The search keeps working in the meantime. Afterwards the AI preparation needed for the hybrid search may still run (see [AI features](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/ai-features.md)).

## What happens during a search

When a customer starts typing in the shop, this happens:

1. The search overlay in the customer's browser sends the search term to our search system.
2. The search cleans up the term, tolerates typos depending on the search strategy and includes word beginnings. Synonyms you maintain are searched as additional variants.
3. If the search recognizes a known value in the input, such as a brand or a price like "under 50 €", it sets it as a filter. For "Bosch cordless drill" it searches for cordless drills of the brand Bosch.
4. The results are ordered by relevance. The search weighting of the fields, the popularity of the products and your search term rules count here.
5. If nothing is found, the search automatically tries again in a relaxed way, corrects typos and, if you wish, shows replacement products (see [No results](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/no-results.md)).
6. The results appear in the overlay or on the search results page.

How the search deals with typos and several words is set with the **search strategy**: "Standard", "Precise" or "Exploratory". You find the setting in the plugin configuration (see [Plugin configuration](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/plugin-settings.md)).

## Quota "Search requests"

What is counted are the search requests of your customers. Further result pages of the same search, intermediate states while typing and bots are not counted. You can see the usage in the plugin under "Search requests this month" with the values "Current search requests" and "Projected total by end of month".

If the quota is exceeded, the search does not switch off and no automatic extra costs arise. In case of a strong overrun we will contact you to find a solution together.

## How fast do changes arrive?

That depends on what you change.

| Change in the shop                                                                 | When it reaches the search                                                       |
| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| New products, changed texts, prices, stock                                         | With the next indexing (daily at the set time or after "Re-import product data") |
| Price, stock, visibility and deleted products with Push and "Live synchronisation" | After about two minutes                                                          |
| Changes to data fields, data attributes and search weighting                       | After "Re-import product data"                                                   |
| Search term rules and ranking settings                                             | After about a minute, without re-reading                                         |
| Filter settings                                                                    | Up to 5 minutes                                                                  |
| New and changed synonyms                                                           | After a short time (cache, up to a few minutes)                                  |

A deleted synonym may still have an effect until the product data is read in again.

**Live synchronisation** is a switch in the plugin configuration (card "Live synchronisation", "Transfer price, stock and visibility changes immediately", default off). It applies to Push only and always to all sales channels. More under [Push and live sync](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/push-and-live-sync.md).

{% hint style="info" %}
With Pull and the option "Generate in the background", Shopware creates the feed file through a scheduled task. Changes then appear only with the next export run of Shopware, and only after that can our search system read them in.
{% endhint %}

## Continue reading

{% content-ref url="/pages/8LkydItrcfm4cyWHUOAn" %}
[Requirements](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/requirements.md)
{% endcontent-ref %}

{% content-ref url="/pages/1Lxj7Rpj8iUl7dhClF69" %}
[Installation and setup](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/installation-and-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/vvF6Ga5yTsoAzmhrYwnD" %}
[Glossary](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/glossary.md)
{% endcontent-ref %}


---

# 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://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/introduction.md?ask=<question>&goal=<user_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.
