Frequently asked questions

We develop 3D configurators for brands with configurable products. Customers can see the product change as they select colours, materials, dimensions, modules or equipment.

Where needed, we connect the experience to pricing, quotes, AI assistance and business systems. The capabilities included are defined around each project’s products and sales journey.

We work with products offering colour, material, dimension, module or component choices. Examples include furniture and storage, yachts and boats, building systems and industrial equipment.

Suitability depends on more than the industry. We review the relationships between options, the available product data and the decisions customers need to make before defining the experience.

We develop around your product rules, interface and sales journey. We use our existing infrastructure while defining the options and connections around your specific requirements.

Scope, content preparation and access requirements are reviewed before implementation. We do not assume the same setup steps will be enough for every product.

No. Your first priority might be product selection and 3D visualisation. Pricing, AI and integrations can be added where they are needed.

We define the priority products and journeys for an initial release, then plan further collections or capabilities as separate phases. The starting scope is agreed during discovery.

The projects section contains customer case studies and links to live experiences. Each case explains the product range, available choices and project approach.

Interactive demos on this website illustrate capabilities. Their behaviour does not mean that every customer project includes the same features as standard.

If you have models, we review them. If not, CAD files, technical drawings, product photography and dimensions can help us assess the preparation required.

The scope of web-ready modelling, part separation and materials is defined at the start. You do not need every file ready for the first conversation.

We assess the file format, part structure, scale and materials together. Having an existing model does not necessarily mean it can be published directly to the web.

Selectable parts, hidden details and file size affect the work involved. Conversion and preparation requirements are defined after the files are reviewed.

Photographs can support the initial assessment and provide visual references. Additional technical information or drawings may be needed for dimensions, module connections and surfaces not shown in the photos.

We identify any missing information together. Prepared content is reviewed against the product information you provide so it represents the product appropriately.

We review material samples, colour references and any available texture images. Fabric texture, surface reflectivity and the part of the product where a material is applied are considered together.

Screens, lighting and viewing conditions can differ from physical samples. Material and colour approval should therefore use the relevant product information and samples.

We classify product families, shared components, variable dimensions and option lists together. Product codes and consistent naming help align the configurator with your catalogue.

Initial collections and later additions can be planned separately. The data and content needed to introduce new products are defined within the project scope.

We assess geometry, texture sizes and the detail required for the target use. Visual clarity is considered alongside loading and interaction performance.

Checks are carried out on target phones, tablets and desktop devices. A single file size, loading time or frame rate is not promised for every product and device.

Depending on the product, options can include colours, materials, dimensions, modules, accessories and equipment. Moving components and alternative layouts can also be considered within the agreed scope.

We define how each choice affects the 3D appearance, product code and any pricing calculation. Minimum and maximum dimension limits can form part of these rules.

We define which parts can and cannot be selected together using product rules. Depending on a chosen dimension or module, alternatives can be disabled, explained or adjusted as agreed.

Accurate rules require information from your product team. We review selection scenarios and their pricing effects together before launch.

CPQ brings configuration, pricing and quote preparation together. While the 3D configurator presents the chosen product and its options, CPQ connects those selections to commercial rules.

A project can use 3D selection alone or connect it to pricing and quotes. The connection is defined around your products and sales process.

Rules can use price lists, dimension-based formulas and additional module or material costs. We define the data behind the calculation and the source of future updates.

Taxes, currencies, equipment and validity conditions are considered separately. We review whether the calculations match your product and sales terms.

Different price lists, dealer terms and customer-group calculations can be considered within the project scope. We also plan who can see which information.

Permissions, currencies and price update sources are defined separately. These are not assumed to be ready-made or identical in every project.

Product codes, dimensions, materials and equipment choices can be linked to a quote summary. PDF layouts, email enquiries or CRM connections are planned as required.

Who reviews a quote and where the sale continues are defined within the project. Illustrative prices on this website are not binding quotations or Viscore service fees.

AI Assistant helps customers understand options and manage the configurator through conversation. Its scope is defined by the product information and actions it supports.

AI Render visualises the selected product in different environments and scenes. The two capabilities serve different needs and can be considered separately.

We define the information sources and supported actions at the start of the project. Product rules, compatibility checks, user approval and follow-up questions form part of those boundaries.

