Not so New
I am not sure how you want this to look in Magento, do you have a custom attribute for fitment data or are you creating different sku’s for the different products?
Every expert was once a beginner
Not so New
As you can see in this image there are 15 lines that have the sku 1061 how ever each has a different fitment this is because the product 1061 will fit all of those different vehicles.
We’ve been looking at a similar project for our automotive website (BMW). Here are a couple of extension that may assist in offering a solution.
Currently we have categories and subcategories for each model series. If a part fits two or more vehicles we list the item in multiple categories.
Hope this offers some help and I’d be interested to hear what solution you arrive at.
Unfortunately, you are dealing with non ACES (Auto Care Association Catalog Enhanced Standard) data here, and that is a bit of a problem. If a manufacturer provides you with a table like that, you will end up with so many configurations that are similar but not the same. This will make for a mess trying to keep some sense for a buyer looking for products and dealing with yearly updates. While dealing with ACES data is a huge undertaking, in the long run it will work much better.
I am going to take a semi-educated guess here and say those are Smittybilt products? If so, I am sure they have ACES data. Usually to get ACES data, the manufacturer will have to approve you to receive the data from either their dealer portal, DCI, SEMA Data Co-Op, or whatever other data provider they may use.
PS. The above is valid for North America, if you are outside North America, there are some other services that do this, but I am not familiar with them.
The following users say thank you to Richard Meldner for this useful post:Matthew Ogborne
One more thought, I think people are getting over the standard Year Make Model design and layered navigation system is going to be better and easier to maintain.
But the build in one by Magento is not good enough for this task, you will need something like this:
There are others, but I think that one gives you a lot of options on how to save the fitment data for each part.
Steve might be able to shed a little more light on the one he using, but one of the issues I found with the YMM ones I looked at is that they use a vehicle database. There will be times when that will not match what a product manufacturer provides as the manufacturer of the product may have updates to new vehicles already in the ACES database that are not yet included in the YMM provider’s database. very typical between August and November every year. By using layered navigation, the data comes from your listings, so you are free to update as soon as new fitments are added by the product manufacturer.
Not so New
Cool, that is what you want to use :) I know it is pain right now, but you will find updates a lot easier later.
Not so New
I’ve returned to this thread several times in my search for ACES/PIES integration into Magento. I have three manufacturers supplying the data already, but I have no clue how to use it, nor do I understand quite all of it (the data itself). Would love to find out more about your process, the structure, and how it worked out for you.
As much as ACES/PIES tries to be a standard, manufacturers can provide some of the extended data (specifications) in different ways. So that can be a challenge no matter what.
This type of data needs to be driven by some sort of navigational method. I have seen implementations that use year, make, model, maybe even submodel as a category. After that it gets a bit dicey…
Year, Make, Model, Submodel or Engine, you could pull from the ACES data and assign products to it using categories and use a layered navigation tool to build the front end for consumers. If you are wanting to go further than this, such as importing the data into a database or providing more vehicle details, you will likely need a custom programmer to write you an extension specific for your needs.
Year, Make, Model, Submodel and Engine are definite musts, I know this just from a 25 year career in 12 volt and accessories installation. As far as mechanical, I’m not sure what else would be needed.
I do want to add these to the database, and of course find a navigational tool for Magento 2 to use the data. I offer both parts and accessories, meaning that some products will need the ACES/PIES data and some will not, and I’m leaning towards attribute sets and possibly custom product types to hold the data. Alas, I’ve been working on structure just for non-repair parts for quite some time, trying to automate import and categorization with magmi with varying degrees of success, and I don’t want to repeat the same mistakes (or start over) with the repair parts. And yes, I do have magmi working with Magento 2.2 CE, it’s wonderful compared to the stock import.
Why Should You Join UnderstandingE?
- Access to over 500 step-by-step video tutorials
- +20 video courses available
- Magento, M2E Pro, Magmi, eBay, Amazon & Design all covered
- Everything is in 100% Plain English
- Learn how to build your own multi-channel software for eBay & Amazon
- Access to the community forums, meet fellow business owners like yourself
Join Now with 2 Clicks
Join now for less that £1 per day you can gain access to over 400 step-by-step video tutorials & learn how to build your very own multi-channel software.
Most Users Ever Online: 1012
Currently Browsing this Page:
Jim @ Moogento: 688
Steve Froggatt: 514
Badeth - UE: 513
Paul Cartwright: 414
Administrators: Matthew Ogborne: 4565, Dave Furness: 4606