The content of this Article has been Archived. For information on formatting your Vehicle Fitment Data, please refer to the examples provided within our Product Finders Help Article.
In order to properly handle Make/Model/Year data, Searchspring highly recommends formatting this data as a hierarchy in a single field.
Examples:
Ford/Mustang/1967 Chevy/Malibu/2006 Chrysler/300/2013
If a product has multiple Make/Model/Year options, you should include all of these options in one field separated by pipes. An example would be a product that is for both the Chevrolet Traverse 2009-2013 and the GMC Acadia 2009-2013, the data would look like the following:
Chevrolet/Traverse/2013|Chevrolet/Traverse/2012|Chevrolet/Traverse/2011|Chevrolet/Traverse/2010|Chevrolet/Traverse/2009|GMC/Acadia/2013|GMC/Acadia/2012|GMC/Acadia/2011|GMC/Acadia/2010|GMC/Acadia/2009
Comments
4 comments
This can make for some monster data cells if you have a product that fits a lot of vehicles. Is there a way to come at this from the vehicle side rather than the product side? In other words, sturcture the data upload to show only the part(s) that will fit the 2013 Chevy Traverse? Or would this be even more complicated?
Jim,
The issue is that SearchSpring relies on a product data set. So the key part of the data feed needs to be the product and then you tell us about the attributes for that product. We've had customers with thousands of Make Model Year combinations for a product and it works fine.
What do you do if the content should contain a slash? An example would be a 1978 GMC C/K Pickup 1500. Can you escape the slashes?
Susan,
Thank you for the question.
No, escaping the slashes won't work in your example, but technically, you can use other delimiters besides "/" and "|" - just as long as the delimiter isn't found within the content, as you pointed out.
So, looking at the above examples, the following would also be valid:
Article is closed for comments.