Most restaurant owners think menu language doesn't impact their bottom line - but data shows regional dialect words can shift both pricing power and order frequency by 15-25%. Guests order familiar-sounding dishes more often, yet they'll pay premium prices for 'authentic' local specialties. The trick lies in measuring which approach actually drives your margins up.
Why language use affects your margin
The name of a dish partly determines what guests expect to pay. A 'farmer's kale mash' suggests a different price than 'traditional Groningen kale with sausage'. Dialect names can work two ways:
- Positive: Authentic, local, justifies higher price
- Negative: Unknown, confusing, lower conversion
Measure ordering behavior per dish name
To measure the impact, you need data on what guests order. Compare the same dishes with different names over different periods. This is the kind of thing you only learn after closing your first month at a loss - small changes in menu psychology can make or break your food cost targets.
💡 Example:
Restaurant in Limburg tests two names for the same dish:
- Month 1: "Sour meat with fries" - €16.50 - 45 sold
- Month 2: "Limburgian sour meat with fries" - €18.50 - 52 sold
Impact: +€2 per portion × 52 = €104 extra revenue, +15% sales
Calculate the margin impact per dish
For each dish with an adjusted name, you calculate:
- Old situation: Number sold × (old price - cost price)
- New situation: Number sold × (new price - cost price)
- Difference: New margin - old margin
💡 Calculation:
Sour meat example worked out further:
- Cost price per portion: €5.50
- Old margin: 45 × (€16.50 - €5.50) = €495
- New margin: 52 × (€18.50 - €5.50) = €676
Difference: €676 - €495 = €181 extra per month
Factors that determine the impact
Not every dialect word works equally well. These factors influence the result:
- Familiarity: How well-known is the word among your guests?
- Positive association: Does the word evoke something delicious/authentic?
- Location: Does it fit where you're located?
- Target audience: Local guests vs. tourists react differently
⚠️ Watch out:
Always test with a limited number of dishes first. Too many dialect words can make your menu confusing, which actually costs you sales.
Set up an A/B test for reliable data
For reliable results, you test systematically:
- Week 1-2: Original name
- Week 3-4: Dialect/regional version
- Week 5-6: Back to original (to rule out seasonal effects)
Measure per period: number sold, average price, customer satisfaction with the dish.
💡 Practical example:
Café in Brabant tests "Sausage roll" vs "Brabant sausage roll":
- Regular name: 28 sold at €4.50
- Brabant name: 35 sold at €5.25
- Cost price: €1.80 per piece
Margin impact: (35 × €3.45) - (28 × €2.70) = €45.15 per week extra
Calculate long-term impact
Once you've proven that a name change works, calculate the annual impact:
- Per week: Extra margin from name change
- Per year: Weekly margin × 52 weeks
- Seasonal adjustment: Account for quiet/busy periods
Don't forget to include costs: printing new menus, informing staff about the changes.
How do you calculate the margin impact of regional dialect words? (step by step)
Choose test dishes and measure baseline
Select 2-3 dishes with potential for regional names. Measure for 2 weeks: number sold, average price, total margin per dish. This becomes your comparison baseline.
Test new names and measure results
Change the names to regional versions and measure the same figures again for 2 weeks. Make sure other factors stay the same: price, ingredients, position on the menu.
Calculate the margin impact per dish
Compare old vs new margin per dish: (new sales × (price - cost price)) - (old sales × (price - cost price)). Calculate this through to monthly and annual revenue for full impact.
✨ Pro tip
Track your 3 highest-margin appetizers over 8 weeks - if regional naming boosts their order frequency by just 12%, you've captured the biggest profit impact without touching your labor-intensive mains.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Can I use regional dialect words if I'm not from that region?
That usually doesn't work well. Guests quickly notice if something isn't authentic. Focus on words that fit your location and background, or use standard Dutch terms with local context.
How long should I test before I switch permanently?
At least 4-6 weeks total: 2 weeks old name, 2 weeks new name, 2 weeks verification. This filters out random fluctuations and gives you reliable data.
What if sales go up but I can't raise the price?
You still benefit from higher revenue on the same dish. More sales of profitable dishes improves your overall margin, even without a price increase.
Should I convert all dishes to regional dialect at once?
No, that's risky. Test 1-2 dishes first, measure the impact, then gradually expand. Too many dialect words can make your menu confusing.
How do I measure this if I don't have a cash register system that records per dish?
Keep track manually of how many of each test dish you sell, for example with tally marks on paper. It takes time but gives you the data you need for a good calculation.
Do seasonal dishes respond differently to dialect naming than year-round items?
Yes, seasonal specialties often see bigger price premiums with regional names since guests expect authenticity from limited-time offerings. Test these during their peak season for maximum impact.
How do I account for staff confusion when calculating costs?
Factor in 2-3 hours of training time per server at their hourly wage, plus any mistakes during the first week. Most dialect name changes pay for training costs within 10-14 days if the margin lift is significant.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Engineer your menu for maximum margin
Menu engineering combines popularity with profitability. KitchenNmbrs gives you the data to strategically design your menu. Test it free for 14 days.
Start free trial →