Skip to content
Code Craft — web development and digital marketing
Node.js App + Mobile Appv1.0.0

Quillnest Stays — Hotel Booking App

A hotel and guest-house booking platform you host yourself: nightly price calendar, seasons and rate plans, no overbooking, front desk with check-in and guest ID, commission ledger, REST API and an Expo mobile app

No reviews yetUpdated November 2026
Guest web app home with search by city, check-in, check-out, adults, children and rooms
Screenshots · 1 / 15

Everything included

  • Search by city, dates, guests and rooms
  • Nightly price calendar, seasons, weekend rates
  • Rate plans: add-ons such as breakfast, policies
  • No overbooking: every night taken in one transaction
  • Flexible, moderate and non-refundable cancellation
  • Front desk: arrivals, check-in, rooms, check-out
  • Guest ID stored privately, deleted after the stay
  • Owner panel: rooms, rates, staff, ledger
  • Admin: property approval and commission ledger
  • REST API and Expo app with guest and front-desk modes
How it works

From order to a live website

  1. 1

    Choose a package

    Code only, We set it up, or Customised. All prices are one-time.

  2. 2

    Pay securely

    Your download link is emailed once payment is confirmed and also appears in My Account.

  3. 3

    We contact you

    For setup packages we email within one business day for your cPanel / hosting login and domain.

  4. 4

    Live on your domain

    Your booking platform runs on your own Node.js hosting, with arrivals at the front desk, rates in the owner panel and the commission ledger in your admin.

A booking platform you own

Quillnest Stays gives you the code of a working hotel booking platform instead of paying a commission on every booking to someone else. Use it as the booking site for your own hotel or guest house, or as a small marketplace where property owners join, wait for your approval and pay you a commission. The download has four parts that share one database: the guest web app, a host panel at /host for owners and their front-desk staff, the admin panel at /admin, and a REST API used by the included mobile app. The name Quillnest Stays is a placeholder: change the name, logo and colours in Admin → Settings. The sample pictures are labelled illustrations, not photos of real places.

  • Guest web app built for phones
  • Host panel for owners and front-desk staff
  • Admin panel with a setup wizard for an empty install
  • REST API /api/v1 and an Expo mobile app

What guests do

Guests search by city, check-in and check-out dates, adults, children and rooms. Results show only room types free on every night of the stay, with the total. A property page has its pictures, amenities, house rules and a map, and lists each room type with every rate plan's total, its cancellation policy and how many rooms are left. A public price calendar shows the price of each night for a room type and rate. The booking page shows the night-by-night price, the tax and the fee the guest would pay if they cancelled, then takes the guest's details and payment method. In My trips the guest sees the status, a cancellation preview and a cancel button, the refund status, a UPI link and QR code to pay the property, an optional ID upload before arrival, the invoice or confirmation PDF, and after check-out they can write one review of the stay.

  • Only rooms free on every night
  • Night-by-night price and tax before booking
  • Cancellation fee shown before cancelling
  • ID upload, confirmation PDF and one review per stay

Rates, seasons and no overbooking

Each room type has a base rate, a weekend rate, the guests included and the maximum, and an extra-guest charge. Rate plans sit on top: a percentage up or down, an add-on per night such as breakfast, and a cancellation policy. Seasons cover a date range with a percentage or a fixed rate for one room type, and owners can set a special price, the number of rooms on sale (allotment) or stop sale for any night or range. The server works out each night in a fixed order (special price, room-type season, property season, weekend, base), then applies the rate plan, extra guests and the tax slab for that night's price. Each room type has a row per night with a sold counter; a booking takes every night with a conditional update inside one transaction, and if any night is full the whole booking rolls back. The tests run two guests for the last room (one wins) and five guests for two rooms (two win).

  • Base, weekend, season and special prices
  • Rate plans with add-ons and policies
  • Allotment and stop sale per night
  • Tax slabs by the per-room price of each night

Front desk and owners

