Preparation of Excel and XML files for SKU cards import

If you already have a SKU cards list, you can import it from a file in the Goods and Services section.
Currently supported is the format of Excel 2007 and XML.

Preparation of an Excel 2007 file (.xlsx)

To import your SKU cards list, you must prepare your file for import. This must be a spreadsheet with column headings in the first line. The Column headings must contain special “tags”, allowing the Store&Cash system to identify data pertaining to your goods.

NB: The file must be named using Roman characters (letters and digits) only, no spaces, brackets or other special characters. It often happens that when a file is saved, its name looks like this “file (1).xlsx”. In this case you need to remove “ (1)” from its name.

  • {internalId} Generally speaking, never write anything in this column. It is needed for synchronization.
  • {offerId} This your in-house SKU number. For example, the SKU number on the database of your E-shop. Store&Cash will use it to compare goods on re-import and synchronization via API. If the field is left blank, and you perform a re-import of an Excel 2007 or XML file with the same goods -the goods will be duplicated. Hint: You can use SKU number or barcode from a supplier's price list to update your SKU cards list using a price list.
    If you have no such number, leave the fields blank, but make sure that when you re-import your SKU cards list, the files have no goods that have already been imported in order to avoid duplicating goods and confusion in your records.
  • {barcode} Barcode in the EAN13 format
  • {groups} Groups of sizes and categories. If in doubt as to what to write there, leave them blank. You have no way of knowing the size and category groups until you export your SKU cards list from Store&Cash. What purpose does it serve?
    Example: You have imported 100 SKU cards of garments. Now you need to assign categories and size groups to all items. You hate accessing 100 items and entering one and the same value for all of them. So you only edit unique items, export your SKU cards list and copy the values to the Excel file from the unique items — to the others for which the values of categories and sizes must be the same. The first value is the category, the second the size. This is what it is supposed to look like: 10; 17
    We are aware that this is not very intuitive, but if you need to do this and are not sure how to go about it, write us at support, and we will explain and help you.
  • {sku} SKU number
  • {name} SKU name of goods or service
  • {vendor} Brand, [trade] mark or manufacturer
  • {price_p} Purchase price (or your cost if you make goods in-house)
  • {price} Retail price
  • {price2}... {price5} 4 more sale prices
  • {type}-Type — goods or services. Goods = 1, Services = 2.
  • {inDel} Deletion flag. Deleted = 1, Active =0.
  • {picture} Link to an image of goods on the Internet

It should look something like this:

Once your file is prepared like this, you can proceed to SKU cards import.

Download the sample file link: export_products.xlsx

You can export your SKU cards from the service, edit, expand and re-import it the same way.

NB: The import operation is irreversible!
If you are unsure whether your file is correct, contact our technical support:

Please leave this field empty.




Preparation of an XML file (*.xml)

Important! Preparation of XML format is a job for power users or programmers.

Document title (XML header)

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE xml_catalog SYSTEM «shops.dtd»>

Currently only utf-8

Standard XML header with a link to the file description (DTD) format. The title should begin with the first row with a null character.

Standard XML header with a link to the format description file (DTD [Document Type Definition]). The XML header must begin in the first line, at zero character.
The second line of the XML document header contains a link to the data format description file (DTD). All you need to specify here is the name of the file shops.dtd. You need not specify the path to the because it is located on the side of the Adensya market.
Element xml_catalog
Any XML document can only contain one root element. The XML format uses xml_catalog as the root element. The date attribute of the xml_catalog element must match the date and time of generation of the XML file on the shop's end. The date must be in the YYYY-MM-DD HH:mm format.
required element!!

Element <categories>...</categories>

<categories></categories>
<category id="1">Clothing</category>
<category id="2">Shoes</category>
<category id="3" parentid="1">Underwear</category>
<category id="4" parentid="1">t-shirts</category>
<category id="5" parentid="2">boots</category>
<category id="6">gifts</category>
<category id="7">Bags</category>

The element <categories > ... </categories> contains a list of the shop's categories. Each category is described with a separate element <category>...</category>. The description of a category must include its identifier (id parameter) for all categories and an identifier of the higher-level category for subcategories. The category identifier must be a unique positive integer. None of the categories may have its id parameter equal to “0”. If no parentId element is specified, then the category is deemed to be a root category.  The id parameter must be an intrinsic attribute of category in your database. Otherwise all categories and goods therein will be mixed up, and duplicate categories will be created.

Element <category>...</category>

id — unique intrinsic identifier of your goods category. This parameter must match the category number in your database and must never change for the category.

parentId — identifier of the preceding goods category in the hierarchy.

Element <offers>...</offers>

<offers></offers>
<offer>...</offer>
...

In the offers lists of product offerings of stores. Each commodity offer describes an individual element of the offer.

Example offer element:

<offer id="12341" type="vendor.model"></offer>
<name>HP Deskjet D2663 Printer</name>
<price>700</price>
<categoryId>6</categoryId>
<picture>http://best.seller.ru/img/device12345.jpg</picture>
<vendor>NP</vendor>
<article>223345567HP</article>

All these elements are mandatory.

ID element you need to enter the actual ID of your item on the database of your shop since in the course of import the robot links the item to your offer of goods for subsequent update of goods.

<price>...</price>
The price at which you will normally sell your goods. For example, the retail price.

<price_p>...</price_p>
Optional tag. The book price at which you normally source goods or the cost of the manufacture thereof.

<categoryId>...</categoryId>
Goods category identifier (integer up to 18 digits). Goods offering can belong to one category only

<picture>...</picture>
Link to respective goods offering image.

<vendor>...</vendor>
Brand, [trade] mark or manufacturer

<sku>...</sku>
SKU number

<name>...</name>
Goods offering name

Other tags are not supported and will be ignored.

NB: The import operation is irreversible!

If you are unsure whether your file is correct, contact our technical support:

Please leave this field empty.