Hatipathar: cottages, meals, one GST bill

The problem before BitLegacy

A cottage property with meal plans and a restaurant has three truths that must match: which room is occupied, what the guest ate, and what the final GST invoice should say. When WhatsApp bookings, a register for rooms, and separate food slips diverge, checkout slows down and the owner loses evenings reconciling. Guests who found the place online also needed a clear way to request a stay without only calling the desk.

What Resort Hatipathar runs on BitLegacy

Hatipathar runs Stay Requests with clear statuses, Stay Calendar, Rooms, and Rate Plans — including meal plans such as all meals included — plus Rate Calendar for dated prices. Guests book direct on the BitLegacy website. During the stay, Room Orders from guest QR ordering post to the stay bill; Cafe & Service can Charge to stay. Finance and GST stay invoices carry the rate plan name and taxed total. Charges & discounts adjust a stay when needed. Owner feedback on invoices helped shape how those bills read.

How day-to-day feels now

Arrivals show up in Stay Requests instead of a buried chat. Meal plan and room type are already on the booking. Food from the room or the restaurant can land on the same stay. At leave, the GST invoice is one document with the agreed total — not a room slip plus a cafe slip plus tax worked out later. For a Purulia nature lodge, that is a quieter counter on a busy weekend.

What they rely on

• Stay Requests (Pending / Awaiting payment / Paid / Arrived) + Stay Calendar
• Rooms, Rate Plans (e.g. all meals included), Rate Calendar
• Public booking website — Request a Stay
• Room Orders (guest QR ordering to stay bill) + Menu
• Cafe & Service (restaurant POS, Charge to stay)
• Finance, GST stay invoices, Charges & discounts on a stay

Capabilities described by the owner’s story — not a claim that every BitLegacy module is in use at this property.