<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jean-Baptiste Sébrier on Medium]]></title>
        <description><![CDATA[Stories by Jean-Baptiste Sébrier on Medium]]></description>
        <link>https://medium.com/@jbsebrier?source=rss-6e9159f179fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kk6I_200Rc5Ls5MWp_ou6g.jpeg</url>
            <title>Stories by Jean-Baptiste Sébrier on Medium</title>
            <link>https://medium.com/@jbsebrier?source=rss-6e9159f179fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:51:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jbsebrier/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 Classic mistakes of master product data management]]></title>
            <link>https://medium.com/@jbsebrier/5-classic-mistakes-of-master-product-data-management-b135138a08fd?source=rss-6e9159f179fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b135138a08fd</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[master-data-management]]></category>
            <category><![CDATA[retail]]></category>
            <dc:creator><![CDATA[Jean-Baptiste Sébrier]]></dc:creator>
            <pubDate>Wed, 14 Nov 2018 15:20:01 GMT</pubDate>
            <atom:updated>2018-11-14T15:26:40.415Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Five Classic mistakes of master product data management</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zQy-RqEObNcuRfm3fZneQ.jpeg" /></figure><p>According to a recent Gartner survey, more than half of CTOs have put centralised master data management (MDM) as one of their top 3 priorities for next year’s roadmap, and 61% of companies that have launched projects on this topic are still in prototyping or planning phases. More alarming still is the fact that only 24% of MDM projects are rated “successful”.</p><p>Though the need for better structured data has never been higher (read our article about this <a href="https://medium.com/scalia/the-missing-piece-of-the-data-economy-puzzle-3adaf9a5b00d">here</a>), companies still struggle to clearly define the architecture, rules and tools needed to reach their data centralisation dreams. MDM remains critical in helping define how any modern business operates.</p><p>As per our observations, most of the time the problems hindering a proper set-up of master data management tools are always the same. This article gives an overview of top 5 data management mistakes and bad habits we have encountered so far. The risks ? Most of the time, these will induce irreversible data losses, staff discouragement and frighteningly ballooning costs for organisations.</p><p><strong>1. Tool-oriented processes</strong></p><p>Too often in any kind (and any size) of corporations we have witnessed processes and user behaviours where data and its target usage only come second to the tool and its actual functioning.</p><p><em>“I’ll put this otherwise I won’t be able to load it”</em></p><p><em>“It’s better to leave it blank”</em></p><p><em>“Actually it’ll save time to load empty columns and then edit manually”.</em></p><p>This kind of behaviour creates incomplete product data or situations where the least amount of data is created. Yet, the initial input actually included additional information that will be lost forever or — even worse — will have to be re-written manually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8-598f7H-lBB0i-6T1xzQ.jpeg" /></figure><p><strong>2. Twisted data structures</strong></p><p>One of the consequences of the previous issue will be a strange tendency to bend rules rather than making the data compliant. Data consistency guidelines set up at system installation will often block data integration, and users will eventually change the rules in order to be able to keep uploading their data.</p><p><em>“I’m not sure what this is about but if I put 1 for every product it works”</em></p><p>This will result in having multiple attributes for the same characteristic, generic product categories (easier than spending time categorising products to custom and relevant categories), or inputting the same value for every single point of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kauFnEF_55AgzNbZunbhyA.jpeg" /></figure><p><strong>3. Lack of vision / sponsorship in the taxonomy management</strong></p><p>In most organisations, setting-up a centralized data management system implies creating a company taxonomy from scratch (read more about this here). The issue is to find someone to do it. Usually that person will be picked among the teams in charge of data creation, turning into an <em>accidental taxonomist</em> as <a href="http://www.hedden-information.com/accidental-taxonomist/">Heather Hedden likes to call them</a>.</p><p>This person will have a huge challenge to tackle: collecting input from many actors, being as comprehensive as possible, having to take clear cuts (that will 100% of the time be reproached to her by part of the users)… If you add very limited resources available to help, usually no budget, and pile that on top of previous attributions, you can see disaster looming.</p><p>The responsibilities implied are extremely high though, given the impact on the final data management tool. It has become very common to say that in data management the “Garbage in, Garbage out” rule is key and to praise for quality of incoming data. But that is also very true for data management <em>tools</em> : if you don’t set it up right from start it will never be of any use.</p><p><strong>4. Lack of data management education of the key people</strong></p><p>It is frequent that the users of data management tools actually fail to understand why and how product data has to be managed. Deep and complete understanding of the product structure is key to ensure the quality of information management.</p><p>It is key for organisations to allocate part of their MDM project budget to the training of the team, onboarding of new team members and continuous learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c333d_YNEHG4q3UDb1wTA.jpeg" /></figure><p>I have in mind a corporation where the whole budget was eaten up by delays and consulting fees for set up and the system was launched without any training of the users, resulting in low traction and poor results.</p><p>Current state of MDM tools also require <em>data stewardship </em>(=costs) to keep the system running. Recent developments of artificial intelligence tend to show a solution might be coming though.</p><p><strong>5. Parallel universes</strong></p><p>One of the issues we frequently encounter is the duplication of data due to a combined use of various systems by one company. If an organisation has a PIM, an ERP and a CMS, it is very likely that the product information will be available in all three. This is a -regretfully- common set up close-coupled data systems. Worryingly, there might (and will) be inconsistencies in the data between systems.</p><p>Moreover, if those systems are silos, and as such are only connected through human work and/or hardcoded flows (export from one system, most likely transform the data and then import it in another system) and use different data structures, then the risk of error in data transmission will be increasingly high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIOXZClbNyqK8UXpqD9G3w.jpeg" /></figure><p>Data management projects are long and tough to set up but also complicated to keep running. It remains crucial from the start to acknowledge the need for processes and tools that will help the MDM system to live up to its promises.</p><p>One of the key issues is to manage the interconnectivity of systems, inside and outside the organization, and that is today too often left behind or managed by tedious and dull human work, blocking the scalability of the project.</p><p>Helping brands and retailers alike, Scalia offers an AI-powered solution to spur the connectivity of systems allowing to curb data losses and make sure data arrives in a system in the exact format expected.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b135138a08fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The do’s and don’ts of Product Taxonomy]]></title>
            <link>https://medium.com/@jbsebrier/the-dos-and-don-ts-of-product-taxonomy-e8b452c5dc78?source=rss-6e9159f179fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8b452c5dc78</guid>
            <category><![CDATA[taxonomy]]></category>
            <category><![CDATA[e-commerce-solution]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[retail]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Jean-Baptiste Sébrier]]></dc:creator>
            <pubDate>Tue, 03 Oct 2017 13:12:33 GMT</pubDate>
            <atom:updated>2017-10-06T11:23:20.262Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hfHQwrRXapj9xaN-Nv3bg.jpeg" /></figure><p>Launching a website, changing your back-office solution or simply reviewing your current organisation, there are many moments in a company life stage where giving a bit of thought to your product taxonomy will help you enhance your future performance and eventually save a lot of time in the future.</p><p>For those of you who haven’t read it yet, you can find out about the perks of a robust and well-maintained product taxonomy <a href="https://medium.com/scalia/why-scalia-decided-to-open-source-its-taxonomy-67e0cdf36d7d">right here</a>. After that previous publication, we’ve received a lot of emails asking what would be the best practices for product taxonomy, how to build an efficient category tree or how to differentiate between what’s category material and what should be treated as an attribute.</p><p>First of all, a bit of vocabulary about product taxonomy. There are three main tools :</p><p>1. The <strong><em>category tree</em></strong> (also known as product hierarchy): it helps group products by nature in a set of hierarchized categories.</p><p>Example: <em>Home &gt; Home Appliances &gt; Kitchen &gt; Cooking &gt; Rice Cookers</em></p><p>2. The <strong><em>attribute list </em></strong>(also known as <em>facets</em>,<em> dimensions </em>or<em> refinements</em>): additional information attributes, used to qualify the products in a same category. When applied to a product, an attribute will require a value.</p><p>Example: <em>Bowl capacity, color, type of sole …</em></p><p>3. The <strong><em>value list</em></strong>: for some attributes, the finite, predefined set of possible values, for Booleans (yes/no) or rich attributes</p><p>Example: <em>Blue, 1.5 litres, 220V, strong, …</em></p><p>Each attribute will apply to several categories, and have various values. Values are linked to one and only attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*Q3y4gp11WROM4Hs5V4wopQ.jpeg" /></figure><p>Understanding the relationships between those three tools is essential to the understanding of taxonomy design. What will follow is a set of advice based on our experience and research and intended to help the would-be and the seasoned taxonomists in their designing or revamping of product classifications</p><p><strong>How many is too many ?</strong></p><p>In our opinion a robust and understandable category tree should have a hierarchy depth of 3 to 5 category levels, and between 5 and 15 level one categories. This is of course dependent on the width of the assortment you are selling and your product normalization.</p><p>For the attributes, and the values, there’s no limit! The more you have, the more accurate product description will be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNCLj4TEJ0KvHREbZMyIXA.png" /><figcaption>A simple category hierarchy</figcaption></figure><p><strong>Where should I start ?</strong></p><p>Check your inventory and the products you sell. That should give you a good view on how deep your category tree should be. If you are running a physical store and wish to go online, do not necessarily replicate the organization of your store on your website categories. That might help the loyal customers, but the whole point of an e-commerce website is to go beyond your customer base and reach new customers. The use of physical space and the use of screen space are very different, as well as the customer behaviour online and offline. Remember that the categories will help your customer find your product, through navigation or search. Attributes will help the customer access in-deep information about the product.</p><p><strong>How should I name my categories and attributes ?</strong></p><p>Make it:</p><ul><li>Short</li><li>Self-explanatory (at least within your organization and for your target customer)</li><li>Unique (as much as possible)</li></ul><p>On the other hand, Attributes are to be re-used across the whole category tree and are stand alone. They are never too accurate, so don’t hesitate to have “Diameter of watch dial” and “Diameter of bicycle wheel”, rather than a global “Diameter”. That will strengthen your data consistency (maybe not all diameters are commonly expressed in the same unit), enhance the ease of use of people within<em> your </em>organization, as well as improve clarity for customers.</p><p>One thing we see a lot is a “Other” subcategory in almost every category. We strongly advise against this. Customers are never searching for “others”. While it might seem convenient for products not fitting in an existing category, it is always better to create the adequate category rather than having a messy and vague category. A category is never too small or too specific.</p><p><strong>So what’s attribute material?</strong></p><p>There is often a question about whether a difference in product nature should be treated as an attribute or a subcategory :</p><p><em>Example: should I have a category for denim shirts and one for jersey shirts, or a shirt category, with the attribute fabric = “denim” or “jersey”</em></p><p>The answer often comes with a bit of common sense and experience of the e-commerce industry (category = product class that can stand by itself, attribute = descriptive element that can be used on several product types), but there are a few rules:</p><ul><li>If you can re-use the qualifier on other categories (“denim jackets”), it makes sense to define it as an attribute (DRY = Don’t repeat yourself !)</li><li>It all boils down to having one additional attribute or one additional level of categories: try to balance between those two lists</li><li>Try to understand what your customers are looking for: would they consider denim a subcategory of shirts (i.e. they would look for denim shirts exclusively) or an additional information on the product ?</li></ul><p><strong>Should products appear in more than one category ?</strong></p><p>Offering the same product in several aisles of a physical store or various categories of a website can enhance the visibility of this product and thus its sales.</p><p>For instance a Ski jacket could be in Sports equipment and also in Apparel&gt;Jackets</p><p>Sometimes a product can be displayed also in a special category (“offers of the week”, “Best deals”…)</p><p>However that has to remain a front-end or store display option only. In your product management system or WMS, a product cannot be in more than one category. Otherwise, there are many risks: double-counting at reporting, mix-up in the stock management, inconsistencies in your purchase orders…</p><p>Most e-commerce software allow to display a product on several categories online, but this should be seen as a marketing tool only, and not infer with the product back-end management</p><p><strong>What level of standardization should I apply to my values ?</strong></p><p>Once again, choosing to standardize values for an attribute (= all the values for this attribute can only be picked in a pre-defined, finite set of values) is often a tough choice, mixing flexibility, IT constraints, ease of management of the product list…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JaArtFYUe-z8iIkMvv6JIA.jpeg" /></figure><p>We’re not going to deny that there are perks to a strictly standardized value system, among others:</p><ul><li>IT-wise, it helps ensuring the quality of the data appearing online</li><li>It can help to do cross-category and cross-attribute reporting or filtering</li><li>It keeps the consumer in known grounds and will be less confusing for him (I know what <em>Pink</em> is, but what colour is <em>Amaranth</em> ?)</li></ul><p>That might sound appealing, but one shall not forget the constraints:</p><ul><li>Having to reformat/”translate” all the information received from your suppliers can be extremely time-consuming if you don’t have the right tools (Scalia can help !)</li><li>You might be missing slight nuances in meaning</li><li>Forcing your system to accept only some values can, and will, lead to issues at product creation: products that will not update, system rejections…</li></ul><p>We believe this has to be done on an attribute-by-attribute basis. It boils down to the number of different values for an attribute. Managing a set of 8 or 10 shirt sizes is achievable, but some attributes just don’t do very well with fixed values even though it might seem possible to standardize, simply because there are too many possible values (<em>Brand</em>, <em>Color</em>…)</p><p>There are no strict rules to product taxonomy. However, the various elements listed in this article need to be thought of beforehand to make sure your product taxonomy will be able to help your business grow and never represent a hinder to your daily management. Having the right tools to help you manage and interconnect your taxonomy with your business partners is also a wise choice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8b452c5dc78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Scalia decided to open source its taxonomy]]></title>
            <link>https://medium.com/@jbsebrier/why-scalia-decided-to-open-source-its-taxonomy-67e0cdf36d7d?source=rss-6e9159f179fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/67e0cdf36d7d</guid>
            <category><![CDATA[scalia]]></category>
            <category><![CDATA[taxonomy]]></category>
            <category><![CDATA[category-tree]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Jean-Baptiste Sébrier]]></dc:creator>
            <pubDate>Tue, 27 Jun 2017 17:20:48 GMT</pubDate>
            <atom:updated>2017-07-06T13:25:44.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9_ZBFP4b-MVW_Qf9FEAOjg.jpeg" /></figure><p>Having discussed with a wide range of retailers as well as a <strong>lot</strong> of their suppliers, we have discovered that taxonomy is a very diverse concept: while some companies have thousands of sub-sub-sub-sub-categories and gazillions of attributes, others simply don’t have anything clearly stated on how their products should be organized, classified or described.</p><p>But what exactly is taxonomy when it comes to retail? To us, it groups the three tools that help categorize and break down the characteristics of a product:</p><p>1. the <strong><em>category tree</em></strong> (how can I group my products by nature?)</p><p>2. the <strong><em>attribute list</em></strong> (what additional information on my product can I give?)</p><p>3. the <strong><em>attribute value list</em></strong> (what are the most common values for a given attribute?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*yL-TfLtJv4LGWf6o9vq9nA.jpeg" /></figure><p>Through our discussions with 20 retailers and more than 80 of their suppliers, we have found out that about</p><ul><li><strong>23%</strong> do not have a fixed category tree</li><li><strong>49%</strong> do not manage a proper set of attributes for their products</li><li><strong>68%</strong> do not use a list of values.</li></ul><p>Our vision has always been to help standardise product information and to foster more efficient information exchange between e-commerce parties. That’s why we have from the get-go decided that our taxonomy should be open-sourced in order to allow anyone to access an extensive example of category tree giving them a large selection of categories to pick into and a large attribute list to describe products as accurately as possible. This is meant to save designing time and improve communication with other companies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*gV-n9hChh-wtU2n2QHs3mw.jpeg" /><figcaption>I like my taxonomies like I like my coffee [insert joke here]</figcaption></figure><p>Please note that most of the retailers will have dual category trees, one for their back/middle office solution and one for their website. There are a few differences. In the back office category tree a given product will only be in one category while on the website a product might be in several categories, to enhance its visibility. Also the website categories might be frequently changed based on performance monitoring and/or strategic decisions, while the back-office category tree should be more rigid and less often changed, and hence should be designed as robust and comprehensive as possible from the start. The website will always be a partial reflection of the organisation of the core category tree.</p><p>Of course at Scalia we don’t claim to hold the absolute truth in terms of how a category tree should be organized or what attributes the customer would like to have. The number, names and accuracy of the categories and attributes should match the size, organization and maturity of the company. What we offer is what we think a right amount of branch levels and a tentatively comprehensive coverage of the categories companies from the lifestyle retail industry would need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*epzor5Kxk832vUSZiYQddw.jpeg" /><figcaption>What’s for dinner?</figcaption></figure><p>We do however strongly believe in the benefits of a well-designed and well-maintained taxonomy. So maybe the question should not be why we open sourced our taxonomy, but why you would you need a robust, comprehensive taxonomy. Here are just a few of the perks:</p><p><strong><em>Better Onsite classification and search</em></strong>: if you manage a e-commerce website, you’ll be aware that product classification and search bar efficiency are key to your customers’ experience, and to your conversion rate. A visitor will always feel more confident having to navigate through a neatly arranged set of categories, rather than having to dig into a mess of badly classified products or vague and too vast categories. Don’t forget that it also helps internal and external search engines scan through the layout of your site and get it indexed properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*N57Dlu1TeYP1W4TNtPpzAw.png" /></figure><p><strong><em>Better product page: </em></strong>the category tree may be the backbone tool helping a customer to get to your product, but the attribute list will definitely make them buy (or not) your product. And whether it’s the power of that set of speakers or the length of the cord of that rice cooker, at some point, there is someone out there who is going to ask. It’s always better to have the answers ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*3NOOB--gaqSk442FsuBThg.png" /></figure><p><strong><em>Easier transfers: </em></strong>If you are a manufacturer or a supplier, providing the right classification information and a list of characteristics as extensive as possible to your retailers also simply makes sense in order to ease the customer’s journey to your products. You might not have the exact same category tree with your retailers, or the same attribute names but if you give them a clear and organized set of categories and description of your products, you’ll save them time and ensure your products are given the exposure they deserve.</p><p><strong><em>Stronger reporting:</em> </strong>For any company, identifying the over or under performing divisions is a vital necessity. When you’re a retailer, it all starts with a proper product classification, doesn’t it? The more accurate it is and the more efficient, decision-supporting and value-creating your reporting will be. And trust us, you’ll save time. A lot.</p><p>The taxonomy we offer is ready for use for any player in the lifestyle retail industry. It can also be seen as a starting point or a best practice example for anyone planning to design their own category tree, or willing to enrich its product listings. And if you’re a Scalia customer you can build your tree on the platform and enjoy intuitive-search options, exclusive designing tools and of course enjoy lightning-fast data transfers with suppliers and retailers.</p><p>Because our goal at Scalia is to make sure data collaboration between suppliers and retailers can be faster, easier and smarter, we want everyone to have access to the right assets from the start. It’ll just make everybody’s job easier.</p><p>Oh and by the way you can download our full taxonomy set <a href="https://drive.google.com/open?id=0B-l4QYv5_cVfRnRPQkpULXdUY2s">right here</a>.</p><p><a href="http://www.getscalia.com/"><em>Scalia</em></a><em> is a SaaS platform which helps lifestyle and fashion brands share their product data with retailers and other business partners. Thanks to machine learning algorithms, we consolidate, enrich, standardise and synchronise product data so that anyone can access it in the format they want, offering flexibility, control and consistency to the whole ecosystem.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67e0cdf36d7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>