Israeli Restaurant Operations

• Wolt: Supports rich category structures and modifier groups. Use detailed descriptions. Photos are critical for conversion.
• 10bis: Simpler menu structure. Keep descriptions concise. Corporate lunch customers want clear portions and pricing.
• Mishlocha: Category-based with combo support. Consider building combo deals (מנה + שתייה + תוספת).

Step 2: Calculate Pricing with Commission Awareness

Help set menu prices that maintain target margins after platform commissions:

Commission Rates by Platform:

Pricing Formula:

Target Net Revenue = Food Cost + Labor Cost + Overhead + Desired Profit
Menu Price = Target Net Revenue / (1 - Commission Rate)
Price with VAT = Menu Price * 1.18

Example Calculation: A schnitzel plate with food cost of 18 NIS, target margin of 60%:

• Target net revenue: 18 / (1 - 0.60) = 45 NIS
• Price on Wolt (30% commission): 45 / (1 - 0.30) = 64.3 NIS, round to 65 NIS
• Price on 10bis (12% commission): 45 / (1 - 0.12) = 51.1 NIS, round to 51 NIS
• Price on Mishlocha (20% commission): 45 / (1 - 0.20) = 56.3 NIS, round to 56 NIS

Many restaurants set a single price across platforms and absorb the margin difference, or set slightly higher prices on higher-commission platforms. Help the owner decide which strategy fits their business.

Delivery Fee Considerations:

• Some platforms charge the restaurant for delivery, others charge the customer
• Factor delivery-related packaging costs (containers, bags, utensils): typically 3-8 NIS per order
• Minimum order amounts vary by platform and affect average order value

Step 3: Draft Review Responses in Hebrew

Help draft professional, warm Hebrew responses to customer reviews on delivery platforms:

For positive reviews (4-5 stars):

שלום [שם], תודה רבה על המילים החמות! שמחים שנהנית מ[המנה/החוויה]. מחכים לך בהזמנה הבאה 🙏

For negative reviews (1-3 stars) about food quality:

שלום [שם], תודה שהקדשת זמן לשתף אותנו. מצטערים לשמוע שהחוויה לא עמדה בציפיות. בדקנו את הנושא עם הצוות שלנו ו[פעולה שננקטה]. נשמח להזמין אותך שוב ולהוכיח שאנחנו יכולים טוב יותר. אפשר ליצור קשר ב-[טלפון] ונשמח לתקן את הרושם.

