Memory ceiling
60 items memorised in week 1 fade by week 8. No human memory survives every shift.
A QR menu that reads the basket, the time and the customer, then pushes the perfect upsell on every order. Sits on any POS.
Seven structural reasons it leaks. None of them your team's fault.
60 items memorised in week 1 fade by week 8. No human memory survives every shift.
Pooled service charge, hourly pay, no commission. No personal upside for pushing the RM14 cheesecake.
Train the menu fully, the team moves on for RM200 across the road. Cycle restarts.
Your menu doesn't know it's 9pm. With 4 lava cakes left. And it's raining.
Your waiter speaks two languages well. The room speaks four. The special in the third never gets explained, so 30 to 40% of the table orders safe.
The 90 seconds the upsell matters are the 90 seconds the floor is slammed. Nobody has a hand free to suggest the side.
Morning crew pushes the croissant. Night crew forgets. Your revenue shouldn't depend on who clocked in.
Three jobs. Perfect timing. Every language. Every check. Automatic.
Reads the basket. Reads the time. Reads the history. Surfaces one suggestion that actually converts.
Flag "push this week". Live on every order, every outlet, instantly. No table tents. No briefings.
Sold out items vanish. Breakfast hides at 11am. Margin movers up top when the rush hits.
Real app. Swipe through 7 live scenarios.
Order an Eggs Benedict at 9:42am, the system surfaces White Coffee. 89% accept rate on that exact basket. One tap to add, no staff awkwardness, no scripts.
Customer adds a coffee and a pastry, banner appears: "Save RM3 with the combo." One tap swaps two lines for one pre-priced combo SKU. Waiter rings the combo through the POS once.
Cart crosses RM50 - a free Almond Croissant drops into the order at RM0. Your waiter rings it through the POS like any normal line. No code, no voucher, no math at the counter.
At 3pm on a Tuesday a "Happy Hour Drinks" category appears with discounted twin SKUs. Window closes at 5pm and the category vanishes. Live countdown on every order.
Owner hits "start flash". A countdown banner appears on every active session. A pre-priced Flash category becomes visible. When the timer hits zero, the category vanishes.
After basket is built, customer spins once. Lands on "Nasi Lemak for RM5 (regular RM12)". Tap to add, tap to skip. Owner sets prize conditions and pricing.
When OpenWeatherMap says it's raining at the outlet, "Rainy Day Specials" goes live with pre-priced SKUs at a discount. Stops raining, category hides. Zero merchant input.
Here's exactly how an order gets from the customer's phone to your kitchen. No integration, no re-platforming, no magic.
Scans, sees the menu, and gets the perfect upsell. Builds the whole basket on their phone.
Records the sale, fires the ticket to the kitchen. Same till, same flow. MenuBase never touched it.
Here's what changes, and what doesn't.
Same POS, same till, same receipt printer. Your team keeps ringing orders the way they do today. The only new thing is the customer's QR menu, and it runs on their phone.
We build the menu, generate the QR codes, train your team in one shift. New hires onboard in under 30 minutes.
The screen carries every special, every modifier, every weekly promo. Your team does the human bits: regulars by name, read the table, handle the curveballs.
Happy hour, threshold rewards and smart upsell live on your menu day one. Most venues hit an 8 to 14% AOV lift by end of month one.
They scan the QR, the menu opens in any browser. No download, no login, no email gate. Loads in under 2 seconds on 3G.
The customer picks their language once. Every special, modifier and promo travels in it. Your team stops being a three-language interpreter.
Monthly billing, no lock-in, no setup fee. Full data export whenever you want. If it doesn't lift your AOV, you leave. The risk sits with us.
MenuBase exists because of a frustration every F&B operator lives: you train a team to know the menu and sell the specials, and six months later they're gone. The menu knowledge leaves with them.
MenuBase was built to move that knowledge off your staff and into the screen, so turnover stops costing you sales. Every shift runs like your best one, no matter who's on the floor.
Before building, we sat with café, kopitiam and mamak operators across KL and Penang. The same patterns came up every time, the problem we built MenuBase to fix.
"Our team takes orders fine. They can't sell specials in EN or Mandarin. Customer nods, orders the usual. Money on every table."
"Scripts. Role-plays. Bonuses. Nothing stuck. By the time they get it, they've moved on."
"Every Sunday I brief new hires. By Monday someone else is on shift. I'm running a kopitiam, not a training company."
"I print the special, staple it to the menu. By Friday night nobody mentions it. The poster may as well not exist."
"Lunch rush, my team is drowning. Nobody has ten seconds to suggest the add-on. We lose the upsell exactly when the volume is there."
"Morning shift pushes the combo, night shift forgets. My revenue swings on who's rostered that day."
Most cafes leave 8-12% on the table. Move the sliders. See your uplift live.
Send your menu. We model the uplift on your real basket. No new hires, no scripts, no briefings.
The food, the room, the regulars - your team's job. The systematic upsell on every check - ours.