A note from Jinova Systems, not part of the sample
Two instruments, three years, and one of them is a rounding error.
Every other sample on this site makes the same argument, because at seven rooms or forty-two beds it is the only argument there is: follow one booking, net off the commission, multiply up. A forty-eight room hotel with a rate desk has a second instrument that a homestay cannot use at all, so the comparison worth printing here is not one booking against one commission line. It is the two instruments side by side, over the three years each of them lasts.
Where the two per-night figures come from. The same ₹6,200 Double leaves you ₹5,146 through Booking.com at 17% and ₹5,933 through your own site at 4.3%, so the gap is ₹787. Direct is not free, which is why that gap is the number to argue from rather than the whole ₹1,054 commission; anyone quoting you the full commission as a saving is selling something. On the agreement, the 15% tier discount is ₹930 a night against the ₹1,054 you would have handed an OTA for the same night, less about ₹58 a night for carrying 45 day terms, which nets ₹66. And 1,426 is 48 rooms at 74% occupancy, which is 12,965 room nights; 55% of those arriving through OTAs is 7,131; one booking in five of those moved is 1,426.
So the right-hand column is worth about two per cent of the left-hand one, and we would still put the rate desk on the page before anything else, because it is the only column whose nights are not back on sale to somebody else next April. What that certainty is worth we are not going to price for you, because we would be making the number up, and this band has enough invented numbers in it already.
Both columns are built from published commission ranges and from the tiers printed further up this page, not from any property's accounts. Bring one month of OTA statements and a year of rate desk enquiries and we will rebuild the whole table from your occupancy, your rate and your own agreements before you commit to anything. If the right-hand column comes out smaller still on your numbers, we will tell you that too.
Why the small column still gets its own section
An agreement is the one thing on this page an OTA has no way to reach, and it is bought by a travel manager who will never look at the booking form. That is why the corporate desk is a section with its own path, its own address and its own three working day promise, rather than a second button under the form. The margin on it is a rounding error. The forecast it produces is not, and a forecast is what lets you hold rate through monsoon instead of discounting into it.
The direct incentive is never a discount
Parity clauses stop you undercutting the OTA price, so what the direct rate carries is breakfast from 05:30 before the first flights, the 16:00 checkout when the floor allows, no device limit on the internet, and the invoice with the right GSTIN on it. In this segment that converts better than money would. Early check-in is charged rather than given away, which is why the arrival planner higher up the page states the price of it instead of hiding it behind a phone call.
We integrate an engine, we do not build one
At 48 rooms that is AxisRooms or STAAH, whichever already holds your MakeMyTrip and Goibibo connections, which in India matters more than the international OTA coverage the vendors lead with. The form at the top of this page is a mock and says so on every result.
What ships in the markup, and what does not
This page now carries schema.org Hotel data, and deliberately leaves aggregateRating and review out of it, because the 4.3 and the three quotes above are invented and a fictional review has no business being machine readable. Your build gets both, from your verified Google and engine reviews, pointed at your Google Business Profile. The noindex stays on this sample regardless.
Rebuild this table from our statements