Prepare the product data before adding the button
An AI Photo Try-On launch depends on a reliable connection between the product page, its image, and the experience the shopper opens. The button is the visible part. Behind it, your team needs an accurate product name, the right product image, and the correct destination page.
Vizbl's documented integration accepts a direct JPEG or PNG image URL. Review these inputs for the first launch group before extending the integration across a catalog. This gives merchandising and development the same reference for checking results.
Match the image to the selected product
Use an image that clearly represents the item being sold. Check that its color, finish, and design match the product option shown beside the button. If your page lets shoppers change variants, decide how that selection will be passed into the try-on experience and verify the behavior.
Create a simple product list with the item name, category, image address, page address, and variant information. Mark any uncertain asset for review. An accurate source image is more useful than a polished image of the wrong option.
Separate product preparation from website installation
Vizbl describes Photo Try-On as a workflow that can start from existing product photographs without first creating 3D models. It also describes preparing category-specific placement, scale, and variants. Treat that product preparation as a separate task from adding code to your storefront.
Assign an owner to each part. Your merchandising team should approve product identity and imagery. The person responsible for the website should confirm that the intended product data reaches the widget on every page included in the launch.
Register the domain and use your own widget configuration
The official setup guide requires a registered website domain, a shared script, and product-level element parameters. It identifies a public integration key and widget type as values supplied through the dashboard. Use the configuration issued for your own account and chosen experience.
Include the actual launch domain in the setup review. A temporary preview address deserves its own check; a working button on another domain does not establish that the preview or production site is configured correctly.
Let templates carry repeatable product data
If product pages share a template, the documented approach allows product name, image, and page URL to come from that template. This can reduce repeated manual entry, but the field mapping still needs review.
Test more than one product and more than one option. Check a normal product, an item with variants, and an item whose image changes after selection. Confirm that the widget receives the current item's data and that the page still works when the shopper closes it.
Approve the whole customer journey
Before launch, review the photo instructions, loading state, generated output, and return to shopping on mobile and desktop. Use photos your team is authorized to test with. Describe the upload process clearly without inventing assurances about retention or deletion.
Keep a short record of the products and devices reviewed, unresolved issues, and the person responsible for fixes. Once the launch group works consistently, use the same checks for the next group of products.