We have built a system to “classify clothes” automatically, with 175 million classified and correlated meta-products. This system allows us to automatically understand, manage and act upon any collection from any retailer (similarities, correlations, recommendations…)
To explain it easily, this system is like a brain that understands clothes and outfits, and allows you to organize and display products at your convenience, or your shopper’s convenience. It was constructed after analyzing millions of perfectly described outfits and fashion products uploaded to our system by different subsets of users of Chicisimo, and after analyzing how people interact with them.
The system converts fashion products into meta-products, which are abstractions of specific products of any catalog or closet. A fashion product is ephemeral, but its descriptors are not, so the system retains the value.
A meta-product is the most basic yet relevant description of a product, and one of the first tasks of our infrastructure is to convert any incoming fashion product into a meta-product. While a person might see a given garment, our system reads a set of descriptors, for example: burgundy + sweater + v-neck + comfy + casual + for school + size 42 + cashmere, etc.
For any given retailer, this system can automatically digest its catalogue and then, automatically: (i) Understand each product; (ii) Identify missing information; (iii) Identify similar products, defining similarity in a number of ways; (iv) Build complete looks mixing and matching the clothes in the collection; (v) Identify products that make sense to display together; (vi) Recreate any outfit with garments of the catalogue; (vii) display the correct products for each shopper, or for the current interest of each shopper; (viii) If the system detects a product that it cannot understand, it isolates the descriptor and incorporates it into the fashion ontology if the team so wishes.
Technology is opening up a lots of options for fashion and we want to be very clear about what we consider the true building blocks are.
Here’s our view, our Manifesto, for the Future of Fashion Retail:
1. A TASTE GRAPH FOR EACH RETAILER
Each fashion retailer will own its Taste Graph like Pinterest does.
This Taste Graph will contain the intelligence generated by shoppers and their interactions with products. A Taste Graph is your unique data asset and engine to build a competitive moat around your business.
We at the Fashion Taste API respect the data concerns of our customers and have committed to making sure they can use our taste profile and personalization technologies, safely and compliantly. We are committed to the confidentiality, privacy and security of our customers data.
The Fashion Taste API works with respected teams
At the Fashion Taste API, our team believes that the ultimate customer experience relies strongly on transparency and integrity. The Fashion Taste API works with respected teams of IP and data privacy lawyers, financial experts and Venture Capitalists as venture partners.
We are dedicated to meeting global requirements and regulations when it comes to data protection, privacy, security, and operations. Having your trust as a partner in taste profiles and personalization is of the utmost importance to us, and we will continue to invest extensive resources toward maintaining the highest possible industry standards so you can use our technology safely, efficiently, and compliantly.
Fashion Taste API & GDPR
Fashion Taste API is committed to the confidentiality, data privacy and security of its customers and their end-users. We are and will continue to invest extensive resources towards maintaining the highest levels of data protection, privacy and security standards. We are compliant with applicable laws and regulations, and are committed to our ongoing compliance with the EU General Data Protection Regulation (GDPR) and related guidelines.
Data Storage. Fashion Taste API stores customer data in Ireland. Fashion Taste API has proxies deployed in Sao Paulo and Oregon to reduce latency and increase response time in those areas.
Satisfy the Definition of a Data Processor- “Processes Personal Data on behalf of the Controller”. Fashion Taste API provides a full fledged platform which allows marketers to segment and target users with personalized offerings across web, mobile, email and other channels. As such, Fashion Taste API processes its customers’ end-user data, thus, Fashion Taste API customers who are deemed as “Data Controllers” under GDPR and the end users would constitute the “Data Subjects” whose rights must be protected.
Act on Behalf of the Controller Based on Controller Authorization. Fashion Taste API only collects information based on a duly executed contract from the controller. Once an agreement to process data is terminated, Fashion Taste API ceases collecting personal data from the customer’s sources, and the records are deleted within a reasonable period of time from when a deletion request is made. The purposes of the data processing are determined by our customers, i.e. the Controllers.
Appointment of a Data Privacy Officer (DPO). Fashion Taste API has appointed a Data Privacy Officer who oversees our privacy compliance and development program.
Integrity and Confidentiality. Fashion Taste API has employs appropriate technical and organizational measures to safeguard Personal Data.
Demonstrate Compliance with GDPR. Fashion Taste API keeps a record of its processing activities carried out on behalf of the controller, its DPO is open for questions and data processing addendum is entered into with every customer.
Lawfulness, Fairness and Transparency. Fashion Taste API collects and processes Personal Data lawfully and is transparent with its customers about its processing activities. Fashion Taste API has entered with its customers in order to maintain the legal basis for the processing (usually “consent” or “legitimate interest”), which is warranted by the customer as the Controller.
Processing Personal Data- Purpose Limitation. Fashion Taste API only collects data which may be used to analyze user behavior and to provide personalized experiences. Fashion Taste API does not combine any customer collected data with data collected from other customers, does not determine the purpose of processing, and does not share data with third parties except where required to by law.
Processing Personal Data- Data Minimization and Proportionality. Fashion Taste API does not onboard any data which is unnecessary or disproportionate to its needs to best serve end users with personalized experiences. CRM and other data may be onboarded and Fashion Taste API expects its customers to only onboard data which satisfies the proportionality and lawfulness requirement. At the point when Fashion Taste API provides a mechanism for onboarding customer data, we request that sensitive or payment data not be onboarded without our consent.
Processing Personal Data- Accuracy. At the point when Fashion Taste API provides a mechanism for onboarding customer data, Fashion Taste API will allow its customers to rectify any errors or misapplications in onboarded data with new CRM data pushed by the controller.
Processing Personal Data- Storage limitation. Fashion Taste API does not store any data unnecessarily and (at the point when Fashion Taste API provides a mechanism for onboarding customer data) expects its controllers to refrain from onboarding data which is unnecessary for personalization purposes
Processing Personal Data- Accountability. Fashion Taste API’s DPO will work to continuously optimize and introduce improvements and customer feedback to the Fashion Taste API privacy program. The DPO will also cooperate with controllers in case of inquiries and data breaches.
Data Subjects Rights. Erase, Rectify and Export Personal Data. Fashion Taste API will cooperate in full with controllers for handling requests regarding their end users’ data.
Information Provisions- Transparency. Fashion Taste API will cooperate with controllers regarding data requests from customers.
Ownership of Data, Process and Tool. It is now gone the time to provide personalized recommendations to people, without understanding their taste. The Fashion Taste API has been designed to empower teams to own the process, the tool, and the data, while maintaining the highest levels of data protection, privacy and security standards. • DATA PRIVACY: The Fashion Taste API is committed to the confidentiality, data privacy and security of its customers and their end-users. We are and will continue to invest extensive resources towards maintaining the highest levels of data protection, privacy and security standards. • PROCESS & TOOL: The Fashion Taste API does not interfere with any of your existing processes. It starts registering data, as easy as installing Google Analytics. You speed up with whenever you want, with the advantage of having already learnt from the captured data. The fashion industry no longer believes in black-box approaches to personalization that provide zero ownership and control to teams. The Fashion Taste API is a tool for your teams to use on growth. You control the tool.
Apart from the increase in market share that this new category will generate, In-Bedroom Fashion Stylists will have two very relevant consequences:
Data: The amount of incoming taste data will grow exponentially;
Learning: The speed of learning will accelerate thanks to better shopper feedback.
And the current competitive moat around traditional fashion retailers will be gone.
THE VIRTUOUS CYCLE OF DATA
The more digitally powered experiences you offer, the more taste data you will capture. The more data you capture, the better you can automatically serve your shoppers. The better you serve your shoppers, the more adrenaline you generate in your teams, the more ambitious they become.
A SYSTEM TO TAG FASHION IMAGES WITH SHOPPABLE PRODUCTS
We are all starting to see fashion images with dots on top of them, these dots enabling you to find and buy the products in the picture. This system is gaining popularity since 2016, and it was patented by us in 2013.
A SYSTEM TO CAPTURE AND UNDERSTAND HOW CLOTHES IN OUTFITS AND CLOSETS ARE MIXED, MATCHED AND RELATED
In our prior work with music, we extracted relations among songs by analyzing the sequence in which people would listen to music, and by analyzing our interpretation of items. Apple later bought the systems and patents for Apple Music. We then built similar systems for personal finance, and for content-agnostic input.
With this background, we thought that an outfit was like a playlist of songs: a way to communicate that it makes sense to consume several items together. This simple concept allowed us to conceptualize the first version of our Social Fashion Graph. In 2013, we protected a system to capture and understand how people mix and match clothes in outfits and closets.
Today, the technology has evolved significantly. It captures any input in our our Ontology, which includes any concept relevant to fashion, and assigns descriptors to products and to people. We can extract all type of relations among analyzed items.
SEARCH ENGINE FOR FASHION IMAGES AND OUTFIT IDEAS
Our initial interest was related to social tagging of images. Then, we invented more complex mechanisms to assign descriptors to clothes, outfits and people. Our IP protects a system to search outfit ideas and fashion images.
It could be a simple query such as “give me ideas to wear jeans” or a more complex one such as “give me ideas to wear my pair of red pants with my floral shirt, to go to the office in winter”, or “give me clothes that are “similar” grouped by your concepts of similarity”. This is strongly related to our Fashion Taste Graph Technology.
The Fashion Taste API patents are expected to provide a competitive advantage.
Our fashion ontology is our tool to understand products and people, and we built it to respond to very specific needs in our mobile apps.
Why we built our fashion ontology?
Fashion lacks a standard to classify clothes or to refer to the variety of concepts that describe products, styles, and personal fashion preferences.
At some point, we found ourselves receiving a lot of data via our consumer apps. We were receiving millions of described outfits, the described clothes in millions of closets, and hundreds of millions of what-to-wear queries from people trying to decide what to wear
Looking at this data, we only saw unorganized data, so chaotic that it was impossible to manage or build on top of it.
Our users could not really express their needs precisely in a ways that we could understand them, we couldn’t even describe the content displayed in our apps, in a way that could be found by those in need of it.
The backbone of our Taste Graph
Today, our fashion ontology is the backbone of our Taste Graph technology, and it is core to our development process.
We divide our ontology into two parts:
Products ontology. It is a 5-level ontology that describes products and subjective characteristics of products;
Outfits ontology. It is a 2-level ontology that describes outfits, mostly with subjective descriptors.
Our fashion ontology today
Our fashion ontology is our tool to understand products and people: it goes well beyond assigning descriptors to clothing. It has a very strong emphasis on describing people.
Our ontology today is the classification of descriptors needed to define a fashion product and a shopper’s need, in terms that are relevant for shoppers, for retailers and for data scientists. It contains the vocabulary used by people and by fashion retailers, with an understanding of how these descriptors are used together. Our ontology covers all aspects related to fashion purchase drivers: product properties, occasions, brands or influencers, or trends: It is formed by +2500 unique concepts and a few hundreds of thousands of descriptors.
What we’ve built on top of the ontology?
All our Chicisimo products have been built on top of our Fashion Taste Graph, and the ontology is it’s backbone. This is what the ontology has allowed us to build:
The ontology has also provided a unique common language for the team to communicate, and work, more efficiently.
How can I fashion ontology help your business?
Well, that’s a question you’ll have to answer prior to building one. You might already have a fashion taxonomy, and you’ll expand it little by little as your product team demands more tech strength.
In general, your fashion ontology will help you describe products and shoppers in a way that allows you to:
Understand products and shoppers;
Manage products and shoppers.
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.
Characteristics of our ontology
Again, it will depend on the state you are at. Your ontology or fashion taxonomy 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.
Your ontology includes clothing and non-clothing descriptors;
The ontology includes descriptors used by your organization, and by your shoppers;
Descriptors are classified in categories, types, properties and more;
We capture the correlations among your descriptors as defined by your products and your shoppers.
How can you use your ontology?
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.
Omnichannel Personalization with a Fashion Taste Graph allows retailers to understand and classify each product in their catalogue, and each of their shoppers.
How did we build our Fashion Taste Graph for Omnichannel Personalization
Through Chicisimo’s consumer apps, we’ve received millions of described outfits, the described clothes in millions of closets, and hundreds of millions of what-to-wear queries from people trying to decide what to wear.
With so much consumer data, we started capturing the correlations provided in the data, and built a fashion ontology to understand incoming input.
Described outfits: We capture this type of data from millions of described outfits and we also capture how other people interact with those outfit creating more relations among items and allowing the Taste Graph to assign further descriptors to the outfits and the Taste Profiles;
Described clothes in millions of closets: We also receive the described clothes in millions of closets from where we can extract a lot of meaning in terms of correlations and in terms of our own interpretation of the products;
Queries: We also receive hundreds of millions of what-to-wear queries from people trying to decide what to wear and what clothes to buy, for any occasion you can think of. Each of these queries informs the Ontology and the Taste Graph.
This is the origin of our unsupervised learning model. The Taste Graph Technology receives data and correlations. It also assigns the correct descriptors to clothes, outfits and to people. It is the tool on top of which teams can effectively work in personalization. Delivered via a website, in a physical store, or delivered via Alexa in a bedroom or closet. This model allows for omnichannel personalization with a Fashion Taste Graph.
A Fashion Taste Graph is more than a Shoppers Graph
Our Fashion Taste Graph Technology for omnichannel is a personalization engine that allows us to assign descriptors to shoppers. It allows us to understand the taste of each shopper, and provide them with personalized omnichannel recommendations.
The Omnichannel Personalization with a Fashion Taste Graph is the infrastructure and data that contains, manages and understands the taste of each individual shopper, what clothes she has in her closet, and what are the drivers behind her purchases. The behaviour of each individual, the aggregated behaviour of everyone, and the behaviour of any subset we’d want to target.
Should you build a Fashion Taste Graph?
We can help you build your taste graph.
Your Taste Graph contains the intelligence generated by your shoppers and their interactions with your products. It’s formed by your shoppers Taste Profiles, your fashion ontology, and your evolving catalogue of products.
Your Taste Graph is trained to assign descriptors to your products and your shoppers. It is your unique Omnichannel Personalization Engine.
By building your Taste Graph, you are retaining that intelligence and building the competitive moat around your business that will help you delight your shoppers, with true omnichannel personalization.
What can you build with your Fashion Taste Graph?
Your Taste Graph is allows you do work around automation of catalogue, personalization of content, building unique shopper experiences:
Deliver your collection based on the Taste Profile of each shopper.
Automate processes related to the management of your catalogue.
Identify shoppers who can help you identify trends.
Our Taste Graph Technology executes a number of processes to register the taste of each individual shopper, what clothes she has in her closet, and what are the drivers behind her purchases.
Imagine that someone buys a “red and black oversized sweater“. In our opinion, this is not necessarily a predictor of her future purchases, not a descriptor of her taste. We focus on looking for the true motivations of a purchase. That’s the role of the Taste Graph and it’s underlying backbone: the ontology.
We patented in 2013, and we’ve perfected it since then. Your Taste Graph captures all the taste-related activity and data generated in your properties. It captures all the relations among your shoppers, your products and your descriptors.
A strategic asset that improves exponentially
The Taste Graph forms a strategic and tangible body of data that provides you with the intelligence generated in your properties.
The more digitally powered experiences you offer, the more taste data you will capture. The more data you capture, the better you can automatically serve your shoppers, and the more data you will capture. It’s the the virtuous cycle of data. Read our Manifesto on the Future of Fashion Retail.
Your personalization engine
In terms of personalization, there is nothing more powerful that the data asset that understands the taste of each individual shopper, what clothes she has in her closet, and what are the drivers behind her purchases.
Any personalization attempt gets exponentially better, as you scale your Taste Graph. Any new sale, any new interaction, any new query or event, and your Taste Graph gets better, your personalization potential gets exponentially better.
This is strategic. If you are here to stay in the next years, you need this dataset. Also, any sustainable personalization strategy will require the intelligence behind data and correlations that you are most likely letting go today.