> 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/customize-design.md).

# Customize design

Adapt the search to your shop design: custom colours, custom stylesheet, corners, placeholder text, replacement image and notes for agencies.

The search automatically takes over the accent and text colour of your theme. If you want more, you have three levels: set colours via variables, add a custom stylesheet, or replace the default design completely. This page shows all options and is also aimed at agencies.

All settings are in the plugin configuration on the card "Search configuration" and apply per sales channel. You need neither a theme rebuild nor a compilation for them.

## Custom colours

In the field "Custom search colors (CSS variables)" you define the colours. The format is one line per value:

```
--cogi-search-accent-color: #c8102e;
--cogi-search-modal-bg: #fff8f0;
```

Every line ends with a semicolon. A value must not contain a semicolon. Your values win against the plugin's defaults and apply to the window and the dimmed background. They also work in the activation mode "Activate via external trigger".

The field is pre-filled after installation. You see all variables there with their starting value and change only what you need.

| Variable                            | Pre-filled value                                 | Effect                                            |
| ----------------------------------- | ------------------------------------------------ | ------------------------------------------------- |
| `--cogi-search-text-color`          | text colour of your theme, otherwise `#1f2937`   | Text                                              |
| `--cogi-search-muted`               | `#64748b`                                        | Secondary text                                    |
| `--cogi-search-accent-color`        | primary colour of your shop, otherwise `#0ea5e9` | Accent: active filters, links, selection, sliders |
| `--cogi-search-modal-bg`            | `rgba(255, 255, 255, 0.98)`                      | Background of the search window                   |
| `--cogi-search-card-bg`             | `#ffffff`                                        | Background of the product cards                   |
| `--cogi-search-image-bg`            | `#ffffff`                                        | Background behind the product image               |
| `--cogi-search-form-bg`             | `transparent`                                    | Background of the input area                      |
| `--cogi-search-input-bg`            | `#f8fafc`                                        | Input field                                       |
| `--cogi-search-button-bg`           | `#f1f5f9`                                        | Buttons                                           |
| `--cogi-search-button-color`        | `#334155`                                        | Text on buttons                                   |
| `--cogi-search-border-color`        | `#e2e8f0`                                        | Borders                                           |
| `--cogi-search-input-border`        | `transparent`                                    | Border of the input field                         |
| `--cogi-search-scrollbar`           | `#cbd5e1`                                        | Scrollbar                                         |
| `--cogi-search-suggest-hover`       | `#f1f5f9`                                        | Suggestion on hover                               |
| `--cogi-search-suggest-active`      | `#e2e8f0`                                        | Suggestion when marked                            |
| `--cogi-search-filter-hover`        | `#f1f5f9`                                        | Filter option on hover                            |
| `--cogi-search-filter-active`       | `#e2e8f0`                                        | Active filter option                              |
| `--cogi-search-filter-count-active` | `rgba(14, 165, 233, 0.1)`                        | Number on the active filter option                |
| `--cogi-search-focus-ring`          | `rgba(14, 165, 233, 0.25)`                       | Focus ring                                        |
| `--cogi-search-button-shadow`       | `transparent`                                    | Shadow of the buttons                             |
| `--cogi-search-placeholder-color`   | `#94a3b8`                                        | Placeholder text in the field                     |
| `--cogi-search-chrome-bg`           | `#ffffff`                                        | Background of header and frame                    |
| `--cogi-search-overlay-bg`          | `rgba(15, 23, 42, 0.65)`                         | Dimmed background behind the window               |
| `--cogi-search-surface`             | `#f8f9fa`                                        | Surfaces                                          |
| `--cogi-search-filter-panel-bg`     | `#f8fafc`                                        | Filter sidebar                                    |
| `--cogi-search-filter-chip-bg`      | `#ffffff`                                        | Selection buttons of the filters                  |

In addition you can set these variables, even though they are not pre-filled:

| Variable                    | Default                                   | Effect                                 |
| --------------------------- | ----------------------------------------- | -------------------------------------- |
| `--cogi-search-radius`      | set by the plugin (see "Rounded corners") | Rounding of the corners                |
| `--cogi-search-width`       | `clamp(960px, 90vw, 1440px)`              | Width of the window                    |
| `--cogi-search-accent-soft` | `rgba(17, 24, 39, 0.06)`                  | Subtle background in the accent colour |
| `--cogi-filter-max-height`  | `60vh`                                    | Height of the filter bar               |

