Locate which record is actually missing
This procedure assumes the Photoroom Space is already connected to the merchant’s Shopify store. In Photoroom Product Catalog, open the intended product; select Variants in the Shopify sidebar, opening the sidebar first if it is hidden. A missing variant row is not an image-generation problem. The underlying sellable option must exist in Shopify, because Photoroom’s documented workflow does not create variants.
Check the Shopify product record before touching imagery. If the intended variant is absent, select Create Variants in Shopify where offered, create the valid option in Shopify admin, and Save. If Shopify already lists and saves the option but Photoroom does not display it, refresh the Photoroom browser tab and open Variants again. Look for an image box per variant; do not infer any separate sync status.
If the row is visible but the image box is empty or wrong, the catalog prerequisite is complete. Stop refreshing and switch to the assignment decision. Never assign a missing color’s photo to the neighboring SKU just to fill the gallery.
Distinguish selection, attachment and publication
Beside the target variant, select its image icon and choose the image. The documented choices are a new upload into product Assets, an existing Asset, a Design in the Space, or an AI-generated variant candidate. None verifies that the depicted variant is sold.
There is a conditional confirmation that matters: when the seller chooses an existing image or Design, Photoroom says to select Add to listing. Do not treat highlighting that image in the picker as a completed attachment. Verify that it is associated with the intended variant row, then repeat the sequence for the other rows.
After all required assignments have been reviewed, use the back arrow beside Variants to return to Shopify settings and publish the changes to Shopify. This final action is separate from Add to listing. Photoroom also generates SEO filenames and alt text for variant images; inspect or edit them under SEO & metadata rather than assuming they describe the correct option.
Keep catalog readiness separate from visual approval
Use a small state ledger: Shopify variant saved, Photoroom row visible, chosen image attached, variant-to-image match approved, and publication authorized. If a row remains missing after source confirmation and refresh, preserve the source state and investigate the connection rather than generating more creative. If a row exists but the image is inaccurate, replace the asset, not the sellable option.
Inspect Shopify after publication; CartVisual neither synchronizes variants nor publishes this workflow.
Illustrative decision: the third mug color is absent
A mug seller intends three saved options: Terracotta, Slate, and Cream. Photoroom shows only the first two. The seller checks Shopify and discovers Cream exists in the plan but was never saved as a variant. The next action is to create and Save Cream in Shopify, then refresh Photoroom. When the Cream row appears, the diagnostic problem has changed from missing variant to empty image assignment.
Suppose a reviewed Cream photograph already exists as a Photoroom Design. The seller selects the Cream row’s image icon, chooses that Design, and selects Add to listing. They check the visible mapping before moving back to Shopify settings and publishing the authorized changes. If the cream photograph depicts the wrong glaze, they hold that row for a corrected authorized asset; another refresh cannot solve a visual mismatch.
Where CartVisual fits
Use it only to prepare a separate candidate variant image when needed; Shopify variant creation, matching and publishing remain in the external tools.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Photoroom: Apply an image to a Shopify Variant (Web App)
Official source snapshot checked .
The supplied Photoroom Web App help documents a previously connected Shopify catalog, Shopify-only variant creation, the refresh step, image source choices, conditional Add to listing, and final publication. It does not prove synchronization latency, storefront rendering, physical color validity, or CartVisual store integration.