How does the order of image URLs in a WooCommerce CSV decide the featured photo?

What the URL order controls

For one product row, place the image intended for the main product display first in the image URL field. Put the remaining gallery entries after the featured image, then inspect their actual displayed order after the test import. The first image and the remaining entries have different jobs: position one determines the featured image; later positions provide additional gallery images.

Use the built-in WooCommerce Product CSV Importer and Exporter schema and its own mapping. Do not infer the correct column name from an extension or a different import tool. An exported WooCommerce sample row is useful for confirming the expected image field and delimiter before editing your file.

When an Images cell contains multiple image references, the native schema uses a comma-separated list: enclose the complete CSV cell in double quotes so those commas stay inside one field. The first reference is the featured image. For an update to existing products, select Update existing products and confirm the ID or SKU mapping. Leave unchanged media out of copy-only updates.

Prepare evidence before importing

Make a small test copy of the CSV and preserve the original file. Use a test product identity or a new non-production product so the result can be inspected without changing an established listing. Confirm that each image URL is reachable by the importer and that the URLs point to the intended files, rather than relying only on filenames.

Before a large import, inspect an exported sample row and compare its product identity, image field, and mapping with your test CSV. If the importer offers an update or matching choice, use the identity that corresponds to the existing product only when updating is intentional. This preserves product identity and avoids accidentally treating a row as a new product.

Illustrative exercise

Illustrative exercise: define two distinguishable assets before comparing results. Asset A is a visibly labeled front-side-back fixture: front-red.png shows the words FRONT and a red package face. Asset B is gallery-only: back-blue.png shows the words BACK and a blue package rear. These filenames and labels are illustrative; your own files may differ.

In this illustrative CSV, set the Images cell to "front-red.png,back-blue.png", keeping both names inside the quoted cell. Expected pass: the product’s featured image visibly says FRONT, and BACK appears as an additional gallery image. For the A/B comparison, reverse only the two URLs in a second test row: "back-blue.png,front-red.png". Expected pass for that row: BACK becomes featured and FRONT becomes a gallery image. A failure is any result where the first URL does not become featured, or where the second image is missing despite being reachable and correctly mapped.

Short action sequence

1. 1. Export or open a WooCommerce sample product row and identify the built-in importer’s image field and product identity fields.
2. 2. Create a test copy containing one deliberately labeled front image followed by one deliberately labeled gallery image.
3. 3. Check that both URLs are reachable, preserve the original CSV, and import only the test row with the intended mapping.
4. 4. Open the resulting product and inspect the featured image and gallery thumbnails, recording which label appears in each position.
5. 5. Repeat with the two URLs reversed only if the first test is ambiguous; compare the observed positions.

Choose the next action

If the first URL is featured and later URLs appear in the gallery, keep the ordering rule and apply it to the larger import after reviewing identity matching. If the wrong image is featured, inspect the actual parsed field value, separators, whitespace, and URL order in the importer preview or mapped row; then correct the CSV and rerun the test.

If an image is absent, stop changing the order and verify reachability, the built-in schema mapping, and the exact URL value. If a reachable image still fails, compare the test row with an exported sample and retain the importer’s expected field structure before investigating anything broader.

Scope of the documentation

The official references below support tool behavior and feature boundaries. The test fixture, branching decisions and acceptance criteria are Itemlume editorial recommendations; citation does not imply endorsement. Illustrative sizes, names and timings are not your production specifications.