> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/configurator/product-setup/hybrid-modular-configurator.md).

# Set up a hybrid modular configurator

A hybrid modular configurator sits between a standard and a modular configurator. It combines option-based configuration with reusable components and snaps. Learn how to set one up.

Customers choose options, and rules populate the snaps automatically. Unlike a fully modular configurator, customers cannot click a snap to add a component, and they cannot drag and drop components into the scene.

Use this approach when a component's position or quantity depends on another item in the configuration.

***

## Choose a setup path

For both paths, the main product uses **Hybrid Modular** mode. Choose one path and follow it throughout this guide.

<table><thead><tr><th width="140"></th><th>Path A: tables as components</th><th>Path B: tables in the main product</th></tr></thead><tbody><tr><td><strong>Tables</strong></td><td>Created as products of the <strong>Component</strong> type and added to the main product's components section</td><td>Table geometries and their chair snap points imported directly into the main product</td></tr><tr><td><strong>Chairs</strong></td><td>Created as products of the <strong>Component</strong> type</td><td>Created as products of the <strong>Component</strong> type</td></tr><tr><td><strong>Anchor</strong></td><td>A central scene snap anchors the table, and snaps on the table define the chair positions</td><td>No central scene-to-table connection is required</td></tr><tr><td><strong>Choose it when</strong></td><td>You want each table's models, options and visibility rules managed in a reusable Component product</td><td>You want the table models and their visibility rules managed directly in the main product</td></tr></tbody></table>

Replace the sample names, codes and positions with those required by your own products. The example used throughout this guide is a dining set made of tables and chairs.

***

## Key terms

