100 Samosas: The Line That Started Yaha
August 15, 2026 · 6 min read
The order that wouldn't fit in a phone call
The phone rang during the Friday rush at a small halal spot in Toronto, and the woman on the other end wanted 100 samosas for a fundraiser the next morning. Behind the counter, twelve people were already waiting to order. Harun was working the till part time while finishing a master's degree, and he did the only thing you can do with a landline and a line out the door: he asked her to hold.
She held for six minutes. Then she called back twice more to confirm the count, because nobody had written it down anywhere she could trust. That's the actual failure mode of restaurant technology in 2018, and honestly still today for a lot of shops: not that the food is bad, but that the business has no way to take a real order from someone who doesn't want to stand in a line or babysit a phone call.
Harun decided to build a website.
Why restaurant technology usually fails on the floor, not on paper
Every restaurant online ordering software pitch sounds the same: put your menu online, take payments, done. What that pitch misses is where the failure actually happens, which is the ten seconds between a customer deciding what they want and someone on staff being available to take that order down correctly.
A PDF menu doesn't fail there. A call-in order fails there, constantly, because it depends on a human being free at the exact moment a customer is ready, and restaurants are almost never staffed for their busiest five minutes. The samosa order wasn't a menu problem. It was a workflow problem, and the existing restaurant ordering websites at the time were built by people who had never stood behind that counter during a rush.
Harun had. So the thing he built, salaamahut.com, wasn't trying to look impressive. It was trying to survive a Friday night.
What the first version had to get right
The obvious version of this project is a form: pick items, enter your name, submit. Harun didn't build that. He got obsessive about something most restaurant ordering websites still don't bother with, which is how few steps stand between a person discovering what they want and actually ordering it.
No account screen up front. No "create a password" wall before you've even seen the menu. A customer landed on the page, saw the food, added what they wanted, and started checkout. The account got created quietly, as a side effect of checking out, not as a toll booth before it. That sounds like a small design choice. It is actually the entire difference between a restaurant ordering website people finish and one they abandon halfway through, which is exactly what happens when digital ordering for restaurants treats registration as step one instead of a byproduct.
The second thing was verification and notification without hardware. The restaurant didn't buy a tablet, a printer, or a subscription to an enterprise point-of-sale system. An order came in, the customer got verified, and the restaurant got an SMS with the order on it. No installation appointment. No sales call. No monthly invoice for software the owner didn't fully understand. Just an order landing on a phone that was already in someone's apron pocket.
That constraint, no special hardware and no expensive deployment, wasn't a limitation Harun was working around. It became the whole philosophy.
The real unlock: one restaurant revealed a bigger problem
Salaamahut.com worked. Big pickup orders stopped requiring a hostage negotiation over the phone. But the more interesting realization came after it worked: the actual hard part, the checkout flow, the account creation, the SMS notification, the verification, none of that was specific to that one restaurant's menu. It was infrastructure. It could belong to any small business that wanted to sell online without paying a tax on it.
That's the moment a restaurant ordering website for one shop became the idea for a restaurant commerce platform for every shop. Instead of rebuilding this every time a shop owner had the same 100-samosa problem, the better answer was multi-tenant: one platform, one set of storefront tools, and every business gets its own real order page without needing its own engineer.
That platform is Yaha.
What Yaha looks like today
The pickup problem was the first one solved, and it's still core: a shop gets a real order page at yaha.app/r/their-name, orders land on a phone, and there's no monthly fee sitting on top of a thin margin. Salaama Hut, the restaurant where this all started, still runs its ordering through Yaha at yaha.app/r/salaamahut.
But the same underlying idea, remove the wait and the hardware, has stretched into problems Harun didn't originally set out to solve. QR code restaurant ordering came next: a code on the table, a customer orders and pays without flagging down a server who's already covering eleven tables alone. We wrote about the staffing problem that creates in One Server, Eleven Tables. Room service in small hotels works the same way, a code in the room instead of a phone call to a front desk that's also checking someone in.
Discovery mattered too. A shop can be the top result on Google Maps and still have nothing but a "Call" button, which is the same failure as the phone ringing during the rush, just moved onto a map. We covered how to fix that in How to Add an Order Online Button to Your Google Business Profile. Customer accounts, payments, and the mobile app all grew from the same original decision: never make the person paying do more work than the moment requires.
How fast a shop actually goes live
The other lesson from that first restaurant never left the product: speed to selling matters more than feature count. A shop signing up for Yaha isn't waiting on a hardware install, an integration with a legacy point-of-sale system, or a sales engineer's calendar. Setup happens in minutes, and a shop can be taking real orders the same day, which is a different category of promise than most restaurant online ordering software makes, because most of them are still selling a deployment, not a storefront.
That speed isn't a marketing line. It's the same constraint the samosa order created: if the system isn't ready before the next rush, it hasn't solved anything.
Why this still matters
Every part of Yaha's product philosophy traces back to a phone call that took too long. Checkout should feel like a natural extension of deciding what you want, not a separate chore. A restaurant shouldn't need to buy anything or wait for anyone to start selling online. And the point of restaurant technology was never the technology, it was the person on hold, and the person behind the counter who couldn't get to them fast enough.
If you run a shop and you've had your own version of that phone call, a line, a big order, a customer you couldn't get to fast enough, you can see what a real order page looks like at yaha.app/join.