E-commerce
Generate SKUs for every product variant combination
Upload your product options as CSV and get every size, colour or other combination as a row with its own SKU. The job stops if two SKUs would be identical.
or drop it here
- CSV
- Up to 100,000 generated variants
1 prepared source file · 77 bytes
- Products: 1
- Variants: 6
result.csv · findings.csv · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Building a SKU for every product variant
Your options go in
You upload your product options as a CSV file, such as sizes, colours or materials. The builder makes one row for every combination of the options you supply. A single run can produce up to 100,000 variants. Option lists multiply fast, so a run that would create a very large matrix shows a preview first and asks you to confirm. It is a standard tool, included in your 3 free jobs a day with a free account.
result.csv, findings.csv and manifest.json
result.csv is a plain table with your option columns and the generated SKU on each row. If two combinations would get the same SKU, the job stops instead of overwriting a row, and findings.csv names the combinations that clashed. manifest.json is a short summary of the run that records your source file, so you can check which upload the result came from. Your original file stays unchanged.
The SKU pattern and what you still do by hand
You write a SKU pattern with placeholders for your option names, and the builder fills it once per combination. Characters that would break a filename are normalised, so the same code also works as an image name. The builder does not guess which combinations you do not sell. Remove those rows from result.csv yourself. Marketplace column layouts are not applied either, so map the columns onto your platform template before you import.
Questions before you run it
How does the SKU pattern field build each code?
You supply a pattern with placeholders for your option names and the builder fills it once per combination. Characters that would break a filename are normalised, so the same code works as an image or asset name.
What happens when two option combinations produce the same SKU?
The job stops on the collision instead of quietly overwriting a row. findings.csv names the combinations that clashed so you can make the pattern more specific.
Can I exclude option combinations that I do not actually sell?
No. Exclusion rules are not inferred, so the matrix is the full Cartesian product of the options you supply. Remove the rows you do not stock from result.csv afterwards.
How many variants can a single run produce?
The ceiling is 100,000 generated variants. Option lists multiply fast, so a run that would produce an explosive product asks for a preview and an explicit confirmation first.
Will the output import straight into Shopify or another marketplace?
result.csv is a plain table of your option columns plus the generated SKU. Marketplace column profiles are not applied, so map the columns onto your platform template yourself.