> For the complete documentation index, see [llms.txt](https://docs.hubyte.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hubyte.de/artikel-konfigurator/english-documentation/erste-schritte.md).

# Getting started

## Where do I find the configurator?

Fields are managed centrally in the administration under:

<figure><img src="/files/W2iJg68XK0s0YiURBPxP" alt=""><figcaption></figcaption></figure>

**Catalogues > Article Configurator**

Below it you will find two menu items:

| Menu item                                        | Content                                                                                                                                                              |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Article Configurator – Own/Additional Fields** | Here you create the fields and assign them to products, categories or dynamic product groups.                                                                        |
| **Dependencies of fields with checkbox**         | Here you define that fields are only shown after a checkbox has been confirmed (see [Dependencies](/artikel-konfigurator/english-documentation/abhaengigkeiten.md)). |

## How the plugin works in a nutshell

Unlike Shopware custom fields, the fields here are **created centrally** and then assigned. A single field can therefore apply to one product, to entire categories or to a dynamic product group – you do not have to maintain it on each article individually.

The typical workflow is:

1. **Create a field** – Create a new field in the configurator, choose the field type and settings (see [Creating fields & field types](/artikel-konfigurator/english-documentation/felder-anlegen.md)).
2. **Assign the field** – Define for which products, categories or dynamic product groups the field should appear (see [Field assignment & priorities](/artikel-konfigurator/english-documentation/feldzuordnung.md)).
3. **Optional: price / multiplier** – Add a surcharge or factor to options or number fields (see [Surcharges & multiplier](/artikel-konfigurator/english-documentation/preise-und-multiplikator.md)).
4. **Check in the frontend** – On the product detail page the fields appear above the "Add to cart" button. The entries are added to the cart and to the order.

## The field overview

In the **Own/Additional Fields** list you see all created fields with name, field type, placeholder and info text. Use **Create** to add a new field, or click an entry to edit an existing field.

> **Important:** Fields are maintained per language. Using the **language switcher** at the top right of the detail view you can store name, placeholder, info text and available options per language.

## Recommended workflow

1. Consider which entries you need from the customer (e.g. engraving text, dimension, color, file).
2. Create one field with the appropriate field type per entry.
3. Assign the field to the desired level (product, category or dynamic product group).
4. Mark fields as **required** where needed and define an **order**.
5. Check the result on the product detail page in the frontend.


---

# 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:

```
GET https://docs.hubyte.de/artikel-konfigurator/english-documentation/erste-schritte.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.