In my last blog post in the series “API Terminology Explained”, I explained the difference between product type, product and article. In this blog post, I will give you more details on our product type model.
Understanding the Product Type Model
In our terminology, a product type represents the pure piece or apparel, e.g. a T-shirt, as we get it from our supplier, e.g. American Apparel. A typical product type, e.g. a yellow T-shirt from American Apparel in size M, is illustrated in the picture above. A product type has the following characteristics:
- Core data: Each product type has a set of core data, such as name description and price.
- Appearances: A product type has one or more appearances. An appearance describes a pattern/color combination for a piece of apparel, e.g. a yellow T-shirt (no pattern/yellow color) or a camouflage T-shirt (camouflage pattern/light green and dark green as colors). It’s important to understand that we are not able to print with each available print type, e.g. flock, flex or digital direct, on each available product type. Therefore, we define for each appearance, which print types are allowed.
- Sizes: A product type has one or more sizes, such as S, M or L. Please note, that size information may vary between different product types. Sizes for adults are for example different from sizes for babys or kids.
- StockStates: Each product type provides stock state information for all allowed appearance/size combinations. We tell you for each combination, whether we have that in stock or not. Continue reading “The Product Type Model (API Terminology Explained #2)”