For your question, I like to use the Scrollbar's methods to the advantage of determining if the user wants to see more or not.
Depending on what the booking is for, the majority of the use-cases will mostly have the user wanting to view/edit/cancel the recent bookings possibly done in the same week/month.
If you could say - place an upper limit to how many bookings can be stored in the app offline itself, for example - 3 months' bookings will stay offline. Now if the user reaches the end of the list, load the rest, with a progress bar/circle.
How this works psychologically:
You know the user is looking for his earlier bookings when they scroll down and reach to the bottom of the list. In this case, the natural action would be to load the previous bookings as well.
There is no extra step involved or data loss. If you give the user the option to load more bookings, you are wasting one tap and if you are loading all of them without permission, you are wasting user's data.
If there is only a single booking which is done before 3 months, it won't load automatically. But this also means that means the offline bookings list is 0 and the end has been reached, hence load the previous bookings.