Magento and Adobe Commerce 3D product configurator

Connect the Commerce product to the exact design your customer accepted.

Configurix connects complex product rules, made-to-measure inputs, real-time 3D and saved revision identity to a scoped Magento Open Source or Adobe Commerce cart, quote and order journey.

Plan a Commerce demo Explore ecommerce configuration

Configurable productsProduct rulesGraphQL or storefrontCart or quote

Configured Commerce item

Merchandise + saved revision

Validated

Parent SKU

BIO-PERGOLA

Child SKU

BIO-A-XL

Configuration

CX-6042 · rev 3

Dimensions

5.5 × 4.0 m

Customer group

Trade EU

Workflow

Cart after review

Continue with the accepted revision

Integration patterns

Choose the Commerce path that matches how the product is actually sold.

A product-page journey, headless GraphQL storefront, quote-first process and hybrid route solve different catalogue and buying problems. They can share one governed Configurix design record.

Commerce product-page journey

A Configurix experience is embedded in or launched from the agreed Magento or Adobe Commerce storefront surface. The buyer completes a valid design before an eligible parent product, child SKU, quantity and saved configuration reference move toward cart.

Useful when a configured result can be represented by a sellable Commerce item and continue through checkout.

Headless GraphQL storefront

A custom or headless frontend coordinates Commerce catalogue and cart operations with Configurix rules, real-time 3D and saved project services. The contract defines selected options, customer authorization, price ownership, errors and retries.

Useful for composable storefronts that require a controlled experience beyond a conventional product template.

Configure and request a quote

The buyer submits a complete configuration for sales, technical or commercial review instead of being forced into immediate checkout. Dimensions, options, image, buyer context and the saved revision remain connected to the opportunity.

Useful for installed, engineered, surveyed, account-priced or high-value configurable products.

Hybrid cart and project flow

Standard validated combinations can proceed to cart. Nonstandard dimensions, restricted destinations, installation services or technical-review rules route the same saved design into a quote or consultation path.

Useful when one catalogue contains both ecommerce-ready variants and project-based made-to-order products.

Source of truth

Let Commerce own commerce and Configurix own the product design.

Configurable products and customer groups are useful commerce concepts. Continuous dimensions, geometry rules and saved project revisions need a product system designed for that state. Every shared decision receives one explicit authority.

DecisionAuthorityRecord

Catalogue and merchandise

Adobe Commerce

Product, configurable product, child SKU, attributes, store view and availability

Configuration validity

Configurix rule engine

Dimensions, dependencies, exclusions, quantities, required choices and review states

Real-time visual state

Configurix 3D bindings

Geometry, materials, component visibility, approved animation and visual revision

Displayed and transacted price

Agreed commercial owner

Base item, configured additions, customer group, website, currency, tax, discount and service

Saved product design

Configurix project service

Stable configuration ID, revision, structured state, image and reopen policy

Cart and checkout

Adobe Commerce

Cart identity, product or child SKU, selected options, quantity, customer and checkout

Quote and approval

Configurix workflow or agreed CPQ

Buyer, account, configuration, commercial context, proposal, owner and status

Order and fulfillment

Agreed system of record

Commerce order item, configuration reference, ERP mapping and optional operational data

Configured-item contract

The cart should recognize the merchandise and retrieve the full design.

Adobe Commerce receives the identity and options needed for commerce. Configurix preserves the validated state and revision needed by the customer, sales and operations.

parent_sku

Configurable or base Magento product that represents the customer-facing product family

child_sku

Eligible simple-product SKU when the selected attributes resolve to a tracked variation

selected_options

Commerce option identifiers required to represent the chosen configurable-product variation

quantity

Requested commerce quantity, kept distinct from quantities derived inside the configured product

configuration_id

Stable Configurix identity for the accepted product design

configuration_revision

Explicit version referenced by cart, quote, order, customer service and operations

configuration_summary

Permitted customer-readable dimensions, finish and primary selections

price_context

Website, store view, currency, customer group, quantity, tax posture and calculation version

visual_reference

Approved image associated with the same accepted configuration revision

reopen_url

Controlled route that restores the correct design under the agreed access policy

workflow_mode

Cart, quote, consultation, technical review or another supported outcome

integration_version

Version of the storefront, payload, extension and order-item mapping contract

Implementation blueprint

Model the configured-product contract before modifying the storefront.

Product and SKU mapping, rule authority, price ownership, saved revisions and cart or quote behavior should be explicit before the visual interface is connected.

Classify

Separate Commerce products from configured product state

Decide which choices are Adobe Commerce attributes or child SKUs, which remain Configurix fields and which values are calculated or operational.

