Skip to main content

Product Types

Mimeeq products fall into distinct architectural types that determine how the configurator works, what the user experience looks like, and how products relate to each other. Understanding these types is important when choosing embed approaches, interpreting API data, and building custom UIs.

There are two independent dimensions:

  • The interaction model (Standard, Hybrid Modular, Full Modular)
  • The product role (Standard product vs Component product)

These dimensions are related but not the same.

Standard (Variant)​

A standard product is a single item with configurable options — colors, materials, sizes, features. The product's structure stays the same regardless of what options the user selects; only the attributes change.

In API data, standard products have:

  • mode: 'VARIANT'
  • variantType: 'STANDARD'

This is the most common product type and the simplest to integrate. One embed loads one product, the user configures options, and the finish event fires a single product payload.

Standard products are fully autonomous — they can be embedded independently and may also be used inside hybrid or full modular configurations.

Hybrid Modular​

A hybrid modular product looks and behaves like a standard configurator from the end user's perspective — they select options from panels, not place products manually on a scene.

In API data, hybrid products have:

  • mode: 'VARIANT'
  • variantType: 'HYBRID'

Under the hood, however, the system attaches, removes, or swaps products automatically using snap points and configuration rules. These products may be either:

  • Standard (VARIANT) products
  • Component (COMPONENT) products

This process can be recursive — a product attached through rules may itself trigger additional attachments.

From an integration perspective, hybrid products behave like standard products. The finish event, pricing, and embed attributes work the same way. The key difference is that the 3D structure may change as options are selected.

Hybrid products require the modular licence in addition to the standard product licence.

Full Modular​

A full modular product is a spatial configurator where users manually build assemblies by selecting and placing products on a scene. Think furniture systems, kitchen layouts, or office configurations — the user decides which products to add, where to place them, and how to connect them.

In API data, modular products have:

  • mode: 'MODULAR'

The embed loads a scene, not a single product. Users add items from a product list inside the configurator. These items can be:

  • Standard (VARIANT) products
  • Component (COMPONENT) products

The finish event payload contains an elements array with each placed product's configuration.

We recommend displaying modular configurators in a full-width, full-height modal for the best user experience.

Component​

Component products (mode: 'COMPONENT') are products designed to function only as part of another product.

They:

  • Cannot be embedded via mmq-embed
  • Cannot function as standalone products
  • Do not appear independently in product lists

However, they can be used within both hybrid and full modular configurations.

The distinction between Standard and Component products is autonomy:

  • Standard products can function standalone or as part of another product.
  • Component products can only function as part of another product.

This is separate from the interaction model (Standard vs Hybrid vs Full Modular).

Summary​

TypemodevariantTypeStandaloneCan Be Used Inside Other Products
StandardVARIANTSTANDARD✅ Yes✅ Yes
Hybrid ModularVARIANTHYBRID✅ Yes❌ No
Full ModularMODULAR—✅ Yes❌ No
ComponentCOMPONENT—❌ No✅ Yes

Next Steps​