LC ListCombinator

Catalog operations

Plan product variants with constraints before catalog import

Combine colors, sizes, materials, regions, and packaging options while keeping invalid combinations visible as a rules problem—not an after-the-fact cleanup surprise.

Ecommerce operationsCatalog managersMarketplace sellersProduct data teams

The recurring problem

Why make this a workflow?

A blind Cartesian product creates impossible variants, platform-limit surprises, and manual SKU cleanup. The useful workflow estimates scale and documents exclusions before export.

Inspectable pipeline

Recommended steps

  1. 1

    Import attributes

    Paste or import option lists such as color, size, material, region, and pack size.

  2. 2

    Estimate combinations

    Review the theoretical count and likely output size before generating.

  3. 3

    Apply constraints

    Document forbidden pairs, dependencies, required options, and mutually exclusive values.

  4. 4

    Build identifiers

    Add a stable prefix, normalized tokens, and a separator for SKU candidates.

  5. 5

    Validate and export

    Review duplicates and platform limits, then export a catalog-ready working file.

Concrete example

Input sketch

Color: red, blue
Size: S, M, XL
Material: cotton, wool
Rule: wool cannot use XL

Reviewed output

TEE-RED-S-COTTON
TEE-BLUE-M-WOOL
TEE-RED-XL-COTTON
Excluded: *-XL-WOOL

Count before generation

Avoid freezing a browser or exceeding a commerce platform's variant limits.

Rules stay explicit

Dependencies and exclusions can be reviewed with product owners.

Safer identifiers

Normalize option tokens and inspect duplicate SKU candidates before import.

Limits to review before production

  • Every commerce platform has its own column names and variant limits.
  • Generated SKU candidates must be checked against existing inventory identifiers.
  • Constraint rules require domain knowledge and should be approved before production import.

Questions about this workflow

Can it prevent invalid combinations?

The workflow supports explicit filtering and is designed to expand into dependency and exclusion rules; always review the resulting rule set.

Does it connect directly to Shopify or WooCommerce?

Not currently. Export a reviewed file and map it to the current platform schema.

Is catalog data uploaded?

No. Normal inputs and outputs remain in your browser.

Build the Recipe locally

Load the recommended deterministic steps, inspect every option, and run them against your own browser-local data.

Load this Recipe

Privacy settings

Control optional providers

Necessary local storage keeps your consent choice and, when you ask, recipes or favorites on this device.