Best barcode & UPC database APIs compared (2026)

First, know which category you need

The phrase barcode API covers two very different jobs. Confusing them is the most common reason teams pick the wrong tool.

• Barcode generators and readers: these produce a barcode image from a number, or decode a barcode from an image. They do not know anything about the product.
• Product-data lookup APIs: these take an existing GTIN and return information about the real product it identifies, such as title, brand, and category.

If you want to print labels, you need a generator. If you want to identify a scanned item, you need a product-data API. This comparison is mostly about the second category, because that is where database quality matters.

Free and open barcode tools

Open and free services such as barcode image generators render and decode barcodes well. These projects usually have a simple endpoint that returns a barcode image in formats like Code128 or EAN. Many are open source or free to self-host.

Their strength is that they are cheap and unlimited for image work. Their limitation is scope: they do not carry a product catalog, so they cannot tell you what a scanned number represents. Use them for label printing and in-app barcode rendering, not for product identification.

Product-data lookup APIs

Product-data APIs take a barcode and return the product behind it. The table lists six of them with the entry plan and free tier each vendor published on its own site on 2 October 2026. Prices are in the currency the vendor uses and are not converted.

Sources: kicks.dev, retailed.io/pricing, devs.upcitemdb.com and go-upc.com/plans/api. The Barcode Lookup website blocked our request that day, so no price is quoted for it.

• UPCitemdb is a general database that states over 744 million unique UPC and EAN numbers. The free Explorer plan allows 100 requests per day with no signup. DEV costs $99 per month for 20,000 lookups per day and PRO $699 for 150,000 per day. It is the strongest free option for general products.
• Go-UPC is a general database that states over 500 million products. Developer costs $74.95 per month for 5,000 requests, Startup $245 for 45,000 and Enterprise $795 for 450,000.
• Barcode Lookup is a general product database with an API. Its pricing is not verified here.
• KicksDB is a sneaker market data API. It aggregates pricing, sales history and product details from StockX, GOAT and Flight Club, with lookups by SKU, UPC or name. The free plan has 1,000 requests per month for the US market. Starter costs €29 for 50,000 requests and Pro €79 for 250,000, excluding VAT. It has the lowest cost per request in this table.
• Retailed.io sells scraper APIs by data source on a credit model. You get 50 credits once for free, then plans start from $49 per month for 18,000 credits. Its Sneaker Lookup UPC endpoint is available on request.
• Barcodes.gg is a barcode database for sneakers and streetwear with 3.09 million barcodes across 1.57 million products. Each barcode is stored with its size. Basic costs €19 per month for 2,000 requests, Standard €49 for 10,000, Pro €99 for 50,000 and Enterprise €199 for 200,000. The Plus plans (€35, €79 and €129) add reverse lookup from style code to barcodes. The trial runs 7 days with 100 requests and no payment method, and lookups that find nothing are not charged. It is far smaller than the general databases and does not return resale prices.

All six take an identifier and return a JSON record, so the interface is not what separates them. The catalogue is. Keep your lookup layer thin, so that switching provider or splitting traffic between a general database and a category one is a small change. The sneaker-specific options are compared in more detail on the sneaker barcode API comparison.

How to evaluate them honestly

Ignore database-size numbers. Raw record counts say little about whether your items are covered. Test each API against a sample of the barcodes your users will scan.

• Pull 50 to 100 real GTINs from your domain and run them through each candidate.
• Measure match rate on your sample, not the vendor total.
• Check field completeness for the fields you display, not just whether a record exists.
• Confirm the pricing model fits your request volume and caching strategy.

This is a far more reliable signal than any published benchmark, and it takes an afternoon.

Why category depth matters

General databases are built for packaged goods, where one product has one barcode. Fashion works differently: a single style spans many sizes and colorways, and each size has its own barcode. If your users scan sneakers or apparel, check that a candidate returns the size behind each barcode and the style code. A product title alone is not enough. We have not measured how the general databases perform on sneaker barcodes, which is why the test above matters.

A category database answers that case directly. Barcodes.gg returns the size for each barcode in US, UK and EU sizing. On Plus plans it returns every barcode held for a style code. Try a code on the free sneaker barcode lookup. For how to integrate, read the barcode API guide.

Getting started with Barcodes.gg

The barcode lookup API page lists the endpoints, parameters and a sample response. The 7-day trial gives 100 requests with no payment method, which is enough to run a 50-barcode test. Paid plans start at €19 per month for 2,000 requests on the pricing section.

Without an account you can validate identifiers with the barcode validation tool and normalize formats with the GTIN converter. You can also preview a real result on a public page such as this lookup. The API documentation is the reference for every route.