Case study series 1: Using the Semantics3 API as a UPC lookup database

This week, we look at a specific use of the Semantics3 Product API

Semantics3    2 mins

Case study series #1: Using the Semantics3 API as a barcode lookup database

One of the incidental side effects of operating one of the largest product databases around is our growing UPC database. As we talked about in an earlier post, there doesn’t really exist a centralized UPC database that accurately records product data and linked UPCs (or barcodes).

There are numerous reasons for this as detailed here

Semantics3 uses a product-centric approach to extracting product information from retailers. Product data from several retailers are extracted, disambiguated, and merged to matched products.

For example, if you have Product A on Site 1 and the same product on Site 2, our software generates a confidence interval matching of 99% before confirming that both products are a match.

Once this happens, product data from both sites are extracted, disambiguated and merged into a unified product metadata for that particular item. In this case, if one site has a UPC or barcode linked to the product, this is subsequently included into the database.

This is particularly useful as an all-in-one barcode lookup database.

Using our API, you can query a UPC (or barcode) and get full product metadata, along with latest prices and offers.

Here’s an example:



This output is called JSON, which is pretty much the most malleable data-object.

Once you set up a display to read out this data, it would look like the following:

Name: Victorinox Women’s 249061 Alliance Analog Display Swiss Quartz Silver Watch


Price: $370.45

UPC: 46928038398

Latest Offer:

Offer Price: $370.48

This makes the API particularly useful as a product inventory enrichment tool. If all you have is a bunch of UPCs and nothing much else besides, you can use our database to get full, rich product data.

Published at: November 13, 2014

← Read other posts