Whole-Class Simulation · Instructor-Led

Build a restaurant
that survives lunch rush.

Four phases. Each one gates the next. The class configures a real POS, designs a QR menu, and handles a service crisis — and nothing advances until it would survive live service. Project this. Type the class's answers. Hit Validate together.

Outlet Initialization

Every config decision flows from who the outlet is.

A hotel is a property, not an outlet. Pick one revenue center and define it. A steakhouse and a vegan café have completely different POS trees.

Outlet / Concept Name

Primary Cuisine / Program

Target Demographic

POS Architecture

Petpooja / Oracle MICROS logic — the part the guest never sees.

Map 5 diverse items (≥1 customizable beverage, ≥1 customizable dish) into the backend: Major & Family Groups, forced modifiers, and food vs. beverage tax brackets.

The 5 items + their Major / Family group mapping Forced modifiers (size, milk, spice, protein, etc.) — and their sequence on the KDS Tax architecture (GST brackets — what rate applies to what?)

QR Menu UI/UX

The guest-facing flow. Scrolling behaviour dictates what sells.

Design the digital flow for revenue. What's at the top & why? How does the cross-sell fire? Build a real "Make it a Combo" bundle.

Menu hierarchy — what sits at the top, and why? Where does the low-ticket beverage go? The cross-sell prompt — text, dismissible?, fires at add-to-cart or checkout? The combo bundle — items, price vs. separate, new SKU or stacked discount?

Digital Feedback & Service Recovery

Contain the complaint privately — before it hits Google.

Design a 3-question micro-survey that fires on digital payment. Then: a guest rates 2★ — "the latte was melted & watered down by the time my bowl arrived." Draft the automated recovery. Twist: that complaint is the failure mode of the class's own combo coursing rule.

The 3 survey questions + format of each (thumbs / stars / free-text) The automated service-recovery message (acknowledge specific issue · concrete comp + its cost · contain privately · on-brand tone)

Simulation Complete

🏁 Certified.

The class built a backend that survives lunch rush, a menu that converts, and a recovery loop that closes the exact failure their own architecture was meant to prevent.

Build a restaurantthat survives lunch rush.

Outlet Initialization

POS Architecture

QR Menu UI/UX

Digital Feedback & Service Recovery

Build a restaurant
that survives lunch rush.