Past channel bookings: manual import by period

This content is not available in your language yet.


Why	After a channel is connected, only new bookings arrive in the calendar; guests who booked before the connection get into the system through a manual load for a period.
Who	The administrator who has just connected a channel — or is connecting the next one.
What you’ll get	Past bookings of the channel in the “Bookings” list and in the calendar grid, with dates and guests.
Limitations	The load runs for one channel at a time; loading the same period twice is a decision to make consciously.

Connected a channel — and its past months of sales are already in the calendar? Not yet: the system starts accepting the channel’s bookings from the moment of connection. Everything the channel sold earlier is loaded as a separate operation — for a chosen period, one channel at a time.

The good news is that the operation is a single one: you name the channel and the period, and the bookings appear in the system exactly as they would have if they had arrived on their own. This article covers where the load lives, how to set the period, and what to check afterwards.

Why past bookings do not arrive by themselves

The channel sends events about new bookings — and this stream starts at the moment of connection: every sale made after the two systems are joined lands in the calendar grid on its own, with a notification on the screen. Whatever happened earlier never enters the stream, no matter which dates it concerns — the channel does not send new events about past sales.

Until past bookings are loaded, the calendar grid shows only what the channel sold after the connection — and looks more vacant than it really was. That is why it makes sense to run the load right after connecting a channel, before the calendar becomes your main working tool.

Past bookings have a separate path: the system does not receive them by itself, but it can request them. You name the channel and the period — everything else happens inside.

Open the load

Open “Channel Manager” in the left menu — the “Channels” tab.
On the card of the channel you need, press the “Mapping” icon — the “Category and rate mapping” dialog opens.
In the dialog header, next to the “Reconfigure” and “Refresh” buttons, press “Load bookings”.

Result: the booking load dialog of the selected channel is open.

There is no separate menu item for the load — it lives inside the mapping and always runs in the context of a specific channel: whichever card you opened it from is the channel that gets loaded. If several channels are connected, bring the bookings over one by one, channel by channel.

Choose the period

The “Load bookings” dialog has a “Stay period to load” label and two fields: “Start date” and “End date”. What is meant here is the dates of the stay: the bookings that reach the system are the ones covering the nights the channel sold inside this interval.

By default the fields are pre-filled with a period roughly one year ahead of the current date. Adjust the boundaries to fit your data — for example, from the start of the season or from the date your sales history in the channel begins. The interface shows no limit on how far back the period can go.

In the “Start date” field, enter the date to request bookings from.
In the “End date” field — the date to request bookings up to.
Choose what to do with the bookings after the load — that is the next section — then press “Load bookings”.

Result: the period is set by stay dates; if you are unsure about the boundaries, start with a short stretch — the result can be checked before you widen the period.

What to do after the load

Below the period fields there is a question — “What to do with the bookings after loading them into the PMS?” — and two options:

load into the PMS only — the bookings appear in the system, and nothing is sent to the channel;
load and send to the channel — after the load, the system sends data to the channel according to the property’s settings.

For a history transfer, the first option is usually enough: these bookings existed in the channel before the connection, and the task is to see them in the system next to the new ones. The second option is for when the load should be accompanied by a send to the channel according to the property’s settings.

The first one is selected by default — confirm it or switch to the second, then press “Load bookings”.

Result: the bookings are loaded into the system; sending anything to the channel is not required — a history transfer does not need it.

Check the result

The loaded bookings appear in the “Bookings” list and in the calendar grid — with guests and stay dates, like any bookings in the system.

Open the “Bookings” list and find the channel’s bookings by their source label: in the booking row the source is visible as text — next to the booking number, for example “Confirmed by Booking.com”.
Open the calendar grid: on the bar of a channel booking there is the channel’s logo.
No bookings visible — check whether the data arrived at all: the “Events” tab → the “Incoming” sub-tab shows what the channel sent.

If nothing is there after the load, the bookings for the chosen period did not come from the channel: double-check the channel and the period boundaries and run the request again. How the events journal works — in the article Delivery log.

Result: the source is the fastest way to recognize what you loaded: the channel label is visible both in the list and on the grid.

Honest limits

One channel at a time. The load runs in the context of a single channel: there is no button that loads the past bookings of all channels at once. If several channels are connected, repeat the load for each.
Overlapping periods — a risk of duplicates. Loading overlapping periods again can produce duplicates: load one period first and check the result before widening it.
Money — check it in the channel. Commissions and payments on past bookings should be checked in the channel’s account.