Menu and recipes stay in this browser. Not uploaded. Not encrypted.
What is Restaurant Menu & Recipe Cost?
Build categories, prices, English/Bangla labels, variants and add-ons. Dishes are available or not — they are not Retail-style finite prepared portions unless you set optional limits. Ingredient purchases are cash out. Recipe COGS applies only when costing is on and real averages exist. Data is fst-restaurant, isolated from Tea Shop and Retail. Workspace Quick Start may add empty category names only — no fake orders.
Key features
- Categories, items, variants, add-ons, EN/BN labels
- Available / unavailable flags
- Optional ingredients, purchase prices and per-serving recipes
- Menu PDF and local backup
- Separate IndexedDB from Retail and Tea Shop
Popular uses
- Write tonight's board without claiming live kitchen sync
- See a margin only after real ingredient averages exist
- Print a menu PDF for the table
Supported formats
Menu PDF and JSON backup. Not a live public website menu unless you export QR separately.
Troubleshooting
- Margin is missing Enter ingredient costs and enable costing; otherwise we will not invent it.
Also known as: Food menu builder, Recipe costing, Restaurant item list.
How it works
- Add categories and menu items with sell price; mark available or unavailable.
- Optionally add ingredients, purchase prices and a recipe per dish for cost and margin.
- Export a menu PDF or backup. Data stays in this browser (fst-restaurant).
FAQ
Is dish stock finite like Retail?
No. Menu items use availability (and optional prepared limits you configure). Ingredient stock is separate and optional.
Are purchases counted as COGS?
No. Ingredient purchases are cash out. Recipe COGS applies when you complete an order with costing enabled and real ingredient averages.
Same database as Tea Shop or Retail?
No. Restaurant uses fst-restaurant IndexedDB.