Audit the assets you already own
Lighting teams may have engineering files, visualization models, supplier assets and photographs of the same fixture. Inventory them before commissioning new work. Record which file represents the current sellable product, what dimensions it uses and whether the finish information is complete.
Do not assume a detailed engineering file is ready for a shopper's phone. It may include internal parts or geometry that contributes nothing to the customer view. The goal of the catalog model is to explain the product accurately while remaining practical to load and manipulate on the viewing device.
Approve scale before visual polish
Check the model against the manufacturer's approved dimensions. A beautiful model with the wrong height or diameter undermines the purpose of an in-room preview. Keep dimensions linked to the exact size variant rather than treating them as a generic property of a product family.
Vizbl's published model requirements use real-world dimensions and meters as the modeling units. They also describe placement configuration for floor, wall and ceiling objects. Have the model team verify the origin and orientation appropriate to the intended mounting surface before the asset reaches the website team.
Prepare materials for inspection
Shoppers may rotate and zoom closer than they could in a lifestyle photograph. Review visible joins, edges and surfaces from several angles. Make sure the finish is associated with the correct product option and that transparent or reflective parts are prepared deliberately.
The documented input formats include FBX, OBJ, GLB and USDZ, with different packaging requirements. Provide complete materials and textures in the required form. A supported extension alone does not establish that every dependent file, material or dimension is correct.
Build only the variants you can support
Agree on the first release's configurations: finish choices, sizes or other options that customers actually order. A configurator is more useful when its choices match the catalog clearly than when it offers a long list of approximate color substitutions.
For each variant, confirm the product identifier, displayed name and destination page. Check how the chosen variant passes from the 3D experience to AR. Multi-fixture scenes, where required, should have their own review rather than being assumed to work because one fixture renders correctly.
Plan the catalog and integration as separate stages
The website script is only one part of the project. Model preparation, merchant approval and product mapping can determine the launch timeline. Avoid promising that a whole catalog will be live in the time it takes to paste a snippet.
Review a small group on the devices and connections your customers use, then document the accepted assets. Keep a process for updating models when dimensions, finishes or product URLs change. The same discipline that produces a good first launch also prevents a growing catalog from drifting away from the products customers can buy.