Support
Answers before you go live.
Straight answers about ordering, plans, and how Zup keeps tenants safe.
- Ordering
- Plans & billing
- Hotels
- Security
Zup is a multi-tenant SaaS platform for restaurants, cafes, food courts, and hotels. Guests scan a QR code or open a public page to browse the menu and order. Staff run kitchens, payments, reservations, and operations from one dashboard.
Each table gets unique QR artwork with a cryptographically opaque token. Guests open the menu, customize items, and place dine-in orders. Staff control sessions, and QR tokens never expose database IDs or admin access.
Yes. Hotel modules are optional. Room-service orders and room-charge posting go through verified integration adapters — Zup never pretends a room charge succeeded without confirmation.
Growth and Enterprise plans support multi-branch restaurants with branch-specific menus, pricing, and staff access. Quotas are enforced on the server, not only in the UI.
Customer payments start with Razorpay behind a provider interface, plus cash and counter workflows. SaaS subscription billing is separate from restaurant guest payments.
Self-serve plans are pay-first: subscribe on Billing, then create your restaurant. Enterprise is available through sales. Account registration alone does not unlock venue creation.
Zup is multi-tenant with server-side membership checks. Tenant A cannot read Tenant B’s orders, menus, or staff. Every sensitive mutation validates the ownership chain.
Yes. Even when operational features are suspended after subscription expiry, access needed for billing history and data export is preserved per platform policy.
Didn’t find it?
Ask us anything about going live.
From QR rollout to hotel room service, we’ll help you get a clear path before you subscribe.