Product configurator for an online store: what to include in a 2D and 3D estimate
The customer has configured a product on the website, but the sales manager still has to clarify the material, fixings and dimensions. For the store owner, this is a signal: a product configurator should be commissioned as a tool for recording a valid configuration, not just as an interactive image. Otherwise, an attractive screen will leave manual work in the sales process and a risk of manufacturing errors.
The estimate should separate selection rules and order transfer from the preparation of 2D or 3D assets. First, decide what the store should receive: an item ready for payment or a request for review. Then choose the visualisation that will help the customer make a decision. This is how to compare contractors' proposals without inventing a universal price tag.
What a product configurator must do before adding 3D
The configurator must allow only approved combinations of options and save the result in a form that makes sense for ordering. Rotating a model is not necessary to check the compatibility of materials, dimensions and additional components. It is a separate interface feature that can be added to an already defined set of commerce rules.
Dependencies distinguish a configurator from the selection of a predefined variant: a custom product requires checks on limits and mandatory components. Whether each combination needs its own stock keeping unit depends on your business's inventory accounting.
Ask the contractor to show the configuration result in the order: option names and codes, entered parameters, quantity, price or an indication that the price requires confirmation. A preview can be an attachment, but not the only description of the purchase. The sales manager must be able to understand the product's components without opening an interactive scene or questioning the customer again.
How to choose between a form, 2D and 3D for the estimate
A form is suitable when names, dimensions and a specification are enough for the buyer. 2D helps show the arrangement and combination of components from a defined angle. Consider 3D when viewing from different sides genuinely affects the choice and the business is prepared to maintain the necessary models.
Compare the same product logic, changing only the presentation: viewing without placing an order is not equivalent to a calculation that transfers the configuration. The table below will help you prepare a request for an estimate.
| Criterion | Form without a scene | 2D preview | Interactive 3D |
|---|---|---|---|
| Buyer's task | Set parameters and read the component list | Check the appearance from a specified angle | Inspect the shape and details from different sides |
| Source assets | Descriptions, diagrams, option reference data | Approved images or layers | Geometry, materials, textures, scene settings |
| Required work common to all approaches | Validate options and record the configuration | The same logic, plus ensuring the preview matches the selection | The same logic, plus ensuring the model matches the selection |
| Product range maintenance | Update parameters and rules | Additionally: new images and mappings | Additionally: model updates and rendering checks |
| What to check in the demo | Clarity of the selection and summary | Layer alignment, scale and mobile display | Controls, loading and a fallback scenario |
WebGL is a browser interface for interactive 2D and 3D graphics, not a separate configurator format. Its operation also depends on the user's hardware. The 3D budget must therefore include testing on agreed devices, while buyers need a way to complete their selection without a working scene.
Compatibility rules: what to prepare instead of a list of buttons
Document how options interact, the reasons for restrictions and the explanations for customers. These must be approved by a business representative who knows the product: developers should not have to guess at manufacturing constraints.
An option compatibility matrix can start as an ordinary table. For each rule, specify the condition, action and explanatory text. Flag unresolved questions separately: whether the material can be changed after choosing a size, which dependent options must be reset, and whether non-standard values are allowed through a request.
- Mandatory parameters: what is needed for a complete configuration.
- Allowed values and limits: what can be selected or entered.
- Dependencies: which parameters change the availability of others.
- Price: which components are known immediately and which require clarification.
- Responsibility: who approves the rule and future changes.
Assess dependencies, not the number of fields. Resolve undefined rules with the production specialist before finalising the estimate.
Why a disabled button is not enough
Browser-side validation helps the buyer, but does not replace server-side validation before accepting an order. The server must validate allowed values and the meaning of their combination, even if the interface has already done so. This principle is described in the OWASP Input Validation Cheat Sheet.
For the business, this means a specific requirement in the specification: it must be impossible to order a prohibited configuration by tampering with request parameters. The rule also applies to price: an amount sent by the browser must not determine the purchase price on its own. The calculation method and the point at which it is confirmed must be agreed before implementation.
Hypothetical example: a wall-mounted shelving configurator
Imagine a store selling shelving to fit a specified recess. This is a hypothetical scenario, not a GL.ua case study: the buyer enters the width and selects a finish and fixing type. Under the assumptions of this example, concealed fixings are available only for manufacturer-approved dimensions, while an uncertain wall substrate requires consultation.
After the width changes, the previously selected fixing may become unavailable. Rather than silently substituting another, the interface explains the reason and asks the buyer to confirm a new selection. The preview does not determine whether a product is permissible: that is determined by manufacturer-approved rules. Otherwise, the screen will retain a convincing design that cannot actually be manufactured.
For the first version, the store could commission a front-facing 2D preview: width and colour are visible without rotation. If buyers need to inspect projections or side fixings, the team assesses the value of 3D separately. Either version includes a text summary: parameters, finish, fixings and review status.
The acceptance scenario here is simple: change the width, receive an incompatibility message, select an allowed fixing and place the order. Then compare the data in the sales manager's dashboard and the fulfilment document. If the old version remains there, the image demonstration has succeeded, but the configurator has not done its job.
How to separate the visual asset budget
Preparing images or models must be estimated separately from programming. A presentation file or an engineering model does not prove that the assets are ready for web display. The contract should list what the client supplies, what the contractor prepares and who accepts the result.
For 2D, check viewing angles, layer transparency, consistent scale and how size changes are displayed. For 3D, check the geometry, surface materials, textures, viewpoints and the ability to replace parts. Preparing 3D models and integrating them into the store are different tasks, even when one contractor manages both.
GL.ua (Глянець) develops online stores and integrations; this is relevant expertise for connecting a configuration to the catalogue and order. The production of 3D models should be agreed separately with whoever is responsible for visual assets. Having a web developer on the project does not mean modelling is automatically included in their service.
Clarify rights to source files and the viewer's terms of use. An estimate for adding the next product will reveal the recurring costs of maintaining the range.
Where selection ends and ordering begins
The configuration must pass from the configurator to the cart and business management system without losing the meaning of its parameters. For a product ready for sale, this may be an item with a confirmed price. For a custom product, it may be a request that must not be presented as an approved production order.
Agree on a snapshot of parameters at the time of purchase: exactly what the customer ordered, the rules used to arrive at the price and the assets they added. An old order should not be reconstructed solely from the current catalogue: its description may change after options are updated. Identifiers and versions are needed for clarity, not to complicate the interface.
Separately define what happens if the price list changes between saving the configuration and payment. The buyer must see an updated summary, and the sales manager must see the reason for the difference. If inventory is tracked in the business management system, the estimate must include data exchange, handling service unavailability and reconciling the result.
Do not confuse this task with the full process of approving B2B proposals. The configurator defines the product's components; approval determines who authorises a sale and on what terms. If both processes are needed, their connection must be estimated rather than hidden behind the generic label “calculator”.
How to accept the work and protect the budget after launch
Accept the configurator based on agreed orders and error behaviour, not on how impressive the demonstration looks. Before development starts, select a product group for testing and define the expected outcome of each scenario. This will help distinguish an implementation defect from a new request.
- Build an allowed configuration and verify its price, summary and order record.
- Try a prohibited combination, a missing parameter and a value outside the agreed limits.
- Change the initial selection and check all dependent options, messages and previews.
- Open a saved configuration after a change in the price list or an option's availability.
- Complete the selection on a phone, using a keyboard and without the graphical scene loaded.
For SEO, retain a clear product page with a description and ordering terms outside the graphics. Do not turn every arbitrary combination into a separate indexable page without an agreed plan. For performance, test the path to selection and the cart on real mobile devices, not just the smoothness of rotation on a desktop computer.
Which line items an estimate should include
The proposal must clearly separate rule analysis, the interface, validation and calculation, integrations, visual assets and testing. It must also include assumptions, exclusions and the procedure for charging for changes. Compare the same scope of work, not the totals of two documents with different boundaries of responsibility.
The timeline depends on the readiness of rules and assets, access to the business management system and the speed of approvals. Request a dependency plan: what can start immediately and what must wait for a sample or order format to be approved. Licences, file storage, support and product range updates also need responsible owners and a budget.
For a meaningful estimate, prepare a sample product, a compatibility table and the desired order format. Discuss online store development with GL.ua to define the scope of the configurator, integrations and visual component. Starting this way will help you commission the process you need rather than pay for graphics before it is clear what the site will actually sell.
Frequently asked questions
Can the configurator initially be launched for only part of the catalogue?
Yes, if the selected group has agreed rules and a clear path to ordering. Define how buyers will distinguish products with a configurator from standard items so that a partial launch does not create false expectations.
Does the store have to move to another platform?
No: first check whether the required interface can be added and configurations saved on the existing platform. Migration should be based on a confirmed limitation, not simply on the introduction of a configurator.
What about uploading a customer's logo or artwork?
Treat file uploads as a separate scope of work, with format validation, restrictions and controlled access. Displaying artwork in a preview does not mean the file is ready for printing or manufacturing; an agreed review procedure is needed.
Can a saved configuration be shared with another buyer via a link?
This feature can be included, but define how long it remains accessible and what data is visible. A configuration link must not automatically reveal a customer's personal information or grant permission to change their order.
How should the benefits be assessed after launch?
Track completed valid configurations, orders and the reasons why sales managers need to make manual clarifications. Model rotation alone does not demonstrate value; compare the result with the original business objective and account for changes in the product range and traffic.
Just one step to your perfect website



