Visual commerce
3D & CPQ Systems
A buyer should not be able to see one product while the sales system prices another.
Real-time browser-based 3D is connected to configuration, pricing and quote logic, with agreed integrations carrying the valid product state into the wider sales environment. The product context belongs to Animech; SKWD works as an implementation partner.
- Status
- Active
- Evidence
- Deployed
- Ownership
- Animech product context; SKWD project partner
01 / The operating problem
Complex product sales break when visual choice and commercial logic drift apart.
Buyers need to understand the product they are configuring. Sales teams need valid options and a usable quote. Product and commercial owners need the experience to follow current rules, prices and system records. A 3D and CPQ implementation joins those responsibilities instead of leaving the visual configurator disconnected from the order path.
Participants
A shared configuration layer linking the visual product, valid options, commercial rules and quote data.
System outcomes
Connected modules
- 013D product model
Represents the configurable product visually.
- 02Configuration rules
Controls valid options and dependencies.
- 03Pricing and quote logic
Calculates the commercial result of the configuration.
- 04Sales integrations
Connects configured data to surrounding business systems.
02 / What stays shared
The engine can be reused; every product model and rule set must still be built.
The local source describes the capability family. It should not be read as SKWD ownership of Animech’s product. The reusable and implementation-specific boundaries must be agreed with the product owner for each engagement.
Shared core
Visualization, configuration, pricing and quote flow
The documented foundation links the main stages of complex product selection.- Real-time 3D viewer
- Configuration engine
- Pricing and quote logic
- API connection layer
Configured layer
The manufacturer product and commercial model
Options, assemblies, constraints, prices, currencies and quote rules vary by product and market.- Product hierarchy
- Option dependencies
- Pricing rules
- Quote structure
Connected environment
CRM, ERP and commerce systems
The implementation must define which system owns product, price, customer, quote and order data.- CRM
- ERP
- E-commerce
- Product or asset data
Implementation work
3D assets, business rules and data contracts
A real delivery requires model preparation, rule definition, integration and commercial-data governance.- 3D asset pipeline
- Rule mapping
- API contracts
- Data ownership
03 / What the platform enables
Capabilities keep the visible product and the valid quote in the same state.
- VisualizationReal-time 3D configurationBuyer or sales user
Each selected option can update the browser-based product view.
documented - GuidanceStructured product selectionBuyer or sales user
A complex product can be presented through a more controlled choice sequence.
documented - CommercialPricing and quote generationSales team
The configured state can inform price and quote data.
documented - ValidationConfiguration rulesProduct owner
Invalid combinations can be restricted before the quote path continues.
documented - IntegrationCRM, ERP and e-commerce APIsSales operations
Configuration and quote data can connect to the surrounding commercial workflow.
documented
04 / How it connects
Every implementation needs an explicit source of truth for product, price and quote.
Inbound
- 3D product assets and configuration modelThe product structure and visualization assets must be prepared for each manufacturer.implementation-specific
- Pricing and compatibility rulesCommercial and product rules depend on the connected systems and markets.implementation-specific
Platform responsibility
- 3D rendering state
- Configuration dependencies
- Selection validation
- Price calculation
- Quote payload
Outbound
- CRM, ERP and e-commerceAPI connections to these system categories are part of the documented capability.confirmed
- Order and production handoffThe local source does not define order, manufacturing or fulfilment ownership.open
05 / How it enters use
Start with one product family and one authoritative quote path.
- 01Scope
Choose one product family, sales flow and accountable product and commercial owners.
- 02Configure
Prepare 3D assets, product options, dependencies, pricing and quote rules.
- 03Connect
Map CRM, ERP, commerce and any product-data source of truth.
- 04Validate
Test visual state, valid combinations, pricing and quote payload together.
- 05Operate
Assign model updates, rule changes, integration monitoring and support.
The implementation must also resolve performance budgets, browser coverage, accessibility, asset versioning, price authority, security and support. None of those terms should be inferred from the presence of a browser-based configurator.
06 / What is verified
The capability and partnership context are documented; outcomes require project evidence.
3D-to-quote capability model
The local source connects real-time 3D, guided selection, configuration rules, pricing and quoting.
- Source
- platforms-v2.md
- Limit
- No named implementation, working artifact or verified sales outcome is supplied in the local platform record.
Business-system integration direction
CRM, ERP and e-commerce API integration is included in the described capability set.
- Source
- platforms-v2.md
- Limit
- No connector, data contract or system-of-record boundary is specified.
Animech and SKWD relationship
The public SKWD detail presents the product as an Animech company product and SKWD as a project partner.
- Source
- Current public SKWD 3D and CPQ page
- Limit
- Ownership, implementation scope and permission to publish assets must be confirmed for each use.
Ownership and access
How the platform enters a real engagement
- OwnershipdefinedAnimech product context
SKWD is presented publicly as a project partner, not as the owner of the underlying product.
- First engagementdefinedImplementation discovery
Start with one product family, one quote path and clear responsibilities across the product owner, SKWD and client.
- Commercial and service modelimplementation-specificPartner-specific
Licensing, delivery scope, hosting, support, asset work and pricing require joint confirmation.
Next step
Bring one product family and its real commercial rules.
The first conversation should align product ownership, 3D assets, configuration logic, price authority and the systems that receive the quote.
Start a platform conversation3D and CPQ is presented as a documented capability and partner context. Animech ownership, SKWD delivery scope, implementation evidence, asset rights, integrations, hosting, support and commercial terms require confirmation.