1 · Restaurant Details

API key (stored only in your browser)

Enter a few details so MenuProof can build your menu accurately. ?How credits work.
Every menu is capped at 2,000 credits — guaranteed. A simple menu (food truck, café) might use ~750; a dense fine-dining menu would cost more but stops at 2,000. You never overpay. Whatever you don't use stays in your wallet for the next menu.

Restaurant name *

Cuisine *?Why this matters.
Cuisine tells FIRE AI what to expect: an Italian menu has antipasti and primi; a Mexican menu has barbacoa and rajas. Picking the right one sharpens the read on ambiguous item names and groups dishes into the right departments automatically.

Pick "Other (specify)" if nothing fits.

Restaurant type *?Different from cuisine.
Cuisine = what they cook. Type = how they serve it. A pizzeria, a fine-dining Italian spot, and a counter-service Italian deli all serve Italian — but their menus parse differently (sit-down expects courses; QSR expects combos; pizzeria expects size-by-toppings grids). Picking the right type sharpens layout reads + modifier choices.

🍸 Does this place serve drinks? (tap to set — optional)

Pick what they pour and the AI builds the right drink buttons (pours, sizes, mixers). Leave both off for a food-only place.

🍷 Beer & Wine 🥃 Full Bar + liquor & cocktails

Your API key never leaves your browser. It's saved only in this tab's localStorage. Don't paste this URL anywhere — anyone who opens the tab on your machine can see the key.

2 · Upload Menu ?Best file types, in order:
• PDF (cleanest read — vector text)
• Sharp photo / scan (≥1500px wide, well lit, in focus)
• HEIC from iPhone (auto-converted)

What hurts accuracy: blurry photos, heavy shadows, glare on glossy menus, rotated pages. If a page reads badly you can re-shoot just that page and drop it back in — already-parsed pages won't be redone.

Drop a PDF or menu photos here — or click to upload PDF, JPG, PNG, or HEIC. Photos: good light, lay it flat, fill the frame. Add more pages anytime.

On a phone? Snap each page — it uploads straight in.

?Builds your whole menu in the cloud.
FIRE AI runs on our servers — it reads every uploaded page, builds the item list with departments + pricing, and suggests modifier groups (sizes, add-ons, prep style). You can keep working or close the tab — when it's done it lands under Resume Saved Menu (top right, green dot) and is saved to your account automatically.

Cost is capped at 2,000 credits per menu — guaranteed. A simple menu uses less; a dense one stops at 2,000. You never overpay. ?Save where you are — two places at once.
Saves the parsed menu + your edits to your account (☁️ cloud — open it on any device) AND this browser (💾). Come back later and hit Resume Saved Menu (top right) to pick up exactly where you left off, even on another device. Doesn't cost credits. ?Save this, then start fresh.
Saves the current menu to your account (☁️ cloud) + this browser — like Save Progress — and clears the workspace so you can start a new restaurant from scratch. Use this when you've finished one job and the next is unrelated.

📝 Manager's handwritten notes — a.k.a. the Chicken Scratch Decoder™ 🐔

Add photos of handwritten manager notes. You'll review every suggested change before anything is applied.

⚠️ Handwritten notes USE EXTRA CREDITS. How well it reads depends on the handwriting — and let's be honest, most restaurateurs write in legendary chicken scratch 😂. Drop a clear, well-lit photo of the note in with your menu and we'll do our best to decode it.

I have handwritten manager notes to cross-reference

3 · Review and Download

Check the menu, fix anything needed, then download your POS file. MenuProof gets you ~90% there — clean, flat menus your staff can actually run; your tech handles the final on-site tweaks.

?Pick the POS BEFORE you export.
The export format is tuned for each POS's bulk importer — column names, sheet layout, and modifier mapping are all different. Pick the wrong one and the import will reject or load wrong.

Shift4 Dine, Clover + SpotOn are verified against the live importer. Square is in BETA. ?The main export.
This is the file you upload to your POS's bulk importer. Fully populated — items, modifier sets, departments, taxes — drop it straight into the POS and it loads. (Details: open the "About the POS file" panel below the table.)

More options — touch me to make me pop 👀

?Reorder all your departments fast.
Opens a compact popup with just the department list (no items) — drag the ⠿ handle or use ▲ ▼ to put them in the order you want, and a search box to find one in a long menu. Great for big menus. Changes apply instantly. ?Add a category by hand.
Use this if FIRE AI missed a category (e.g. you want a separate "Kids" or "Holiday Specials" group) — adds an empty department you can fill in by clicking + item under it. ?See what's in the .xlsx before downloading.
Opens a popup that lists every sheet + row that will be in the export. Lets you spot-check item counts, modifier sets, prices, taxes — without leaving the app or opening Excel. ?CSV alternative.
A flat one-row-per-item CSV — useful if your POS isn't supported above, or if you want a quick spreadsheet to scan. Not pre-mapped to any POS's import template; you'd map columns yourself.

Same buttons as top — hover the ones up there for what each does.

About the POS file

16 sheets matching the Shift4 Dine / Lighthouse bulk-import template — populated for you: Items, Modifier Sets, Modifiers, Map Modifier Sets, Map Items, Department, Revenue Classes, Taxes, Map Item Taxes, plus empty stubs for the rest. Modifier sets are deduplicated by structural identity (so a "Dressing" group reused on every salad becomes one shared set), and every item is pre-tagged with Sales Tax so you don't do that row-by-row. Drop the file straight into Lighthouse's Menu → Import.

About CSV export

Fallback for spot-pasting individual cells. One row per modifier option. Columns: Department · Item Name · Description · Price · Modifier Group · Option · Price Delta · Required · Default.