Best Practices for Creating a SKU value

Last updated about 5 years ago

When creating a new SKU, you should keep in mind the requirements for each channel, your ability to identify SKUs, and the ease of exporting/importing data. Some people prefer that all SKUs start with the brand or vendor they're attributed with. Some people have a number of product groups that vary by color and like to keep the color somewhere in the SKU value. Please keep in mind that SKUs are immutable in Zentail. Once a SKU value is saved in Zentail, it cannot be changed.

Based on our conversations with our clients, our understanding of each marketplaces' requirements, and our own experiences, here are our Do's and Don'ts:

Do the following:

  • Standardize your SKU values across integrations. This means, if your product is "medium123shirt" in one place, the same SKU should be named "medium123shirt" everywhere. Learn more about the importance of standardizing your SKUs here: Standardize your SKUs.
  • Keep the SKU length under 36 characters
    • The most significant constraint is Amazon- who has a 40 character limit on SKU length. In some cases, we will add "+MF+" at the end of your SKU value to create a merchant fulfilled version within Amazon's Seller Central.
  • Make it something you can readily identify
    • i.e. University of Maryland gear all begin with "UMD_"
  • Good SKU: UMD_SHIRT1_RED

Avoid the following:

  • Avoid leading zeroes
    • When exporting or importing data, leading 0's can get dropped if not formatted properly
  • Avoid leading periods or decimal points
    • A leading decimal point, followed by numbers, can incorrectly add a leading 0
  • Bad SKU: .111222333
  • Bad SKU: 0dell_XPS_black_13inch_laptop_computer_123

Related reading:

powered by
SlimFAQ