<table><thead><tr><th width="200">Term</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Snap</strong></td><td>A single-face plane in the model that marks where one item attaches to another.</td></tr><tr><td><strong>Target snap</strong></td><td>The snap that stays in place and receives another item, for example a chair position around the table.</td></tr><tr><td><strong>Source snap</strong></td><td>The snap on the item being attached, for example the central snap on a chair.</td></tr><tr><td><strong>Block name code</strong></td><td>The code of an option block, for example <code>Size</code>. Rules use it to read the selected option. Blocks in the main product and in a component that share a block name code are linked.</td></tr><tr><td><strong>Visibility code</strong></td><td>The code of an individual option, for example <code>4</code> for 4 Seater. A pattern such as <code>{Size#visibility-code}</code> resolves to the visibility code of the selected option.</td></tr><tr><td><strong>Variant code</strong></td><td>Set in a component's <strong>General</strong> tab. A component is shown when the selected option's code matches its variant code.</td></tr><tr><td><strong>Mesh code / snap code</strong></td><td>The <strong>Code</strong> field of a mesh or snap in the Meshes list. Rules match this field, not the mesh name.</td></tr></tbody></table>

***

## When to use hybrid modular

A table and chair set is a good example. The table comes in several sizes, and the selected size determines the number and arrangement of chairs. The customer chooses a chair design, and rules place that design at the relevant snap positions.

Reuse chair components instead of duplicating every chair design in every position. Snaps define the positions, dynamic visibility determines which snaps are shown for the selected size, and an **Always Active** snapping rule attaches the chairs to the visible snaps.

![Finished dining set configurator with a rectangular table and six chairs](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2F8Kdjzt3JHcLzihVjmjkx%2Fhybrid-modular-01.png?alt=media)

![Finished dining set configurator with a long oval table and ten upholstered chairs](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FkdMA2fj0kgyUossOwFdm%2Fhybrid-modular-02.png?alt=media)

***

## Before you start

Prepare the 3D assets in Blender before you create the products in Mimeeq. For general snap guidance, see [Modular Products in Blender](https://help.mimeeq.com/configurator/3d-assets/modular-products-in-blender.md).

| Asset                                                                                   | Path       |
| --------------------------------------------------------------------------------------- | ---------- |
| One central scene snap to anchor the table component                                    | Path A     |
| One central snap for each table component, facing the scene snap                        | Path A     |
| Table geometries in separate collections                                                | Both paths |
| Snaps around each table that define the chair positions                                 | Both paths |
| Chair geometries in separate collections, centred in the scene                          | Both paths |
| One central source snap for each chair component, reused by all instances of that chair | Both paths |

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FrxSXGpobLqseFuvq3MlZ%2Fhybrid-modular-03.png?alt=media" alt="Central scene snap selected in Blender"><figcaption><p>Central scene snap</p></figcaption></figure>

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FMSpE7MU7upmWpLapesLg%2Fhybrid-modular-04.png?alt=media" alt="Central table snap selected in Blender"><figcaption><p>Central table snap, reused across different table sizes and designs</p></figcaption></figure>

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FaN4nFCDTiQyEUlkzA151%2Fhybrid-modular-05.png?alt=media" alt="Chair-position snaps selected around the table in Blender"><figcaption><p>Snaps that position the chairs</p></figcaption></figure>

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FFbt0qbVMhHTLamLA34Rf%2Fhybrid-modular-06.png?alt=media" alt="Centrally positioned chair with its snap selected in Blender"><figcaption><p>Centrally positioned chairs with one shared snap</p></figcaption></figure>

Create each snap as a **single-face plane**. There is no required naming convention, but including **snap** in the name (for example `Snap_Table` or `snap_chair`) makes snaps easy to find in the Meshes list later. No extra export settings are needed.

{% hint style="warning" %}
**Face direction matters.** Snaps attach when their front faces point towards each other. In Blender, turn on **Face Orientation** in the viewport overlays: the front of a face shows blue, or neutral in newer versions. Make sure this side of each source snap faces the same side of its target snap.
{% endhint %}

***

## Set up the configurator

{% stepper %}
{% step %}

### Create the product

Click **New** and enter the main product's name and display name.

Set the main product's mode to **Hybrid Modular**, choose the appropriate visibility and finish creating the product.

![Create Product dialog with Mode set to Hybrid Modular](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FlCR9z1QJiYZL0dG3IWEf%2Fhybrid-modular-07.png?alt=media)
{% endstep %}

{% step %}

### Add the models and define the snaps

Open the main hybrid modular product and go to **3D/AR** > **Model 3D**.

{% tabs %}
{% tab title="Path A" %}
Import the GLB containing the central scene snap. Define the mesh as a **Snap** and set it to **always visible**. The table meshes and chair-position snaps are loaded into table components in the next step.

![Meshes list with Snap\_Start set to type Snap, with Visible checked](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2F9cvBSb8FSv6zldXKT57G%2Fhybrid-modular-08.png?alt=media)
{% endtab %}

{% tab title="Path B" %}
Import the table geometries and their chair-position snaps directly into the main hybrid modular product.

* Assign material definitions to the table geometries.
* Set each size-specific table mesh to **Dynamic**, leave **Visible** unchecked and give it the code for its size option.
* Keep chair-position meshes set to **Type: Snap** and leave **Visible** unchecked. A rule you create in the next step controls their visibility.
  {% endtab %}
  {% endtabs %}
  {% endstep %}

{% step %}

### Create the components

{% tabs %}
{% tab title="Path A" %}
Create a separate product of the **Component** product type for each table design and each chair design.

* **Chair components:** load the chair geometry, assign its material definitions, add its central source snap and set that snap to **always visible**.
* Assign a **Variant Code** in each component's **General** tab. This code links the component to the corresponding design option in the main product.
* Create the size and finish option blocks required by each component. Use linked **option sets** for consistency, and give corresponding main-product and component blocks matching **option block names** so they can be synchronised.
* **Table components:** load the table geometries and assign their material definitions. Set each size-specific table mesh to **Dynamic**, leave **Visible** unchecked and give it the code for its size option. Keep the central source snap as **Type: Snap**, **Visible: checked**. Set chair-position meshes to **Type: Snap**, **Visible: unchecked**, and assign codes for the size and position they represent. Then define the dynamic patterns in rules.

Repeat for all table and chair designs.
{% endtab %}

{% tab title="Path B" %}
Create a separate product of the **Component** product type for each chair design. The tables are already meshes in the main product.

* **Chair components:** load the chair geometry, assign its material definitions, add its central source snap and set that snap to **always visible**.
* Assign a **Variant Code** in each component's **General** tab. This code links the component to the corresponding design option in the main product.
* Create the size and finish option blocks required by each component. Use linked **option sets** for consistency, and give corresponding main-product and component blocks matching **option block names** so they can be synchronised.

Repeat for all chair designs. Manage the table meshes and their chair-position snaps in the main product.
{% endtab %}
{% endtabs %}

![Create Product dialog with Mode set to Component and a Variant Code entered](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FvHyZgjXNXQjSYcuvMSO7%2Fhybrid-modular-09.png?alt=media)
{% endstep %}

{% step %}

### Create the option panel in the main product

Create option blocks for table design, table size, table finish, chair design and chair finish in the main hybrid modular product.

Assign customer-facing blocks to option groups so they appear in the standard option panel.

Then link the design options to their components:

{% tabs %}
{% tab title="Path A" %}
Set each table-design and chair-design option's **Code** to match its component's **Variant Code**.
{% endtab %}

{% tab title="Path B" %}
Match chair-design option visibility codes to the chair components' variant codes. Use the main product's table design and size options to control the table meshes and chair-position snap visibility directly. Match the table-design visibility codes to the corresponding mesh visibility codes.
{% endtab %}
{% endtabs %}

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FHi6N67VOrMfcP59qofkG%2Fhybrid-modular-10.png?alt=media" alt="Chairs Style option set with the Visibility Code column highlighted"><figcaption><p>Option visibility code</p></figcaption></figure>

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FGA6C1lQ33BTtTbzvGTWw%2Fhybrid-modular-11.jpg?alt=media" alt="Component variant code in a component&#x27;s settings"><figcaption><p>Component variant code</p></figcaption></figure>
{% endstep %}

{% step %}

### Add the components

In the main hybrid modular product, open **3D/AR** > **Components** and click **Add**.

* **Path A:** add the table and chair components.
* **Path B:** add the chair components. The table meshes remain in the main product.

Save your changes.

Component meshes appear greyed out in the main product's mesh list. Edit those meshes and snaps in their source components. Their snaps are available for the snapping rules in the main product.

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FG8RFGPxmJWqGDnK0Xczf%2Fhybrid-modular-12.png?alt=media" alt="Components section of the 3D/AR tab listing chair and table components"><figcaption><p>Components added to the Components section</p></figcaption></figure>

<figure><img src="https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FOZ0FrHzmXtyET5IDPiHM%2Fhybrid-modular-13.png?alt=media" alt="Meshes list with component meshes greyed out"><figcaption><p>Greyed-out components in the Meshes list</p></figcaption></figure>
{% endstep %}

{% step %}

### Show the selected component

Open **Rules** in the main hybrid modular product, create a rule and set its trigger to **Always Active**.

Choose **Show Components Dynamically**.

{% tabs %}
{% tab title="Path A" %}
Add a code pattern for the table-design block and another for the chair-design block, for example `{SelectTableStyle#visibility-code}` and `{ChairsStyle#visibility-code}`.
{% endtab %}

{% tab title="Path B" %}
Add the chair-design pattern, for example `{ChairsStyle#visibility-code}`. The table design and size options should control the table meshes directly through a separate, standard dynamic mesh visibility rule.
{% endtab %}
{% endtabs %}

For example, the table option with the code `TABLE_1` shows the table component with the variant code `TABLE_1`. Save your changes.

![Always Active rule with the Show Components Dynamically action and two code patterns](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FmjRkcJ7K2Y4K45EpiuXy%2Fhybrid-modular-14.png?alt=media)
{% endstep %}

{% step %}

### Configure snapping

Configure the core size-dependent connections below with an **Always Active** trigger and the **Snap meshes** action. Use **Basic** for standard snapping, as in this dining set example, or **Advanced** for multi-axis snapping, for example when a chair needs to be tilted at an angle. Optional choices such as adding end chairs can use a separate conditional snapping rule.

Chair-position snap visibility comes from the **Show Meshes Dynamically** rule you created in step 3: in the table component for Path A, or in the main hybrid modular product for Path B.

{% tabs %}
{% tab title="Path A" %}

#### Connection 1: table to scene

Connect the table component to the main product's central scene snap. Select **Basic** and configure the target and source snapping codes:

1. **Target:** select the central scene snap code in the main product, for example `Snap_Start`.
2. **Source:** select the central table snap code in the table component, for example `Snap_Table`.

![Snap meshes action connecting the central table snap to the central scene snap](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FF6rMjcvfkt47CGnF8egB%2Fhybrid-modular-15.jpg?alt=media)

Save the table-to-scene rule, then configure connection 2.

#### Connection 2: chairs to table

Create a chair snapping rule with an **Always Active** trigger, the **Snap meshes** action and the **Basic** snapping method.

* **Target:** select the chair-position snap codes belonging to the table components.
* **Source:** select the chair component's central source snap code. Give interchangeable chairs the same source code (`snap_chair` in the example) so one rule works for every chair design. If your chairs use different source codes, select all of them.
  {% endtab %}

{% tab title="Path B" %}
Skip the table-to-scene connection, as the table meshes are already in the main product.

#### Chairs to table

Create a chair snapping rule with an **Always Active** trigger, the **Snap meshes** action and the **Basic** snapping method.

* **Target:** select the chair-position snap codes imported directly into the main hybrid modular product.
* **Source:** select the chair component's central source snap code. Give interchangeable chairs the same source code (`snap_chair` in the example) so one rule works for every chair design. If your chairs use different source codes, select all of them.
  {% endtab %}
  {% endtabs %}
  {% endstep %}

{% step %}

### Synchronise size and configure finishes

{% tabs %}
{% tab title="Path A" %}
Create a rule in the main product, set its trigger to **Always Active** and choose **Sync Options**.

For example, the main product's block is named **Table Size** and the table component's block is named **Size**, but both use the block name code `Size`. Their displayed names can differ.

Link both blocks to the same global **Table Size** option set. This gives both blocks the same option codes and visibility codes.
{% endtab %}

{% tab title="Path B" %}
The table-size **Sync Options** rule is not required, because the table meshes and chair-position snaps already use the size option in the main product.
{% endtab %}
{% endtabs %}

#### Keep table and chair finishes separate

Option block names control whether a choice made in the main product is passed through to a component. To link them, use the **same** block name in both the main product and the component. To let customers choose the same set of options, such as wood finishes, independently for different items, give each a unique block name, such as **table woods** and **chair woods**.

![Sync Options action with the Table Size block selected](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2F33YJDgCQwFdJcDYkg0DT%2Fhybrid-modular-16.png?alt=media)
{% endstep %}

{% step %}

### Preview the configuration

Open the product preview and check the following:

* Switch between table designs and every available table size. Check the table geometry and the expected chair count for each configuration.
* Switch between chair designs. Check that the chosen design appears at every intended position with the correct position and rotation.
* Switch from a smaller table to a larger one and back again. Check that extra chairs disappear when no longer required, shared central positions remain correct, and no duplicate chairs appear.
* Change the table and chair finishes. Check that each selection reaches the intended meshes and components, and that separate table and chair finish choices remain independent where configured.
  {% endstep %}
  {% endstepper %}

{% hint style="success" %}
When the setup is complete, customers choose a table and chair design from the option panel, and rules place the chosen chair at every position for the selected table size.
{% endhint %}

***

## Troubleshooting

<details>

<summary>A chair is missing, upside down or facing the wrong way</summary>

Check that the source and target snaps face each other with their blue (front) faces, and that the target snap's code is included in the snapping rule.

</details>

<details>

<summary>Chairs appear at positions for the wrong table size</summary>

Check that the snap codes match the patterns in the **Show Meshes Dynamically** rule, and that the chair-position snaps have **Visible** unchecked.

</details>

<details>

<summary>The wrong table or chair design appears</summary>

Check that the option's code matches the component's variant code.

</details>

<details>

<summary>Duplicate chairs appear</summary>

Check that two visible snaps don't share the same position for one size, and that end-position codes aren't selected in both the core snapping rule and the end-chair rule.

</details>

<details>

<summary>The table doesn't change size (Path A)</summary>

Check the **Sync Options** rule, and that the size blocks in the main product and the table component use the same block name code.

</details>

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Modular Products in Blender</strong></td><td>Build modules that snap, collide and measure correctly in Blender.</td><td><a href="https://help.mimeeq.com/configurator/3d-assets/modular-products-in-blender.md">Modular Products in Blender</a></td></tr><tr><td><strong>Rules Overview</strong></td><td>Understand how triggers and actions work together.</td><td><a href="https://help.mimeeq.com/configurator/rules/overview.md">Rules Overview</a></td></tr><tr><td><strong>Actions Overview</strong></td><td>A reference for all actions available in the configurator.</td><td><a href="https://help.mimeeq.com/configurator/rules/actions.md">Actions Overview</a></td></tr></tbody></table>


---

# 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://help.mimeeq.com/configurator/product-setup/hybrid-modular-configurator.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.
