The short version
SKU creation is a rules problem, not a writing problem.
A reliable SKU should uniquely identify the product or variant it belongs to and remain stable as that product moves through inventory systems, marketplaces, fulfillment workflows, and internal reporting.
That makes SKU generation a good candidate for deterministic automation. The structure can be defined once, generated consistently, checked for collisions, and reused everywhere the product appears.
The goal is not to encode every possible fact into the SKU. The goal is to create a predictable identifier that can be generated and understood without introducing ambiguity.
Where manual SKUs break
Manual identifiers create hidden inconsistency as the catalog grows.
A small store can often get away with creating SKUs by hand. Someone abbreviates the product name, adds a size or color, checks that the result looks unique, and moves on.
The weakness of that approach becomes visible when more people, products, variants, and marketplaces are involved. Different abbreviations appear. The same color receives multiple codes. One marketplace uses an old SKU while another uses the new version.
Eventually the SKU stops functioning as a stable identifier and becomes another field that needs to be interpreted.
Typical failure pattern
Variant created
↓
SKU invented manually
↓
Marketplace copies it differently
↓
Product identity begins to drift
A good SKU system
A SKU should be stable, unique, predictable, and boring.
The best SKU systems are usually less clever than people expect. They do not need to communicate every product characteristic to a human reader.
They need to create one durable identifier for one product or variant, using a structure that can be generated repeatedly without interpretation.
A SKU can include meaningful components such as a product ID, size code, or color code when those components help the business operate. But every component should come from a controlled mapping rather than free-form text.
Structure
Build a SKU from controlled components.
A common pattern is to combine a stable product identifier with deterministic variant codes.
Product ID
Size code
Color code
Final SKU
Example pattern
PRODUCT-SIZE-COLOR
The important part is not the exact format. It is that every component is generated from controlled product data rather than typed or interpreted manually.
Variant codes
Map attributes to codes instead of abbreviating them on the fly.
If color and size appear inside the SKU, those values should come from explicit mappings.
Controlled size codes
Map each supported size to one stable code so the same size is represented identically across the entire catalog.
Controlled color codes
Define a single mapping for colors rather than allowing BLK, BLACK, BK, or other ad-hoc abbreviations to appear.
Stable product identity
Keep the product-level identifier independent from titles or names that may change for merchandising or SEO reasons.
Explicit variant combinations
Generate SKUs from actual supported combinations instead of assuming every attribute combination is valid.
Validation
Generating the SKU is only half the job. The system also needs to prove it is safe to use.
Before a generated SKU becomes authoritative, deterministic checks can verify that it follows the expected format and does not conflict with an existing product.
Generation rules
- Allowed character set
- Maximum length
- Required components
- Known attribute codes
- Stable formatting
Integrity checks
- Uniqueness
- Collision detection
- Variant existence
- Product relationship
- Idempotent regeneration
Multi-channel identity
Your canonical SKU and a marketplace identifier are not the same thing.
Marketplaces may create their own listing IDs, offer IDs, product identifiers, inventory references, or parent-child relationships.
Those identifiers can be stored alongside the canonical SKU, but they should not replace the business's internal product identity.
Keeping those layers separate makes it possible to map the same SKU into Etsy, eBay, Amazon, or another channel without letting one marketplace become the source of truth for the product.
Where AI does not belong
Do not ask a language model to invent your SKU.
SKU generation has a defined correct answer. Given the same product and the same variant, the system should produce the same identifier every time.
That is the opposite of the kind of open-ended semantic task where AI provides value.
AI may help optimize the title, description, tags, or categorization around the product. Product identity should remain deterministic.
In the larger system
SKU generation belongs near the product model, not inside each marketplace workflow.
Generate the business identifier once, attach it to the canonical product or variant, and then let marketplace adapters reference that identity.
Product data
SKU rules
Canonical SKU
Enrichment
Channel mapping
Marketplace
Live example
Variant identity can be generated alongside the rest of the listing workflow.
In the DDC Listing Engine, product variants are generated from structured product data. SKU construction, size and color relationships, pricing, imagery, and marketplace structures can therefore remain aligned instead of being rebuilt manually for each listing.
The result is not just faster listing creation. It is a more consistent identity layer underneath the catalog.
See the Decal Design Center case study →Related architecture
A SKU system works best when the catalog itself has a stable source of truth.
If product identity, variants, pricing, and marketplace data are currently maintained separately, start with the underlying catalog architecture.
Read the multi-channel catalog guide →Etherfolk Systems
Encode the rule once instead of rebuilding identifiers by hand.
Etherfolk Systems builds catalog and marketplace workflows around stable product data, deterministic business rules, and channel-specific integrations.
SKU generation can sit alongside variant construction, pricing, image mapping, validation, AI-assisted optimization, publishing, and reconciliation as part of one larger operational system.
Explore marketplace integrations →Still creating product identifiers by hand?
If SKU creation becomes harder every time you add products, variants, or marketplaces, the underlying rule can usually be made explicit and automated.
Discuss a catalog workflow