EXPERTISE IN MARKETPLACE SOFTWARE
Experience Is Key to eMarket Success
Handling Different Data Formats
The other thing that's often a default assumption is that the vendors are all going to have similar data. Once you've done several of these projects, you realize that's simply not true. This can be a really common pitfall for new marketplaces, as they’re assessing landscape and looking at the cost of getting up to speed, etc., a lot of the meta information, images, category data tagging and other forms of annotating the schema on product—it's not consistent at all between the different vendors.
Logistically, this can be a huge challenge if not handled properly, because whenever you're leveraging a marketplace, you want to have this very consistent presentation throughout the data on the marketplace. Therefore, if somebody goes to look for a certain category and subcategory in a sub-subcategory, or do a search, look at a certain filter, etc.—just think about all of the different attributes that products have based on different types of products. Well, those have to be normalized and standardized across the different inputs on the vendor dashboard.
So again, this is one of those scenarios where it's important that we are able to work with the vendors and deal with these data feeds and technically do some form of data transformation and mapping, so that whenever the data is in a specific format from this other vendor, we have the mechanism and the business workflow capability to dynamically map that into a normalized and standardized set of attributes and categories and subcategories.
These are all real problems that happen at scale, but they can also happen really quickly with just a few different vendors, a few different distributors, even from whom we’re bringing in data.