Handling for unclear or out-of-scope requests is planned. An assistant is not assumed to know every fact correctly or have unlimited ability to act.

AI Render supports visual presentation and environment exploration. The resulting scene, material appearance or product details may differ from the physical product.

Verified product information should be used for dimensions, manufacturing, installation and technical suitability. We plan image generation and review steps with this distinction in mind.

The AI Assistant example uses predefined commands and does not include a live open-ended chat connection. Scenes on the AI Render page illustrate the capability.

Live AI services, information sources, providers and any variable usage charges are defined separately for the real project.

We can assess placement on your product page, an experience opened through a link, or a domain or subdomain used by your brand.

The right method depends on your web infrastructure, access and user journey. Publishing arrangements and responsibilities are defined during the technical review.

The chosen product code, options, quantity and price can be mapped to your store products and passed into a cart. Payment and delivery continue in your existing e-commerce system.

We do not promise a ready-made connection before reviewing the platform’s data structure and integration capabilities. Mapping and scope are agreed together.

Depending on the requirements, this can include quote requests, customer contact details, product and part codes, price lists or availability. We define the direction of data flow and which system is the source of truth.

API access, permissions, update frequency and error handling are reviewed during technical discovery. They form part of making the connection work and stay current.

We adapt logos, colours, typography, product names and selection steps around your brand. This is our White Label approach: a branded interface and user journey.

We define the languages required, product content to translate and selections to preserve when switching languages. Multilingual scope involves more than button labels.

The publishing address, hosting requirements, technical access and operational responsibilities are agreed within the project. Your existing infrastructure and integration needs influence that decision.

Any hosting, licence and third-party usage charges are considered separately from development and maintenance. These conditions should be clear in the project proposal.

A short description of your products, available options and the sales experience you want to improve is enough. A catalogue, product page or example product can help us get started.

Existing 3D files, price lists and system details help with later assessment. We can identify missing preparation together; you do not need to send every file in your first message.

We begin with discovery and scope, then plan 3D content and experience design. Product rules and the necessary connections are developed, followed by testing and joint review before launch.

Post-launch maintenance and further needs are planned separately. Stage outcomes and the information required from you are defined through the process.

Product families, relationships between options, model preparation, pricing rules, AI and integration needs all affect the scope. Review and approval steps are also included in the timeline.

We therefore do not give one fee or fixed delivery period for every project. Once the scope is clear, initial development, maintenance and any additional usage charges are considered separately.

Your product and sales information is the basis for dimensions, options, compatibility and commercial terms. We compare the prepared visuals, rules and calculations with that information during joint reviews.

Viscore carries out technical checks, while the relevant customer teams need to review product and pricing accuracy. Pre-launch checks and approvals are agreed together.

Technical maintenance, content updates and new capabilities are different types of work. The updates covered by maintenance, support channels and working arrangements are agreed separately.

We review and prioritise the work required for new collections, options or system connections. New capabilities are not automatically assumed to be included in the maintenance fee.

3D content, application access, documentation and usage rights to be delivered are defined in the project agreement. Rights in your existing files and third-party content are also considered.

Source code, licensing, hosting and future changes are not determined by a general marketing page. These points should be agreed during the proposal and contract stage.

When you choose Send enquiry, your details are securely submitted to the server and emailed to our team. A confirmation appears when the email service accepts the message.

The homepage, project enquiry and partnership forms use the same delivery service. If sending fails, your details are preserved so you can try again or contact us directly by email.

A necessary browser record without personal form data remembers your preference. Google Analytics loads only after your explicit consent; advertising tracking and embedded external media are not used.

The preference record is valid for 180 days. You can change Analytics permission or delete the record through Cookie preferences in the footer. FAQ search runs in the browser and does not send your search text to the server or Analytics.

The Viscore website presents solutions and project examples. Displaying a product does not mean that Viscore sells it or provides its warranty.

Live customer projects may have their own usage and privacy terms. Discuss orders, payments, manufacturing and delivery with the relevant manufacturer or seller.

You can send an enquiry on Start a project or email [email protected] directly. Include your product range and the problem you want to solve to help with an initial review.

Do not share sensitive personal information that is unnecessary for the first conversation. Final project scope and commercial conditions are decided after a joint assessment.