Here’s another entry in my ongoing series about payment apps and POS systems, otherwise known as “please, for the love of all things, take my money.”
This time, it’s about Zizzi.
We like Zizzi. Pretty good for a chain, consistent, close to home. The kids enjoy it, and I’m a sucker for a solid lasagna, so it works.
A while back, they introduced the option to order right from your table. You scan, browse the menu, and place your order online. In theory, convenient. In reality, not so much.
The first time we tried it, the whole thing collapsed like a bad soufflé. I think we spent 15 minutes trying to order before admitting defeat. Then the waiter came over, who, to their credit, also had trouble with the system. When the staff can’t make the app work, that’s not a user problem. That’s a “this is broken” problem. Logging in, confirming the order, something always failed. After twenty minutes of tech support cosplay, we gave up and just ordered the old-fashioned way.
Since then, I’ve avoided the “order at the table” gimmick. My appetite doesn’t need a debugging session before pasta.
That said, Zizzi redeems itself with their payment setup. That’s where they actually get things right. You scan the QR code, pay with Apple Pay (no logins, no fuss), and it just works. Recently we had one of the kids’ birthday dinners there, large table, chaos, cake, the usual. The service was great, and paying through the app was quick and clean.
There was one hiccup: the app didn’t let us add a tip. And we really wanted to, because the staff had gone above and beyond with the birthday stuff. We ended up having to flag someone down, who couldn’t add it either. Apparently, the built-in service charge meant we were done. Nice in theory, but awkward when you actually want to leave extra.
Still, credit where it’s due. Ordering? Fail. Paying? Solid.
Zizzi gets a mixed review from me, half frustration, half appreciation. The tech that takes my money works great. The tech that takes my order? Not so much.