Key takeaways
- Treat every new dish as a small project: develop, cost, test, train, set up, launch and review.
- Cost the dish with a recipe card before you set the price, and include garnish, sauce and packaging.
- Test it as a special for two to four weeks before it earns a permanent place on the menu.
- Review it after 30 days with sales, margin, prep time and customer feedback, then keep, change or drop it.
New dishes keep a menu interesting and give regulars a reason to come back. They also add complexity: another recipe for the kitchen to learn, more ingredients to stock, another button on the POS and another line in the menu engineering report. Many new items quietly underperform because they were added without a plan. This guide sets out a simple process for a new menu item launch, from the first tasting to the 30-day review, that works for a cafe, hawker stall or full-service restaurant.
Why a launch process beats “just add it to the menu”
When a new dish goes straight onto the menu, several things tend to go wrong. It is priced on a guess. Front-of-house staff cannot describe it. The kitchen makes it three different ways. The POS button sits in the wrong category, so sales reports lump it with something else. After a few weeks nobody knows whether it is working.
A launch process fixes this with a few checkpoints. Each step below has a clear output, so you know when you are ready for the next one. For seasonal and festive items, pair this process with our seasonal menu planning guide.
Step 1: R&D and tasting
Start with a reason for the dish. Good reasons include filling a gap your menu engineering analysis revealed (for example, no high-margin vegetarian main), using an ingredient you already buy, or answering repeated customer requests. “The chef wanted to try something” is fine too, as long as the dish is then held to the same tests.
During development:
- Use ingredients you already stock where possible, to avoid new suppliers and wastage.
- Check the kitchen can make it at peak. A dish that needs the only oven during the lunch rush will slow everything else.
- Taste with a small panel: the head chef, a manager, a server and, if possible, two or three regulars. Use a simple score sheet for taste, look, portion and value.
- Photograph each version so you can compare plating and agree the final look.
The output of this step is a final recipe with exact quantities, method, plating photo and target prep time.
Step 2: Cost the dish before you price it
Turn the final recipe into a recipe card with the cost of every ingredient, adjusted for yield. Our guide to standard recipe cards covers versioning and photos. Our recipe costing template shows how, including the lines people forget: garnish, sauces, oil, and takeaway packaging. Then set the price:
- Check the food cost percentage against your target for that category.
- Compare the price with similar dishes on your menu and nearby.
- Work out a delivery price separately if platform commission applies.
- Check how prices must be displayed. IRAS’s GST guidance for F&B explains when you may show GST-exclusive prices with a prominent statement and when takeaway or delivery-only items must show GST-inclusive prices.
If the margin does not work at a price customers will pay, change the recipe or portion now, not after launch.
Step 3: Test it as a special
Run the dish as a special or limited-time item for two to four weeks before it joins the permanent menu. This keeps the commitment low and gives you real sales data. During the test:
- Offer it at the price you intend to charge, not a discount, so the results are honest.
- Give it a proper spot: a table card, a line on the QR menu, a mention from servers.
- Track sales daily and ask servers to note what customers say.
- Watch prep time and any tickets that come back.
Decide in advance what “success” looks like, for example a minimum number sold per day and a food cost within target. It is much easier to drop a dish against a target you set before launch than against a feeling afterwards.
Step 4: Train front and back of house
Before the dish goes on sale, both teams need to know it. Our staff training checklist covers training in general; for a new item focus on:
- Kitchen: recipe card, plating photo, portion sizes, prep list changes, storage and holding times.
- Front of house: a two-sentence description, main ingredients and allergens, what it pairs with, and which customers it suits.
- Tasting: let every server taste it. Staff sell what they have eaten.
- Delivery: how it is packed, and any notes for the customer.
Record who has been trained. A dish launched on a Friday with half the weekend team untrained will get mixed reviews.
Step 5: Set up the item in your POS
The POS set-up decides whether you can measure the launch properly. Get these right before the first order:
- Category: put it in the right category so reports compare it fairly.
- Modifiers: spice level, add-ons and options, each with the correct price.
- Kitchen routing: send it to the right printer or kitchen display station.
- Recipe link: connect the item to its recipe so stock is deducted as it sells.
- Channels: decide whether it appears on dine-in, QR, kiosk, online ordering and delivery apps, and at what price.
- Time rules: if it is a lunch-only or weekend-only item, set that up so staff cannot sell it at the wrong time.
ChaChaCha supports custom modifiers, kitchen display routing by station, recipe-level stock deduction and recipe costing per menu item, and puts the item on QR ordering and the online ordering page from the same menu. Ask us to confirm how to schedule items by time of day for your set-up.
Step 6: Launch and promote
Once the dish is ready, tell people. Simple, low-cost options:
- A photo and short caption on your social media, using the same photo as the menu.
- A table card or counter sign for dine-in customers.
- Feature the item at the top of the QR menu for the first few weeks.
- A WhatsApp message or voucher to loyalty members who have opted in.
- Servers suggesting it to regulars.
Use the same photo everywhere, so customers recognise the dish on the table card, the QR menu and the delivery app. Keep the launch message short: what the dish is, why it is worth trying, and whether it is available for a limited time.
Avoid launching several new items in the same week. It confuses customers and makes it impossible to tell which change caused a shift in sales.
Step 7: The 30-day review
After 30 days, pull the numbers and decide. Look at:
| Measure | Where to find it | Question to ask |
|---|---|---|
| Units sold per day | POS item sales report | Did it meet the target you set? |
| Food cost % | Recipe costing, supplier invoices | Is the actual cost close to the recipe card? |
| Contribution margin | Price minus food cost | Does it earn more or less than the dish it replaced? |
| Effect on other items | Category sales | Did it add sales or just take them from similar dishes? |
| Prep time and returns | Kitchen display times, voids | Is it slowing service or coming back? |
| Feedback | Staff notes, reviews | What do customers say, unprompted? |
Then choose one of three outcomes: keep it on the permanent menu, change it (price, portion or recipe) and test again, or drop it. Record the decision and the reason, so the next launch learns from this one. Add the dish to your regular menu engineering review.
A launch timeline you can copy
- Weeks 1 to 2: develop and taste; finalise the recipe and plating photo.
- Week 3: cost and price; set up the POS item, recipe and modifiers; train staff.
- Weeks 4 to 7: run as a special at full price; track daily.
- Week 8: 30-day review; keep, change or drop.
Adjust the timings to suit your kitchen, but keep the order. If you want help setting up items, recipes and reports on your POS, talk to ChaChaCha.