For negative reviews about delivery time (not the restaurant's fault):

שלום [שם], מצטערים על העיכוב. המנה יצאה מהמטבח שלנו בזמן, אבל לצערנו אין לנו שליטה על זמני השליח. העברנו את המשוב לפלטפורמה. נשמח לראות אותך שוב.

For negative reviews about wrong/missing items:

שלום [שם], מצטערים מאוד על הטעות. לקחנו את זה לטיפול ושיפרנו את תהליך הבדיקה שלנו לפני שליחה. נשמח לפצות אותך בהזמנה הבאה. צרו קשר ב-[טלפון].

Response guidelines:

• Always respond within 24-48 hours
• Never argue with the customer, even if the complaint seems unfair
• Keep responses under 500 characters (platform limits)
• Offer a concrete resolution, not just "we're sorry"
• Include a phone number for direct contact on serious complaints
• Match the customer's language (if they wrote in Hebrew, respond in Hebrew; same for English or Arabic)

Step 4: Compare Delivery Platforms

Help restaurant owners decide which platforms to join based on their restaurant type and location:

Platform Comparison:

Decision framework by restaurant type:

• New restaurant, urban area: Start with Wolt for visibility, add 10bis if near offices
• Established restaurant, loyal base: Mishlocha (lower commission) + Wolt for new customers
• Near office buildings/industrial zones: 10bis is a must (corporate meal benefits)
• Small town/periphery: Mishlocha often has better coverage outside Tel Aviv/center
• High-end restaurant: Consider Wolt only, where presentation and branding tools are best

Important note about 10bis dual model: 10bis operates as both a consumer delivery service and a corporate meal benefit platform (ארוחת עובדים). The corporate side has lower commissions but different order patterns (weekday lunches, set budget per employee). Make sure the owner understands which 10bis program they are joining.

Step 5: Analyze Food Costs and Menu Engineering

Help with recipe costing, margin analysis, and menu optimization using the menu engineering matrix:

Recipe Costing Template:

מנה: [שם]
מרכיבים:
  - [מרכיב 1]: [כמות] x [מחיר ליחידה] = [עלות]
  - [מרכיב 2]: [כמות] x [מחיר ליחידה] = [עלות]
  ...
סה"כ עלות מרכיבים: [סכום]
עלות אריזה למשלוח: [3-8 ש"ח]
עלות כוללת למנה: [סכום]
מחיר מכירה: [מחיר]
אחוז עלות מזון: [עלות / מחיר * 100]%
רווח גולמי למנה: [מחיר - עלות]

Target food cost percentages by restaurant type:

• Fast food / street food: 25-30%
• Casual dining: 28-35%
• Fine dining: 30-40%
• Delivery-only (cloud kitchen): 25-32%

Menu Engineering Matrix (Stars/Puzzles/Dogs/Plowhorses):

To classify menu items, you need two data points per item:

1. Popularity: Number of orders per week (or % of total orders)
2. Profitability: Gross margin per plate (selling price minus food cost)

Items above average on both metrics are Stars. Below average on both are Dogs.

Step 6: Plan Daily Operations and Scheduling

Help with operational checklists, food safety, and scheduling around Israeli calendar considerations:

Opening Checklist (רשימת פתיחה):

• Check ingredient freshness and expiry dates
• Verify delivery platform availability status is "open"
• Confirm staff assignments for the shift
• Check packaging supplies (containers, bags, utensils, napkins)
• Review previous day's reviews and respond to any unanswered ones
• Update any sold-out items on all platforms

Closing Checklist (רשימת סגירה):

• Mark restaurant as "closed" on all delivery platforms
• Record daily sales summary (total orders, revenue per platform)
• Log food waste
• Clean and sanitize kitchen per health regulations
• Update ingredient inventory
• Prep list for tomorrow

Food Safety Temperature Log:

Israeli Calendar Scheduling Considerations:

• Shabbat: Most restaurants close Friday afternoon through Saturday evening. Update platform hours weekly (sunset times change seasonally).
• Jewish holidays: Rosh Hashana, Yom Kippur, Sukkot, Pesach, Shavuot all require schedule changes. Some restaurants stay open on holidays, others close.
• Pesach: Major menu changes required (no chametz). Plan a separate Pesach menu at least 2 weeks ahead.
• Ramadan: Restaurants in mixed cities may see different order patterns. Late-night orders increase significantly.
• Memorial Day / Independence Day: Yom HaZikaron (low orders, somber mood) immediately followed by Yom HaAtzmaut (high demand, BBQ orders spike).
• Summer hours: Extended evening hours, more delivery orders after 9pm.

Staff scheduling tip: Israeli labor law requires different pay rates for Shabbat, holidays, and overtime. Factor this into staffing decisions for high-demand delivery periods.

Examples

Example 1: Setting Prices for a New Hummus Restaurant

User says: "I'm opening a hummus place in Ramat Gan, my food cost per plate is about 12 NIS. How should I price for delivery?"

Analysis:

1. Target food cost: ~30% (casual dining)
2. That means menu price should be around 40 NIS (12 / 0.30)
3. But delivery requires packaging (add 5 NIS cost, so total cost = 17 NIS)
4. With 30% food cost target: 17 / 0.30 = ~57 NIS (too high for hummus)
5. Adjust to 35% food cost: 17 / 0.35 = ~49 NIS

Platform pricing:

• 10bis (12% commission): 49 / 0.88 = 55.7, round to 56 NIS
• Mishlocha (20% commission): 49 / 0.80 = 61.3, round to 61 NIS
• Wolt (30% commission): 49 / 0.70 = 70 NIS

Recommendation: Price at 56 NIS on 10bis, 65 NIS on Wolt and Mishlocha. Ramat Gan has heavy office presence, so prioritize 10bis. Consider hummus + drink + side combos at 65-70 NIS to increase average order value across all platforms.

Example 2: Rewriting a Menu Description

User says: "My shakshuka listing on Wolt isn't getting orders. The description just says 'shakshuka with bread'"

Before:

שקשוקה עם לחם

After:

שקשוקה ביתית על האש
עגבניות טריות מבושלות לאט עם פלפלים קלויים, תבלינים מהמטבח ושתי ביצים עלומות. מוגשת עם לחם טרי מהטאבון. מנה ל-1.
תגיות: צמחוני | כשר

Why this works better: Sensory words (מבושלות לאט, קלויים, טריות), cooking method (על האש, מהטאבון), clear portion size, dietary labels for search filters.

Example 3: Handling a Negative Review About Cold Food

User says: "I got a 2-star review on Wolt saying the food arrived cold"

Draft response:

שלום, מצטערים מאוד שהאוכל הגיע קר. אנחנו שמים דגש על אריזה חמה ושליחה מהירה, אבל לפעמים עיכובים בדרך משפיעים על הטמפרטורה. נשמח לפצות אותך בהזמנה הבאה. צרו קשר ב-[טלפון] ונסדר את זה.

Additional advice to the owner:

• Invest in insulated packaging (costs 2-3 NIS more per order but reduces cold-food complaints significantly)
• Ask Wolt about their "preparation time" setting. If you mark dishes as ready too early, they sit waiting for a courier.
• Consider which dishes travel well and which don't. Fried items lose crispiness, soups travel great, salads should be packaged separately.

Gotchas

• Israeli delivery platform commission rates (Wolt 25-35%, 10bis 10-15%, Mishlocha 15-25%) differ significantly from US platforms like DoorDash or UberEats. Agents trained on US data will use wrong commission assumptions for revenue calculations.
• VAT in Israel is 18%, not 20% (UK) or 0% (some US states). Agents must use the correct rate when calculating net revenue from gross order values.
• Israeli restaurants commonly close Friday afternoon through Saturday evening for Shabbat. Agents scheduling operations, promotions, or report generation must account for this weekly downtime pattern.
• 10bis (Tenbis) operates as both a corporate meal benefit platform and a consumer delivery service. The commission structure and order flow differ between the two modes. Agents may conflate them.
• Hebrew menu item text requires RTL handling. When generating or editing menu descriptions, agents must produce valid Hebrew text without mixing LTR characters in ways that break display on delivery platforms.
• Menu prices in Israel are always in NIS (New Israeli Shekel). Agents should never convert to or assume USD/EUR pricing. Rounding should be to the nearest whole shekel (no agorot on delivery platforms).
• Kosher certification levels matter: "כשר" (regular kosher), "כשר למהדרין" (mehadrin/strictly kosher), and "כשר לפסח" (kosher for Passover) are all different. Mislabeling can cause serious trust and legal issues.

Troubleshooting

Problem: Menu description not generating orders

Cause: Generic descriptions, missing dietary tags, no photos, or poor category placement. Solution: Rewrite descriptions with sensory words and cooking methods (see Step 1). Add dietary labels. Ensure the item is in the right category. On Wolt, high-quality photos increase conversion by 30-50%.

Problem: Margins too thin after platform commissions

Cause: Pricing set without accounting for commission percentages and packaging costs. Solution: Recalculate using the formula in Step 2. Consider raising delivery prices 10-15% above dine-in prices (this is standard practice). Review food costs and look for ingredient substitutions that maintain quality.

Problem: Too many negative reviews about delivery

Cause: Issues with courier timing, packaging, or food that doesn't travel well. Solution: These are largely outside the restaurant's control. Use response templates from Step 3 that acknowledge the issue without accepting blame for courier delays. Invest in better packaging. Adjust "preparation time" settings so food doesn't sit waiting.

Problem: Unsure which platform to prioritize

Cause: Each platform has different strengths, and spreading too thin can hurt service quality. Solution: Use the comparison framework in Step 4. Start with 1-2 platforms, get operations smooth, then expand. Track orders and margins per platform monthly to see which actually works for your restaurant.

Problem: Food costs creeping up without price adjustments

Cause: Ingredient prices in Israel fluctuate frequently, especially produce, dairy, and meat. Solution: Re-cost your top 10 selling items monthly using the template in Step 5. Set calendar reminders to review prices quarterly. If a key ingredient rises more than 10%, adjust menu prices within a week.