Brand and presentation
Set branding, backgrounds and lighting around accurate product materials.
The 3rDoor platformCreate. Manage.
Create. Manage.
Deliver.
Create, manage and deliver interactive product experiences from one platform. Reuse product assets across 3D Product Viewer, Product Configurator and supported AR Product Viewer experiences.
One connected product journey
- Reusable assets01
- Central authoring02
- Preview and approval03
- Published experiences04
- Your audience05
Platform lifecycle
From the product assets to the customer.
Follow each stage to see how preparation, authoring and delivery stay connected.
Assets
Bring together accurate models, materials, dimensions and visual references.
Assets and product packages
Prepare the product once, with its real choices.
A Product Package brings the relevant models, materials, dimensions and supported options together. Accurate references give the authoring team a consistent starting point.
A clear production handover
Confirm product structure, finish names and valid combinations. Keep missing references visible during preparation rather than hiding them in the customer experience.
Reuse preserves product accuracy; each experience is still reviewed for its own purpose.
Asset reuse
One Product Package. Several useful experiences.
Begin with a shared product foundation instead of disconnected asset work for every presentation.
One Product Package
3D Product Viewer
Reuse the prepared geometry and materials for supported inspection and product detail.
Product and experience model
One product can have independent experiences.
A Refrigerator can have a Viewer for inspection, a Configurator for supported choices and an AR experience for placement. Each presentation has its own purpose, settings and review.
Product: Refrigerator
3D Viewer
Inspect form, controls and reviewed product detail.
Illustrative product model. These branches do not certify a live Refrigerator experience.
Preview, review and publish
Approve what the audience will actually see.
Author
Prepare presentation, choices and product explanations.
Experience delivery
Keep the preview useful and the launch deliberate.
A published experience is delivered through the existing 3rDoor delivery layer. The website provides the entry point and a clear route back to product information.
Load after intent where appropriate
Begin collections and campaigns with lightweight media. Let customers choose when to launch a reviewed experience, with an enquiry or product destination nearby.
Keep a preview when live delivery is unavailable; publication and device support are confirmed before offering the launch.
Integration
Bring the approved experience to the buying journey.
3rDoor Platform
Publish the reviewed product experience through the existing delivery platform.
Keep the product connected
The website maps the product to its approved experience. Product identity stays consistent across viewing, configuration and placement.
Fit the real page
Confirm responsive sizing, loading states, gestures, supported browsers and the return path with your website team.
Agree the handoff
Enquiry, saved selections, pricing or checkout depend on the agreed destination and existing business systems.
Analytics
Measure the questions that matter.
Define what you need to understand about experience use before agreeing the measurement.
Usage and engagement
Review available experience usage and engagement signals for the agreed implementation.
Product interaction
Confirm which viewing or configuration interactions are recorded before relying on reports.
Operational insight
Agree the visibility needed to understand delivery issues and the operation of the experience.
Reporting coverage, event definitions, consent and access are confirmed for the project. No conversion lift, ROI or attribution result is implied.
Clients, workspaces and governance
Keep each team’s work and publishing responsibilities clear.
Plan separate client or workspace handling, content ownership and the people responsible for reviewing and publishing changes. Apply the reusable platform to each agreed client context.
Controlled publication
Agree who authors, reviews and approves the experience. Confirm access, workspace separation and publishing controls against the actual project setup.
Enterprise requirements
Review security, procurement and operational responsibilities for the deployment. No particular certification or unverified control is implied.
Responsive web delivery
Useful on desktop, tablet and mobile.
Review controls, reading space, gestures and orientation on supported screens. Device support is confirmed for the actual experience.
Keep product images, dimensions and the next action available when an interactive feature cannot run. Test loading, permissions and the return to the website as part of the whole journey.
Your project journey
Keep the product and the customer in view.
Product→
Experience→
Publish→
Website
Product
Gather product references, materials and the choices customers need to understand.
Questions
Agree the scope before publication.
Does this website replace the authoring platform?
No. Product preparation, authoring, review and publishing remain with the existing 3rDoor platform. This website introduces and launches the resulting experiences.
Can a product be reused across experience types?
Where its assets and authored features support them. One Product Package can underpin multiple independently reviewed experiences.
Are all integrations and analytics included automatically?
No. Confirm supported methods, event coverage, responsibilities and commercial scope for the particular project.
Does a product diagram mean the runtime is available?
No. Diagrams explain the platform model. A public launch requires an approved experience and verified delivery configuration.
A new way to discover
Start with the product journey.
Bring your product, available assets, website and the next step you want customers to take.
Book a Demo