What MineRooms stands for
One stay, shared context
Room, dates and guest details give reception, housekeeping and food service a common starting point.
A view for each team
Guests browse their own account; staff work from the front desk, a phone or the Kitchen Display.
A product you can adapt
Drupal modules, a hotel theme and provider boundaries leave room for your policies, branding and integrations.
One hotel application, from room choice to room readiness
A stay crosses several teams. The guest needs room information; reception needs the booking and room state; housekeeping needs the room task; the kitchen needs the food queue. MineRooms brings those surfaces into a Drupal application with hotel-domain modules.
The sample site lets you inspect these views under their actual roles. Use it to work through your own operating case, then agree the rules and integrations your deployment needs.
View full sizeThe tools for the hotel’s working day
Room information, booking context and operational views support guests and staff in their existing roles.
- RoomsFind the right stayRoom types, capacity, amenities and property information.
- BookingChoose dates and guestsAvailability results and guest-information entry points.
- ReceptionRead the room stateRoom Board, Bookings, Walk-in and arrival/departure forms.
- CleaningWork beside the roomPhone Task Board, checklist, issue and inspection views.
- KitchenRead the order queueNew, Preparing and Ready columns in Kitchen Display.
- GuestReturn to the accountBookings, food orders, notifications and profile.
- ContentMaintain hotel informationArticle and page authoring with permitted editor access.
- DrupalAdapt the deploymentHotel modules, a shared theme and provider boundaries.
Built around the work of a hotel
Independent hotels
Review the solutionStart with the guest site and the front desk, then choose the operational pieces your property needs.
Hotels with housekeeping and F&B
Read the user guideReview the hand-off between reception, room cleaning and food service against a real example from your day.
Groups with several properties
See the architectureMap property inventory, pricing and staff access before choosing the deployment and reporting scope.
Agencies delivering hotel systems
Working with WeebPalUse the product as a starting point for your client’s brand, policies and integrations, with a clear fit report.
From choosing a room to preparing the next stay
The operating journey to agree and verify for your hotel deployment. The sample views illustrate each team’s part.
Choose the stay
Browse room types and properties; choose dates, capacity and the room you need.
Check rooms
Review the room options, nightly rate and stay length returned by the search.
Make the booking
Collect the guest details and select the payment route agreed for your hotel.
Prepare the arrival
Find the booking at the front desk and review the room and arrival information.
Check in
Assign a ready room and start the stay under the hotel’s check-in policy.
Serve the guest
Review room food orders in the kitchen and keep the charge with the stay.
Check out
Review the stay and its folio, settle the balance and record the departure.
Prepare the room
Housekeeping works through the checklist and reports anything that needs attention.
Review the day
Reconcile the business day and use the result to prepare the next shift.
Know which room comes next
Reception starts with the room state and the booking. The Room Board puts the sample inventory in one view, with floor and status filters, while Bookings and Walk-in provide the context for the next arrival.
- Room Board with Available, Occupied, Hold, Cleaning and Maintenance states
- Bookings filtered by status or source, with a booking detail view
- Check-in, check-out and cancellation forms for a selected booking
- Room types, calendar, room prices and hourly booking pages
View full sizeThe task stays beside the room
Housekeeping has a phone-oriented route from Task Board to room checklist. The staff member can read the room, the current task and the items to check without carrying the front-desk screen into the corridor.
- Room number, task status and assignment in the same view
- Checklist covering linen, bathroom, minibar, towels and amenities
- An issue form for reporting a room problem
- Inspection views for the housekeeping walkthrough
View full sizeRead the order queue at a glance
Kitchen Display separates New Orders, Preparing and Ready. Its captured empty state is useful too: the shift can see that there is currently no work in the queue, instead of guessing whether the screen has loaded.
- Three visible stages with order counts
- A dedicated Kitchen Staff role and operational screen
- Public restaurant and menu pages for the guest-facing side
- Room QR menu, cart and order-status pages in the sample site
View full sizeWhat guests and staff see
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full sizeLive demo
Each demo is a working copy of MineRooms with sample data, open for you to try.
A booking page and a hotel workflow
The difference is the work after a room has been chosen. This is a scope comparison, not a comparison with a named vendor.
| Standalone booking-page scope | MineRooms scope | |
|---|---|---|
| Starting point | The guest chooses a room and date | Guest choice plus the hotel’s operational views |
| After booking | Confirmation is the end of the page flow | Arrival, room assignment, service and departure are part of the scope |
| Who works in it | Primarily the visitor | Guest, reception, housekeeping, kitchen and content roles |
| Room readiness | Handled in a separate process | Room Board and housekeeping views can be reviewed together |
| Hotel rules | Built into the booking flow | Specified across inventory, staff access, folio and providers |
| Deployment fit | Website content and checkout | Content, operations, integrations and acceptance |
What stays in the product, and what is yours
Keep the hotel’s policies and provider choices visible in the deployment scope. The Drupal application provides modules, services and a theme to build on.
A MineRooms deployment
Your systemsPayment gateways, OTA channels, accounting, communications and selected AI providers
Provider contracts and integrations
Your hotel layerYour brand, room inventory, rates, staff access, operating policies and connected providers
Custom modules, theme and configuration
Product coreDrupal, Commerce, the MineRooms hotel modules and the shared site theme
In the current edition
- Public rooms, branches, restaurant menus and availability-search views
- Guest account pages for bookings, orders, notifications and profile
- Receptionist Bookings, Walk-in, Room Board, calendar and pricing views
- Housekeeping Task Board, checklist, issue and inspection views
- Kitchen Display with New, Preparing and Ready columns
- Drupal room and booking entities, hotel modules and Commerce folio services
Built and verified for your deployment
- Your brand, public content, room inventory and property configuration
- The staff-role and branch-access rules for your hotel
- Connected payment provider, verified callbacks and refund handling
- Live OTA connections, room/rate mapping and retry policies
- Real AI providers, data boundaries and rate-approval rules
- End-to-end acceptance, migration, pilot and operational handover
How a hotel deployment runs
Begin with the people and the operating case, then turn the fit report into a concrete delivery plan.
From the sample installation to the agreed hotel scope
- DiscoverWalk through the sample site with the people who do the work.Your hotel use cases
- Fit reportList existing capability, configuration and development.Agreed scope
- PrototypeShow your brand, inventory and key workflow on staging.Reviewable screens
- BuildImplement the selected rules, role access and integrations.Working increments
- AcceptanceCheck saved results, permissions and provider outcomes.Recorded results
- Pilot & handoverRun the agreed pilot and transfer code, access and documentation.Operating handover
Define the handover before launch
These are the decisions and deliverables to record in the project scope. Pricing, hosting, support and warranty are agreed separately.
- Inventory and policies Room capacity, booking times, day-use overlap, taxes and cancellation rules.
- People and access Staff roles, property scope, privileged actions and guest-record ownership.
- Provider results Payment callbacks, refunds, OTA synchronisation and AI review behaviour.
- Migration and content Room and guest data, public content, redirects and opening balances.
- Acceptance and pilot The agreed scenarios, expected results, recorded tests and launch decision.
- Operations and support Hosting, backup/restore, access, support and commercial terms in the agreement.
Start with a real moment in the hotel day
Find the arrival and inspect its room context before opening check-in.
An arrivalFront deskRoom Board and Bookings Read the room task, follow the checklist and report anything that needs attention.
A room to prepareHousekeepingPhone Task Board and room checklist Review the guest’s room menu and the kitchen’s order stages in the same walkthrough.
A food requestFood serviceRoom QR menu and Kitchen Display
Questions about MineRooms
Is MineRooms a booking website or a hotel application?
Both are part of its scope. The sample site contains the public room and booking pages, a guest account, front-desk views, housekeeping and a Kitchen Display. The deployment review connects those surfaces to the hotel’s operating process.
Can our team try the sample site first?
Yes. Open the live demo, read the user guide and the solution presentation, then walk through your own example: an arrival, a room needing cleaning, a food order or a departure. The fit report should record what is available and what your deployment needs.
Are payment, OTA and AI already connected?
The current local edition contains payment stubs, a mock OTA connector and mock AI clients. A deployment needs real provider credentials, contracts and recorded sandbox checks before relying on those services.
Can housekeeping use a phone?
The sample site has phone-oriented Task Board, room checklist, report-issue and inspection pages. The role guide shows the current mobile screens; the hotel must still agree task assignment and inspection responsibility.
Can we offer day-use as well as overnight stays?
Day-use pages and hourly services exist in the project. The room inventory, time-slot overlap, cleaning buffer and checkout policy should be agreed and tested together, because both products use the hotel’s rooms.
Does a Manager have every operational screen today?
That is the intended management scope, but the current Manager role cannot open some operational routes. The Manager guide records the boundary; it must be resolved before the role is used for a hotel deployment.
Can we bring our brand and existing systems?
The site is built with Drupal modules, configuration and a custom theme. Branding, content, data mapping and integrations are scoped in the fit report, then built and tested for the chosen deployment.
What comes with the project handover?
Agree the deliverables before development: application and deployment code, configuration, data-migration records, role guides, acceptance results and operating documentation. Hosting, support, pricing and warranty are terms to confirm in the contract.
A guide for each part of the hotel
Step by step, on the current site.
Hotel tools
Walk through MineRooms with your hotel team
Bring an arrival, a room-cleaning case and a food order. Start from the sample site, then record the fit, the policy decisions and the work for your deployment.