My Shopify CSV import succeeded. Why are some product images still missing?

Build an expected-media ledger

List each product handle, SKU, source image address and intended role. A product with three source rows does not necessarily require three different images: repeated addresses can represent an association rather than a new asset. Count unique expected pictures separately from variant links.

Inspect the actual product in the admin and the public storefront. Record a missing asset, an existing asset with a wrong association, and an existing but undisplayed asset as different outcomes. A theme presentation problem needs a different repair from a failed download.

Verify the file address before repairing

Open a missing image address in a fresh signed-out session. It should reach the intended image file without an account, expired sharing permission or a page that merely contains a preview. This checks one access path only; it does not prove Shopify’s own request succeeded. Verify the imported media separately. Check that the address still returns the correct SKU picture rather than an error or replacement.

Do not put confidential photos on a public host just to satisfy this test. Use approved public product assets, keep restricted material out of the import, and ask the host owner to resolve an access failure. CartVisual creation and Shopify import are separate manual activities.

1. Export the original CSV and retain the import report.
2. Mark the exact missing product and SKU before changing any row.
3. Test one approved image address outside the signed-in session.
4. Repair one affected record using the current Shopify workflow.
5. Recheck media, variant selection and the public product page.

Fictional exercise: separate two failures

In this fictional exercise, a mug import finishes successfully. The blue image uses an expired share address; the green image is already in the product library but the green variant points to blue. These observations are deliberately invented to demonstrate diagnosis, not an CartVisual test.

Replace only the blue address with an approved accessible file and verify its arrival. Then correct the green association without uploading another green picture. If the asset remains absent after that isolated repair, stop repeating the batch and preserve the report for store support.

Choose association repair or a limited reimport deliberately

When the image already exists, use the intended association control instead of assuming a CSV retry will reuse it. Shopify’s CSV guidance notes that a Files image URL can be downloaded again and duplicated during import.

Keep row counts, distinct expected pictures and media records separate. This is a manual recovery plan, not an CartVisual connector.

Close against the buyer’s selected variant

Approval requires the expected image in product media and the intended result when the buyer selects the variant. Compare color, package count and model name, not only file existence. Record the final file and association alongside the repaired row so another operator can reproduce the check.

A green checkmark on the import screen is not the stopping rule. Stop when each affected ledger entry has a verified outcome, or explicitly hold the unresolved entry. Do not describe the rest of a catalog as approved after checking one product.

Missing-image decision ledger

Use this matrix as a manual review record and add your own real evidence. Its conditions are not completed test results.

Download this question’s review worksheet (CSV)