Model

Create the authoritative product rules

Define ranges, increments, dependencies, exclusions, defaults, required accessories, derived quantities and technical-review conditions.

Visualize

Bind valid state to browser-based 3D

Connect accepted fields to geometry, materials, visibility and camera behavior, then test minimum, maximum and representative combinations.

Price

Choose one authority for every amount

Define base product, configured additions, customer groups, websites, currencies, catalog rules, discounts, tax, shipping, installation, rounding and quote behavior.

Persist

Save the exact design before cart or quote

Create a stable configuration ID and revision, summary, visual reference and policy for reopening after product, rule or price changes.

Integrate

Implement the selected storefront pattern

Map parent and child SKUs, selected options, GraphQL or REST operations, extension data, authentication, errors, retries and order-line display.

Test commerce and project outcomes end to end

Verify rules, known prices, carts, duplicate designs, customer groups, promotions, taxes, quotes, orders, mobile use and accessibility.

Operate

Version and observe the integration

Preserve historical designs, monitor failures and retest Adobe Commerce, storefront, catalogue, rule, pricing and integration changes before release.

Acceptance evidence

Test products, GraphQL carts, prices and saved revisions together.

A 3D experience is ready only when customer choices, Commerce behavior, the accepted price and the quote or order record continue to agree.

Configurable-product mapping

Choose every representative Commerce attribute combination.

The correct parent and eligible child SKU or agreed base item is selected.

Configured-only fields

Change a dimension or option that is not a Commerce variation.

The saved revision changes while merchandise identity follows the defined mapping policy.

Invalid combination

Attempt an excluded or out-of-range product state.

Cart and quote actions stay unavailable and the buyer receives useful recovery guidance.

Known price

Load approved B2C, customer-group, market and quantity cases.

Displayed, quoted and transacted amounts reconcile within the agreed rounding and tax policy.

GraphQL cart

Submit the accepted product, options, quantity and configuration reference.

One intended cart line is created and errors do not produce duplicate or partial lines.

Saved revision

Reopen the design from a cart, quote or service record.

The exact referenced revision is restored or a documented migration or review state appears.

Promotion and tax

Apply supported catalog or cart rules, currency and destination context.

The commercial owner applies adjustments once and records the calculation context.

Order visibility

Complete checkout for an ecommerce-ready configuration.

Customer, admin and downstream records can identify and retrieve the accepted design.

Failure recovery

Interrupt save, price or cart operations and retry.

The buyer sees a controlled state and retry behavior remains idempotent and traceable.

Extension architecture

Use the extension boundary supported by the actual Commerce deployment.

Magento Open Source, Adobe Commerce PaaS, on-premises and Adobe Commerce as a Cloud Service do not expose every extension mechanism identically. Confirm edition, version and hosting before selecting the pattern.

Storefront integration

Theme, custom frontend or headless component coordinates the buyer experience and Commerce cart action.

Commerce API integration

GraphQL or REST operations use scoped authentication, stable identifiers and explicit error handling.

Synchronous validation

A supported webhook or service boundary can validate or enrich an in-process action where the chosen Commerce edition and deployment support it.

Asynchronous events

Adobe I/O Events or another accepted mechanism can notify external workflows after meaningful Commerce events.

App Builder extension

Runtime actions and administration surfaces can support upgradeable integration logic where App Builder is part of the architecture.

Custom module boundary

PaaS or on-premises implementations may use a reviewed module when the required behavior belongs inside that Commerce runtime.

Configurix + Adobe Commerce

Complex visual configuration with a durable commerce and project record.

Configurix models configurable physical products, validates rules, controls real-time 3D and preserves a structured design for prices, quotes, carts, orders and downstream use. Adobe Commerce can remain the catalogue, customer and transaction platform where that is the appropriate route.

Edition, storefront, products, configurable options, customer groups, GraphQL or REST operations, events, webhooks, cart mapping, order data and operations are confirmed against the working system and agreed scope.

Review your Commerce product Explore integration architecture

Primary Adobe Commerce references

Configurable products GraphQL cart mutation Commerce webhooks Adobe I/O Events App Management Commerce performance

Magento configurator questions

Detailed answers for commerce, product and integration teams.

These answers explain how complex product state, real-time 3D, price context and saved revisions can remain connected to Magento Open Source or Adobe Commerce.

A Magento 3D product configurator is an interactive product-selection experience connected to Magento Open Source or Adobe Commerce. Customers change permitted dimensions, components, materials, finishes or accessories while a browser-based 3D scene and structured configuration state update. A complete integration also defines how the accepted design maps to catalogue products, configurable-product options, a cart or quote, price context, saved revision, order record and optional downstream project data.

