EAN-130882956445803   EAN-13 barcode 0882956445803
UPC-A882956445803   UPC-A barcode 882956445803
Product Name0882956445803
Amazon.com12-06-2018 6:00:40pm
UPCChecker.com05-11-2017 11:44:08pm
Upcdatabase.org12-06-2018 6:00:41pm
Created05-11-2017 11:44:06pm
Modified12-06-2018 6:00:40pm
Search Googleby EAN or by Title
Query Time0.0118270

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.