Skip to content

Article Data

Every day we publish product information, price and stock details. This information can be imported into your Web shop, ERP system, POS system etc. for sales and comparison functions.

Availability

Data feeds are generated daily, during the night. In general, files are generated and ready for import at 06:00 in the morning. During the initial setup of the service agreement you can specify which days of the week you would like to receive the data feed.

File Types

Article data is available in the following formats:

  • CSV
  • XML

File Size

To prevent excessive file size we compress the data feeds. This saves transfer time and bandwidth on both sides. We use the GZIP (.gz) standard to accomplish this. During the initial setup it is possible to (de)activate this option.

Character Encoding

Both file types, CSV and XML use the UTF-8 Character encoding set. When doing an import make sure to use: 65001 Unicode (UTF-8).

Download Options

There are 3 options available to obtain the data feed.

  • Manual download via the Nedis webshop (My Account > Nedis Connect > Datafeed)
  • Nedis FTP server
  • Your own FTP server

The best way to obtain the data feed is by downloading it from our FTP server or have it uploaded to your own FTP server. At the initial setup, we will create a private account on the Nedis FTP server to post the data feed to and will send you your personal login details for the server. From here, you can download the file in the morning for processing.

File Naming

The following file format is used:

nedis_catalog_YYYY-MM-DD_ll_LL_CCCCCCCC_VVVV_VVVV.EEE

CSV Example

nedis_catalog_2013-01-01_en_US_282828_v1-0_csv_full.csv

XML example

nedis_catalog_2011-10-27_en_US_282828_v1-0_xml.xml

Creation Process

The creation process in short:

  • While the file is being generated it will appear on the server as a TMP file
  • After a successful transfer we will rename the file to the according format
  • The old file will be deleted.
  • This means that there is always 1 file available for download.
  • We don’t store old files on the Nedis FTP server.

Note

When you choose the option to receive the file on your own FTP server, please make sure you have enough disk space available. Also take note that you purge/delete old files after a certain time interval. We do not delete files on external FTP servers.

Whitelist IP Address

Make sure our server is allowed to connect to your FTP server in case you want to have the files posted on your own server.

IP: 213.207.103.125

Extra Files / Public FTP Server:

Address: ftp.content4us.com

Login: nlnedisfiles

Password: w5sS3jPYEjGP

The Extra Files are available from the public FTP server that can be used in combination with your personal data feed. The personal data feed is not posted here but available as described above in the download options.

Available Extra files on Public FTP Server:

Name Description
OOP / Inactive File List of NedisPartnr that have gone Out of Program or that have set inactive for sales (6 month range)
Alternatives File (CSV+XML) List of alternative products for a NedisPartnr
Accessories File (CSV+XML) List of accessories for a NedisPartnr
Family File (CSV+XML) List of variants (products that differ on one or two attributes) with a product family
Media File List of media files attached to NedisPartnr (documents, images, videos)
Tax Additions List of Tax Additions (governmental fees on batteries, copyrighted media, etc.)
Logistical Data file List of logistical data for a NedisPartnr
UNSPSC Reference File Reference Table with category descriptions
FAQ File (XML) List of available Questions and Answers for a NedisPartnr
Property File (CSV) List of all available properties for NedisPartnr
Property Translation File (XML) Necessary file to map properties from the XML datafeed to it’s correct language and unit.
Cross Reference File (XML) List of external make/models mapped to Nedis products. (Beta)

Data Feed Communication workflow

Screenshot

Available Data by File Type

Below an overview with available data which is included in the main article data files (csv/xml) or availability of the data at another location.

