Plan the commercial surface
Define which pages, selling flows, and modules the branded site needs before implementation begins.
Website delivery add-on
Launch the branded website layer around the platform when the rollout needs more than a module alone.
This is not positioned as a separate product equal to the visualizer modules. It is the implementation layer for teams that need the branded site, Studio connection, and platform rollout handled together.
Commercial implementation view
Branded rollout surface
Implementation viewIllustrated view
Website delivery capture
Illustrated view of the branded website layer, Studio connection, and platform rollout scope.
What this add-on covers
Branded page delivery, platform integration, and the practical work required to connect the customer-facing website to Studio and the catalog.
Recommended use
Use this when your team wants the commercial surface and the visualization rollout planned together instead of stitching pieces together later.
Rolled out around the live catalog, not separate from it.
Implementation scope
Position the website as the rollout surface around the platform modules.
The value here is not generic agency work. It is a defined implementation scope for retail teams that need the commercial surface, the platform connection, and the rollout path aligned.
Connect Studio and platform modules
Wire the catalog and admin flow first, then place the visualizer where it improves the buyer journey.
Integrate and launch
Handle the critical API connections, merchandising hooks, and implementation details needed for a real rollout.
What you get
A practical implementation layer around the visualization platform.
- Branded marketing and commerce page implementation
- Studio connection and product data wiring
- Optional visualizer placement on selected pages
- API integration for the required customer-facing flows
- Launch checklist and rollout handoff
- Support for phased implementation around the live catalog
Book demo
Use the demo session to decide whether website delivery belongs in your rollout scope.
We will review whether you need the website add-on at all, which modules the site should support, the API and Studio work involved, and what the rollout should deliver first.