Not necessarily. Adobe Commerce can remain responsible for catalogue merchandise, websites, store views, customer groups, cart, checkout, tax and orders, while Configurix owns complex product rules, real-time 3D and saved configuration identity. The implementation assigns one authority to every decision. Configurix can also support quote-first workflows where the configured product is not suitable for immediate ecommerce checkout.

An Adobe Commerce configurable product normally represents variation choices through attributes, with eligible combinations linked to simple products and SKUs. A Configurix configuration can hold a much larger state: continuous dimensions, dependent modules, technical rules, optional services, calculated quantities, visual bindings and a saved revision. The integration maps the subset needed by Commerce while retaining the full validated design in Configurix.

Yes, when the selected commerce pattern and product are eligible for checkout. The integration can pass the agreed product identity, selected configurable options, quantity and a controlled reference to the saved Configurix revision. Adobe recommends the general addProductsToCart GraphQL mutation for adding product types to a cart. Exact fields, extension data, authentication, cart errors and order-line persistence are verified against the working Commerce version and storefront.

Yes. A headless frontend can coordinate Adobe Commerce GraphQL catalogue and cart operations with Configurix configuration, pricing and project services. The contract should define canonical state, customer and cart authorization, option and SKU mapping, price ownership, saved-design identity, retries, analytics and failure recovery. The 3D interface should not become a second unaudited source of catalogue or price truth.

Yes, the commercial design can account for Adobe Commerce website, store view, currency, customer group, quantity, catalog or cart rules, tax and other agreed context. The key requirement is explicit price authority. If Commerce owns the final transaction price, Configurix can request or reproduce the relevant context under a tested contract. If Configurix calculates made-to-measure additions, the handoff must prevent another layer from silently recalculating or discounting them twice.

Yes. Configurix can save the complete design and create a quote, consultation or technical-review workflow with customer, account, site, configuration, visual and commercial context. A hybrid implementation can allow standard validated products to enter cart while routing custom dimensions, installation, unsupported destinations or engineering conditions to review. Both outcomes should reference the same stable configuration identity.

The integration can be scoped for Magento Open Source or an Adobe Commerce deployment, but capabilities and extension patterns vary by edition, version and hosting model. Adobe Commerce as a Cloud Service, PaaS and on-premises systems do not expose every event, webhook or App Builder pattern in the same way. The project verifies the actual platform, storefront, modules, APIs, authentication, security controls and operational constraints before committing the design.

Configurix can map the accepted configuration to BOM-oriented, engineering or production data when source item structures, formulas, units, identifiers, effectivity, revisions and destination contracts are defined. The Commerce order should retain the stable configuration reference. Production output is accepted through deterministic known cases and destination acknowledgement; it is not inferred from a visual preview or a generic cart option.

Each saved design should carry a stable configuration ID and explicit revision plus the relevant product, rule, visual and commercial context. The operating policy then determines whether a historical design reopens exactly, migrates with warnings, requires review or receives a fresh price. A quote or order must not silently become a different product because a label, child SKU, option, rule or price changed later.

Use a governed web-asset pipeline with reusable glTF or GLB assets, compressed geometry where appropriate, texture and material budgets, stable binding identifiers and representative device tests. Load the heavier runtime only where it serves the buyer journey, keep useful product content available before the scene is ready and measure Core Web Vitals on the real storefront with consent, analytics, extensions and caching enabled.

Yes, when the product page contains useful server-rendered or crawlable HTML, one canonical URL, descriptive product information and substantiated structured data outside the 3D canvas. Customers should be able to reach and understand controls with a keyboard and assistive technology, receive text validation and complete important actions without relying only on color, motion or precise pointer interaction. The working page is tested against agreed WCAG and performance criteria.

Timing depends on product count, rule complexity, source assets, configurable-product and SKU mapping, price ownership, storefront architecture, quote or cart behavior, documents, integrations and review speed. Configurix offers a focused fast-launch route when inputs are ready and scope is narrow; a multi-product, multi-store, white-label or operationally integrated system needs a broader plan. The timeline follows discovery and written acceptance criteria.

Bring a representative configurable product, continuous or non-variant fields, invalid combinations, known customer-group prices, a saved-design scenario and the required cart or quote destination. Ask each vendor to demonstrate product and child-SKU mapping, rule validation, visual reproduction, price reconciliation, GraphQL or storefront failure recovery, historical revisions and order visibility. Compare working evidence and the operating model rather than unverified conversion claims or plugin-installation speed.

Bring a real Commerce product and storefront

Define how the accepted design becomes a cart line, quote or order.

Book a focused demo