All assembly runs in your browser—product data is not sent to SynthQuery servers.
Live preview
ELC-TSH-M-BLK-0001
Turn off to force lowercase SKUs.
Generation mode
Output
0 SKUs
Validate uniqueness in your OMS or storefront before going live. Free tools · All tools
About this tool
A stock keeping unit (SKU) is the internal identifier your team uses to tell one sellable item apart from every other variant on the shelf, in the warehouse, or in your ecommerce catalog. Unlike marketing names that change with seasons, SKUs stay stable enough for purchase orders, pick lists, barcode labels, and ERP sync—yet flexible enough to encode category, product family, size, color, season, or channel when you design the pattern deliberately. Retailers and direct-to-consumer brands that wing it with duplicate codes, vague spreadsheets, or copy-pasted supplier strings eventually pay for it in mispicks, accounting tie-out pain, and marketplace listing errors.
SynthQuery’s SKU Generator is a privacy-first, browser-based utility that helps you prototype and export consistent SKU schemes before you commit them to Shopify, WooCommerce, NetSuite, or a custom stack. You choose which segments appear (category prefix, product type, size or variant, color, sequential counter, optional random alphanumeric tail), pick separators—dash, underscore, or none—and preview the composite string instantly. Generate ten, fifty, one hundred, or five hundred rows in one click for staging imports, or paste a CSV of draft products so each line inherits the right variant fields while the sequential slice still increments predictably. Copy to the clipboard or download CSV and plain text; everything runs client-side so confidential assortment plans never leave your device unless you choose to save them. The tool lives in our Free tools series next to other Code & ID utilities, while the full product index at https://synthquery.com/tools (also linked from the site footer) connects you to AI detection, readability scoring, plagiarism checks, grammar assistance, and the rest of the SynthQuery platform when your workflow moves from inventory scaffolding to publish-ready copy.
What this tool does
Most spreadsheet templates force you to concatenate cells by hand, hunt for the right formula when someone adds a new color, or worse, let every merchant invent their own mnemonic until the database looks like a ransom note. This generator keeps the mental model visible: each enabled segment becomes an ordered token, joined with the separator you select, so teammates can read a SKU aloud in the warehouse and still understand which slice means “apparel tops” versus “footwear.” Category prefixes can be typed manually when you already reserved two- to four-letter families, or generated automatically as random uppercase letters when you want a quick sandbox dataset before leadership approves the taxonomy.
Product type, size, and color fields accept whatever short codes your style guide allows; non-alphanumeric characters are stripped automatically so you do not accidentally ship spaces or slashes that break importer validation. Sequential numbering supports a starting value and minimum width for zero-padding, which keeps lexical sorts aligned with numeric intent in CSV viewers. The optional random segment uses cryptographically suitable randomness from your browser to append a high-entropy tail—ideal when you want uniqueness guarantees without maintaining a central counter yet, or when parallel teams mint SKUs offline and you need collision resistance inside a batch.
Batch mode repeats your template across N rows, incrementing the sequence each time and drawing a fresh random tail whenever that segment is enabled. CSV mode maps flexible column headers (prefix, product_type, size, color, plus common aliases) so you can import a merchant’s rough export, generate one SKU per populated row, and still respect the same global format rules. Preview updates as you toggle segments, so merchandisers can sanity-check readability before they hit Generate. Downloads emit newline-delimited text or a single-column CSV compatible with most ecommerce bulk editors.
Customizable format and separators
Dash-separated SKUs mirror how English-speaking teams read codes over the radio; underscores suit filenames and some ERP imports; omitting separators yields compact tokens when your channel caps field length. Combine only the segments you need so seasonal capsules can drop color while basics keep it.
Batch generation at commerce scale
Choose 10, 50, 100, or 500 SKUs per run to match typical staging batches. The tool caps each generation at five hundred rows to protect browser performance; run again with the next sequential start if you need more.
CSV import and export
Paste comma-separated text or upload a UTF-8 .csv file. Headers are detected case-insensitively, BOM characters are tolerated, and each data row produces one SKU. Finished lists download as CSV or TXT for spreadsheets, PIM tools, or platform importers.
Preview, validation, and case control
Live preview shows a representative string, manual prefixes validate for two- to four-letter categories, and an uppercase toggle enforces consistent casing for channels that treat SKUs as case-insensitive.
Technical details
Strong SKU systems balance human scanability with machine uniqueness. Keep segments short but meaningful, avoid visually confusable pairs if operators dictate codes verbally, and document the meaning of each slice in a living style guide. Uniqueness is enforced within a generated batch when possible—duplicate outputs surface as errors, especially in CSV mode where two identical rows would collide. Character sets are intentionally limited to letters and digits after sanitization, which aligns with most ecommerce importers and reduces URL-encoding surprises.
Sequential widths should reflect realistic catalog growth: a four-digit pad handles nearly ten thousand variants inside a family before you roll the prefix. Random segments draw from an uppercase-safe alphanumeric alphabet to limit ambiguous glyphs; length scales entropy roughly linearly, so six characters from a 32-symbol set is dramatically harder to guess than three. Case sensitivity is a platform decision—Shopify treats SKUs as case-insensitive in many flows, while databases may be case-sensitive—so the uppercase toggle helps you mirror production rules during prototyping. Always re-validate inside your system of record; this generator does not know about legacy codes already stored in PostgreSQL or your PIM.
Use cases
E-commerce teams launching a new collection generate SKUs while the creative brief is still in Figma, letting developers wire Shopify or WooCommerce metafields before photography lands. Retail store associates rely on consistent prefixes printed on shelf tags so back-of-house systems line up with POS search. Warehouse operators scanning inbound cartons match supplier labels to internal codes faster when the pattern encodes category and variant at a glance.
Third-party logistics partners often require flat files with vendor SKU, inner pack quantity, and customs descriptions—having a deterministic generator reduces the back-and-forth when onboarding hundreds of variants. Wholesale catalogs distributed as PDF and CSV can embed the same codes buyers later type into B2B portals, which prevents “similar but not identical” strings from fracturing demand planning. Multichannel sellers mirroring Amazon, eBay, and proprietary storefronts reuse one internal SKU per variant, while marketplace-specific fields stay separate; this tool focuses on that canonical internal identifier.
Shopify merchants map SKU to inventory items, bundle components, and fulfillment integrations; WooCommerce stores attach SKUs to variable products for XML feeds. When marketing later needs polished descriptions or policy text, teams jump from this utility to the Product Description Generator, Grammar Checker, or SynthRead readability tools without leaving SynthQuery’s ecosystem.
How SynthQuery compares
Paid Shopify apps and enterprise inventory suites bundle SKU helpers with subscription fees, workflow automation, and sometimes server-side generation that logs your catalog structure. Spreadsheets cost nothing but hide formula errors until import day. SynthQuery targets operators who want transparent segment rules, immediate preview, cryptographic optional tails, and exports without creating another vendor relationship. The comparison table highlights practical trade-offs without naming specific third-party products.
Aspect
SynthQuery
Typical alternatives
Execution location
Runs entirely in the browser; SKU strings are not uploaded for generation.
Cloud SKU wizards may process files on vendor infrastructure—verify each policy.
Cost
Free as part of SynthQuery Free tools; no per-row metering on this page.
Shopify apps and WMS modules often bill monthly or per seat.
Integration depth
Exports lists for you to import—no direct API write to Shopify or WooCommerce.
Inventory platforms may push SKUs straight into live environments with audit trails.
Taxonomy governance
Encodes your chosen segments explicitly so teams agree on structure before PLM sign-off.
Enterprise PIMs enforce workflows but require longer implementation cycles.
Adjacent content tools
Same ecosystem as AI detection, readability, plagiarism, and marketing generators.
Standalone SKU utilities rarely connect to copy quality workflows.
How to use this tool effectively
Follow the steps below when onboarding a new category or refreshing an old catalog. The same sequence works for brick-and-mortar assortments, DTC launches, and marketplace variants because it starts with rules, not spreadsheets.
Step 1: Define your SKU format (segments and separators)
List the attributes that must survive from purchase order to pick ticket—often category, product family, variant dimensions, and a disambiguator. Enable matching segments in the UI, choose dash, underscore, or no separator, and decide whether the category prefix is a reserved manual code or an auto-generated placeholder for testing. Toggle the random segment only when you truly need extra entropy; otherwise lean on sequential numbering for auditability.
Step 2: Enter category, product type, and variant info
Type the short codes your operators already use (for example TSH for tees, M for medium, BLK for black). If a segment is enabled but left blank, the generator stops with a clear validation message instead of silently emitting malformed strings. For CSV workflows, put one product per row with headers such as prefix, product_type, size, and color—the parser accepts sensible aliases—then click Apply CSV or upload a file.
Step 3: Set quantity and generate SKUs
In template mode, pick 10, 50, 100, or 500 rows and press Generate SKUs. Sequential numbers advance from your chosen start for every row, and random tails refresh per line when enabled. In CSV mode, generation walks your parsed rows, still incrementing the sequence so you can merge the output back to the sheet by row order.
Step 4: Copy or download your SKU list
Use Copy all for a quick handoff in Slack or email, or download .txt for plain pipelines and .csv for Excel or platform importers. Before production, load a micro-batch into staging, verify uniqueness constraints, and confirm your storefront normalizes case the same way the generator does.
Limitations and best practices
SynthQuery does not replace your inventory database, channel APIs, or legal contracts with suppliers. It cannot detect whether a generated code already exists in production, enforce channel-specific length caps, or block trademark conflicts—those checks belong in your PIM, ERP, or legal review queue. Random segments reduce collision risk but are not a substitute for centralized sequencing when finance requires gapless audit logs.
When importing CSV files, ensure UTF-8 encoding, watch for smart quotes pasted from email, and trim leading spaces in supplier extracts. Test imports in staging with partial files before running full-catalog updates on Black Friday week. If your OMS strips non-alphanumeric characters differently, align sanitization rules with IT. For invoices, warranties, and customer-facing references, pair SKU discipline with the Invoice Generator and policy tools in Free tools, and route finished prose through grammar and plagiarism checks when accuracy matters.
Model cost of goods sold and inventory math after SKUs tie variants to purchasing data.
Frequently asked questions
A SKU (stock keeping unit) is your organization’s unique pointer to one purchasable variant—think “medium black crewneck” rather than the entire brand. You need SKUs so purchasing, warehousing, accounting, and ecommerce channels can reference the exact item without relying on long titles that change with marketing. Good SKUs reduce mispicks, simplify cycle counts, and make analytics trustworthy because every sale maps to a stable key.
The best format is the one your cross-functional team can explain without a decoder ring, yet stays compact enough for labels, scanners, and CSV columns. Many retailers combine a short category prefix, a product family code, variant attributes (size, color), and either a sequential number or a random disambiguator. Avoid embedding purely temporal data unless you truly retire codes each season; otherwise historical reports become unreadable. Document the pattern in a style guide and enforce it at import time.
Length is dictated by channel limits, label print area, and human memorability. Ecommerce platforms often allow dozens of characters, but longer SKUs increase typos in phone orders and manual spreadsheets. Aim for the shortest string that stays unique across your catalog—often 8–20 characters for SMB retailers, longer when you encode multiple dimensions. Preview in this tool while watching how the string wraps on mobile admin apps.
Spaces and exotic punctuation frequently break importers, shell scripts, and URL parameters. SynthQuery sanitizes segments to letters and digits so exports align with conservative platform rules. If you absolutely need punctuation, confirm how Shopify, WooCommerce, or your ERP normalizes inputs—many systems trim spaces or collapse case. When in doubt, stick to A–Z, 0–9, and your chosen separator style outside the stored tokens.
Reserve two- to four-letter prefixes per merchandise division (for example ELC for electronics, APP for apparel) and never reuse a prefix for unrelated families. Within a prefix, use consistent positions for product type, variant dimensions, and counters so sorting spreadsheets feels intuitive. Train buyers and planners on the schema early; taxonomy drift costs more than a few hours in documentation. This generator’s prefix field enforces the letter-only rule when manual mode is enabled.
Yes. Paste CSV text or upload a UTF-8 file with headers such as prefix, product_type, size, and color—the parser recognizes multiple alias names. Each row becomes one SKU using your global segment toggles, with sequential numbers incrementing row by row. Fix parser errors in the UI before generating, and keep backups of the source sheet. Only the first five hundred rows run per pass to keep the tab responsive; split larger files if needed.
A UPC (universal product code) is a standardized, globally unique barcode digit string managed by GS1 for retail POS scanning. A SKU is internal—it can encode whatever structure helps your company operate, and two retailers might use different SKUs for the same manufacturer item. You might print both on a label: UPC for checkout compatibility, SKU for your WMS. SynthQuery’s Barcode Generator can help visualize barcodes once you have the numeric payload you need.
Template mode offers batches of 10, 50, 100, or 500. CSV mode processes up to five hundred data rows per run, warning you if more rows exist in the file. Run multiple passes with updated sequential starts when you need thousands of codes, and deduplicate inside your database because the tool cannot see production inventory.
Treat them as case-sensitive when designing, even if some channels normalize to uppercase, because accidental collisions (sku123 vs SKU123) cause subtle fulfillment bugs. Pick one convention—usually uppercase for omnichannel—and stick to it. This tool includes an uppercase output toggle so exports mirror your standard.
Yes, as a planning and export aid. Generate or import SKUs here, download CSV, then use Shopify’s or WooCommerce’s product import tools with their required column mappings. Validate uniqueness inside those platforms; they remain the system of record. Pair with SynthQuery’s Product Description Generator for copy, Barcode Generator for label proofs, and Grammar Checker for policy pages that reference your codes.