{% hint style="warning" %}
If you empty the field, the plugin's default colours apply (an almost black accent `#111827` in the light scheme) and no longer your shop's pre-filled accent. Delete individual lines you do not change rather than the whole field.
{% endhint %}

**Example:** A shop with a red brand colour and a warm window background sets

```
--cogi-search-accent-color: #c8102e;
--cogi-search-modal-bg: #fff8f0;
--cogi-search-filter-count-active: rgba(200, 16, 46, 0.1);
--cogi-search-focus-ring: rgba(200, 16, 46, 0.25);
```

The last two lines colour the number on the active filter option and the focus ring to match the accent colour, because these values are pre-filled in blue otherwise.

## Rounded corners

"Use rounded corners" is on by default: corners have a rounding of 0.625 rem. When off, they are square. The setting sets the variable `--cogi-search-radius`. If you enter it yourself in "Custom search colors", your value wins. Cards in the two-column grid on phones are 60 percent as round as the value.

## Custom stylesheet

In the code editor "Custom stylesheet for search" you add your own CSS. It is loaded into the page as a style block after the page has been built and applies per sales channel. It only works if the search is active and the layout is not "Native Shopware design".

This is the right way for things that variables do not cover: other font sizes, spacing, a changed card format or a look for the search field in your theme's header.

## Replace base styling

"Replace base styling with custom CSS" is off by default. If you switch it on, the default design of the search is dropped completely. This only applies if something is in the stylesheet field.

* Your CSS must then provide all rules for window, cards, filters, sliders and so on itself.
* **Deliberately excluded** are the rules for "Filters on mobile devices" and for the mobile designs (panel from the bottom, bars, fixed button). They stay active so that they do not break with custom CSS. See [Search on mobile](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-on-mobile.md).

Use this option only if you want to design the search completely yourself. For almost all cases colours and a supplementary stylesheet are enough.

## Placeholder in the search field

Two fields control the text in the empty search field:

| Setting                                 | Effect                                                                                                                                                                                          | Default                |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| "Search field placeholder"              | One text for all languages.                                                                                                                                                                     | "Enter search term..." |
| "Search field placeholder per language" | One line per language in the format `en-GB=What are you looking for?`. A short code such as `en` applies to all English languages. Lines starting with `#` are ignored, at most 200 characters. | empty                  |

The order: first the exact language, then the short code, then the field "Search field placeholder". If that is empty too, the plugin uses the bundled text "Enter search term...".

{% hint style="info" %}
The placeholder only works in the search field that the plugin creates itself, that is with "Search field always visible" and "Activate via external trigger". With "Use Shopware standard search field" and "Activate via search button" your theme's placeholder stays.
{% endhint %}

## Texts in the window

All other texts in the window are Shopware snippets that you can override under Settings → Shop → Snippets. Their keys start with `cogi-insightsearch.storefront.`. German and English are included. For further languages, create your own snippet set.

Built in and not translatable are: the "ab " (German for "from") in front of from-prices, the "UVP ", the labels "von" and "bis" (from and to) on the sliders, "Suche löschen" and "Logo".

## Replacement image

You choose the "Image for products without an image" from your Shopware media, per sales channel. It appears in the search window, in replacement products and in the shopping assistant when a product has no image or the image does not load. If an image fails to load, it is swapped once for the replacement image. Without a selection a grey placeholder with an image icon remains. Cross-Selling Pro uses the image too if none is maintained there. It does not apply on Shopware's search results page and on category pages.

## Notes for agencies

* **Order of the means:** first variables, then a supplementary stylesheet, last "Replace base styling".
* **Page cache:** The configuration is part of the head of every page. After changes you may need to clear the shop cache until the same is visible everywhere.
* **Check all layouts and the phone** before you go live. Cards, list, compact grid and carousel have different structures.

## Theme conflicts

Heavily customised themes can change the structure of the header or class names. The search overrides the Shopware templates for the header search, the suggestion window, the search results page and the product list. If your theme overrides the same templates, they can get in each other's way.

If the search does not open as expected:

1. Change the activation mode, for example to "Activate via external trigger" or "Activate via search button". See [Search in the shop](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-in-the-shop.md).
2. Check whether a cookie banner or chat window grabs the focus and closes the window.
3. Check whether a security policy or an ad blocker blocks the search.
4. Adapt the look with a custom stylesheet instead of changing the theme.

More steps are on the page [Troubleshooting](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/troubleshooting.md).

## Read on

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

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

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

{% content-ref url="/pages/cPKiMg6nNvV0NE0owXnG" %}
[Troubleshooting](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/troubleshooting.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/customize-design.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.