Owners manage their properties (details, amenities, map pin, photos, the property's own UPI ID, check-in and check-out times), room types and room numbers (inventory follows the room list), rate plans, the price calendar and seasons, front-desk staff logins and their ledger. Front-desk staff see only their property: arrivals, departures and guests in house. At check-in they upload or check the guest's ID, choose empty rooms of the booked type and check the guest in. They record a payment as cash or card at the desk, or UPI with the UTR, check guests out once the payment is recorded (leaving early gives the remaining nights back to sale), cancel, mark a no-show, record refunds and download the invoice PDF. Cancellation follows the policy: flexible (free until 24 hours before check-in, then the first night), moderate (free until 5 days before, then half) or non-refundable. The fee and refund are calculated on the server, and the owner can waive the fee.

  • Arrivals, departures and in house
  • Check-in with room numbers and guest ID
  • Payments, check-out, no-show and refunds
  • Three cancellation policies, fee can be waived

Admin, ledger and guest ID privacy

The admin approves, suspends or returns properties to pending, sets a commission per property, sees every booking (cancel, record refunds, invoice, view the ID) and manages guests, owners and staff. The commission ledger shows, per property, what was kept from guests, the commission and refunds owed, exports to CSV, and settlements are recorded by the admin; no money moves through the app. Settings cover business details, brand colours, SEO, maintenance mode, commission, tax slabs, stay rules, weekend nights, guest-ID rules, map, live chat, WhatsApp, analytics, an announcement banner, a cookie notice and SMTP. Guest ID files (JPEG, PNG, WebP or PDF up to 5 MB) are stored outside the public folder under a random name. Only the property's owner, its front desk and the admin can open one, every opening is logged on the booking so the guest sees it, and the files are deleted automatically 30 days (you can change this) after check-out or cancellation. The app does not file police or immigration reports for you.

  • Property approval and commission per property
  • Ledger per property with CSV export
  • Private guest ID files with logged access
  • Automatic deletion after the retention period

REST API, mobile app and what is in the zip

The REST API at /api/v1 uses bearer tokens that last 90 days. It covers search, properties, the price calendar and quotes, a guest's bookings, cancellation and invoice, the front desk's check-in, check-out, payments, no-shows and refunds, and the owner's calendar and ledger; API.md documents every endpoint. The mobile/ folder holds an Expo (React Native) app with a guest mode (search, property, price calendar, booking, my trips, cancellation preview and UPI link) and a front-desk mode for owners and staff (arrivals, departures, in house, check-in with room choice, payment with UTR, check-out, no-show). The zip has server.js, the routes, views, the sample illustrations, the Prisma schema and seed script, ADDONS.md, mobile/, README.md, API.md and the PDF guide. npm run setup creates two invented towns with four sample properties (one waiting for approval) and demo logins; no bookings, reviews or ratings are invented. npm test runs 22 tests on a throwaway SQLite database, covering overbooking races, seasonal prices, cancellation fees and refunds, guest ID privacy and owner isolation.

  • API.md documents every endpoint
  • Expo app: guest and front-desk modes
  • Sample properties, no invented bookings or reviews
  • 22 unit, API and web tests

Honest limits

There is no channel manager and no OTA sync: rooms and prices are not synchronised with other booking sites or a property-management system, so if a property also sells rooms elsewhere, the owner closes nights or lowers the allotment here by hand. There is no housekeeping or live room-status module and no yield management. The mobile app cannot upload a guest ID because it has no file picker; guests and the front desk upload it on the website. Native Android and iOS builds of the mobile app have not been run; it type-checks, so test your EAS builds on real phones. No payment gateway is bundled and UPI payments are confirmed by hand with the UTR; there is no wallet and refunds are made outside the app. Maps use OpenStreetMap's public tiles, which are for testing only. Only SQLite was tested.

  • No channel manager or OTA sync
  • Guest ID upload on the web only, not in the app
  • Native builds not run; no gateway bundled, no wallet

More ready-made websites

Built by the same team, with the same setup service and support.

Browse every ready-made website, or compare our custom website packages if you need a site designed from scratch. Want more guests to find you on Google Maps? See our local SEO service, or talk to our web design team.