With SEMA Data integration, your X-Cart store will be able to create and update products in your store's catalog by importing data from SEMA Data. The imported data will be used to populate the product fields Product name, SKU, UPC, Images, Category, Full Description, Price, Availability, Weight, and Brand. For products with attributes, the integration will be able to import all the existing attributes.
Since data imports from SEMA are fully compatible with the Make/Model/Year functions of X-Cart Automotive, the integration will also:
import special product attributes that are used to specify the product's fitment;
import each product's fitment data;
import the complete Make/Model/Year/Submodel hierarchy.
The latter means that if your X-Cart store does not have an MMY configuration at the time of catalog data import from SEMA Data, this configuration will be created based on the data your store will receive from SEMA. If, however, your store is already using some kind of MMY configuration, the integration will do its best to reconcile the data received from SEMA with the configuration that already exists in your store:
No existing data will be deleted as a result of import, and new data will be tied to the existing MMY configuration hierarchy, where possible.
The order of Make/Model/Year/Submodel configuration levels will remain the way it has been configured in your store.
Important: For lossless import of product fitment information from SEMA Data, your X-Cart store needs to use the Make/Model/Year/Submodel MMY configuration. You can check and adjust your store's MMY configuration on the Vehicles & Fitments Settings page in the Admin backend (Catalog > Vehicles & Fitments, Settings tab). You are free to arrange the levels in any order you prefer, just make sure the names are Make, Model, Year and Submodel. Please specifically note that the name Engine, which, depending on the version of X-Cart software you are using, may be used in your X-Cart store for one of the levels by default, will not function as a substitute for Submodel; you will have to manually replace the name Engine with Submodel to make it work.
Related pages: