Use **Inventory Load → PMS or CR Master -> Channel(s)** to prepare outbound rate, availability and restriction updates from an inventory image already stored in ChannelRUSH. You can load one destination channel or the eligible configured channels for one property.

An **image** is ChannelRUSH's stored inventory data. This workflow does **not** request a fresh download from your PMS, read back the OTA's current values, or perform a two-way synchronization.

## When to use this load

Typical uses include:

- Loading stored inventory to a newly configured channel after its room and rate-plan mappings are ready.
- Reloading stored PMS inventory after the relevant PMS overrides have been removed.
- Sending the intended stored values again after someone changed inventory directly in a channel's extranet.

First check that the source image contains the values you want to distribute. Reloading an old or incomplete image does not make it current or fill every gap. Remaining overrides, mappings, calculations and channel settings can affect the resulting updates.

This guide covers **PMS or CR Master -> Channel(s)** only. **Channel Refresh**, **Delete Images** and the other copy/load options are different operations; they are not steps in this procedure.

## Before you start

- Use an account with **Org Admin** access and access to the intended property.
- Confirm the property's source connection and destination channel setup, including the required room and rate-plan mappings.
- Decide whether you need one destination or **All Channels**. For a single-channel correction, select that channel rather than broadening the load to all destinations.
- Check the stored inventory and any overrides or calculations that could change it. If you need newer PMS data, resolve that inbound-data issue first; this load does not fetch it.

**Save on the final Confirm screen starts processing.** The two **Continue** buttons select and validate the scope; they do not start the load. You can inspect the confirmation and leave with **Cancel** without submitting it.

## 1. Select the property

1. Open **Org Admin → Inventory Load**.
2. Under **Inventory Load Options**, choose **PMS or CR Master -> Channel(s)**.
3. On the **Master to Channel** page, use **Property Select → Property** to choose the property. The current property is normally selected; verify its name and ID rather than relying on that default.
4. Click **Continue** to open **Channel Select**.

The property list is limited to properties available to your account. **Cancel** on Property Select returns to Inventory Load.

## 2. Select the source and destination

Check the **Property** name and ID shown on Channel Select, then complete both dropdowns:

| Field | Choice and meaning |
|---|---|
| **From Image** | Choose **PMS: [connection name]** to use that connection's inventory already stored in ChannelRUSH, or **ChannelRUSH Master Image** to use ChannelRUSH's shared master values. |
| **To Channel** | Choose a named destination to load that channel, or **All Channels** to process eligible configured outbound channels for this property. |

A blank dropdown is not the same as **ChannelRUSH Master Image** or **All Channels**. Select both choices explicitly, then click **Continue**.

![Channel Select with PMS: Mirage as From Image and All Channels as To Channel.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBdWNDIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--efec9de9f048eae1d681289a0cdcc6b85a576840/inventory-load-source-target-pms-all.png)

*Example: the stored Mirage PMS image is selected for all eligible channels. Your available connections depend on the property's setup.*

### Choose the right image

- **PMS: [connection name]** uses the stored inbound image for that PMS. Processing can include its shared values and relevant destination-specific values, and applies the relevant stored UI overrides and configuration. It is not a command to remove overrides or to ask the PMS for new data.
- **ChannelRUSH Master Image** uses its shared **“sent to all”** values, not its channel-specific exceptions. If a destination should retain an exception, confirm the intended source before proceeding.

### Understand the scope

**All Channels** means eligible configured outbound channels for the selected property—not every connection in your organization and not a guarantee that every field is sent to every destination. Channels without usable setup and products without the required mappings may be excluded. Supported fields, source-specific apply settings, calculations and each channel's supported date window still matter.

Selecting **All Channels** can also change ChannelRUSH's local master inventory state. With a PMS source, processing can save the resulting values to the ChannelRUSH master image; with the ChannelRUSH Master Image, it can update the stored submission timestamps. It is not merely a wider destination preview.

