MMY Data Import/Export

Learn how to export and import data to the Make/Model/Year add-on.

Olga Tereshina avatar
Written by Olga Tereshina
Updated over a week ago

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 fitment info.

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

MMY Data Export

The add-on Make/Model/Year adds a new field to the main product export file (products.csv) - fitmentType; this field is where information about a product's fitment type is stored. This add-on also introduces two additional data types for export/import:

  • Vehicles - This type of data includes information about the store's MMY levels and their detailed information. When exported from X-Cart, this type of data is saved to a CSV, Excel, or OpenDocument file with a name beginning with mmy; for example, mmy-2024-01-18.csv.

  • Product fitments - This type of data includes information about all MMY levels available in the store and the products assigned to them. When exported from X-Cart, this type of data is saved to a CSV, Excel, or OpenDocument file with a name beginning with fitmentvalues (X-Cart 5.5.x) or products-mmy (X-Cart 5.4.x) file; for example, fitmentvalues-2024-01-18.ods or products-mmy-2024-01-18.csv.

To export MMY data from your X-Cart store, go to the data export page in your X-Cart store's Admin area and select the data types you require:

  • X-Cart 5.5.x: Import & Export page (Catalog > Import & Export, CSV Export tab)

  • X-Cart 5.4.x: Export To CSV / Spreadsheets page (Catalog > Export)

Information about the basic principles for data export is available in the section How to Export Data from X-Cart.

MMY Data Import

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

Importing Filter Levels Data

A store admin can use import to create and update the vehicles' filter structure and import filter level-related data, like logos, banners, etc. The name of the import file for this purpose must begin with mmy.

Examples of correct file names:

  • mmy.csv;

  • mmy-01-02-03.csv;

  • mmy-from-my-provider.csv;

  • mmy-2023-07-25-sorted-to-import.csv

The supported file formats are CSV, Excel, OpenDocument, and ZIP.


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


The import process 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

make*

Make name

String

model*

Model name

String

year*

Model year

String

engine*

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

A store admin can assign products to filter combinations. The name of the import file for this purpose must begin with fitmentvalues (X-Cart 5.5.x) or products-mmy (X-Cart 5.4.x:)

Examples of correct file names:

  • X-Cart 5.5.x:

    fitmentvalues.csv;

    fitmentvalues-01-02-03.csv;

    fitmentvalues-from-my-provider.csv;

    fitmentvalues-2024-01-25-updated.csv

  • X-Cart 5.4.x:

    products-mmy.csv;

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

    products-mmy-from-my-provider.csv

The supported file formats are CSV, Excel, OpenDocument, and ZIP.


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


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

A sample file may look as follows:

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

Importing Fitment Info

Using the X-Cart store's import facilities, a store admin can update products' fitment type via the products.csv file that is usually used for importing general info about a product. In this file, the field that is responsible for fitment information is fitmentType.

The fitmentType field has three possible values: regular, universal, or specific; this corresponds to the fitment types described in the section Products Fitment Management. The screenshot below demonstrates how it may appear in the products.csv file.

If the fitmentType field is left blank when importing a new product, the product's fitment type is set to regular. If that happens when updating an existing product, the previously assigned fitment type remains unchanged.

Related pages:

Did this answer your question?