V E L L P I NCatalogCheck
Free pilot · v0.4

Check the shoot against
what the client asked for.

For product photographers and small studios delivering e-commerce images. Compare the client's SKUs and required views with your finished folder, and find missing views, conflicting filenames and images below the requested size before handoff.

Free, with no sign-up. Your images are read by this browser on your device; they are never uploaded or changed. The example uses made-up products and needs no files.

What you need

  • The client's SKUs and the views each product needs, such as front, back and side.
  • Your filename convention, such as {sku}_{view}.jpg for 00123_front.jpg, or a CSV that lists every expected filename.
  • The finished JPEG or PNG images in one folder; subfolders are fine.
  • A desktop browser, to choose the folder.

How to check your delivery

  1. Paste the SKUs, enter the views and check the filename pattern. The preview lists the names CatalogCheck will look for. Already have a CSV with filenames? Choose “Shot list with filenames” and import it.
  2. Choose your delivery folder.
  3. Select Check delivery and work through “Items to review”. Each finding says what to fix.
  4. Export the findings as a CSV if you want a record.

Good to know

  • It checks that every required view is there exactly once, that each image opens as a JPEG or PNG, and that it meets your minimum size as displayed.
  • It cannot tell whether the right product or angle is pictured, or judge colour, crop or retouching. Visual approval stays with you.
  • Limits: JPEG and PNG only; up to 5,000 required images and 5,000 files per check; 100 MB per image; shot-list files up to 2 MB in UTF-8 CSV. Tested so far only in Chromium (the open-source base of Chrome and Edge) on Linux; other browsers, Windows and macOS are not yet verified.

1 Your shot list

How to describe the shot list

Separate with commas. If filenames use codes, add them: front=01, back=02.

Use {sku}, {view} and {code}. They are replaced exactly, so leading zeros stay.

Products need different views? Use a sku,view list

Comma-separated, or paste two spreadsheet columns. When this list has rows it replaces the SKU list and shared views; view codes still come from the views field. Optional min_width,min_height columns override the shared minimums.

    File naming and supported inputs

    Build from SKUs: one SKU per line, kept exactly as typed, including leading zeros. Separate views with commas and add codes with front=01. Names a filename cannot hold, Windows reserved names and names that would collide (ignoring letter case) must be fixed before checking. Products with different views can use a sku,view list. Minimum sizes are whole pixels from 0 to 100,000. The generated list is not offered for download when a SKU, view or filename starts with a character spreadsheet apps can run as a formula (=, +, -, @); checking still works.

    Shot list with filenames: use comma-separated UTF-8 text; in Excel, save as “CSV UTF-8 (Comma delimited)”. Required columns: sku,view,filename. Optional columns: min_width,min_height, in pixels. The filename column must contain a basename such as 001_front.jpg, not a path. Matching ignores letter case and Unicode composition (NFC), but preserves spaces, punctuation and leading zeros. Multiple files with the same matching name are flagged, including files in different subfolders. Duplicate SKU/view rows and duplicate expected filenames must be corrected before scanning. Maximum 5,000 expected images and 5,000 selected files.

    Images: JPEG and PNG, up to 100 MB per file. Other formats, and files whose content does not match their .jpg or .png name, are explicitly marked unchecked. This version does not inspect image subject, crop, colour accuracy, retouching or near-duplicate content.

    2 Finished images

    Choose a delivery folder or select individual files.

    Keep your current folder structure.

    Subfolders are included. JPEG and PNG files are opened one at a time for a dimension check.

    No files selected.