All Posts

    The nice thing about standards is that there are so many to choose from. They're valuable and are used throughout the web development process. Certainly the web is comprised entirely of standards, from HTTP to HTML, web services, transaction processes, linked data processes and new methods of sharing information across shopping channels like Milo. 

    Standards allow systems to communicate and help to save time and effort by not reinventing the wheel when it comes to sharing various types of data. If someone has done this before, can’t you borrow it? Don’t industries have standards for interoperability? If I want to share information amongst manufacturers in the supply chain of the aerospace industry, there are agreed upon specifications for transmitting data as well as unstructured content such as technical manuals, project-related documentation and proposals.

    Companies that use channel sales can also syndicate content from their websites through partner sites in order to support end customers with help materials, manuals, troubleshooting guides and other content.

    In the e-commerce realm, there are standards for transacting on specific websites — iTunes has a set of metadata standards that sellers must comply with in order for placement in the iTunes catalog. The rule of thumb here is that standards are very useful when transmitting and sharing information across companies, partners and suppliers.

    Complying with standards ensures interoperability and is a source of efficiency. Syndicating content to a partner speeds time to market. Having consistent standards from a supplier makes it easier and cheaper to add products to a retailer's offering. Many new classes of functionality, such as integration with social media sites like Facebook and Twitter, depend on shared web standards in order to transmit and receive information about user preferences and social commerce functions. (This is still in its nascent stage, but not something to be ignored in the future.)

    What about standards for how information is displayed on a website? Does it make sense that display taxonomies are completely standard since there are only so many ways to show categories like “Electronics” or “Home Furnishings”? Well, perhaps not. In fact, there are standard taxonomies for products such as those in Google Commerce Search. However, in that taxonomy, diaper bags appear under "Luggage." If your site specialized in products for parents of infants and toddlers, it's unlikely you'd have a “Luggage” category. At Babies"R"Us, luggage fits under “Gear” along with “Strollers” and “Car Seats.”

    Site taxonomy is more nuanced and complex than many people realize. Consider a physical store layout. The character of the store — i.e., its look and feel — is in part determined by signage and furnishings, but also by physical product layout. A plan-o-gram is used to study, optimize, standardize and formalize the physical layout of products.

    A site taxonomy can be considered part of a virtual plan-o-gram. No two plan-o-grams will be identical. A great deal of effort goes into differentiating offerings in the physical retail world. Competitive advantage is gained through the differentiation of offerings, either through selection, quality, service or price or more of the subjective experience such as the store's look, layout, feel, convenience of checkout, cleanliness, sounds, smells, even textures and types of fixtures. Friendliness, expertise, capability of staff, overall store ambience, and ease and completeness of information access are also important differentiators.

    Since the online experience is completely information driven, your information must be differentiated. That's where competitive advantage is gained. Back to the Google Commerce example. One bit of data that's captured is “Feature.” Feature is a challenging attribute since there are many ways to define features.

    What's the difference between a feature and a specification, for example? What if there are multiple feature sets that need to be considered during faceted search? There are likely ways to deal with this in Google Commerce, however, the point is that there may be more attributes that are important to consumers than those outlined in the Google Commerce standard specification. 

    The bottom line is that terminology, taxonomy, attributes and data are the sources of efficiency and enable external communication. If your goal is competitive advantage, then organizing principles like taxonomies, attributes and metadata must be leveraged to differentiate your site from its competition.


    This Article was published on on June 29, 2011.

    Recent Posts

    [Earley AI Podcast] Episode 41: Ian Hook

    Ian Hook on Advancing Operational Excellence with AI and Knowledge Management - The Earley AI Podcast with Seth Earley - Episode #041 Guest: Ian Hook

    [Earley AI Podcast] Episode 40: Marc Pickren

    Search Optimization, Competitive Advantage, and Balancing Privacy in an AI-Powered Future - Marc Pickren - The Earley AI Podcast with Seth Earley - Episode #040 Guest: Marc Pickren

    [RECORDED] Product Data Mastery - Reducing Returns to Increase Margin Through Better Product Data

    Improving product data quality will inevitably increase your sales. However, there are other benefits (beyond improved revenue) from investing in product data to sustain your margins while lowering costs. One poorly understood benefit of having complete, accurate, consistent product data is the reduction in costs of product returns. Managing logistics and resources needed to process returns, as well as the reduction in margins based on the costs of re-packaging or disposing of returned products, are getting more attention and analysis than in previous years. This is a B2C and a B2B issue, and keeping more of your already-sold product in your customer’s hands will lower costs and increase margins at a fraction of the cost of building new market share. This webinar will discuss how EIS can assist in all aspects of product data including increasing revenue and reducing the costs of returns. We will discuss how to frame the data problems and solutions tied to product returns, and ways to implement scalable and durable changes to improve margins and increase revenue.