Information field Field Description CSV XML
Supplier The supplier of the products in the file. Examples are: Nedis_NL or Nedis_BE
Locale ISO Country and language settings Examples are: en_US or fr_BE
NedisPartnr This is the Nedis sku name for the product used by all subsidiaries this is used for ordering at Nedis.
Nedis Article ID This is a unique number applied to the products (can ++not++ be used for ordering at Nedis!)
Vendor Part Number This is the vendor part number for the product. This can differ from the NedisPartnr tag. It refers to the original part number from the manufacturer. In many cases this is the same as the NedisPartnr since we are the manufacturer. But in other cases (Logitech, Philips, Sony) if available the original part number will be shown here.
Brand This is the brand of the product
EAN EAN13 code of the product
Intrastat Code The intrastat code of the product for export and import reporting.
UNSPSC The UNSPSC code of the product
Header Text (short) This field contains the short product description as shown on the Nedis websites
Internet Text (medium) This field contains the long product description as shown on the Nedis websites.
General Text (long) This field contains the additional product descriptions as shown on the Nedis websites.
Currency Monetary Currency in which price information is displayed
Pricing Levels Price levels based on our tier pricing
Special pricing Levels Price levels based on our special offer tier pricing
MOQ Levels Minimum Order Quantity related to the tier pricing level
Local stock Information This is the stock quantity at the moment of file creation.
Central Stock Information This is the stock quantity at the moment of file creation
Next Date for Stock (Local) Date when we expect new stock. Format: YYYY-MM-DD
Next Date for Stock (Central) Date when we expect new stock. Format: YYYY-MM-DD
Advised Retail Price Estimated retail price (Incl. VAT)
Category Levels ID ID numbers for categorisation tree
Category Levels Descriptions Categorisation levels
Product Introduction Date Date the product had first stock
Serial Number Keeping Nedis does not yet keep serial numbers for tracking.
Price Date Range “From – To” - date for a price
Packaging Types Type of packaging 1
Packaging Weight Weight of the SKU + packaging 1
Packaging Quantity Amount of SKU in a packaging 1
Packaging Dimensions ( L x W x H ) Dimensions of the packaging of the SKU (length x width x height)
Additional Tax info Some products contain governmental taxes or environmental / copyright fees (batteries, dvd-r etc.) 1
Accessories A list of accessories that are suitable with the SKU 1 2
Alternatives A list of alternatives for the SKU 1 2
Units of Measurement (Um-file) Type of packaging and the next available packaging types and quantities + dimension + weight info 1 2
FAQ’s Frequently asked questions available for the SKU 1 2
Image / Photo Type Type of photo (Application / Packaging, Front etc.) 1
Product Photos (all) Different type of product photos 1
360 degree photos Interactive photo that shows the product from all sides 1
Product videos Video about the product 1
PDF Documents Documents available for the product 1

Info

1 This information is available in a separate csv file

2 This information is available in a separate xml file

Additional Information on Data Fields

Going Prices

This is the suggested retail pricing in the local currency (including local tax). The going price is always based on the smallest sales unit.

Picture Dimensions

To obtain other formats you can change the directory path (if available) according to the table below:

Dimensions Link
60px (square) http://pictures.content4us.com/60px/
100px (square) http://pictures.content4us.com/100px/
140px (square) http://pictures.content4us.com/140px/
283px (square) http://pictures.content4us.com/283px/
350px (square) http://pictures.content4us.com/350px/
High Resolution http://pictures.content4us.com/products_high_res/

General Implementation Notes

More information on Stock

The stock data communicated in the data feeds is static. This is the closing stock from the day before. Where our warehouses and systems are running 24/7 the stock can change by the minute. Please use the real time stock check before accepting an order to prevent backorders on products with low availability.

More information on Pricing

All purchase prices are excluding the local tax. The mentioned going prices are including the local tax. At the moment prices communicated are based on the default tier pricing system. In case of specific price agreements with your local Nedis office this might not be visible in the data feed. Please enquire with your representative for more information.

More information on Minimum Order Quantities

In some cases the mentioned quantity with cables on reel (packaging type 16) is per meter and not per reel. With batteries the quantity can be 4 because they are packed per blister. We are in an ongoing process to adjust these measurements for all our products to a per 1 packaging quantity. Always use the combination MOQ x Price to obtain the correct price for an article.

General Advice on Implementation

The articles that are available on the day of import, is the assortment that is active for sales at that specific day. If a particular product is not in the feed in the next day, it’s not for sale at Nedis and it’s best to deactivate/delete this from your database. When the product is activated again it will also appear in the data feed again. For a list of articles that have gone Out of Program (OOP) or are set to inactive (temporarily) please refer to the OOP/Inactive File.

Detailed XML Data Feed Information

<?XML version=”1.0” encoding=”UTF-8” ?>
Standard header for xml messages.

<!-- Legal disclaimer -->

<nedisCatalogue>
Start of main message

<headerInfo>
In this tag you can find overall information about this Content-Connect data feed.

<feedVersion>
This is the version number of the file you are receiving. Caused by strong development of the E-business possibilities and infrastructure at Nedis, this can change. Important! When we have a new version available, we will notify you and we define a time period in which the old version is phased out.

<dateCreated>2013-02-02T15:12:34+01:00</dateCreated>
This is the date/time stamp when the data feed was created. Format is YYYY-MM-DDTHH:MM:SSZZZ:ZZ where the Z represents the time zone.

<supplier>Nedis_NL</supplier>
This is the identifier from which Nedis subsidiary the file is originated.

<locale>nl_NL</locale>
This identifier for the language of the data feed. If you requested more languages there will be separate files available for you.

<productList>
The start of the product listing.

<product>
This tag encloses each product in the feed. This is a repeating group

<nedisPartnr>
This is the Nedis part number for the product used by all subsidiaries, this is the only accepted order code at Nedis

<nedisArtlid>
This is the Nedis database number for the product used by all Nedis subsidiaries

<vendorPartnr>
This is the vendor part number for the product. This can differ from the nedisPartnr tag. It refers to the original part number from the manufacturer. In many cases this is the same as the NedisPartnr since we are the manufacturer. But in other cases (Logitech, Philips, Sony) if available the original part number will be shown here.

