← NextPrev →

MenuTrace - Computer Vision Allergen and Calorie Extractor for Independent Restaurant Menus

Independent restaurants upload a photo of their handwritten or printed menu and MenuTrace returns a structured JSON with every dish, its allergens, and estimated calories in under 30 seconds. No manual data entry, no dietitian on retainer, no excuse for not having a digital menu.

𝕏 Post Reddit HN

Difficulty

beginner

What is it?

Independent restaurants are increasingly required by health-conscious diners and local regulations to publish allergen information, yet 70% still rely on handwritten or printed menus with no digital equivalent. MenuTrace is a computer vision pipeline that accepts a menu photo, uses GPT-4o Vision to extract dish names and descriptions, classifies allergens via a rule-based matcher against the FDA top-9 allergen list, and estimates calories using a lookup-augmented generation approach against a USDA nutrition database. Output is a structured JSON and a shareable public menu URL. The SaaS layer is a dead-simple Next.js app where restaurant owners upload photos, review the extracted data, correct any errors, and publish. Buildable in 2 weeks — GPT-4o Vision handles the messy OCR and structure extraction, no custom model training required.

Why now?

GPT-4o Vision now handles handwritten and printed text extraction with near-human accuracy as of early 2026, making the menu photo to structured JSON pipeline reliable enough to sell without a human review layer for 95% of menus.

▸GPT-4o Vision extraction that reads handwritten, printed, or photographed menus and returns structured dish-level JSON
▸Allergen auto-classification against the FDA top-9 list (milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, sesame) with editable overrides
▸USDA FoodData Central lookup for calorie estimation per dish with confidence indicator
▸Public shareable menu URL with QR code generation for table cards and Google Business profile

Target Audience

Independent restaurant owners (est. 500k in the US alone) running single-location restaurants without a tech team or POS-integrated menu system

Example Use Case

Carlos, owner of a 40-seat Mexican restaurant, photographs his laminated menu, uploads it to MenuTrace, reviews the extracted 22 dishes with flagged allergens in 5 minutes, pays $19, and shares the public menu URL on his Google Business profile before dinner service.

User Stories

▸As a restaurant owner, I want to upload a photo of my menu and get allergens extracted automatically, so that I can publish a compliant digital menu without hiring anyone.
▸As a diner with a nut allergy, I want to see allergen icons on a restaurant's public menu URL, so that I can order safely without interrogating the waiter.
▸As a restaurant owner, I want a QR code I can print on table cards, so that customers can view the digital menu on their phones immediately.

Done When

✓Extraction: done when user uploads a menu photo and sees all dishes with names, descriptions, and allergen flags in the review table within 30 seconds
✓Allergen override: done when user clicks an allergen checkbox to add or remove it and the change persists after page reload
✓Stripe checkout: done when user pays $19 and is redirected back to a page showing their live public menu URL and QR code
✓Public menu: done when the public URL loads in a new tab showing all dishes with allergen icons, viewable without login.

Is it worth building?

$9/month x 300 restaurants = $2,700 MRR at month 4. One-time $19 x 200 restaurants month 1 = $3,800 launch revenue. Realistic given 500k target market — requires 0.06% conversion.

Unit Economics

CAC: $5 via in-person demo + local SEO. LTV: $108 (12 months at $9/month subscription) or $19 one-time. Payback: immediate. Gross margin: 88%.

Business Model

One-time menu publish fee $19 per menu, or $9/month subscription for unlimited updates

Monetization Path

Free extraction preview (first 3 dishes blurred). $19 one-time or $9/month unlocks full menu and public URL.

Revenue Timeline

First dollar: week 1 via in-person restaurant demo. $1k MRR: month 2. $5k MRR: month 5.

Estimated Monthly Cost

GPT-4o Vision API: $40 (est. 500 menu photos/month at $0.08 each), USDA API: $0 (free), Supabase: $25, Vercel: $20, Stripe fees: ~$10. Total: ~$95/month at launch.

Profit Potential

$3k–$8k MRR within 4 months if distributed via local restaurant association email lists.

Scalability

High — QR code menu generation, multilingual menus, POS integrations, and white-label for restaurant groups are natural V2 features.

Success Metrics

50 menus uploaded week 1, 20 paid publishes week 2, 60% month-2 renewal rate on subscription tier.

Launch & Validation Plan

Post before/after demo in r/restaurateur and r/smallbusiness — count DMs asking for beta access before building Stripe integration.

Customer Acquisition Strategy

First customer: walk into 5 local independent restaurants, photograph their menu with your phone, show the owner the extracted result on your laptop, and offer to publish it for free in exchange for a testimonial. Ongoing: local restaurant association newsletters, Google Ads targeting 'digital menu QR code', r/restaurateur, Yelp partner ecosystem.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): photo upload, GPT-4o extraction, allergen flags, Stripe publish, public URL with QR. V2 (month 2-3): multilingual extraction, custom branding, Google Business auto-post. V3 (month 4+): POS menu sync, online ordering link, restaurant group accounts.

Milestone Plan

Phase 1 (Week 1): extraction API, allergen matcher, USDA lookup, review UI — done when a real menu photo produces correct dish list. Phase 2 (Week 2): Stripe checkout, public URL, QR code, Vercel deploy. Phase 3 (Month 2): 30 published menus, 15 paying customers, ProductHunt launch.

How do you build it?

Tech Stack