There are no date-range, room-type, rate-plan or individual-field selectors in this wizard. It works from the stored forward inventory, subject to the processing rules above. Do not use it as though it were a one-date or rates-only edit. Missing stored values are not an instruction to clear the destination or set everything to zero.

**Cancel** on Channel Select returns to Property Select.

## 3. Review the confirmation, then submit if intended

The **Confirm** screen shows:

- **Property:** the property's ID and name.
- **From Image:** **Master** for ChannelRUSH Master Image, or the selected PMS connection's ID and name.
- **To Channel:** **All** for All Channels, or the selected destination's ID and name.

![Confirm showing Master as From Image and 6 - Booking.com as To Channel.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBdWdDIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--d95a159e4333f8703a551e94a565ab21dd47405d/inventory-load-confirm-master-booking.png)

*Separate example: ChannelRUSH Master Image to Booking.com only. This is a different selection from the PMS-to-All example above; always review your own confirmation.*

1. Check all three values. Confirmation shows the scope, not a preview of every inventory value or the final number of updates.
2. If anything is wrong, click **Cancel** or the **Channel Select** breadcrumb to return to selection. Select both dropdowns again; they can be blank when you return.
3. Only when you intend to initiate the load, click **Save** once.

The application returns to Property Select and displays a **“process initiated”** message stating that an email will follow. Do not submit another load simply because this page has returned or a destination has not changed yet.

## 4. Check processing and the destination

The initiation message is not proof of successful handoff or delivery: it can appear even if the request failed to reach the processing service.

The completion email is addressed to the initiating user's account email. Its **Successful** or **UNSUCCESSFUL** result concerns inventory-load generation. **Successful does not confirm that all updates were saved or that every destination accepted them.** An unsuccessful result also does not prove that nothing changed; some work may already have completed. There is no fixed end-to-end completion time.

To investigate:

1. Select the same property and open **Updates → Status**.
2. Start with the intended destination **Channel**, **Status = All**, and an appropriate **Created** date/time window for the submission. Leave **Sent By** unrestricted initially; these loads are not always attributed to the person who clicked Save.
3. If useful, select **Source = PMS Refresh** for a PMS image or **Master Refresh** for ChannelRUSH Master Image. Clear this filter if you need a broader investigation.
4. Click **Search**, then inspect the returned updates, affected stay dates, products, values, statuses and messages. Open the requests/logs where available. Record the **Change ID** or **Request ID** for support. A load can produce multiple updates and sends; one successful row does not establish completion of the whole load.
5. If expected work is missing, broaden the filters and include not-sent or archived updates where appropriate. An empty search is not proof of delivery—or proof that nothing was saved.
6. Compare the intended stored values with the destination's inventory for the relevant room, rate plan and dates when channel confirmation is needed. Stored reports and processing statuses alone do not prove the channel's current values.

Use **Search** to refresh the results. **Go** runs a selected action; do not use it merely to check progress. This procedure does not require a resend, archive or other request action.

## If you cannot continue or the outcome is unclear

| Situation | Safe next step |
|---|---|
| A source or destination has not been selected | Choose both **From Image** and **To Channel**, then click Continue. Blank does not select the special Master or All option. |
| A connection is missing, not enabled, not set up, or does not support the required inventory direction | Recheck the property and have the connection's setup reviewed. An entry appearing in a dropdown does not establish that its setup is complete. Do not change the URL to bypass the selection checks. |
| Confirmation shows the wrong property, image or destination | Cancel and select the scope again. Start from Property Select if changing property; do not reuse a bookmarked confirmation URL. |
| The email is unsuccessful, does not arrive, or disagrees with what you see | Check stored inventory and Update Status, then contact support with the property ID, source image, destination scope, submission time and time zone, affected products/dates, messages and any Change/Request IDs. |
| Only some channels, dates or fields changed | Review source coverage, mappings, overrides, apply settings and channel support with support. Do not assume a full-image load overrides these rules. |

**If you cannot establish what happened, contact support before saving the load again.** Partial processing is possible, and repeating the load is not a guaranteed recovery or rollback.