<brand>
This is the brand name of the product.

Note

Since this is a !CDATA field it can contain HTML or non-standard characters.

<EAN>
This is the EAN code of the product.

<intrastatCode>
The intrastat code of the product for export and import reporting.

<UNSPSC>
The UNSPSC code of the product. (where available).

<headerText>
This field contains the short product description as shown on the Nedis websites.

Note

Since this is a !CDATA field it can contain HTML or non-standard characters.

<internetText>
This field contains the long product description as shown on the Nedis websites.

Note

Since this is a !CDATA field it can contain HTML or non-standard characters.

<generalText>
This field contains the additional product descriptions as shown on the Nedis websites.

Note

Since this is a !CDATA field it can contain HTML or non-standard characters.

Picture Types

<images>
    <image type=”XX” order=”YY”>filename</image>
XX parameters
2 Product Picture
3 Packaging Picture
4 360/3d photograpy (needs Flash)
5 Application Picture
16 Package Content
22 Energy label
25 Primary Packaging Picture

The YY parameter is ascending and shows the order sequence we use to show the picture on our websites. For example a picture with order=1 is our main picture on the Nedis website. The pictures are available in different sizes and can be fetched by combining the URL below and the filename which is in the <image> tag,

Dimensions Link
60px (square) http:// pictures.content4us.com/60px/
100px (square) http:// pictures.content4us.com/100px/
140px (square) http:// pictures.content4us.com/140px/
283px (square) http:// pictures.content4us.com/283px/
350px (square) http:// pictures.content4us.com/350px/
High Resolution http://pictures.content4us.com/products_high_res

Type 4 images (360/3D photography)

With this parameter you can show 360/3D photography on your website.

To do this you need to implement the code snippet below. On the position marked with red the data should be replaced with the parameters which are in the type 4 tag of images.

If we do not have 360/3D content the type 4 tag not mentioned in the image section and the code below is not necessary.

<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase=http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,65,0 width="100%" height="100%">
<param name="movie" value="http://360.content4us.com/fsi/viewer/fsi.swf?&amp;cfg=viewer3d_presets/3d_spin_and_blur&amp;images3durl=Nedis+Images%2f<PUT TAG INFO HERE> &amp;initialaction=NextScene&amp;intro=intro_nedis&amp;language=english"> <param name="allowscriptaccess" value="always"> <param name="allowfullscreen" value="true"> <param name="quality" value="high"> <embed src="http://360.content4us.com/fsi/viewer/fsi.swf?&amp;cfg=viewer3d_presets/3d_spin_and_blur&amp;images3durl=Nedis+Images%2f<PUT TAG INFO HERE> &amp;initialaction=NextScene&amp;intro=intro_nedis&amp;language=english" allowscriptaccess="always" allowfullscreen="true" quality="high" type="application/x-shockwave-flash" pluginspage="http://www.adobe.com/go/getflashplayer" width="100%" height="100%"> </object>

Note

the 360 viewer will be loaded from our server with the Nedis skin by default. Other skins available can be loaded as &skin={skin name}

Available skin names are: nedis, plain, silver, black.

<attachments>

If products have commercial attachments like manuals and product sheets you can find them here.

Note

Since this is a !CDATA field it can contain HTML or non-standard characters.

<attachment type=”XXX” description=”description”><![CDATA[URL]]></attachment>
  • Portable Document Format ( Acrobat Reader)
  • Driver Software
  • Movie
  • External Link
  • Manual
  • CE
  • Safety datasheet
  • Product datasheet

When there is a description available it will be shown. This a more human readable text which can be used for an anchor text in the link.

Driver Software:

