What should a business prepare before launching a 3D configurator?

Create one source of product truth

A frequent source of delay is not development but conflicting names, codes, and restrictions across departments. Before building, identify the product information source that everyone can confirm against.

It does not need to be perfect on day one, but it should state the approved name, option range, and owner for every product, module, and option.

• Product models, versions, and applicable markets

• Lists of finishes, materials, parts, dimensions, and accessories

• Images, models, or textures for each selectable item

• SKU, price, lead-time, or sales notes

• The team responsible for maintenance and approval

Turn sales knowledge into executable rules

Many important rules live only in the experience of sales or engineering teams: a size may not work with a finish, or an accessory may only be available on a premium version. These decisions need to become conditions the project team can review and test.

Start with rules that affect purchasing and delivery. Edge cases can follow in later releases.

• Which configuration should be recommended by default

• Which options must appear together

• Which options cannot appear together

• Which choices affect price, SKU, or lead time

• How incompatibility should be explained to the buyer

Agree on handoff before launch

The intended user of a configuration result determines what needs to be output. Website inquiry, dealer use, and Shopify checkout each require a different handoff, so define it before interaction design begins.

• What the buyer does after configuring

• Which buyer and configuration data sales receives

• Whether saved links, PDFs, or configuration sheets are needed

• Who maintains new products and rules

• Which measure determines whether the first release works

Confirm whether 3D assets are web-ready

Having a model file does not mean the model is ready for the web. For each product, record its format, polygon count, material count, texture resolution, units, coordinate system, and component structure. Also identify which parts need to switch independently.

At minimum, prepare an asset register covering:

Asset	What to confirm
Source model	Format, units, scale, coordinates, hierarchy, and usage rights
Web model	Existing GLB/glTF, polygon count, file size, and mobile suitability
Materials	Color, roughness, metallic, normal maps, and texture rights
Scene assets	Floor, lighting, background, camera views, and brand direction
Product data	Models, option codes, prices, inventory, lead times, and markets

If usable models do not exist, list modeling, part separation, optimization, and material production as separate work items instead of hiding them inside frontend development.

Define acceptance before the build

In addition to “the page is live,” specify which configuration paths the representative product must support, which invalid combinations must be blocked, what sales receives after submission, and what mobile loading and interaction targets apply. Specific acceptance criteria keep later revisions measurable.