Skip to main content
All CollectionsProductsFilling the catalog with products
Preparing files for importing products
Preparing files for importing products

Basic principles of forming a file for import, creating variants in the file, an example of an Excel file for import

Updated today

If you are preparing an Excel file to import new products into the catalog by yourself, please pay attention to our recommendations.

Rules for creating an import file

Pay attention to the basic principles of forming a file with products, which will help you avoid mistakes during import:

  1. One product — one row;

  2. Each product must have a unique SKU number;

  3. For each new product, all mandatory data must be specified.

Required data for new products

To successfully import a new product, the file must contain the following required fields:

  • SKU — a unique product identifier;

  • Title — product name;

  • Category — category name.

Table with required data — Cartum

How to fill in the Category column correctly

Categories must be created on the website before importing.

  • The name of the category in the file should be exactly the same as the name on the website.

  • If the third-level category has a unique name, it is enough to specify only that name.

  • If the name of the subcategory is repeated in other categories, you must specify the name of the parent category in the format Phones/Mobile phones with a separator / (slash).

  • The name of the category should not contain the symbol /.

Optional but recommended fields

  1. Price — the current price of the product;

  2. Quantity — the quantity of goods in stock (if stock accounting is enabled);

  3. Availability — [In stock, Out of stock] status of the product availability (if stock accounting is not enabled);

  4. Show on storefront — [yes, no] display or hide the product for customers on the site; if the field is not filled in, the product will be hidden;

  5. Image — links to product photos.

Creating and merging variants in a file

If a product has variants (by color, size, or other attribute), each variant must be described as a separate product:

  1. Each variant has a unique SKU;

  2. For all variants of one product, a common parent SKU must be specified, which is the SKU of one of the variant — the main one;

  3. The main variant is indicated first in the general table.

Warning: each possible combination of variant attributes is a separate product. For example, you have a T-shirt that is available in four colors and five sizes. In the file, it should be organized like this:​

Product with variants in the file — Cartum

A product with variants created with this table on the website:

A product with variants on the website — Cartum

The Title and Variant title fields

In the product properties, there are two similar fields — Title and Variant title. Both of these fields can be imported from Excel file.

  • Title is a general field, it can be filled in once and will be common to all product variants.

If only the general name is filled in for the products, the variant name in the shopping cart will be generated automatically as Title + variant attributes (for example, color and size).

  • Variant title — a unique name for each variant that will be displayed on the site and in the cart instead of the automatically generated one.

You can use different properties for each product: where it is convenient to specify only the Title, and where necessary, specify Variant title.

Multiple languages

If your site has several language versions, all text values need to be translated. For example, instead of one column Title, two columns Title (EN) and Title (RO) are created.

By analogy, you need to prepare separate columns for description and attributes of the string type.

Importing value translations for attributes of the Selection from list type

You can set translations for the values of attributes of the Selection from list type either manually when editing the directory itself or by importing them.

Warning: bulk import of translations does not work for Multiselect option.

When importing each language version, a separate column with the corresponding language value should be generated.

Importing value translations for parameters — Cartum

After importing, the attribute values in all languages will be automatically filled in the attributes values list.

Warning: each combination of values in different languages will be defined as a new value when imported (for example, if you specify the pairs oil — oil and oil — grease, then two oil records with different translations will be created in the attributes values list).

Importing photos

You can use an import file to add photos to a product. To do this, the import table must contain the Image and/or Gallery columns:

  1. These columns should contain the photos URLs.

  2. The link should always begin with the protocol http:// or https://.

  3. If you need to add several photos, add their URLs in one cell separated by ; (semicolon).


Did this answer your question?