Variant Matrix Completeness Worksheet

01 · Declare

You define what “complete” means

The worksheet builds a Cartesian product from your option values, then subtracts only the exclusion rules you wrote with reasons. It never infers that an absent combination should exist.

A · Options

Declared option space

Required

One option per line: Option: value | value

Names and values are exact, trimmed, and case-sensitive. ; and = are reserved.

B · Existing

Existing variant rows

Required for comparison

One full variant per line: Option=value; Option=value

Every valid row must name every declared option. Unknown or incomplete rows stay explicitly unknown.

C · Exclusions

Intentional exclusion rules

Optional, but explicit

Partial or full rule plus reason: Option=value; Option=value => reason

A partial rule excludes every matching combination. Overlapping rules are retained, with all reasons shown.

Review

Missing expected

Classify these; do not assume they are errors.

Combination	Why listed

Accepted

Intentional exclusions

Absent and covered by an operator rule.

Combination	Operator reason

Conflict

Excluded but present

Check the rule or the catalog row.

Combination	Reason	Existing lines

Duplicate

Repeated combinations

Same exact option values on multiple rows.

Combination	Rows	Line numbers

Method & limits

What this result can and cannot say

Observed: exact text you entered, deterministic Cartesian combinations, duplicate rows, and rules you explicitly supplied.
Not observed: storefront behavior, inventory, prices, SKU validity, publishing state, feeds, themes, or platform settings.
Unknown stays unknown: malformed, incomplete, or undeclared rows are not silently repaired.
Local guard: this prototype stops above 20,000 potential combinations. That is a worksheet performance guard, not a platform limit.

Source boundary · checked 2026-09-27

Terminology and problem evidence

Official documentation confirms that product variants are combinations of option values and may be generated or added selectively. The worksheet deliberately does not encode any vendor limit.

These links support terminology and the existence of the operator problem. They do not validate this worksheet against a live store or prove search volume.