Variation SKU audit checklist and change log
Last updated: 2026-07-31
Written and reviewed by Seller Profit Guard Editorial Team.
A variation SKU audit records parent-product scope, option names and order, value-code dictionary, expected and sellable combination counts, generated rows, duplicate and reserved checks, length limits, operational mappings, endpoint tests, exclusions, migration crosswalk, exceptions, approvals, release evidence, monitoring, and restoration without exposing private catalog records.
Audit parent identity
Record internal product reference, status, platform scope, owner, and evidence date. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Use redacted pointers. For checkpoint 1, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit option dictionaries
Record name, order, label, code, status, approver, effective date, and retirement. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Prevent ambiguous mappings. For checkpoint 2, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit matrix counts
Record expected, generated, sellable, excluded, active, and imported rows. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Explain every gap. For checkpoint 3, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit collision results
Record internal, cross-matrix, case, archived, pending, and reserved comparisons. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Retain the query version. For checkpoint 4, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit relationships
Check price, quantity, images, fulfillment, returns, labels, scanners, and reports by variation. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Sample evidence needs scope. For checkpoint 5, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit migration
Retain source export, transform, crosswalk, test batch, import summary, reconciliation, and restore packet. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Keep files private. For checkpoint 6, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Audit decisions
Record defects, corrections, reviewers, approvals, release, monitoring, stop rules, and restoration. The variation audit and change log must retain the parent grain, option position, human value, generated code, expected combination count, source version, tested endpoint, owner, reviewer, exception state, and effective date needed for a reproducible variation SKU audit.
Make changes reversible. For checkpoint 7, compare a valid matrix, a collision case, an excluded impossible pair, a corrected mapping, and the prior restorable set. Explain why the evidence supports only a reproducible variation SKU audit, not catalog truth, inventory accuracy, platform acceptance, or migration completion.
Variation SKU Audit and Change Log Template: matrix completeness control
Record option counts, expected multiplication, intentional exclusions, generated count, sellable count, and active count. Guardrail 1 declares its measurement, source, uniqueness scope, row limit, pass condition, failure owner, correction deadline, and rollback trigger before a generated set can move forward.
Unexplained gaps block bulk action. Apply the guardrail to the concrete variation audit and change log; keep fixed variants separate from modifiers, canonical identifiers separate from barcodes, and public aggregate evidence separate from private catalog rows.
Variation SKU Audit and Change Log Template: collision and reservation control
Compare normalized rows within and across matrices plus active, archived, pending, reserved, and alias registries. Guardrail 2 declares its measurement, source, uniqueness scope, row limit, pass condition, failure owner, correction deadline, and rollback trigger before a generated set can move forward.
One collision is material. Apply the guardrail to the concrete variation audit and change log; keep fixed variants separate from modifiers, canonical identifiers separate from barcodes, and public aggregate evidence separate from private catalog rows.
Variation SKU Audit and Change Log Template: variant relationship control
Map each generated row to parent, option labels, price, quantity, image, fulfillment, return, label, and report records. Guardrail 3 declares its measurement, source, uniqueness scope, row limit, pass condition, failure owner, correction deadline, and rollback trigger before a generated set can move forward.
A code is not the relationship. Apply the guardrail to the concrete variation audit and change log; keep fixed variants separate from modifiers, canonical identifiers separate from barcodes, and public aggregate evidence separate from private catalog rows.
Variation SKU Audit and Change Log Template: endpoint compatibility control
Test delimiters, lengths, case, imports, errors, POS, ERP, 3PL, labels, scanners, and downstream exports. Guardrail 4 declares its measurement, source, uniqueness scope, row limit, pass condition, failure owner, correction deadline, and rollback trigger before a generated set can move forward.
Use exact system versions. Apply the guardrail to the concrete variation audit and change log; keep fixed variants separate from modifiers, canonical identifiers separate from barcodes, and public aggregate evidence separate from private catalog rows.
Variation SKU Audit and Change Log Template: privacy and recovery control
Keep raw catalogs private, publish aggregates, retain the original export, crosswalk, approval, stop rule, and restore packet. Guardrail 5 declares its measurement, source, uniqueness scope, row limit, pass condition, failure owner, correction deadline, and rollback trigger before a generated set can move forward.
Never expose buyer or credential data. Apply the guardrail to the concrete variation audit and change log; keep fixed variants separate from modifiers, canonical identifiers separate from barcodes, and public aggregate evidence separate from private catalog rows.
Audit parent identity: combination exercise 1
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Record internal product reference, status, platform scope, owner, and evidence date. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Use redacted pointers. Exercise 1 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit parent identity” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit option dictionaries: combination exercise 2
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Record name, order, label, code, status, approver, effective date, and retirement. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Prevent ambiguous mappings. Exercise 2 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit option dictionaries” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit matrix counts: combination exercise 3
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Record expected, generated, sellable, excluded, active, and imported rows. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Explain every gap. Exercise 3 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit matrix counts” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit collision results: combination exercise 4
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Record internal, cross-matrix, case, archived, pending, and reserved comparisons. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Retain the query version. Exercise 4 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit collision results” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit relationships: combination exercise 5
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Check price, quantity, images, fulfillment, returns, labels, scanners, and reports by variation. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Sample evidence needs scope. Exercise 5 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit relationships” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit migration: combination exercise 6
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Retain source export, transform, crosswalk, test batch, import summary, reconciliation, and restore packet. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Keep files private. Exercise 6 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit migration” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Audit decisions: combination exercise 7
Regenerate the relevant rows using the six-row TEE size-color matrix and four-row PEN material-finish matrix. Record defects, corrections, reviewers, approvals, release, monitoring, stop rules, and restoration. Change exactly one input, recalculate the Cartesian product, list every affected identifier, and record the expected Block, Review, or Ready result.
Make changes reversible. Exercise 7 records the source-review date, dictionary-effective date, expected sellable-row count, one of the nine confirmations, and both length and matrix utilization for this exact “Audit decisions” decision. Include a hard failure whose generated rows are masked, a corrected dictionary, and the external platform, inventory, image, fulfillment, return, reporting, and restore evidence still required.
Evidence boundary for a reproducible variation SKU audit
The generated packet can demonstrate option-value multiplication, deterministic row construction, local duplicate detection, entered reserved-value comparison, declared length checks, and a reproducible status under synthetic inputs.
It cannot demonstrate that every variation exists or is sellable, that option claims and images are accurate, that price and stock are reconciled, that a platform or integration accepts the values, that a barcode is valid, or that historical orders survive migration.
Release, monitor, and restore the variation audit and change log
Block malformed or duplicate option mappings, generated collisions, reserved matches, fake dates, sellable-row mismatches, incomplete nine-control evidence, private exposure, and open conflicts, then mask derived rows. Review readability ambiguity or seller-set capacity thresholds. Ready clears only the two distinct local matrices.
Before public indexing or private import, retain source and rollback artifacts, run typecheck, tests, build, content, similarity, SEO, image, link, mobile, strict-404, deployment, and live checks, then measure delayed discovery and tool use without claiming same-period causality.
Variation SKU Audit and Change Log Template: field-level working record
Start the audit log with a change ticket, declared parent scope, catalog snapshot identifier, option-dictionary version, operator, reviewer, proposed effective time, and restoration owner. Separate the proposal from the approved result so a later reviewer can reconstruct what changed and who accepted each exception.
Create a matrix-count table with first-option count, second-option count, mathematical product, intentionally excluded pairs, expected sellable rows, generated rows, active rows, imported rows, and reconciled rows. Every difference needs a named reason, evidence pointer, owner, and disposition rather than a silent adjustment.
Create a collision worksheet that records normalization, checked registries, exact duplicate, case-only duplicate, separator-only duplicate, archived match, pending-import match, alias match, and reserved match. Store identifiers privately; publish only synthetic examples and aggregate defect counts.
Create a relationship checklist for each sampled variation: parent, both option labels, price, quantity, location, image, weight, fulfillment instruction, return lookup, label output, scanner lookup, POS lookup, ERP reference, 3PL reference, and reporting export. Mark not tested explicitly instead of treating a blank as passed.
Create a release ledger with test cohort, before-and-after counts, rejected rows, warnings, approver, release timestamp, monitoring checks, stop threshold, rollback decision, restored version, and final reconciliation. A Ready generator result is merely one attachment to this release ledger.
Close the audit only when defects have dispositions, exceptions have expiry dates, affected systems have owners, the crosswalk is retained, monitoring has a dated outcome, and restoration has been tested or documented. Keep the log append-only so renames and retired codes remain traceable.
Sources and further reading
- Seller Profit Guard methodology: Evidence versions, formulas, privacy, correction, release, and rollback.
- Seller Profit Guard data privacy: Local-first boundaries for catalog, buyer, order, supplier, credential, and raw-record data.
- Shopify Help: Variants: Official definition of variants as combinations of option values with variant-level inventory context.
- Shopify Help: Using SKUs to manage your inventory: Official SKU uniqueness, character, length, consistency, growth, fulfillment, and barcode boundaries.
- Shopify Help: Adding variants: Reviewed July 31, 2026: up to three options and 2,048 variants per product, with theme, app, channel, media, and legacy-tool caveats above 100 variants.
- Etsy Help: How to Add Variations for Your Listings: Reviewed July 31, 2026: up to two variation attributes, with price, quantity, processing profile, photo, and SKU controls.
- Etsy Help: How to Use SKU for Your Inventory: Official SKU purpose, shop search, multi-channel, short-code, ambiguous-character, and symbol guidance.
- Square Support: Create and edit item options and variations: Reviewed July 31, 2026: reusable option sets can generate all combinations and each variation can carry cost, price, and SKU.
- Square Support: Bulk import items: Official variation-level SKU uniqueness and pre-import export guidance.
- Shopify Help: Exporting products: Official product-export workflow for a private pre-change catalog snapshot.
Related Seller Profit Guard tools
- Variation SKU Generator: Expand two option sets and collision-check every generated row.
- SKU Naming Generator: Design the canonical naming architecture used by each matrix.
- Etsy Variation Naming Checker: Review buyer-facing option labels separately.
- Etsy Photo Coverage Checklist: Review visible option-image relationships.
- CSV Import Validator: Review a redacted structure before private import.
- Methodology: Review evidence, formulas, privacy, correction, release, and rollback.
- Data Privacy: Protect catalog, supplier, buyer, order, credential, and raw-record data.
- Variation SKU Formula and Input Rules: Expand parent and option codes into unique variation SKUs with explicit row limits, length rules, reserved values, evidence, and rollback.
- Variation SKU Worked Example: Size and Color: Expand three sizes and two colors into six traceable T-shirt SKUs, then verify counts, decoding, length, uniqueness, and reserved values.
- Variation SKU Sets for Material and Finish: Generate and review four pen variants from walnut or maple materials crossed with matte or gloss finishes and one parent code.
- Variation SKU Collision Mistakes and Fixes: Correct duplicate option codes, incomplete matrices, impossible pairs, overlong rows, retired collisions, segment drift, and unsafe imports.
- Variation SKU Evidence and Data Sources: Source parent products, options, value dictionaries, existing identifiers, platform constraints, operational mappings, and migration evidence.
- Variation SKU Acceptance and Import Gates: Separate option completeness, row-count, uniqueness, reserved, length, readability, sellability, integration, and rollback thresholds.
- Variation SKU Matrices: Options Compared: Compare a six-row size-color matrix with a four-row material-finish matrix at the same parent, mapping, length, and evidence grain.
- Weekly Variation SKU Control Routine: Operate a repeatable review for parent changes, option dictionaries, matrix counts, collisions, mappings, imports, exceptions, and restoration.
- How to Interpret Variation SKU Sets: Read combination counts, generated identifiers, collisions, length, reserved checks, and status without claiming catalog or import proof.
Next step: Open Seller Profit Guard.
This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.