<attachment type="Driver Software" description=""><![CDATA[http://attachments.content4us.com/datasheets/DRIVER_WIN7_AT-UC232A.ZIP]]></attachment>

This is a direct link to the driver for this product.

Portable Document Format ( Acrobat Reader):

<attachment type="Portable Document Format ( Acrobat Reader)" description=""><![CDATA[http://attachments.content4us.com/datasheets/MANUAL_AT-UC232A_ENG.PDF]]></attachment>

This is a direct link to a PDF. This can be a product datasheet or manual.

Manual:

<attachment type="Manual" description="Product Manual"><![CDATA[http://attachments.content4us.com/datasheets/DATASHEET_AT-VE560.PDF]]></attachment>

This is a direct link to a PDF of the product’s Manual.

Movie:

<attachment type="Movie" description="Product Presentation"> <![CDATA[http://www.youtube.com/watch?v=j9CFt_O9j6E]]></attachment>

This is a direct link to the product videos on Youtube.com

CE:

<attachment type="CE" description="CE Declaration"><![CDATA[http://attachments.content4us.com/datasheets/CE_DOC_AVSPLIT-24.PDF]]></attachment>

This is a direct link to product’s CE file

Safety Datasheet:

<attachment type="Safety datasheet" description="Product Safety Document"><![CDATA[http://attachments.content4us.com/datasheets/HAV-IR23_TESTRESULT.PDF]]></attachment>

This is a direct link to the product’s safety warnings.

Product Datasheet:

<attachment type="Product datasheet" description=""><![CDATA[http://attachments.content4us.com/manuals/NLNED/PRODUCT_DATASHEET_HAV-KCD11.PDF]]></attachment>

This is a direct link to the product’s datasheet.

<categories>
    <tree name=”XXXXXXX”>

This will tell you which tree Nedis is using for the categorization of the product on the Nedis sites.

Note

a product can be assigned to multiple trees, it is the choice of the users to adopt this or choose one of the trees.

<entry depth=”0001” id=”506”>

Text representation of the category

The entry depth will tell you on which level it is in the tree, the higher the number the deeper the tree level entry is. The id represents a numerical representation of the text which will follow in this tag.

Note

the following id’s are used to identify retail support and POS materials. These can be filtered out if required. ID:1002154 (catalogues) ID:1002153 (blister support) ID: 1002156 (poly bags)

<properties>
 <property id="XXX" multiplierID="" unitID="" valueID=””><![CDATA[YYY]]></property>

These values represent the different properties a product may have. For example: length, connector types, diameter, watt, voltage, usage, color. This is a repeating element and can differ per product.

To use this you also need the use the additional file called nedis_property_translations_YY-MM-DD.xml which can be fetched from our general FTP (login details provided above). This file contains the text values of the ID’s in all languages we support.

In the next section the property translation file will be described in detail.

<status>
    <code status=”XX”>

An article can have status NORMAL or GOTO

NORMAL: article is active for sales at Nedis GOTO: Article is not active for sales anymore and there is an alternative/replacement in place

Note

When there is a code GOTO the following field is the Nedis_artlid and NOT the standard Nedis partnumber. This number can be found in the tag <nedisArtlid> of the feed.

<packaging quantity=”Y” Weight=”ZZZ”>XX</packaging>

This tag contains the packaging information. The packaging element can be repeated while there are more packaging types available

ID Explanation
0 Unknown
1 Backcard
2 Bag
3 Blister
4 Bottle
5 Giftbox
6 Giftbox with eurolock
7 Header
8 Inlay
9 Label
10 Label + backcard
11 Sticker
12 Wrap
13 Box
14 Label with eurolock
15 Unpacked
16 Reel / Rol

The packaging quantity (Y value) is the amount in this packaging. For example batteries: the packaging is one blister and the quantity is 4.

Note

In some cases the packing quantity (Y value) can have an empty value.

Apart from that, the packing quantity (Y value) is never a value to fall back on when in doubt of MOQ’s (Minimum Order Quantity). More on MOQ’s below.

Please use the value as a multiplier. If the Y value is 4 then 2 packages will contain 8 items.

Note

The weight is always in metric grams and decimal separator (point)

<introductionDate>

This date refers to the date the product was first on stock in the warehouse.

Identify New Articles: <introductionDate> Makes it easy to identify new products and mark them as such. For example: if the product is in stock and the introductionDate falls within range of today’s date minus 14 days you can show newest products from the last 2 weeks.

Identify Expected Products: <introductionDate> will show 0000-00-00 as date and the product already contains a <NextExpectedStockDateCentral> that lies in the future.

<serialnumber_keeping>

Future use, currently we do not store serial numbers

<priceLevels>
    <normalPricing from=”YYYY-MM-DD” to=”YYYY-MM-DD”>
        <price level=”X” moq=”Y” currency =”ZZZ”>AMOUNT</price>
    <specialOfferPricing from=”YYYY-MM-DD” to=”YYYY-MM-DD”>
        <price level=”X” moq=”Y” currency =”ZZZ”>AMOUNT</price>

This field contains the pricing levels. Each level has its own MOQ (Minimum Order Quantity) and pricing in the currency which we provide. The point (.) is the decimal separator.

For most B2C webshops the MOQ will be 1. However some of our products currently have deviant MOQ levels so when used in combination with dropshipping always check if an item is available for dropshipping per 1 item.

Note

When a special offer is active the feed will contain both sets of pricing. You can choose which set to use and this is especially important if the price will be calculated back to single item prices like in a webshop. When there is no special price active the fields will be left empty. In case you wish to make use of the “best pricing mechanism” it’s advised to do so based on your own set of business rules.

<goingPriceInclVAT currency=”XXX” quantity=”Y”>AMOUNT</goingPriceInclVAT>

The last tag in the field is the advised sales price including the country specific tax. The point(.) is the decimal separator.

<tax>
    <tax_addition moq="XX" code="YY" text="ZZZZ" currency="EUR" PricePerPiece="1234">14.88</tax_addition>

This field contains the possible additional taxes which are mandatory on certain products. This can differ per country. The amount is in the local currency.

The MOQ indicates the minimal order quantity of the products, please use this field a multipliable value. If the MOQ is 4 please do not order 6 or 10 but 4, 8 or 12.

Important

It’s important that additional taxes on certain products are shown correctly to the user as we have to invoice them and pay them to the local tax offices.

Example:

<tax>
    <tax_addition moq="5" code="3" text="Buma/stemra-heffing" currency="EUR" PricePerPiece="0.35">1.75</tax_addition>
</tax>

Note

These taxes can change per country. Every country has its own regulations. Please consult your local Nedis office for details which taxes could be applied.

<stock>
    <inStockLocal>

This is the quantity which was available on stock on the moment the catalogue file was created.

Important

This is a dynamic number which fluctuates during the day.

<inStockCentral>

This is the quantity Nedis has in stock at her central warehouse in the Netherlands.

Important

This is a dynamic number which fluctuates during the hour. For a real time value please use the Real Time Request before accepting or posting the order.

<ATP>
    <nextExpectedStockDateLocal>

This is the date when we expect new free for sales stock. Format YYYY-MMM-DD

Important

This is an indicative date. This date can change without notice. It is not confirmed!

<nextExpectedStockDateCentral>

This is the quantity of free stock which we expect to receive on the date in the field above.

Important

This is an indicative date. This date can change without notice. It is not confirmed!

Implementation of Product Properties (XML)

To successfully implement the product properties you need to use the additional file called nedis_property_translations_YY-MM-DD.xml which can be fetched from our general FTP (login details provided earlier). This file contains the text values of the ID’s in all languages that are supported.

With this file you can translate the various id mentioned in the data XML file to values an text.

Version

We have 2 versions available for download. One is compressed with gzip and the other one is uncompressed. There is a date stamp in the filename.

Filename: nedis_property_translations_2010-06-14.xml.gz OR nedis_property_translations_2010-06-14.xml

Format

The format described in this document is XML with UTF-8 as codebase. All values are written as !CDATA.

<?xml version="1.0" encoding="UTF-8"?>

Standard XML header

<nedisCatalogue>

Start tag of the feed

<headerInfo>

Start of header information

<translations>

Start of the translations

<properties>
    <property id=”XXXX”>

This property id matches the ID in the xml product feed. In the local tag you can find the value.

<locale name=”yy_YY>![CDATA[ZZZZZ]]</locale>

In the locale name you can find the country code and the value contains the value of this locale

Important

We currently do not maintain the attributes 'multiplierID', 'unitID' and 'valueID' anymore so they will remain empty. The value of the property is now placed in the property tag itself enclosed by CDATA tags. You will still need to get the property name in your language by using the additional file mentioned above.

Example

Below a snippet from the XML datafeed. The product is a an in-ear headphone with our product number SWTWS01B

<nedisPartnr>SWTWS01B</nedisPartnr>
<nedisArtlid>550654800</nedisArtlid>
...
<properties>
 <property id="238" multiplierID="" unitID="" valueID=""><![CDATA[Built-In Lithium-Polymer]]></property>
 <property id="270" multiplierID="" unitID="" valueID=""><![CDATA[v4.1]]></property>
 <property id="578" multiplierID="" unitID="" valueID=""><![CDATA[Bluetooth]]></property>
 <property id="578" multiplierID="" unitID="" valueID=""><![CDATA[TWS]]></property>
 <property id="963" multiplierID="" unitID="" valueID=""><![CDATA[Built-In Microphone]]></property>
 <property id="1016" multiplierID="" unitID="" valueID=""><![CDATA[Black]]></property>
 <property id="1258" multiplierID="" unitID="" valueID=""><![CDATA[5 V 0.5 A]]></property>
 <property id="1266" multiplierID="" unitID="" valueID=""><![CDATA[USB]]></property>
 <property id="1453" multiplierID="" unitID="" valueID=""><![CDATA[Stereo]]></property>
 <property id="1591" multiplierID="" unitID="" valueID=""><![CDATA[In-Ear]]></property>
</properties>

Let’s examine the properties and try to match this in the us_US language

<property id="238" multiplierID="" unitID="" valueID=""><![CDATA[Built-In Lithium-Polymer]]></property>

In the translation file we find

<property id="238">
 <locale name="en_US"><![CDATA[Battery type]]></locale>
 <locale name="de_DE"><![CDATA[Battery type]]></locale>
 <locale name="fr_FR"><![CDATA[Battery type]]></locale>
 <locale name="nl_NL"><![CDATA[Type batterij]]></locale>
 ...
</property>

Here we find the value is “Battery type”

Conclusion: this in-ear headphone has a property “Battery type” with the value “Built-In Lithium-Polymer”. Via this method you can find all properties attached to the products.

Property files in CSV format

Part of the Extra Files which can be found on the public FTP server is the Property File in CSV format. With this file you can import all the properties of the articles active for sale on the day of import.

This is equal to the assortment in the article datafeed. Because this can differ per county the files are country specific.

Filename: nedis_properties_xx_XX_YYYY-MM-DD.csv

Where xx_XX stands for the country codes and YYYY-MM-DD for the create date.

Example 1: The German File is named: nedis_properties_de_DE_2013-01-09.csv For country with more than one official language, there are separate versions available.

Example 2: Belgium: Dutch Belgium version: nedis_ properties nl_BE_2013-01-09.csv French Belgium version:nedis properties _fr_BE_2013-01-09.csv

Frequency: These files are updated on a daily basis.

OOP / Inactive Files

These files contains the products which have gone Out Of Program (OOP) in the last 6 months. These products are not contained in the feed anymore and are no longer available for sale. Note: This feed can also contain products that have gone temporary blocked for sales. When they are active again they will be distributed through the regular data feed process again.

Because this can differ per county the files are country specific.

Filename

nedis_ooplist_xx_XX_YYYY-MM-30.csv

Where xx_XX stands for the country codes and YYYY-MM-DD for the create date

Example 1 (German): The German File is named: nedis_ooplist_de_DE_2010-07-30.csv For country with more than one official language, there are separate versions available.

Example 2 (Belgium): Belgium: Dutch Belgium version: nedis_ooplist_nl_BE_2010-07-30.csv French Belgium version:nedis_ooplist_fr_BE_2010-07-30.csv

File format
The file is in CSV format, comma separated and fields are delimited with double quotes.

The first line contains the field definition names.

The first column is named NedisPartnr and contains the Nedis partnumber code of the OOP product.

The second column is named EAN and countains the EAN code of the OOP product.

The third and last column is name DateChanged and shows the date the product got deactivated.

Example
"NedisPartnr","EAN","DateChanged"
"12041500","5412810118557","2010-07-30"
"21982500","5412810118786","2010-07-30"
"ANT 113-KN","5412810120406","2010-06-14"

Frequency
These files are updated on a daily basis.

Accessories Files

This file provides accessories we advise for certain products in our range and can be used to automate the cross-sell process.

XML Format The format described in this document is XML with UTF-8 as codebase.

Filename nedis_acclist_YYYY-MM-DD.xml

Example

<?xml version="1.0" encoding="UTF-8"?>

Standard XML header

<nedisCatalogue>

Start tag of the feed

<headerInfo>

Start of header information

<feedVersion>1.0</feedVersion>

information about the version

<dateCreated>2010-03-22T01:50:03+0100</dateCreated>

The date the feed was created

<supplier>Nedis</supplier>

Supplier

<headerInfo>

End of the header information

<productlist>

Repeating tag per product

<product>

Repeating tag per product

<nedis_artID>13007</nedis_artID>

The Nedis artID. This is the unique number for the product

<nedis_artCode>SBC5221</nedis_artCode>

The Nedis part number as used on the Nedis websites.

<accessoiries>

Start of the accessories for this product.

<accessory id="28465">CAMC.CHARGER</accessory>

Per alternative you will find the ID (=Nedis_artID) and the nedis_artCode

            </accessoiries>
        </product>
    </productlist>
</nedis_catalogue>

CSV Format The file is comma separated and fields are delimited with double quotes. The first line contains the field definition names. We communicate a one on one relation between 2 products, the match can be made based on NedisPartnr or on NedisArtlId.

Filename nedis_acclist_YYYY-MM-DD.csv

Frequency These files are updated on a daily basis.

Example

"NedisArtlId","NedisPartnr","AccessoryArtlId","AccessoryNedisPartnr"<br>
"99396","273513","35979","W1-04197"
"297362","361127","35979","W1-04197"
"56021209","9001666404","56021213","9001666578"
"56021209","9001666404","56021215","9001666586"

Alternative Files

In these files we communicate alternative products related to the products communicated in the Article Data Feed. This file can be used for up-selling purposes (based on price of the alternative) or showing related products.

XML Format The format described in this document is XML with UTF-8 as codebase.

Filename nedis_altlist_YYYY-MM-DD.xml

Example
<?xml version="1.0" encoding="UTF-8"?>
Standard XML header

<nedisCatalogue>
Start tag of the feed

<headerInfo>
Start of header information

<feedVersion>1.0</feedVersion>
Information about the version

<dateCreated>2010-03-22T01:50:03+0100</dateCreated>
The date the feed was created

<supplier>Nedis</supplier>
Supplier

</headerInfo>
End of the header information

<productList>
Start of the product listing

<product>
Repeating tag per product

<nedis_artID>10764</nedis_artID>
The Nedis artID. This is the unique number for the product.

<nedis_artCode>130.41275</nedis_artCode>
The Nedis part number as used on the Nedis websites.

<alternatives>
Start of the alternatives for this product.

<alternative id="153">BY228-PHI</alternative>
Per alternative you wil find the ID (=Nedis_artID) and the nedis_artCode

            </alternatives>
        </product>
    </productList>
</nediscatalogue>

CSV format The file is comma separated and fields are delimited with double quotes. The first line contains the field definition names. We communicate a one on one relation between 2 products, the match can be made based on NedisPartnr or on NedisArtlId.

Filename nedis_altlist_YYYY-MM-DD.csv

Example

"NedisArtlId","NedisPartnr","AlternativeArtlId","AlternativeNedisPartnr"
"10402","052.10399","76714","NFR25 39R"<br>
"20411","115710-GVT","1022170","AH-972/60"<br>
"659423","1182.0887","14886","HR6488"<br>
"659423","1182.0887","91339","KN-3019000"

Frequency

These files are updated on a daily basis.

Family Files

In these files we communicate the products communicated in the Article Data Feed that differ on one or two properties, like colour or length. This file can be used for up-selling purposes (based on price of the variant) or showing related products.

XML Format

The format described in this document is XML with UTF-8 as codebase.

Filename

nedis_familylist_YYYY-MM-DD.xml

Example
<?xml version="1.0" encoding="UTF-8"?>
Standard XML header

<nedisCatalogue>
Start tag of the feed

<headerInfo>
Start of header information

<feedVersion>1.0</feedVersion>
Information about the version

<dateCreated>2010-03-22T01:50:03+0100</dateCreated>
The date the feed was created

<supplier>Nedis</supplier>
Supplier

</headerInfo>
End of the header information

<productList>
Start of the product listing

<product>
Repeating tag per product

<nedis_artID>10764</nedis_artID>
The Nedis artID. This is the unique number for the product.

<nedis_artCode>130.41275</nedis_artCode>
The Nedis part number as used on the Nedis websites.

<alternatives>
Start of the alternatives for this product.

<alternative id="153">BY228-PHI</alternative>
Per alternative you wil find the ID (=Nedis_artID) and the nedis_artCode

            </alternatives>
        </product>
    </productList>
</nediscatalogue>

CSV format
The file is comma separated and fields are delimited with double quotes. The first line contains the field definition names. We communicate a one on one relation between 2 products, the match can be made based on NedisPartnr or on NedisArtlId.

Filename
nedis_familylist_YYYY-MM-DD.csv

Example

"NedisArtlId","NedisPartnr","AlternativeArtlId","AlternativeNedisPartnr"<br>
"10402","052.10399","76714","NFR25 39R"<br>
"20411","115710-GVT","1022170","AH-972/60"<br>
"659423","1182.0887","14886","HR6488"<br>
"659423","1182.0887","91339","KN-3019000"

Frequency
These files are updated on a daily basis.

Media File

This file contains all attached media to a product. The NedisPartnrs in this file are corresponding to the part numbers in the article data feed.

Filename:
nedis_mediafiles_xx_XX_YYYY-MM-DD.csv

Where xx_XX stands for the country codes and YYYY-MM-DD for the create date.

File format
The file is in CSV format, comma separated and fields are delimited with double quotes. The first line contains the field definition names. The first column is named NedisPartnr and contains the Nedis partnumber code of the OOP product. The second column is named EAN and countains the EAN code of the OOP product. The third and last column is name DateChanged and shows the date the product got deactivated.

Example:

"Supplier","Locale","NedisPartNr","File type","Description","Order sequence","Identifier","Url"
"Nedis_XPNED","en_US","KN-LED60","Packaging Picture","","1","KN-LED60_MR.JPG","http://pictures.content4us.com/283px/KN-LED60_MR.JPG"

Frequency:
These files are updated on a daily basis.

Tax Additions

This file contains all additional taxes or fees that can be applicable to a product in certain countries. Most of the time this concerns governmental taxes and fees on Batteries, Digital Media and energy related products.

Filename
nedis_taxadditions_NEDCODE_YYYY-MM-DD.csv

Where NEDCODE stands for the supplier code (see chapter 2.13) country codes and YYYY-MM-DD for the create date.

File format
The file is in CSV format, comma separated and fields are delimited with double quotes. The first line contains the field definition names. The first column is named NedisPartnr and contains the Nedis partnumber code of the product containing an additional charge. The second column is named TaxDescription and contains a short description about the fee. The third and last column is Price and shows the monetary value of the particular tax or fee.

Example

"nedisPartNr","TaxDescription","Price" "HQ-NIMH-AA-04","Cat I AA/(L) R06","0.0800" "HQ-NIMH-AAA-01","Cat I AAA/(L) R03","0.0800"

Here, a 0.08 cent tax is active on the product. It concerns a tax on batteries (NL).

Frequency
These files are updated on a daily basis.

FAQ File (Frequently Asked Questions)

This file contains a collection of frequently asked questions and answer for certain products (where available).

XML Format
The format described in this document is XML with UTF-8 as codebase. All values are written as !cdata because they can contain non-html codes.

Filename
nedis_faqlist_YYYY-MM-DD.xml

Example

<nedisCatalogueFaq>
    <headerInfo>
        <feedVersion>1.0</feedVersion>
        <dateCreated>2012-01-17T04:50:01+0100</dateCreated>
        <supplier>Nedis</supplier>
    </headerInfo>
    <faqList>
        <faq nedisArtlid="19381" sequence="10" langid="1" locale="en-US">
            <question><![CDATA[Where can I download the latest driver?]]></question>
            <answer><![CDATA[You can download the latest driver on the following link: <a href="http://attachments.content4us.com/upload/TEST.ZIP">TEST.ZIP</a>.]]></answer>
        </faq>
    </faqList>
</nedisCatalogueFaq>

nedisArtlid the article id of the product where this FAQ applies to.
sequence to determine sort order when multiple questions&answers apply.
langid the language id
locale the country / language code
question The question about this product
answer The answer to the question Since these can contain certain non-HTML characters it is placed with the !CDATA tag.

CSV format
The file is comma separated and fields are delimited with double quotes. The first line contains the field definition names. Since the quote sign (“”) can be included in questions-answers we add slashes to the character, this results in /” Make sure to use a StripSlashes function. Note that the questions and answers can also contain HTML breaks in the text < br/>. The column Locale is to determine the country and language the FAQ is active in.

Filename nedis_faqlist_YYYY-MM-DD.csv

Example

"NedisArtlId","Sequence","Locale","Question","Answer"
"28503","10","en_US","Where can I download the latest driver?","You can download the latest driver on the following link: <a href=""http://attachments.content4us.com/datasheets/CMP-BLUEKEY24.ZIP"">CMP-BLUEKEY24.ZIP</a>."
"28503","10","de_DE","Wo kann ich den aktuellen Treiber downloaden?<br />","Unter dem folgendem Link:<a href=""http://attachments.content4us.com/datasheets/CMP-BLUEKEY24.ZIP"">CMP-BLUEKEY24.ZIP</a>.<br />"
"28503","10","hu_HU","Hol tudom letölteni a legfrissebb drivert?","A legfrissebb drivert az alábbi link segítségével töltheti le: <a href=""http://attachments.content4us.com/datasheets/CMP-BLUEKEY24.ZIP"">CMP-BLUEKEY24.ZIP</a>."

Frequency
These files are updated on a daily basis.

UNSPSC Reference Table

In the Article Datafeeds, where available, we communicate the UNSPSC categories (level 4 only). Using the reference table corresponding descriptions and upper category levels can be retrieved.

Filename
nedis_UNSPSClist.csv

More information on UNSPSC can be found at: http://www.unspsc.org Screenshot

Logistical Data

Both XML and CSV Article Data files already contain most of the logistical information necessary. To provide a complete overview of this dataset this file can be used.

Filename
logistical_data_YYYY-MM-DD.csv

File format
The file consists out of a collection of NedisPartnrs, this can be repeated over multiple lines as there might be more information available for a specific product followed by the NedisArtlid (databaseID), the UmId (unique id for the packaging), the Um (shortname for the packaging), the factor (amount of pieces in this unit) and the Dimensions of the particular packaging unit (LxWxH) followed by the weight. Detailed XML Data Feed Information Example

"NedisPartnr","NedisArtlid","UmId","Um","Factor","Length","Width","Height","Weight"
"HQSS5555-1.5","1098722","146896975","BLI","1","280","190","70","160"
"HQSS5555-1.5","1098722","146896971","BO2","10","397","310","220","2060"
"HQSS5555-1.5","1098722","146896967","BOX","20","460","420","340","5240"
"HQSS5555-2.5","1098723","146896987","BLI","1","280","190","70","200"
"HQSS5555-2.5","1098723","146896983","BO2","10","400","220","310","2500"
"HQSS5555-2.5","1098723","146896979","BOX","20","460","410","330","6020"

Frequency
This file is updated on a daily basis.

CSV Import in Excel

Due to the fact that we use UTF-8 encoding the standard import in Microsoft excel will show “strange” characters. To import correctly, please follow the following steps (based on Microsoft excel 2003)

  1. Download the CSV file.
  2. Start Excel
  3. Create an empty worksheet
  4. Click on the menu Data -> Import External Data -> Import data (screenshot below)

Screenshot

A wizard will show and (screenshot below) and please select the datatype Delimited and choose the 65001: Unicode(UTF-8) option as the file Origin.

Screenshot

Click on the “Next” button On the following screen choose the Comma as delimiter and click on finish. After this the list will be correctly imported.

Screenshot

Important

Please check the NedisPartnr and the EAN code colum for the right format (number/text). Do not use “general” for those fields