VTEX Product SKU Image Spreadsheet Preflight: Download and Check Import URLs Before Upload

Why VTEX image imports need preflight

VTEX documents image import as a spreadsheet workflow for product SKU images. That is convenient for catalog teams because the file can be reviewed in Excel before upload, but it also means small spreadsheet mistakes can become catalog mistakes. A URL can be reachable in a browser but fail the exact VTEX field rule. A helper column can accidentally change the official template. A row intended to update an existing image can be turned into a new-image row and create a duplicate.

The practical solution is a preflight step before anyone uploads the workbook. Treat the VTEX spreadsheet as both an import file and a manifest of remote image binaries. VTEX needs the official columns and row behavior. Your team needs proof that the URLs resolve, that the files have been backed up locally, and that failures are visible before the import job starts. Sheet Image Downloader supports that second job: it reads an Image URL column from a separate download workbook, optionally uses File Name and Folder Path columns, saves files locally, and records failed rows in its run results.

This boundary is important because the official VTEX rules are specific. The image import accepts .xls and .xlsx files. For a new image, only SKU ID and Image import URL are required. The import URL must start exactly with http:// and end with one of the documented image extensions: jpg, png, gif, ico, svg, or webp. For an existing image update, VTEX says to keep the Image ID and leave Image import URL blank to avoid creating a duplicate. A successful import queues products for indexing, so upload success is not the same as immediate storefront confirmation.

VTEX spreadsheet rules that matter

Start with the official VTEX template and do not modify it. Use a working copy for notes, formulas, filters, or QA helper columns, but paste only approved values back into a clean workbook for upload. This prevents a local operations habit from changing the structure VTEX expects. It also gives reviewers a clear difference between the audit file and the import file.

Also include the known export issue in your review. VTEX documents that account names beginning with p may export incomplete URLs missing the leading p. The official workaround is to insert the missing p with an Excel formula or another method. If your account name starts with p, check this before local download, because the same incomplete URL will fail your backup run.

Eight-step SKU image workflow

This workflow keeps platform actions and local backup actions separate. VTEX remains the place where the spreadsheet is uploaded and indexed. Sheet Image Downloader is used before that upload with a separate download workbook to test whether the image URL list is reachable and recoverable.

Checklist before uploading XLS/XLSX

1. File type is correct. The upload file is .xls or .xlsx.
2. Template is unchanged. No renamed headers, deleted columns, moved sections, or helper columns remain in the import area.
3. New image rows have the required pair. Every new image row has SKU ID and Image import URL.
4. Existing image updates are not new imports. Rows for existing images keep Image ID and leave Image import URL blank.
5. URL format matches VTEX. Populated URLs start exactly http:// and end with jpg, png, gif, ico, svg, or webp.
6. The leading-p export issue is checked. Account names beginning with p get a specific exported-URL review.
7. Local backup is complete. Every populated URL has been downloaded or appears in reviewed failed-row results.
8. Indexing expectations are clear. The team knows a successful import queues products for indexing and still requires VTEX follow-up.

Common issues and fixes

Related spreadsheet workflows

VTEX is one version of a larger spreadsheet image operations problem. These related guides cover adjacent workflows and are useful when a team handles multiple platforms:

• Akeneo product image asset URL preflight
• Prepare product image spreadsheets for marketplace upload
• Bulk download product images from a spreadsheet
• Retry failed image downloads from Excel
• How to name and organize downloaded images by SKU
• Product image URL spreadsheet template

How to hand off the preflight package

A useful VTEX preflight does not end with a clean spreadsheet. It should leave behind a package that another teammate can audit without reopening every source system. Store the final VTEX workbook, the untouched original template or export, the separate download workbook, the dated local image folder, and the Sheet Image Downloader run results in the same project folder. If the import later needs to be explained, rolled back manually, or repeated for another workspace, the team can see which URLs were used and which files were actually reachable on the day of the run.

Use a simple naming convention for that package. A folder such as VTEX-images-2026-07-14 can contain source-export.xlsx, upload-approved.xlsx, downloaded-images/, and download-results.json. Inside the downloaded image folder, names based on SKU ID are easier to reconcile than generic image names from a supplier CDN. This follows the same principle as a broader SKU-based image organization workflow: every local file should answer which catalog row created it.

For review, ask one person to check VTEX-specific compliance and another to check image reachability. The VTEX reviewer confirms workbook format, template integrity, new-image required fields, existing-image duplicate protection, and the leading-p export issue when applicable. The image reviewer confirms that every populated URL was attempted locally using the separate download workbook, failed rows were resolved or deliberately excluded, and the final upload workbook contains only approved values. Splitting the review prevents a clean download log from being mistaken for a complete VTEX import validation.

After upload, keep the same evidence package until indexing and storefront checks are complete. VTEX's documented behavior is that successful imports queue products for indexing. If a product is not visible immediately, the local backup cannot prove an indexing outcome, but it can prove that the spreadsheet referenced reachable files before upload. That distinction helps support teams troubleshoot calmly: URL reachability, spreadsheet acceptance, indexing, and storefront rendering are separate stages.

Frequently asked questions