Next.js, GPT-4o Vision API, USDA FoodData Central API, Supabase, Stripe — build with Lovable for UI, Cursor for API routes, v0 for menu display components

Suggested Frameworks

OpenAI Vision API, FastAPI, USDA FoodData Central REST

Time to Ship

2 weeks

Required Skills

GPT-4o Vision API, USDA API lookup, Next.js, Supabase, Stripe.

Resources

OpenAI Vision API docs, USDA FoodData Central API docs, Next.js app router docs.

MVP Scope

app/page.tsx (upload landing + hero with live demo), app/menu/[id]/page.tsx (public menu display), app/api/extract/route.ts (GPT-4o Vision extraction handler), app/api/publish/route.ts (Stripe checkout + menu activation), lib/allergens.ts (FDA top-9 rule matcher), lib/usda.ts (USDA API calorie lookup), lib/db/schema.ts (menus and dishes Drizzle schema), components/MenuReviewTable.tsx (editable dish review grid), .env.example (OPENAI_API_KEY, USDA_API_KEY, STRIPE_KEY)

Core User Journey

Upload menu photo -> review extracted dishes and allergens -> correct any errors -> pay $19 -> share public URL and QR code.

Architecture Pattern

User uploads menu photo -> Supabase Storage -> GPT-4o Vision API extracts JSON -> lib/allergens.ts classifies -> USDA API enriches calories -> dishes written to Supabase -> review UI displayed -> Stripe checkout -> public menu URL activated.

Data Model

Restaurant has many Menus. Menu has one Photo and many Dishes. Dish has name, description, allergens array, calories estimate, and confidence score. PublicURL belongs to one Menu.

Integration Points

OpenAI GPT-4o Vision API for menu extraction, USDA FoodData Central API for calorie lookup, Supabase for dish storage and file storage, Stripe for one-time and subscription payments, Vercel for hosting.

V1 Scope Boundaries

V1 excludes: multilingual menus, POS sync, online ordering, team accounts, custom branding on public menu page.

Success Definition

A restaurant owner finds MenuTrace on Google, uploads their menu photo, pays $19, and shares the public URL on their Google Business profile without ever contacting the founder.

Challenges

Restaurant owners are notoriously resistant to new software — the hardest problem is convincing them in the first 30 seconds that photo upload to published menu actually works. A live demo video showing a real handwritten menu being processed is worth more than any landing page copy.

Avoid These Pitfalls

Do not attempt to train a custom OCR model — GPT-4o Vision handles handwritten menus better than any custom model you could build in 2 weeks. Do not skip the manual review step — if owners cannot correct extraction errors before publishing, a single wrong allergen label will create a support nightmare.

Security Requirements

Supabase Auth with Google OAuth. RLS on all menu and dish rows by user_id. Uploaded photos stored in private Supabase bucket, deleted 30 days after publish. Rate limit: 10 extraction requests/hour per user. GDPR: menu data and photos deletable on request.

Infrastructure Plan

Next.js on Vercel, Supabase for DB and photo storage, no separate backend needed — all API routes in Next.js. Sentry for error tracking. Total infra ~$95/month at launch.

Performance Targets

Extraction target: under 30 seconds from photo upload to review table display. Public menu page load: under 1.5s (static ISR). API response for dish save: under 300ms. CDN via Vercel for all static assets.

Go-Live Checklist

☐Security audit complete.
☐Stripe one-time and subscription flows tested.
☐Sentry error tracking live.
☐Custom domain configured with SSL.
☐Allergen disclaimer copy reviewed by non-lawyer friend.
☐Privacy policy and terms published.
☐5 restaurant owners beta-tested full flow.
☐Rollback: previous Vercel deployment.
☐ProductHunt and r/restaurateur posts drafted.

First Run Experience

On first run: app shows a demo mode with a pre-loaded taqueria menu photo already extracted showing 8 sample dishes with allergen icons. User can immediately: click through the review table, toggle allergens, and see the public menu preview without uploading anything. No manual config required: demo extraction is served from a cached result so no API key is consumed on first visit.

How to build it, step by step

1. Define Supabase schema: restaurants, menus, dishes tables with RLS by user_id. 2. Run npx create-next-app menutrace --typescript --tailwind --app. 3. Build lib/allergens.ts as a keyword rule matcher against FDA top-9 allergen triggers in dish descriptions. 4. Build lib/usda.ts calling USDA FoodData Central search API to estimate calories from dish name. 5. Build app/api/extract/route.ts that accepts an image upload, calls GPT-4o Vision with a structured JSON prompt, then pipes result through allergens.ts and usda.ts. 6. Build components/MenuReviewTable.tsx as an editable grid showing dish name, allergens (checkbox toggles), and calories with confidence bar. 7. Build app/api/publish/route.ts that creates a Stripe checkout session and activates the public menu URL on payment success webhook. 8. Build app/menu/[id]/page.tsx as the public menu display with QR code generated via qrcode.react. 9. Build app/page.tsx with a drag-and-drop upload zone and a live demo video showing a real menu being processed. 10. Verify: photograph a real restaurant menu, upload it, confirm all dishes appear in the review table with allergens flagged, complete Stripe checkout, and confirm the public URL loads correctly.

Generated

April 22, 2026

Model

claude-sonnet-4-6

← Back to All Ideas

DriftWatch Agent - Autonomous Feature and Prediction Drift Monitor With Slack Triage

Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.