A lot of consumer brand companies and manufacturers deal with seasonal products. Keeping up with trends and demand, they may want to stock these products only for certain months of the year. On the other hand, many products remain useful and in-demand year-round. Companies who carry a mixture of seasonless and seasonal products at the same time need a system to keep it all in order.
When it comes to season codes, often you’ll see them embedded in style numbers. This is a mistake and could cause a problem If the company wants to sell a seasonal product across seasons, they will probably need to create a new style number for the same product and switch any remaining inventory from the old-style number to the new. There is a better way to manage season codes in modern
Take as an example a coat marketed for the autumn 2019 season. It might be designated as style CoatA19 ( A for autumn, 19 for 2019). Because the coat comes in various colors and sizes, variants might be created to differentiate them. CoatA19-Brown-Large would be different from CoatA19-Blue-Medium, and they would have different style numbers. What if this coat became extremely popular with buyers and your company decided to carry it for autumn and winter, or even year-round? Or what if you want to offer the exact same coat next year in the fall of 2020?
You would have to designate a new style number, perhaps CoatA20, as well as its variants like CoatA20-Blue-Medium. After creating dozens of new SKUs, you’d then have to change the held-over inventory from the old SKUs to new SKUs in order to sell them in the autumn of 2020. If you have to perform these steps with hundreds of styles, you’d be creating hundreds of new SKUs and hundreds of inventory transfers. Imagine the time involved.
Ask the fundamental question: what is the purpose of the season code? Do you want to document when the product was designed or manufactured? Do you need to track its selling season? You might find that there are multiple seasons to track. A better way would be to categorize the codes for design seasons that are attached to the product and transaction seasons, which could be attached to the transaction, e.g., sales.
Finally, it is more common to see colors, rather than styles, being carried across seasons. Perhaps you want to carry over CoatA19-Brown, but not the blue one. Seasons are more lined up with colors than the styles themselves. The right data model will link the season code (CY19) to a color (Brown) rather than the style (Coat).
The right ERP solution, such as