3D product configurator for Magento and Adobe Commerce

Magento 2, now sold as Adobe Commerce with a free Magento Open Source edition, is built for large catalogs and B2B. It handles standard configurable products well. The trouble starts with 10 or more options, conditional rules or material swaps the customer needs to see.

What Magento offers natively

Magento gives you two tools for product options:

• Configurable products: a parent product with child simple products for each combination of attributes (size, color). Each child has its own SKU, stock and price.
• Custom options: dropdowns, checkboxes, text fields and file uploads that add a fixed or percentage price. They do not create SKUs.

This breaks down when:

• Combinations explode, so you manage thousands of child products
• Options depend on each other (this frame only with these fabrics)
• Price depends on dimensions or combinations, not fixed add-ons
• Customers need to see the result, not a dropdown

Magento configurator extensions

The Adobe Commerce Marketplace and third-party vendors offer product designer and configurator extensions. Most fall into three groups:

• Option dependency extensions: add conditional logic to custom options. Good for forms, no visuals.
• 2D product designers: canvas tools for text and artwork on apparel, mugs and print. A design tool, not a configurator.
• 3D platforms with a Magento connector: SaaS configurators that embed on the product page. Expivi is the best known in this group, popular with European furniture and manufacturing brands and priced by quote. Read our Expivi review for details.

The common limit: extensions that install inside Magento run in your codebase. Every Magento, PHP or theme upgrade is a chance for something to break, and the fix lands on your agency.

Custom development: the expensive route

The other path is an agency building configuration logic directly into Magento. It can work, but you end up owning complex custom code tied to one platform version, for products that change every season. When the developer who built it leaves, so does the knowledge.

A configurator as a separate layer

ConfiguraThor takes a third route. Eyedex builds the 3D configurator around your product and runs it as a separate layer connected to Magento through its API:

1. The configurator loads on the product page at a defined embed point
2. It reads your product data, SKUs and customer group pricing
3. The customer builds the product in 3D and sees the right price for their account
4. On add to cart, the API creates a quote item with the configured product, options and price
5. The order reaches Magento admin with every attribute, ready for your ERP or production

Because it does not live inside Magento’s code, platform upgrades rarely touch it. You do not rebuild your catalog inside another system either. The configurator maps to the SKUs you already have.

When to go beyond an extension

An extension or Magento’s custom options are enough if:

• Your product has a handful of options with no visual impact
• A 2D preview or option summary explains the product well
• You are testing customization on one product line

A custom 3D configurator makes sense if:

• Your configurable products already run into hundreds of child SKUs
• Options have technical dependencies your team checks by hand today
• Visual quality is part of the brand, as with premium furniture, lighting or equipment
• Configurations need to reach an ERP or production system as structured data
• You sell to businesses with account pricing and quote workflows

B2B configuration and quotes

Many Magento stores sell to businesses. Buyers configure, then need a price for their account or a formal quote before ordering. A configuration layer handles both:

• Customer group and tier prices shown while configuring
• A quote request with the full spec instead of a direct checkout, using Adobe Commerce B2B quotes where you have them
• Structured data your sales team can act on, not free-text notes

More on this in our guide to B2B 3D product configurators.

Headless Magento and custom stacks

If you run Magento headless with a PWA Studio or custom frontend, the same approach applies. The configurator is a standalone component that your frontend embeds, and it talks to Magento through GraphQL. One set of 3D models and rules serves your web store, B2B portal or app, so pricing and assets never drift apart. The same holds for other headless backends with a cart API.