Cleaner, more responsive design

Improved Search and Filter functions

The Add Product modal has been simplified

Product Cards displayed Product Name, ID, and Image only.

Style names were truncated to fit on each card.

Season and Year were only displayed in "Quick View."

Season, Year, Date Created, and Creator are all displayed on Product Cards

The Quickview option is no longer available (See more info here.)

The toolbar is revised - the search bar is smaller, the arrangement of the Filter / Sort / View Toggle actions has been adjusted, and the (+) Add Product button has moved from the bottom right to the top right of the page

List View now displays "Created Date" instead of "Last Modified Date"

The Library can be filtered based on any Product-Level Taxonomy or Custom Field

Custom Field Dividers now display in the Filter Drawer

Filters now include "not set" to include filter styles with fields that are undefined

The (+) Add Product button was located in the bottom right-hand corner

The New Product modal opens as a full-page overlay

The modal is overly complex - listing all Custom Fields and Product details

The + Product button is located in the upper right-hand corner

Adding a New Product opens a small modal

Users may only assign Name/Code and Taxonomy level data in this modal

Style Number is now a required field

We saw only about 10% adoption of this feature across our client base. We reached out to some of the folks who were using this feature, and the majority of them were relying on it just to check the Season, Year, Creator, or Creation Date for a Product without being made to open its whole record. By elevating these data points to the card/row for each Product in the main library page, we solve this use case without the need for an extra click. Removing the Quickview from the Product Library reduces complexity and optimizes the page for its most important functions.

In place of Quickview, we recommend creating an All Products Line Sheet. This will allow you to quickly view your full Product Library and individual Product attributes all on one page. Check out the video below for details.

We offer a nicer dedicated experience for uploading image files in the Image section of each Product Record. Uploading images there is best practice as you can immediately organize the images into relevant subsections, adjust captions as needed, and more. Plus, streamlining the steps to create a New Product allows you to work faster and removes the risk of data loss if you don’t remember to click “Save”.

We offer a nicer dedicated experience for setting Custom Field values in the Summary section of each Product - or in the Item View. Setting Custom Field value there is best practice as you can also access your Variant level Custom Fields. Plus, streamlining the steps to create a New Product allows you to work faster and removes the risk of data loss if you don’t remember to click “Save”.

Only 5% of New Products were created via the Global Navigation panel - 95% were created within the Product Library already. Removing the little-used option from the Global Navigation panel helps bring focus to the key job of the panel, which is to facilitate access to the different areas of the app.

Fewer than 2% of Tech Packs were generated using this method in the last year - the vast majority of our users generate their TPs via the TP ledger within a Product Record. Continuing to support this feature was going to require a significant technical lift due to some incompatibilities with our new front-end framework and our old one. The Library is written with newer technology that is much more performant and scalable. Eventually, we will also rewrite the Generate Tech Pack modal in this newer technology. At that point we hope to introduce better tools for creating many Tech Packs at once. But for now, our priorities lie elsewhere, enhancing features that are more widely used.

Users reported the Style Numbers we used to generate automatically were confusing and didn’t add a lot of value, since they were just a random string of numbers and letters. It wasn’t always clear to users that these Style Numbers could be overwritten. Typically brands have an internal logic that dictates the correct Style Number for a given Product (like two digits to represent the season, two to represent the year, one to represent the gender, etc.) and would prefer to just key these in directly without the need to highlight/delete the default value first.

If your brand does not generate this kind of Style Number, or if you find yourself creating a Product Record before its Style Number is known, we recommend typing in a standard value like “-” or “XXX” as a placeholder going forward.

How to generate a unique code for the Style ID: