Grocery & retail
Barcode Food API for Grocery & Retail
A barcode food API for grocery and retail resolves a UPC or EAN to a name, brand, and macros per 100 g in one request. Open Food Facts is the fallback when the catalog misses.
The two-source design, verified local catalog plus Open Food Facts fallback, matters most in retail, where new products appear on shelves weekly. Misses return a clean 404 so your app can offer text search instead.
Why teams choose us
Built for your product's hardest problems
Shelf coverage is a moving target
Open Food Facts fallback extends coverage to newly released and regional products automatically.
Allergen answers must be fast
Ingredients and allergen lists arrive in the same scan response, no second lookup.
Kiosks and fleets share IPs
Per-account (not per-IP) rate limits keep in-store kiosks and app fleets behind NAT working.
How it maps
Product needs → API endpoints
Each need in your roadmap maps to a documented endpoint you can try in the playground today.
| Product need | Endpoint |
|---|---|
| Scan to product data | GET /search/barcode/{upc} |
| Search fallback on miss | GET /search/foods |
| Brand browsing | GET /foods/brands/ |
| Category navigation | GET /foods/categories/ |
Barcode Food API for Grocery & Retail: frequently asked questions
How well are non-US products covered?
EAN codes are supported and the Open Food Facts fallback has strong international coverage, which the local catalog extends over time.
Can in-store kiosks share one API account?
Yes, limits are per account rather than per IP, so a kiosk fleet works naturally. Size your plan to fleet-wide request volume.
Do scan responses include package sizes?
Serving metadata and package quantity appear when the source provides them; per-100g values are always present as the normalization baseline.
Ship nutrition features this sprint
Create a free account, explore the playground, and integrate with your stack using our framework guides.