> 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 & Limits
Understand the difference between Standard, Modular, and Component products, and how each type counts toward your subscription limits.
***
## Product types in Mimeeq
### Standard configurators
Standard configurators are standalone product configurators that can be embedded on your website or shared directly with sub-customers.
{% hint style="info" %}
Sharing products with sub-customers requires a special Mimeeq sharing licence. Contact your account manager if you need this capability.
{% endhint %}
**Key characteristics:**
* Can be embedded independently on any web page
* Can be shared directly with sub-customers through the sharing system
* Work as complete, self-contained configurators
* May also be used as building blocks within modular configurators
**Common examples:**
* A chair configurator embedded on your product page
* A lamp configurator shared with dealers
* An individual desk configurator that customers can access directly
***
### Modular configurators
Modular configurators allow customers to build complex products by combining multiple elements or modules together. There are two types:
**Full Modular:** Customers manually select and arrange individual components to create their final configuration.
**Hybrid Modular:** The system combines elements based on pre-defined rules and appears more like a standard configurator to the user, but is built from modular components behind the scenes.
**Key characteristics:**
* Enable complex product building from individual elements
* Provide flexibility for customisable systems
* Use component products as building blocks
* Create sophisticated, multi-part configurations
**Common examples:**
* A modular shelving system where customers select shelves, panels, and connectors
* A kitchen configurator with cabinets, worktops, and appliances
* A modular furniture set with mix-and-match pieces
***
### Component products
Component products are the building blocks used exclusively within modular and hybrid configurators. They are not embedded or shared independently.
**Key characteristics:**
* Only used within modular configurator systems
* Not embedded standalone on websites
* Not shared directly with sub-customers
* Lighter on your subscription limits
**Common examples:**
* Individual shelves within a modular shelving configurator
* Lamp bulb options as part of a lamp configurator
* Chair seat variations within a modular chair system
* Cabinet door options in a kitchen configurator
***
## How products count toward your subscription limits
Mimeeq counts products in three separate categories:
| Category | What it includes |
| ------------------ | --------------------------------------------------------------------------------- |
| Standard Products | Standalone configurators and those that can be embedded |
| Modular Products | Full modular and hybrid modular configurators (counted as one per modular system) |
| Component Products | Individual building blocks within modular systems |
{% hint style="info" %}
These categories are counted separately, so limits in one category do not affect the others.
{% endhint %}
### Active vs. inactive products
Only active products count toward your subscription limits. Inactive products do not use up product slots — you can keep them in your account and reactivate them at any time.
***
## Choosing the right product type
When creating a product, ask yourself: **"Will this product be embedded on a website or shared directly with sub-customers?"**
{% tabs %}
{% tab title="Yes → Create as Standard" %}
Choose **Standard** when the product:
* Needs to be embedded on a website
* Should be accessible independently by customers
* Will be shared directly with sub-customers
Standard products can also be used as components within a modular configurator — think of "Standard" as anything that needs the capability to be embedded or shared, even if it is also part of a modular system.
{% endtab %}
{% tab title="No → Create as Component" %}
Choose **Component** when the product:
* Is only a building block for a modular system
* Will not be embedded standalone on a website
* Will not be shared independently with sub-customers
Components are lighter on your subscription limits and are the right default for most modular building blocks.
{% endtab %}
{% endtabs %}
**Example scenario:** You are creating a table and chairs set using a hybrid modular approach. The chair also needs its own standalone configurator on your website.
| Item | Type | Reason |
| ---------- | --------- | ----------------------------------- |
| Chair | Standard | Needs independent embedding |
| Table legs | Component | Only used within the modular system |
| Table top | Component | Only used within the modular system |
***
## Managing your subscription limits
### Best practices
1. **Default to Component for modular projects** — unless there is a clear need for embedding, mark modular building blocks as Components
2. **Document your decisions** — keep notes on why products were classified as Standard vs. Component
3. **Review regularly** — periodically audit your products to ensure proper classification
4. **Deactivate unused products** — move products you are not actively using to inactive status to free up limit capacity
### Checking your current usage
1. Navigate to **Settings → Account Information**
2. View your current usage across all three product categories
3. See how many slots remain available in each category
### When to reconsider classification
If you are hitting subscription limits, review your products for:
* Standard products that are only used in modular builds and never embedded independently
* Products planned for embedding that were never implemented
* Building blocks incorrectly classified as Standard
***
## Common questions
Can I convert a Component to Standard later if needed?
Yes, you can change product classifications as your needs evolve. This will adjust your subscription limit usage accordingly.
What happens if I exceed my subscription limits?
You will not be able to activate additional products in that category until you either upgrade your subscription or deactivate existing products.
Do deleted products affect my limits?
No. Deleted products are permanently removed and do not count toward any limits.
Can a Component product be part of multiple modular configurators?
Yes, Component products can be reused across different modular configurator systems.
If I have a hybrid modular configurator, does each component count separately?
No. The hybrid modular configurator counts as one Modular product, and its component parts count separately under Components.
***
## Related topics
* [Embed Types](/configurator/embeds-and-translations/embed-types.md) — embed Standard and Modular product configurators.
* [Modular Products in Blender](/configurator/3d-assets/modular-products-in-blender.md) — prepare components for modular configurators.
* [Sharing as Owner](/configurator/sharing-products/sharing-as-owner.md) — share eligible products with partners.
***
## Need help?
If you are unsure about how to classify a product or need assistance managing your subscription limits, contact your Customer Success Manager or reach out to Mimeeq support.
---
# 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, and the optional `goal` query parameter:
```
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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.