Is InnMetric a channel manager or PMS?
No. InnMetric works across the hotel systems you already use. It audits their combined commercial behavior then supports approved corrections and verification.
FAQ
Frequently asked questions
Is this only a public OTA audit?
No. A public review can identify a symptom. The paid baseline may include authorized work inside the PMS, channel manager, booking engine and OTA extranets so the cause can be verified.
Do you guarantee more revenue?
No. Distribution corrections can remove commercial friction but InnMetric does not invent revenue impact. A financial claim requires reliable hotel data, a defined baseline and an agreed measurement method.
Will you change rates without approval?
No. The hotel names the approver and the permitted scope. Material changes are logged before implementation.
Do you need our passwords?
Use named accounts with the lowest practical access level whenever the system permits it. Credentials should not be sent through ordinary email. Access is removed when the agreed work ends.
Can you work with our current vendors?
Yes. InnMetric is designed to work across the existing stack. Some issues require a vendor ticket or vendor-led change. That dependency is documented rather than hidden.
Which properties are a fit?
The strongest fit is an independent hotel, resort, aparthotel or small hotel group with a direct booking path plus two or more active OTAs. A hotel owner, GM or commercial lead must be able to approve access and changes.
Do you work with non-hotel lodging?
The current focus is hotel-operated accommodation. Individually listed homes and non-hotel lodging portfolios are outside the primary scope.
What does a baseline audit produce?
The output includes a system map, evidence register, confirmed findings, unresolved hypotheses, a prioritized correction backlog and the QA test for each recommended action.
Is ongoing support available?
Yes after the baseline. The cadence may include pricing, availability, restriction, mapping, promotion and live-channel checks. The contract defines which controls are daily, weekly or monthly.
How is pricing determined?
Pricing depends on property size, stack complexity, channel count, access requirements and whether implementation is included. The first call is used to define a fixed initial scope.