An 8-table cafe near Galata Bridge in Karaköy started July 2024 with a 67 TRY average ticket and ended December 2024 at 91 TRY — zero added marketing spend, pure menu engineering. Here is the month-by-month breakdown and which decisions actually moved the needle.
Baseline: July 2024
The cafe served roughly 82 guests/day, ticket 67 TRY, daily revenue ~5,500 TRY. Servers took paper orders, error rate 4-6 per week. The menu had 38 items, flat 25-95 TRY range, no "stars" highlighted.
Owner Burak had two complaints: "Customers buy a coffee plus a cookie and leave" and "Nobody sees the dessert menu". Hypothesis: menu order and price anchoring were subconsciously suppressing the ticket.
Changes by month
August: a premium dessert added — "Pistachio Tiramisu 145 TRY" — a decoy not meant to sell volume, just to make other desserts feel cheaper. Dessert category jumped from 12 to 24 sales/week immediately.
Sept-Oct: a set menu (Filter Coffee + Cheesecake = 78 TRY, vs 92 TRY separately) placed on the cover. 41 sets in September, 89 in October. November: a one-day pro photo shoot (8 items) uploaded to the QR menu. December: QR self-ordering launched — order errors fell to 0, servers just confirm with one tap.
- August: 67 → 71 TRY (decoy effect)
- September: 71 → 76 TRY (set menu)
- October: 76 → 82 TRY (set spreads)
- November: 82 → 87 TRY (visuals trigger appetite)
- December: 87 → 91 TRY (QR add-on prompts)
Results and lessons
After 6 months: +35% average ticket, guest count flat, errors dropped from 4-6 to 0, server tips up ~18% (no angry customers). Net: daily revenue 5,500 → 7,460 TRY, annualized gain ~715,000 TRY.
Key insight: the decoy is not meant to sell — it is meant to reprice everything else. The 145 TRY tiramisu sells 3-4 units a week and earns its keep purely through anchoring. Any cafe with basic menu literacy can replicate this.
FAQ
Does the decoy have to be a real item? Yes — if a guest orders it and you cannot serve it, you lose trust. Keep small stock and aim for 3-5 sales per week.
Does QR ordering make sense at only 8 tables? Absolutely — one wrong coffee costs ~25 TRY. 16-24 errors a month means 400-600 TRY savings plus servers reclaim table-side time.
How aggressive should set-menu discounts be? 12-18% below the sum. Big enough to feel like a deal, small enough to protect margin. In our case 92 → 78 TRY (15% off) cost only 4% in actual food cost.
Found this helpful? Share it.
Related articles
Why Digital Menus Increase Restaurant Revenue by Up to 30%
Studies show restaurants using digital QR menus see measurable increases in aver…
When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS
Most SaaS apps run a single line of code when a customer downgrades — but old fe…
JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers
Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…