> 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/pickup.md).

# Pickup

Recent booking speed for a stay date, and why it is the fastest signal Revhero reads.

**Pickup** is the number of room nights booked recently for a future stay date. A **room night** is one room sold for one night.

Pickup is the fastest of the 7 inputs to react. It shows booking activity immediately, before any other input has changed.

A date that starts filling shows it in pickup first. A date that has gone quiet also shows it in pickup first.

![The same stay date read at two points in time](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-ce6e07a941068661bbf7bc912908b274669c09fe%2Fwhat-changed-since-the-last-look.svg?alt=media)

*The same stay date, read a week apart. The difference between the two reads is your pickup.*

## Why it matters to you

Room nights tell you where a date stands today. Pickup tells you where it is going.

2 dates can have the same occupancy. One is booking steadily. The other has had no bookings for 2 weeks. They should not carry the same rate.

Pickup moves quickly, so it is also the least stable input Revhero reads. 1 group booking can raise it sharply for a single date. 1 cancellation can remove it. That is why Revhero never reads pickup as a raw number. It reads it against what your property normally picks up at the same distance from arrival.

## What to do about it

Look at the recent booking activity on the date before you act.

| What you see                                      | What to do                                                                                                                                                                                       |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Strong pickup, and a higher rate is suggested     | Accept it, unless the pickup came from 1 booking that you already know about                                                                                                                     |
| Pickup has stopped, and a lower rate is suggested | Check whether the date has simply gone quiet, or whether something is blocking it. It could be a restriction, a closed channel, or a mistake in your availability                                |
| A cancellation you recognise                      | 1 large cancellation can pull the suggestion down further than the date deserves. Set your own rate for that date. The next run will settle once the cancellation has worked through the figures |

Revhero calculates pickup from your own reservation data. You do not need to set anything up.

## Related

* [Room nights on the books](/revhero-docs/automation/rate-recommendations/what-it-considers/room-nights.md)
* [Pickup](/revhero-docs/your-hotels-performance/dashboard/pickup.md) — the Dashboard widget to check against

***

**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%2Fpickup.md) and quote this page: `rate-recommendations/what-it-considers/pickup.md`. Say what you expected to find — that is the part we can fix.