Thanks to a self-service configurable system by the customer, bindCommerce can import products starting from text files, even very different ones; let's see the fundamental characteristics of these files.

File format

Both text files and spreadsheets, such as Excel and OpenOffice, are accepted.

If a text file is imported, it can be plain text with separator-delimited fields (columns), or fixed-width text; optionally a text qualifier can also be used. The first line can contain the names of the fields (but not necessarily). If it contains them, they must all be filled in (any columns without a corresponding field name would give rise to import errors). The file encoding can be ASCII or UTF-8.

XML and JSON files are also accepted.

With regard to the file format we are not using restrictive indications as the bindCommerce import file functionality is very parametric and allows you to manage situations that are also very different from each other.

Tools to manage text files

To be able to read (and possibly convert/edit) text files in an easy way, we recommend the use of an advanced text editor, such as Notepad ++ ( available for Windows platform, or jEdit ( available for Windows, Mac OS X and Linux, both open source and free

thumb file-testo-notepad

There are various ways to obtain such a file, for example starting from a spreadsheet such as Excel or OpenOffice Calc (the free opensource alternative downloadable from the site


From OpenOffice Calc it is possible to export in text format by following the menu File -> Save as, in File type choose CSV text (.csv) and the option "Change filter settings". Here we recommend choosing the UTF-8 character type (as it is compatible with practically all the alphabets used), a field separator rarely used in texts like the pipe (|) and for added security, also a text separator, like for example the quotation marks (").

export settings

The settings chosen here must then be set in the import file configuration to allow bindCommerce to correctly interpret the file.

Columns to consider

There are no limits on the names of the column headings, as during the configuration phase it will be possible to tell bindCommerce which names to look for in the file. So let's see which columns you need to include in the file so that complete product sheets can be generated, suitable for publication on Internet sites and marketplaces

SKU code

Each record must be identified by a unique code (often called SKU). This code will be the connecting key of all the platforms connected to bindCommerce.

Example:  EMOTIKO - BSS204


The use of a barcode (such as EAN, UPC, ISBN, etc.) is necessary for publication on some marketplaces, and in particular on Amazon.

Example: 8057288550132


Each product must be identified by a descriptive title, not too long (we recommend max 80 characters for compatibility with eBay). The title (possibly unique) should contain the most important keywords to facilitate online research.

Example: Stainless steel bracelet *Pearl of Nile* eMotikO


Product brand

Example: eMotikO


The product description should be as detailed as possible. It is possible to use HTML tags, but the use of formatting such as colors, font size, etc ... is not recommended.

Example: eMotikO stainless steel river pearls * Pearl of Nile * bracelet is manufactured using 316 L steel, the same used for surgical tools. In combination there are natural white river pearls. The size is adaptable to every wrist.


Categorizing products is necessary both for publication on your own eCommerce site and for publication on marketplaces. On these it is necessary to provide the same level of detail as the catalog used, and among these normally the most restrictive (detailed) is that of Amazon. The cataloging can be communicated through a single field, by concatenating the various levels, or through different fields (up to 3).

Example 1: Category = Jewels>>>Bracelets

Example 2: Categoria1 = Jewels - Category2 = Bracelets


The price can be VAT included, or not included, as it will be possible to detail what you are importing during the configuration phase. The VAT rate can be omitted if the file has a uniform rate (in this case it must be indicated in the configuration). The decimal separator can be a period or a comma. It is important not to use currency symbols and thousands separators.

Correct examples: 1.22 30.00 5300.00 5300.00 50

Incorrect examples: € 1.22 1.22 € 5,300.00

Stock availablity

Indicate the quantity in stock, to be updated with subsequent imports. For products that are always available, this column can be skipped and a fictitious value will be indicated in the configuration during the import phase.

Example: 29


Images must be communicated via absolute URL. If there are more than one, it is possible to indicate them in different columns (up to 8).


Characteristics of the images

The image formats allowed are all web ones: jpg, png and gif. The size must be relatively large (possibly at least 500 pixels on the shorter side), but without exaggerating (no more than 1600/2000 pixels).

If the images are not available online, it will be necessary to publish them, at least temporarily (to do this, a hosting space is needed, which can be the same deputy to host the web server node necessary for bindCommerce).

The resolution and the level of compression must provide a not excessive weight for each image; in this regard jpg is better, and the recommended resolution is 72 dpi.

In order to be imported on marketplaces, images must have some minimum quality requirements. Amazon for example has published a specific qualitative guide that we report below.


images amazon

Standard image

Each product published on Amazon must be accompanied by one or more images. Choose images that are sharp, immediate and easy to understand. Make sure they describe the product clearly, are detailed and present themselves well. The published product must be identical to the one you will send to the customer and the background of the photograph must be empty or in any case it must not distract. Inside, texts, logos and other images in the box are not allowed. Whenever possible, provide more than one image so that you can show the product from different angles and in more detail. In other words, it is only through images that you will have the chance to show your product to potential buyers, so quality is an important factor.

We reserve the right to reject images that do not meet the criteria illustrated.
It is your responsibility to ensure that you have the rights to publish the images you provide.

Main image

* The background of the main image must be pure white in order to blend with the background of the Amazon product pages, which have RGB values of 255, 255, 255.
* The main image must not be a drawing or illustration nor must it show accessories that are not included with the item or media that could be confused with the product itself. Likewise, it must not contain text that is not part of the product, logos, watermarks or other images in the box.
* The product must occupy at least 85% of the image area.

Alternative images

* The main image should be complemented by alternate images showing the product from different angles, its use and other details not highlighted in the main image. In the case of Media products, alternative images may show the back cover of the article, full pages or screenshots. You can add up to eight (8) images.
* The use of a white background is preferable but not mandatory. Alternative images must not include logos or watermarks, and media and accessories must be presented in a manner that does not confuse the customer's expectations.

Image size

The images must have a size equal to or greater than 1000 pixels in height or width in order to make it possible to use the zoom on the site (it has been proven that the zoom helps to stimulate sales). Images with the longest side measuring less than 500 pixels will be rejected by the system.

Titles and image formats

* Amazon accepts the following image file formats: JPEG (.jpg), TIFF (.tif), or GIF (.gif). The JPEG format is preferable as, having a smaller size, it can be processed and loaded faster.
* We suggest that you name the images with a title that contains the product SKU followed by the image type or variant code, p. ex. PRINC (for the main image), ALT01-ALT08 (for the alternate ones), which can include sample images (CAMP), used for products with multiple variations to show the sample of one color, fabric etc. Example: 8845013515.PRINC.jpg, 8845013515.ALT01.jpg, 8845013515.CAMP.jpg

Manage product variants (sizes and colors)

To import products with variants for which it is necessary to monitor the quantities in stock, the file to be imported must contain:

  • one row for the parent product
  • one row for each variant (child product), with reference to the parent product

The common characteristics (description, categories, images) must be inserted on the line of the parent product, while the specific ones (eg the size, bar code) on the child products. The following images show a concrete example.



If the row of the parent product is not present, bindCommerce offers the possibility to create it starting from the first of its children, using as code the one specified in the "parent" column (model code). In this case it is also possible to choose which attributes present on the child to copy to the father (eg YES material, NO size).

5 of 5 - 1 votes
Thank you for rating this article.


bindCommerce platform
Creating a Web Server node to publish images
Product attributes
Price lists and prices
Alternative descriptions
Payment and shipping methods
Filter setting on products
Filter setting on orders
Multi warehouse
Differential approach
Internal processing
How to use templates
Template gallery
Creation and customization of templates
Responsive photo gallery in eBay description
Creation and activation of a connector to create/update alternative descriptions
Match categories
Update Price List
Dynamic currency conversion
Internal processing script
Attribute enrichment script
Barcode type calculation
Generation of derived products
Order transformation
Quantity rules
Distribution grid
Conversions and normalizations
Currency conversion
Order status normalization
SKU recoding
eBay integration
eBay nodes installation
Matching with eBay categories
Sales terms
Parameters for listing generation
eBay listing generation
Download listings from eBay
Fixed price sale or auction
eBay listing details list
Listing update
Early ending of listings
Responses from eBay and related logs
The automated workflow
Download orders from eBay
Download categories from the eBay shop and match with product categories
Matching of eBay categories international markets
Copy Manufacturer and MPN to Attributes
Amazon integration
Amazon node
Amazon listings and details
Creation and publication of products/offers to Amazon
Set up Amazon shipping templates
Products already on Amazon
Parameters configuration for preparing Amazon offers
Amazon offers generation connector
Creation of products already present on Amazon
New products publishing
Parameters configuration for preparing Amazon offers
Creation of products not present on Amazon
Amazon offers generation connector
Matches with Amazon categories
Selling on Amazon: Attributes tutorial
Clothing category tutorial
Shoes category tutorial
Responses from Amazon and related Logs
Download orders from Amazon
Order status update from bindCommerce
Amazon Business integration
B2B prices
VAT classification
Discounts for quantities
Amazon Business order download
Billing management
Upload invoices issued by Danea
Download invoices on Danea
Transfer of invoices issued by Amazon to Danea
Delivery preferences
ePrice integration
ePrice listings preparation
ePrice node installation
Sending ePrice listings
Download ePrice orders
Creation of sample product files
Orders update to ePrice
ManoMano integration
ManoMano nodes installation
Send listings to ManoMano
Download orders from ManoMano
cDiscount integration
Category matching
Shipping methods mapping
Cdiscount node
Couriers mapping
Publishing new products on cDiscount
Publication of offers on Cdiscount
Import orders from Cdiscount
Cdiscount problem fixing
Allegro integration
Allegro node installation and configuration
Create Allegro Category Matches
Publishing products on Allegro
Product update on Allegro
Import orders from Allegro
AliExpress integration
AliExpress node installation
AliExpress category matching
Publishing products on AliExpress
Product groups and AliExpress brands
Download orders from AliExpress
Wish integration
Wish node installation
Publishing products on Wish
Carrier mapping for Wish
Download orders from Wish
Order update on Wish
Zalando integration
Zalando node installation (CR)
Offers management on Zalando (CR)
Import orders from Zalando (CR)
Leroy Merlin integration
Leroy Merlin node installation
Leroy Merlin pairing categories
Export products on Leroy Merlin
Offers publication on Leroy Merlin
Offers update on Leroy Merlin
Delete products/offers on Leroy Merlin
Downloading orders from Leroy Merlin
Orders update on Leroy Merlin
Conrad integration
Conrad node installation
Conrad category matching
Product creation on Conrad
Sending offers on Conrad
Removing products/offers from Conrad
Update offers on Conrad
Import orders from Conrad
Order update on Conrad
VirtueMart integration
VirtueMart node
Download orders from VirtueMart
Upload orders on Virtuemart
Upload products on VirtueMart
Download products from VirtueMart
Download product link from Virtuemart
WooCommerce integration
WooCommerce node
Download orders from WooCommerce
Download configurations from WooCommerce
Uploading orders on WooCommerce
Product publishing
Import products from Woocommerce
Plugin bindCommerce for WooCommerce
Prestashop integration
Prestashop node installation
Uploading orders on PrestaShop
Download orders from Prestashop
Downloading products from Prestashop
Product publishing on Prestashop
Connector for downloading Prestashop configurations
Magento integration
Magento node
Download orders from Magento
Upload orders on Magento
Product publishing on Magento
Import of Magento products
Shopify integration
Shopify node
Products import from Shopify
Publishing products on Shopify
Download configurations from Shopify
Integration of Mlveda's Multi Country Pricing App
Download orders from Shopify
Upload orders on Shopify
OpenCart integration
OpenCart node installation
Publishing products on OpenCart
Download orders from OpenCart
Import products from OpenCart
Uploading orders on OpenCart
Ecwid by Lightspeed integration
App installation and connection
Publishing products on Ecwid by Lightspeed
Import products from Ecwid
Import orders from Ecwid
Export orders from Ecwid
Social Networks
Facebook Catalogue integration
Configuring the Facebook Catalogue feed
Price comparators
Google Shopping integration
Translation and content enrichment
Integration with Google Translate
Integration with Icecat
Payment systems
Integration with PayPal
Import files
File format
Data file import
API for developers
API node
Export Orders
Import Products
Export Products
Documents import
Shipping update (legacy)


bindCommerce s.r.l.

VAT Number IT07798861212 - SDI M5UXCR1
Registered in Napoli - REA: NA - 910618
Share capital € 20.000,00 fully paid
Tel: +39 011 089 122 0
E-mail: [email protected]

PON 2014>20 Riaccendiamo lo sviluppo