Cinepod
Online booking for private theatre screens.
- Client
- Cinepod Private Theater
- Year
- 2026
- Scope
- Booking website, Backend API, Payments, Notifications
- Stack
- Next.js, NestJS, PostgreSQL, Redis, BullMQ, Razorpay, Amazon S3, Amazon SES, WhatsApp Cloud API
(01) The problem
What had to work.
Cinepod rents themed private screens for birthdays, anniversaries and other celebrations. Each booking is a 90-minute slot on one screen, with a package, a cake and add-ons such as decorations and videography.
The pricing has real rules: extra guests above a free threshold, a flat decoration charge, a discount when a cake comes with a package, and a fixed advance to hold the slot. The booking had to get all of that right online, every time.
- Screens, each with its own slots
- 3
- Packages
- 9
- Cakes
- 32
- Add-ons
- 41
(02) What we built
Built for the way they actually work.
- 01
A booking flow in one pass
Screen and slot, package, guest details, cake and add-ons, terms, a one-time code to sign in, then payment. Each screen keeps its own schedule of slots.
- 02
A ₹750 advance through Razorpay
The advance reserves the slot online, and the balance is paid at the venue. Coupons and a waitlist for full slots are built in.
- 03
A backend for the whole business
Beyond bookings, the API covers leads, staff attendance, invoices, expenses, reports and an audit log of every change.
- 04
Messages where customers are
Confirmations go out by email and WhatsApp, and customers can sign in with a code sent on WhatsApp.
(03) Where it stands
The result.
The customer booking flow was verified end to end in a real browser, from the home page to payment, against the real catalogue.
The staff back office is the next phase.