Records + assets + explicit rules

Listing Pack Check

Check whether each product record has enough reliable file matches, then review explicit image requirements and set-level differences before import, migration or handoff.

Local processingSources unchangedGuided result
1 · Product records

Add data

Open CSV, TSV, Excel or compatible JSON. A current or recent TaskThimble table can also be reused.

No product data loaded.

2 · Asset files

Add product files

Choose files now, or reuse a current or recent compatible file set from the local TaskThimble workbench.

No files selected.

3 · Requirements

The file-count and pixel rules are your requirements. Shape and brightness differences are set-relative review signals, not automatic defects.

Completeness and readiness are different questions

This check asks whether product records have enough reliable filename matches and whether image files cross the explicit minimums you entered. It does not establish that the product listing itself is factually correct or approved for a marketplace.

Use it before the store or PIM

This is a platform-neutral preflight. It does not need store credentials and does not write to Shopify, WooCommerce, a PIM or a marketplace. Use it to make the package understandable before import, migration or handoff.

Unclear matches stay unclear

Near or competing filename relationships are shown for review instead of being promoted to confirmed coverage. Resolve naming or record ambiguity before treating the pack as complete.

Re-check the final pack

After obtaining missing files or correcting output copies, run the same pack check again. If a marketplace or client has additional explicit rules, continue with a more specific readiness check.