Your online store allows exporting and importing all vehicle-related data supported by the Make/Model/Year add-on. For example, you can use import to upload new or update existing products in your store, create filter levels, populate them with data, and update fitments info.

To understand the data import file formats, we recommend first exporting data samples and checking the information they contain.

MMY Data Export

You can export data on the Export page of the store's Admin area (Catalog > Export). Read about basic data export principles here.

The Make/Model/Year add-on adds product fitment type to the main product export file (products.csv) and also introduces two new formats of data export/import:

  • Product Fitment (products-mmy.csv) - the file contains info about all MMY levels available in the store and the products assigned to them.

  • Vehicles (mmy.csv) - the file contains info about the MMY levels and their detailed information.

MMY Data Import

The Make/Model/Year add-on allows a store admin to configure filtering levels, make product assignments, and update product fitment info via import facilities.

Importing Filter Levels Data

The mmy.csv file allows a store admin to create and update the vehicles' filter structure and import the filter level-related data, like logos, banners, etc. The import file can have the name mmy-xxxxxx.csv, where the part "-xxxxxx" can be anything you want or even be omitted.

Examples of correct file names:

  • mmy.csv;

  • mmy-01-02-03.csv;

  • mmy-from-my-provider.csv


The default level names are Make, Model, Year, and Engine, if you have not changed them during the Make/Model/Year add-on setup.


The import procedure will automatically add the level names and their respective values to the Catalog -> Manage Vehicles section of your store's Admin area.

A sample mmy.csv file may look as follows:

The table below describes the fields included in the file.

CSV file field name

What this field describes

Value type

make*

A name of the make.

String

model*

A name of the model.

String

year*

The model year

String

engine*

The engine type

String

<level>**_logo

For any logo that needs to be imported, you must specify the image location. You can use one of the following ways:

  • Image URL (can be local to the X-Cart server);

  • Path to the image on the server relative to the <XCART-DIRECTORY> folder; for example, images/level[X]logo/auto/image1.png.

Note that if you require to store images for import inside the /images folder of your X-Cart store installation, they must be placed inside the folder /images/level[X]logo, where [X] if the number or the corresponding level.

X-Cart will not be able to import images stored in the /images folder outside the /images/level[X]logo/auto subfolder. It will be able, however, to import images stored in other locations within your <XCART-DIRECTORY> folder, outside of the /images folder.

Correct:

  • images/level1logo/auto/Ford.png

  • images/level2logo/Ford-Logo-History-11-scaled.jpg

Incorrect:

  • images/test.jpg

  • images/test/test.jpg

Also, note that the images import takes considerably less time if the images to be imported are stored locally on the server. It does not matter if the image path is specified as a URL or as a file path — X-Cart will try to detect if the URL is local to the server. So, if you need to import a considerable number of images stored elsewhere, you can speed up the process quite a bit simply by saving those images locally on the server inside the <XCART-DIRECTORY>/images/level[X]logo/auto folder.


<level>**_banners

For any banner that needs to be imported, you must specify the image location. You can use one of the following ways:

  • Image URL (can be local to the X-Cart server);

  • Path to the image on the server relative to the <XCART-DIRECTORY> folder; for example, images/level[X]/auto/image1.png.

Import rules are the same as specified above for the <level>_logo field.

Additionally, you can specify more than one image for import by separating the image paths with the '&&' symbols.

e.g., images/level2/a3fd2222348fcda4b28926f1d1696809.jpg&&images/level2/407b9df62737e5836b535640f1613044.jpg

String,
Multiple

<level>**_cleanURL

Level page SEO-friendly URL.

e.g., ford

Clean URLs are imported according to the following rules:

  1. If the cleanURL field doesn't exist in a .csv file, the product Clean URL field stays unchanged.

  2. If the cleanURL field value is defined in a CSV file and this field is empty for a product at the moment of import, the respective product property is created the product Clean URL gaining the value of the respective field from the CSV file.

  3. If the cleanURL field value is defined in a CSV file and this field is NOT empty (exists) for a product at the moment of import, the respective product Clean URL value is substituted with the one from the CSV file if the field value doesn't conflict with any of the existing Clean URLs values. If the conflict exists, the cleanURL field value is automatically modified by adding -1 to the end of the field value.

String

<level>**_show_on_frontpage

Whether the level info should display in the promo block on the store's home page.

Yes/No

<level>**_enabled

Whether the level is enabled.

Yes/No

* Required field (the number of required fields and their names will depend on the Make/Model/Year add-on configuration settings).

** Use the respective level name instead of <level>. The mmy.csv file can include as many level-related fields as you configured for the add-on.

Use the mmy.csv file to import new and update existing filter combinations in your online store. You can use import as an alternative to the regular filter configuration routine.

Importing Product Assignments

Using the products-mmy.csv file, a store admin can assign products to the current filter combinations. The import file can have the name products-mmy-xxxxxx.csv, where the part "-xxxxxx" can be anything you want or even be omitted.

Examples of correct file names:

  • products-mmy.csv;

  • products-mmy-01-02-03.csv;

  • products-mmy-from-my-provider.csv


The default filter level names are Make, Model, Year, and Engine, if you have not changed them during the Make/Model/Year add-on setup.


If you assign an SKU to a not existing filter combination, the import procedure will automatically create respective combinations and ad new values in the Catalog -> Manage Vehicles section of your store's Admin area.

A sample products-mmy.csv file may look as follows:

If a product matches several filters, you need to assign this SKU to each new filter combination in a separate line.

You can also use "ALL" as the field value if an SKU matches all existing model years or engines of a particular Make.

e.g., BBK007BLK-2/make/model/year : FORD/Fiesta(MK7)/ALL

Importing Fitment Info

Using import facilities, a store admin can update product fitment type via the products.csv file usually used for importing general info about a product. The field responsible for the fitments info there is fitmentType.

The fitmentType field has three possible values - regular, universal, or specific, corresponding with the fitment types described here. Below is how it may look like in the products.csv file.

If you left the fitmentType field empty when importing a new product, it gains the regular fitment type by default. If you do this when updating an existing product via import, the previously assigned fitment type will remain unchanged.

Related pages:

Did this answer your question?