> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/automation/rate-recommendations/what-it-considers.md).

# What a recommendation considers

The 7 things Revhero takes into account when it prices one of your dates.

Every recommendation takes 7 things into account.

6 of them describe demand. They cover what is already sold, what is booking now, and how much interest your market and your property are attracting. They also cover what the date normally does at this time of year, and how far away the date is.

The seventh is a limit that you set yourself.

![The 7 things a recommendation takes into account](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-0d6a61bd72ebc47b159e192fc0fb11e905e0bdfa%2Fwhat-a-recommendation-weighs.svg?alt=media)

*All 7 are read together. One rate comes out, at your base combination, and your pricing structure derives the rest.*

These 7 things matter for 1 practical reason. When a rate comes back higher or lower than you expected, check them before you decide whether you agree with the rate.

| Input                                                                                                               | The question it answers                                 |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| [Room nights on the books](/revhero-docs/automation/rate-recommendations/what-it-considers/room-nights.md)          | How much of this date is already sold?                  |
| [Pickup](/revhero-docs/automation/rate-recommendations/what-it-considers/pickup.md)                                 | How fast is it booking right now?                       |
| [Market demand](/revhero-docs/automation/rate-recommendations/what-it-considers/market-demand.md)                   | How much interest is there in my destination?           |
| [Demand for your property](/revhero-docs/automation/rate-recommendations/what-it-considers/property-stay-demand.md) | How much interest is there in *my hotel* for this date? |
| [Seasonality](/revhero-docs/automation/rate-recommendations/what-it-considers/seasonality.md)                       | What does this date normally do?                        |
| [Your minimum rate](/revhero-docs/automation/rate-recommendations/what-it-considers/minimum-rate.md)                | How low am I willing to go?                             |
| [Pricing lead time](/revhero-docs/automation/rate-recommendations/what-it-considers/pricing-lead-time.md)           | How far away is the stay?                               |

{% hint style="info" %}
These are not 7 separate votes that are added together. Revhero reads them together, against your property's own history. That is why the same occupancy on 2 different dates can produce 2 different rates.
{% endhint %}

## Related

* [How recommendations work](/revhero-docs/automation/rate-recommendations/how-it-works.md)
* [Using recommendations in practice](/revhero-docs/automation/rate-recommendations/using-in-practice.md)

***

**Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20rate-recommendations%2Fwhat-it-considers%2FREADME.md) and quote this page: `rate-recommendations/what-it-considers/README.md`. Say what you expected to find — that is the part we can fix.