Seven Studio
Prepare product assets, organize variants and define the interactive experience with Seven Studio. Agree the asset-production and configurator implementation scope for your products and destination platform.
A 3D product configurator lets buyers explore a product and choose from its available options in an interactive view. Product assets, selectable variants and application behavior are distinct parts of the project.
Send what you have; not every input is required to start a discussion.
Existing models or CAD, product families, dimensions, materials, finishes and visual or brand references.
An option matrix, product IDs or SKUs, pricing needs, desired behavior, target platform and commerce requirements. Include existing project access where available.
Existing assets may need preparation before they enter a configurator. Agree each deliverable and who implements it.
Modeling covers product geometry; texturing covers materials and finishes. Formats and budgets depend on the destination.
Configurator work covers agreed option mapping and behavior. Finished product renders are a separate image deliverable; asset delivery alone does not include application development.
Identify shared and unique geometry, option groups, finishes and component relationships. Agree naming and product IDs before extending a representative product across the catalog. Conditional rules need a supported implementation; product data is not automatically imported from PIM or ERP systems.
Discuss option selection, visibility and material changes, camera views and annotations. Dimensional changes and product rules need a feasibility check on the chosen platform. Only the behaviors confirmed in the project scope are included.
Destination capabilities differ. These pages explain asset requirements and platform context. Confirm integration feasibility, access and the responsible developer before committing to storefront, pricing, cart or product-data connections.
Start with a representative product and agreed acceptance criteria. Define the target browsers and devices, review rounds and handoff responsibilities.
Review option and variant mapping, materials, views and the agreed behavior. Include import or platform checks where relevant.
Resolve the scoped review points before extending the batch. Agree files, mapping notes and documentation; changes beyond the accepted scope may require additional work.
Use our specialist page for Colengo / oneCORE asset preparation and implementation responsibilities.
Share the product range, available assets, option matrix, desired behavior and target platform. We can identify missing inputs during scoping.
No. Modeling and texturing can be scoped if suitable assets are not available. Existing files need review against the destination requirements.
Variant work can include shared or unique geometry and material options. Agree the product structure, naming and mapping before production.
The engagement can cover assets and agreed implementation support. Application development, commerce connections and ongoing maintenance need explicit responsibilities and scope.
Start with your destination requirements. Platform pages provide context; support for a particular setup must be confirmed. Colengo / oneCORE has a separate implementation page.
Describe the data source, pricing and cart requirements. Access, platform capabilities and integration ownership must be agreed; a connector is not assumed to be included.
Agree a representative product, visual and behavior checks, target devices, review rounds and acceptance criteria. Additional scope may incur charges.
The quote depends on asset readiness, product and variant complexity, behavior, platform work and review requirements. Confirm the deliverables before production starts.
Bring your products, options and destination requirements. We can discuss the assets, implementation responsibilities and review plan.
Discuss Your Configurator ProjectGuides from our 3D production team on this topic.
Nine enterprise product configurator platforms: Threekit, Expivi, Zakeke, ShapeDiver, KBMax, Configure One, DriveWorks, Cylindo, VividWorks, on scalability, integrations, rendering quality and total cost.
Real-time 3D in the browser or pre-rendered product imagery? Cost per variant, load time, AR support and where each approach pays for itself.
The features that separate a real 3D configurator platform from a demo: rules engine, real-time rendering, AR, CPQ and ERP integration.
A step-by-step guide to scoping, modelling, rule-building and shipping a 3D product configurator, from asset preparation to platform choice.