Review variant changes while retaining omitted rows
Compare current and proposed variant IDs, handles and options. Detect option combinations that collide with proposed or retained variants.
Can a partial variant update conflict with a row I did not include?
Yes. A changed option combination can match an existing variant that remains in the catalog. Variant Audit assumes a partial update: it overlays proposed rows onto current rows by variant ID and retains current variants omitted from the proposal.
Input requirements and report limits ↓Inputs
Copy a table from Excel or Google Sheets, including its header row, and paste it below. CSV/TSV files also work. Use “Map your columns” for different headers. IDs stay as text.
Free: UTF-8 CSV/TSV · 200 KB / 500 rows per input · 5 successful reviews per browser per day. CSV calculations run locally.
Need larger files or repeat batches? View editions →
Reuse a column profile
A profile stores column names only. It does not store your file contents.
Review report
Before you use this review
| Bring | Current and proposed handle, variant_id, option1, option2, option3 tables. |
|---|---|
| Match | Unique variant IDs. Overlay proposed rows on current rows and retain omitted current variants. |
| Read the result | Duplicate effective handle + option combinations, identity edits and new or omitted IDs. |
| Cannot establish | Explicit deletions or platform import behavior. An incomplete current file can hide conflicts. |
Required inputs
Both files need handle, variant_id, option1, option2, option3. Variant IDs must be unique within each file. A handle and first option value are required; unused later options may be blank.
Interpret the report
The effective result is checked for duplicate handle + option combinations. Changes to an existing variant's handle or options require identity review. New IDs and current IDs missing from the proposal are also identified. Missing does not mean deleted.
For example, changing variant 1 from Red to Blue conflicts if retained variant 2 already has Blue under the same handle and remaining options. This is a normalized review template, not a platform import. Explicit deletions and other Shopify dependencies are not modeled. Check SKU and barcode collisions separately.
Do I need the current variants if I am changing only one row?
Yes. Include the current variants that could share the affected product handle and options. An omitted row can only be retained and checked if it exists in your current input. An incomplete current file can hide a conflict.
Does leaving a variant out of the proposal delete it?
No. This review assumes a partial update and retains that current row. Use the report to check the combined result, then follow your platform’s own update procedure. Deletion instructions and platform-specific import behavior are outside this check.
Prepared by Supplier Desk Team · Updated . Examples are synthetic.
Who this is for
Small retail and wholesale operations teams reviewing supplier exports before changing catalog, stock or purchasing records. This is a focused review worksheet; it does not connect to your store or post transactions.
Related background
Read the source discussion or documentation. This describes the broader workflow. Use the input requirements and calculation rules above to decide whether this particular check fits your task.
Free tools with optional offline batch editions. Higher file limits, saved batch configurations and grouped report exports. No automatic store changes.