About upc.dev

Product Intelligence Infrastructure

The Thesis

Barcodes are the DNS of physical goods. A UPC or EAN is a globally-unique identifier assigned at manufacture — the same way a domain name identifies a server on the internet. Every product sold in retail carries one. Every scan generates data. Every listing references it.

But unlike DNS, there's no canonical registry a developer can query. Product data lives scattered across marketplaces, regulatory agencies, open databases, legal filings, consumer forums, and first-party catalogs. Each source has a partial view. None of them agree on formatting, completeness, or truth.

upc.dev is the canonical layer. One lookup, one barcode in, structured intelligence out — name, brand, category, ingredients, nutrition, pricing history, recall status, regulatory signals, risk scoring.

What We're Building

A product intelligence API for developers, brand teams, compliance professionals, and researchers. 10M+ canonical product records aggregated from dozens of authoritative sources. Every data point timestamped. Every change captured as a signal.

Canonical doesn't mean "the most recent answer." It means the resolved identity — the product as it exists across sources, normalized, deduplicated, and versioned. When a brand changes packaging, when a recall is issued, when a listing appears on a new marketplace, a signal lands and the canonical record updates.

Why Intelligence, Not Just Lookup

Barcode lookup APIs return a name and an image. Product intelligence infrastructure returns context: is this product safe? is it priced fairly? is it authentic? is the supply chain compliant? has it been recalled? is there active litigation? does the GS1 prefix match the claimed country of origin?

These are questions no single source can answer on its own. The value is in the join — and the join is hard enough that most teams don't build it themselves.

Trust

We don't publish our source list (competitive moat). We don't publish SKU-level counts at the brand level (per-SKU noise misleads). We do commit to:

• Canonical integrity: one record per identified product, not one per marketplace listing
• Signal history: every change is captured and timestamped; nothing is silently overwritten
• Origin independence: no source can single-handedly drive a risk flag; we require corroboration across independent data streams
• Audit trail: authenticated requests can see the full signal chain that produced any canonical field

For Developers

The public API is JSON-first, authenticated via API key. Endpoints for product lookup, search, barcode validation (including GS1 decode), and signal history. Full schema at /openapi.json. Free tier for experimentation, paid tiers for volume — see pricing.

Contact

For API partnerships, brand-protection inquiries, or compliance workflows: reach out via upc.dev.

Last updated: April 2026