EAN-130041260357206   EAN-13 barcode 0041260357206
UPC-A041260357206   UPC-A barcode 041260357206
Product Name0041260357206
Amazon.com12-11-2018 9:13:57am
UPCChecker.com10-20-2016 6:33:08pm
Upcdatabase.org10-20-2016 6:33:07pm
Created08-26-2016 7:25:29pm
Modified12-11-2018 9:13:56am
Search Googleby EAN or by Title
Query Time0.0044119

The extra items are numerically indexed and provide extra text to go along with numeric values such as weights or distances or even currencies. The attributes that use these extra indexes are all numeric and take two fields. You can send the data in a single field as long as you use the same short or long text that we keep in our database.

Although the data feed API can deliver information as JSON or XML, we are using XML here because it is easier to read.


Looking at this example, you can see that the EXTRA portion is an array of values each with their own properties. Here is what each section means:

This extra information is normally used in a drop down box next to the numeric data field that we want to enhance. Some examples might be:

You see we can display the long or short version of the extra code by using the ID index.

Fields that make use of this extra information require it when pushing data back to us in the feed. You can either send the data in two fields (value and extra_id) or in a single field (value) as long as the text following the numeric portion matches the long or short version of the extra data we store for the field.

For example, if you wanted to update a field that represented distance with the value "100 yards", you could either send that data just like that in the value field value=100+yards or in two seperate fields value=100&extra_id=505 and you would get the same results. If you send an invalid extra_id or text after the number that doesn't match our accepted list, your update would be rejected.