Posted on by

What’s new in Product Configurator v2

3D configurator mode

The headline feature of v2 is native 3D product configuration, powered by Three.js.

  • Choose between a 2D configurator (classic layered images) and a 3D configurator per product.
  • Upload GLTF/GLB models, with support for compressed assets (Draco, Meshopt).
  • Manage a dedicated 3D Objects library: models, lights, and environment maps.
  • Configure the scene visually in the admin with a live 3D preview.
  • Drive the viewer from your existing layer/choice logic with 3D actions:
    • Show/hide objects
    • Switch material variants
    • Apply textures and colors
    • Change material properties
  • Fine-tune the experience with:
    • Environment maps (HDRI presets or custom environments)
    • Orbit controls (polar/azimuth limits, zoom limits)
    • Camera positions linked to angles, including import from GLTF cameras
    • Post-processing (reflections, ambient occlusion, bloom, anti-aliasing)
    • Ground plane and fake shadow, plus optional real-time shadows
  • 3D screenshots can be captured and used as configuration images in the cart.

If you already work with 3D renders or CAD exports, you can now bring those models directly into the configurator instead of relying only on stacked PNG layers.

Global configurators

Manage configuration data more efficiently across many products:

  • Create Global configurators — shared configuration posts that multiple products can reference.
  • Link a product to a global configurator, or keep a local copy.
  • Convert an existing product configuration into a global configurator, or detach into a local copy when needed.
  • WPML-compatible global configurator workflow.

Ideal if you run several products that share the same base options, or if you want one place to maintain a product family’s configuration.

Global layers

Reuse individual layers across products:

  • Create Global Layers (shared layer + choices).
  • Import them into any product configuration.

Useful for common option sets — finishes, sizes, add-ons — that appear on many products.

Redesigned admin experience

The product editor has been significantly reworked:

  • Cleaner navigation with updated icons and layout.
  • Configurator options moved to their own tab.
  • 3D settings integrated into the main editor sidebar.
  • Improved mobile admin UX — slide-in panels, swipe gestures, and smoother navigation on tablets and phones.

Improved data storage

Configuration data is moving to a new chunked storage format (per-layer meta instead of large monolithic blobs):

  • Better performance and reliability for large configurations.
  • Built-in integrity checks.
  • Automatic migration tooling with clear admin notices.

Security enhancements

  • Rate limiting on sensitive frontend actions.
  • Frontend action tokens for protected operations.
  • Optional CAPTCHA support (Cloudflare Turnstile, hCaptcha) for guest users.

Other improvements

  • Add to cart from an existing order (“order again” with configuration restored).
  • Safer JSON handling for stored configuration data.
  • Continued compatibility work across the WooCommerce ecosystem.

Important upgrade warnings

Please read this section carefully before upgrading production sites.

1. This is a major release — test on staging first

V2 introduces new storage formats, new admin UI patterns, and an entirely new 3D pipeline. We strongly recommend upgrading on a staging or development site first, and verifying every configurable product before going live.

2. Automatic data migration on save

When you upgrade, existing configurations will be migrated to the new chunked storage format the next time you save each product.

  • You may see a “Data migration required” notice in the configurator home screen.
  • Legacy data is kept alongside the new format until you confirm everything works.
  • You can then delete legacy data, or restore from legacy if something goes wrong.

Back up your site and database before upgrading.

3. Premium add-ons must be updated

If you use premium add-ons (Extra Price, Conditional Logic, Form Fields, Stock Management, Text Overlay, Save Your Design, Multiple Choice, etc.), you will need v2-compatible versions of those add-ons.

Do not upgrade the main plugin to v2 until your add-ons are confirmed compatible. Mixing an old add-on with v2 can cause missing features or broken behavior — especially in 3D mode.

4. Switching between 2D and 3D is not automatic

The new Configurator type setting lets you choose 2D or 3D per product. These are different workflows:

  • 2D continues to use layered images (your current setup).
  • 3D requires GLTF models, 3D objects, and 3D-specific choice actions.

Changing the type requires updating the product to reload the correct editor. Existing 2D configurations are not automatically converted to 3D.

5. Custom themes and CSS may need updates

V2 includes admin and frontend markup changes. If you use a custom configurator theme or custom CSS targeting the configurator, plan time to review and adjust after upgrading.

6. 3D mode has higher resource requirements

3D configurators load WebGL assets and may use post-processing effects. Consider:

  • Optimised GLTF files (compressed geometry, reasonable texture sizes).
  • Hosting with adequate memory and modern browser support for your customers.
  • Enabling only the post-processing effects you actually need.

7. Global configurators and variable products

Global configurators are not available on variable products unless “Variations share the same configuration” is enabled. Check this setting if you plan to use global configurators on variable products.

8. Global configurators affect all linked products

When a product points to a global configurator, changes apply to every linked product. Use local copies when you need product-specific overrides.

Recommended steps before upgrading

  1. Back up your site and database.
  2. Update all premium add-ons to their v2-compatible releases.
  3. Upgrade on a staging site first.
  4. Open each configurable product, review any migration notices, and save once to complete migration.
  5. Test thoroughly on the frontend: configuration, pricing, add to cart, cart/checkout display, and any quote/request flows you use.
  6. Only delete legacy configuration data after you have verified everything works.
  7. If adopting 3D, start with one pilot product before rolling out across your catalogue.

Resources

Thank you for using Product Configurator for WooCommerce. V2 is the biggest step we’ve taken since the plugin launched, and we’re excited to see what you build with it — in 2D and 3D.