Tag: attributes

True Demand Intelligence – Knowing who is buying what, where and why

SKU numbers are an easy way to keep track of items that are built, stocked and sold. The SKU number itself is arbitrary and contains no ‘intelligence’.

The SKU number was invented for a very good reason. When this practice started, the number of SKU’s was small, and people and systems needed a simple way to track what they had. So ASP-678 may be the SKU number for a toothpaste tube with spearmint flavor, whitening, and tartar control. However, customers do not look for SKUs. They look for toothpaste with whitening, tartar control, flavors, sizes, etc. Customers buy attributes, and combinations of attributes. Some companies code the attributes into the SKUs, by concatenating two or three character codes (like SPWHTC). But this is at best a clumsy way of handling a few attributes. Companies want to know what attributes customers are looking for, and SKU numbers hide the attributes.

As the number of attributes starts to grow, whether you have them coded into the SKU number or not, the problems start to mount! The most important one is that companies do not know what customers are buying, or trying to buy. As the number of choices grows, the number of combinations grows much faster and companies drown in their own SKUs.

SKU intelligence is going behind the SKU numbers and ‘detecting what attributes customers are buying’. Knowing who is buying what, where and why is “True Demand Intelligence”.
Products have attributes. For example, a computer has a processor, a memory, and a hard drive. For each attribute there may be several alternative choices. This means that there are many different product configurations. Some companies make only a fixed subset of all the possible configurations and give each one a SKU number. Other companies allow customers to order exactly what they want, and if this is something new, then they create a new SKU number for it. In either case, a SKU number is supposed to represent a unique product configuration.

If you are trying to figure out what your customers want, then SKU numbers are a form of encryption. You have to look at your sales history in terms of the underlying attributes, and the choices for those attributes. Instead of looking at one SKU number you need to look at perhaps 20 separate attributes. The SKU number is a way of collapsing those 20 dimensions into a single dimension, with tremendous information loss. One of the things that is lost is proximity to other SKU’s, based on attribution. A customer who bought SKU A-1234 might have been satisfied with (or really looking for) SKU B-3728. These two SKUs have the same choices for 18 of the 20 attributes, and differ on only two. This is obvious when the unique configurations are represented as a set of attribute choices, but hidden when they are represented as SKU numbers. The first step in analyzing a sales history has to be expressing it in terms of the underlying attributes. Each SKU number has to be expanded into a list of choices. Then we can begin to find patterns in how the choices are made. The leather seats and the DVD player are usually bought together. Engine block heaters are not ordered on convertibles. Buying patterns exist at the attribute level, not at the SKU level.

“Buying patterns” are popular combinations of attribute choices. These can be pairs of attributes, triples of attributes, or even more. Popularity is measured by the share of sales that have that combination. Buying patterns are helpful in selling, because they reveal how customers can be moved to configurations (SKUs) that we have in stock, or that we would prefer to build. Experienced sales people are skilled at moving customers, but If these patterns are represented in some kind of knowledge base, then a computer can make the recommendations.

Customers also have attributes. The simplest is perhaps geographical location. There are patterns that involve both product attributes and customer attributes. Customers in Florida are more likely to buy convertibles; customers in North Dakota are more likely to buy engine block heaters. Customers may have several attributes, for example demographic attributes for individuals or industry attributes for companies. (We don’t assign SKU numbers to customers!) If your sales history contains information about the customer as well as information about the product, then we can look for buying patterns that are associated with certain kinds of customers.

As an example, for a desktop computer the list of attributes might be: Processor, Memory, Hard Drive, Keyboard, Monitor, Mouse, CD/DVD, Application. A specific SKU number like A-1234 is a code for a specific configuration, say (2GHz, 2GB, 120GB, Ergonomic, 22” flat panel, Wireless, R/W Combo, Gaming). The Application attribute is really a customer attribute, with values like Home, Small Business, or Entertainment, as well as Gaming. This would make it possible to look for typical Gaming configurations and typical Entertainment configurations.

SKU numbers are a useful shorthand for record keeping. Each SKU number represents a unique product configuration. But analyzing SKU numbers is like analyzing telephone numbers. To see the buying patterns, you have to go to the attribute level. The patterns exist among the attributes, so you have to decode the SKU numbers to see them.