An Ontology inclusive of all fashion concepts, to understand and manage your products and your shoppers
We build your Fashion Ontology.
Your ontology will help you describe products and shoppers in a way that allows you to:
Your ontology will help you manage your catalogue with new browsing methods, humanized categories adapted to different types of shoppers or situations. It will reflect how your organization wants to talk to shoppers, always retaining total control over your voice while understanding the voice of your shoppers.
It will guide your data-attaching mechanisms to attach the right descriptors to products and shoppers. Data-attaching mechanisms include your taste graph, your editors, your deep learning algorithms, and other sources of product and shopper descriptors.
Your Fashion Ontology is a tool that contains the organized and structured descriptors that define your products and your shoppers, in the terms that are relevant for your organization and your shoppers.
The Fashion Taste API main focus has been about the search for structure, in the unstructured world of clothing classification.
Once we learnt about clothing classification, we learnt that purchase drivers go well beyond clothing taste, and we gave a structure to those as well. So, believe us, we love clean and structured data that our algorithms can work with.
Despite of the above (or because of the above), we have found amazing value in shoppers' unstructured input. This input are descriptors that you would not expect your shoppers to be using when interacting with you.
We've learnt that people refer to their fashion needs in ways that are very different to how retailers do. Also, the type of taxonomies that fashion retailers tend to have cover mostly product descriptions. But drivers of purchases are related to other factors: products, occasions, influencers, brands and trends. You can read about it here.
The Fashion Taste API gives you easy access to a categorized list of all descriptors that people use in your web/app... that you don't have in your taxonomy. This input might come from the search box, or voice input in you have it, or any other field where shoppers write or say something unstructured.