What steps should you follow to launch the project?
- Pick the starting products: Do not start with the whole range. Choose the 5–15 products with the highest traffic and return rates; that is where impact is measured fastest.
- Record baseline metrics: Note the current conversion rate, return rate and time on page for the selected products before the project starts. Without these numbers, impact cannot be measured afterwards.
- Take a file inventory: For each product: is there a CAD file, in which format, is it current? Without CAD you need a dimension table and multi-angle reference photography. This inventory directly determines quote scope.
- Define the variant structure: List colour, finish and part variants for each product. Where combinations are invalid, such as specific body-door pairings, write them down as rules; this layer is what sets the cost.
- Decide format and platform: glTF/GLB is needed for web and Android, USDZ for iOS AR. Establish whether your e-commerce platform has native 3D support; if not, integration is built at template level.
- Set a performance budget: Define a target file size and polygon budget for mobile. Without a budget set up front, the trade-off between model quality and page speed becomes an argument later.
- Instrument measurement events: Tag viewer interaction and AR launches as analytics events. Conversion comparison rests on comparing sessions that engaged with 3D against those that did not.
- Measure and expand: Measure the first group over at least one full sales cycle. Decide on the rest of the range from that data rather than assumption.
Which gap in preparation delays projects most?
| Gap | Delay it causes | Preventive step |
|---|---|---|
| CAD file cannot be found | Model is built from reference photography, taking longer | Request a file inventory from production and design |
| Variant rules are not written down | Configurator logic changes mid-project | List invalid combinations up front |
| No baseline metrics | Impact cannot be shown at the end | Record conversion and return rates before starting |
| No template editing rights | Integration step waits | Clear permissions with the platform vendor in advance |
| Performance budget undefined | Model quality is argued about late | Write the mobile file size target up front |