> 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/getting-started/product-types-and-limits.md). # Product Types Choose between Standard, Component, Modular and Hybrid Modular products, and understand how reusable products work together. Mimeeq has four product modes: **Standard**, **Component**, **Modular** and **Hybrid Modular**. Choose a mode based on what customers will configure and how the product will be used. ## Choose a product mode * [**Standard**](#standard): configure one standalone arrangement, such as a chair, desk or lamp. * [**Component**](#component): create a reusable product (Element) for use inside a Modular or Hybrid Modular configurators, without its own standalone embed. * [**Modular**](#modular): let customers build an arrangement by choosing modules and where to place them, such as a modular sofa system where the user has maximum control over the placement. * [**Hybrid Modular**](#hybrid-modular): combine reusable products in a parent scene, with options, rules and connection points controlling the arrangement, such as a table-and-chairs set. ## Standard {% hint style="info" %} This is our most popular configurator type and standard configurators still power extremely complex arrnagements, to understand when you need to change a hybrid modulr configurator check [#hybrid-modular](#hybrid-modular "mention") {% endhint %} A Standard product is a standalone configurator with its own options, rules and pricing. Customers can configure it independently through an embed on your website. **Use it for:** an individual product that customers need to configure on its own. **Example:** a chair with choices for upholstery, legs and finish. A Standard product can also be reused inside a Modular or Hybrid Modular configurator. The same chair can have its own product-page configurator and form part of a table-and-chairs scene. [Learn about embedding configurators](/configurator/embeds-and-translations/embed-types.md). ## Component A Component is a reusable product with its own options, rules and pricing, much like a Standard product. It is used inside a Modular or Hybrid Modular configurator and **cannot be embedded independently**. **Use it for:** a building block that only needs to be configured as part of a larger system. **Example:** a sofa module that has its own fabric and leg choices but is only offered within a modular sofa configurator. Components can be reused in multiple configurators. If a reusable product also needs its own standalone configurator, use Standard instead. [Learn about preparing modular products in Blender](/configurator/3d-assets/modular-products-in-blender.md). ## Modular Modular, also called Full Modular, lets customers build an arrangement by selecting products or modules and choosing where to place them at available connections. **Use it for:** systems where customers need direct control over the arrangement. **Example:** a modular sofa. A customer chooses a seat module, clicks an available connection to place it, and then adds a corner or another seat to extend the sofa. The Modular product has dedicated settings and Modular Rules for the assembly. Its reusable building blocks can be Standard products or Components. [Learn about preparing modular products in Blender](/configurator/3d-assets/modular-products-in-blender.md). ## Hybrid Modular Hybrid Modular combines reusable products inside a parent configurator. Customers make configuration choices, while rules and connection points control which products appear and where they are placed. A connection point, also called a **snap**, defines where another product can attach. The inserted products can be Standard products or Components, each with their own options, rules and pricing. **Use it for:** a combined configuration that reuses existing products and controls their arrangement through configuration choices. ### Example: a table-and-chairs configurator 1. **Prepare the reusable products.** Tables and chairs have their own configurators. Use Standard for products that also need standalone embeds, or Component for products used only within a larger configuration. 2. **Combine them in a Hybrid Modular scene.** The parent configurator loads the chosen table and chairs. Connection points on the selected table define the chair positions around it. 3. **Let rules control the arrangement.** Changing the table can change the available chair locations. The chairs are inserted and positioned using the rules and connection points at each level. This lets one Hybrid Modular configurator combine different table and chair models. You maintain the source products, and changes to them are reflected where they are reused. You do not need to build every possible arrangement as duplicated meshes and then hide or show them. Hybrid Modular reuses products and positions them through rules and connection points. {% hint style="info" %} **Modular or Hybrid Modular?** Choose Modular when customers select modules and place them at available connections. Choose Hybrid Modular when their choices determine the products, connections and arrangement through rules. {% endhint %} ## Changing product modes You set the product mode in the **General** tab. The editor shows different tabs depending on the selected mode. You can switch between **Standard**, **Component** and **Hybrid Modular** where your account features, permissions and shared-product restrictions allow. {% hint style="warning" %} Existing products cannot be changed into or out of **Modular** mode through the General tab. Review existing configurations and rules after changing any product's mode. {% endhint %} ## Allowances and session credits Only **active** products count toward your allowances. Standard, Modular and Hybrid Modular products share one **configurator allowance**. Components count toward a separate **Component allowance**. Inactive products do not use either allowance. Session credits measure configurator use separately from product allowances. A session starts when the configurator is fully loaded and ready, and ends when it is unloaded. Standard uses **one session credit**; Modular and Hybrid Modular use **two**. Components are not embedded independently and do not start separate sessions. See [Mimeeq pricing plans](https://mimeeq.com/pricing/) for the allowances included in each plan. ## Related articles * [Embed Types](/configurator/embeds-and-translations/embed-types.md) — choose how customers open a configurator. * [Rules Overview](/configurator/rules/overview.md) — learn how product rules control configuration behaviour. * [Modular Products in Blender](/configurator/3d-assets/modular-products-in-blender.md) — prepare reusable 3D products. --- # 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/getting-started/product-types-and-limits.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.