Start from the shift, not the feature list
Walk one Friday order through the demo: table to kitchen to pass to bill. If any hop needs a workaround in the demo, it will need ten on a real night.
One system or five subscriptions?
A menu app from one company, a KDS from another and a POS from a third gives you seams, and every seam is somewhere an order can fall through. An end-to-end system (guest app, POS, KDS and dashboard on one login) removes them. We built Zervoo that way on purpose.
Demand zero commission
Any per-order percentage is a tax on growth. Flat per-venue pricing is predictable and doesn’t punish your best nights.
Check the hardware bill
Good software runs on phones and tablets you already own. Proprietary terminals are a lock-in strategy wearing a hardware costume.
Ask what happens when you outgrow it
Sooner or later every floor needs something the product doesn’t do, so ask the vendor now whether they’ll build it. Zervoo builds custom solutions, either inside the platform or alongside your current stack, as well as custom-branded guest apps in your colours.
Support is a feature; test it
Raise a ticket during the trial and time the answer. On a Friday night, support that answers Monday is decoration. Look for same-service resolution. To compare costs, start with published restaurant software prices in India, and for the kitchen, KDS vs KOT.
Walk a Friday order through it with your real menu. Twenty minutes, no card needed.
Book a demoasked first.
How long should rollout take?
For QR ordering + KDS on existing hardware: under an hour. Weeks-long rollouts signal complexity you’ll live with forever.
Should the system replace my POS?
Ideally the system includes one, because that’s one less seam. Zervoo’s POS runs in the browser on your existing till.