Channel Manager
Bulk Inventory Import
Use a CSV file to update rates, availability and restrictions across dates, room types, rate plans and authorized properties. Download an empty template, fill in your changes, validate the file, then submit it for background processing. Upload & Validate does not apply inventory changes. Process does. Processing can update master inventory, store manual overrides for incoming PMS inventory where enabled, and create outbound channel updates. Import completion is not confirmation that a channel accepted the changes. Before you start - Select the property in the application's property selector. Open Admin, find the Channel Manager section, then choose Bulk Inventory Import. - Use ChannelRUSH property, room-type, rate-plan and channel IDs—not names or external channel room codes. Your file can include more than one property, but you must have access to every property you intend to update. Authorized distributor users can include properties in their managed active child organizations. - Confirm the destination channels and product mappings are set up for inventory sending. Channel capabilities and settings determine which values can be applied. - Keep a copy of the intended values and the CSV you submit. There is no automatic undo. Your account needs the permissions for every update type in a row: CSV values supplied Required permission Rate Update - Rates Allocation or StopSell Update - Availability CTA , CTD , MinNights , MinNightsThrough , MaxNights , MaxNightsThrough or CutOffDays Update - Restrictions A row containing several update types needs each corresponding permission. A missing permission makes the row invalid; the importer does not strip out only the unauthorized field. Update Close-Outs alone is not sufficient for StopSell in this importer. Ask your administrator to review access rather than changing IDs or using a broader update to work around a restriction. 1. Download a template and find your IDs Empty-template selections for room types, optional rate plans and channels Default selections before choosing dates. The on-screen “empty for no change” note means no explicit field value is supplied; configured rules can still derive related changes, as explained below. 1. On Bulk Inventory Import, click Bulk Inventory Import Template in the Upload CSV File heading. 2. Check the property name and ID at the top. The template is for this property only. 3. Choose a Date Range, using the month picker or date-range control. Both endpoints are included. Choose dates from the property's today onward, with no more than 1,095 dates in one template. Import validation separately requires every date to be no later than the property's today plus 1,095 days. 4. Select the Room Types to include. All are selected initially; at least one is required. 5. Select Rate Plans, if needed. None are selected initially. No selection omits the RatePlanId column and creates room-level rows. Selecting plans creates rows for each selected room/plan combination, without additional room-only rows. 6. Select Channels. All offered channels are selected initially. Use the checkbox beside each group heading to select or clear that group, then choose individual entries. The selection counts and summary help you check the scope. 7. Click Download Empty Template. The CSV contains dates and IDs, with empty update cells. It is not an export or backup of your current rates, availability or restrictions. A template combination does not establish that the selected room and rate plan have an enabled mapping on every channel. Narrow or split large templates to stay within the import limits below. All channels versus named channels - When every offered channel is selected, the template uses ChannelId = 0: one all-channel row per date and room/plan combination, not separate rows for each named channel. - When you select only a subset, the template creates rows with those specific channel IDs. - 0 uses the property's eligible inventory-send channels when the import is processed. It is not a frozen list from the day you downloaded the template. If you need a fixed set of destinations, use explicit channel IDs in the CSV. - A property with no eligible inventory-send channel cannot process an all-channel row, even if a template can be downloaded. Room-level does not mean rate plans are untouched. Room-level inputs can also apply to enabled mapped rate plans and virtual room types through your channel setup. To target a particular standard rate plan, use its positive RatePlanId and check its channel mappings. ID Reference Download Use the separate ID Reference Download section when building or checking your file: - This Property downloads IDs for the selected property. - All My Properties downloads IDs for your assigned active properties. These downloads are Excel workbooks (.xlsx) with Properties, Room Types, Rate Plans when applicable, and Channels sheets. The Channels sheet includes 0 for all channels and the inventory-send channels represented in the workbook. A channel listed in a multi-property reference is not necessarily configured on every property. Use the workbook as a reference; do not upload it as an import. For a multi-property CSV, use each property's matching room and rate-plan IDs. 2. Fill in the CSV Open the template in your spreadsheet application, or create a file using the column reference below. Enter only the changes you intend to submit. File and formatting rules - Save as a comma-separated text CSV (.csv), preferably UTF-8. Renaming an Excel workbook to .csv does not convert it. Semicolon-separated files are not the required format. - Put the header on the first line and each record on its own line. Do not put line breaks inside cells. Quoted cells and doubled quotes within quoted cells are supported on a single line. - Header names are case-insensitive and surrounding spaces are ignored. Columns can be reordered. Keep each header unique. - Include Date, PropertyId, RoomTypeId and ChannelId. Optional columns can be omitted when not needed. - Keep comma separators for blank cells so later values stay under the correct header. Do not use null, dashes or other placeholders for an empty value. - Use a decimal point for rates, without currency symbols or thousands separators. Use whole numbers for IDs, allocation and numeric restrictions. - Maximum upload: 10 MB (10,485,760 bytes) and 100,000 parsed data rows. The header, blank lines and rows containing only empty cells are not counted as data rows. Blank, zero and false are different A blank update cell means you are not explicitly submitting that field. It does not clear an existing value. 0 and false are explicit values, not blanks. Configured inventory rules can still derive related changes. In particular, when Auto Stop Sell = NO When Allocation > 0 is enabled and you leave StopSell blank, a positive allocation can reopen a previously closed date; an allocation of 0 can set Stop Sell to Yes. Review both availability and Stop Sell before submitting an allocation-only file. Other channel rules can adjust rates, supply defaults or translate unsupported restrictions into a close-out. CSV column reference All update columns are optional. A row needs at least one update value to be processed. Column What to enter and what it means Date Required Inventory date in exact YYYY-MM-DD format. It must be between the property's local today and today plus 1,095 days , inclusive. Use the property's time zone, which may differ from yours. PropertyId Required Positive ChannelRUSH property ID for an authorized property. RoomTypeId Required Positive standard room-type ID belonging to that property. RatePlanId Positive standard rate-plan ID belonging to that property. Leave blank or omit the column for room-level input. Do not use 0 or a negative ID as a substitute for blank. ChannelId Required 0 for all eligible inventory-send channels, or a positive channel ID configured and enabled for inventory sending on that property. Blank is invalid. Rate Sell rate, such as 199.99 . Must be greater than zero. 0 does not remove a rate. Configured channel calculations can change the outbound amount. Allocation Number of rooms available, from 0 to 32767 . 0 explicitly submits no availability; a positive number submits availability. See the Stop Sell interaction above. StopSell true closes sales; false requests removal of Stop Sell. Reopening does not supply missing rates or availability, or remove other restrictions. CTA Closed to Arrival: true prevents a stay starting on this date; false removes this arrival closure. CTD Closed to Departure: true prevents a stay departing on this date; false removes this departure closure. MinNights Minimum length of stay for arrivals on this date. Use 1 to remove a multi-night minimum. The importer accepts 0 , but outgoing update requests normalize it to 1 . MinNightsThrough Minimum total length of stay for stays including this date. Use 1 to remove a multi-night through-stay minimum. An imported 0 is normalized to 1 in outgoing update requests. MaxNights Maximum length of stay for arrivals on this date. 0 requests removal of the maximum-stay limit. MaxNightsThrough Maximum total length of stay for stays including this date. 0 requests removal of the through-stay maximum. CutOffDays Minimum advance-booking interval in days before the inventory date. 0 requests no advance-day cutoff. For StopSell, CTA and CTD, accepted values are true/false, 1/0 or yes/no, in any letter case. For MinNights, MinNightsThrough, MaxNights, MaxNightsThrough and CutOffDays, accepted CSV values are whole numbers from 0 to 32767. Negative values are invalid. When both fields are supplied in a row, MinNights must not exceed MaxNights, and MinNightsThrough must not exceed MaxNightsThrough. This comparison also applies when the maximum is 0; do not pair a positive minimum with a zero maximum in the same row. These are import rules, not a promise that every destination supports every field or accepts the full numeric range. Restriction removal is an explicit update, subject to the destination's supported fields and mappings; a blank cell does not request removal. Illustrative example—not a captured upload The property and room IDs below are illustrative. Replace both IDs with your own, and replace every date with an intended property-local date within the allowed import window. ChannelId = 0 deliberately targets all eligible channels; replace it with a specific channel ID if that is not your intention. Date,PropertyId,RoomTypeId,ChannelId,Rate,Allocation,StopSell,CTA,CTD,MinNights 2027-01-15,10001,20001,0,199.99,10,false,false,false,2 2027-01-16,10001,20001,0,219.99,10,false,false,false,2 2027-01-17,10001,20001,0,249.99,5,false,false,false,3 2027-01-18,10001,20001,0,,0,true,,, The first three rows submit rates, allocation, open-sales/arrival/departure values and minimum nights. The last row submits zero allocation and Stop Sell only; its blank rate and restriction cells do not explicitly replace those fields. All rows are room-level because the example has no RatePlanId column. 3. Upload and review Upload CSV File with template link, file selector, size limits and Upload & Validate 1. Return to Bulk Inventory Import. 2. Under Select CSV File, choose your completed CSV. 3. Click Upload & Validate. 4. On Review Import, confirm the file name and each property's name and ID. Multi-property files also show an overall summary. 5. Check Total Rows, Valid rows to process, Skipped (empty data) and Errors for each property. 6. Read header warnings and the row error list. Correct the original CSV before proceeding if its scope or values are not what you intended. How to interpret the preview: - Valid rows passed the current checks and contain at least one update value. Validation does not prove that a channel mapping will create an update or that a channel will accept it. - Skipped (empty data) means a row passed validation but all its update fields are empty. Invalid IDs or dates still cause an error even if the update cells are empty. - Errors counts rows with errors, not individual messages. A row can have several messages. Row numbers refer to physical file lines, including the header as line 1. The preview displays at most 500 error messages; fix all affected rows and validate again rather than relying only on the visible list. - Duplicate Column Headers Detected - Cannot Process blocks the normal Process control, even if there are otherwise valid rows. Keep one header for each field and one room type per record. - Unrecognized Columns Detected lists ignored columns. A misspelled update header may cause intended changes to be ignored; correct it rather than dismissing the message. - If there are no processable rows, use Try Again. Otherwise, use Cancel to return without submitting the preview, edit your CSV and upload it again. The preview expires after 30 minutes. If it expires, upload and validate again. Editing the local file after validation does not change the uploaded preview. 4. Submit the import and check its progress 1. When the file and scope are correct, click Process [number] Valid Rows once. This submits real inventory changes for background processing. 2. On Background Import Started, record the Request ID, file name and preliminary counts. 3. Click Go To Status Page to open Import History. You do not need to keep the confirmation page open. 4. Find the job by ID and file name. Reload or search again to check its status; the confirmation page's Pending badge is not a live progress indicator. The entire original file is checked again when processing starts. Dates, permissions, property access and channel setup may have changed since preview, so final counts can differ. Rows that were invalid in the preview are not permanently excluded if they become valid later. If you want to exclude a row, remove it from the CSV and validate the revised file before clicking Process. Processing can skip properties where updates are not allowed, such as locked or inactive accounts. Eligible rows can produce no channel requests when mappings or supported-field settings prevent them. Some changes can be saved before a later failure; Failed does not mean nothing changed. A completion email is sent to the uploader's recorded email address when available. Use Import History to check the result even if the email does not arrive. Missing email alone is not a reason to re-upload. 5. Use Import History Import History lists submitted jobs, not files that were only previewed. It is not restricted to the currently selected property: it uses the applicable organization context and your uploader visibility. Most users see their own uploads; organization administrators and users with broader portfolio access can see other uploaders' jobs. 1. Select Status or leave All. 2. Select Uploaded By if you need to narrow the uploader. 3. Set Created Date Range if needed. This filters job creation using UTC day boundaries, not the property-local inventory dates inside the CSV. 4. Click Search. Use Clear to remove the filters. 5. Use the paging arrows to browse results, 25 jobs per page. If nothing matches, clear or widen the filters before assuming a job is missing. Widen the creation range around a date boundary if necessary. Each entry shows: History item Meaning ID Bulk import job ID. Keep it for investigation; it is not an outbound channel request ID. File Name Opens Bulk Import File View in a new tab. The entry also shows the uploader and a property name or property count when available. Status Import-processing state, described below. Rows Processed Rows / Total Rows , not a channel-delivery fraction. These counts are not a live per-row progress meter. Requests Requests counted during import generation/saving. A dash can appear while pending or processing; a finished job can show 0 . It is not a count of channel-accepted days. Timestamps Created, Processing start and Completed when recorded. Completion can include a failed outcome. Result/error text Stored processing summary. Long error text is shortened in the list; open the file view for the stored detail. Import statuses Status Meaning and next step Pending Submitted and waiting for background processing. Do not submit another copy merely because it has not started. Processing Import processing has started. Check again before deciding on a correction. Completed Import processing finished without recorded validation errors or skipped-property warnings. It does not establish channel acceptance or guarantee that every row produced a request. Completed with Errors Processing finished with validation errors or skipped properties. Read the result and errors before preparing a correction. Failed Processing could not finish, or no valid rows remained. Inspect the error and any already-applied changes before retrying. Timed Out badge A job is still marked Processing more than 30 minutes after its recorded start. It may subsequently be marked Failed. This is not proof of rollback or permission to submit a duplicate. There is no cancel, retry or undo action for submitted jobs on this page. The preview's Cancel only leaves the preview; it does not cancel an already submitted job. 6. Inspect the original file and processing summary In Import History, click the file name. Keep the history tab open: Bulk Import File View opens separately without the main navigation. Original upload Top excerpt of an existing demo upload showing request identity and read-only inventory rows Top excerpt of an existing demo file, not current channel inventory. The viewer may display dates in a spreadsheet format such as M/D/YYYY; an import CSV still requires YYYY-MM-DD. Confirm the file name, Request ID, Created timestamp and Rows at the top. The Import Data spreadsheet displays the stored original upload, including rows that failed validation. It is not a successful-row report or a fresh view of current channel inventory. The spreadsheet can include empty CSV records excluded from the parsed total, so the records displayed in the grid may not match the Rows count shown above it. The spreadsheet is read-only. You can resize columns to read values, but cannot edit cells or open another file in it. File → Save As downloads a spreadsheet copy; the file name is prefilled from the upload. File → Print prints the displayed spreadsheet. Neither action submits inventory, repairs the import or undoes changes. Handle downloaded or printed files according to your organization's data-sharing rules, especially for multi-property uploads. If File content not available appears, check the summary and errors below. Missing grid content does not establish that the import never ran. Processing Summary Completed demo import with row counts, requests created, execution time and result Completed describes import processing—not channel acceptance. Use the Processing Summary jump link or scroll below the spreadsheet. Reload the page to obtain a newer snapshot. Field Meaning Status The import job's state, not the destination channel's result. Total Rows Parsed data records, excluding the header and entirely empty records. Valid Rows Rows with update data that passed validation. Pending values are preliminary; background processing recalculates them. Error Rows Records that failed validation, not the number of error messages. Skipped Empty Valid-identity/date records without update values. Processed Rows At normal completion, the revalidated row count passed into processing. It can include rows for a property subsequently skipped; it is not a count of successful saves or deliveries. Requests Created Generation/save-stage request count. It can be zero, and it need not equal the row count. It does not count accepted channel dates. Execution Time Recorded elapsed processing time, when available. Completed Recorded job completion timestamp, when available—not channel acceptance time. Result Additional outcome text, when available. Read it even if the counts look satisfactory. Processing Errors When an error summary exists, Processing Errors appears below the summary with a jump link at the top. This is the full stored summary, not necessarily every error in the original file: background validation retains at most 100 validation messages, and a processing failure may show a general error instead. Scroll within the error area to read it. Correct files outside the viewer. Saving a spreadsheet copy does not change the original submitted job. Save As creates a generated spreadsheet copy, not a byte-for-byte download of the original CSV. Dates may be reformatted in the viewer or downloaded copy. Before reusing a copy for import, save it as CSV and check that every Date value is exactly YYYY-MM-DD. Prefer editing your retained original CSV. 7. Verify channel updates and recover safely After checking the import result: 1. Select an affected property and open Updates → Status. 2. Select the relevant Channel, room type or rate plan, and Source: UI Bulk Import. Use Status: All when following an update through different states. 3. Click Search, then inspect the relevant dates, values, status and available messages or logs. Do not enter the bulk import job ID as an outbound Request ID. 4. Repeat for other affected properties and destinations. Check the destination channel's product and dates when you need confirmation of its current inventory. Import History answers “Did the import finish processing?” Update Status answers “What happened to the outbound updates?” Neither the import's Completed badge nor its Requests Created count replaces the second check. Problem Safe next action File rejected, parse errors or shifted columns Export a real text CSV, check comma separators, header spelling, dates and numeric formats, then validate again. Split files exceeding the byte or row limit. Invalid property/product/channel or permission error Check the ID reference and the property's enabled mappings. Ask your administrator to correct access or setup where necessary; do not substitute unrelated IDs. Session expired. Please upload the file again. A preview may have expired or already been used. If you clicked Process or its response was uncertain, first search Import History for the job. Re-upload only after establishing that a new submission is needed. No email, Pending/Processing does not advance, or Timed Out Search/reload history and inspect the job. If it remains unresolved, contact support with the job ID rather than repeatedly uploading. Completed but zero requests, missing changes, or unexpected values Read Result and Processing Errors, then check mappings, channel field support, configured calculations and outbound status. Do not assume zero requests means master inventory was unchanged. Completed with Errors or Failed Compare the original CSV, stored outcome, current inventory and outbound updates. Some changes may already have applied. Prepare only the corrections still needed. Wrong values were processed There is no automatic undo. Establish the correct current values, then submit a deliberately scoped corrective import or use the appropriate update screen. Re-importing an old file can overwrite newer changes. For support, provide the import Request ID, file name, affected property/channel/product IDs, inventory dates, action time and time zone, and the relevant error text. Share only the necessary file excerpts; no passwords or unrelated guest information are needed.
Channel Settings - Review Mapping Changes
Use this review after room types, rate plans or connection settings change on a channel. The goal is to match the correct channel IDs to your ChannelRUSH rooms and plans, keep the intended update settings, and remove only mappings that are genuinely obsolete. Before you start Open the correct property's Admin page, then the relevant channel's settings. Check the property and channel names before making changes. Editing, adding and deleting mappings requires Channel Settings permission; connection credentials require the separate Channel Settings - Login Info permission. If you arrived here from a Missing Room Type Mappings alert, check the property, channel and reported room ID against the current settings and mapping information. No new items in the list is not enough to dismiss the alert; resolve missing or uncertain data with support. Finish or discard any unsaved edits before navigating away or reloading. Note the affected room/rate IDs and any custom settings you need to retain. Do not change credentials or enable updating just to clear a warning. 1. Load and check the mapping information Click Mappings at the top of Channel Settings. It opens in a new tab. image For channels that support retrieval, opening this page requests mapping information and can update ChannelRUSH's saved mapping list. Other integrations use saved or manually supplied mappings, or show the mappings prepared for a PMS. This is not a universal, read-only refresh, and you should not assume Booking.com or Expedia has already refreshed every change automatically. 1. Check the property, channel and Channel Property ID shown on the mapping page. 2. Read any Mapping Error banner before relying on the results. An error, empty channel list or unexpected missing room/plan is a reason to investigate—not to delete mappings. 3. Review Mapped Room Types, Unmapped Room Types and, where available, All [channel name] Mappings. Compare room and rate-plan IDs, not names alone. Check the detailed rows as well as Issues Requiring Attention. Mapped, zero Errors or zero Warnings do not prove a successful fresh retrieval. The page can show locally mapped rooms and zero issue counts alongside a separate Mapping Error. Likewise, no Mappings Updated! banner does not necessarily mean retrieval failed: the returned information may be unchanged. Mapping Error banner reporting that no channel mapping room types were returned. Banner from a demo comparison using saved mapping data. The same page showed locally mapped rooms and zero issue counts; this example does not demonstrate a fresh provider retrieval. If the result is unexpected, confirm the connection/property ID with an authorized administrator and compare the affected IDs with the channel's extranet. Contact ChannelRUSH support if retrieval fails or the lists disagree. Do not treat an old saved list as confirmation that a plan was removed remotely. Mappings - Other, when available, lists other channel-specific IDs; it is not a replacement for the room/rate comparison. A Send Mappings tab describes mappings prepared for a supported PMS connection, not proof that they were delivered. Return to Channel Settings and reload it to display the saved mapping information. Reloading that page alone is not another channel retrieval. 2. Review mismatches and existing settings Use Expand All and each room or rate plan's Additional Settings to review the affected sections. - Check Channel Room Type ID, Channel Rate Plan ID and Standard Rate Plan Mapping, where shown. - Read [NOT SETUP], [INVALID MAPPING], INVALID RATE PLAN MAPPINGS and any page-level warnings. - A red [ X ] highlights a difference from available mapping information, such as Updating Enabled, occupancy or a supported feature. Compare the actual values and the intended setup before changing anything. Yes is not always the right correction. image No red [ X ] does not establish that everything is correct: checks depend on the channel's capabilities and the mapping data available. Confirm intended updating at the channel, room and rate-plan levels, including any deliberately disabled features or rate calculations. For a PMS connection, review the receive settings rather than assuming the OTA updating controls apply. If an existing mapping has the wrong ID, correct it to the confirmed ID under the correct room type and save the settings. Do not add a duplicate or delete an otherwise needed plan merely to hide the warning. 3. Map missing rooms, then add the intended rate plans Add Unmapped Room Types and Add Unmapped Rate Plans appear only when the available mappings and supported setup allow them. A missing link does not prove that the channel has no missing products. Room types 1. Open Add Unmapped Room Types when offered. 2. For each ChannelRUSH room shown, select the corresponding channel room by name and ID. Leave rooms blank if they should not be mapped to this channel. Do not select the same channel room for multiple entries. 3. Click Save when the choices are correct. This saves the room assignments and imports available room settings; it is not just a preview. 4. Complete the rate-plan screen if it opens. Otherwise return to Channel Settings and check for Add Unmapped Rate Plans. If there is no suitable room entry or choice, resolve the room setup first rather than assigning an unrelated room. Rate plans UNMAPPED RATE PLANS means the available mapping list contains plans that are not configured under that channel room in ChannelRUSH. Add only those this connection should manage. image Open Add Unmapped Rate Plans above the room settings: image On the add screen: 1. Check every room heading and Channel Rate Plan ID. The displayed plans are selected by default; uncheck any you do not want to add. 2. Review Rate Plan Name and Updating Enabled for each selected plan. Do not enable updating solely because a plan appears in the list; respect the channel's update restrictions. 3. Select the appropriate Standard Rate Plan Mapping, where offered, so the new plan uses the intended standard plan. Do not guess a correspondence from similar names. 4. Click Save, then review the resulting Channel Settings and messages. Open the new plans' Additional Settings and apply any required custom settings from the replaced plans. Adding a plan does not automatically copy the old plan's custom calculations or disabled features. image These additions use ChannelRUSH's saved mapping list; opening the add screen is not a fresh retrieval. If expected plans are absent, resolve the retrieval or room mapping first. 4. Remove only confirmed obsolete rate plans image INVALID RATE PLAN MAPPINGS or [INVALID MAPPING] means the configured rate-plan ID was not found in the mapping information for that room. It does not, by itself, prove someone deleted the plan from the channel. Before deleting, confirm that retrieval succeeded for the correct connection, the room ID is correct, and the plan is genuinely retired or replaced. If the plan still exists, correct the mapping or ask support to investigate. Record the old plan's standard-plan mapping, calculations, feature switches and other custom settings before removal. Remove one plan Open that rate plan's Additional Settings, scroll to Delete This Rate Plan, and follow the delete link. Check the room and plan on the confirmation page. Choose Delete only when this is the intended local plan; otherwise choose Cancel. Remove several plans 1. Open Delete Rate Plans above the room settings. image 2. Select only the plans you have confirmed should be removed. The list can include valid plans too; an [INVALID MAPPING] label is a prompt to investigate, not permission to delete. Room-level select-all controls select that room's plans, not just invalid ones. image 3. Click Continue to review the selected plans. This step does not delete them. image 4. Review every room/rate ID and any additional-settings warning. Go back to change the selection, or Cancel to leave without deleting. The final Delete button performs the deletion. Understand the additional-settings warning The warning identifies selected plans with certain disabled features or nonzero rate calculations that will be lost with the local plan. It is separate from an invalid-mapping warning and is not a complete inventory of every custom setting. Delete Rate Plans - Confirm showing the full additional-settings warning for an existing demo Standard rate plan. Existing demo warning example on Delete Rate Plans - Confirm. The plan is shown only to illustrate its additional settings; no deletion was performed. Additional Settings detail: Allocation is disabled for the demo Standard rate plan under Garden View Two Queens. Detail from the same example: Allocation is disabled. A warning identifies settings to review; it does not by itself mean the mapping is invalid. Review and record the required settings before proceeding, then deliberately apply them to any replacement. Do not assume that no warning means there is nothing to preserve. Deletion removes the rate plan and its settings from this ChannelRUSH channel configuration. It is not an instruction to delete or close the plan in the channel extranet, and it is not an undoable hide action. Supported integrations may also send updated settings after the local deletion. Do not use deletion as a substitute for stopping sales on the channel. 5. Verify the result and handle errors After each save, addition or deletion: - Read all messages, not just the success message. Where offered, Save & Refresh saves changes and reloads the settings; it is not a read-only refresh. - Reopen Channel Settings and check the actual saved IDs, room assignments, standard-plan mappings, update switches and custom settings. Confirm that intended additions are present and only intended deletions are absent. - Review the mapping comparison again where supported, including retrieval errors and the detailed rows. A clean comparison is not proof of rate or availability delivery or of bookability on the channel. A local save can succeed before a subsequent settings send fails. If you see a send error, a timeout or an uncertain result, check what is already saved before retrying. Do not repeat an add/delete operation blindly or assume an error rolled it back. Give ChannelRUSH support the property, channel, affected room/rate IDs and exact message—never passwords—and confirm the next step if the saved state or channel outcome remains unclear. Related article Channel Settings Page - OTA
Configure OTA and PMS channel settings
Connect the correct property, rooms and rate plans, then choose how inventory and reservations move between ChannelRUSH, your online travel agencies (OTAs) and your property management system (PMS). This guide covers the shared Channel Settings page. An OTA connection sends rates, availability and restrictions out to a sales channel. A PMS Inventory Receive connection brings inventory into ChannelRUSH. Reservation delivery has its own controls and can run in the opposite direction. The fields shown depend on the selected connection, its supported features and your permissions. The examples use Expedia and Viewpoint PMS; use your own provider's identifiers and agreed connection settings, not the example values. Before you start - Select the correct organization and property. Confirm the channel name at the top of the editor before changing anything. - You need Channel Settings permission to save. The login section requires the separate Channel Settings - Login Info permission. You may be asked to verify your password before opening the page. - Have the provider-confirmed property ID, room IDs, rate-plan IDs and connection details. A familiar room name does not prove that its ID is correct. - Confirm who controls rates, allocation and restrictions: your PMS, manual ChannelRUSH updates, or a combination using overrides. - Agree changes to credentials, reservation delivery, pricing model or inventory source with your implementation contact before saving. These can interrupt an active connection. Saving is an operational change, not a preview. It can refresh mappings from a supported provider, save the configuration and send mappings/settings to a supported provider. It can also notify connection monitoring; turning reservation handling off can notify support. Do not save merely to inspect a field or obtain a fresh screenshot. Open the connection 1. Select your property in the property selector. 2. Open Admin → Settings - CM. 3. In Channel Manager → Channels, select the OTA or the entry marked [PMS]. 4. Confirm the channel name and ID at the top of Channel Settings. 5. Use Additional Settings within the property, room or rate-plan section to reveal its optional controls. Expand All and Collapse All change the display; they do not save the form. Expedia connection header with Mappings, Login, Expand All, Collapse All and Menu links. Help opens this shared guide. Channel Support opens provider-specific instructions when available. Mappings opens the channel mapping comparison in another tab. Login, when shown, opens the provider's extranet; it does not save this form. Configure the connection in a safe order 1. Check the shared connection details Review Username, Password and Channel Property ID against the provider's setup instructions. If API URL appears, verify the approved endpoint as well. Do not replace an established connection login with your personal extranet login unless the provider requires that change. Use Notes for non-sensitive operational context. Do not paste passwords, payment details or guest information into notes or support screenshots. Additional username/password fields are protected login information; use them only as directed for your connection. Choose Channel Currency to match the currency configured for this connection. Confirm any conversion requirements before changing it. Rounding Setting controls rounding used in rate processing; it is not a currency selector. Channel Currency set to USD and Rounding Setting set to Do Nothing. 2. Check every room mapping Each room card is headed by the property's standard room type. Inside that card: 1. Set Channel Room Type Name to a recognizable description of the provider's room. 2. Enter the provider's exact Channel Room Type ID. The ID, not the display name, establishes the external mapping. 3. Where shown, check OccupancyMin and OccupancyMax against the provider's occupancy pricing setup. 4. On an OTA, review that room's Updating Enabled and its supported feature controls. 5. Repeat for every room you intend to manage. PMS Garden View Two Queens room mapping with Channel Room Type Name, ID and occupancy fields. PMS example: the standard room is Garden View Two Queens; the provider-facing room name and ID are separate fields. These demo mappings are examples of the form, not recommended mappings for your property. An OTA room header can also show PMS: name (ID) or PMS: [UNMAPPED]. This is a reference to the associated PMS room mapping, not a field that you edit on the OTA card. If it is unexpected, check the PMS connection and any inventory-group assignment before changing the OTA ID. 3. Check the rate plans under each room 1. Find the intended rate plan under the correct room card. 2. Review Rate Plan Name and enter the external Channel Rate Plan ID. 3. Select the corresponding Standard Rate Plan Mapping, where available. 4. On an OTA, review the rate plan's Updating Enabled, feature controls and rate calculations. 5. Repeat for each room/rate-plan combination. Do not assume a rate-plan ID is interchangeable between rooms. Standard rate plan for Garden View Two Queens: name and Standard Rate Plan Mapping. Standard rate plan: Channel Rate Plan ID and Updating Enabled. A blank Standard Rate Plan Mapping leaves that selection unassigned; it does not automatically choose a standard plan. For a PMS receive connection, avoid assigning multiple incoming rate plans under the same room to the same standard rate plan: duplicate standard mappings can prevent saving. 4. Apply the OTA or PMS controls below Review the appropriate section before saving. Updating Enabled, Inventory Receive and Reservation Handling are different switches; enabling one does not enable the others. OTA: control inventory sent to the sales channel Updating Enabled and feature groups An OTA can have Updating Enabled at connection, room and rate-plan level. No disables inventory updating at that scope. Yes permits it, subject to the channel being available, the product being set up, and the relevant feature controls. A room or rate-plan switch is not a reservation-delivery switch. Under Additional Settings, distinguish these groups: Group What it controls When unchecked Standard Features - On/Off Whether a supported inventory feature is enabled for this product. That feature is disabled for the product's updating workflow. Checking another group does not override this master feature switch. Standard Features - On/Off - Populate Automatic population from broader controls on manual update screens. A broader manual edit does not automatically populate this product's feature. A permitted channel-specific edit may still be available. This is not the PMS switch. Standard Features - On/Off - PMS Whether PMS-generated inventory can update this OTA product's feature. The PMS-generated path does not apply that feature to this OTA product. This does not switch off the entire PMS connection. Room-type Standard Features: Allocation and Stop Sell for On/Off, Populate and PMS. Room-level example: Allocation and Stop Sell have separate On/Off, Populate and PMS controls. Rate-plan Standard Features: complete On/Off, Populate and PMS controls for Rates, Stop Sell, CTA and CTD (left side). Rate-plan Standard Features: complete Min Nights and Max Nights controls for On/Off, Populate and PMS, in the same top-to-bottom order (right side). Rate-plan groups continue across the page. The right-hand screenshot shows Min Nights and Max Nights in the same top-to-bottom order: On/Off, Populate, PMS. The available features vary by provider and by level. Expedia's room-level allocation controls and rate-plan restrictions are not a template for every other channel. Review both levels rather than assuming a checkbox on one controls every field on the other. Net, sell, markup and margin Net, Sell, Markup, Margin Settings appears only for supported OTA connections. Use the pricing model agreed with that provider; do not use this section as a general substitute for product rate calculations. Net, Sell, Markup, Margin Settings: Markup and Margin values. Net, Sell, Markup, Margin Settings: Type and Minimum Markup Dollars. Field How to use it Markup The adjustment used to calculate the sell/net relationship. With % Percentage , markup is measured against the net amount. Margin The corresponding percentage of the selling amount. Changing a percentage markup or margin updates the companion value on screen. They are not two independent percentage additions. Type % Percentage uses a percentage. $ Flat Fee , or the displayed currency equivalent, uses an amount. The margin control is hidden for flat-fee calculation. Minimum Markup Dollars A minimum monetary markup for the supported net/sell calculation. Use only if required by the connection's pricing agreement. Per Date Range Lists dated markup settings. Add New opens a separate date-range editor; existing entries are maintained separately from this form. Save or discard pending work here before leaving for that editor. For illustration, a net amount of 80 with a 25% markup gives a selling amount of 100. The corresponding margin is 20%, not 25%. Confirm whether the provider expects net or sell rates before applying either figure. Provider-specific Additional Settings These controls are not universal. Required fields carry an asterisk, and provider-supplied mapping differences may be highlighted. Expedia Additional Settings showing RateAcquisitionType and Rate Type selectors. For the Expedia example: - RateAcquisitionType offers NetRate and SellRate. Choose the acquisition basis configured for your property with Expedia. - Rate Type offers PerDay, PerOccupancy and PerPerson. Match Expedia's pricing setup rather than choosing whichever makes an individual rate look correct. Other providers can have different required property, room and rate-plan parameters. Use Channel Support and the provider's confirmed mapping details. Do not copy Expedia's selections into a different connection. PMS: receive inventory and protect selected manual updates Inventory Receive modes PMS Inventory Receive and Connection Monitoring controls. Inventory Receive Effect Off Disables receiving/storing inventory through the connection's enabled receive workflow. The page warns that inventory will not be received/stored. On Processes incoming inventory and creates automatic outbound channel updates for eligible mapped destinations. It does not guarantee those destinations accept the updates. On - Queued Stores the incoming inventory changes without automatically creating outbound channel updates in that receive-processing path. Do not treat this as normal automatic distribution with a promised delay. On - Delta Only Processes incoming inventory and generates updates while suppressing unchanged product/date snapshots. It is not a promise that every outgoing request contains only individually changed fields; a changed day can include existing values populated into that day's snapshot. Do not turn a second PMS source On without checking inventory groups. If another active inventory-receive source already exists outside the required group configuration, saving can be refused. Resolve the source-to-destination design rather than disabling the existing source to bypass the warning. Connection Monitoring and receive timestamp PMS Connection Monitoring Hours and informational Inventory Receive Timestamp. - Connection Monitoring enables or disables the connection's inactivity monitoring setting. - Connection Monitoring Hours is an inactivity threshold in hours, not how often the PMS is polled. Monitoring also has eligibility and system checks; setting a number is not a guarantee of an alert at exactly that elapsed time. - Inventory Receive Timestamp is informational. For a push receive connection it comes from the latest recorded inbound inventory-message creation time. For a monitored/pull connection it comes from the inventory monitor's recorded activity. A dash means no corresponding timestamp is available. The timestamp is not proof that a particular room/date was updated or that an OTA accepted its inventory. Use it as a starting point for investigation, together with PMS ARI Log and outbound Updates Status. User PMS Override The User PMS Override section determines which types of saved manual updates can take precedence over later PMS inventory for the affected products and dates. User PMS Override checkboxes for allocation, restrictions, rates and Stop Sell. - Checked: an existing applicable manual override can block replacement by the corresponding PMS field. - Unchecked: that override protection is not enabled for the field; later PMS inventory can overwrite manual values. - Checking a box does not create an override value. A manual value must also have been saved for the relevant product/date through the update workflow. Stop Sell has a special rule. Protection applies to a saved manual closure, Stop Sell = Yes. It can also prevent positive PMS allocation from reopening that closure. Do not assume a saved manual reopening, Stop Sell = No, is protected against a later PMS closure in the same way. Review each field independently: Allocation, CTA, CTD, Cut Off Days, Max Nights, Max Nights Through, Min Nights, Min Nights Through, Rates and Stop Sell. Decide which system should own each value before changing these switches. Unchecking a switch does not by itself establish that a new PMS value has arrived or been sent onward. PMS product sections can also show Standard Features - On/Off and rate calculations. Their supported fields relate to that PMS connection. The OTA-only Populate and PMS groups are not the same as this property-level override policy. Reservation controls: separate from inventory For an OTA, Reservation Handling concerns reservations received from that channel. For a PMS delivery connection, it concerns reservations delivered to the PMS. The property-level reservation configuration and the provider's capabilities must also support the intended flow. PMS Reservation Handling, Reservation CC Info and Reservation Retry controls. Field Meaning and precautions Reservation Handling On enables the connection's supported reservation workflow; Off disables it. Turning OTA inventory updating off is not a substitute for turning reservation handling off. Coordinate changes with support/provider, especially when stopping delivery. Reservation Send Type Shown when both delivery methods are supported. Push sends through the provider's push integration. Pickup / Confirm uses the pickup/confirmation integration. Match the receiving system's setup. Reservations - Send Email Notifications A separate On/Off option shown for connections supporting this email override. Email notification is not confirmation of PMS delivery. Reservation Retry Enables or disables the PMS connection's automatic reservation retry setting. It is not a manual resend button and does not prove a failed reservation has been delivered. Reservation CC Info Controls the payment-card information prepared for the supported PMS delivery. Select the least information required by the approved integration. Token options require an appropriate token-capable setup. Guest Messaging Connection-level On/Off control when the feature, property and permissions make it available. It is separate from inventory and reservation handling. Guest Reviews Connection-level On/Off control when the review feature is available. Its absence is not a room-mapping error. Reservation CC Info options - Off: removes the card number, security code and expiry from the PMS-bound reservation preparation. Do not interpret this as deleting every card-related field or the original reservation. - On: does not apply that stripping/abbreviation step; the actual information available still depends on the reservation and integration. - On - Abbreviated: keeps only the last four characters of the card number, removes the security code and retains expiry information. - On - CC Token Only: uses the token workflow and strips raw number, security code and expiry from the PMS-bound preparation. - On - CC Token - Abbreviated: uses the token workflow with abbreviated card details. Never include card numbers, security codes, tokens or connection passwords in a support request or screenshot. Shared field reference Identity, scope and required values Field or indicator Reference Username / Password Provider connection credentials. Required markers are not proof that the credentials have been accepted remotely. Keep established managed connection values unless instructed to replace them. Channel Property ID The provider's property identifier. It is distinct from the ChannelRUSH property ID in the property selector. Preserve significant characters and remove accidental leading/trailing spaces. Extra Username 1 / 2; Extra Password 1 / 2 Additional login fields shown with the login-info permission. Use only according to the connection's requirements; do not use them as general notes. API URL Provider-specific endpoint where supported. Editable with login-info permission; it can be shown read-only otherwise. A wrong endpoint can direct connection traffic incorrectly. Notes Notes about this property's selected connection. Keep them non-sensitive. Channel Room Type Name / Rate Plan Name Descriptive local labels for the channel products. Editing a label does not substitute for correcting its external ID. Channel Room Type ID / Channel Rate Plan ID Exact external product identifiers. A rate plan belongs to its displayed room context. Blank or incorrect IDs can leave the product not set up or wrongly mapped. Standard Rate Plan Mapping Associates the connection product with a property standard rate plan. A blank selection is unassigned. Some channels expose this at room level instead of rate-plan level. OccupancyMin / OccupancyMax Occupancy bounds used for occupancy-based rate setup where supported. Match the provider. On this form a blank minimum is read as 1, while a blank maximum is unset; neither means “copy the provider's current value.” Occupancy Room Rate Mapping Appears for applicable occupancy-based PMS mappings. Identifies the occupancy used for that mapping; agree it with the PMS setup rather than guessing from the room name. [NOT SETUP] The product lacks an external ID or has not met setup requirements. Saving a display name alone does not establish setup. [INVALID MAPPING] The external product ID was not found in the available channel mapping data. Review the provider and mapping comparison before replacing the ID. [ X ] / INCORRECT SETTING - Correct: … A difference against available channel mapping information. Inspect the specific field; this is not a confirmation that a send failed or that automatic replacement is safe. Inventory feature names These checkboxes enable or route a feature; they do not enter a nightly value themselves. Feature Inventory value it concerns Rates The product's monetary rate. Occupancy/additional-rate settings may have their own controls. Allocation Rooms or units available for sale. Stop Sell Whether selling is closed. CTA / CTD Closed to arrival / closed to departure. Min Nights / Max Nights Minimum / maximum length-of-stay restrictions for the supported channel model. Min Nights Through / Max Nights Through Stay-through length-of-stay restrictions, where supported, rather than assuming the arrival-based fields cover the same rule. Cut Off Days The supported advance-booking cutoff. Additional Features - On/Off Provider-specific inventory features. Follow their displayed names and channel instructions. A Property Level Standard Features - On/Off group can appear for providers that support property-level fields. Room and rate-plan feature groups apply to their displayed product. Do not infer that every provider exposes or interprets every feature at all three levels. Currency, rounding and rate calculations Control Reference Channel Currency Currency configured for the connection. Do not assume every integration or incoming amount is automatically converted merely because this field is selected. Rounding Setting: Do Nothing No rounding by this setting. Round To Nearest Dollar / Round Up / Round Down Round to the nearest whole monetary unit, upward, or downward respectively where this rounding setting is used. The displayed label can say “Dollar” even when another currency is selected. Rate Settings — Calculation 1 through 6 Ordered product-level adjustments. Each has an amount and a percentage/flat-fee type. Use zero for an unused adjustment; blank numeric calculation inputs are read as zero when that calculation is saved. Rate Settings - [occupancy/additional rate] Separate controls for the displayed occupancy or additional-rate component, where supported. Its On/Off and available Populate/PMS controls belong to that component, not every rate in the room. Calculations are sequential, so order matters. For example, 100 increased by 10% and then by a flat 5 becomes 115. Review the full chain, including other property or channel calculations, before adding a second adjustment. Saving configuration is not a command to resend every previously distributed date. Save and check the result 1. Review the entire connection, including expanded room and rate-plan settings. The top and bottom save controls submit the same form, not only the nearest card. 2. Choose Save & Refresh from the arrow beside Save if you want to remain in this editor for verification. Save normally returns to the originating administration page after an existing connection saves without warnings/errors. If warnings remain, the editor can stay open. 3. Read all success, warning and error messages. A settings-saved message and a settings-send result describe different stages. 4. Reopen or refresh the saved editor and verify the intended IDs, modes, feature switches and calculations. 5. Where supported, open Mappings and review the provider comparison. A successful local save is not proof that the provider accepted the mapping/settings send. 6. For inventory delivery, open Menu → Updates Status. Select the intended outbound OTA destination and relevant dates, then click Search. If you opened this from the PMS editor, change the channel filter from the PMS to the destination you are checking. Inspect the actual request and its result; an empty result or a receive timestamp is not proof of delivery. 7. For PMS inventory, also inspect Admin → PMS ARI Log for incoming messages. For reservations, use Menu → Reservations - Delivery Status and its Search action to investigate delivery separately. Cancel leaves this editor without submitting the pending form. It does not undo a previous save or any downstream work already triggered. A new connection may instead show Save & Continue so that setup can continue after its first save. If a save reports an error after configuration was saved, do not assume everything was rolled back. Reopen the connection and inspect the current values and status before repeating an action. Do not resend inventory or reservations solely to test whether a setting worked. Common problems and safe next actions Symptom Check and safe next action This channel is not set up or [NOT SETUP] Check the required connection/product fields and provider-specific Additional Settings. Verify external IDs with the provider. Ask support if correct confirmed values still leave setup incomplete. [INVALID MAPPING] , UNMAPPED ROOM TYPES or a mapping difference Compare the saved IDs with Mappings and the provider's actual inventory. Mapping data may not contain the expected product. Do not change IDs based on names alone or bulk-import blindly. Duplicate room/rate-plan mapping error Check repeated external IDs and PMS standard-rate-plan assignments. A duplicate can involve another property. Ask support to resolve ownership if the error identifies a property you cannot inspect. A second PMS cannot be enabled Review inventory-group membership and which source feeds which channels. Do not switch off an established source merely to make the new one save. Virtual room type cannot be saved for PMS Inventory-receive connections do not allow virtual room types. The presence of Add Virtual Room Type in navigation is not proof that the selected PMS supports it. No automatic OTA updates from PMS Check Inventory Receive is not Off or On - Queued , then inspect mappings, OTA Updating Enabled, supported feature/PMS switches, override values and request status. Avoid changing several controls at once. Manual values are replaced by PMS Check the applicable User PMS Override switch and whether an override value was saved for those exact products/dates. Apply the special Stop Sell rule rather than assuming all Yes/No values behave identically. Manual close does not reopen after PMS allocation arrives A protected manual Stop Sell closure can block reopening. Review the saved closure and override policy before changing inventory. Reservation warning although Updating Enabled is Yes Inventory and reservations are independent. Check Reservation Handling and property-level reservation configuration. Coordinate any delivery shutdown with the provider/support. Settings saved but settings send failed Reopen to confirm local persistence, record the message and investigate the provider connection. A second save can repeat remote work; confirm the safe retry with support. Missing or disabled controls Check edit/login-info permissions, provider capabilities and property feature availability. Do not use another channel's settings as a workaround. Unexpected rates Check currency, pricing model, rounding, net/sell settings, all ordered calculations and the exact product mapping. Compare the generated request before changing prices again. When escalating, provide the property name/ID, channel name, affected room/rate-plan IDs, stay dates if relevant, action time and time zone, and the exact warning/error. Exclude passwords, payment details and unnecessary guest information. Related guides - Channel Settings - Review Mapping Changes - PMS Overrides - Expedia
Channels Report - Grid View
Overview Use Grid View to compare rates, availability and restrictions for selected sources, room types and rate plans, with one column per date. It is a report, not an inventory editor. Read the source name before comparing values. Stored channel reports, PMS/master images and CRS inventory represent different stages of your inventory. A green cell or matching rate is not confirmation of a live guest-facing offer, successful delivery or rate parity. Open the report 1. Select the property you want to review. 2. Go to Reports > Rates & Availability. 3. Choose your sources, room types, rate plans, dates, weekdays and data types. 4. Click Grid. You need a signed-in account with access to the selected property. The available sources and products depend on that property's setup. You do not need inventory-update permission merely to read the grid; editing inventory and requesting a data refresh are separate actions with their own access requirements. Grid report controls for List, Excel, CSV, Open calendar and New window, with Grid selected. The controls above the report let you change dates and filters, switch to List or Excel, download CSV, or open a separate report window. Open calendar leads to the inventory-editing calendar; it does not make the grid editable. Choose dates and filters Change the date range 1. Set the start and end dates above the grid. In a single-property report, these controls sit beside the legend. Month / Year fills a whole month into the date range. 2. Click Load to reload those dates using your current dropdown selections. 3. Check the resulting date headers and visible rows. Selecting dates or a month alone does not load them. The date range and Days work together: a date appears only if its weekday is selected. You can therefore review only weekends within a longer range without changing the range itself. Use the dropdowns Control What it selects All Channels Stored sources available for the property, including applicable channel, PMS and master-image sources. It is not a promise that every connected channel has reportable data. Room Types Standard room types to show across the selected sources. Configured virtual rooms follow their parent room's selection. Rate Plans Plans to show below the room rows. Unmapped , when offered, includes configured channel plans without a standard rate-plan mapping. Leaving all plans unchecked is allowed and shows room-level rows only. Data Rates , Availability and Restrictions . Occupancy prices and extra-person charges belong to Rates , not a separate data option. Days Weekdays whose date columns should appear. Select all checks every option in that dropdown. When all are checked, clicking it again clears them. A partial selection shows a count. Clearing a list does not mean “include everything.” To load a valid report, keep at least one source, room type, data type and weekday selected, and use a valid date range. Rate plans are optional. Follow the selection warning if Apply is disabled. Know when Apply is needed In Grid View, hiding data already loaded takes effect immediately. You can also re-show that same loaded data without fetching it again. Selecting a source, room type, rate plan, data type or weekday that was not loaded requires Apply — reloads report. A checked option does not mean its data has loaded yet. Room Types dropdown with King checked and Apply — reloads report visible while the loaded report still shows Studio and Queen. Selecting an option that was not loaded leaves it pending until you apply the selection. Click Apply — reloads report when it appears. It uses the current selections across the dropdowns, not just the dropdown containing the button. Then confirm the requested rows and dates are visible. Filters work together: a rate-plan row needs its source, room type and rate plan selected. A room row needs its source and room type selected. A channel heading disappears when all its product rows are hidden. Hiding rows or cell text changes the report display, not the property's inventory or channel setup. Understand the source headings The blue section bars identify the source of the rows beneath them. Do not treat similarly named sections as interchangeable. Source shown How to interpret it Ordinary channel name The stored channel-report representation. Depending on the integration, it can reflect reported data or values recorded through outgoing-update processing. It is not universally an independent read-back from the OTA . PMS - … An inbound/PMS or master/override source. The master image and an enabled manual-override image are distinct stored sources, not additional OTAs. ChannelRUSH CRS or booking-engine source Inventory loaded through the CRS configuration, with its room/rate relationships and applicable promotion calculations. It is not a complete guest booking search. … - Live Read , when available A separate read from a supported PMS inventory-monitoring integration. All Live Read is offered only for an eligible single current property, not every OTA or a multi-property comparison. Loading this source can contact the connected service; it is not just another view of stored data. A separate Channel Image source is restricted to ChannelRUSH administrators. Its absence from a customer account is expected; it is not a missing customer permission to request. It represents the stored channel-inventory image, not a screenshot or proof of what an OTA is selling. For an ordinary stored-data review, use All Channels and leave Live Read unselected. Load and Apply reload the report; they do not guarantee that an upstream service has supplied newer values. The criteria screen's Refresh Data is a separate request action, and that screen can also perform an automatic refresh check. A refresh request is not an immediate-completion guarantee. Read the rows and dates Grid detail showing ChannelRUSH CRS, Studio, Standard and Package across October 29 through November 1, 2026. - Blue section bar: the channel or source name. - Room row: the standard room type, followed by its rate-plan rows where supported. - Indented rate-plan row: the standard plan name when mapped, otherwise the channel plan name. - Virtual room: marked Virtual: and associated with its parent room selection. - ID: a product identifier for the displayed source. Identical names do not prove identical mappings, and identifiers need not be the same across sources. Some integrations hold availability at room level and rates or restrictions at rate-plan level. Read both levels rather than expecting every cell to contain every field. For CRS, the room row displays availability while rate-plan rows carry rates and restrictions; an empty rate-plan availability line is not automatically missing inventory. Grid date headers for October 29 through November 1, 2026, with the capture-day blue highlight and darker Saturday and Sunday headers. Date-header example captured on October 29, 2026: blue marks that day, and Saturday and Sunday have darker headers. Dates run left to right. Weekend columns have darker shading, and the report marks its current day in blue. The historical screenshot's blue date is not permanently “today.” Scroll inside the grid to reach more rows or dates. Date headers stay at the top of that scroll area. On wider screens, the left product column stays visible during horizontal scrolling; on mobile-sized screens it scrolls with the table instead. Hovering a product label can show its channel name. Row hover subtly darkens cells and highlights the left label; it is not a new availability status. When the loaded report contains more than 8 selected date columns, it uses the full available page width. This is not browser fullscreen. A long range or a narrow screen may still require horizontal scrolling. Use a shorter range or fewer products for a more manageable comparison. Read the cell values Availability and rates With Availability selected, the cell's top number is its allocation value. With Rates selected, the sell rate appears below, formatted to two decimal places. Not every source or product level supplies both. - A blank can mean no value was supplied, the data type is hidden, or the source does not show that field at that level. It is not automatically zero, open or closed. - An explicit 0 allocation is different from a missing allocation. However, a CRS room row can display 0 when its allocation is missing, so that display alone does not prove a recorded sellout. - A main sell rate of 0.00 can be displayed. Do not interpret it as a verified free offer. - The grid does not display a currency beside every rate. Confirm the currency and equivalent product/occupancy before comparing amounts. Occupancy prices and extra charges Where supplied, additional lines can include 1 Pax through 10 Pax, Extra Adult, Extra Child, Extra Bed, Crib, or other source-specific rate parameters. These are separate price values, not the number of rooms available. The grid lists only positive additional sell-rate values. An absent occupancy or extra-charge line therefore does not establish that the charge is zero or that the occupancy is unavailable. Turning off Rates hides these lines too. For CRS rate plans, a crossed-out price is the pre-promotion sell rate when the report's promotion calculation supplies one; the following price is the resulting sell rate. This is not an inventory of all promotions or confirmation that a particular guest qualifies. The report does not collect a guest's coupon or full booking context. Restrictions With Restrictions selected, applicable codes appear in red beneath the rates: Code Meaning SS Stop Sell CTA Closed to Arrival CTD Closed to Departure Min:n Minimum nights Min Thru:n Minimum nights through Max:n Maximum nights Max Thru:n Maximum nights through Cut Off:n Cut-off days Here, n is the displayed number of nights or days. CTA and CTD may share one line. Labels can vary with the interface language. The grid shows minimum-night values only above 1, cut-off days only above 0, and Stop Sell/CTA/CTD only when true. Maximum-night values appear when present. An empty restriction line is not proof that every restriction is explicitly off: values may be missing, hidden or held at a related product level. Interpret the color legend carefully Grid legend: Available, Has Restrictions, Unavailable/Stop Sell and No Data. The legend labels describe the report's availability classification, not a live bookability check. Color and label What it tells you Green — Available The classifier found the rate/allocation information it uses and did not flag one of its unavailable or restricted conditions. It does not check every guest, stay or sales rule. Yellow — Has Restrictions The classifier detected a restriction, such as CTA, CTD, a minimum stay above 1 night, a positive cut-off, or a maximum-stay value from 0 through 27. Read the actual codes and related room/rate rows. Red — Unavailable/Stop Sell Allocation is non-positive, Stop Sell applies, or a related room/rate condition makes the product unavailable under this source's rules. It is not necessarily a Stop Sell on that exact row. Gray — No Data The classifier lacks sufficient rate/allocation information. The cell can still contain a rate, allocation or restriction; gray does not mean every field is empty. Colors can use parent-room or child-rate information that is not printed in the same cell. A room's classification can also consider configured child plans that are not currently displayed. Hiding Rates or Restrictions does not recalculate the background color. The rules differ by source. Stored report/image rows can use occupancy-rate parameters and related product data; Live Read's classifier requires both the main sell rate and allocation before it can classify the cell. A missing value can therefore produce a different color in different source sections. Read values and source labels together rather than interpreting color alone. Compare safely 1. Start with a short date range and one room type. 2. Select the sources and equivalent rate plans you want to compare. Apply any pending changes. 3. Check the source headings, product names/IDs, currency and occupancy basis. 4. Read the room row and rate-plan row together, including restrictions and any extra price lines. 5. Record the exact source, room, plan and date for any unexpected value. Check the relevant mapping and update status, or ask support to investigate. This workflow helps identify differences worth investigating. Matching values do not prove live retail parity; different values do not by themselves prove a failed update. Do not resend inventory simply because a cell is gray or two sections differ. Switch views, download or open the calendar - Grid: compare dates horizontally. - List: inspect detailed rows in the list format. - Excel: open the spreadsheet view; this button does not directly download a workbook. - CSV: download the selected report as comma-separated values. - New window: open a separate copy of the report. Grid already uses a standalone layout without the main navigation; this is not a different dataset. The control is omitted in a copy already opened as a new window. - Open calendar: open the selected property's editable calendar in a separate tab/window. It passes the loaded date range, not all the grid's source, room, rate-plan and data filters. Recheck the calendar's scope before making changes. Apply pending changes before switching views or downloading. If the page asks Apply pending filters before continuing?, choose Apply and continue to use them, or Cancel to remain on the current report. Cancel closes the navigation prompt; it does not reset your selections. What CSV includes CSV is a row-based report, not a copy of the colored grid. Its identity columns are PropertyId, PropertyName, ChannelId, ChannelName, RoomTypeId, RoomTypeName, RatePlanId, RatePlanName, ChannelRatePlanId, ChannelRatePlanName, followed by Date. The selected Data groups add: - Rates: SellRate. - Availability: Allocation and RoomsSold. - Restrictions: StopSell, MinNights, MinNightsThrough, MaxNights, MaxNightsThrough, CutOffDays, CTA and CTD. Timestamp remains at the end. Occupancy/extra-charge Rate Params are not included in CSV, and the colors are not exported. CSV uses the spreadsheet projection, which can combine room/rate values differently from the grid's separate lines. Do not treat blank RoomsSold as zero or a timestamp as proof of a fresh provider response. Troubleshooting An option is checked but its rows or dates are missing Look for Apply — reloads report, apply the selection and check again. Also check the other dropdowns: a selected rate plan cannot show under a hidden source or room. An offered option represents configured scope, not a guarantee of populated inventory. The report is empty or Apply is disabled Follow the selection warning. Choose at least one source, room type, data type and weekday. Check the date range and property. Rate plans may remain unselected for room-only results. If a source still has no rows, check that the channel and room mappings are set up and, for CRS, that the room and plan are enabled. A rate, restriction or occupancy line is blank Check Data, the source's supported fields and both the room and rate-plan rows. Do not replace an unknown value with zero or assume a blank restriction is an explicit No. The colors do not match the visible text Review the legend rules above. Hidden data and parent/child relationships can affect the classification. A restriction such as Max:28 can be printed without making the cell yellow under the maximum-stay threshold. A value seems stale or differs from an OTA website Confirm you are comparing equivalent products, occupancy and currency, and distinguish stored report values from Live Read. Reopening the grid does not certify a new upstream observation. Use update-status evidence and support investigation rather than assuming Refresh Data or an inventory resend is the correct remedy.
Create, share and schedule saved reports
Build a reusable report from several sections, choose its property scope, and optionally email it on a schedule. Before you start - Select the correct property and organization. Saved reports belong to an organization, not to the property currently selected in the navigation. - To change a report, you need Reservations - Actions or Channel Settings permission. You must also have access to every property the report covers. If the page says the report includes properties you cannot access, ask an Org Admin to make the change. - Personal reports are normally visible to their owner; Org Admins can also manage them. Organization reports are available to other users in the same organization. Sharing a report does not grant application access to its properties. - Decide who may receive the data before enabling email. Explicitly selected users and additional email addresses receive every selected property's report, even if those people cannot open those properties in the app. Open or create a saved report 1. Open Reports → Saved Reports → Manage Reports & Schedules. 2. Find your report and choose Edit. If it is missing, choose All in the Show control. 3. To create one, choose New Saved Report. 4. Enter its Name. Choose whether to show it in the Reports navigation and whether it is shared with the organization. 5. Choose Save & Continue. The report must exist before you can add sections, select properties or configure emailing. An existing report has three tabs: Report Settings, Properties and Emailing. The number beside Properties is the current selection count; Emailing shows On or Off. While editing, these badges describe your unsaved form, not confirmation of a successful save. Saved Report Settings with the Report Settings, Properties and Emailing tabs, sharing controls and three example sections Understand when changes are saved All three tabs use one Save. Adding, removing or moving a section, changing its settings, selecting properties or recipients, and adding, editing or removing schedule and email rows remain unsaved until you submit the form. - Save saves the form and returns to Saved Reports. - Open the arrow beside Save and choose Save & Refresh to save and reopen the editor. - View Report opens the last saved report in another tab. It does not save or preview pending edits. - Cancel returns to Saved Reports without submitting your current edits. If you are prompted about unsaved changes, stay on the page to keep editing or deliberately leave to discard them. Cancel does not undo an earlier successful save. - Switching tabs, opening a section's Settings, or opening an information icon does not save. If Save displays an error, read the message and inspect the relevant tab. Do not assume a selection that remains visible has been saved. After an uncertain connection or save result, reopen the report before repeating your edits. Choose and arrange report sections 1. On Report Settings, open Select a section to add. 2. Choose a section and click Add section. It is appended to the form. A section already present is marked (added) and cannot be added twice. 3. Where a row has a Settings button, expand it and complete the fields described in the reference below. Rows without that button have no editable section criteria on this screen. 4. Drag the handle at the left of a row, or use its up/down arrows, to change the order. 5. Use Remove section to take a section out of the form. This is not a separate save or confirmation page. Adding the same section again before leaving restores the removed row and its unsaved settings. 6. Choose Save & Refresh, then verify the sections, settings and order after reload. After a removal has been saved, do not rely on re-adding the section to restore its old criteria. Review its settings again. If another user changed the same report while you were editing, check the reloaded section list rather than assuming your original list was still current. Report Sections with the manual inventory updates Settings panel expanded to show Past Hours What the available sections cover Section Purpose and settings on this screen Channel Settings Current channel setup and mapping information. No section settings; not a live connection test. Opportunities Stored opportunity messages. Choose the exact message level. Reservations - Occupancy Captured reservation counts for the property's current period, not a room-occupancy percentage. No section settings. Reservations - Arrivals / Reservations - Departures Arrivals or departures for the property's current local day. No section settings. Reservations Captured reservations; the default section uses yesterday's local receipt date. No editable reservation-search criteria here. Reservations - Group Recent individual bookings meeting the room-count threshold. Set lookback and room count. Reservations - Discounted Recent bookings meeting the comparison threshold against stored channel net rates. Set lookback and percentage. Reservations - PMS Delivery Failures Recent failed PMS deliveries, with a default four-hour lookback. No section settings here; viewing the report does not resend anything. Update Processing Summary Pending/processing inventory work and recent outcome counts. No section settings. Inventory Updates - Manually Created by Users Recent user-created inventory requests. Set the lookback. A request appearing here is not proof of channel acceptance. Inventory Updates - Missing Availability Missing supported rate/allocation data. Set months, grouping, channels and room types. Missing data is not proof of deliberate stop-sell or sellout. PMS ARI Last Update Timestamp Stored inbound PMS-message time or supported monitoring evidence. No section settings or live refresh request. Daily Revenue / OTB; Length of Stay; Seasonal Trends; Booking Patterns — Cross-analysis; Rate Plan Performance; Cancellation Analysis; Channel Production; Booking Source Mix Current captured reservation production, using the stay-production fields below. These are not historical as-of snapshots. Booking Pace / Pickup Receipt-based retained-history reconstruction and movement. Uses its own date and cutoff fields. Portfolio Overview / Channel Net Revenue Property-level commercial summaries. Saved sections remain per-property even when emailed together. Mapping Coverage / Channel Health Stored mapping and processing evidence, with optional channel/state/flow filters. No remote check or repair is triggered. Internal Rate Consistency / Inventory Discrepancies / Restriction Coverage Stored outbound inventory evidence. Requires a compatible outbound inventory channel and a bounded product/date scope. Set property scope Open Properties and select the properties the report should cover. No properties selected does not mean email all properties. If you manage multiple properties, choose Report Mode: Mode Opening View Report in the app Scheduled email One Report Per Property Uses your current navigation property. It need not be selected for emailing. Sends a separate report for each selected active property. One Report For All Selected Properties Shows selected properties you can access together. With no configured selection, it falls back to your current property; a stale or inaccessible configured selection is not the same as intentionally selecting none. Combines the selected active properties' sections in one email. This does not turn the individual sections into consolidated portfolio totals. Properties tab showing Report Mode and the selected demo properties Use Search Properties to find names. Turn off Ticked only to see unselected properties. The All Properties checkbox selects or clears the enabled properties matching the search; clear the search first if you intend to affect the whole list. It ignores the Ticked only restriction and turns that switch off. The count still describes the whole list. Searching or hiding a property does not deselect it. For a combined report, turn Include All Users With Access To The Property to No on Emailing before switching away from One Report Per Property. That option is hidden in combined mode but a previously saved Yes must still be cleared; the incompatible combination is rejected on Save. Configure email delivery safely Keep Emailing → Enabled = No while building and checking the report. You can save sections, recipients and schedules while delivery is disabled. 1. Select the intended Properties and report mode. 2. On Emailing, choose Email Empty Reports. 3. Add or review the delivery schedules. 4. Select approved users and any additional recipients. 5. Choose Save & Refresh and review the reloaded values. 6. Open View Report to check the saved sections and data for the intended property scope. 7. Only when the scope and recipients are correct, set Enabled = Yes and save again to activate scheduled delivery. Saving Enabled = Yes does not send an immediate test email. Delivery also needs an eligible schedule, at least one selected active property, at least one report section, and eligible recipients. There is no Send now control on this editor. Email Delivery controls showing Enabled No and Email Empty Reports Yes Email Empty Reports defaults to No for a new report. No omits sections that report themselves empty; if none remain, that property's report is not emailed. Yes includes empty sections. This is not a web-view filter. A section can contain useful setup/status rows without any problem to report; Occupancy can also remain nonempty with zero activity. Do not interpret No as “only send when something is wrong.” Add, change or remove schedules 1. In Email Delivery Schedule, choose Add a schedule. 2. Set the hour from 1–12, a minute of 00, 15, 30 or 45, and AM or PM. 3. Select the weekday chips when delivery should run. Choose at least one day; a schedule with every day cleared will not become due. 4. Choose the time zone from the searchable selector. 5. Repeat for another delivery time if needed. 6. To remove a schedule, click its × button. 7. Save the main form and verify the rows after reload. A new row starts at 8:00 AM, every day, in your user time zone. Existing schedules retain their own time zone. The selected clock and weekdays belong to the selected zone; choosing another zone does not convert the displayed hour to an equivalent instant. The scheduled time is not a promise of exact mailbox arrival time. Inline daily schedule at 8 AM with all weekday chips selected and Mountain Time Use one row for a given time and time zone. To add weekdays at the same time, select them on that row instead of creating a duplicate. If a schedule was added or removed elsewhere while your editor was open, follow the row's message and reload the saved configuration before reconciling it. Older schedules may show an off-quarter-hour time or a damaged-schedule warning. Saving unrelated report fields leaves an untouched schedule unchanged. To repair or change that row, supply a valid time, quarter-hour minute and time zone, or remove it. Editing an older fixed-UTC schedule and successfully saving it converts that row to the selected local-time recurrence; review its weekdays and zone before saving. Choose recipients Control Who receives the report Include All Users With Access To The Property Available in One Report Per Property mode. Yes adds unlocked users in the organization with access to each particular property to that property's email. Defaults to No. User Emails Every checked eligible user receives every selected property's report, including properties they cannot open in the app. This explicit choice is separate from automatic property-user inclusion. Additional Emails External addresses that need not have a ChannelRUSH login. They receive the selected property reports too. The All User Emails checkbox selects or clears the offered users. Where a search is present, it applies to search matches; clear the search first to affect the full list. Removing a user's explicit check does not stop their email if automatic property-user inclusion still includes them. For Additional Emails, choose Add email, enter one plain address per row, and use × to remove a row. You can edit an existing address directly. Blank rows are ignored; surrounding spaces are trimmed and repeated addresses are saved once without regard to case. An invalid address blocks the form's save; correcting its syntax does not verify that the mailbox exists. All additions, edits and removals are saved with the main form. Email Delivery Recipients with automatic property users disabled, three demo users selected and one example additional address Check the saved result After Save & Refresh, check all three tabs—not only the tab you edited: - Report Settings: correct name, sharing, menu visibility, section order and criteria. - Properties: intended mode and checked properties. - Emailing: intended Enabled and Email Empty Reports values, schedule time/zone/weekdays, checked users and additional addresses. Open View Report only after saving. Check the property headings, included sections and the period each section actually reports. For rolling analytics, dates are resolved when the report runs using the property's local date; the schedule's clock zone does not redefine every section's data period. To compare with a separate interactive report, match explicit dates, feed, filters and any as-of cutoff. A saved configuration or a successfully opened web report does not establish that a scheduled email was sent or received. If an expected email is absent, use the checks below rather than repeatedly creating schedules or changing recipients. Field reference: Report Settings Field Meaning and new-report default Name Required, nonblank report name; surrounding spaces are removed. Identifies the saved report and emailed report. Show in Reports Nav Menu Defaults to Yes. Eligible reports with at least one section appear under Reports → Saved Reports. No hides the navigation shortcut; it does not delete the report. Shared with organization Yes - Org Report makes it available to the organization. No - Personal Report is the default and keeps it personal, subject to Org Admin access. This is not publication to the internet and does not restrict explicit email recipients. Report Sections One row per section type, in output order. Its Settings fields apply whenever that saved section runs. Add/remove/order changes need Save. Opportunities, group, discounted and manual-update sections Section / field Meaning and default Opportunities — Minimum Level Blank includes all returned levels. Choose Info, Warning or Critical to match that exact level—not that level and every higher one. Reservations - Group — Past Hours Default 24. Looks back over captured reservation creation times. Enter a sensible positive whole number. Reservations - Group — Number of Rooms Default 6. Minimum room entries in one qualifying booking, including new/modified reservations. It does not combine unrelated bookings into a group block. Reservations - Discounted — Past Hours Default 24. Recent captured reservation window. Reservations - Discounted — Percentage Default 10. Minimum detected nightly discount against the stored channel net rate; missing/nonpositive comparison rates are unavailable, not a zero discount. It does not identify which promotion caused a discount. Inventory Updates - Manually Created by Users — Past Hours Default 24. Looks back over creation times of user-created inventory requests. These legacy lookback and threshold fields accept whole-number input but do not consistently enforce business ranges. Use positive lookbacks and meaningful room/percentage thresholds; do not use negative values to mean “all.” Inventory Updates - Missing Availability Field Meaning and default Number of Months Default 18. Future scan horizon, limited by each channel's supported advance period. Values above 36 are capped at 36; use a positive number. Group By By Channel or By Room Type ; defaults to By Channel. Changes grouping, not which inventory is checked. Channels Select a subset, or all. No boxes checked also means all , including future additions. Room Types Select a subset of the offered standard room types, or all. No boxes checked also means all , including future additions. The unusual no-selection-means-all rule applies only to these section channel/room lists. It does not apply to report Properties or User Emails. Options can come from properties available to the editor; confirm that the chosen subset makes sense for each property that will run the report. Stay-production sections The following fields are shared by Daily Revenue / OTB, Length of Stay, Seasonal Trends, Booking Patterns — Cross-analysis, Rate Plan Performance, Cancellation Analysis, Channel Production and Booking Source Mix. Field Accepted values, defaults and effect Stay from / Stay through Enter both dates or leave both blank. Inclusive, ordered range of at most 366 days. Blank uses the property's local run date and Rolling days. Explicit dates stay fixed while the captured reservation state can still change. Rolling days (1–366) Default 30. Must remain in range even when explicit dates are entered. Reservation feed ID (1 = booking engine) Positive source/feed ID; default 1. Not a property ID. A valid number alone does not prove data coverage. Channel room ID (optional) Exact source room identity, up to 200 characters; blank does not narrow by room. Not a standard-property mapping row ID. Channel rate-plan ID (optional) Exact source rate-plan identity, up to 200 characters; blank does not narrow by rate plan. Currency (optional) Blank keeps currencies separate; otherwise a currency filter, trimmed and uppercased, up to 10 characters. No automatic currency conversion. Seasonal grouping month , weekday or weekend ; default month . Affects Seasonal Trends, not the other sections merely because they show the shared field. Seasonal prior-year alignment none (default), calendar or weekday . Seasonal Trends only. Compares current captured prior-period production, not historical on-the-books state. Comparison feed ID (0 = none) Rate Plan Performance only. Default 0; otherwise a positive feed different from the primary. Comparison data stays separate rather than being merged or deduplicated. Include canceled business as separate rows Defaults off where offered. Cancellation Analysis, Rate Plan Performance, Channel Production and Booking Source Mix instead always include active and canceled business in their stay-cohort denominator. These are not cancellation-event counts. Daily OTB measures captured stay-date nights/value, not posted accounting revenue. Length of Stay uses full-stay buckets with nights clipped to the selected period. Booking Patterns uses the first retained receipt for its booking-window analysis. Source reports do not assume bookings across feeds have been deduplicated. Booking Pace / Pickup Field Accepted values, defaults and effect Reservation source ID Positive source ID; default 1. Stay days (1–93) Default 30. Validated even with explicit dates. Movement days (1, 3, 7, 14, 30) Choose exactly one of these values; default 7. Controls the detailed movement window. Stay start / Stay end Both blank or both supplied. Inclusive ordered range, at most 93 dates, years 2000–2100. Blank uses the property's rolling period. As-of with UTC offset or Z Blank uses execution time. Otherwise enter a timestamp with an explicit offset or Z, such as 2026-09-08T12:00:00Z ; it must not be in the future. Maximum 64 characters; year 2000 or later. Source room ID / Source rate-plan ID Optional exact source identities, up to 200 characters each. Currency Optional, up to 10 characters, trimmed and uppercased. Currencies are not converted. Prior-year alignment (history gated) Calendar (default) or Weekday. Selecting an alignment does not create missing qualified same-time-last-year history. This is retained receipt-based reconstruction, not a guarantee of original sale time or exact database-commit history. Incomplete history is not zero movement. Portfolio Overview / Channel Net Revenue Field Accepted values, defaults and effect ChannelId Positive reservation source ID. Default 1 for Portfolio; 572 (Mirai) for Channel Net Revenue. Net commission deduction is qualified for stored Mirai-supplied commission, not every accepted source ID. Days Default 30; 1–366. Rolling period when dates are blank; validated even with fixed dates. OpportunityDays Default 30; 1–90. Opportunity-message creation lookback for Portfolio. Still validated but does not change Net Revenue. Start date / End date Both blank or both supplied. Inclusive ordered range, at most 366 dates, years 2000–2100. Portfolio uses stay-date nightly production; Net Revenue uses a whole-booking arrival cohort, not clipped nightly net revenue. Currency Optional, up to 10 characters, trimmed and uppercased. Applies to both reports despite the shared “geography: Portfolio only” label. Country Portfolio only: optional exact property country code, up to 10 characters, trimmed and uppercased. Leave blank for Channel Net Revenue. City Portfolio only: optional exact property city, up to 100 characters, trimmed and case-insensitive. Leave blank for Channel Net Revenue. Include canceled separately Defaults off. Shows canceled business separately when enabled. A combined saved-report email contains per-property sections. Use the separate interactive Portfolio report for consolidated portfolio totals. Mapping Coverage / Channel Health Field Accepted values, defaults and effect Channel ID (0 = all) Default 0; nonnegative integer. A positive ID narrows each property's channels. Terminal history days (1–90; Health only) Default 30. Channel Health's terminal-request creation lookback; current pending/processing work is not limited by it. Keep a valid value for Mapping Coverage too. State (blank = all) Optional exact, case-sensitive state text, up to 60 characters. Flow / kind (blank = all) Optional exact, case-sensitive row kind, up to 60 characters. For Mapping Coverage, state values include Disabled, Missing target, Missing virtual parent, Not set up, Unknown, Mapped and Intent unknown. Kinds are Room mapping, Rate mapping, Hotel room coverage, Hotel rate coverage, CRS room and CRS rate. For Channel Health, states include Failed requests, Disabled with pending work, Pending work, Unsupported, Disabled, Not set up, Unknown, Monitoring evidence, Idle, Idle / no retained activity and Review evidence. Flows are Outbound inventory, Inbound PMS inventory, Inbound PMS monitoring and Reservation delivery. These text filters are not fuzzy searches. A typo can produce no rows; empty output is not proof of healthy distribution. Internal Rate Consistency / Inventory Discrepancies / Restriction Coverage Field Accepted values, defaults and effect Channel Required outbound inventory channel. The editor can suggest the first available choice; verify it for every selected property. A choice appearing in the list does not prove it is configured for each property. RoomTypeId / RatePlanId Nonnegative channel-setting mapping row IDs; 0 means all matching mappings. These are not standard-property IDs or external channel room/rate strings. Specific mappings are property/channel-specific. Ask support if you do not know the correct mapping identity. Start date / End date At most 31 dates, ordered, years 2000–2100. Blank start resolves to the property's current date; blank end resolves to six days after the resolved start. Unlike the other families, these fields can be supplied one at a time. Field (blank = all) Optional exact case-sensitive field text, up to 120 characters. Use a field relevant to the selected section. State (blank = all) Blank or one of the exact states listed below. Standard field names include Sell rate, Net rate, Allocation, Min stay, Max stay, Min through stay, Max through stay, Closed to arrival, Closed to departure, Cutoff days and Stop sell. Specialized rate-dimension names must match the actual evidence field; do not guess them. State values are Consistent, Different values, Pending difference, Unknown, Currency not comparable, Unsupported, Not applied, Restriction recorded and No restriction recorded. - Internal Rate Consistency includes rate fields only. - Restriction Coverage excludes rates and Allocation. Its restriction states describe explicit recorded requested values after support/applicability checks; they do not establish effective channel restrictions or requested-versus-remote agreement. - Inventory Discrepancies can include all fields and states; it is not automatically limited to differences. An irrelevant but accepted Field/State combination can return no rows. These reports read stored images, not live OTA prices. Keep the scope within 500 mapped products, 3,100 product-days and 100,000 projected rows. Saving criteria does not run the report or establish that its selected scope fits those limits. Specific mapping IDs should not be reused blindly across properties. Common problems Symptom Check and safe next action Properties and Emailing are unavailable on a new report Enter a name and use Save & Continue first. If saving is refused, resolve the displayed restriction rather than repeatedly submitting. Demo logins cannot save these settings. Changes disappear after reopening Section edits, schedules and additional emails now require the main Save. Check for validation errors, then save and reload. Do not rely on the tab badge or current row list as proof of persistence. Save reports an invalid schedule Read the message beneath the row on Emailing. Supply a valid hour/minute/AM-PM/zone. For a duplicate clock/zone, use one row and select its days. Save complains about property-user inclusion in combined mode Switch to One Report Per Property, set automatic property-user inclusion to No on Emailing, then choose the intended combined mode and save. Review recipients again. A section cannot be added because it needs an outbound inventory channel Ask an authorized administrator to review channel setup. Do not choose an unrelated channel merely to bypass the requirement. A report covers properties you cannot access Ask an Org Admin to update it. Do not remove hidden properties to work around access restrictions. Report is missing from the navigation Check Show in Reports Nav Menu, report ownership/sharing and that it has at least one section. Find it through Manage Reports & Schedules with All selected. Expected email is absent Reopen the saved report. Check Enabled, selected active properties, sections, recipients, schedule days/time/zone and Email Empty Reports. Verify the recipient address and check the mailbox's spam handling. Do not create duplicate schedules as a retry. A user still receives email after being unchecked Check automatic property-user inclusion and Additional Emails as well as the explicit user list. A report is empty or one section fails Check its own source/feed, dates, property/channel setup and field/state filters. A configuration save is not a successful data query. Narrow an evidence report's date/product scope if it exceeds its bounds. If the problem remains, contact support with the report name, property/organization, affected section or schedule, action time and time zone, and exact error text. Do not send passwords or unnecessary guest data.
Inventory Load
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. 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. 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.
PMS Overrides
Summary For one reason or another, you may wish to override the data flowing from your PMS to your OTAs. You can do this by issuing updates via the ChannelRUSH Extranet. Be careful, though, when an 'override' is issued, it effectively blocks the PMS from updating that item (i.e. rate, min nights, max nights, etc) moving forward. It can get tricky to keep track of - i.e. rate overrides issued more than 6 months ago, then wondering why the PMS rates are not flowing through to the OTAs for those dates and room types. PMS Override Settings On your PMS settings screen (Admin -> Settings -> Channels), you will see a section named 'User PMS Override [Checked = User Override of PMS Allowed]'. image When an item is checked, any updates issued for it manually by a user in the ChannelRUSH Extranet will override or block the PMS from updating that information until that block is removed. If the item is not checked, you can still issue updates for it via the ChannelRUSH Extranet, although the PMS can still send updates for those room types and dates moving forward. So the PMS is not 'overridden' or 'blocked' - it can issue updates that overwrite yours. This can create its own confusion - i.e. the last to update the data wins. You updated Min Nights = 3 today, but the PMS updates Min Nights = 1 tomorrow, etc. View Existing PMS Overrides To view existing PMS overrides - go to Reports -> Rates & Availability Report. From there, under the 'PMS' section, select the channel that ends with ' - UI Override'. 'UI' stands for 'User Interface', representing overrides issued manually by a user in the ChannelRUSH Extranet. 💡 For clarity, it might be best to unselect all items under 'Channels' by clicking 'Channels' to view only the UI Override information per date and room type. Once loaded, you can view the information overriding or blocking the PMS per date and room type. Removing PMS Overrides To remove PMS Overrides for a certain item - i.e. rates, go to the PMS settings screen (Admin -> Settings -> Channels), then locate the 'User PMS Override [Checked = User Override of PMS Allowed]' section. image When you uncheck a selected item and save the settings, all overrides issued are deleted for that item. For example, you would uncheck 'Rates' and then save the settings to remove all rate overrides. This will delete ALL rate overrides previously issued. You can put the rate override back after this if you wish by selecting the 'Rates' checkbox and saving the settings. This doesn't restore any of the rate overrides you have previously issued (they were just deleted when you unchecked the box and saved the settings) - but this restores that rates issued after this point will override and block the PMS again. While the overrides or blocks have been removed, the PMS information still needs to be sent or synchronized with the OTAs. Inventory Load - Sync'ing the PMS with the OTAs After clearing the PMS overrides and removing the blocks, you will need sync the PMS information with the OTAs. You can find instructions on how to process a full refresh of inventory here: Inventory Load / Full Refresh Inventory Load / Full Refresh
Reservation Delivery Check - Undelivered Reservations
Reservation Delivery Check - Property Name - # Undelivered If you receive an email regarding reservations that haven't been delivered, it means that all attempts to send the reservation to the property, whether via email or electronically to the PMS, have failed. Currently, the reservation exists on the OTA and in ChannelRUSH, but not at the property. The first item is to diagnose why all delivery attempts have failed - is it an email server outage? The Internet is down at the property, and ChannelRUSH is unable to connect to the PMS? Once this is identified and fixed, you can resend the reservation. Resend Reservation Once the issues affecting email or PMS delivery are fixed, you can resend the reservation either via email or to the PMS. Go to Reservations -> Search, and then you click on 'Email' or 'PMS' to initiate the new delivery attempt. image
Investigate reservation delivery failures
Reservation Delivery Failures property report with Past Days, View Report, HTML, Excel, CSV, New window and Help Property report with a seven-day lookback and no matching delivery failures. Use the Reservation Delivery Failures report to find unsuccessful reservation-delivery requests, share the details and decide what needs investigation before taking corrective action. Before you start Sign in with access to the property you want to check. Select that property in the property selector. You do not need Org Admin access specifically to view this report. This report counts delivery requests, not unique reservations. Several requests can relate to the same reservation. A failed request does not, by itself, prove the reservation is missing from your property management system (PMS). Open and run the report 1. Open Reports → Home. 2. In the Reservations section, select Delivery Failures. 3. Enter a positive whole number in Past Days. The default is 1; increase it when investigating an older delivery issue. 4. Select View Report to apply the lookback to the selected property. The lookback uses the delivery request's creation date, not the guest's arrival date. Treat it as a date-based lookback, not an exact rolling number of hours. Running the report does not resend reservations or change their delivery status. You can run it again to refresh the results. New window opens the report without the main navigation and retains the applied lookback. Help opens this guide in a new tab. Read the results The number before Failed Deliveries is the full count of matching unsuccessful delivery requests. The in-app list shows the newest requests first, up to a safety limit of 10,000. If more match, a Listing the newest … notice points you to View all matching deliveries. Scheduled email reports remain limited to the newest 50 requests; their total can be larger. Each row shows Channel Reservation ID | Status, with PMS: … underneath when a PMS reference is available, followed by Source, Destination, Timestamp, and the workflow links. Two values need particular care: - Status is the reservation state, such as New, Modified, or Canceled. It is not the delivery outcome: the requests in this report are already filtered to unsuccessful deliveries. - Timestamp is the delivery request's last-updated time, displayed in your signed-in timezone. It is not the creation date used by Past Days. A recorded error message appears beneath its request. View all matching deliveries opens Delivery Status with the property, unsuccessful status and start date carried over. That screen is paginated; its first page is not necessarily the complete list. Share the list with your PMS provider Use the controls beside View Report to hand the failures to whoever needs to enter or investigate them: - Copy to Clipboard (in the HTML view, beside Failed Deliveries) copies a plain-text list you can paste into an email or support ticket: the property, the Past Days lookback and count, then for each failure its reservation ID, PMS ID, status, source, destination, timestamp and error. - View: Excel shows the same failures as a spreadsheet, one row per request: ReservationId, ReservationPmsId, ReservationStatus, SourceChannelId, SourceChannelName, DestinationChannelId, DestinationChannelName, Timestamp and ErrorMessage. Use the spreadsheet's File → Save As to keep a copy. - Download: CSV downloads those same columns as a file that opens in Excel or any spreadsheet program. These outputs use the same request selection and 10,000-row limit as the HTML list. Run View Report after changing filters, then choose your output. Timestamp uses your signed-in timezone; Excel and CSV write it year first (for example 2026-10-16 14:12:34). IDs and error text can be sensitive, so review the output before sharing it and send it only to people who need it. All your properties in one report Organization Reservation Delivery Failures report with Properties: All and output controls Organization report with all offered properties selected and no matching delivery failures. Open Org Admin → Reports and, under Reservations, select Reservation Delivery Failures. This report covers the organization of the currently selected property. Org Admins can report on all active properties in that organization; other users are limited to their assigned active properties in that organization. Each failure names its property beneath the reservation information: - Open Properties, search by name and tick the properties to include. Select all toggles the properties currently shown by the search; it does not clear selections hidden by the search. Select View Report to apply your choice. With nothing ticked—or every property ticked—the report covers all properties offered by the filter. - Excel and CSV start each row with PropertyId and PropertyName, and Copy to Clipboard starts each failure with its property. - View all matching deliveries opens the organization's Delivery Status page with the report's property scope, unsuccessful status and start date. Open the report from Delivery Status On Reservations → Delivery Status (or the organization's Delivery Status page), set Status to Unsuccessful and select Search. A Reservation Delivery Failures link appears in the top right when that scope can be represented by the report. It carries the property or property selection and converts Start Date into a day lookback, defaulting to 30 days when no Start Date is set. Other Delivery Status filters are not all carried over, so the result counts can differ. If you switch organizations without selecting a property, the link may disappear; select a property in that organization first. Use the reservation shortcuts Use History | Email | PMS | View in the Actions column to investigate or act on a reservation. Each link opens in a new tab, keeping the report open. PMS appears only when reservation delivery is enabled for the property. View opens the reservation version associated with the failed request in a new tab. History, Email and PMS use the latest reservation version: - History: review the reservation history. - Email: open Email Reservation. Enter or select the intended recipients and check the Email field before choosing Send. Opening the form does not send anything; Send queues a new email delivery. This is not a PMS retry. - PMS: open Send Reservation to PMS. This link appears when the property has reservation delivery enabled. Review the listed destinations before choosing Send: it queues new delivery requests to all currently enabled PMS destinations, not just the destination on the failed request. Opening the form does not send anything. Check the destination system before submitting an email or PMS resend. Use Cancel if you are not ready to send. These links navigate to existing workflows; they do not repair the failed request merely by being opened. A send confirmation means a new delivery request was queued, not that the recipient received the email or the PMS accepted the reservation. Check the new attempt in Delivery Status and confirm the result in the destination system. The report opens Delivery Status filtered to unsuccessful requests; change that status filter when looking for a successful new attempt. An older failed request can remain listed after a separate attempt. On Delivery Status, Status describes delivery processing, and the displayed time is the request's creation time—not the report's last-updated Timestamp. Check the result and follow up safely No Delivery Failures means no matching unsuccessful requests were found for the selected property scope and lookback. It does not prove that every reservation was delivered or that older failures have been resolved. For a listed failure, check the reservation and recorded error, then confirm the reservation's current state in the destination system. Although the report displays a manual-entry warning, verify whether the reservation already exists before entering it or requesting a resend. Do not assume repeated sends are duplicate-safe. The report itself does not repair delivery. A failed request alone cannot establish the outcome of a separate delivery attempt. If you cannot establish what happened, contact support before repeating the action. Common problems - The report is empty, but you expect a failure. Check the selected property and increase Past Days if needed. If a known issue still cannot be located, give support the reservation reference and approximate delivery time. - The list says "Listing the newest …". A very large lookback can match more failures than one page lists (over 10,000). Shorten Past Days, or use View all matching deliveries and the paging controls on Delivery Status for the rest. - The reservation says Modified or Canceled. That describes the reservation, not successful delivery. Read the recorded error and check the corresponding change in the destination system. - The PMS link is missing. It is shown only when reservation delivery is enabled for the property. Ask your administrator to check the PMS delivery setup; using Email does not enable or repair PMS delivery. - You cannot access the property or report. Ask your account administrator to check your property access. Contact support if access is confirmed but the page still cannot be opened. When escalating, include the property, source channel, destination, reservation reference, selected Past Days, relevant time and timezone, and error text. Do not include passwords, payment details or unnecessary guest information. Related - Reservation Delivery Check — Undelivered Reservations - Reservations
Check reservation delivery status
Find delivery attempts for a reservation, check their destinations and processing statuses, and gather the details needed to investigate any failures. Before you start Searching does not send or resend a reservation. Submitting a new send requires the Reservations role or higher, or the Reservations - Actions permission. Find delivery attempts 1. Select the property in the property selector. 2. Open Reservations → Delivery Status. 3. Enter the complete channel reservation number in Reservation ID to investigate one booking. Leave it blank to review multiple bookings. This field does not search PMS confirmation numbers. Numeric searches can also match internal IDs: confirm the displayed channel reservation number and source channel before investigating or sending. 4. Choose Delivery Type → PMS or Email to narrow the search down, or leave All selected. 5. Choose Delivery Status. Use Unsuccessful to find failed requests, or All to compare failures with later attempts issued after the failure. 6. Add Channel, Start Date or End Date only when needed. Channel matches a request's source or destination. Dates refer to when the delivery request was created - not arrival or departure. After entering a date, leave the field before searching. 7. Select Search. Check that your chosen filters remain displayed. Delivery Status filters with Unsuccessful and PMS selected, plus Search and Clear Search Filter controls Example: search for unsuccessful PMS delivery requests at the selected property. Use Clear Search Filter to remove the filters while keeping the selected property. With no dates entered, the search has no date restriction. More filters narrow the results. Read the result Each entry is a delivery request, not a unique booking. One reservation can have several requests or destinations (i.e. one request for the PMS, 3 requests for different email addresses). - Reservation ID / Status identifies the channel reservation and its booking status, such as new, modified or canceled. Select its reservation number to view that version of the reservation. - Delivered To identifies the destination channel or email address. The heading does not mean delivery succeeded. - The Status beneath the entry is the delivery-processing status: Pending, Processing, Successful or Unsuccessful. Do not confuse it with the booking status above. Pending and Processing are not completed delivery confirmations. - ID beneath the entry identifies the delivery request. The adjacent time is its creation time, displayed in your user time zone—not its completion time. Successful records a successful processing outcome for that request. Check the correct destination and, where necessary, confirm the booking in the PMS or the email's receipt; an email success does not establish PMS delivery. Results are normally shown in order of newest requests, up to 50 per page. When available, page forward » opens older requests and page back « returns to newer requests. A reservation ID search can return more than 50 matching requests. There is no overall total on this screen. Investigate a failure Read the error shown with an unsuccessful PMS request. Open History for reservation history, or Logs when available for delivery-request details. Times inside Logs are UTC, unlike the user-time-zone request time on Delivery Status. Email entries can show Delivery Receipt or Opened Receipt when that information is available. With Delivery Status → Unsuccessful applied, a Reservation Delivery Failures Report link appears at the top right. It provides a separate investigation/export view. It carries the property and a lookback derived from Start Date—30 days when Start Date is blank. It does not preserve every filter, so its results can differ. The report's Timestamp is the request's last updated time, unlike the creation time shown in Delivery Status. Do not resend merely because an old failed request remains. Check later attempts with All statuses and confirm the destination's current state first. Opening Email or PMS displays a send form; submitting it creates new requests. PMS → Send uses the latest reservation version and all currently enabled PMS delivery destinations, not only the failed destination. Repeated sends can create additional requests. Email does not repair PMS delivery. Common problems - No rows: check the property and complete channel reservation number, then clear restrictive filters. If a request near a date boundary is missing, remove the dates and search by reservation number. An empty list does not prove delivery succeeded. Contact support if an expected request remains absent. - A date is missing after Search: re-enter it, move out of the field and search again. Check the retained filter before interpreting the result. - PMS or Logs is missing: these links depend on configured delivery and available request logs. Use History and ask your Org Admin or support if the expected path is unavailable. - A failure remains or a booking is still missing: provide support with the property, channel reservation number, destination, request ID, status/error text and time zone. Do not include passwords, payment details or unnecessary guest information. Related - Investigate reservation delivery failures - Find reservations and open their send forms
Update rates, availability and restrictions in the calendar
Use Calendar Update to change rates, available rooms and booking restrictions for individual dates, either through your property's master values or for a particular channel product, then check the resulting update requests. Before you start - Select the correct property and open Updates → Calendar. The page heading is Calendar Update. - You need property access and the appropriate update permission: rates, availability (including Stop Sell), or restrictions. Available fields also depend on the property's enabled features and the channel's setup, mappings and supported updates. - Decide whether the change is for the room type, one rate plan, or one channel product. These are different scopes even when they show the same field names. - If a PMS supplies inventory, review the property's PMS override settings. A manual change can prevent later PMS values from replacing that field; where overrides are disabled, a later PMS update can replace your manual value. Do not assume a channel-specific price or every special mapping creates a lasting PMS override. Every changed calendar cell submits individually. There is no final Save button. A dropdown submits when you select a different value. A text cell submits when you finish the change by leaving it or pressing Enter. Clicking another cell or a display control can therefore submit the text edit you were making. Choose the intended scope and value before touching an inventory cell. 1. Choose dates and visible fields 1. Confirm the property in the selector at the top. 2. Set the Date Range, or choose Month / Year. Completing the date selection reloads the calendar automatically. Wait for the grid and check the actual date headings before editing. 3. Select the required Room Types. Select a Rate Plan as well if you want its separate section. A room type must be visible for its rate-plan sections to be visible. 4. Use Days to show the weekdays you need. Use Options to show Rates, Allocation, Stop Sell, Min Nights, Max Nights, CTA, CTD or Cut Off Days. These selections show and hide existing rows or date columns immediately; they do not submit inventory updates. 5. To inspect channel-specific values, leave the required channel selected under Channels, then expand [ + ] Channels beneath the relevant room type or rate plan. Room Types and Rate Plans display selectors with one room type and Standard rate plan selected Selecting Standard reveals its own section. It does not make the room-type master cells Standard-only controls. Use the left and right arrows beside a section's date headings to move the whole calendar back or forward by the displayed date-range length. Check the new dates after navigation. For a wide range, scroll horizontally or shorten the range so you can keep the field label and date together. Display selections are not a sending checklist. Hiding a channel or rate plan does not exclude it from a master update. Clearing a display selection hides its rows; it does not clear the stored values or cancel changes already submitted. 2. Choose the correct editing level Master room-type section The section headed with the room type alone contains the master controls for that room type. A master edit can update eligible products across configured channels, regardless of which channels are visible. A room-type master edit also updates that room type's standard rate-plan values, including rate plans hidden by your display selections. For rates, configured rate-plan calculations can produce prices different from the room-type price. Mapped channel products, including eligible virtual-room mappings, can receive the resulting updates. Review configured product relationships rather than treating one visible row as the complete effect. Use this level only when the broader room-type change is intended. For example, to change Standard but not Non-Refundable, do not enter the value in the room-type master row. Master rate-plan section Select the rate plan under Rate Plans, then find the heading containing both the room type and Rate Plan — [name]. Its master cells change that room/rate-plan combination across eligible configured channels. This is narrower than the room-type master section, but it is still not channel-specific. Channel mappings, rate calculations and configured relationships can affect the resulting values. If you see Unmapped, it groups channel rate plans without a standard rate-plan mapping; it is not another ordinary named standard plan. Expand its channel rows and identify the actual channel product before editing. Channel-specific section Expand [ + ] Channels beneath the intended room type or rate plan. Read the complete heading: room type, rate plan where present, channel name, and any Virtual Room Type label. Edit the cell in that channel's section, not the master cell above it. The channel section uses that channel's supported fields and product level. One channel may expose allocation at room-type level while prices and restrictions appear under rate plans. Some channels show additional occupancy or other rate fields. A channel price change can also calculate its enabled additional rate values. Expanded Booking.com Standard rate-plan section with its own date columns, Sell Rate and supported restrictions This is a channel-specific rate-plan section. Its fields differ from the master section. Blank values are shown here; they do not mean the channel is open, closed or successfully updated. Rows received from a PMS can be read-only. Other channel cells can also be read-only because of permissions or the property's update mode. Ask your administrator to check the intended setup; do not use a broader master edit to work around a read-only channel row. 3. Make an individual-date change Change a price 1. Locate the intended master or channel section and the correct date column. 2. Find Sell Rate, or the specifically labeled additional rate you intend to change. Confirm the property's/channel's currency and pricing setup; this is a price, not an amount to add or subtract. 3. Enter the new positive price. Use the decimal separator shown by your interface, without a currency symbol. The rate must meet the room type's configured minimum allowed rate. 4. Press Enter or move out of the cell to submit that edit. 5. Read any returned message and inspect related displayed prices. Then follow Check the result below. For example, entering 150.00 requests a sell rate of 150.00 in the applicable currency. It does not increase the previous price by 150.00. Master-to-channel markup, margin, rounding and rate-plan calculations can make destination prices differ from the value you entered. Do not use a zero rate to close sales; use the appropriate Stop Sell or Allocation control instead. Change available rooms or close/reopen sales 1. Identify the correct product, level and date. 2. To replace the available room count, enter a whole number in Allocation, then press Enter or leave the cell. 5 means a requested allocation of five, not five additional rooms. 3. To apply a sales closure, select Yes in Stop Sell. To remove that stop-sell restriction, select No. The dropdown change submits immediately. 4. Check Allocation and Stop Sell together, then verify the requests and affected destinations. Changing master Allocation to 0 also sets Stop Sell to Yes. Increasing Allocation above zero automatically sets Stop Sell to No only when the property's automatic-stop-sell setting is enabled. Allocation changes in channel sections can also interact with this setting. Check Stop Sell explicitly when reopening. A positive allocation or Stop Sell No does not remove minimum stays, arrival/departure closures or other restrictions, and does not by itself prove that a room is bookable. Set or remove a booking restriction 1. Show the relevant option under Options. 2. Check the full row label. Min Nights Arrival and Min Nights Thru are different restrictions; the same distinction applies to maximum stays. 3. Enter the intended whole-number limit, or choose Yes/No for an arrival/departure closure. Text edits submit on leaving the cell or pressing Enter; dropdown changes submit immediately. 4. Use the explicit removal value from the field reference below when removing a restriction. Do not erase a cell to remove it. 5. Check the other restrictions for the same dates and verify delivery. To restrict arrivals on a Friday to stays of at least three nights, use Min Nights Arrival = 3 on that Friday. To apply a three-night minimum to stays that include Friday night even when they arrive earlier, use Min Nights Thru = 3, where supported. These examples illustrate the difference; they are not recommended settings for every property. Correct an edit safely Before a text edit submits, Escape restores the cell's remembered value. Clearing a cell and leaving it also restores that remembered value rather than deleting inventory. A blank dropdown option, when present, is not a remove action. The remembered value is not a server-side undo point. The page remembers a newly entered value before it knows whether the request succeeded. After submission, Escape or clearing the cell may restore that attempted value, not the previously saved value. Neither action reverses an update already submitted. If you entered the wrong value or saw an error, stop and check stored values, PMS overrides and update requests before making another change. Entering the old value again is a new update, not a rollback. 4. Check the result A value remaining in a calendar cell, a changed related cell, or a colored line beneath a date does not confirm delivery. Calendar values are stored inventory information, not a live read of the channel's current sales screen. 1. Open Updates → Status for the same property. 2. Start with Status = All so successful as well as pending or unsuccessful requests remain visible. Select Channel, Room Type and Rate Plan as needed. For a master edit, inspect all affected destinations rather than only the channel you had displayed. 3. Open More Filters and select Source = UI Calendar to look for calendar-originated requests. 4. If narrowing by affected inventory dates, choose Start/End Date under Date Range and enter both the first and last affected dates. This finds requests whose inventory date ranges overlap those dates. Creation Timestamp and Processing Timestamp concern request activity, not stay dates; use the matching timestamps in the results when identifying the attempt. 5. Click Search. Changing the Status filters alone does not run the search. Go belongs to request actions such as Retry, not filtering. 6. Match the product, affected dates, requested values, source, Created, Last Run, request ID and reported Status. Do not mistake an older successful request for the edit you just made. Result What it tells you Next step Pending The request is waiting to be processed. Check it again; do not assume delivery has completed. Processing Processing is underway. Wait for the resulting status and investigate if it does not progress. Successful ChannelRUSH reports that this request processed successfully. Check every affected destination. Confirm the channel's own inventory if you need to establish what is currently for sale. Unsuccessful The request did not complete successfully. Review its details or Logs and resolve the cause before another edit or retry. No matching request Your current search found no request. Broaden the filters and check local inventory/overrides. It does not prove that nothing was saved. If you cannot find a request, remove unnecessary product/date filters and search again. Selecting only some of Rates, Availability and Restrictions can hide records, especially older requests without detailed changed-field information; all three or none avoids that data-type narrowing. Include Archived if you are looking for an archived request. Do not use Retry merely to find out whether the original edit worked. An error or an empty Status result does not guarantee rollback. Master values and applicable PMS overrides can be saved before later channel-request checks fail or reject a request. Some destinations may have progressed when another did not. Reload and inspect the affected inventory as well as Status; if the saved scope is unclear, ask support to confirm it before resubmitting. Field reference Display and navigation controls Control What it changes Defaults and useful details Property selector The property whose calendar you are viewing. Confirm it before every edit; identical room names can exist at different properties. Date Range The dates loaded into the calendar, including both endpoints. A fresh default range starts on the property's current date and covers 14 days. Completing a new range reloads the page; check the resulting headings. Month / Year Loads a calendar month. It is an alternative to entering a date range, not a separate inventory submission. Days Shows or hides weekday columns within the loaded range. All weekdays are initially selected unless saved preferences or the current page selection say otherwise. The Days heading toggles the group. Options Shows or hides types of inventory rows. Rates, Allocation and Stop Sell initially show; the other options initially hide. The Options heading toggles the group. Room Types Shows the selected room-type sections and their visible plans. Initially selected. Clearing all room types hides their grids; it does not select all products for updating. Rate Plans Shows separate plan sections under selected room types. Initially unselected. Select the named plan to use its own master or channel section. Unmapped appears only when relevant to the property's mappings. Channels Shows the selected channel rows inside expanded sections. Setup channels are initially selected. This is a display filter, not the destination list for master updates. Group checkbox and selection count Selects/clears a display list and shows how many items are selected. A partially selected group shows a mixed state. These are display selections, not inventory values. [ + ] Channels Expands/collapses channel rows for that particular room or plan. The channel, room, rate plan and relevant Options must also be selected. Left/right date arrows Loads the preceding/following date range of the same length. Moves the calendar, not the inventory. Verify the dates after navigation. The browser remembers display selections for your user and property, so your initial selections can differ from the defaults above. Do not rely on yesterday's visible rows as today's update scope. Rates, allocation and restrictions The fields below appear only where supported and enabled. The Options names are shorter than some grid labels. Selecting Min Nights reveals supported Arrival and Thru rows; Max Nights works the same way. CTA shows Closed To Arrival, and CTD shows Closed To Departure. Master room-type calendar showing Sell Rate, Allocation, Stop Sell, arrival and through length-of-stay limits, arrival/departure closures and Cut Off Days This master section shows all common field families. Blank cells mean no explicit value is shown for that stored field; they are not zero, No, or confirmation that a channel has no restriction. Number entry: Rates use up to two decimal places. Allocation, night limits and Cut Off Days use non-negative whole numbers, not fractions or negative values. Keep these whole-number values within 0–32767, the range supported by Calendar's request parsing; channels can impose narrower rules. Use operationally appropriate values rather than the technical maximum. A syntactically accepted number is not proof that a channel supports or accepted it. Grid field Meaning and example Values and removal behavior Sell Rate The selling price for that date and product. 150.00 requests that price, not a price adjustment. A master rate is a starting value for configured destination calculations; a channel rate is entered in that channel's pricing context. Enter a positive amount meeting the room type's minimum allowed rate. An amount below that minimum reverts in the browser. Zero is not a safe close-out or deletion command: it can remove a stored master price while the channel rate request is rejected. Use Stop Sell for a closure. Additional labeled Sell Rate rows Channel-specific rate components, such as a supported occupancy price. The label identifies the component; it is not another generic master price. Use a positive price and the same minimum-rate rules. Only configured, enabled components appear. Changing the main channel Sell Rate can calculate additional enabled components; check them before making separate overrides. Allocation Available room inventory for the date at that product level. 5 replaces the requested count with five. Whole numbers; 0 means no available inventory, not “leave unchanged.” A master zero also closes Stop Sell. Positive allocation automatically reopens Stop Sell only with the relevant property setting; always check both. Stop Sell A closure to sales for the date/product. Yes applies the closure; No removes that stop-sell restriction. No does not restore allocation, prices or remove other restrictions. Blank is not No. Min Nights Arrival Minimum total stay length for a booking arriving on this date. 3 requires at least three nights for arrivals that day. Use 1 for the normal one-night minimum, or a larger whole number. Entering 0 is normalized to 1 ; it does not remove the field or allow a zero-night stay. Min Nights Thru Minimum total stay length for a stay that includes this date as a stay night, even if arrival is earlier. Use 1 to remove a higher minimum-length requirement, or a larger whole number. 0 is normalized to 1 . This does not remove a separate Arrival minimum. Max Nights Arrival Maximum total stay length for a booking arriving on this date. 7 limits those arrivals to seven nights. A positive whole number sets the limit. 0 requests removal of this maximum restriction; it is not a zero-night maximum. Confirm that removal on each destination. Clearing the text is not removal. Max Nights Thru Maximum total stay length for a stay that includes this date as a stay night, even if arrival is earlier. A positive whole number sets the limit; 0 requests removal of this through maximum. It does not remove the separate Arrival maximum. Closed To Arrival ( CTA ) Whether a booking may begin on this date. A Friday closure prevents Friday arrivals; it is not the same as closing Friday to every stay that began earlier. Yes closes arrivals; No removes this arrival closure. Other restrictions still apply. Closed To Departure ( CTD ) Whether a booking may depart on this date. A Sunday closure prevents Sunday departures. Yes closes departures; No removes this departure closure. Check the departure date, not only the nights occupied. Cut Off Days Advance-booking lead time for the affected date. 2 requires the applicable date to be at least two days ahead under the destination's cut-off rules. Whole numbers; 0 removes this additional days-in-advance requirement. It is not a check-in time or a number of nights. Channel booking cut-offs and other policies can still apply. Other channel-specific fields Extra restrictions or parameters supported by that integration. Their labels, available choices and any label tooltip define the channel-specific setting. Use only the displayed choices or the documented format for that channel. Do not transfer zero/No meanings from another field. If the meaning is unclear, check the channel guide or ask support before changing it. Arrival versus Thru: Arrival rules are evaluated against the check-in date. Thru rules concern stay nights, not the checkout date itself. For example, a Thursday arrival with Friday night included can be affected by Friday's Thru limit but not Friday's Arrival limit. A departure closure is checked against the checkout date. Channels do not all support both length-of-stay forms; inspect the available channel row and resulting request rather than assuming they are interchangeable. Keep minimum and maximum limits consistent. For example, a three-night minimum and a two-night maximum can leave no eligible stay for the affected dates. Do not assume that every contradictory combination is prevented before submission. Stored values, blank cells and date indicators - Blank numeric cell: no explicit value is displayed for that stored field. It is not the same as allocation zero, a one-night minimum, or removal of a maximum stay. Related product values and channel rules can still affect sales. - Blank Yes/No cell: no explicit boolean value is displayed. It is not equivalent to No. Once a value exists, the blank dropdown choice may no longer be present. - Stored versus requested values: normalization can change what is stored. A zero minimum becomes one; removing a maximum with zero can leave the stored master value blank on reload. The attempted value can remain visible until the page reloads or a response changes it. - Read-only value: you can inspect it, but that row is not an editable control for your current permissions, product setup or update mode. - Colored line beneath a date: a summary derived from the stored inventory and related products—red for a closure/no allocation, gray for insufficient rate/allocation information, yellow for a restriction signal, green for the remaining available-state classification. It is not a complete stay search or channel-acceptance indicator; a green line does not guarantee every stay is bookable. - Date-heading tooltip: shows the stored inventory edit timestamp where available, in the displayed user time zone. It is not the channel's delivery/acceptance time. Common problems Symptom Check and safe next action A field or plan is missing Check Options , Room Types , Rate Plans , Channels , and the appropriate [ + ] Channels expansion. Fields also require enabled property features and supported, enabled mappings. Ask your administrator if the expected field is still absent. Everything disappeared after a display change Re-select the room type, relevant weekday, option and plan. Clearing a display group hides its content; it does not erase inventory. A channel row is read-only It may be a received PMS row, lack the relevant update permission, or be restricted by the property's update mode. Ask your administrator to review the setup; do not broaden the edit to master scope as a workaround. A price immediately reverts It may be below the room type's minimum allowed rate. Check the intended amount and minimum. If it still fails, stop and provide the field/value and message to support. A minimum entered as zero becomes one Minimum stays normalize zero to one. Enter the intended positive minimum; use the field reference rather than erasing the cell. Clearing a field restores its previous/attempted value Blank entry is not a delete command. Use the explicit value for the intended change, such as No for a closure or zero for removing a maximum stay. First check whether a previous edit already submitted. The value stays visible but the update is missing or an error appears The displayed value is not a save or delivery receipt. Check Updates → Status using Search , reload the affected calendar values, and check applicable PMS overrides. If the saved scope remains uncertain, contact support before retrying. A hidden plan changed after a room-type edit Hiding a plan does not exclude it from the room-type master's effects. Review all affected plans and destinations before correcting the values. Use a specific plan section for a genuinely plan-specific change. Positive allocation still does not reopen sales Check Stop Sell and the automatic-stop-sell setting, then prices and the other booking restrictions. Verify the resulting request and channel inventory. A manual value changes later, or PMS changes no longer flow Review the field's PMS override policy and the product/mapping scope. Not every channel-row edit is stored as a lasting override. Do not clear overrides as a casual retry; that can affect more inventory than the cell you are investigating. For support, provide the property, channel, room type/rate plan, affected dates, editing level, field and intended value, action time/time zone, and error text or request ID. Do not include passwords, payment details or unrelated guest information. Related - PMS Overrides - Channel Settings Page — OTA - Quick Update — for a shared change across a date range rather than individual calendar cells.
Update daily rates, availability and restrictions
Use Daily Update to enter different rates, availability and restrictions for individual dates, review the affected room types and rate plans, and submit the changes for your property's enabled channels. Before you start - Select the correct property. You need access to that property and permission to update the relevant Rates, Availability or Restrictions. Channel setup, mappings and supported fields also determine what you can update. - Daily is not a single-channel editor. Send Updates considers the property's enabled inventory-send channels; there is no channel selector on this page. A displayed field does not mean every channel supports it. - Check your PMS override settings. Manual changes can block later PMS updates for affected items when overrides are enabled. Without those overrides, later PMS updates can replace your manual values. - Product selections control the grid, not a complete list of update destinations. In particular, a room-level update can reach that room's configured channel rate plans even when those plans are hidden or unselected. For a narrow update, leave broader fields blank and use the specific room/rate-plan block. 1. Load the dates and products 1. Open Updates → Daily for the selected property. 2. Set Date Range. You can use Month / Year to choose a month or enter a start and end date. Check the visible dates after entering them. Use today or future dates, with the end on or after the start. 3. Under Days, select the weekdays to include. For example, select Fri and Sat for weekend dates within the range. Keep at least one weekday selected. 4. Under Options, select Rates, Availability and/or Restrictions. Keep at least one option selected. 5. Select the Room Types and Rate Plans to display. 6. Click Load Screen. This loads the grid; it does not send inventory updates. Reloading can discard unsent entries, so read any discard confirmation before continuing. 7. Check the date headings, room columns, rate-plan rows and selection summary. If you see Not loaded yet: Load Screen to show these choices., the old grid is still displayed. Load the new choices before entering updates. Daily criteria showing the date range, weekdays, options, Studio and Standard selections, and Load Screen This example loads one room type and one rate plan. The selections are display choices, not a channel-send checklist. On a fresh page, the initial range runs from the property's current date through 14 days later, with all weekdays, options and available products selected. The Days and Options headings toggle all choices in their group. The checkboxes beside Room Types and Rate Plans select or clear their lists. Selecting no rate plans leaves room-level controls; it does not prevent room-level updates reaching channel rate plans. Selecting no room types leaves Global controls, not all rooms. Direct Global updates in that case require a channel that supports hotel-level updates. Unmapped appears only where setup provides channel rate plans without a property rate-plan mapping. If the page shortens the end date because the grid is too large, use fewer options/products or split the work into smaller ranges, then load and check the result again. Where Toggle Row Wrap is shown, it switches the layout between wrapping product blocks and keeping them side by side; it does not change the update values. 2. Choose the right block for each date Each date has its own set of editing blocks: Block Use it for Global at the upper left A broad starting value for that date. It can populate room and linked-plan fields. A room-type heading , such as Studio Changes at that room's level for that date. These can also reach its configured channel rate plans, including plans not displayed. A rate-plan heading in the left-hand column , below Global A value for that plan across the displayed room types for that date. A rate plan beneath a room type , such as Standard below Studio Changes to that room/rate-plan combination for that date. Configured links can still populate related products. One Daily date with Global and Studio blocks above the Standard rate-plan blocks; all update inputs are blank The left-hand Standard block applies across rooms; the right-hand Standard block belongs to Studio. Each date is separate. Blank fields and stored values The editable controls hold your new changes. Blank means no new value for that field. It is not zero, No, deletion of a saved value, or removal of a PMS override. The value or dash beside a room/plan input is the loaded ChannelRUSH master value, not a confirmation from the destination channel. A dash means no stored value is shown; it is not zero. Colored indicators summarize the stored state: red for closed/no availability, gray for missing required rate or availability, yellow for restrictions, and green for available under that indicator. They do not establish channel acceptance. The indicator's hover timestamp, when present, is the stored edit time in your user time zone. Enter broad values before specific exceptions Changes to broader fields can populate or overwrite more specific fields. Rate calculations, rounding and configured room/rate-plan links can affect the resulting values. Room-to-plan propagation can differ for rates, availability and restrictions according to the link settings. If you intend a broad update, enter the broad value first, wait for population to finish, and then make the specific exceptions. Check every affected block and date before submitting. Changing a broader value again can replace those exceptions. Daily uses Sell Rate; it has no rate-type selector or occupancy-rate inputs. Common editing workflows Change one room/rate plan on one date 1. Load the required date, room type and rate plan, with Rates selected. 2. Find the rate-plan block beneath the room type on that date. 3. Enter the new Sell Rate there. Leave Global, room-level and left-hand rate-plan fields blank if you do not intend broader changes. 4. Wait for any linked-product population and inspect the other blocks. Repeat only for the other dates you intend to change. 5. Follow Submit and check the result below. Close or reopen sales 1. Load the affected dates/products with Availability selected. 2. To close sales, set Stop Sell to Yes in the intended block. Use Allocation = 0 only when you also mean zero available units: entering zero sets Stop Sell to Yes during field population. 3. To reopen, enter the intended positive Allocation and check Stop Sell. A positive allocation changes Stop Sell to No automatically only when the property is configured to do so; do not assume replenishing allocation reopened sales. Set No explicitly where required. 4. Review linked products and other restrictions. Stop Sell = No alone does not provide availability or remove stay-length, arrival or departure restrictions. 5. Submit once, then verify the affected destinations. Apply or remove a restriction 1. Load the relevant dates and products with Restrictions selected. 2. Enter the required restriction in the appropriate block, using the field reference below. Arrival limits apply to arrivals on that date; Thru limits apply to stays through it, where supported. 3. To remove CTA or CTD, select No, not blank. To remove a maximum-night limit or advance-day cutoff, use 0. For a minimum-night limit, use 1 for the least restrictive value; zero is normalized to one, not an unrestricted blank. 4. Check the other minimum/maximum limits and populated linked products before submitting. Clickable headings: clear or repopulate unsent entries The blue Global, room and plan headings are editing shortcuts, not navigation links. They operate on that date only and use the values currently entered in the form, not the stored values beside the inputs. 0 and No count as populated entries. Heading you click What happens Global Clears all pending Global, room-type, left-hand rate-plan and room/rate-plan inputs for that date. It does not copy values to other dates. Room type If its own block contains an entry, clears that room's block and its rate-plan blocks for the date. If its block is empty, repopulates from the date's Global and left-hand rate-plan entries. If neither broad source has entries, it clears the room and its child plan entries instead. Rate plan beneath a room If the block contains an entry, clears that block. If it is empty, populates from the same-date room and left-hand plan entries; a left-hand plan value takes precedence for a field supplied by both. Rate calculations can apply. With neither source populated, it remains empty. Rate plan in the left-hand column Checks that plan's room-level blocks for the date. If any contains an entry, clears the left-hand plan block and that plan's blocks across rooms. If they are all empty, fills those room/plan blocks from their room-level entries, applying rate calculations. It is not a copy-across-dates shortcut. Review the resulting entries after every shortcut. Clearing a field only removes the pending change from this form; it does not undo an earlier submission, restore server values or remove an existing PMS override. Submit and check the result 1. Confirm the loaded date/product scope and review all populated inputs, including linked fields and any specific exceptions. Check Allocation and Stop Sell together. Wait until field population has finished. 2. Click Send Updates once at the bottom of the page. 3. Read every success, warning and error message. A saved confirmation means update requests were saved for processing, not that every channel accepted every change. Some requests can save while others are rejected. 4. Open Updates → Status for the same property. 5. Set Status to All, then select the relevant Channel, Room Type and Rate Plan, or leave them at All for a broader search. An Unsuccessful filter hides successful and pending requests. 6. Open More Filters and set Source to UI Daily. Under Date Range, choose Start/End Date and enter both affected inventory dates to find requests whose date ranges overlap your update. These are the dates you changed, not the day you submitted it. Creation Timestamp searches when the request was created; Processing Timestamp searches its processing/edit time instead. 7. Click Search. Changing filters alone does not refresh the results. Check that your selections remain applied and review each matching request's channel/product, affected dates, values, Status, Attempts, Created and Last Run. Match the creation time to your submission so you do not mistake an older request for the new one. 8. Pending and Processing are not completion. Unsuccessful requires investigation of the request's message/logs. Successful is that request's recorded processing result, not a guarantee that later PMS or channel activity has left the value unchanged. Check the actual affected dates/products on the destination channel before relying on the update. For an empty or unexpected Status search, widen the filters and click Search again. Leave Rates, Availability and Restrictions all unselected to avoid narrowing by data type; selecting all three also removes that restriction. A subset can exclude older requests without data-type detail. Select Archived if you need to include archived requests. Clear Search Filter resets the criteria. Transaction ID and Users can narrow an investigation when you have the relevant details. The Go buttons belong to the separate request actions, such as Retry and Archive. They are not Search buttons. Do not retry or repeat Send Updates merely because a filtered list is empty or a result is unclear. Important: even a message that no updates were saved does not prove nothing changed. Local inventory values and enabled PMS overrides may still have saved independently of channel requests. Check the affected local values, overrides and channel-specific results. If you cannot establish what saved, ask support before resubmitting; an empty Status search alone cannot resolve that uncertainty. Use Cancel to leave unsent entries and reload Daily's initial view. It does not undo a previous submission. Field reference Fields appear according to your permissions, selected Options, property setup and channel support. Use nonnegative whole numbers for quantities, days and nights. Sell Rate accepts up to two decimal places using your displayed number format. Channel-specific limits and validation still apply; there is no single maximum value valid for every channel. Field What it changes Values and example Sell Rate The selling rate used as the basis for this date/product's update. Linked-product and channel calculations can change the final amount. A positive amount, for example 150.00 . Zero is not a valid selling rate; leave blank for no rate change. Allocation Available units for this date/product. A whole number, for example 5 . 0 means no available units and also sets Stop Sell to Yes during population. A positive value only automatically reopens Stop Sell when the property setting enables it. Stop Sell Whether sales are closed for the date/product. Yes closes; No requests reopening subject to availability and other restrictions; blank makes no new change. Cut Off Days How many days in advance a booking must be made. For example, 2 requests a two-day advance requirement. 0 removes that requirement where supported. Min Nights Arrival Minimum stay length for a guest arriving on the date. For example, 3 requires at least three nights. Use 1 for the least restrictive minimum; 0 is normalized to 1. Min Nights Thru Minimum stay length for a stay passing through the date. For example, 3 requires at least three nights for a stay that includes the date, where supported. 0 is normalized to 1. Max Nights Arrival Maximum stay length for a guest arriving on the date. For example, 7 requests a seven-night maximum. 0 removes this maximum where supported. Max Nights Thru Maximum stay length for a stay passing through the date. For example, 7 requests a seven-night maximum for a stay that includes the date, where supported. 0 removes this maximum. CTA Closed to arrival: prevents a guest arriving on this date. Yes applies the restriction; No removes it; blank makes no new change. It is not a full stop sell. CTD Closed to departure: prevents a guest departing on this date. Yes applies the restriction; No removes it; blank makes no new change. It is not a full stop sell. Blank has the same no-new-change meaning for every field. To remove an existing PMS override rather than change inventory, follow the separate PMS Overrides guide. Common problems - A field or product is missing: check Options and the loaded selections. If it is still missing, ask your administrator to check permissions, mappings, channel setup and support for that field. Do not use a broader update to work around a missing specific control. - The grid shows the wrong dates/products: check the pending-selection notice and click Load Screen before editing. If the end date was shortened, reduce the grid size and reload. If the loaded result still differs, stop and contact support with the selections and displayed dates. - Specific values changed after a broader edit: linked-product population or rate calculations may have replaced pending values. Review the whole date, enter broad values first and make exceptions last. If the calculated result is unexpected, have the link/calculation settings checked before sending. - A channel reports setup, date-limit or value errors: identify the affected channel and product in the messages. Check its configured update horizon and supported values with your administrator. Do not assume the other channels were rolled back; inspect Status and local values before correcting and resubmitting. - Sales remain closed after increasing Allocation: check Stop Sell and the remaining restrictions. Positive availability is not an unconditional reopen command. - Values later change, or PMS changes stop appearing: review PMS overrides and the upstream inventory source before changing settings or sending again. - No saved requests, mixed results or uncertain delivery: follow the result-check procedure above. If you cannot reconcile the local values and request outcomes, contact support before retrying. For support, include the property, channel, affected dates, room/rate plan, submission time and time zone, request ID if available, and exact message. Do not include passwords or guest information. Related - PMS Overrides - Quick Update - Channel Settings Page — OTA
Update rates, availability and restrictions with Quick Update
Use Quick Update to apply one set of rate, availability or restriction changes to selected dates and weekdays for a property's rooms, rate plans and channels. Before you start - Select the correct property in the property selector, then open Updates → Quick. The heading is Quick Update. - You need property access and permission for the items you change: rates, availability (including stop sell), or restrictions. Fields also depend on the property's enabled features, channel support and mappings. Seeing a field does not mean every selected channel supports it. - Check which room types and rate plans are linked. A room-specific change can populate dependent rooms or plans; a rate-plan change can populate its dependent plans. - If a PMS supplies inventory, check your property's PMS override policy. Manual updates may create overrides that prevent later PMS values from replacing those items. Where overrides are disabled, later PMS updates can replace your manual values. Channel selection also matters: all-channel changes and selected-channel changes can affect different stored inventory and override scopes. This is a change-entry form, not a view of your current inventory. Its inventory fields start blank. Editing a field or using a heading shortcut prepares the form; Send Updates submits it. Do not use zero to mean “leave unchanged.” 1. Choose dates and weekdays 1. Under Date Ranges, choose a Start date and End date. Both dates are included. Use dates on or after the property's current date, with the end on or after the start. 2. Under Days, leave selected only the weekdays you want to update. All seven start selected. The range must contain at least one of the selected weekdays. 3. To apply the same changes to another period, select Add Date Range and enter its dates and weekdays. You can use up to ten ranges. Remove an extra range with [ X ]. 4. If you type dates, move out of the field and check that both dates remain visible before continuing. For example, to change Friday and Saturday nights throughout a month, choose that month's start and end dates and leave only Fri and Sat selected. All the inventory values entered below apply to every selected range; use separate submissions when different periods need different values. Quick Update Date Ranges with Start date, End date, Add Date Range and seven selected weekdays 2. Choose the right level of change Use the narrowest fields that match your task. Room columns align with the rate-plan columns below them. Where you enter a value What it prepares Global Room Type Populates room-type fields across the property and their applicable dependent rate-plan fields. Channels with property-level support can also receive a property-level update. This is a broad update, not a room-selection filter. A named room under Room Types Prepares that room's update. Configured room links and rate-plan relationships can populate other fields. Room-level requests can also apply to the room's enabled, mapped channel rate plans. Global - [rate plan] under Rate Plans Populates that rate plan across rooms. Room calculations and dependent-plan relationships can change the resulting values. A rate plan in a particular room's column Prepares that room/rate-plan combination. Configured dependent plans may also be populated. Unmapped , if shown Represents channel rate plans without a matching property rate-plan mapping; it is not a new plan or an instruction to repair mapping. Confirm the intended channel products before using it. To change only one room/rate-plan combination, start with the broader global and room fields blank. Enter the intended values in that combination's rate-plan fields, then review any populated dependent fields. Clearing a rate-plan field alone does not reliably exclude that plan while a broader room update remains filled: the room update can still generate requests for channel rate plans. Do not use a broad update to work around missing permissions or unsupported fields. Global Room Type and Studio columns with blank rate, allocation and restriction fields Focused example of the Room Types section. Your room names and available fields may differ. 3. Enter and review the changes 1. Enter only the values you want to change at the level chosen above. The field reference below explains each field. 2. Move out of the edited field and allow automatic population to finish. Rates can be recalculated using configured room/rate-plan relationships and rounding; do not assume every populated rate will equal your original entry. 3. Review the room fields and the rate-plan fields below them, including linked rooms and dependent plans. Check the whole form, not only the field you edited. 4. Review every date range and weekday selection again. Blank, zero and No are different - Blank: no explicit change from that field. It does not delete the stored value, remove a restriction, or cancel a broader update elsewhere in the form. - 0: an explicit numeric value, subject to the field's and channel's rules. Allocation = 0 also populates Stop Sell = Yes. A zero rate is not a valid way to close sales. - No: an explicit request to remove that particular boolean restriction. For Stop Sell, it requests reopening; for CTA or CTD, it removes the arrival or departure closure. Other availability and restrictions still apply. Review Allocation and Stop Sell together. When the property's automatic stop-sell setting is enabled, entering allocation above zero can populate Stop Sell = No. This may reopen sales for affected products, including populated dependent plans. Do not assume changing allocation leaves stop sell untouched. Global Standard and room-specific Standard rate-plan fields In this example, the Standard column on the right belongs to the first room column above. Use the column alignment to identify the room before editing. What clicking a blue heading does The blue room and rate-plan headings are populate/clear controls, not navigation links. They act on the unsent form; they do not fetch your current inventory or undo a submitted update. 0 and No count as filled values for these shortcuts. Heading Behavior Global Room Type Clears the global room fields, every room's fields, global rate-plan fields and room-specific rate-plan fields. Dates, weekdays and channel selection remain. A room name under Room Types If any of that room's own fields is filled, clears those fields and all its rate-plan fields. If the room fields are blank and global values are available, populates the room and its plans from the global room/global rate-plan values. If neither global source has values, clears the room and its plans. Global - [rate plan] If any room-specific field for that plan is filled, clears the global fields and every room-specific field for that plan. If all the room-specific fields are blank, uses the entered room-type values to populate that plan across rooms, with configured rate calculations. It does nothing when there are no room-type values to copy. A rate-plan name in a room's column If any field in that room/plan block is filled, clears the block. If the block is blank, populates it from that room's fields and the matching global rate-plan fields where available. Matching global rate-plan values take precedence; rate calculations still apply. After any shortcut, review the resulting fields. To abandon the entire unsent form, use Cancel and confirm any unsaved-change prompt. If Toggle Row Wrap is offered, it changes how the columns fit on screen, not which products receive an update. 4. Select channels and send 1. When Channels is shown, review the selected destinations. Eligible channels start selected. Use the individual checkboxes or All Channels to select or clear the enabled choices; disabled channels cannot be selected. 2. Confirm the intended channels support the fields and dates you entered. Channels assigned to inventory groups are not offered for direct selection here; use Detail or Calendar for their direct updates. 3. Wait until automatic population has finished. Do not submit while the page says Please wait, data on the screen is still populating.... 4. Select Send Updates once. 5. Read every success, warning and error message before deciding what to do next. Some users have a standard-only update mode with no channel checkboxes. The form can still submit updates through the property's configured distribution setup; absence of checkboxes does not make it read-only. Confirm the destination setup with your administrator if you are unsure. Quick Update Channels selection, All Channels, Send Updates and Cancel Cancel resets the unsent form. It does not cancel queued work, remove PMS overrides or reverse updates already submitted. 5. Check what was saved and processed Your updates have saved and are now processing. means requests were saved for processing. It does not establish that every selected channel accepted every requested change. A large date selection may appear as several requests. 1. Open Updates → Status for the same property. The heading is Update Status. 2. Set Status to All so a filter does not hide successful, pending or processing requests. 3. Choose the relevant Channel. Leave Room Type and Rate Plan at All initially if the update included room-level or property-level changes; narrow them when checking a specific combination. 4. Open More Filters. To find Quick submissions, choose Source → UI Quick. If you enter dates, choose Start/End Date to search the affected inventory period, or Creation Timestamp to search when requests were created. Processing Timestamp concerns processing, not the stay dates. Move out of typed date fields and check the retained values. 5. Select Search. Changing a dropdown alone does not load the filtered results. 6. Inspect the matching channel/product, affected dates, update values, Status, Attempts, Created and Last Run. Use the paging arrows if needed. Confirm that the request belongs to your action, not an older update for the same dates. 7. Check the affected inventory and, when necessary, the destination channel before correcting or repeating the update. Pending and Processing are not finished outcomes. Successful is the recorded processing result for that request, not proof that unrelated requests succeeded or that no later update changed the channel. For Unsuccessful, read the request's error information and resolve the cause before considering a retry. If nothing matches, use Clear Search Filter, set Status → All again, and select Search with broader criteria. Leave data-type filters unselected when investigating broadly; restrictive filters can hide relevant history. Include Archived under More Filters if the request may have been archived. Do not use Retry or Go merely to refresh the list. An error does not necessarily mean nothing was saved. Valid channel requests can be saved while others fail. Local inventory and PMS overrides are handled separately and can be changed even when no channel request was saved. A “no updates saved” message or an empty Status search is not proof that all stored values stayed unchanged. Inspect Status and inventory before resubmitting; if you cannot establish the saved scope, ask support to confirm it. Field reference All update fields are optional individually, but you need an actual change, a valid date range and, when the channel list is shown, at least one enabled selected channel. The form starts with blank inventory values, not default rates or restrictions. Enter numbers in the format used by your account. Rates accept decimal amounts; allocation and day/night restrictions use whole numbers. Do not enter currency symbols, percentages or formulas. Allowed limits and supported combinations vary by channel; there is no single Quick Update range that guarantees acceptance everywhere. Field What it changes Example and important checks Sell Rate The rate for the selected scope and dates. Room/plan calculations can populate dependent rates; channel settings can further affect the outgoing rate. 150.00 is a rate amount, not a percentage increase. Rates must be above zero and satisfy the room's configured minimum allowed rate and channel rules. Leave blank to omit the explicit rate change. Occupancy-specific rate fields, when enabled The rate for the occupancy named by the field. These appear only for supported, configured room/plan combinations; global columns do not provide a separate input for every occupancy. A two-person occupancy rate applies to that named occupancy. Review values after changing Sell Rate because configured calculations can populate them. Do not assume an occupancy edit populates other occupancies or plans. If a field does not respond as expected, stop and ask support rather than submitting uncertain values. Allocation The number of units offered for the selected scope/dates. 5 requests five units, not five additional units. 0 requests zero allocation and also populates Stop Sell = Yes . A positive value can populate Stop Sell = No when configured. Review both fields and dependent products. Stop Sell Whether sales are closed for the affected product and dates. Yes closes sales; No removes this closure. Reopening does not override zero allocation or other booking restrictions. Blank omits the explicit stop-sell change. Cut Off Days The advance-booking cutoff, measured in days, for supported products. 2 sets a two-day advance-booking requirement. Use the destination's supported cutoff values. Blank leaves this field out; do not assume zero has the same reset behavior on every channel. Min Nights Arrival Minimum stay length for a booking arriving on an affected date. 3 requires at least three nights for an arrival on that date. It is different from a minimum applying to a stay that passes through the date. Min Nights Thru Minimum stay length for a booking whose stay includes an affected night. 3 requires a stay of at least three nights when it includes that night, even if arrival is earlier. Channel support is required. Max Nights Arrival Maximum stay length for a booking arriving on an affected date. 7 limits arrivals on that date to seven nights. Check it against the applicable minimum-stay restrictions. Max Nights Thru Maximum stay length for a booking whose stay includes an affected night. 7 limits a stay including that night to seven nights. Do not treat this as an arrival-only maximum. CTA Closed to arrival. Yes prevents arrivals on the affected dates; No removes the arrival closure. It is not a stop sell for every stay passing through those dates. CTD Closed to departure. Yes prevents departures on the affected dates; No removes the departure closure. It is separate from CTA and Stop Sell. For numeric restrictions, blank means omit, not “remove the existing restriction.” To remove or relax one, use the value supported by the destination channel. Do not assume zero universally means unlimited or unrestricted. Check the applicable minimum/maximum together and verify the resulting request. Common problems and safe recovery Symptom What to check Safe next action Date or weekday error Both dates are required; dates must not be in the property's past; at least one selected weekday must occur within the range. Correct the range/weekday selection. Check all added ranges, not only the first. No updates have been saved since no channels were selected, please try again. No channel was selected in a mode that requires the channel list. Select the intended enabled destinations and review the form before submitting. A rate is rejected Zero/negative rate, a room minimum-rate rule or a channel-specific rule may apply. Read the channel/product error, correct the intended value, and check for partially saved requests before repeating anything. A channel is disabled or a field is missing Permissions, property feature settings, inventory-send enablement, setup or mapping may prevent that update. Inventory-group channels are omitted from Quick's direct-selection list. Ask your administrator to check the relevant setup. Do not broaden the update to bypass the restriction. Only part of the requested future period is processed Channels have different future-date limits and may exclude dates beyond their limit. Read the warning and inspect the actual request dates. Do not assume the entire range was accepted. Unexpected values appear in other rooms/plans Global entry, room links, dependent plans, automatic rate calculations or allocation/stop-sell coupling can populate fields. Before sending, correct the scope and review the whole form. If you cannot explain the population, cancel and ask your administrator or support. Population never finishes, a field does not react, or the page errors The prepared form may be incomplete. Do not select Send Updates. Record the affected field and error; use Cancel if you are discarding unsent work. If submission may already have occurred, check Status and inventory first. Success and error messages appear together, or the submission result is unclear Updates are not one all-or-nothing transaction. Local values/overrides and channel requests can have different outcomes. Do not resend the whole form blindly. Check Status, affected inventory and PMS overrides; contact support if the saved scope remains uncertain. When contacting support, include the property, channel, room/rate plan, affected dates, action time and time zone, any request ID, and the exact error text. Do not send passwords, guest details or payment information. Related - PMS Overrides
Review reservation details
Open the correct reservation version, check its rooms and guests, and understand the amounts, remarks and available payment information for your selected property. Before you start You need access to the property in ChannelRUSH. When you open details through Reservations → Search, full card details require Reservations - Credit Card permission; additional account restrictions can still keep the number protected. If your account has password re-verification enabled for that access, ChannelRUSH can ask you to verify your password. The Org Admin → Reservations detail view always uses the protected card summary instead. This is a view of a stored reservation, not a form for changing or canceling it. Opening it does not send or resend the reservation, collect a payment, or issue a refund. Booking status, delivery status and payment information are different things. Keep reservation details private. Do not include guest names, contact information, card data or transaction references in screenshots for support. The screenshots below show only actual field labels; all reservation values are outside the crops. Open the reservation from the property 1. Select the property in the property selector. 2. Open Reservations → Search. 3. Enter the channel reservation number in Reservation ID. If you do not have it, use Guest Name / Email or other appropriate search criteria. 4. Select Search. Changing a filter alone does not apply the search. 5. Check the result's property, channel and stay dates. 6. Select the linked reservation number. Its details open in a new tab, leaving Search available in the original tab. If Re-Verify Password appears, enter your own account password on that ChannelRUSH page and select Continue. Never send your password to support or another person. If verification fails, stop and use your normal account-access recovery process. Open the reservation from Org Admin Use this path when reviewing reservations across properties. If Org Admin is not available, use the property-specific path above for a property you can access. 1. Open Org Admin → Reservations. 2. Choose the booking's Property in the search filters. If Organization is shown, select the intended organization first, then reselect the property. 3. Enter the channel reservation number in Reservation ID, or use the other search filters described in Reservations. 4. Select Search. Check that the retained filters and results match the intended property. 5. Check the result's property, channel and stay dates. 6. Select the linked reservation number. The reservation document opens in a new tab; return to the original Reservations tab to continue searching. Org Admin search includes archived reservations automatically; there is no Include Archived box. The opened document always uses the protected card summary, even when you have Reservations - Credit Card permission. Other personal and payment information can remain visible, so keep the document private. For authorized full-card access, use the property-specific path above with your own account; opening the Org Admin document again does not change its summary mode. The Org Admin document does not provide Return to report, Guest messaging or Guest reviews links. Their absence here is expected, not evidence that the reservation failed or that a message was sent. Review the booking in order 1. Confirm the booking and its version Check the heading's source channel and property, then Reservation ID and Status in Overview. Detail-page status Corresponding Search status Meaning CONFIRMATION New This version records a new reservation. MODIFICATION Modified This version records a reservation change. CANCELLATION Canceled This version records a cancellation. These labels do not establish whether the PMS received that version, whether the guest paid, or whether a refund was made. A cancellation can still show amounts and stay details; do not treat those amounts as a newly calculated cancellation charge or refund. A prominent previous-version warning means a newer record exists for the same property, channel and channel reservation number. Treat the displayed record as historical. Return to the search you used—Reservations → Search or Org Admin → Reservations—select Search again, and open the matching result to review the latest stored version. Check that the warning is absent there. A saved detail link continues to identify that particular version. Reloading it does not replace it with the latest version. A detail link from a delivery attempt or report can intentionally open the version associated with that attempt. The latest stored version is not a live re-fetch from the booking channel. 2. Check the whole-booking overview Use # of Rooms and Room Types to establish how many room entries you need to review. Total describes the reservation as a whole; it is not the price of each room or an amount already collected. Read Remarks here before moving to the rooms. These are reservation-wide notes, separate from the remarks attached to an individual room. An absent note is not confirmation that a request was accepted or fulfilled. Overview field labels, with all reservation values outside the crop Overview field labels, cropped from the live application to exclude reservation values. Tax and Total Paid are conditional rows. 3. Separate the booking contact from the staying guests Booked By contains the booking contact's name, company and available contact details. It is not necessarily the person staying in every room, and it is not necessarily the card holder. For each Room section, check Guest Name, Check In, Check Out, # of Nights and # of Guests. Different rooms can have different guests, dates, prices and remarks. Do not apply the first room's details to the whole booking. The room's Guest Name lists the people associated with that room. # of Guests is a separate occupancy value: the number of names shown is not a reliable substitute for the guest count. Room field labels from Guest Name through Description, with all reservation values outside the crop Room field labels, with all values excluded. Fee is conditional. Daily Rates can occupy several lines, one for each recorded date. 4. Read prices, taxes and extras together Use these three levels rather than treating every amount as another charge: - Overview → Total: the whole-reservation amount, with tax excluded, tax included, or both lines. - Room → Price: the total for that room entry's stay, not an average nightly rate and not a per-person rate. It also identifies the tax basis. - Room → Daily Rates: the individual dated room-rate entries, with currency and any available rate-plan name or ID. These are the rates recorded with the reservation, not today's inventory rates. Tax, Fee and Addon rows can appear beneath the whole-reservation Total or a room's Price. Their position identifies their scope. Read their names, amounts, quantities and pricing descriptions. Do not automatically add every displayed row to Total again: some items are included, and a supplied total can already account for them. The page uses an explicitly recorded before-tax or after-tax total when one is available at that level. If neither is recorded, it calculates an amount from daily room rates and non-inclusive extras. The whole-booking calculation includes all room entries plus reservation-level extras; a room calculation includes only that room's rates and extras. Tax-excluded calculation omits extras classified as Tax, not all fees or add-ons. When both explicit totals are available, both are displayed. When only one is available, only that tax basis is displayed. When neither is available and the two calculated totals differ, both calculated amounts are shown. If the calculated amounts are equal, the display assumes tax excluded for USD, CAD or a missing currency, and tax included for other currencies. This is a display assumption, not confirmation of the channel's tax treatment. Check the booking terms or ask support if the tax basis is unclear. Currency codes identify the currency recorded for the booking; this screen does not convert amounts. Commission Amount can use a different currency, so check its own code. Differences between the sum of Daily Rates, a room Price and the reservation Total can reflect extras, different scopes or explicitly supplied totals. Investigate a discrepancy rather than changing the reservation or collecting an additional amount based only on this display. 5. Review payment information without treating it as a payment result Total Paid appears in Overview only when the reservation contains a paid amount, including an explicitly recorded zero. It is the amount recorded with this reservation version, not a live payment-provider check. If the row is absent, the page has no recorded paid amount to show; absence does not mean zero or unpaid. Credit Card Details can show protected information, incomplete details, or a message that the channel did not provide any credit card information. A protected number does not mean there is no card. Missing card information does not establish whether the guest paid. The Total inside Credit Card Details has its own meaning: - When a recorded Total Paid and an explicit reservation total are both available, it shows their difference labeled total due. The after-tax total is used when available; otherwise, the before-tax total is used. - Otherwise, it repeats the reservation Total and its tax label or labels. Do not assume that every amount in this section is an outstanding balance. Neither a card, a Transaction ID nor a displayed total proves a successful charge, settlement or refund. Follow the booking's payment arrangement and your authorized payment process. If details are unavailable, ask your organization administrator to check your access and the booking arrangement. Never copy card numbers, security codes or transaction references into email, chat or support tickets. Check the result Before relying on the details, confirm the correct property, source channel, reservation number, booking status and room dates. Check every room and both levels of Remarks. If you need current information, reopen the booking from a fresh Search result and make sure there is no previous-version warning. To investigate delivery, select the booking's property in the application tab and open Reservations → Delivery Status. Enter the reservation number, choose the relevant filters and select Search. Use All delivery statuses when comparing an earlier failure with later attempts. Follow Check reservation delivery status for the complete investigation workflow. On Delivery Status, the processing status describes a delivery request, and its displayed request time is the request's creation time. These are not the booking Status or Overview Timestamp described below. Do not resend merely because this detail page shows a modification or cancellation, or because an old delivery failure remains. Field reference Heading, Overview and footer Field or section What it tells you Availability and important distinctions Reservation … / From … / For … Booking status, source channel with its reservation number, and the property. Check all three before using the record. A known original source channel is used in the heading when available. Reservation ID The channel reservation number, followed by an arrival summary and a guest-name summary. Use each room's details for the full guest and date information. The number is different from the footer's internal CR-ID. Status CONFIRMATION, MODIFICATION or CANCELLATION for the displayed version. Not delivery-processing or payment status. Agency Agency name and/or IATA reference. Appears when either is recorded; the reference is shown with IA# . It is separate from Booked By Company. Total Whole-booking amount in the reservation currency, with its displayed tax basis. May show one or two lines. Explicit totals take precedence over a component calculation; see the price explanation above. Tax / Fee / Addon Reservation-level extras with the available name, pricing detail and description. Only recorded extras appear. Their displayed total may include a quantity or a Per Night, Per Person, or Per Person, Per Night description. An inclusive/no-charge add-on may show its description or quantity without an extra price. Do not interpret an omitted price as a missing booking total. Total Paid Recorded paid amount in the booking currency. Appears only when supplied, including zero. Not an independent confirmation of current payment status. # of Rooms Number of room entries in this reservation version. A dash appears if there are no room entries. It is not the number of guests, nights or distinct room-type names. Room Types Names of the reservation's room entries. Multiple room entries are listed separately, so the same type can appear more than once. Names can be resolved from channel mapping when not supplied. Commission Amount Recorded commission amount. Appears only when recorded, including zero. Uses the commission currency if available, otherwise the reservation currency. It is not a separate guest payment or a calculated net-revenue figure. Timestamp Channel edit time when available; otherwise, this record's creation time in ChannelRUSH. Displayed in your user time zone. It is not necessarily the original booking time, a delivery time or the time you opened the page. PMS ID PMS reservation reference stored on this version. Appears only when present. A reference alone does not confirm that the latest modification or cancellation reached the PMS. Remarks Notes attached to the whole reservation. A dash means no reservation-level notes were recorded. Multiple notes are displayed as separate entries. Review room Remarks as well. Footer time / CR-ID / END OF RESERVATION Creation time and internal identifier of this stored reservation record. The time uses your user time zone and can differ from Overview Timestamp. CR-ID identifies this record/version, not the channel reservation number or a delivery-request ID. Booked By Field What it tells you Missing or conditional information Name The booking contact's name. A dash appears when no booking-contact profile is available. This is separate from room guests and the card holder. Company Company name and/or company ID associated with the booking contact. The ID can follow ID: . A dash appears when neither is available. Telephone The booking contact's recorded primary telephone number. A dash means none is available in that contact profile. Email The booking contact's recorded email address. A dash means none is available. Its presence does not establish that an email was delivered. Address Available booking-contact address lines, city/region/postcode and country. Only supplied components are shown; a dash appears if there is no address to display. It need not match the card address. Each Room section Field What it tells you Missing or conditional information Room 1, Room 2, … The sequence of room entries, followed by the room-type name and channel room-type ID when available. This sequence is not an assigned physical room number. A room-type name may be resolved from mapping. Guest Name Names associated with this room entry. Multiple names are joined with & . A dash appears if there are no names to display. It need not match Booked By. Check In / Check Out Arrival and departure recorded for this room. A dash appears when the corresponding date is absent. A time is included when the stored hour is nonzero; a date-only display is not confirmation of a midnight arrival or departure. # of Nights Difference between this room's departure date and arrival date. A dash appears if either date is missing. It is based on calendar dates, not elapsed hours. # of Guests Recorded adults/children, or a general guest count when neither breakdown value is present. See the guest-count rules below. This is per room, not a booking-wide total. Price This room entry's total for the stay, with currency and tax basis. May show a before-tax amount, an after-tax amount, or both. Uses explicit room totals when supplied; otherwise calculates from that room's rates and non-inclusive extras. Tax / Fee / Addon Extras attached to this room, rather than the reservation as a whole. Only recorded items appear. Read quantities and pricing descriptions; do not add inclusive items again. Remarks Notes attached specifically to this room entry. A dash means no room-level notes were recorded. These do not replace Overview Remarks. They are not an editable message or proof that a special request was fulfilled. Daily Rates Each recorded date and its room-rate amount in the booking currency. Each entry can also show a rate-plan name, ID or both. Day-level plan information is used first; if both are absent, room-level plan information is used. A missing name may be resolved from mapping. No entries leaves this area blank, not a zero-rate statement. Description Available room description and amenities. Amenities can follow the description as separate lines. A dash appears if neither is available. This is descriptive information, separate from Remarks. How to interpret # of Guests: - If either the adult count or the child count is recorded, the page uses that breakdown instead of the general guest count. It shows only the supplied parts; an omitted child count is not the same as an explicit 0 Children. - If neither breakdown value is recorded, a nonzero general count appears as Guest or Guests. A missing or zero general count displays a dash. - An explicit adult count of zero with no child count, or with zero children, also displays a dash. Do not interpret that dash as a verified unoccupied room. A supplied children-only count can appear without an adult count. - Names and occupancy are stored separately. If they conflict or the count is incomplete, check the source booking rather than inferring occupancy from the names or silently treating blanks as zero. Credit Card Details Only authorized users should handle the values in this section. The section can be incomplete even when some card information is present. Field What it tells you Availability and limits Card Holder Name Recorded card-holder name. May differ from Booked By and the staying guests. Treat it as sensitive. Card Info Card number, expiry, security code and card type/description, separated by vertical bars. Number and security code may be protected with # characters. Summary access does not hide every other field. A missing security code is a dash; unavailable expiry components can show zero placeholders. Neither placeholders nor visible fields validate the card. Virtual CC Indicates that the stored card is a virtual card. Appears only when the reservation marks it as virtual. An Activation Date is included when recorded, converted to your user time zone. It does not confirm a charge or grant permission to charge it. Total Calculated total due when the required recorded totals exist; otherwise the reservation Total. See the payment explanation above. This is not a payment action or a live balance inquiry. Transaction ID Transaction reference recorded with the reservation. Appears when present within a displayed card-information block. Its presence alone does not establish payment success. Keep it out of support screenshots and chat. Address Available address associated with the card. A dash means no address is available. It can differ from Booked By Address. Channel did not provide any credit card information No card-information block is available to display for this version. This is different from protected or partially supplied information. It does not establish an unpaid booking. Additional links The property-specific detail document can also offer these links depending on the entry path and available features. They are not included in the Org Admin detail document: - Return to report returns to the originating report when that report context was supplied. - Guest messaging appears when messaging is available to you for the property; it opens the reservation's messaging workspace. Opening it does not send a message. - Guest reviews appears when reviews are available to you and reviews are associated with the reservation. The link includes a count. These links are not reservation-modification or delivery-success controls. If an expected feature is absent, ask your organization administrator to check availability and access rather than changing the URL. Common problems - No matching Search result: check the selected property and complete reservation number. Clear unnecessary channel, status or date restrictions. In the property-specific search, check Include Archived; Org Admin search already includes archived reservations. Select Search again. An empty search does not prove the reservation was never received. If it remains missing, give support the property, source channel, reservation number, relevant dates and search time with time zone. - The details look older than the channel booking: check for the previous-version warning and search again for the latest stored version. If that version still differs, provide the reservation reference and the change's approximate time. Do not resend or recreate a booking merely to refresh its details. - Total does not match the room-rate sum: compare the same currency and tax basis, every room, and both reservation-level and room-level extras. Explicit totals and calculated component sums can differ. If the difference is unexplained, ask support before treating it as an amount to charge or refund. - Guest counts, contacts or remarks are missing: these fields depend on what was recorded for that version and scope. Check Booked By, every room and both sets of Remarks separately. If operationally necessary information is still missing, confirm it through your authorized booking workflow; a dash is not confirmation of zero guests or no requests. - Card details are protected or incomplete: the Org Admin document always uses the protected card summary. If you need full details, use the property-specific path with your own account and ask your organization administrator to check Reservations - Credit Card access and any account restrictions. Confirm the source booking's payment arrangement. Do not use another person's login or request payment data through support chat. - A saved detail link fails: return to Search in the correct property and use its actual result link rather than editing identifiers in the address. If that link also fails, report the property, channel, reservation number, action time and visible error text. Include only the information needed for investigation. Do not send passwords, card details, transaction references, full reservation screenshots or unnecessary guest information. Related - Reservations: search and delivery-request forms - Check reservation delivery status - Investigate reservation delivery failures
Update rates, availability and restrictions with Detail Update
Use Detail Update to prepare rates, available rooms and selling restrictions for selected dates, inspect the pending values for each channel, and submit the intended changes for processing. Before you start - Select the correct property, then open Updates → Detail. Confirm the Detail Update heading before entering anything. - Your user needs property access and the relevant update permissions for rates, availability or restrictions. Channels, rooms and rate plans must be enabled and set up for updates. A field appears only where its permissions, channel capabilities and configuration support it. - Know which rooms, rate plans, channels and dates should change. Check the property's rate calculations, linked products and rounding rules before using broad fields. A room change can populate related rate plans or linked rooms; a plan change can populate linked plans. - If a PMS supplies inventory, check the override policy first. Manual updates can block later PMS changes for configured fields. Without an override, a later PMS update can replace your manual values. Leaving a field blank does not remove an existing override. See PMS Overrides. This is a pending-update form, not a display of current inventory. A fresh form starts with blank update fields. Blank does not mean the channel currently has no rate, no availability or no restriction. Changing a field can start calculations that populate other fields on the form. Those calculations prepare the update; Send Updates is the submission control. Leave the edited field, let population finish, and review the results before continuing. Do not treat a value remaining on screen as proof of a saved update. 1. Choose dates and weekdays 1. Under Date Ranges, enter Start date and End date using the displayed date format or calendar. Both dates are included. For one day, use the same date twice. 2. Under Days, keep the weekdays that should receive the changes. All seven are selected initially. Each range must include at least one selected weekday that actually occurs within that range. 3. For a separate period with the same values, click Add Date Range and set that range's dates and weekdays. The screen supports up to ten ranges. 4. Remove an unwanted additional range with its [ X ] link. Recheck the remaining ranges before submission. Date Ranges controls with blank Start date and End date, Add Date Range, and all seven weekdays selected. Use today or a later date in the property's time zone, and put the end date on or after the start date. An unused extra range may remain blank; a partially entered range needs both dates. A Friday-only selection in a Monday-to-Thursday range contains no update days. Every selected date receives the same pending values. Multiple ranges do not give you separate prices or restrictions per range. If two periods need different values, handle them as separate, reviewed submissions. Avoid overlapping ranges when one range will do. Channels can have different advance-booking limits. Read any future-date warning: dates beyond a channel's supported limit may be trimmed or omitted, not held for automatic delivery later. 2. Choose the intended channels In the normal Detail mode, scroll to the channel sections and select the intended channel checkboxes before entering upper-level values. Select All Channels selects all enabled channel boxes; when all are selected, clicking it clears them. A partly selected group shows a partial-selection indicator. These boxes are populate/clear controls, not a final sending checklist: - Selecting a channel can copy the current upper room and rate-plan values into its mapped products, with configured calculations. - Clearing a channel clears its pending channel fields and calculated labels. It does not clear the upper room and rate-plan entries. - Selecting it again can repopulate those fields. This is not a way to restore a previously typed channel-specific exception. - What matters at submission is the populated destination fields. Do not assume that an unchecked box by itself prevents a populated channel value from being submitted. Review every channel section before sending, including channels you do not intend to change. Their pending fields should be empty. Never use a channel checkbox as a substitute for checking the values. If your property uses standard-only updates The channel boxes are fixed and the channel room/rate-plan fields are disabled. Enter changes in the upper Room Types and Rate Plans sections. The configured channel mappings determine the destinations; you cannot use Detail to select an individual channel in this mode. Do not use a broader upper-level edit to work around a disabled channel field when your actual goal is a channel-only change. Ask your administrator or support which update mode and workflow are appropriate. 3. Enter values at the narrowest useful scope For a broad change, work from broad to specific: global fields first, individual rooms next, individual room/plan combinations next, and channel-specific exceptions last. A later broad change can replace a more specific pending value. Where you enter the value Intended scope and what to review Global Room Type in Room Types A starting value across the property's room types. It populates individual room fields and their eligible mapped channel products. Rate calculations can make the room or channel values differ from the global entry. This is not a separate room you can sell. A named room column in Room Types That property's room, with configured room-to-plan and parent/child relationships. Review the room's rate plans and any linked rooms as well as the main room field. Global - [plan name] in Rate Plans That property rate plan across room types. Review each room's plan values and mapped channel destinations. A plan field in one room's column in Rate Plans That room/plan combination, plus any configured linked-plan propagation. Keep broader fields blank for a plan-only change. Columns follow the room order shown above. A room field inside a named channel That channel's mapped room-level value, where supported. It is different from the upper property-room field. Review any associated channel rate-plan fields separately. A rate-plan field inside a named channel That channel's mapped room/rate-plan value, where supported. Check both the property name and the channel mapping name shown in parentheses. Unmapped , when shown in Rate Plans Channel rate plans that do not have a property rate-plan mapping. It does not mean all plans, and it does not repair a missing mapping. Review the actual destination products. Room Types: Global Room Type and Studio columns with Sell Rate, Allocation, Stop Sell, Cut Off Days, arrival and through-stay night limits, CTA and CTD. This focused crop shows Global Room Type and the first room, Studio. Your room names and available fields may differ. Change a rate 1. Enter the positive Sell Rate at the intended scope. For one room only, leave Global Room Type blank and use that room's field. 2. Leave the field and wait for the pending calculations to finish. 3. Review the Rate Plans section, linked rooms/plans, and each selected channel's final rate. Check additional occupancy rates and Net Rate displays where present. 4. Leave allocation and restrictions blank unless you also intend to change them. If calculations or channel-specific edits do not populate as expected, stop before sending and contact support; do not assume submission will repair a missing calculation. Changing a channel's main rate can affect configured additional rates. Enter channel-specific exceptions only after the broader values have settled, then recheck the entire destination product. Change availability or close/reopen sales 1. Enter Allocation at the intended scope when changing the number of rooms available. Enter the intended quantity, not a plus/minus adjustment. 2. Review Stop Sell immediately. An upper allocation of 0 also populates a close-out. A positive allocation can populate Stop Sell = No when automatic reopening is configured. Review the resulting room, linked-plan and channel values—not only the field you typed. 3. To close sales explicitly where supported, use Stop Sell = Yes. To request reopening, use Stop Sell = No and verify that availability and the other restrictions permit selling. 4. Check the channel fields before sending. Depending on the channel and configuration, a close-out can be represented by zero allocation instead of a separate Stop Sell value. Reopening may require restoring a valid allocation; No alone is not a guarantee that a room becomes bookable. Restrictions that a channel cannot represent may also lead to a configured close-out. If an unexpected Stop Sell or zero Allocation appears, resolve it before submission rather than treating the value as harmless. Change one rate plan's restrictions 1. Leave the global room and individual room restriction fields blank if the change is only for one plan. 2. In Rate Plans, use Global - [plan name] for that plan across rooms, or the plan field under one room's column for one room/plan combination. 3. Enter the restriction, such as Min Nights Arrival = 3, and wait for population. 4. Review the mapped destination plans and any configured linked plans. Check that unrelated plans remain blank and that no unintended close-out was populated. Rate Plans: Global - Standard and the first room’s Standard column, showing separate rate, availability and restriction fields. The left column applies to Standard across rooms. The next column is Standard for the first room in the room order above; it is not a second global field. Review a channel-specific change In normal Detail mode, a channel section may offer direct room and rate-plan entry. First select the channel, confirm the correct mapped product and review any existing pending entries. Keep upper fields blank if you do not want to prepare a broader change. Enter only the intended channel fields, then check the channel checkbox, rates, additional rates and calculated labels yourself. Do not assume direct entry automatically selects the channel or refreshes every calculated value. If the field, checkbox or calculated labels behave unexpectedly, stop and contact support before Send Updates. Do not switch to an all-channel/global edit to bypass the problem. 4. Review, send and check the result Before sending, check: - The property, every date range and each range's selected weekdays. - Every nonblank upper room/plan value and the linked products it populated. - Every channel section, including those you intended to leave unchanged. - Rates and any occupancy rates; allocation together with Stop Sell; arrival and through-stay restrictions; channel-specific options. - That population has finished and Send Updates is available. 1. Click Send Updates once. 2. Read all confirmations, warnings and errors. A saved confirmation means requests were saved for processing—not that every destination accepted them. Some requests can save while others fail. 3. Open Updates → Status for the same property. Set Status to All, choose the relevant Channel, Room Type and Rate Plan, then click Search. Check any other active criteria if the expected requests do not appear. 4. Match the request's affected dates, values and creation time to your submission. One submission may produce multiple requests, so check the complete intended scope rather than one successful row. 5. Pending and Processing are not completion. Inspect Unsuccessful messages. Successful is the recorded processing outcome; check the channel's extranet when you need to confirm its current selling state. An error is not a rollback. Valid requests can already be saved when other requests fail. Some fields may clear while failed values remain, and dates or upper values may reset after a partial success. Do not resend the form based only on what remains visible. Master inventory and configured PMS overrides can save independently of channel-request success. An empty Status search or a “No updates have been saved” message does not prove that nothing changed. Check request history and ask support to confirm saved inventory and overrides before resubmitting when the result is uncertain. Cancel reloads Detail and discards unsent form entries. It does not cancel processing, undo a saved request or remove an existing PMS override. Worked examples These are planning examples, not suggested prices or inventory levels for your property. Use the actual product names and supported fields in your account. Friday and Saturday arrivals: one plan, one room To require three nights for Friday/Saturday arrivals on one room's Standard plan: 1. Choose the period, keeping only Fri and Sat under Days. 2. Select the intended channels in normal Detail mode. 3. Leave global fields and the room's general restriction fields blank. 4. In that room's Standard column under Rate Plans, enter 3 in Min Nights Arrival. Do not use Min Nights Thru for an arrival-only rule. 5. Inspect that plan's channel fields and linked plans, then send and verify through Updates → Status → Search. Close one room for a maintenance period To close a room across its intended selling products, select the dates and channels, then use that room's Stop Sell = Yes. Review all of its mapped plans and virtual/linked products. If the channel uses allocation for closure, verify the resulting zero allocation. Do not enter a new rate unless it should also change. Before reopening later, confirm both availability and all remaining restrictions; clearing the old form is not reopening. Two separate periods with the same rate Use Add Date Range for the second period, set the weekdays independently, and enter the rate once at the intended scope. The same values apply to both ranges. If the second period needs a different rate, do not add it to this submission; complete and verify the first scope before preparing the second. Full field reference Defaults, blanks and accepted input A fresh Detail form has one visible date-range row, blank dates, all weekdays selected and blank update entries. In normal mode the channel boxes start unselected; standard-only mode fixes the channel selection. The examples below are input examples, not defaults and not guarantees that a particular channel accepts the value. - Blank: no explicit change supplied by that field. It does not erase a stored rate/restriction or remove a PMS override. Clearing an upper field may clear pending values below it; always inspect the destinations afterward. Other populated fields, calculations and configured channel defaults can still affect the request. - 0: a real numeric value, not blank. It closes availability when used for allocation. It is not a valid way to clear a selling rate. For nights, cut-off days and channel-specific options, zero's accepted meaning is channel-dependent; do not assume it universally means “unlimited” or “remove.” - No: an explicit negative value. For Stop Sell, CTA and CTD it requests removal of that particular restriction, not removal of all restrictions. - Whole-number fields: use nonnegative whole numbers, without a sign, currency symbol or thousands separator. Standard allocation/day/night inputs must fit 0–32767; this is the form's parsing limit, not a channel's accepted business range. A channel may impose a much smaller maximum. - Rate fields: enter a positive amount, normally to two decimal places, using the page's decimal convention and without a currency symbol. Room minimum-rate rules, calculated net rates and channel requirements still apply. Rates and inventory Field What it changes Accepted input, blank/zero meaning and example Sell Rate The selling amount for the identified scope. Upper values can be transformed by room, plan, channel and rounding rules. Positive decimal amount, for example 150.00 . Blank supplies no rate change. Zero or a negative rate is not a clearing command; rates at or below zero and rates below the room's allowed minimum can be rejected. Check calculated destination values too. Net Rate A calculated display for channels using a sell/net markup or margin model. Read-only display, not another amount to type and not proof of channel acceptance. It can be blank before calculation. If it does not refresh as expected, stop rather than assuming the displayed value is current. Occ 1 Sell Rate , Occ 2 Sell Rate , and other configured occupancy Sell Rate fields A price for the stated number of occupants on that channel product. Occ 1 means one occupant; it is not an extra-person surcharge or a room-count field. Positive decimal amount for each displayed occupancy. These fields appear only for supported and enabled occupancy pricing. Configured calculations may populate them from the main rate. Some channel pricing models require a complete set; review the displayed set and any validation message rather than assuming one field is enough. Occupancy Net Rate displays The calculated net counterpart of an occupancy Sell Rate where the channel supports the model. Read-only. Review alongside the corresponding occupancy Sell Rate; do not enter a rate into the label or assume a blank label means zero. Allocation The number of rooms offered for the selected dates and scope. It is an absolute available quantity, not a delta or occupancy count. Nonnegative whole number, for example 5 . 0 supplies no availability and can also close Stop Sell. A positive value can reopen Stop Sell when automatic reopening is configured. Blank supplies no allocation change. Stop Sell Whether sales are closed for the specified product and dates. Blank / Yes / No . Yes closes; No requests opening. It does not restore missing inventory, clear CTA/CTD or override stay-length limits. Review allocation-based closure where a channel does not support a separate Stop Sell field. Agoda.com channel: Studio room Allocation and Stop Sell, plus Standard plan Sell Rate, Net Rate, Occ 1 Sell Rate, Occ 1 Net Rate and restrictions. Example channel section: the Studio room has Allocation and Stop Sell, while its Standard plan has rates and stay restrictions. Occ 1 Sell Rate and the Net Rate labels are separate from the main Sell Rate. This is a blank pending form, not a current-inventory report. Booking and stay restrictions Field What it changes Accepted input and example Cut Off Days The minimum advance-booking lead time, in days before arrival, where supported. This is not a stay-length limit. Nonnegative whole number; 2 requests a two-day lead-time rule. Blank supplies no change. Use 0 only when that channel's zero-day/reset rule is appropriate; it is still an explicit value. Min Nights Arrival Minimum stay length for bookings arriving on a selected date. Whole number of nights; 3 requires a stay of at least three nights for those arrivals. Blank supplies no change. Use the channel's supported value to relax the minimum; zero is not a universal reset. Max Nights Arrival Maximum stay length for bookings arriving on a selected date. Whole number of nights; 7 requests a maximum seven-night stay for those arrivals. Keep it consistent with the corresponding minimum. Blank supplies no change; confirm the channel's unlimited/reset convention before using zero. Min Nights Thru A minimum-stay restriction for stays passing through a selected stay date, rather than only arrivals on that date. Whole number of nights, for example 3 , where supported. A guest arriving before the selected date can be affected. Blank supplies no change. Channel rules determine the treatment of a zero and how multiple stay-date restrictions combine. Max Nights Thru A maximum-stay restriction for stays passing through a selected stay date. Whole number of nights, for example 7 , where supported. Keep it consistent with the through-stay minimum. Blank supplies no change; do not assume zero means unlimited. CTA — Closed to Arrival Whether arrival is prohibited on each selected date. It does not by itself close every stay that crosses that date. Blank / Yes / No . Yes closes arrivals; No removes this arrival restriction. Availability, Stop Sell and other restrictions still apply. CTD — Closed to Departure Whether departure is prohibited on each selected date. Blank / Yes / No . Yes closes departures; No removes this departure restriction. It is not interchangeable with CTA or Stop Sell. For all restriction fields, the selected weekday/date combination is the date to which the rule applies. Arrival rules and through-stay rules are different; do not substitute one because the other is unavailable. Additional channel fields, when enabled A channel can expose additional rate or restriction options inside its own room or rate-plan section. These are not global fields. Their presence and choices depend on the integration and the enabled product settings. Use the displayed label, choices and tooltip for that destination. Do not copy a provider-specific value into another channel's similarly named field. Additional entries start blank. Blank omits an explicit value; some integrations then use configured defaults when constructing a request. It does not necessarily remove the existing channel setting. A zero amount, No, or a named “no meal/no guarantee” choice is an explicit selection, not an empty entry. Additional field or group Meaning and input Extra Adult , Extra Child , Extra Person or Extra Person Fee Additional-person pricing where that integration offers it. Enter the amount for the named supplement, not an occupancy-total price. Depending on the integration, it appears as an additional Sell Rate or a channel-specific amount field. Follow its configured pricing basis; do not assume zero is accepted or clears the supplement. Extra Bed , Child Rate , Junior Rate Additional channel rate fields where configured, such as Agoda extra-bed pricing or Best Day child/junior pricing. Enter a positive amount for the named category and review its configured calculation. Child and junior age categories belong to the channel's setup; do not assume these mean the same as Occ 1 or Occ 2. Rollaway Adult , Rollaway Child , Crib rates The named extra-bed/crib amounts on integrations such as reconline. Review the configured calculation/default for each item. These are not room allocation fields. Maximum advance booking days A maximum advance-purchase window on integrations that expose it, such as Trip.com. Enter whole days according to that channel's rule. It is separate from Cut Off Days , which supplies the minimum lead time, and from the channel's technical limit on how far ahead updates can be sent. Breakfast Included Whether breakfast is included on integrations such as Caesar Data. Choose blank, Yes or No ; No is an explicit exclusion, not “leave unchanged.” Credit Card Guarantee Whether the product requires a credit-card guarantee where offered. Choose the displayed blank/Yes/No option. This sets a booking rule; it is not a field for entering card details. Breakfast Type A channel-specific included/excluded breakfast choice. HRS displays blank, Exclusive (breakfast excluded), or Inclusive (breakfast included). Select the applicable option rather than entering a price or occupancy. Exclusive Rate The channel's exclusive-rate flag where offered. Choose blank, Yes or No in accordance with the channel agreement. It does not mean an exclusive change to only that room. Surcharge / additional-room surcharge A channel-specific surcharge amount, such as HRS additional-room/category pricing. Enter a monetary amount on the integration's agreed basis. Rebate / additional-room rebate and Rebate Type A rebate value together with its unit: flat amount or percentage where offered. Keep the value and type consistent; do not enter a percentage as a flat currency amount. Free Sale A channel-specific free-sale flag at room or rate-plan level where supported. Choose blank, Yes or No only with a confirmed channel configuration; do not treat it as a substitute for an ordinary allocation update. Cancellation Possible Whether cancellation is allowed under the offered channel policy. Choose blank, Yes or No where provided. It changes a policy, not an existing reservation's cancellation status. Reservations / reservation mode The product's reservation/guarantee mode, such as standard, guaranteed or guaranteed with credit card on HRS. Select a displayed option, not a reservation number. Cancellation Deadline A provider-defined deadline choice. HRS can offer standard or named day-before-arrival choices; reconline can offer time-of-day or day-based choices. Select the appropriate labeled option; do not interchange raw numbers between providers. Cancellation Deadline Days A whole-day cancellation lead-time value where the channel exposes a separate numeric field. Coordinate it with that product's policy and any deadline selector. Cancellation Fee Percent The cancellation penalty percentage where offered. Enter a whole-number percentage consistent with the agreement; do not enter a currency amount. Pre Pay Percentage The prepayment percentage where offered. Enter a whole-number percentage consistent with the agreement, not a monetary amount. Advance Booking Deadline A whole-day advance-booking/reservation deadline where offered by HRS. Use the integration's agreed policy; it is not a length-of-stay field or the technical horizon for sending updates. Board Type / Meal Plan The included meal basis. HRS Board Type offers blank, Exclusive , InclusiveBreakfast , InclusiveHalfBoard , InclusiveFullBoard , and AllInclusive . Other channels can offer named meal/breakfast variants. Only the choices offered in that field are supported. A named no-meal option is an explicit selection; blank is not the same thing. Guarantee A provider-specific guarantee selection, such as no guarantee, IATA guarantee, credit-card guarantee or credit-card deposit on reconline. Select the displayed choice rather than entering payment credentials. Some additional controls accept whole numbers, two-decimal amounts, or a single/multiple selection. A multi-select can supply several supported choices; review all selected options. Do not guess a channel-specific default, reset value or allowed maximum from the field's appearance. If the option or its meaning is unclear, confirm it with support before sending. Date, selection and page controls Control What it does Start date / End date Inclusive date boundaries. Required for each range you use; dates must not be in the property's past. Days: Mon–Sun Limits that range to the selected weekdays. All start selected; at least one must occur within the range. Add Date Range Reveals another range for the same pending values, up to ten total. [ X ] beside an additional range Clears/removes that extra range from the pending submission. It does not undo saved updates. Channel checkbox Selects/populates or clears that channel's pending fields in normal mode. It is not a server-side sending allowlist. Select All Channels Applies the selection/clearing action to enabled channel boxes. Selecting again can repopulate from upper values. Settings inside a channel Opens that channel's configuration in another tab. Opening it does not submit this form. Settings changes are a separate task; do not alter configuration to bypass an unexplained disabled field. Toggle Row Wrap , when shown Changes the visual arrangement of long product rows. It does not change the intended update scope. Send Updates Submits the pending form for validation and request processing. A saved message is not channel acceptance. Cancel Reloads the editor and discards unsent entries; it does not undo previous submissions. Linked headings: exact populate/clear behavior Blue room and plan headings are actions, not expanders. Scroll to inspect a section; do not click a heading merely to read it. These shortcuts affect pending values and calculated labels, not saved inventory. A field containing 0 or No counts as populated, and a nonblank calculated label can count too. Heading you click Behavior to expect and review Global Room Type Always clears the global room values, global plan values, individual room values and individual room/plan values. It also clears pending fields in selected, enabled channels. This is a broad clear action, not a toggle that reloads current inventory. Review every channel afterward; do not assume it is a universal reset of unchecked or disabled sections. A named room in the upper Room Types section If its controls/labels contain a value, clears that room's pending upper values, its upper plan values and corresponding fields in selected, enabled channels. If the room is empty, the populate action reads Global Room Type values and applies the room calculations. It does not load saved inventory or take its values from the global plan fields. With no usable source values, there is nothing to restore. Global - [plan name] If any individual room/plan field for that plan contains a value, clears the global plan fields and the individual room/plan entries for that plan, with corresponding clearing in selected, enabled channels. If those individual plan fields are empty, it repopulates from each room's upper room values, using the plan calculation for rates. It does not restore the last saved channel values. A plan heading under one room in the upper Rate Plans section If that room/plan block contains pending values or labels, clears that block and corresponding mapped fields in selected, enabled channels. If empty, populates from that plan's global values where provided, otherwise from the room's upper values, with the relevant rate calculation. A linked room heading inside a channel If that channel-room block contains pending controls/labels, clears that room-level block. Otherwise it populates from the applicable upper room/plan data. Associated channel rate-plan blocks are separate: clearing the room heading does not mean all its plans were cleared. A linked rate-plan heading inside a channel If that channel-plan block contains pending controls/labels, clears it. Otherwise it populates from the applicable upper room/plan data and mappings. A successful populate response can select the channel. Review the actual fields and checkbox rather than relying on that side effect. Headings rendered as plain text are not populate controls. Channel mappings, virtual rooms, linked plans and disabled controls can make the affected scope less obvious, so inspect the resulting destination fields after any shortcut. For a clean restart of the entire unsent form, use Cancel rather than a sequence of heading clicks. Troubleshooting What you see Likely cause and safe next step Missing/disabled fields, Not Setup , or Channel Temporarily Disabled Check update permissions, product setup, channel availability and the property's update mode with an administrator. Do not use a broader field to circumvent the restriction. Escalate if the expected supported product remains unavailable. Date-format, missing-date or past-date error Use the date picker and confirm both boundaries in the displayed format and the property's time zone. Read the full result before retrying; do not assume every kind of error means no earlier request saved. No weekdays selected, or no selected weekdays within the range Select at least one weekday that occurs inside each range. Recheck additional ranges as well as the first. A rate is rejected Check that it is positive, meets the room minimum and leaves valid calculated sell/net and additional rates. Correct only the outstanding scope after checking Status for partial saves. Values disappear after clicking a heading The heading may have cleared pending entries. Review the shortcut reference above. It did not undo saved inventory; re-enter only the intended unsent changes. Unexpected rates, missing population, a checkbox not updating, or a stale Net Rate label Stop before sending. Check the property, product mappings and configured calculations with support. Do not assume the missing values will be repaired at submission. Unexpected close-out or reopening after an allocation/restriction edit Review Allocation and Stop Sell together at room, plan and channel level. Automatic closure/reopening or unsupported-restriction handling may be configured. Resolve the discrepancy before sending. A future-date warning A channel supports a shorter update horizon. Inspect the saved request dates; dates outside that horizon may not have been included. Do not assume they are queued for later. Mixed confirmations/errors, an uncertain response, or No updates have been saved Open Updates → Status , use All , apply the relevant filters and click Search . Master inventory/overrides may have saved independently. Ask support to confirm the saved scope before repeating an uncertain submission. A saved request is still Pending/Processing or is Unsuccessful Inspect its recorded details and error message. Do not repeatedly resend or use a blanket retry. Escalate with the request identity and intended scope if the correct next action is unclear. A later PMS update replaces your manual value, or PMS values no longer flow through Review the configured override policy and existing overrides. Blanking Detail is not an override-removal workflow. Use the PMS Overrides guide and obtain confirmation before changing override settings. For support, provide the property, channel, room/rate plan, affected dates and weekdays, intended values, action time with time zone, request IDs and exact error text. Do not include passwords, card details or unnecessary guest information. Related guide - PMS Overrides — understand how manual changes interact with PMS-supplied inventory.
Add a virtual channel room type
Connect an additional room type on a channel to an existing standard room type in your property. A virtual room type is an additional channel mapping under a standard property room type. It does not create another standard room type or another physical room. For example, if two room products on a channel should belong to the same standard room type, one can be the main mapping and the other a virtual mapping. Confirm that relationship before adding it; a similar name is not enough. Before you start - Select the correct organization and property, then confirm the channel you are configuring. - You need Channel Settings permission to save. If the form is disabled, ask your organization administrator to check your permissions. Public demonstration logins cannot submit this settings change. - The channel must already be assigned to the property, and the intended standard room type must already exist. - Have the channel-confirmed room name and room ID. Check the existing mappings first so you do not add a room that is already connected. - This workflow is not supported for Inventory Receive connections, such as a PMS sending inventory into ChannelRUSH. The Add Virtual Room Type link can still appear for those connections; its presence does not mean they support virtual rooms. - Plan the virtual room's rate-plan mappings, occupancy and updating settings as well. Adding the room is not proof that its complete setup is ready to distribute inventory. Save is a real settings change, not a preview. ChannelRUSH saves the mapping locally and, for connections that support it, then attempts a settings push. The push can concern the connection's settings, not only the new room. Review the property and channel before saving. A later send error does not undo the local save. Open the form 1. Select your property in the property selector. 2. Open Admin → Settings - CM. 3. In Channel Manager → Channels, click the channel's name. 4. On Channel Settings, open Menu → Add Virtual Room Type. There is also an Add Virtual Room Type link above the room sections. 5. Confirm the channel in the breadcrumb and the heading Add New Virtual Room Type. If you normally work from Accounts, clicking the channel name beneath the correct property opens the same Channel Settings page. Choose the parent room type In Room Type To Add Virtual Room Type To, select the existing property room that should contain this additional channel mapping. The standard property room name appears in square brackets. If its main channel mapping has a name, the option also shows that channel name and its ID. Those details identify the parent's existing mapping, not the new virtual room's name or ID. Parent room selector showing standard room names in brackets and their existing channel mappings Example choices from a demonstration property. Use your property's room names and channel IDs. The selector starts blank. You must choose a parent. If the intended standard room is missing, stop and confirm the selected property and its standard room setup rather than attaching the virtual room to another room temporarily. Add the channel room The form shows one of two alternatives. You do not need to fill both. When you see Virtual Room Type To Add This dropdown appears when ChannelRUSH has stored channel mapping information containing room IDs that are not already mapped in this connection. 1. Select the intended room in Virtual Room Type To Add. 2. Check both the displayed channel room name and ID against the room you intend to connect. 3. Recheck the parent room, then click Save once. The selection supplies the channel room's name and ID. ChannelRUSH also takes its updating-enabled value, available occupancy values and supported room-level settings from the stored mapping information. It does not copy all of the parent's settings or automatically add every rate plan. The list uses stored mapping information; opening this form does not retrieve a fresh room list from the channel. A missing room can mean it is already mapped or is absent from the stored list. Do not choose another room as a substitute. Check the channel settings and ask support to help verify the mapping information if necessary. When you see Virtual Room Type Name and Channel Room Type ID: This is the manual-entry form. It appears when the stored mapping information does not offer an unmapped room to select; that does not prove the channel has no other rooms. 1. Enter the intended channel room name in Virtual Room Type Name. 2. Enter its exact channel-issued identifier in Channel Room Type ID:. This is not the standard property room ID or the ID displayed beside the selected parent. 3. Check the parent, name and ID together, then click Save once. Add New Virtual Room Type manual form with parent selector, name, channel ID, Save and Cancel The manual form starts with blank fields. Do not copy IDs from the example parent selector. Use a meaningful name and the correct nonblank channel ID even though these fields do not show required markers. A saved entry with missing setup information is not a usable mapping. The ID is a channel identifier, not a number to calculate or invent; preserve its provider-defined spelling and leading zeros where applicable. The manual form has no Updating Enabled control. A manually created virtual room starts with updating enabled at the room level; connection-level settings, supported fields, rate-plan settings and setup completeness still govern what can be sent. Review those settings on the result page before using the new mapping. Check the result and finish setup After a successful local save, the normal destination is Channel Settings. If the selected stored room has rate plans still to add, ChannelRUSH can open Add Unmapped Rate Plans instead. On Channel Settings 1. Find the selected standard room's section and the additional section labeled Virtual Room Type with the new name. 2. Check the virtual room's Channel Room Type Name, Channel Room Type ID and parent room. Reopen the channel settings if you need to confirm what was stored. 3. Review the virtual room's Updating Enabled, occupancy, required channel-specific fields and rate-plan mappings. The creation form does not replace that review. 4. If rate plans are needed and no import screen opened, use Add Rate Plans for the intended virtual room. Follow Add channel rate plans, selecting the virtual room rather than only its parent. For the remaining connection and product fields, see Configure OTA and PMS channel settings. If Add Unmapped Rate Plans opens The virtual room has already been saved. This is a separate step for adding its rate plans, not an unsaved preview of the room. If this screen fails to load, reopen the same channel's Channel Settings and check for the saved virtual room. Do not repeat Add Virtual Room Type. Ask support to help complete its rate-plan setup if the follow-up remains unavailable. - Locate the heading for the virtual room you just added. Other room headings may also be visible; do not assume this redirected workflow will save changes for those other rooms. - Review the offered rate-plan checkboxes. Plans are initially selected, so clear any you do not intend to add to this room. - For each intended plan, check Rate Plan Name, the displayed Channel Rate Plan ID, Updating Enabled and, when available, Standard Rate Plan Mapping. Choose the correct standard mapping when the plan should follow one. - Click Save only when the intended plans and mappings are correct. This is another settings submission and can attempt another channel settings push. - To postpone rate-plan setup, click Cancel to return to Channel Settings. Canceling this follow-up does not remove the virtual room already saved in the preceding step. Reopen the channel settings and check the new virtual room and its rate plans after this step. If the expected virtual-room section is missing from the follow-up, or the room/plan IDs are not the ones you intended, stop and ask support rather than saving unrelated entries. What the result does—and does not—confirm A local save confirmation and a visible mapping establish that ChannelRUSH stored configuration. They do not prove that the channel accepted rates or availability, or that the room is available for sale. Some connections attempt a settings push and can show a separate send result. Others do not send settings through this action. Even a successful settings-send result is not confirmation of an inventory delivery. For example, Booking.com's settings-push behavior depends on its pricing mode; it is not a general room-creation confirmation. Use Mapping Coverage to review the stored relationship. Confirm the intended products and downstream channel state separately before treating the setup as complete. Do not send a test inventory update merely to check whether a room was saved. Field and action reference Field or action What it does What to check Room Type To Add Virtual Room Type To Chooses the existing standard room's channel mapping that will contain the virtual room. Initially blank. Select the correct standard room in brackets. Any accompanying channel name/ID describes its existing main mapping. Virtual Room Type To Add Appears only when stored mapping information offers unmapped channel rooms. Initially blank. Supplies the selected room's name, ID and available supported mapping settings. Select the exact channel product. Already-mapped room IDs are omitted. The list is not a live channel refresh. Virtual Room Type Name Manual alternative for the new virtual mapping's name. Initially blank. Use the intended channel room name. It does not rename the standard parent room. Channel Room Type ID: Manual alternative for the channel's identifier of the additional room. Initially blank. Use the provider-confirmed room ID, not the parent's existing channel ID, a rate-plan ID or a ChannelRUSH standard room ID. Blank is not a removal command on this creation form. Save Submits one new virtual room, validates the virtual room/settings, saves locally, and then invokes any supported settings push. Can continue to rate-plan import. Check the result before repeating an uncertain submission. Saving is not an inventory-delivery test. Cancel Leaves this creation form for the same channel's settings without submitting its new room. It does not undo any earlier completed save. If a leave-without-saving confirmation appears, review it before discarding your unsent entries. Channel breadcrumb Returns to the same channel's settings. Do not use navigation as a substitute for Save when you intend to add the room. Common problems What you see What to check and do next The form or Save is disabled Ask your organization administrator to check Channel Settings permission. A public demonstration login cannot save this change. Do not try to bypass the restriction. The parent selector is blank or does not contain the intended room Select a parent. If no appropriate choice exists, verify the property and standard room setup before continuing. No Virtual Room Type To Add dropdown The form has no unmapped room available from its stored mapping information. Use manual entry only with confirmed channel details; absence of the dropdown is not evidence that the room does not exist remotely. The expected room is missing from the dropdown Check whether its ID is already connected, and confirm the correct channel/property. Ask support to verify the stored mapping list if it is missing or outdated. Do not map a different room to get past the step. A duplicate/already-mapped room error Review existing main and virtual mappings and the supplied ID. A room ID may already belong to another mapping or property for that connection. Resolve the intended relationship rather than changing the ID to an invented value. “For PMS/CRS companies (i.e. inventory receive), virtual room types are not allowed.” This connection receives inventory and does not support virtual rooms. Cancel and use the supported standard mapping workflow with your administrator or support. A room is saved but its setup is incomplete Check nonblank name/ID, occupancy, required channel settings and rate plans on Channel Settings . A save message is not a complete setup check. A settings-send error appears after Save, the rate-plan follow-up fails to open, or the browser times out The local mapping may already exist. Reopen the same channel's settings and check it before doing anything else. Do not submit another new room or repeatedly push settings to recover an uncertain result. Ask support to investigate the send result. Rate-plan import opens unexpectedly The chosen stored room has rate plans not yet present locally. Review only the intended virtual room's plans, or Cancel and complete that setup later. The virtual room itself is already saved. Validation leaves you on the form Review the displayed errors and recheck every field and selection before resubmitting. Do not assume all entered values survived unchanged. If the message is unclear or the same error returns with confirmed details, stop and contact support. For support, provide the organization/property, channel, intended parent room, channel room ID, action time and time zone, and the exact error text. Say whether the new virtual room appears when you reopen Channel Settings. Do not include channel passwords, authentication tokens or guest information. Related - Configure OTA and PMS channel settings - Add channel rate plans - Check room and rate mapping coverage
Check room and rate mapping coverage
Use Mapping Coverage to identify which room and rate targets are represented in one property's stored configuration, separate intentional exclusions from findings that need review, and export the evidence. Before you start - Select the property you want to investigate. You need access to that property; organization-wide access and permission to edit mappings are not required to read this report. - Know which channel and hotel product you expect to be connected. A product can be intentionally excluded from a channel, derived from another product, or priced independently. - This is a current stored-configuration report, not a live channel check or mapping history. Running it, changing its report filters, paging, and downloading CSV do not refresh mappings, change settings, or send inventory. Mapped does not mean correctly mapped, available for sale, or accepted by the channel. It means the report found a current target under the checks described below. Confirm that it is the intended target before treating a finding as resolved. Run the report 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Mapping Coverage. 3. Leave Channel = All property channels, State = All states, and Product kind = All for a first overview. To investigate a known problem, choose the relevant channel and product kind instead. 4. Click View report. Opening the page alone shows the filters; it does not run the report. 5. Check the property name, matching-row count, and extraction timestamp above the results. Mapping Coverage filter card with Channel, State, Product kind and View report The initial filter card. There is no date-range field: the report examines current stored configuration. After a run, Filters collapses and the submit button becomes Update report. Expand Filters, change the selection, then click Update report. Changing a dropdown alone does not replace the loaded result. Narrow by channel within the result When the result contains more than one channel, an All channels dropdown appears above the report. It offers the channels represented in that result, not every possible channel. 1. Open All channels. 2. Tick the channels you want to keep. Select all toggles the listed checkboxes. 3. Click Apply — reloads report when it appears. 4. Check the reloaded count and channel headings. This narrowing applies to the complete filtered result and CSV, not only the visible page. This is an additional filter: it cannot broaden a single-channel choice in the main Filters card. After narrowing, excluded channels may no longer appear in the result dropdown. To start over, expand Filters, choose All property channels, All states, and All, and click Update report. That also clears the result's extra channel selection. Unticking every channel is not a way to request zero channels. An empty selection removes that extra narrowing. Use the main filters to establish the scope you want. Investigate a finding 1. Read the channel heading first. Each section names the channel and its ID. The same hotel product can have different findings on different channels. 2. Identify the row's direction. A Room mapping or Rate mapping starts with a channel product and points toward a hotel product. A Hotel room coverage or Hotel rate coverage row starts with a hotel product for which that particular channel has no represented mapping. CRS room and CRS rate describe booking-engine configuration. 3. Compare Product with Current target. Confirm the IDs and names are the pair you intended. A present but wrong target can still be Mapped. 4. Read State, Enabled, Setup, and Evidence / limitation together. State shows one finding, not a checklist of every possible problem. For example, Disabled can take precedence over a missing target. 5. Decide whether the configuration is intentional. Check exclusions, virtual parents, inherited inventory, and independent CRS pricing before requesting a correction. The product-kind and state references below explain these cases. 6. If you need more configuration context, use Inventory Settings / Channel Settings below the report. It opens the property's Channel Settings report; it is not a repair or save action, and the Mapping Coverage state/product filters are not carried across. Actual mapping changes belong in the separate settings workflow and require the appropriate permission. 7. After an authorized person confirms or corrects the configuration, return here and click Update report. Recheck the exact channel/product/target and the new extraction timestamp. If you selected only Missing target, a corrected row may disappear because it now has another state. Use All states to inspect it again. Mapping Coverage result header showing the property, matching-row count, extraction time, CSV, New window and interpretation warnings Example: a demo-property result narrowed to Agoda.com room mappings. This is the result header and explanation; the detailed table continues below it. What a completed check establishes You have completed the diagnostic check when you can name the affected channel/product, identify its current target or missing relationship, and distinguish a confirmed intentional setup from an unresolved finding. A changed count or an empty result is not enough. The report does not establish live availability, correct remote product IDs, successful inventory delivery, or what a mapping looked like when an older reservation was made. For separate flow/processing evidence, use Channel Health; its processing states answer a different question from mapping states. Paging and freshness The matching-row count is for the full filtered result, not unique rooms, unique rates, or only the rows on screen. Different channels and product kinds can produce several rows for the same hotel product. The table shows at most 100 rows per page, grouped by channel. When a page contains multiple channel sections, click a channel heading (or focus it and press Enter or Space) to collapse or expand that section. This only hides or reveals rows on screen; it does not change the matching count, filter criteria, or CSV. A page with only one channel section has no collapse control. Use Next page and Previous page below the report when available. A channel section can continue on another page. Each page load reads current stored configuration again; the extraction time can change, and changes made between page loads can change the result. Expand Coverage and freshness beneath the results for the scope and limitations. The displayed extraction time is when the stored records were read, not when a mapping was last edited or a channel was last contacted. Preserve its displayed UTC offset when sharing it; do not assume it is your property's local clock. Expanded Coverage and freshness explanation with property, channel filter, state, product-kind scope and evidence contract In this technical scope line, “flow” means the selected Product kind for Mapping Coverage. Blank state or flow means no narrowing by that field. Download and share the evidence 1. Apply the filters you want and check the loaded report. 2. Click CSV beside Download. The file is named mapping-coverage.csv. 3. Open it as comma-separated UTF-8 data. It contains the full filtered selection, including channels chosen through the result dropdown, rather than only the current 100-row page. 4. Check PropertyId, View, ExtractedUTC, and the row-level ChannelId/ChannelName before sharing it. Keep the original file if a spreadsheet reformats IDs or dates. 5. Include the report URL or a written list of selected channels with the file. ChannelFilter records the main single-channel dropdown only; the additional multi-channel selection has no separate metadata column. A value of 0 in ChannelFilter therefore does not guarantee that the export was unnarrowed. CSV is a new read of current stored configuration, not a frozen copy of the table already open in your browser. Its extraction timestamp—and its rows if settings changed—can differ. There is no separate 100-row export limit in this report. For an empty selection result, CSV still contains the header and one placeholder row with State = No matching rows. That is not a product finding. Its ChannelId = 0 is a placeholder, not a real channel result; other product/evidence cells are blank. New window opens the loaded selection in a separate report window without the normal application navigation. It preserves the selected report/page criteria and leaves the original open, but also reads current data again. The New window control is not repeated inside that separate window. Share only what is needed: property, channel, product/target IDs or names, selected filters, extraction timestamp with offset, and the unexpected state or error. Do not send passwords, payment details, or guest information. Common problems and safe next actions What you see What it can mean Safe next action No rows match The channel/state/product-kind combination excludes the records, or the expected configuration is not represented. Reset the three main filters and click Update report . If the product is still absent, ask the mapping owner or support to check the intended setup. Absence is not proof of healthy distribution. A channel is in the results but not the main Channel list The report reads stored settings, while the main dropdown lists the property's channel choices. Stored configuration can have a wider scope than that dropdown. Use All property channels , inspect its section or the result-channel dropdown, and provide support with its name and ID if it is unexpected. Do not delete it solely to remove a report row. Missing target but Enabled = Yes Enablement flags do not establish that a valid hotel target exists. For a CRS rate, independent pricing can also explain a missing hotel-rate target. Check the product kind and intended target; ask the mapping owner to confirm the relationship. Do not enable, recreate, or send inventory to test it. Disabled with another suspicious value Disabled takes precedence for mapping/CRS rows and can hide other findings in State. Read Current target and Evidence / limitation too. Confirm whether disabling was intentional before any change. Mapped but the product is wrong, or a related row has a problem The existence checks are not a validation of the intended pair or the entire mapping chain. Compare the exact IDs and inspect related room/rate rows under All states . Escalate a wrong target even when the row says Mapped. Unknown , Enabled = Unknown , or Setup = Not established Required evidence is absent or not applicable; these are not synonyms for No or for success. Keep the unknown value in your report. For CRS, remote Setup is not applicable. For unexplained channel rows, send support the channel/product and evidence text. The result dropdown no longer lists a channel you excluded Its choices come from the latest result. Reset through the main Filters card and click Update report . A saved/direct link returns a filter error Its property, channel, page, output, or filter values may be invalid. Reopen Mapping Coverage from the selected property's Reports menu and use the normal controls. If it persists, give support the exact message and URL without credentials. Do not treat an error page as an empty successful check. You cannot open the property/report Your account may not have access to that property. Confirm the selected property and ask your organization administrator to check access. Escalate if access is confirmed but the error remains. For a saved link showing Check report filters, page and output format., Select an authorized property and a valid channel., Select valid channels., or Invalid state or flow filter., reopen the report from the property menu and reselect the normal controls. A message about 1–90 days of terminal request history concerns a shared link parameter, not a Mapping Coverage date filter; reopening the page restores the normal defaults. If any error persists, send support the exact message rather than trying arbitrary URL values. Re-running the report is safe for inspecting the latest stored configuration. It does not repair a mapping, refresh a provider's product list, or resend an update. Stop and seek confirmation when the intended mapping remains unclear. Field reference: filters and report controls Field or control Values, default, and behavior Property selector Defines the single property being inspected. Confirm it again after changing property; this is not a portfolio-wide coverage report. Channel Defaults to All property channels . A named choice narrows to that channel's stored rows. The all-channel result can include retained settings not offered in the main dropdown. State Defaults to All states . Standard choices are Mapped , Disabled , Missing target , Missing virtual parent , Not set up , and Intent unknown . Unknown can appear in results even though it is not a standard dropdown choice; use All states to include it. Product kind Defaults to All . Choices are Room mapping , Rate mapping , Hotel room coverage , Hotel rate coverage , CRS room , and CRS rate . This filter intersects with Channel and State. Filters Expands/collapses the main criteria card. Closing it does not apply pending selections. View report / Update report Runs the selected main criteria. Update report also resets paging and clears the extra result-channel narrowing. Neither button edits configuration. All channels result dropdown Available only when more than one channel is represented. Checkboxes stage a selection; Apply — reloads report runs it. All or none removes this extra narrowing. Matching rows Total detail rows in the loaded, filtered result across all pages. It is not a health score or count of unique hotel products. Extracted timestamp Time the report read the current stored records, with a displayed offset. It is not a last-mapping-change or last-provider-check timestamp. Channel section heading Names the channel and ID. When multiple sections appear on a page, click or press Enter/Space to hide/reveal that section's rows. Does not filter counts or CSV. Next page / Previous page Move through the 100-row pages using the current criteria. Only applicable directions appear. CSV Downloads every filtered row using the fixed column reference below. Re-reads configuration at download time. New window Opens the current loaded selection separately; hidden in that separate report window. Coverage and freshness Explains evidence limits and shows property ID, main channel filter ( 0 means all), state, product kind labeled “flow,” and the export contract. It does not list the extra multi-channel selection. Inventory Settings / Channel Settings Opens the property's separate Channel Settings report for context. Does not correct, save, or resend anything on Mapping Coverage. Field reference: the on-screen results The channel name and ID are shown as a section heading, followed by these seven columns. Column Meaning and how to use it Product kind Identifies the type and direction of the row. Use the product-kind reference below before interpreting Product or Current target. State One classification from the current stored configuration. Earlier checks can mask later findings; see the precedence reference below. Enabled Yes , No , or Unknown . Its meaning depends on product kind. It is not proof that every flow is enabled or that delivery works. Setup Yes , No , or Not established . For channel mapping rows, combines the applicable stored setup flags; it does not run a new setup/connectivity check. CRS rows show Not established because remote setup is not applicable. Product Channel room/rate identifier, hotel product ID/name, or CRS product identifier/name, according to kind. For a rate mapping, the channel room context appears after / room . Treat IDs as identifiers, not quantities. Current target The matched current hotel room/rate ID and name, or an explicit missing-target message. Coverage rows instead say No configured channel target . A present target still needs to be the intended target. Evidence / limitation Context such as real or virtual mapping, parent reference, inherited/derived inventory, independent CRS pricing, or unknown distribution intent. Read it with the other columns, not as independent proof of correctness. Product kinds and flag meanings Room mapping - Product → target: stored channel room ID → current hotel room ID/name. Missing IDs can display Unknown channel room or No current hotel room. - Enabled / Setup: Enabled combines the applicable channel inventory flow with the target hotel room's enabled flag when that room exists. Setup combines stored channel and channel-room setup flags. - Virtual and inherited rooms: a virtual room checks that its referenced parent mapping exists in the same channel settings. Its evidence names that parent. A real mapping can instead show that its hotel room inherits rates, availability, or restrictions from a parent. The report does not expand or validate all inherited values; its evidence text is not an exhaustive dependency check. Rate mapping - Product → target: stored channel rate ID plus channel room context → current hotel rate ID/name. A missing rate ID can display Unknown rate. - Enabled / Setup: Enabled uses applicable channel flows and, for outbound inventory, both room and rate send switches. Setup combines stored channel, room, and rate setup flags. - Derived rates and related rooms: a derived hotel rate can name its parent in Evidence / limitation. This row does not independently validate the room's hotel target or virtual-parent relationship; inspect the Room mapping row too. Hotel room coverage - Product → target: enabled hotel room ID/name → No configured channel target for this channel. - Enabled / Setup: Enabled is Yes because this coverage check includes enabled hotel rooms only. Setup is the stored channel setup flag. State remains Intent unknown. - Coverage boundary: generated separately for each configured channel lacking a represented room mapping. Disabled hotel rooms do not receive these gap rows. A represented mapping suppresses the gap row even if that mapping is disabled or not set up. Hotel rate coverage - Product → target: hotel rate ID/name → No configured channel target for this channel. - Enabled / Setup: Enabled is Unknown; the report does not establish that flag for these rows. Setup is the stored channel setup flag. State remains Intent unknown. - Coverage boundary: checks both a room-level hotel-rate selection and explicit rate mappings. Derived or room-level behavior may still explain an apparent gap. Existence of a disabled/not-set-up mapping still counts as represented for this coverage check. CRS room - Product → target: CRS room ID → current hotel room ID/name, or No current hotel room. - Enabled / Setup: Enabled is the CRS room's own enabled flag. Setup is Not established. - Coverage boundary: appears under ChannelRUSH Booking Engine when that property's CRS room configuration exists and the channel filters include it. Does not establish overall booking-engine readiness or the hotel's room enablement. CRS rate - Product → target: CRS rate ID/name → current hotel rate ID/name, or No current hotel rate. - Enabled / Setup: Enabled is the CRS rate's own enabled flag. Setup is Not established. - Independent pricing: a Missing target can reflect valid independent pricing. The report cannot decide whether a hotel-rate target was intended. It is not a test of rate saleability. How channel-flow enablement works: for Room mapping and Rate mapping, an enabled supported inbound inventory/monitoring flow or an enabled supported outbound inventory flow can make the flow enabled. The channel-level and property-setting switches matter. Room/rate send switches apply only to the outbound side, so turning off a send switch does not necessarily make Enabled = No while inbound remains enabled. Rate mapping does not repeat the target hotel-room enabled check used by Room mapping. Use Channel Health for separate flow evidence rather than inferring direction from a single Yes. Coverage is per channel, not “missing everywhere.” For example, a hotel rate may be mapped on one channel but have an Intent unknown coverage row on another. Conversely, no gap row does not prove that a represented mapping is enabled, correctly targeted, or operational. States and which finding takes precedence State Meaning Diagnostic next step Disabled An applicable flow or product enabled check is false. Confirm whether that is intentional; still inspect the target and evidence for additional gaps. Missing target The mapping/CRS product has no matching current hotel target in this property. Confirm the intended target. For CRS rates, check whether independent pricing is intentional before calling it a fault. Missing virtual parent A Room mapping references a virtual parent not found in the same channel settings. Ask the mapping owner to verify the parent relationship. Do not delete/recreate the room to test it. Not set up At least one applicable stored channel/room/rate setup flag is false. Review the relevant settings with an authorized person; this is not a fresh provider test. Unknown Channel-flow enablement cannot be established after the earlier checks. Preserve the uncertainty and provide support with the row details. Do not read it as disabled or successful. Mapped A target is present and no earlier state check for that row takes precedence. Verify that the target is intended. It does not validate all related rows, remote IDs, or inventory delivery. Intent unknown A hotel-product coverage row has no represented mapping for this channel. Confirm exclusions, derived rates, or room-level selection before requesting changes. The first applicable check wins: - Room mapping: Disabled → Missing target → Missing virtual parent → Not set up → Unknown → Mapped. - Rate mapping: Disabled → Missing target → Not set up → Unknown → Mapped. - CRS room / CRS rate: Disabled → Missing target → Mapped. - Hotel room coverage / Hotel rate coverage: always Intent unknown, even when Setup is No. For example, a disabled mapping with no target is classified Disabled, so filtering only to Missing target will miss it. Use All states when checking a product's complete configuration context. Field reference: every CSV column The CSV uses the same fixed 25-column schema as the related distribution report, but Mapping Coverage does not populate request-processing evidence. Blank means absent/not established here—not zero, No, or a successful outcome. Export scope and extraction fields Exact CSV header Mapping Coverage meaning Contract Schema identifier, currently captured-distribution-evidence-v1 . Helps identify the evidence format; not a health verdict. PropertyId ID of the single property whose configuration was read. Repeated on each row. View Mapping Coverage . Distinguishes this export from Channel Health even though the headers are shared. ExtractedUTC Extraction timestamp in ISO-8601 format with fractional seconds and UTC offset, for example 2026-10-20T11:17:57.6497090+00:00 . It dates the read, not the last mapping change. ChannelFilter Main Channel filter: 0 means all property channels at that filter layer; otherwise a channel ID. Does not record the result dropdown's additional channel list. Days Shared report parameter, normally 30 . It does not impose a 30-day mapping-history window ; Mapping Coverage reads current configuration and has no days control. StateFilter Selected State text; blank means All states. Different from each row's State . FlowFilter Selected Product kind , despite the header's name. Blank means All. For example, Room mapping . Channel, product, and finding fields Exact CSV header Mapping Coverage meaning ChannelId Channel ID for this result row. In the empty-result placeholder only, 0 is not a real channel finding. ChannelName Channel section name repeated on each row. Unknown channel means a name was not available, not that the channel is healthy or absent. Kind Product kind: Room mapping, Rate mapping, Hotel room coverage, Hotel rate coverage, CRS room, or CRS rate. State Row classification described above. No matching rows is the empty-result placeholder, not a normal mapping state. Enabled True or False for an established boolean; blank when not established. These correspond to Yes, No, and Unknown on screen. Interpret by product kind. Setup True or False for stored setup evidence; blank corresponds to Not established. CRS rows leave it blank because remote setup is not applicable. Product Same product identifier/context as the on-screen Product column. Target Same value as Current target on screen, including explicit missing-target messages. Evidence Same explanatory text as Evidence / limitation on screen. This is the final CSV column, after the processing fields below. Shared processing fields: blank in Mapping Coverage Exact CSV header What its blank value means here Pending No pending-request count is supplied by this mapping report; not zero pending work. Processing No processing-request count is supplied; not zero processing work. UnresolvedFailures No failure count is supplied; not proof that no requests failed. OldestPendingUTC No oldest-pending timestamp is supplied. QueueAgeHours No queue age is supplied. It is not mapping age or delivery latency. KnownRetries No retry count is supplied; not zero retries. LatestOutcome No request outcome is supplied; blank does not mean success. LatestEvidenceUTC No processing-evidence timestamp is supplied. Use ExtractedUTC for this export's read time, not for provider freshness. Text containing commas, quotes, or line breaks is CSV-quoted. Some text beginning like a spreadsheet formula receives a protective leading apostrophe; do not treat that prefix as a changed mapping ID. Preserve blanks when importing or comparing the file. Related - Channel Settings Page - OTA - Channel Health
Check channel queues and processing failures
Use Channel Health to identify queued work and retained failures for one property, then choose the appropriate investigation screen. Before you start You need access to the property in ChannelRUSH. This report reads stored configuration and processing evidence. It does not contact a channel to check its current rates or availability, resend requests, or change settings. Run the report 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Channel Health. 3. Choose a Channel, or leave All property channels selected. 4. Set Terminal request history (days) to a value from 1 to 90. The default is 30. This includes completed or failed requests created within that period. Current pending and processing work can be older than the selected period. 5. Choose a State, or leave All states selected. 6. Choose a Flow, or leave All selected. The flows distinguish outbound inventory, inbound PMS inventory, inbound PMS monitoring and reservation delivery. 7. Click View report. Channel Health filters showing channel, terminal history, state, flow and View report. To change the report, expand Filters, adjust your selections and click Update report. Running it again reads current evidence; it does not retry any work. Check the result Confirm the property name and extraction timestamp above the table. Each row describes a channel and flow, not an individual request. Channels can appear from stored settings or retained request history, including channels not offered in the main Channel selector. The totals above the table cover the full filtered result. The web table shows at most 100 rows per page; channel-heading subtotals describe the rows on that page. CSV exports the full filtered selection, not only the visible page. Each load or export reads again, so processing activity can change the values between them. Read the evidence Column or state What it tells you Pending / Processing Work currently waiting or being processed. Unresolved failures Retained failed requests that still meet this report's unresolved-failure rules. Oldest in queue (h) Age of the oldest pending or processing request, in hours. This is queue age, not delivery latency or a promised completion time. Known retries Recorded extra attempts for included outbound inventory requests. An unavailable value is not zero. Latest outcome / Last seen The latest retained request state and its edit time; monitoring instead uses a recorded heartbeat. Read the displayed time-zone offset. Enabled / Setup Stored configuration flags, not proof that the remote channel is synchronized. Idle or Idle / no retained activity No current failure or queue takes precedence, and the applicable retained evidence is successful/reviewed or absent. A quiet connection is not automatically failing. Monitoring evidence A heartbeat was recorded. This does not establish current inventory freshness or a monitoring SLA. Unknown / — Evidence is unavailable or not established. Do not read it as success or zero. A Failed requests state takes precedence over pending work and disabled settings. Read the counts and configuration columns together rather than relying on State alone. Investigate without resending Use the links beneath the report: - Inventory Settings / Channel Settings opens the settings report. - Inventory processing detail opens the inventory processing summary. - Reservation delivery detail opens Reservation Delivery Failures. These links preserve the property, not this report's channel, state, flow or history filters. Check the destination's scope before comparing counts. Reservation Delivery Failures initially uses its own 1-day lookback. Opening a detail screen does not itself resend a request. An unrelated successful request does not clear an earlier failure. For channel reservation delivery, a later success must match the same reservation version and destination channel. Do not resend solely to remove a historical failure from this report. Common problems - No matching rows: Your filters may exclude the available evidence. Return to All property channels, All states and All, then run again. No matching rows is not proof of successful delivery or complete telemetry. - Disabled with pending work: Work remains queued while the flow is disabled. Inspect the settings and processing detail; contact support before changing enablement or resending. - Unsupported, Not set up or Unknown: Review the flow and stored setup before treating this as a delivery failure. If the expected setup and evidence disagree, contact support. - “Select 1–90 days of terminal request history.”: Correct the history value and run again. If the evidence still does not explain the problem, send support the property, channel, flow, filters, extraction time with its offset and relevant error text. Do not include passwords or payment details. Related - Track and recover reservation delivery failures - Review channel mapping coverage
Investigate stored inventory differences
Use Internal Rate Consistency and Inventory Discrepancies to compare requested channel values with stored report values and identify what needs investigation. Before you start You need access to the selected property and a configured channel that supports outbound inventory. These are read-only inventory reports. Running them does not send updates, retry requests or check the channel's live extranet. Stored report values can come from outgoing updates; agreement does not prove what travelers see online. Run the report 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Internal Rate Consistency for rates, or Inventory Discrepancies for rates, availability and restrictions. 3. Choose one Channel. 4. Set Inventory dates to an inclusive range of 1–31 days. Leaving both dates blank uses today through six days ahead in the property's time zone. 5. Leave Room mapping ID (0 = all) and Rate mapping ID (0 = all) at 0, unless you know the channel mapping IDs to investigate. IDs appear in report rows and Mapping Coverage; they are not the channel's external room codes. 6. Leave State at All states for the first run. 7. Choose a Field, or leave All fields selected. 8. Click View report. To change a completed report, expand Filters, adjust the selection and click Update report. The two view tabs retain the loaded filters. Inventory Discrepancies does not automatically hide consistent rows: select Different values or Pending difference to narrow the results. Inventory Discrepancies filters with Booking.com, Allocation and Update report Example: Inventory Discrepancies filtered to Allocation. Update report applies changes after the first run. Check the result Confirm the channel, inventory dates and filtered field-row count above the table. Each row represents one field for one product and date—not one update request. Product names include mapping IDs; enabled/setup labels describe current configuration. - Requested image: stored channel-specific values, including adjustments such as markup, rounding and occupancy rates. - Report image: stored distribution values, which may come from sent updates rather than an independent channel check. - Raw master context: internal rate information for reference, not proof of the original input used for that request. - —: unavailable evidence, not zero or unrestricted selling. Stored report values currently have no currency label, so monetary rate differences cannot be calculated. Availability and restriction comparisons remain available. Understand the state State Meaning and next step Consistent Comparable stored values agree within the applicable tolerance. This is not live channel confirmation. Different values Comparable stored values differ, with no matching pending work recorded. Investigate before changing inventory. Pending difference Values differ and matching product/day work is pending or processing. The count does not prove that this particular field is queued. Unknown A requested or report value is missing. Check scope and mapping coverage rather than treating the blank as zero. Currency not comparable Rate currency evidence is missing or incompatible. Visible amounts alone cannot establish parity. Unsupported The connector does not declare support for this field at that product level. Not applied The field is supported by the connector but not applied under the current property/product configuration. Pending / stored timing repeats product/day request counts across fields. Do not add them together as unique updates. Report image predates requested image compares stored edit times only; it does not establish a failed or overdue update. Extracted is the report run time with its displayed offset. Stored edit timestamps are shown as recorded, not converted into a guaranteed user-local time. Neither identifies the latest independent channel check. Export or continue investigating Use the page controls to move through results; each page shows up to 100 rows. CSV reloads and exports the full filtered table within the report's limits, so it may differ from an earlier screen. An empty export contains a No matching rows record. Use Mapping Coverage to investigate mappings, or Channel Health to inspect queued work and retained failures. Do not resend solely because this report shows a difference. Common problems - No rows match: clear State/Field filters and check mapping IDs and dates. Rates-only views cannot show Allocation or restriction fields. The shared Restriction recorded states belong to Restriction Coverage, not these views. An empty result does not prove healthy distribution. - Date or size error: use ordered dates within 2000–2100 and shorten the range or select fewer mappings. The report allows at most 500 products, 3,100 product-days and 100,000 filtered field rows. If a small valid selection still fails, send support the error text. - Channel unavailable or configuration missing: check the property and its channel setup. A channel appearing in the dropdown does not guarantee outbound-inventory support. Ask your administrator or support if the intended channel remains unavailable. For unexplained findings, send support the property, channel, mapping IDs, inventory dates, filters, extraction time/offset and error text. Do not include passwords, payment details or guest information.
Review recorded restrictions with Restriction Coverage
Use Restriction Coverage to review recorded stay limits, closures and cutoff values for one property's channel, then identify missing or inapplicable fields that need investigation. Before you start You need access to the selected property and a configured channel that supports outbound inventory. You do not need permission to edit restrictions to read this report. This is a read-only report. Running it or downloading CSV does not send inventory, retry an update or check the channel's live extranet. It shows stored values, not proof that a room is bookable or that a channel accepted a restriction. It does not measure a restriction's effect on bookings or revenue. Run the report 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Restriction Coverage. 3. Choose one Channel. 4. Set Inventory dates to an inclusive range of 1–31 days, or leave both dates blank for today through six days ahead in the property's time zone. Month fills a whole calendar month. 5. Leave Room mapping ID (0 = all) and Rate mapping ID (0 = all) at 0 for all mappings. Enter a channel mapping ID only when you know which product to investigate. 6. Leave State at All states for your first run. 7. Choose a restriction Field, or leave All fields selected. 8. Click View report. To change a completed report, expand Filters, change the fields and click Update report. Changing a filter alone does not reload the results. The shared dropdowns also contain options for other inventory reports. In Restriction Coverage, choose one of the eight restriction fields listed below. Sell rate, Net rate and Allocation produce no rows here. Likewise, Consistent, Different values, Pending difference and Currency not comparable are not states produced by this report. Check the result Confirm the property, channel and inventory date range above the results. The filtered field rows count covers the complete selection, not only the current page. Each row represents one field, for one product, on one date. Read Date / product before interpreting a value. Property-level, room-level and rate-plan-level rows are separate. Room and rate mapping IDs identify channel mappings; they are not the channel's external room codes or the property's standard room/rate IDs. The report does not combine levels into one effective booking restriction or fill a missing rate-plan value from its room or property. Enabled / Disabled and Set up / Not set up describe current configuration. Disabled or incomplete products can still appear. These labels are separate from the field's evidence state. Understand the state The state describes the explicit Requested image field, after checking support and applicability. It does not compare Requested image with Report image to determine whether the channel applied the value. State Meaning What to do Restriction recorded A supported, applicable requested field has a recorded value other than false or zero. Read the value and product/date. This is not channel acceptance or a guarantee that the restriction is effective online. No restriction recorded The explicit requested field is false or zero. It is not missing. Interpret it for this field only. Other fields, product levels or channel rules may still restrict selling. Unknown The field is supported and applicable, but its requested value is missing. Check the selected mapping and recorded inventory. Do not interpret the blank as zero or unrestricted selling. Unsupported The connector does not declare update or report support for this field at this product level. Check whether the restriction belongs at another product level. Do not assume the channel itself has no such rule. Not applied The connector supports the field, but it is not applicable under the current property/product settings. Review the relevant setup with your administrator or support before changing settings. A missing Report image does not prevent Restriction recorded. A row marked Unsupported or Not applied is classified that way even if stored values are present. Read the value and timing columns Column How to interpret it Requested image Retained channel-specific requested values, including applicable channel adjustments. These are not recalculated from today's settings when you run the report. Report image Stored distribution values. They may come from outgoing sent updates rather than an independent channel check. Agreement with Requested image does not prove what travelers see online. Raw master context A shared column for internal rate context. Restriction rows do not supply a raw master restriction value here; it is not a fallback for a missing requested value. State / difference The restriction state described above. Restriction Coverage does not calculate numeric differences or tolerances between the two images. Pending / stored timing Matching pending/processing work for that product and date, plus a warning when the report image predates the requested image. Stored edit times appear beneath the image values. The same request count repeats across fields; do not add the rows together as unique updates. A pending count does not prove this particular field is queued. — means unavailable, not zero or false. Extracted is the report run time with its displayed offset, not the latest channel check. Stored edit timestamps show when records changed; they do not establish when each field was last verified. Report image predates requested image compares stored edit times only—it is not proof of a failed or overdue update. Filter reference Filter Accepted selection and effect Channel One property channel. The dropdown can include channels that do not support this outbound-inventory report; appearing in the list does not guarantee compatibility. Month Fills the inventory date range with a complete calendar month. Click View report or Update report to apply it. Inventory dates Inclusive start/end dates, ordered and within 2000–2100, spanning no more than 31 days. Blank start uses today in the property's time zone; blank end uses the resolved start plus six days. Room mapping ID (0 = all) A nonnegative channel room-mapping ID. Zero removes this filter. A specific room with rate ID zero includes that room and its rate-plan mappings. Rate mapping ID (0 = all) A nonnegative channel rate-mapping ID. Zero removes this filter. Room and rate filters apply together, so an incompatible pair has no matching mapping. State All states, or one of the five restriction states above. The comparison states from other reports return no rows here. Field All eight restriction fields, or one selected field. Rates and Allocation are excluded even though their options appear in the shared dropdown. Use the IDs displayed in results or Mapping Coverage rather than guessing mapping IDs. Restriction field reference These descriptions explain the recorded fields. They do not reconstruct the channel's full booking rules or confirm how an individual reservation would be evaluated. Field What the recorded value describes Example Min stay Minimum stay length for arrivals on the date, in nights. 3 records a three-night minimum. Max stay Maximum stay length for arrivals on the date, in nights. 14 records a fourteen-night maximum. Min through stay Minimum stay length for stays that include the date, in nights. 3 records a three-night through-stay minimum. Max through stay Maximum stay length for stays that include the date, in nights. 14 records a fourteen-night through-stay maximum. Closed to arrival Whether arrival on the date is closed. True records an arrival closure; False records no closure in this field. Closed to departure Whether departure on the date is closed. True records a departure closure; False records no closure in this field. Cutoff days Advance-booking cutoff in days before arrival. 2 records a two-day cutoff. Stop sell Whether selling is stopped for that product/date. True records stop sell; False records no stop sell in this field. For a supported, applicable field, an explicit zero or false gives No restriction recorded. A missing value gives Unknown. Neither establishes unrestricted availability across all rules and product levels. Export or continue investigating - Use Next page and Previous page to move through results. A page contains up to 100 field rows. Paging reloads the report; it is not a frozen snapshot. - Use Download → CSV for the full filtered table within the report limits, not only the visible page. The export reloads stored data and may differ from an earlier screen. An empty export contains a No matching rows record rather than a restriction result. - Use New window to open the loaded selection without the application's navigation. It does not apply unsent filter changes. - Use Mapping Coverage, Inventory Settings or Processing status / existing tools beneath a completed report for further investigation. These links retain the property, not this report's channel, dates or mapping filters; reselect the relevant scope on the destination screen. For a guided investigation of retained queues and failures, use Channel Health. For requested-versus-report comparisons, use Inventory Discrepancies. Do not resend inventory solely because a restriction is missing, pending, older or different in these stored records. Common problems - “No rows match these filters.” Clear State and Field to All states / All fields, check your mapping IDs and dates, then click Update report. Shared options for rate comparisons can produce an empty restriction report. An empty result does not establish complete or healthy distribution. Contact support if an expected product/field remains absent after checking scope. - “Select one property channel and valid mapping IDs (0 means all mappings).” Choose a channel and use zero or a valid nonnegative mapping ID. If the selected IDs are correct but the report rejects them, send support the error and selected scope. - “Select an ordered date range of 1–31 days, between 2000 and 2100.” Correct both dates or shorten the range, then run again. If a short valid range still fails, include the displayed date values in your support request. - Outbound connector, missing configuration or no matching mapping error. Check the selected property/channel and reset mapping IDs to zero. CRS and inbound PMS channels are not supported by this view. Ask your administrator or support to investigate missing setup; do not create or change mappings merely to obtain a report. - Selection exceeds report limits. Reduce the date range or select a specific mapping. The limits are 500 products, 3,100 product-days and 100,000 matching field rows; an oversized selection is rejected, not silently truncated. If the error identifies an undeclared rate-dimension data fault, narrowing filters will not repair it—contact support. - Unexpected Unknown, Not applied, pending work or older stored values. Review the state definitions and relevant configuration/processing evidence. Rerunning this read-only report is safe, but it does not repair inventory or retry delivery. If the explanation remains unclear, contact support before submitting another update. For support, include the property, channel, mapping IDs, inventory dates, selected filters, extraction time/offset and exact error text. Do not include passwords, payment details or guest information. Related - Check room and rate mapping coverage - Check channel queues and processing failures - Investigate stored inventory differences
Check inventory update status across properties
Use Update Status to find properties and channels with queued or unsuccessful inventory requests, then open the matching requests for investigation. Before you start This organization-wide report is for Org Admin users in distributor or PMS Connect partner organizations with portfolio access. Access to one property alone does not grant access to this report. If you cannot open it, ask your organization administrator or ChannelRUSH Support to confirm your access. The report covers active properties and organizations in your authorized portfolio that have a corresponding channel mapping. The property selected in the application's top bar provides navigation context; it does not restrict this report to that property. Refresh only reloads the report. It does not resend inventory, retry requests or check the channel's live rates and availability. Run the report 1. Confirm you are signed into the intended organization. 2. Open Org Admin → Updates - Status Report. The page heading is Update Status. You can also reach it through Org Admin → Reports → Update Status. 3. Choose a Status. The initial selection is Pending. 4. Choose a Channel, or leave Select ... for all channels within the report's scope. 5. Click Refresh. Update Status filters showing Failed, Booking.com and the Refresh button. The example shows where to select a status and channel. It does not demonstrate a failed request. After changing either filter, click Refresh again. Confirm that the dropdowns retain your selections and the heading above the results matches the selected status. The page does not refresh itself automatically. Check the result Each row groups requests for one property and one channel. The # column counts requests in the selected status, not rooms, stay dates or delivery attempts. Rows with the largest counts appear first. Groups with no matching requests do not appear. A table containing only its column headings means there are no matching groups in the report's current scope. It does not prove that every channel has the correct inventory or that an earlier failure was resolved. Understand the status and reporting period Status What it means What the count includes Pending Requests waiting to be processed. Current, unarchived requests, without a date-window filter. Processing Requests marked as being processed. Current, unarchived requests, without a date-window filter. Successful ChannelRUSH recorded successful request processing. Periodically refreshed summary counts for requests created since the reporting day's start 90 days ago, including archived requests. Unsuccessful Request processing did not succeed. Read the request's message to investigate. The same creation-based summary window, including archived requests. Failed Request processing failed. Read the request's message rather than assuming a particular cause. The same creation-based summary window, including archived requests. The completed-status window follows the system's reporting calendar, not the requested stay dates or your selected display time zone. It is not a rolling 90 × 24-hour period. There is no date-range control on this summary page. Completed-status counts are refreshed periodically and can lag behind request details. Successful is a processing status, not an independent check of the channel's current inventory. A pending or processing count alone does not establish that an update is overdue. Open the requests behind a count 1. Find the relevant property/channel row. 2. Click its Channel name to open Update Requests - Processing Status in a new tab. 3. Confirm Property, Channel and Status on the new screen. The linked selection loads when the screen opens. 4. If you change a filter, click Search to apply it. Use More Filters to reveal additional criteria when needed. 5. Inspect the matching request's affected dates, room/rate plan, requested values, attempts and status message. Note its transaction ID and Created / Last Run times before asking support to investigate. Displayed request timestamps use your signed-in user's time zone. The three row links do not open identical searches: Link Scope passed to the request screen Channel The row's organization, property, channel and selected status. Use this for the closest matching investigation. Hotel The row's organization, property and selected status. The channel restriction is dropped. Org The row's organization and selected status. Both the property and channel restrictions are dropped. The original summary stays open. Opening a link does not retry or archive anything. Why the detail count may differ The summary and request search are not two views of one frozen result: - Pending and Processing summary counts use current unarchived requests. Completed-status counts use a periodically refreshed, creation-based summary window that includes archived requests. - The linked request search does not inherit that summary date window and excludes archived requests by default. Older requests may no longer be available in this search. - Clicking Hotel or Org broadens the scope as described above. - The request screen normally shows 50 requests per page. Its Pending, Unsuccessful and Failed count indicators stop at 10,000+; those capped indicators are not the summary report's counts. - Requests can change status between opening the summary and opening the details. For older requests, More Filters → Archived includes archived requests as well as unarchived requests. Check the resulting rows and recheck this control before searching or paging again; do not assume it remains selected. If a summary count still has no corresponding detail, give support the organization, property, channel, selected status and the time you checked it. An empty detail search does not establish that the original failure was repaired. On the request screen, Date Range → Start/End Date refers to the dates the inventory update affects. Creation Timestamp and Processing Timestamp instead refer to request timestamps. They are not interchangeable. Leave date filters blank for the initial investigation rather than accidentally excluding the request. Keep investigation separate from retrying Use Search for investigation. The separate Select Action and Go controls can retry or archive requests; they are not another way to refresh the report. Do not retry solely because a count is nonzero or because a request is old. A retry can also requeue later overlapping requests for the same product. Archiving changes request visibility; it does not repair or successfully deliver an update. If the cause or intended scope is unclear, contact support before using those actions. Summary-page field reference Field or control Selection and effect Example Status One of the five statuses above. Required selection; initially Pending. Different statuses use the different counting windows described above. Choose Unsuccessful to investigate requests whose processing did not succeed. Channel One channel, or Select ... for no channel restriction. The list comes from channels configured for inventory sending within your portfolio. Choose Booking.com to exclude other channels from this summary. Refresh Applies Status and Channel and reloads the report. Does not initiate delivery. Change the channel, then click Refresh. # Count of matching requests for that property/channel group. A count of 12 means twelve requests, not twelve rooms or twelve failed attempts. Channel / Hotel / Org Identifies the group and opens a differently scoped request search in a new tab. Click Channel to retain both property and channel. This page has no property filter, date-range input, export button or pagination control. Use the linked request screen to investigate a specific property or request. Account Holder, if visible to ChannelRUSH staff, is not a customer control required for this workflow. Common problems - The report is unavailable or says organization administrator access is required. This report needs distributor/partner portfolio access, not only a property assignment. Ask your organization administrator or support to confirm the account's eligibility. Do not change another user's permissions to troubleshoot the report. - No rows appear. Check Status and Channel, then click Refresh. Confirm the organization and whether the expected property and channel mapping are active. If a known request remains absent, ask support to check its scope and status; do not interpret the empty table as proof of delivery. - Counts remain unchanged after Refresh. There may be no status change, or completed-status summaries may not yet reflect current details. Open the relevant request search and compare its message and Last Run time. Escalate unexplained differences instead of repeatedly retrying the update. - More requests appear after clicking Hotel or Org. Those links intentionally remove narrower filters. Return to the summary and click the Channel name, or select the intended property/channel on the request screen and click Search. If the scope still looks wrong, stop and contact support. - A Failed search shows a request labeled Unsuccessful. The request-row label can use Unsuccessful for a failed request. Keep the selected status and transaction ID with the request's message when escalating; the label alone is not a diagnosis or evidence of recovery. For support, include the organization, property, channel, selected status, affected inventory dates, transaction ID when available, the time/time zone you checked and the exact message. Do not include passwords, payment details or guest information. Related - Check channel queues and processing failures for one property - Investigate stored inventory differences
Investigate inventory update requests across properties
Find the inventory update requests behind a rate, availability or restriction change, understand their processing results, and decide whether to contact support, retry or archive them. Before you start - Open Org Admin → Updates. The heading is Update Requests - Processing Status. The Org Admin menu is available to organization administrators and users with access to multiple properties; available properties remain limited by your account access. - This page is for outbound inventory updates, not reservation delivery. Go To Report Status switches to inventory-report requests; it is not the result of sending an update. - Choose the Property inside Search Filters. The property selected in the application's top bar is not a substitute for this search filter. All searches your accessible scope, not only the top-bar property. - Searching does not resend inventory. Go runs the selected action. Retry and archive operations require at least one of the update permissions for rates, availability or restrictions. The public demo login can search, but cannot run these actions or submit a support request from this page. Find the requests 1. Open Org Admin → Updates. 2. Select the affected Property in Search Filters. 3. Select the destination Channel, if known. 4. Select Status, or leave All to avoid hiding a request whose status has changed. 5. Click Search. 6. Open More Filters if you need to narrow by product, source or dates. 7. Choose the additional filters described below. 8. Click Search again. Selecting a filter does not load new results by itself. Check the retained selections and the displayed requests after every search. Choosing a property and searching first also supplies that property's Room Type and Rate Plan choices. Primary search filters showing a demo property, Successful status and ChannelRUSH Booking Engine The search controls are stacked at narrower screen widths. These are the same filters as on the desktop layout. The initial page can show an empty table before a search. Clear Search Filter clears the search criteria; it does not clear saved requests. Use Search to load the scope you want. The « and » paging links move through results, normally 50 requests at a time, with the newest request IDs first. Find a known request ID 1. Select the correct Property. 2. Open More Filters. 3. Enter the request's numeric ID in Transaction ID. 4. Leave all three data-type switches—Rates, Availability and Restrictions—off, or turn all three on. 5. Click Search. This is the inventory request ID, not a reservation number. An exact-ID search still respects your accessible property scope, but bypasses most other filters, including status, channel, dates, source and the usual archived exclusion. A partial data-type selection can still hide it. The page may update Status and clear the dates after finding one request; do not interpret that as a change to the request itself. Read a request and check the result Each request shows its property, channel, room type and, when applicable, rate plan. The Updates column shows the affected inventory dates, selected weekdays and the values carried by the request. These dates are different from when the request was created or processed. A complete demo inventory request with allocation, Successful status, attempt count, request ID and timestamps This example is a stored allocation update. Its successful processing status is not a fresh comparison against inventory currently displayed by a channel. Look beneath the values for: - Status: the current processing result. Read any accompanying error or explanation, not only the colored marker. - Attempts: the processing attempt count. It is not a count of confirmed successful network deliveries. - Source and user: where the request originated. For example, the filter label UI Quick appears as UI - Quick in a result. A PMS-related source can show its channel name instead of an individual user. - Archived: when present, the request has been marked archived. This is separate from its processing status. - ID: the request's internal identifier, useful for Transaction ID searches and support. - Created: when the request was created. - Last Run: the request's recorded processing/edit time. Queuing a retry also changes this value, so a new Last Run time alone does not establish a completed send. The displayed timestamps use your user's time zone; retain the zone when reporting a problem. - Logs: opens the available attempt log in a new tab. Logs use UTC, unlike the localized timestamps on this list. Save Log File downloads the available log text; it does not resend the request. A missing or empty log is not proof of success or failure. Status meanings Status filter What it establishes All No status restriction. Use this when following a request through status changes. Pending Waiting for processing. It does not establish channel acceptance. Processing Processing is in progress. Investigate before starting a duplicate retry. Successful ChannelRUSH recorded successful processing. This is not a guarantee that every current channel value matches the intended inventory. Unsuccessful Processing did not succeed. Read the message and resolve the relevant issue before considering another attempt. Failed A failed processing result requiring investigation. It can include communication or other processing errors; the label alone does not identify the cause. Important: a request selected by the Failed filter can display Status: Unsuccessful in its row. Use the filter and message together; Unsuccessful and Failed are separate search statuses. For an update you are following, note its ID, search again with All or by Transaction ID, and inspect the latest status, message and logs. A request disappearing from an unsuccessful-only search can mean its status changed. An empty search does not establish delivery, and a processing result is not a substitute for checking the intended dates and values in the channel when that confirmation is required. Counts above the results Some searches show Pending, Unsuccessful and Failed panels. Each panel counts that status within the other applicable filters, excluding archived requests. These are not a total of all statuses or a count of the rows currently displayed. Counts above the reporting bound show 10,000+. The number followed by p is the corresponding page count; it can also be capped. Exact-ID searches can make these status panels misleading because the ID takes precedence over the status filter. Use the matched request itself in that case. These display caps do not limit the scope of an All action. Additional filters and field reference Expanded filters for organization, request ID, room, rate plan, source, dates and data types Property, channel and origin Field What it does and how to use it Property Limits results to one accessible property. All uses your accessible organization/property scope. Set this explicitly for a property-specific investigation. Status Matches one processing status, or All . See the status reference above. Channel Limits results to one destination channel. This is different from Source , which describes the origin of the update. Users Intended to select the user associated with a request. The selection is currently not retained by the normal Search/paging route. Do not rely on it to isolate work or define an action's scope; use property, channel, source and known request IDs instead. Organization Appears when multiple organizations are available. Changing it clears the Property selection. Reselect the intended property and click Search . Only use organizations you are authorized to access. Transaction ID Finds one internal inventory request ID, subject to accessible scope. Overrides most other filters; see the known-ID procedure above. Clear it before returning to an ordinary search. Room Type Limits results to the selected property's standard room type. Search with Property selected first if choices are missing. Rate Plan Limits results to the selected property's standard rate plan. This is not a text search for an OTA rate code. Source Matches the origin of the request. All leaves it unrestricted. Choose the workflow that generated the update rather than the destination channel. Source choices include PMS; UI Daily, UI Detail, UI Quick, UI Calendar and UI Bulk Import; Channel Refresh, Master Refresh and PMS Refresh; Reservation Adjustment; Office Hours; and Future Limit Loader. These choices identify the originating workflow, not a separate delivery-success state. Date Range Choose the meaning of the dates before entering them: - Start/End Date: filters the dates the inventory update affects. With both dates entered, requests whose inventory-date span overlaps your range can match, including requests that start earlier or finish later. Start alone means the request starts on or after that date; end alone means it ends on or before that date. Date-span matching does not independently test the request's selected weekdays. - Creation Timestamp: filters when the request was created, not the stay dates it updates. - Processing Timestamp: filters the recorded processing/edit timestamp used for Last Run. A retry can change it before a completed send. Leave both dates blank for no date restriction. Use the date controls' displayed local format. If you see The End Date cannot be before the Start Date., correct the range and search again; do not rely on results shown alongside that error. Timestamp searches have different end-date behavior from inventory-date searches. A multi-day timestamp range does not cover the whole final day. If you are looking for an event late on that date, widen the range beyond it and check the timestamps on the returned rows. A start-only timestamp search avoids an end-date cutoff; an end-only search ends at the entered date boundary. Entering the same start and end date uses a one-day window. For precise event identification, use the request ID and include the displayed time zone when contacting support. Archived and Include Data Types Switch Meaning Archived Includes archived and nonarchived requests. Off normally excludes archived requests; an exact Transaction ID search can still find them. This is a visibility filter, not an action. Rates Matches requests with recorded rate changes, including net/sell rates and additional rate parameters. Availability Matches recorded allocation or Stop Sell changes. Stop Sell belongs to this filter, not Restrictions. Restrictions Matches recorded arrival/departure closures, minimum/maximum nights, through-night restrictions or cutoff-day changes. With none or all three of Rates, Availability and Restrictions selected, there is no data-type restriction. Selecting one or two finds requests containing any selected type; it does not require every selected type. The whole matching request is shown, including its other values. Older requests without recorded change-type details can disappear under a partial selection. Check Archived again after searching or paging. In searches that calculate the status counts, the switch can return to off even when archived results were loaded. Do not use the displayed switch alone as proof of the loaded scope. If the selection and results disagree, avoid an All action; locate the known ID or contact support. Values within Updates The fields shown depend on what the request contains and what its channel supports: - Sell Rate / Net Rate: amounts and currency. An asterisk identifies the request's selected rate type. - Allocation: the available-room quantity carried by the request. - Stop Sell: whether the request closes or opens sales for its scope. - CTA / CTD: closed to arrival / closed to departure. - Cut Off Days: the advance-booking cutoff value. - Min Nights / Max Nights: the minimum/maximum stay values. - Min Nights Through / Max Nights Through: the through-stay restriction values. - Additional rate or channel parameters: channel-specific values, shown when present. A missing field is not automatically zero, No or a removal instruction. This screen displays stored request details; it is not an editor. VRT identifies a virtual room type. [BLANK / NOT SET] indicates missing product-name information and warrants checking the setup before deciding to retry. Send the evidence to support Use this when the message or delivery outcome is unclear. Sending evidence is separate from retrying inventory. 1. Find the affected requests with Search. 2. Tick the checkboxes beside the specific requests. 3. Choose Send to SLS in the action dropdown. 4. Click Go to open Send To Support. 5. Review the selected requests and Subject. 6. In Message, explain the symptom, expected result, affected dates and action time with its time zone. Include the request IDs and relevant error text. 7. Click Send when you intend to send the request to support, or Cancel to leave without sending. Opening the support form does not send it. Send submits your message with generated request details. Those details are not a complete raw payload or an automatic attachment of every attempt log; describe the issue in your own message. The confirmation records the support-send action, not that the inventory problem has been resolved. No receipt time or resolution time is promised here. Never include passwords, payment details or unnecessary guest data. Recheck your filters when returning from the support form: not every selection is preserved. If the send result is unclear, check with support before repeatedly sending the same request. Retry, archive and unarchive safely These actions change requests. Do not use them to refresh the screen, and do not assume a second confirmation dialog will appear after Go. The checkbox in the table heading selects only the requests on the current page. Retry, Archive and Unarchive use the individually selected requests. Retry All, Archive All and Unarchive All use the matching search scope, including records on other pages—not the checked rows and not only the displayed count. Before an All action, choose the final filters and click Search. Verify the scope, clear any unintended Transaction ID, and do not change filters between that search and Go. If a filter is not retained correctly, use specific request IDs or escalate instead. Retry Retry can also requeue later overlapping requests for the same property, channel and mapped products. Those additional requests need not share the selected status or source. Retrying is not a harmless replay of only the highlighted row; processing can use current settings. Ask support to confirm the intended scope if you are unsure. 1. Read the message and resolve the underlying issue, or obtain support's recommendation to retry. 2. Search again and check that the request is not already Processing and the intended inventory dates are still relevant. 3. Tick the specific requests you intend to retry. 4. Select Retry. 5. Click Go. 6. Search again using the known IDs or All status, and inspect the resulting status, message and logs. Retry All requires a specific Property, Channel and Status, even if a validation message suggests fewer filters. It can select matches beyond the current page and can expand to later overlapping requests as described above. Requests selected for retry become Pending, are unarchived, and have their prior message cleared. The attempt count is not reset. Past-only inventory requests may no longer be eligible. A success banner means the retry action was accepted, not that every selected request changed or that the channel accepted the inventory. Do not repeat Retry merely because delivery is not yet confirmed. Archive and unarchive Archive is not cancellation. It does not stop a pending send, prevent automatic retries, reverse inventory or delete the request. Automatic retry can unarchive a request again. Archiving is shared request state, not a private view preference. 1. Search for the requests and review their status and dates. 2. Tick the intended rows. 3. Select Archive or Unarchive. 4. Click Go. 5. Locate the known request IDs or search with Archived enabled, then check the archive indicator. Unarchive only removes the archive flag; it does not itself request a retry. Archive All and Unarchive All require one Property and one Channel. To include archived records in an ordinary search, enable Archived first, but heed the filter-retention warning above before any all-matching action. Neither action changes the processing status or proves a delivery problem has been fixed. Common problems - No requests appear: the initial screen may not have loaded a search, or status/product/source/date/archive/data-type filters may exclude the request. Click Search, broaden the relevant filters, or use a known Transaction ID with all data types included. If still missing, send support the property, channel, dates and action time; do not resend inventory solely because the list is empty. - A Failed result says Unsuccessful in its row: the row combines these labels. Keep the exact Failed filter and read the message. Contact support when the cause is unclear rather than assuming it is a configuration error you can fix by retrying. - Users or Archived does not stay selected: these controls have the limitations described above. Recheck the returned scope. Do not run an All action on a scope you cannot verify. - Retry All is refused: select a single Property, Channel and Status, then Search again. Archive All and Unarchive All need Property and Channel. Do not broaden scope to work around a validation message. - Go reports no action or no requests selected: choose the intended action and, for a selected-row action, tick the requests. If top and bottom action choices disagree, make them match before proceeding. - Some selected requests are excluded: your access does not cover those properties. Ask an authorized administrator to investigate; do not try another property context to bypass the restriction. - An action is unavailable or denied: check update permissions with your administrator. Public demo accounts are limited to searching here. - A request stays Pending/Processing, fails again, or returns after archiving: refresh the investigation with Search and inspect its message and logs. Archiving does not stop processing or automatic retry. Contact support with the ID and observed timestamps before repeated manual retries. Related - Check inventory update status across properties - Review inventory consistency across channels - Update rates, availability and restrictions with Quick Update
Send inventory update requests to support
Send selected inventory update requests with a clear description of the problem so support can investigate the affected property, channel and dates. Before you start - Select the affected property. This guide starts at Updates → Status, not the organization-wide Updates screen. - You need access to the property and at least one existing update request to include. Sending a support request does not require permission to change rates, availability or restrictions. - This workflow concerns outbound inventory updates, not reservation delivery. - The public demonstration login can search and view request details, but cannot use Go to open this workflow or submit a support message. Sending to support is not a retry. It does not resend inventory, change the selected requests' processing status, archive them, or correct the channel's rates and availability. Do not select Retry instead when your intention is to ask for help. Select the requests 1. Select the affected property in the property selector. 2. Open Updates → Status. 3. Choose the relevant Status, Channel, Room Type or Rate Plan filters. Leave Status at All if you are unsure of the current result. 4. Click Search. 5. Review the requests' channel, product, affected dates, values and status message. 6. Tick the checkbox beside each request you want support to investigate. 7. Choose Send To Support in the action dropdown. 8. Click Go. Search loads results; Go runs the selected action. Check the action dropdown before clicking Go. The checkbox in the table heading selects requests on the current page, not every matching request on other pages. Select related requests for the same issue rather than sending an unrelated batch. Opening Send To Support does not send the email. It shows Subject, Message, Send, Cancel, and an Update Requests section containing your selection. Review the selection and describe the problem 1. Check the property, channel, product and dates in Update Requests. If the selection is wrong or empty, use Cancel and select the correct requests again. 2. Enter a short Subject that identifies the issue, such as “Availability differs for the weekend.” 3. In Message, describe what you expected and what you observed. 4. Include the affected stay dates, room type/rate plan, the time you made the change and its time zone, and any relevant error text. 5. Mention any troubleshooting or retry you have already performed. 6. Click Send once when you intend to submit the message to support. Blank Send To Support form with Subject, Message, Send and Cancel controls The fields start blank. The selected requests appear in a separate section below the form. Both text fields are optional in the form, but a useful subject and explanation help support understand the issue. At least one selected request belonging to the current property is needed to send. Do not include passwords, API keys, payment details or unnecessary guest information. If you need to retain your unsent explanation while changing the selection, copy it before leaving the form; there is no Save Draft control. What is included automatically? The message includes generated summaries of the selected requests, with identifying information such as request ID, channel, organization/property, products, affected dates and selected weekdays. It also includes supported summary values, any recorded status message, and request timestamps. Your signed-in name, email address and property are included so support can identify the sender. The request list is not an exact preview of the outgoing email. The summary does not attach every attempt log or include every field shown on screen. Describe consequential values in your message, especially additional channel parameters or through-stay restrictions. There is no attachment uploader or recipient selector on this form; the support destination is determined by your organization's support arrangement. The requests are read again when you click Send. If processing continues while the form is open, the details sent can reflect a later state than the one you first viewed. Check the result After a normal submission, the application returns to Update Status and displays: The selected update requests have been sent to support along with your message. This is the application's send confirmation, not a delivery receipt or acknowledgement from a support agent. It does not confirm that the inventory problem is resolved or that a channel accepted an update. No ticket number or guaranteed response time is provided by this form. Check the selected property and search filters after returning. Not every filter is preserved through the support workflow. Set the scope you want and click Search again before interpreting the results or taking another action. If the page errors, the confirmation is unclear, or you need receipt confirmed, contact support through your usual support channel with the property, request IDs, subject and approximate send time. Do not repeatedly click Send or resubmit merely to obtain a clearer result: another submission can create another email. Read the selected-request reference The Update Requests section is read-only. It lets you verify that you are escalating the intended requests; it is not an inventory editor or a live comparison with the channel. Selected demo inventory request showing its channel, room, allocation, processing status and timestamps This demo request records a successful allocation update. Its status is the inventory request's processing result, not the result of sending a support email. Item What to check Channel / Room Type / Rate Plan The property and destination products affected by the request. A rate plan appears when applicable. VRT identifies a virtual room type. Updates The inventory dates, selected weekdays when shown, and values carried by the request. These are not the dates the support message was sent. Sell Rate / Net Rate Requested amounts and currency when present. An asterisk identifies the selected rate type. Allocation / Stop Sell The room quantity and sales-open/closed value carried by the request. CTA / CTD Closed to arrival / closed to departure values when present. Min Nights / Max Nights Minimum/maximum stay values when present. Min Nights Through / Max Nights Through Through-stay restriction values when present. Include them in Message if they are central to the issue. Cut Off Days The advance-booking cutoff value when present. Additional parameters Channel-specific rate or other values, when applicable. Explain the relevant parameter in your message rather than assuming it is included in the email summary. Status and message The stored inventory-processing result and any explanation. Read the message as well as the colored indicator. Successful is not a fresh check of the channel's current inventory. Attempts The processing-attempt count, not a count of confirmed successful deliveries. Source / user Where the update originated, such as UI - Quick , and user information when available. Archived When shown, the request has an archive flag. This is separate from processing status and does not mean the issue was resolved. ID The inventory request identifier to quote to support. It is not a reservation number. Created / Last Run Recorded creation and processing/edit times, displayed in your user time zone. Last Run alone does not establish a successful delivery. Include the zone when describing events. Logs Opens available attempt-log details in a new tab. Opening it does not resend inventory, and the log is not automatically attached to this support email. A missing value is not automatically zero, No, or an instruction to clear a restriction. [BLANK / NOT SET] indicates missing product-name information; explain it to support if it affects the investigation. Cancel without sending Click Cancel to leave the form without sending its message. If a discard warning appears after you have typed text, keep the form open if you still need that text, or confirm leaving when you intend to discard it. After returning, verify the property selector and filters before searching again. If they are not the intended scope, reselect the property, open Updates → Status, set the filters and click Search. Do not rely on the Status Updates breadcrumb to preserve the originating scope. Common problems - No requests selected. The selection is empty or no longer contains a request available for the current property. Return to Updates → Status, check the property, click Search, and select the intended requests again. If a known ID remains unavailable, give it to support rather than resending inventory to generate a new request. - A request you expected is missing. Check the property, status, product and date filters on Update Status. Broaden the relevant search and click Search. An empty result does not prove that an update was never saved or sent. - Go does not open the support form. Check that Send To Support is selected and at least one row is checked. If the page says Actions do not match, make the top and bottom action dropdowns agree. A demonstration-account warning means this action is unavailable for that login; do not attempt to work around the restriction. - The wrong property or filters appear on return. Reselect the property and rebuild the search before continuing. If the navigation problem persists, report the originating page and expected property to support. - Send reports an error or no clear result. Keep the request IDs, subject and send time. Check with support before submitting again because the email may already have been attempted. - The confirmation appears but the inventory issue remains. The form requests investigation; it does not repair inventory. Follow up with the original request IDs and current observations. Do not retry or archive requests as a substitute for confirming the correct recovery action. Related - Investigate inventory update requests across properties — the separate organization-wide workflow, for users with the relevant access. - Investigate stored inventory differences
Understand your inventory processing summary
Use Updates - Processing Summary to check one property's inventory queue, review recent processing outcomes and open the requests that need investigation. Before you start Sign in with access to the property you want to check. You do not need Org Admin access or permission to edit inventory merely to view this summary. This page concerns outbound rates, availability and restriction requests, not reservation delivery. Viewing the summary and following its links does not retry requests or change inventory. A Successful count is a recorded processing outcome, not an independent check of the channel's current selling values. An empty queue does not prove that every earlier update succeeded. Open the summary 1. Select the affected property in the property selector. 2. Open Updates → Status - Summary. 3. Confirm the heading is Updates - Processing Summary. 4. Review Pending and Processing at the top. 5. Review the Successful / Unsuccessful totals and the detail panels underneath them. The summary loads when you open the page. It has no date inputs, Search button or inventory-submit control. Reload the page to read it again. Reloading does not retry work or force the recent-outcome totals to refresh immediately. Read the current queue - Pending means requests waiting to be processed. - Processing means requests marked as being processed. - These counts cover current requests, including requests older than the recent-history periods below. - If either count is greater than zero, a channel table appears beneath the cards. Its columns are Channel, Pending and Processing. Click a channel's Pending or Processing count to open Update Status for that channel and state. Clicking the channel name opens its requests without selecting one status. The links open another tab, leaving the summary available. A request still marked Processing is not, by that label alone, proof of a healthy active connection or a failed one. Investigate the request before deciding whether to retry it. Read recent outcomes The six cards show Successful and Unsuccessful totals for 24h, 7d and 30d. The large card totals are not links. Use the detail tables below them to investigate a channel. Thirty-day outcome cards showing zero unsuccessful requests and 6,264 successful requests in the demo property. Example from a demo property. Counts change with the selected property and available history. What the periods mean - 24h / Past 24 Hours - Detail: requests created since the start of the hour containing the one-day lookback boundary. This is hour-rounded, not an exact second-by-second last 24 hours. - 7d / Last 7 Days - Detail: requests created from the system's calendar-day boundary seven days ago. - 30d / Last 30 Days - Detail: requests created from the system's calendar-day boundary thirty days ago. The calendar boundaries are system-side boundaries; do not assume they are midnight in your profile's time zone. The periods overlap: 7d includes 24h, and 30d includes 7d. Do not add them together. The periods group requests by when they were created, not by their affected stay dates or most recent processing time. Totals reflect recorded request outcomes and can change when a request's status changes. They are not a count of every processing attempt. Successful and Unsuccessful totals refresh separately from the current queue. They may lag the request list. No refresh countdown is shown on this page. Use the detail panels A populated panel has a Channel column followed by the Unsuccessful count on the left and Successful count on the right. Unsuccessful combines requests recorded as unsuccessful or failed; the total does not identify the cause. Last 30 Days detail panel with ChannelRUSH CRS and ChannelRUSH Booking Engine rows, each showing zero unsuccessful and 3,132 successful requests. - Click a channel name to open its requests from the linked creation-date start, across statuses. - Click a positive Unsuccessful count to open unsuccessful requests for that channel. - Click a Successful count to open successful requests. A displayed zero in this column can also be a link. - A zero Unsuccessful count is plain text, not a link. When available, user activity appears beneath a populated panel. The badge counts recent successful/unsuccessful requests attributed to that displayed user, not sign-ins, edits or clicks. Click the user's name, not the badge, to open their requests. That link does not restrict the result to completed outcomes or one channel. User activity is not a complete audit of every actor: some system, support or unavailable user records are omitted. Its total need not equal the channel totals. The channel totals also follow the property's current channel list; they do not establish complete history for channels removed from the property. Investigate a request and check the result The linked list is a starting point for investigation, not an exact reconciliation of the summary count. Summary and list date boundaries can differ. The summary includes archived requests, while the linked list excludes them by default. Requests can also change state between opening the two pages. 1. Click the relevant channel or count in the summary. 2. Confirm the new tab is Update Status for the same property. 3. Check Status and Channel. A channel-name or user-name link can show multiple statuses; an outcome-count link selects that outcome. 4. Open More Filters if the additional filters are hidden. When already applied, the control reads More Filters Active. 5. Check Date Range. For recent-history investigation, the summary links use Creation Timestamp. Check the actual start date rather than assuming the list reproduces the card's exact cutoff. Queue-count links do not supply a date range. 6. Select Archived if you also need archived requests. This includes archived and unarchived requests; it does not show only archived requests or archive anything. 7. Click Search after changing filters. 8. Review the resulting request's channel, room/rate plan, affected dates, values, Status, Attempts and any status message. Compare Created with Last Run: Created determines the summary's history period; Last Run describes processing time. Opening a summary link loads its initial results without another Search. Later filter changes require Search. The list is paged, so its visible rows are not necessarily the full matching set. Check the date again after changing filters or paging: those controls use date-only values and can change a time-specific starting boundary. If you need to find requests for particular inventory dates rather than their creation date, use Start/End Date under Date Range, enter the affected range and click Search. Those results answer a different question from the summary's history cards. A useful result is an identified request whose property, channel, products, dates and recorded outcome match the issue you are investigating. Successful establishes the recorded result for that request; it does not independently confirm the channel's current rates or availability. Unsuccessful needs investigation. No rows can mean the filters excluded the request, not that the issue is resolved. Do not use Retry, Archive, Un-Archive or the action Go control to refresh the summary. Those are separate workflows. If you need help investigating, follow Send inventory update requests to support. Do not resend inventory merely to make a total change. Field and control reference Field or control What it tells you or does Property selector Selects the property whose summary you are viewing. Check it before investigating another property's counts. Updates breadcrumb Returns to the property's Updates home. Pending card Total currently waiting requests across the property's included channels. Not a link. Processing card Total currently marked as processing. Not a link. Pending/Processing table Appears when current queue totals are positive. Channel names and status counts open filtered request lists. Successful cards Recorded successful request counts in overlapping creation-history periods. Not current channel inventory and not a count of attempts. Unsuccessful cards Recorded unsuccessful and failed request counts combined. Read the request details to establish the cause. Detail channel name Opens the channel's request list with the panel's linked creation-date start and no outcome restriction. Detail outcome count Opens the selected channel and outcome. Successful counts are links; unsuccessful counts are links only when positive. User activity name and badge Name links to that user's requests; the badge reports attributed completed-outcome requests. Neither is a complete user-activity audit. Empty detail message No updates are currently successful or unsuccessful. No completed-outcome rows are displayed for that period and included channel scope. Pending/Processing may still exist. Common problems The summary count and request list differ. Check the property, channel, status, creation-date start and Archived, then click Search. Allow for different summary refresh timing, date cutoffs and changes in request state. A user-name link also includes statuses not counted by its activity badge. If you cannot explain a consequential discrepancy, give support the period/card, clicked link, list filters and observation time with time zone. Do not retry or archive requests to reconcile the numbers. Pending or Processing remains visible. Reload the summary, open the corresponding channel/status count and inspect the request details. A count alone does not establish the cause or whether repeating the update is safe. If the affected inventory is still wrong or the request's state is unclear, contact support with the property, channel, affected dates, request ID and error text. Do not submit another inventory update as a diagnostic test. The page has zeros or an empty detail panel. Confirm the property and period. Check the current queue separately, then open Updates → Status if you need a wider or differently filtered investigation. Zero recent failures is not proof that a particular update succeeded or that current channel inventory is correct. Escalate if you expected a specific request and cannot locate it. An Unsuccessful total is present. Open its positive count, confirm the selected filters and inspect each relevant request's status message. The aggregate does not distinguish a validation issue, transport failure or another processing problem. Ask support when the error or safe next action is unclear. Archiving a request does not repair inventory or remove it from this summary's historical totals. You cannot find a property or open its summary. Check your selected organization and property access. Ask your organization administrator or support to confirm access to the intended property; do not switch to another property's data to diagnose the missing one. When escalating, include only the property, channel, request ID, affected dates, observation time/time zone and relevant error text. Do not include passwords, payment details or unnecessary guest information. Related - Check channel queues and processing failures - Send inventory update requests to support
Inspect an inventory update request log
Open the diagnostic log for an inventory update, read its recorded attempts, and download the available evidence for support without resending inventory. Before you start - You need to be signed in and have access to the affected property. - Start with an existing inventory update request. This guide concerns rates, availability and restrictions sent to channels, not reservation delivery. - Viewing a log and downloading it do not require permission to change inventory. A Logs link is available only for eligible requests; not every request has stored log entries. Opening Logs or saving its file does not retry the request, change inventory or resolve an error. Do not use Retry or Go to open a log. Find the request 1. Select the affected property in the property selector. 2. Open Updates → Status. 3. Choose the relevant Status, Channel, Room Type or Rate Plan filters. Leave Status at All if you are unsure of the current processing result. 4. Click Search. 5. Find the request with the expected channel, products, inventory dates and values. 6. Note its ID, Status, Attempts, Created and Last Run information. 7. Click Logs beside that request. If the request is not on the current results page, use » to see the next page and « to return, when those controls are available. You can also narrow the filters and click Search again. The log opens in a new tab, leaving Update Status available for comparison. You do not need to tick the request's checkbox. Search loads matching requests; Go runs the selected action and is not part of this viewing workflow. Find a known request ID 1. Open More Filters on Update Status. 2. Enter the request's ID in Transaction ID. 3. Clear any selected Rates, Availability and Restrictions checkboxes under Include Data Types to avoid excluding the request by its recorded data types. 4. Click Search. 5. Confirm the returned request's ID and property before opening Logs. Transaction ID is the inventory request identifier, not a reservation number. After date validation, an exact-ID search takes precedence over the ordinary channel, status, product, user, source, archive and date filters, but a partial data-type selection can still exclude it. The search remains within the selected property. If you see The End Date cannot be before the Start Date., clear both dates or correct their order, then click Search again. An invalid date order prevents the search even when you supply a Transaction ID. If you search without an ID, Archived includes archived requests alongside other matching requests. The date choice also matters: Start/End Date concerns the affected inventory dates, while Creation Timestamp and Processing Timestamp concern the request's recorded activity. These are different from the individual message timestamps inside the log. Check that you opened the correct log At the top of Update Request Log View, check: - The channel name. - The request ID. - The property name beneath it. If any of these is wrong, return to the Update Status tab and open the correct request. Do not alter identifiers in the address bar to try to reach another property or request. The viewer has no inventory editor, retry button or search form. Use the original Update Status tab when you need to search again. Close the log tab when you have finished. Read the recorded attempts When entries are available, the page displays text grouped under ATTEMPT #… headings. Each entry can contain a REQUEST or RESPONSE label, a timestamp, a URL and the recorded message. XML and JSON messages are formatted for reading; other messages appear as text. Read the message itself as well as its label. RESPONSE means an entry is presented as a response; it does not mean the channel accepted the update. A response can contain an error or warning. An attempt number is not a count of successful deliveries, and a visible request entry alone does not establish that a response was received. Log-message timestamps use UTC, including milliseconds and a UTC offset. Update Status's Created and Last Run values use your user time zone. Account for that difference when comparing events or telling support when something happened. Inventory dates inside a message describe the dates being updated, not necessarily the time the message was sent. Log field reference Item What it means and how to use it Channel The channel associated with the selected request. Check it against the request you were investigating. ID The inventory request ID. Quote it with the property and channel when asking support to investigate. Property The property whose log you opened. It appears beneath the channel and ID. ATTEMPT #… The stored attempt associated with the following entries. Multiple entries can belong to one attempt. A missing or unexpected number is a reason to ask support, not to assume success or trigger another send. REQUEST / RESPONSE The entry's diagnostic label. Use the accompanying message to understand what was recorded; the label is not a processing result. Timestamp The recorded message time, shown in UTC with milliseconds. It is separate from affected stay dates and the user-time-zone timestamps on Update Status. URL , when present The recorded endpoint for the entry. It is diagnostic context, not a link you need to open or replay. Review URLs for sensitive information before sharing them. Message The recorded XML, JSON or other text. Look for the relevant dates, products and any error or warning. Do not assume that every channel uses the same response format or success indicator. Save Log File Downloads the currently available entries for this property, channel and request as a text file. It does not send the file to support or resend inventory. Download the log 1. Confirm the property, channel and request ID in the log header. 2. Click Save Log File. 3. Open the downloaded text file and check that it contains the evidence you expected. 4. Review the entire file, including URLs, before sharing it through your approved support channel. When entries are available, the filename follows UpdateRequest-{ID}-Log.txt. When no entries are found, it follows UpdateRequest-{ID}-E.txt and contains no log entries. The E filename is not a verdict that the inventory update failed. The download reads the available log again. It is not a screenshot or an exact copy of the page's formatting; labels and spacing can differ. If entries become available between opening the page and downloading, the file can differ from the earlier view. Treat logs as potentially sensitive. Do not assume that every credential or personal detail has been removed. Never post logs publicly or send passwords, API keys, payment details or unnecessary guest information. If you are unsure how to share the evidence safely, provide the property, channel and request ID first and ask support for the appropriate next step. Check the result You have collected diagnostic evidence when the log header matches the intended request and you have reviewed the available entries or downloaded file. That is separate from resolving the update problem. Return to Updates → Status, verify the property and search criteria, and click Search again to check the stored processing result and any status message. Successful is the request's processing result, not a fresh check of the channel's current inventory. The log viewer itself does not provide a separate acceptance confirmation or verify current rates and availability. If the result or response is unclear, give support the property, channel, request ID, affected inventory dates, relevant product, error text and the action time with its time zone. Include any retry already performed. Ask for the correct recovery action before resending inventory. Common problems Logs is missing The link is not shown while a request is Pending or Processing, or before it has a processing attempt. Older request records can also lack this link. Search again to check the current result; do not retry merely to make Logs appear. If the request remains in an unexpected state or you need evidence that is unavailable, contact support with its ID, property and channel. A missing link does not establish that nothing was sent. Logs opens, but the body is blank The viewer can show the correct channel, ID and property with an empty body when no log entries are available. The presence of Logs on Update Status does not guarantee stored content. Check the identifiers, return to Update Status and click Search to review the request's result. If the evidence is still needed, contact support. Do not treat a blank log or empty download as proof of either success or failure, and do not generate a new update to obtain a log. The expected request is not in the search results Confirm the property and request ID. For a known ID, use Transaction ID, clear partial data-type filtering, and click Search. Without an ID, check the status, product, date and Archived filters. If the request is still unavailable, provide support with the known identifiers and approximate action time. An empty search does not prove that the original update was never saved or sent. The log time differs from Update Status The message log uses UTC; Update Status uses your user time zone. Compare the time zones before reporting an ordering or timing problem. If the events still do not line up, include both timestamps and their zones when escalating. A response contains an error, or the result is unclear Record the error text and relevant attempt and timestamp. Compare it with the request's status message. Do not assume that a response label, an HTTP success indication in the text, or a later attempt means the entire update was accepted. Ask support to interpret an unfamiliar channel response before choosing a recovery action. The download is empty or does not open as expected Check whether the filename ends in -E.txt and whether the viewer is also blank. An empty file supplies no diagnostic entries. If a file with expected content cannot be read, report its filename, property, channel, request ID and browser to support; do not modify inventory to troubleshoot a download. Related - Send inventory update requests to support — the separate workflow for submitting selected request summaries and an explanation. - Investigate inventory update requests across properties — the organization-wide workflow for users with the relevant access.
Compare rates and availability across properties
Compare stored rates, availability and restrictions for selected properties and sources, then inspect the results in a list, spreadsheet or CSV file. Before you start - Open Org Admin → Reports → Rates & Availability. The page heading is Org Admin - Rates & Availability Report. - You need access to the properties you want to compare. Org Admin navigation can also be available to users with multiple properties; the menu name does not mean that every property is accessible to you. - Check the Properties list rather than assuming the property in the top navigation is your only selection. Your account may offer properties across an authorized organization portfolio. - This report compares stored source data. A ChannelRUSH master value, a PMS value and a channel report value are different representations. Matching values, a green indicator or a recent-looking timestamp do not confirm channel acceptance or current retail bookability. Build a comparison 1. Open Org Admin → Reports → Rates & Availability. 2. Set Date Range to the stay dates you want to inspect. Both endpoints are included. You can use Month / Year to fill a whole month. 3. Select the required Days. Leave all seven selected for every date in the range. 4. Under Data To Display, select Rates, Availability, Restrictions, or a combination. 5. Under Properties, select only the properties you want. Use the group checkbox to select the whole group or clear a fully selected group, then choose individual properties. 6. Under Rate Plans, select the shared rate-plan codes you want to compare. Select Unmapped if you also need channel plans that have no mapped property rate plan. Clear all plans only when you want room-level rows without rate-plan rows. 7. Select sources under PMS and Channels. For example, select ChannelRUSH Master Image and a channel to compare the internal master with stored channel-report data. You need at least one source across the two groups; you do not need a selection in each. 8. Check the selection counts and summary at the bottom of the form. 9. Choose List, Excel or CSV. Date Range, weekday choices and Data To Display on the organization Rates and Availability form The date and data controls apply to the properties and sources selected below them. List and Excel open a separate tab or window. Excel opens a read-only spreadsheet; it is not an immediate Excel-file download. CSV downloads a file directly. When you select more than 10 properties, this form changes a List or Excel request into a CSV download instead. Checkbox selections are remembered in the same browser for your user and current property context. They can replace the initial defaults when you return. The date range is not remembered by that checkbox mechanism. Recheck the summary before each run. PMS and Channels selections with ChannelRUSH Master Image and Booking.com selected Sources are combined across the properties offered by the form. A checked source contributes data only for properties where that source is configured and applicable. Check the result 1. Confirm the expected property headings in List, or PropertyId and PropertyName in Excel/CSV. Use IDs when property names repeat. 2. Confirm the loaded dates, weekdays and sources. The result must match the submitted selection, not merely a newly checked box. 3. Check both room-level and rate-plan rows. They are not interchangeable. An unmapped channel plan can have channel-plan details without a property rate-plan ID. 4. Confirm that the expected data columns are present. Unchecked data groups are removed from the output, including exports. 5. Investigate missing or unexpected values using the guidance below. An empty report, blank value or available indicator does not establish that an update reached a channel. No currency column or automatic currency conversion is provided. Check that the property and source currencies are comparable before comparing amounts across properties. Change a loaded report List and Excel use a report toolbar without the main application navigation. - Change the dates, then click Load. Choosing a month changes the pending range; it does not load it by itself. - Open All Channels, Room Types, Rate Plans, Data or Days, change the choices, then click Apply — reloads report. A changed checkbox or count alone is not a loaded result. - Apply and Load submit all pending toolbar choices together, not only the dropdown or dates beside the button you clicked. - Use View → List / Excel / Grid to change presentation, or Download → CSV to download. If you have pending filters, the report asks Apply pending filters before continuing? Choose Apply and continue to carry them into the destination, or Cancel to dismiss that continuation. - New window opens another report window. It is not shown on an already opened new-window copy. - Return to the original organization form to change the property set. The result toolbar has no property chooser. For multiple properties, source, room and plan choices can be grouped by property. Repeated choices for the same source stay synchronized; they are not independent on/off switches for that source at each property. The originating form selects plans by shared code, while the result toolbar selects specific property rate plans. Optional Live Read If the result toolbar offers All Live Read, it requests data from the selected supported source rather than reading only the stored comparison data. It is a separate operation, not another name for the normal All Channels filter. Live Read is limited to one property, and that property must be the current property context from which you opened the report. Do not add Live Read to a multi-property comparison. To use it, start from the intended property context and select that property alone. In the result toolbar, select the supported source inside All Live Read, then click Apply — reloads report to initiate the request. A blank Live Read result does not prove that the source returned a successful, complete response. Read the List view Results are grouped by property, date and source, followed by rooms and indented rate plans. Virtual room types are labeled separately. Visible column or indicator Meaning Room/rate-plan labels Identify the product within its property, date and source section. These label columns do not have a separate named header. Sell Rate Appears when Rates is selected. Shows the source rate and, where available, extra occupancy/additional-rate parameters in the same cell. Allocation Appears when Availability is selected. Shows the source inventory count where available. Restrictions Appears when Restrictions is selected. Summarizes active restrictions and values, rather than displaying every restriction field separately. Colored dot Calculated availability: red indicates closed/no availability; yellow indicates restriction-limited availability; green indicates availability according to the report's calculation; gray indicates insufficient data. It is not an update-delivery status. There are no separate Timestamp, RoomsSold, Currency or Rate Params columns in List. Property, date and source appear as section headings, not flat columns. A blank Restrictions cell can mean default or false restrictions, unavailable values, or fields not applicable to that product. Minimum-stay values of 1 and cutoff values of 0 are normally omitted from the summary. Do not interpret a blank summary as confirmation that a channel has no restrictions. A missing sell rate can appear as a dash or a blank cell. Availability can also be blank. CRS room rows can display 0 for missing allocation, while their rate-plan allocation cells are intentionally blank. Exported rows therefore are not a cell-for-cell copy of the List view. Use Excel or CSV Excel displays a read-only spreadsheet. Its File → Save As menu saves a workbook. The report toolbar's CSV control is a separate, simpler export. Both exports honor the selected data groups. Identity fields, Date and Timestamp remain; deselecting Rates, Availability or Restrictions removes that group's fields. Neither output contains the List view's colored availability dots. Use Excel rather than CSV when you need occupancy/additional pricing in Rate Params or source-mapping identifiers. CSV does not include those fields. Excel column order With all three data groups selected, the spreadsheet has these columns, in order: 1. PropertyId 2. PropertyName 3. SourceFamily 4. ChannelId 5. ChannelName 6. RoomTypeId 7. RoomTypeName 8. RatePlanId 9. RatePlanName 10. SettingRoomTypeId 11. SettingRatePlanId 12. ChannelRatePlanId 13. ChannelRatePlanName 14. Date 15. SellRate 16. Rate Params 17. Allocation 18. RoomsSold 19. StopSell 20. MinNights 21. MinNightsThrough 22. MaxNights 23. MaxNightsThrough 24. CutOffDays 25. CTA 26. CTD 27. Timestamp CSV column order With all three data groups selected, the CSV has these columns, in order: 1. PropertyId 2. PropertyName 3. ChannelId 4. ChannelName 5. RoomTypeId 6. RoomTypeName 7. RatePlanId 8. RatePlanName 9. ChannelRatePlanId 10. ChannelRatePlanName 11. Date 12. SellRate 13. Allocation 14. StopSell 15. MinNights 16. MinNightsThrough 17. MaxNights 18. MaxNightsThrough 19. CutOffDays 20. CTA 21. CTD 22. RoomsSold 23. Timestamp CSV excludes SourceFamily, SettingRoomTypeId, SettingRatePlanId and Rate Params. It uses YYYY-MM-DD stay dates and numeric rates without locale-specific decimal formatting. Timestamps include a timezone offset when present. Text containing commas, quotes or line breaks is quoted; formula-like text may carry a protective apostrophe. Export field reference Field Meaning and limits PropertyId / PropertyName Property identifier and display name. Check these inside the file rather than relying only on its filename. SourceFamily — Excel only C means the ordinary stored-source representation, including master, PMS, CRS and stored channel reports. CLR identifies Live Read. CCI , if present in an internally supplied export, identifies a channel inventory image. These are source types, not success statuses. ChannelId / ChannelName Selected source identity. The source can be a PMS, the internal master, a booking engine or a channel. Additional source representations include a suffix such as Live Read. RoomTypeId / RoomTypeName Mapped property room identifier and name, not the external channel room identifier. Virtual products can share the mapped room identity. RatePlanId / RatePlanName Numeric property rate-plan identity and name. Unlike the organization form's plan codes, these identify a specific property plan. Blank on room-only rows and channel plans without a mapped property plan; inspect ChannelRatePlan fields to tell those cases apart. SettingRoomTypeId / SettingRatePlanId — Excel only Source-mapping/product identifiers. Useful for distinguishing products that share a mapped room or plan. Normally blank for master/PMS rows. They are not external channel IDs. ChannelRatePlanId / ChannelRatePlanName Channel/source plan identity, including channel plans with no property-plan mapping. Blank for room-only rows and master/PMS projections. Date Inventory/stay date, not a booking, request or delivery date. Excel uses the displayed date format; CSV uses YYYY-MM-DD . SellRate — Rates Source sell rate. Missing values export blank. There is no currency field. Rate Params — Rates, Excel only Occupancy/additional rates shown as amount and parameter key/type, separated by semicolons. CSV omits them. Allocation — Availability Inventory count. Stored plan rows can fall back to the room's allocation. Missing values export blank; a recorded zero remains zero. RoomsSold — Availability Sales count where the source supplies it. Master/PMS and Live Read leave it blank, and stored zero values can also become blank. A blank does not prove there were no sales. StopSell — Restrictions Y when the effective value is true; otherwise N , including missing values. Stored plan rows combine room and plan restrictions: a stop-sell on either closes the effective value. N is not proof of an explicit source confirmation that selling is open. MinNights — Restrictions Arrival minimum stay. Missing values can fall back to the room and then default to 1. A displayed 1 may be a default rather than a recorded source value. MinNightsThrough — Restrictions Through-stay minimum. The same fallback/default warning applies. MaxNights — Restrictions Maximum stay. Missing values and the value 99 export blank. Stored plan rows can use a room fallback. Blank does not prove the channel has no maximum. MaxNightsThrough — Restrictions Through-stay maximum, with the same blank/fallback rules. CutOffDays — Restrictions Advance-booking cutoff. Missing values can fall back to the room and then default to 0. A displayed 0 may be a default. CTA — Restrictions Closed To Arrival: Y if effective true, otherwise N , including missing values. For stored plan rows, either a room or plan closure can set it. CTD — Restrictions Closed To Departure, with the same representation and room/plan combination as CTA. Timestamp The exported inventory record's edit time, displayed in the signed-in user's timezone; CSV includes the offset. It is not a channel-acceptance or refresh-completion timestamp. Live Read leaves it blank. Missing stored-day placeholders can show a newly generated time, so a recent timestamp beside blank/default data does not prove a fresh channel report. For stored plan exports, numeric restrictions and allocation can fall back to room values, while boolean restrictions combine room and plan values. The plan timestamp does not necessarily date a room value used as a fallback. Use the source, product and actual values together rather than treating one field as a freshness certificate. Criteria field reference Control What to select Date Range Required start and end stay dates. The initial range starts on the current property's local today and ends 28 days later, inclusive. Month / Year Whole-month shortcut for Date Range. It does not generate a report by itself. Days At least one weekday. All seven are initially selected. Clicking the heading clears the selected days; clicking it again when none are selected selects all. Choose a weekday that actually falls within your range. Data To Display At least one of Rates, Availability or Restrictions. All three are initially selected. The heading clears the selections when any are selected, or selects all when none are selected. These choices affect display/export fields, not stored inventory. Properties At least one accessible property. All offered properties are initially selected, so reduce the scope before running a smaller comparison. A mixed group checkbox selects the whole group; a fully selected one clears it. Rate Plans Shared rate-plan codes from the offered properties. All offered codes and Unmapped are initially selected. With no plans selected, request room-level rows only. A source that only reports plan-level inventory may then have no export rows. The group can be absent if no plan codes are available. Unmapped Include configured channel plans without a mapped property plan. This is a report selection, not a mapping repair. PMS Stored received/monitored sources, any configured UI-override source, and ChannelRUSH Master Image. Normally not selected initially unless the same source is also an outgoing channel or remembered selections apply. Channels Configured outgoing sources across the offered properties. Initially selected. A source may not apply to every chosen property. List / Excel / CSV Run the selected comparison. List and Excel use a separate tab/window; above 10 properties the form downloads CSV instead. Refresh Data Request updated report data from eligible sources. This is separate from generating a view; see the next section before using it. Cancel Return to the organization Reports page. Does not undo an earlier refresh request or erase remembered checkbox selections. Refresh stored report data Refresh Data is not required to open the comparison. It explicitly requests new report data from eligible configured outgoing channels. It is not an instruction to resend your rates to them. On eligible accounts, opening this criteria page or downloading CSV can also trigger an automatic refresh check for the current property. Neither that check nor an explicit request guarantees that refreshed data is already present in the comparison. The request scope is broader than your displayed comparison: selected weekdays, data groups and rate plans do not limit the refresh requests. The refresh covers configured room products from today for roughly a year, extended if your selected end date is later. The selected report start date does not restrict that refresh start. You need at least one rates, availability or restrictions update permission for this action. Public demo logins cannot submit it. Some selected sources are not eligible for this kind of report refresh; selecting PMS or the master image does not guarantee a new external report request. If you need to request refreshed reports: 1. Recheck the selected Properties and Channels carefully, taking the broader refresh scope above into account. 2. Click Refresh Data once. 3. Read the confirmation or error message. A processing message is not confirmation that every source was eligible or that new data has arrived. Do not rely on its timing wording as a completion guarantee. 4. Recheck the form's selections after the page returns, then generate the comparison again when you need to inspect it. Compare the relevant values; a recent-looking Timestamp alone is insufficient. 5. If values remain unexplained, contact support with the property, source, room/rate plan, stay dates and the action time/timezone. Avoid repeated Refresh clicks while the first request's outcome is unclear. Common problems Symptom Likely cause and safe next action Run buttons are disabled Read the selection summary. Messages include Choose a date range. , Choose a valid date range. , Choose at least one weekday. , Choose at least one data type. , Choose at least one property. , and Choose at least one source. Correct the indicated choice. No rate plans is allowed. If valid selections still fail, send support the shown error and selected dates/scope. List or Excel downloads a CSV More than 10 properties were selected. Use the CSV, or reduce the selection to 10 or fewer for an on-screen view. No List/Excel window appears The report uses a new browser tab/window. Check for a blocked popup and allow this site if appropriate, or use CSV. If there is no blocking notice, recheck the form summary before retrying. Expected property or source is missing from the choices Access assignments or source configuration may exclude it. Check the current account/property context and ask your organization administrator or support to verify access/setup. A source listed elsewhere does not establish availability on this property. Empty output or missing room/plan rows Check dates, weekdays, selected properties, source applicability and plan choices. No selected plans intentionally excludes plan rows; unsupported or unconfigured products can also produce no rows. Restore a known applicable selection before escalating with the affected product details. Empty output is not proof of zero availability. Toolbar boxes changed but results did not Changes are pending. Click Apply — reloads report or Load , then check the loaded dates, headings and rows. If these still disagree, report the selections and resulting URL to support. CSV has fewer columns than expected Check Data To Display or the loaded report's Data choices. Unchecked groups are removed. Use Excel if you need Rate Params or mapping identifiers; CSV never includes them. Blank, N, 1 or 0 values look unexpectedly reassuring Some missing values are blank and others are normalized to defaults. Check the field reference and source/product context. Do not treat these values or a fresh-looking timestamp as channel acknowledgement. Live Read fails for a portfolio comparison Live Read supports only one property matching the starting property context. Return to that property and select it alone, or retain stored sources for the multi-property comparison. If a valid single-property request still fails, send support the source, dates and error. Refresh is refused or data still appears unchanged Check the required update permission and whether the source supports report refresh. Public demo accounts cannot submit it. A processing notice does not establish completion. Do not repeatedly request refresh; ask support to investigate using the property/source, dates, action time/timezone and message. Support does not need passwords, payment details or guest information for this comparison.
Choose filters for a rates and availability report
Choose a property's dates, products and data sources, then open a rates-and-availability report or download its results. Before you start - Select the property you want to inspect in the property selector. You need access to that property; viewing this report does not require Org Admin access. - Open Reports → Rates & Availability. The page heading is Rates & Availability Report. - Know what you want to compare: the PMS values stored in ChannelRUSH, manual PMS overrides, the ChannelRUSH master image, or a channel's stored report data. These are different sources, not interchangeable confirmations of what a guest can book. - This page selects report data; it is not an inventory editor. Live Read, where offered, requests data from the connected source when you open a report. Refresh Data is a separate request to refresh stored report data. Opening the criteria page can also initiate the application's automatic report-refresh check; it is not a guarantee that every displayed value has just been retrieved. A displayed value, matching values or a recent-looking timestamp does not by itself prove channel acceptance or current retail availability. Build your report 1. Choose dates and data 1. Set Date Range using the start and end date fields. Both endpoints are included. Use the date format shown in your account; after typing, leave the field and check the range in the summary beside the report buttons. 2. To select a whole month, use Month / Year. This replaces both range endpoints; it does not run the report. 3. Under Days, leave the weekdays you want to include selected. Keep at least one selected. For example, a Saturday-and-Sunday selection only includes weekend dates inside your range. 4. Under Data To Display, select Rates, Availability, Restrictions, or a combination. Keep at least one selected. These choices control the information displayed, not updates to those values. On an initial visit without remembered checkbox choices, the page starts with all weekdays and data types selected. The date range starts at the property's current date and ends 28 days later. Review the actual controls rather than relying on those defaults: the browser remembers checkbox choices separately for each user and property. 2. Choose room types and rate plans 1. Under Room Types, select at least one room type. 2. Under Rate Plans, select the plans you want to inspect. Leave every plan clear if you want only the room types' own rows. No rate plans selected does not mean all rate plans. 3. If Unmapped is offered, select it to include channel rate plans that do not have a standard property rate-plan mapping. It does not mean unmapped room types or disconnected channels. Room Types and Rate Plans with one room type selected and no rate plans This example selects one room type and no rate plans. The report shows the room type's own rows rather than its Standard or Package plan rows. The checkbox beside a room-type, rate-plan or source section heading controls the whole section. A dash means some items are selected. Clicking an incomplete section's heading selects all its items; clicking it when all are selected clears them. The count beside the heading shows the current selection. The Days and Data To Display headings work slightly differently: clicking either heading clears its choices if any are selected, and selects all when none are selected. 3. Choose the sources to compare Select at least one source across the available source sections. You do not have to select something in every section. - PMS: select a configured PMS/source, ChannelRUSH Master Image, or the separately listed UI Override source when available. - Channels: select the channels whose stored report data you want to inspect. - Live Read, if offered: select it only when you intend to request an on-demand read from that connected source. It is different from selecting the same source's stored PMS data. For a stored-data comparison, leave Live Read clear. To inspect only the master image, select ChannelRUSH Master Image under PMS and clear the other source choices, including Channels. To compare PMS and channel values, select the PMS entry and the relevant channels together. PMS and Channels source selections with only ChannelRUSH Master Image selected This example selects the stored ChannelRUSH master image only. Clearing Channels does not prevent a report when a PMS source remains selected. If the same connection appears in both PMS and Channels, selecting it in both places does not create two independent copies of that source. 4. Open or download the report 1. Check the summary beside the report buttons. Confirm the dates, matching-day count, products, sources and data choices. This is a summary of the pending selection, not evidence that report data has loaded. 2. Choose an output: - Grid: opens a calendar-style report in a new tab or window, with dates across the page. - List: opens a date-by-date report in a new tab or window. - Excel: opens the spreadsheet view in your browser in a new tab or window. It is not the direct CSV download. - CSV: downloads a file using the selected criteria. The selected data groups determine which data columns are included. 3. Leave the original criteria tab open if you expect to change the selection. Changing its filters does not update reports already open in other tabs; choose the output again to run the revised selection. Do not click Refresh Data to apply filters. The Grid, List, Excel and CSV controls run the report with your choices. Check the result In the report you opened, check: - The property name is the intended property. - The displayed dates and weekdays match your selection. - The expected source headings and room types are present. - Rate-plan rows are present only when you selected plans and applicable data exists. A room-only selection is intentional when every rate plan is clear. - The displayed data matches your choices. For example, an Availability-only List report shows allocation information rather than rate and restriction columns. The report's view/download controls let you continue in another format. If you change the filters within a result screen, use its Apply or Load control when offered and check the loaded result again; those controls are separate from this criteria page's run buttons. An empty result or blank cell does not establish successful distribution, zero availability or the absence of restrictions. A missing stored observation can also produce default-looking fields or a current-looking timestamp in an output. Do not use a timestamp alone as proof of a new provider response. If a comparison matters for a live booking issue, confirm the relevant channel and product separately before changing inventory. Field reference Dates, days and products Field What it changes Requirements and interactions Date Range The stay dates to inspect, including both endpoints. Both dates must be valid and the end must not precede the start. A date being selectable does not guarantee stored data exists for it. Month / Year Sets the range to the first and last day of a month. A shortcut for Date Range, not an additional filter or a report-run button. Days Limits the range to selected weekdays. At least one is required. A selected weekday may not occur in a short range, leaving no matching dates. Rates Includes supported rate information in the chosen output. At least one data type must remain selected. Availability and restrictions can be selected independently. Availability Includes availability/allocation information. A displayed allocation is not a guarantee that a guest can book the product. Restrictions Includes supported restriction information. The fields available depend on the source and product. A blank or default value is not independent proof that no restriction exists at the channel. Room Types Chooses the property's standard room types to inspect. At least one is required. Eligible configured virtual room products can appear under their selected parent room type. Rate Plans Chooses standard rate plans within the selected rooms. All clear means room-level rows only. The section may be absent when there are no choices. Unmapped Includes configured channel plans without a standard property rate-plan mapping. Appears only where relevant configuration is found. It is not a diagnostic result by itself. Sources Source What you are inspecting What it does not establish A named entry under PMS The source's stored inventory information in ChannelRUSH. That the PMS was queried when you opened the report. A source ending in UI Override Separately stored manual override information, when enabled for the property. That selecting or clearing this checkbox creates or removes an override. It only changes the report selection. ChannelRUSH Master Image under PMS ChannelRUSH's stored master inventory image. That every channel has accepted or currently sells those values. A named entry under Channels Stored report data for that channel; CRS and booking-engine sources use their own stored data. A universal independent readback from the channel. Some channel report values can be based on outgoing update data rather than a fresh provider response. Live Read , where available An on-demand inventory read for a supported monitored source when the report loads. Guaranteed successful retrieval or delivery. Missing results can reflect unavailable or unsuccessful retrieval. The source lists depend on the property's configured connections and their capabilities. Live Read is not available for every connection. UI Override appears only when that option is configured. These criteria lists have no search filter: their section controls apply to the entire list. Remembered selections Checkbox changes are remembered immediately in the current browser for your user and property. They can replace the initial choices when you return, even before you run a report. The date range is not saved with these checkbox preferences. This does not create a saved report or change inventory. Check every source and product selection before running, especially after changing properties, using another browser or clearing browser storage. To change the remembered choices, change the checkboxes themselves; there is no separate Save button on this page. When to use Refresh Data Use Refresh Data only when you intend to request a refresh of stored report data for supported selected channels—not to open a report or apply display filters. - You need at least one of the Update - Rates, Update - Availability or Update - Restrictions permissions. Seeing the button does not prove your account can use it. Demonstration logins cannot submit this action. - The action works on eligible selected Channels entries. A PMS-only, master-only or Live-Read-only selection is not a substitute for selecting a supported channel to refresh. - Refresh scope is broader than your report filters. It can include all eligible products for those channels and a broad future date range, even when your display selects one room, one rate plan, a few dates or particular weekdays. Data To Display does not narrow that refresh work. If a refresh is needed: 1. Recheck the selected property and Channels entries. Confirm that the broader refresh scope is intended. 2. Click Refresh Data once. 3. Read the confirmation or error on the criteria page. A processing message does not prove that eligible work was queued, that retrieval completed or that inventory is accepted by a channel. Unsupported selections can produce no useful refresh work. 4. Open the report again using Grid, List or Excel to inspect the relevant data. Do not treat a new-looking timestamp alone as completion evidence. There is no guaranteed completion time established by this page. If expected data remains missing or unchanged, contact support with the property, selected channels, stay dates and action time/time zone. Do not repeatedly click Refresh Data as a substitute for checking what happened. Common problems Symptom What to check Safe next action Report buttons are disabled. Read the selection message beside the buttons. Common messages include Choose at least one room type. , Choose at least one source. , and requests for a date range, weekday or data type. Complete that selection. No rate plans is valid; no room types or no sources is not. No report tab opens. Grid, List and Excel open another tab/window and require the page's JavaScript controls. Check for a browser pop-up block and allow the report window. If the page still does not respond, reload the criteria page, recheck the controls and report the visible error to support. No dates or rows appear. Check that your selected weekdays occur inside the range, that a source is selected, and that the required products are configured. Use a smaller known date range and the intended room/source. If data is still missing, provide the selection and visible error to support; do not infer that channel delivery succeeded. Rate-plan rows are missing. Check whether every Rate Plans checkbox is clear, or whether the plan lacks a relevant mapping/data for that source. Select the intended plan and run the report again. Use Mapping Coverage to investigate configuration; do not change mappings merely to fill a report. A checkbox choice reappears on your next visit. Browser preferences can restore earlier choices. Set the intended boxes explicitly and inspect the summary before running. A new selection does not change an already-open report. The original criteria page and result tabs are separate. Run the revised criteria again, then inspect the newly opened result. Live Read or UI Override is missing. Availability depends on configured connection capabilities and override settings. Use the available stored sources. Ask support to confirm expected configuration; do not enable or change settings solely to make the report option appear. Refresh is refused, or its message appears but the report remains unchanged. Check permissions, selected supported channels and whether new data was actually retrieved. Do not repeatedly refresh. Ask support to inspect the request with the property, channel, dates, action time/time zone and error text. Never send passwords, payment details or unnecessary guest information with a report question. Related - Check room and rate mapping coverage
Read rates and availability in List View
Use List View to inspect rates, allocation and restrictions by date, source, room type and rate plan, and distinguish missing data from a recorded value. Before you start - Select the property you want to inspect. You need access to that property; Org Admin access is not required for a single-property report. - Know which source you intend to read: stored PMS data, manual PMS overrides, the ChannelRUSH master image, a channel's stored report data, or CRS/booking-engine data. These are different representations of inventory. - This is a viewing report, not an inventory editor. There is no Save or Send action in List View. A displayed value or green indicator does not prove that a channel accepted an update or that a guest can book the product. - For a stored-data comparison, leave Live Read clear if that option is offered. Live Read requests data from a connected source when you load a report; see its scope below. Open a List report 1. Select the intended property in the application's property selector. 2. Open Reports → Rates & Availability. 3. Choose your Date Range, Days, Data To Display, Room Types, Rate Plans and sources. Both date endpoints are included. Select at least one room, source, weekday and data type. No selected rate plans is valid: it requests room-level rows only. 4. Under View, click List. 5. In the new tab or window, confirm Rates & Availability Report - List View, the property name, the date headings and the expected sources. For the criteria page's complete field reference, defaults and remembered selections, see Choose filters for a rates and availability report. Keep the original criteria tab open. List View has its own compact toolbar but no main application menu. Changing the original criteria page does not update an already-open report. List View property heading, output links, dates and display filters The List toolbar lets you change the displayed selection and switch outputs. On a narrower screen, its controls wrap onto additional rows. Read a date's results 1. Find the gray heading for the inventory date you want to inspect. This is a stay date, not the time the source last changed. 2. Find the source heading beneath that date. The same date contains separate sections for selected sources. 3. Find the room type, then read any indented rate plans underneath it. A channel's plan name can differ from the property's standard plan name. 4. Read Sell Rate, Allocation and Restrictions together. These columns appear only when their corresponding Data choices are selected. 5. Compare the same property, date and mapped product across sources. Do not treat similarly named products or amounts in different currencies as equivalent without checking their configuration. List View date, source, room and rate-plan rows with Sell Rate, Allocation and Restrictions This demo capture shows recorded CRS prices and room allocation alongside missing Booking.com values. The blank cells, dashes and gray indicators do not prove that Booking.com is sold out, unrestricted or successfully updated. What the colored indicators mean The small colored indicators beside rooms and plans summarize the data available to that source's calculation. They are not delivery statuses. - Red: the calculation marks the product closed or unavailable, for example because of nonpositive allocation or Stop Sell. - Yellow: price/allocation data is present and the calculation recognizes a restriction. - Green: price/allocation data is present without a blocking condition or recognized restriction in that calculation. This is not a retail-availability guarantee. - Gray: the calculation lacks sufficient rate or allocation evidence. This does not mean zero inventory. Read the room and plan together. A plan's indicator can use parent-room values or restrictions that are not repeated in the plan's own cells. A room indicator can also take account of plans hidden by your Rate Plans selection; it is not a worst-color summary of only the visible rows. A green room therefore does not mean every plan is open. The indicators remain visible when you hide the Availability column. Hiding Restrictions does not stop restrictions affecting the calculation. Conversely, not every printed restriction changes the indicator's color. Live Read uses a different calculation and needs a base rate and allocation; extra price lines alone do not establish a green result. Change the selection in List View List filters are staged. Checking a box or changing a date does not update the table until you apply the selection. Change sources, products, data or weekdays 1. Open the appropriate dropdown: All Channels, Room Types, Rate Plans, Data or Days. The channel label and count can change with the selection; inspect its checkboxes rather than relying on the word “All.” 2. Select or clear the choices you need. Select all selects every option when some are clear, or clears every option when all are selected. These dropdowns have no search box. 3. Click Apply — reloads report in a dropdown. Any Apply button applies all pending dropdown and date changes, not only that dropdown. 4. Check the reloaded date headings, source sections, room/plan rows and value columns. Closing a dropdown does not apply it. Clearing every Rate Plans choice deliberately removes plan rows; it does not select all plans. Clearing every room, source, weekday or data type is invalid. Change the date range 1. Enter the start and end dates using the displayed format, or choose them in the date picker. 2. Leave a typed date field and check that both endpoints show the intended dates. 3. If you want a whole month, use Month / Year instead. This fills the range; it does not load it. 4. Click Load. 5. Check the resulting date headings and products. Load applies all pending dropdown choices as well as the dates. The date range is inclusive, then Days narrows it to the selected weekdays. A short range can contain none of the selected weekdays and therefore produce no date rows. Load is not Refresh Data. With stored sources, it reloads the report using the stored data available to it. The original criteria page's Refresh Data action is separate and has different permissions and scope; use the linked filter guide before requesting a refresh. If Live Read remains selected, loading again can request another external read. Switch views or export - Grid: opens the calendar-style output with dates across the page. - Excel: opens the browser spreadsheet view; it is not the CSV download. - CSV: downloads a file for the selected criteria and Data groups. - New window: opens another List tab/window with the selection. It may be absent when you are already in a new-window view. Apply your filters first for a predictable result. If you click an output while changes are pending, the page asks Apply pending filters before continuing? Choose Apply and continue to use those pending choices, or Cancel to stay in List View. Cancel leaves the pending filter choices in place; it does not restore the previously loaded selection. Grid, List and Excel are different presentations. CSV is a separate projection, not a literal copy of every visible List cell or price line. Check the result A successful display change is visible in the reloaded result, not merely in a changed checkbox or count: - The property is correct. - The date headings match the inclusive range and selected weekdays. - Only the intended eligible sources and rooms are shown. - Plan rows match the selected plans, or are absent for a room-only selection. - The Sell Rate, Allocation and Restrictions columns match your Data selection. For example, clearing all rate plans and choosing only Availability, then clicking Load, produces room-level allocation rows without Sell Rate or Restrictions columns. It does not change inventory. If results are missing or look inconsistent, check the selected source and both product levels before taking action. This report has no per-source freshness timestamp. A footer time, where shown, is not the time the provider last supplied inventory. A recent timestamp in a CSV can also accompany a missing record; do not use it alone to confirm retrieval or delivery. Field reference Display controls Control What it selects Important interaction Month / Year A whole calendar month. Replaces the date endpoints; click Load to run it. Start date / End date Inventory dates, including both endpoints. End must not precede start. Selectable dates do not promise stored data or a particular retention window. All Channels / Channels Ordinary stored sources, including eligible PMS, master, override and outgoing-channel entries. This List dropdown combines sources that the criteria page presents in separate sections. Clearing this family does not clear a separately selected Live Read source. Live Read , when available Supported on-demand monitoring sources for the current property. Requires single-property scope and an eligible connection. It is not offered for every OTA or PMS. Room Types Standard property rooms. At least one is required. Configured virtual channel rooms follow their selected parent. Rate Plans Standard property plans and, where offered, Unmapped . All clear means room rows only. Unmapped includes configured channel plans without a standard plan mapping, not unmapped rooms. An empty catalog can show No eligible rate plans . Data → Rates Sell Rate and supported additional price lines. At least one Data choice must remain selected. Data → Availability Allocation. Does not hide the colored indicators or turn them into delivery statuses. Data → Restrictions The combined Restrictions column. Does not remove restrictions from the indicator calculation. Days Weekdays within the date range. At least one is required; it must occur in the range to produce date rows. Apply — reloads report / Load Runs all pending display choices. Does not save inventory. Retained Live Read can repeat an external request. An organization-level report can show separate property cards and grouped product choices. Use the property heading to distinguish them; List has no property selector of its own. The organization's entry workflow is covered in Compare rates and availability across properties. Result fields Field or display Meaning How to read missing or special values Property heading Property whose results follow. Check it even when room and channel names look familiar. Gray date heading Inventory/stay date. Not a processing or update timestamp. Source heading Representation being inspected. A normal channel heading does not establish a live provider read. Room type Property room associated with that source row. Missing rows can reflect selection or configuration, not zero stock. Virtual Room Type A configured virtual channel product associated with the room. It follows its selected real parent rather than having a separate room checkbox. Rate-plan name Plan beneath that room. Channel plan names may differ from the standard property plan name. Sell Rate Row's available base sell rate, displayed to two decimal places. Blank or - can mean unavailable/unreported data or a field not shown at that source level. A displayed 0.00 is different from a missing-value dash. List has no currency-code column; do not assume a common currency or tax basis. Additional price lines Supplied occupancy or extra-person/bed parameter prices, followed by their key/type. Available parameters vary by source. Do not assume the List exposes every price component or a complete retail quote. Struck-through price CRS/booking-engine plan's pre-promotion price when supplied, followed by its effective price. Not proof that every coupon or customer-specific promotion is included. Allocation Row's available-to-sell quantity where supplied/displayed. Blank is not zero. A plan can have a blank cell while its indicator uses a room's allocation. CRS room rows have a special missing-value fallback described below. Restrictions Supported restriction values recorded on that row. Blank does not confirm that the product is unrestricted. Parent restrictions can affect the indicator without appearing here. Restrictions The combined column lists applicable values separated by commas. Names follow your account language. Restriction Meaning When it appears in this column Stop Sell Closed for sale on the date. When true. Minimum nights Minimum stay for arrivals on this date. When greater than one. Minimum nights through Minimum stay when the stay includes this date. When greater than one. Maximum nights Maximum stay for arrivals on this date. When a value is present. Maximum nights through Maximum stay when the stay includes this date. When a value is present. Closed to arrival / CTA An arrival cannot start on this date. When true. Closed to departure / CTD A departure cannot fall on this date. When true. Cutoff days Advance-booking cutoff for the date. When greater than zero. False or unknown flags, missing values, minimums of one or less, and nonpositive cutoff values are omitted. Maximum values can still appear without changing the indicator to yellow. These are recorded-field explanations, not a guarantee that a provider currently enforces those rules. Source differences that matter Source What you are viewing Consequential differences Named PMS source Stored incoming inventory in ChannelRUSH. Opening List does not query that PMS unless you separately selected its Live Read option. Missing rate/allocation cells can be blank. ChannelRUSH Master Image Stored master inventory. Not proof every channel has accepted it. Room and plan cells show their own values, not a fully expanded inheritance calculation. Source ending in UI Override Separately stored manual override information. Selecting or clearing it changes the report, not the override. Ordinary outgoing channel Stored report image for the selected channel. Some integrations populate this from outgoing update data rather than an independent provider readback. Unsupported room-level fields can be blank; supported but missing rates may show - . ChannelRUSH CRS / ChannelRUSH Booking Engine Stored CRS/booking-engine inventory with applicable rate calculations/promotions. Room rows show allocation but no rate or restriction text. Plan rows show rates/restrictions but no allocation cell. A missing CRS room allocation displays 0 ; that zero alone does not establish a stored zero or a sold-out room. Live Read Data requested on demand from a supported monitored connection. Request failure or missing/incomplete data can produce empty or gray results. Neither proves a successful empty response. Room-level output is not necessarily a separate independent observation; inspect plan details where available. Live Read scope: the external read uses the property, source and full date range. Room, plan, Data and weekday choices narrow what is displayed, not the scope of that external request. Opening another output or reloading with Live Read still selected can request it again. Leave it clear when you only want to inspect stored data; do not repeatedly load it to diagnose an unexplained blank result. CSV field reference The CSV link uses the same selection but builds export rows separately. It can combine room allocation with plan prices, so a populated export field does not require an identically populated List cell. A room-only selection leaves plan identity fields blank. With all Data groups selected, the headers appear in this order: PropertyId, PropertyName, ChannelId, ChannelName, RoomTypeId, RoomTypeName, RatePlanId, RatePlanName, ChannelRatePlanId, ChannelRatePlanName, Date, SellRate, Allocation, StopSell, MinNights, MinNightsThrough, MaxNights, MaxNightsThrough, CutOffDays, CTA, CTD, RoomsSold, Timestamp. Header(s) Meaning and availability PropertyId , PropertyName Property identity. Always included. ChannelId , ChannelName Selected source identity. Always included; distinguish its representation before comparing values. RoomTypeId , RoomTypeName Room identity supplied by the export projection. Always included. Use the property/source context when matching records. RatePlanId , RatePlanName Standard property-plan identity where applicable. Always included, but can be blank. ChannelRatePlanId , ChannelRatePlanName Source-specific channel-plan identity where applicable. Always included, but can be blank. Date Inventory date in YYYY-MM-DD form. Always included. SellRate Base sell rate. Included when Rates is selected. Parameter-price lines are not separate CSV columns. Allocation Exported availability quantity. Included when Availability is selected. StopSell Stop Sell flag. Included when Restrictions is selected. MinNights , MinNightsThrough Minimum arrival/through-stay lengths. Included when Restrictions is selected. MaxNights , MaxNightsThrough Maximum arrival/through-stay lengths. Included when Restrictions is selected. A maximum value of 99 is rendered blank in this export. CutOffDays Advance-booking cutoff. Included when Restrictions is selected. CTA , CTD Closed-to-arrival/departure flags. Included when Restrictions is selected. RoomsSold Included when Availability is selected. Not populated for PMS/master/override rows or Live Read. Stored channel/CRS exports suppress zero; room-only rows show only positive values. A blank therefore does not distinguish zero from missing or unexported data. Timestamp Projected record's edit time in your user time zone, with an offset, where available. Always included; Live Read leaves it blank. It is not an acceptance or guaranteed provider-observation timestamp. Exported restrictions can also combine room and plan values. For combined rows, Stop Sell, CTA and CTD are Y if either level is true; missing numeric plan restrictions can fall back to room values. These fields need not match the plan's own List cells. Unticking a Data group removes that group's columns rather than leaving empty columns. The identity fields, Date and Timestamp remain. There is no CSV indicator-color column, currency-code column or parameter-price column. Export defaults are not independent source confirmations. Missing flags can become N, missing minimums 1, and missing cutoff 0. A missing stored record can also produce a current-looking Timestamp. Blank rate/allocation beside those defaults does not mean a provider explicitly returned an unrestricted, freshly observed product. Inspect the source and actual values before using the export for an operational decision. Common problems Symptom What to check Safe next action and when to escalate Filters changed but rows did not. List stages its controls. Closing a dropdown or changing Month / Year is not a reload. Click Apply or Load and check the result. If it still does not match, send support the property, filters and visible error. Choose a valid date range. Missing/invalid endpoints or end before start. Correct both dates, leave the field, then Load. A message asks you to choose at least one source, room type, data type or weekday. A required group is empty. Select an eligible choice and apply. Rate plans can remain empty. If an expected choice is unavailable, ask support to check configuration. Only room rows appear. All rate plans may be clear. Select the intended plans and apply. If still absent, check the expected mapping rather than changing it merely to fill the report. A channel, virtual room or plan is missing. Selection, setup, supported level and CRS enabled/mapping state affect which rows can appear. Recheck the correct property/source/product. Use Mapping Coverage or ask support if the configured product is still missing. No date rows appear. Selected weekdays may not occur in the range. Choose the intended dates/days and load again. Empty output is not proof of healthy distribution. A dash, blank cell or gray indicator appears. Missing data, an unsupported level, intentionally blank CRS cells or unsuccessful Live Read can look similar. Read the source reference and related room/plan rows. Escalate persistent unexplained gaps; do not treat them as zero or resend inventory blindly. An indicator seems inconsistent with the visible cells. Parent values, hidden plans and source-specific calculations can affect it. Inspect both levels and source. Do not change inventory solely to make the indicator green. CSV values or columns differ from the List. Export combines some room/plan values and normalizes missing fields; Data groups control its columns. Check the header and CSV reference. A difference alone does not establish a new inventory change. A report tab does not open. The criteria page's List action opens a new tab/window. Check the browser's popup block. If it still fails, retain the selection and visible error for support. For support, include the property, source, inventory dates, room/plan, action time and time zone, exact error text and a safely cropped screenshot. Do not send passwords, payment details or unnecessary guest information. Never use repeated Live Read, Refresh Data or inventory resends as a substitute for understanding a missing result. Related - Choose filters for a rates and availability report - Compare rates and availability across properties - Check room and rate mapping coverage
Read and export rates and availability in Excel View
Use Excel View to inspect rates, allocation and restrictions in a read-only spreadsheet, then download the workbook or a report CSV for further analysis. Before you start - Select the property you want to inspect. You need access to every property included in the report. Org Admin access is not required for a single-property report. - Decide which inventory source you need. PMS data, manual PMS overrides, the ChannelRUSH master image, stored channel report data and CRS/booking-engine data are different representations of inventory. - Excel View is not an inventory editor. Save As downloads a file; it does not save rates or send inventory to channels. - A displayed price, positive allocation, N restriction or recent timestamp is not proof that a guest can book, that a channel accepted an update, or that the value was read back from the channel. Open Excel View 1. Select the intended property in the application's property selector. 2. Open Reports → Rates & Availability. 3. Choose the Date Range, Days, Data To Display, Room Types, Rate Plans and sources you want to inspect. 4. Under View, click Excel. 5. In the new tab or window, confirm the heading Rates & Availability Report - Excel View, the property name and the date range above the spreadsheet. Both date endpoints are included. Select at least one room type, source, weekday and data group. Leaving all rate plans clear requests room-level rows rather than all rate plans. For the starting screen's full field reference and remembered selections, see Choose filters for a rates and availability report. For an organization-wide starting point, see Compare rates and availability across properties. Change the loaded report The controls above the spreadsheet refine the report. They do not change inventory. Dates 1. Enter the Start date and End date, or choose a month using Month / Year. 2. Click Load. 3. Confirm the dates remain selected and the spreadsheet's Date values match the requested range and weekdays. Sources, products, data and weekdays 1. Open All Channels, Room Types, Rate Plans, Data or Days. 2. Select the entries you need. A dropdown may show a selected-count badge or different summary when only some entries are selected. 3. Click Apply in that dropdown. Its accessible label is Apply — reloads report. 4. After the page reloads, check the selected entries and the spreadsheet's rows or columns. Changes are pending until the report reloads. Apply reloads all pending filter choices, not only the dropdown you clicked. A changed badge alone does not prove the spreadsheet has changed. If you switch view, download CSV or open a new window with pending changes, the application can ask you to Apply and continue or Cancel. Cancel stops that navigation; it does not necessarily clear your pending choices. Filter reference Control What it changes All Channels The selected inventory sources. Available entries depend on the property's connections. A master or PMS source is not an OTA read-back. All Live Read , when available Selects eligible connected sources to request when the report loads. It is not a local-only filter. Use one property matching the currently selected property. Clear all entries when you only want stored data. Room Types Standard room types to include. At least one eligible room type is required. Mapped virtual channel rooms can appear with their selected real parent. Rate Plans Standard plans to include. No selected plans means room-level rows only, where supported. Unmapped , when offered, includes configured channel plans without a standard rate-plan mapping. Data → Rates Includes SellRate and spreadsheet Rate Params . Toolbar CSV includes SellRate but not Rate Params. Data → Availability Includes Allocation and RoomsSold . These do not override stop-sell or other restrictions. Data → Restrictions Includes StopSell, minimum/maximum stay, cutoff, CTA and CTD columns. Days Includes inventory dates on the selected weekdays. At least one weekday is required. Fresh criteria default to all three Data groups and all weekdays. Excel View retains the choices supplied by the starting screen. Clearing a Data group removes its columns from the spreadsheet and from the toolbar CSV; it does not turn the omitted values into zero. Identity, Date and Timestamp columns remain. Channel Inventory Images are restricted to ChannelRUSH administrators and are not a customer-access requirement. Read the spreadsheet - Scroll horizontally to reach the remaining columns. The report is wider than a normal page. - Resize columns when a heading or value is clipped. - Use the Grid or List link above the spreadsheet if another presentation is easier to inspect. Excel identifies the current view. - New window, when shown, opens another report window with the current criteria. Excel View already uses a standalone layout without the usual application navigation. - Cells are read-only. Disabled editing or formatting controls do not mean you lack permission to download the report. Do not use spreadsheet editing commands as a way to update inventory. Rows represent a property, source, product and inventory date. There may be room-only rows, rate-plan rows and multiple channel products mapped to the same standard product. Do not add allocation across these rows or across sources as though each row were separate stock. Blank values and defaults need care - Blank SellRate or Allocation means this projection has no value to show; it does not mean a zero price or zero rooms. - Missing minimum-stay values can display as 1, missing cutoff as 0, and missing boolean restrictions as N. Those defaults are not confirmation that the channel explicitly supplied those values. - Maximum-stay value 99 is displayed as blank, as is a missing maximum. - RoomsSold is blank for sources that do not provide it, and zero can also be suppressed. Blank does not establish that no rooms sold. - On rate-plan rows, some allocation and numeric restrictions can fall back to the room's values. Stop Sell, CTA and CTD can be true when either the room or rate-plan flag is true. - A missing stored day can receive a current-looking Timestamp when the report creates an empty row. A timestamp beside blank values or normalized defaults is not evidence of a fresh source observation. On a combined rate-plan row, it is not necessarily the latest edit time of every displayed field. - Live Read rows have no timestamp in this output. An empty Live Read result does not prove zero inventory or a healthy connection. Download the spreadsheet workbook Use this when you want the spreadsheet's selected columns, including its additional source/product identifiers and Rate Params. 1. Finish applying your filters and check the loaded report. 2. Inside the spreadsheet, open File → Save As. 3. Choose Microsoft Excel (.xlsx). 4. In Save As, check or change File Name. 5. Click Save. 6. Open the downloaded file and confirm the property, dates, source/product rows and selected data columns. Save As dialog with the report filename and Save and Cancel controls The workbook download dialog for a demo-property report. The suggested filename includes the property and date range; a multi-property report uses Multiple Properties. Cancel closes the download dialog without producing the file. Downloaded files contain operational property data; check their contents before sharing them. Save As exports the workbook currently loaded in the browser. It does not re-query inventory. Changes that remain pending in the report controls are not a newly loaded workbook. The menu also offers older Excel, comma-separated values and PDF formats. A CSV chosen inside File → Save As exports the spreadsheet, not the separate toolbar CSV schema below. Do not treat those two CSV choices as interchangeable. File → Print opens the spreadsheet's print workflow; review the print preview before printing. Download the report CSV Use this when you want the report's separate CSV format, with standardized date and number formatting. 1. Apply the report criteria and confirm the selected Data groups. 2. Above the spreadsheet, click CSV in the Download group. 3. Open the downloaded .csv file in a spreadsheet application or import tool. 4. Check its headers, property, sources and date range before using the data. Toolbar CSV runs the report again for the criteria sent with the download. Values or timestamps can therefore differ from an earlier workbook if the underlying data changed. Its dates use yyyy-MM-dd; timestamps include a time-zone offset, not necessarily UTC. The spreadsheet uses localized display dates and timestamps. When importing CSV, preserve identifier columns as text if leading zeroes or long external IDs matter. The report CSV escapes commas, quotes and line breaks and protects formula-like text. If your import tool displays a protective leading apostrophe, inspect the original text rather than treating it as part of an identifier. Toolbar CSV headers With all Data groups selected, the columns appear in this order: PropertyId,PropertyName,ChannelId,ChannelName,RoomTypeId,RoomTypeName,RatePlanId,RatePlanName,ChannelRatePlanId,ChannelRatePlanName,Date,SellRate,Allocation,StopSell,MinNights,MinNightsThrough,MaxNights,MaxNightsThrough,CutOffDays,CTA,CTD,RoomsSold,Timestamp Clearing Rates removes SellRate. Clearing Availability removes Allocation and RoomsSold. Clearing Restrictions removes StopSell through CTD. The CSV never includes SourceFamily, SettingRoomTypeId, SettingRatePlanId or Rate Params. ChannelName retains any source-specific suffix. The remaining fields have the meanings in the reference below. Spreadsheet column reference The spreadsheet orders the identity columns first, then Date, the selected Rates/Availability/Restrictions groups, and Timestamp last. RoomsSold sits beside Allocation here, rather than near the end as it does in toolbar CSV. Column Meaning and example PropertyId ChannelRUSH property identifier. Use with PropertyName to distinguish properties in a combined report. PropertyName Property name for this row. SourceFamily C is the ordinary selected-source path, which can contain master, PMS, stored channel or CRS data. CLR identifies Live Read. CCI identifies the administrator-only stored Channel Image. C alone does not establish an OTA response. ChannelId Identifier for the source channel or inventory representation. It is not a reservation ID. ChannelName Source name. Read it with SourceFamily; special source names can include Live Read or Channel Image . RoomTypeId Standard property room-type ID. Several mapped channel rooms can share it. RoomTypeName Standard property room-type name. RatePlanId Standard property rate-plan ID. Blank on room-only rows or when no standard plan is mapped. RatePlanName Standard property rate-plan name, when applicable. SettingRoomTypeId ChannelRUSH channel-room mapping identifier. Distinguishes mapped products sharing a standard room type. It is not the provider's external room ID. Blank where not applicable. SettingRatePlanId ChannelRUSH channel-plan mapping identifier. Blank on room-only rows and sources without that mapping. ChannelRatePlanId External channel rate-plan ID, when applicable. Different from the standard RatePlanId. ChannelRatePlanName Configured channel plan name. It can differ from the standard RatePlanName. Date Inventory/stay date, not the report-run date or change time. SellRate Selected source's sell price, displayed to two decimals. Blank when absent. No currency column is included; this is not a guaranteed final channel quote. CRS values can reflect applicable configured promotions. Rate Params Additional or occupancy-related prices, where supplied, shown as amount - key/type , separated by semicolons. Blank when no prices are available. These appear only in the spreadsheet/its exports, not toolbar CSV. Allocation Source allocation or rooms available to sell. Positive allocation can coexist with StopSell=Y and does not by itself prove bookability. RoomsSold Source rooms-sold count where supplied. Not a total of reservations across report rows; blank can mean absent, inapplicable or suppressed zero. StopSell Y for a true stop-sell flag; N for false or a normalized missing value. MinNights Minimum length of stay for an arrival on Date. A displayed 1 can be a fallback for missing data. MinNightsThrough Minimum length of stay for a stay including Date. The same fallback caution applies. MaxNights Maximum length of stay for an arrival on Date. Missing values and 99 display blank. MaxNightsThrough Maximum length of stay for a stay including Date. Missing values and 99 display blank. CutOffDays Advance-booking cutoff in days. A displayed 0 can be a fallback for missing data, not a verified channel rule. CTA Closed to arrival on Date: Y/N, with missing values normalized to N. CTD Closed to departure on Date: Y/N, with missing values normalized to N. Timestamp Chosen stored day's edit timestamp displayed in your user time zone. Blank for Live Read. Missing stored days can show a newly generated timestamp; do not use this column alone to assess freshness or delivery. Check the result After loading, verify the property, dates, sources and products against the task you intended. Check the actual columns after changing Data, not only the dropdown badge. In a downloaded file, check the headers again: toolbar CSV and workbook exports are deliberately different. A successful download confirms that a file was generated. It does not confirm inventory delivery, channel acceptance, live retail prices or resolved synchronization problems. Investigate an unexpected value using its property, source, room/plan and date. Do not send or resend inventory merely because this report is blank or shows defaults. Common problems Symptom Likely cause and safe next action A dropdown changed but the spreadsheet did not The choice may still be pending. Click Apply in that dropdown; for dates, click Load . Confirm the loaded rows/columns. If they still disagree, record the criteria and contact support. Required-selection or date error Choose a valid start/end range and at least one eligible room, source, weekday and Data group. No selected rate plans is allowed for room-only output. Correct the displayed error and load again. A source, room or plan is unavailable Choices depend on accessible properties and configured mappings. Confirm the property and ask your administrator to check setup. Do not change mapping or permissions merely to make a report row appear. Live Read refuses a multi-property report Run it for one property matching the currently selected property, or clear Live Read and use stored sources. Escalate if a valid single-property selection is still refused. Rates, allocation or restriction columns are missing Check Data and apply the needed groups. Rate Params and mapping/source metadata are never in toolbar CSV; use the workbook export when those fields are required. The same standard room/plan appears several times Check source, channel plan and mapping identities. Virtual or multiple mapped products can share standard IDs. Do not deduplicate or total them without identifying what each row represents. Blank values, N flags or recent timestamps look inconsistent Missing-data normalization can produce that combination. Compare the correct source/product/date and contact support if the value matters operationally. Do not infer an open channel or successful synchronization. A download fails or no usable file appears Check the browser's downloads and any displayed error. Reopen the report after signing in again if needed, then retry the file download. A retry generates another file, not an inventory send; a toolbar CSV with Live Read selected can request source data again. If it still fails, send support the format, property, criteria, action time/time zone and error text. A downloaded date is shown as a number Workbook applications can display Excel's stored date serial when date formatting is not applied. Format that Date column as a date, or use toolbar CSV for ISO date text. Keep support examples scoped to the affected inventory. Do not send passwords, payment details or unrelated guest information. Related guides - Choose filters for a rates and availability report - Read rates and availability in List View - Compare rates and availability across properties
Add channels to a property
Add one or more channels to a property's channel list, then check which connection setup is still required. Before you start - Select the correct property. The Admin → Settings - CM route requires permission to edit Channel Settings. The Org Admin → Property Edit route requires Org Admin permission; Channel Settings permission alone does not grant access to it. If the relevant entry is missing, ask your organization administrator to check your access. - Know the exact channel or PMS integration you intend to add. Similar names, numbered instances and test integrations are not interchangeable. If you are unsure which entry to use, confirm it with support first. - Adding an entry is not the same as activating a connection. The channel may still need property identifiers, connection settings and room/rate-plan mappings. Its appearance in the list does not confirm inventory delivery, reservation delivery or acceptance by the channel. Special case — ChannelRUSH Master Image: use this entry only when support has confirmed that it belongs in your setup. Adding it can initialize settings and synchronize its room/rate mappings. Depending on existing settings, that setup can also clear stored master-inventory values for disabled fields. Do not include it in an exploratory batch of channels. A later error in the batch does not guarantee that its setup work was undone. Open Add Channels From property Admin 1. Choose the property in the property selector. 2. Open Admin → Settings - CM. 3. In the Channel Manager section, locate Channels. 4. Click Add New beside the channel list. 5. On Add Channels, check the property name and ID above the selectors before making any selection. From Org Admin 1. Choose the property in the property selector. 2. Open Org Admin → Property Edit. 3. Locate Channels near the top of Property Edit. 4. Click Add New beside Sort. 5. On Add Channels, check the property name and ID above the selectors. The breadcrumb also identifies the organization and property. Both entry paths provide the same ten selection slots. Their return destinations differ: the property-Admin form returns to Admin, while the Org Admin form returns to Property Edit for the same property. Add Channels form for a demo property, showing ten empty channel selectors and the Save and Cancel controls. The property-Admin form is shown. Both forms have ten selection slots and Save/Cancel controls; you do not need to fill every slot. Choose and add channels Selections are submitted when you click Save. Searching or choosing an option does not itself add the channel. 1. Open a Select channel... field. 2. Type part of the channel name to narrow the list. 3. Choose the exact entry you need. 4. Repeat in another empty field for each additional channel, up to ten selections in this submission. 5. Leave unused fields at Select channel.... To remove a selection before saving, choose that empty option again. 6. Review all selected names and the property name. 7. Click Save once. If an error appears, stop and read it before submitting again. Check the property's channel list before retrying; a failed submission is not a guarantee that every setup action was rolled back. If the result is unclear—especially if you selected ChannelRUSH Master Image—ask support to confirm the saved state first. To leave without submitting the current selections, click Cancel. The property-Admin form returns to Admin; the Org Admin form returns to Property Edit. Cancel does not reverse a previous Save. Adding another instance of the same channel Entries such as Booking.com - [2] and Booking.com - [3] represent additional instances. Do not choose them as substitutes for the ordinary entry or as a way to repair an existing connection. Confirm with support that another instance is required. Add and verify the ordinary instance first, then add additional instances in order. The page can reject an additional instance when its preceding instance is missing. Existing channels and duplicate selections If the selected channel is already assigned to the property, Save skips that entry. Selecting the same entry in more than one slot does not create another copy or reconfigure the existing connection. A save containing only empty slots or existing channels can return a saved message without adding anything new. Check the list, not the message alone. Check the result and continue setup 1. After a successful Save, review Channels on the return page: the Channel Manager section of Admin for the property-Admin form, or Property Edit for the Org Admin form. 2. Confirm that each intended channel appears under the correct property. 3. Click a channel's name to open its Channel Settings, ChannelRUSH CRS included. On a CRS entry, the [CRS] tag before the name is a link too: it opens CRS Settings at Rooms & Rates. 4. Review the connection's setup requirements and any warnings before enabling or changing its operation. Use the Channel Settings guide for the field reference, and confirm integration-specific details with support when needed. [NS] beside a channel means it is not set up. Resolve the missing setup rather than adding the same entry again. Absence of [NS] is not proof that a channel has accepted inventory or that reservation delivery works. This procedure confirms the property-list assignment. It does not create an account with the channel, replace channel onboarding, or test the connection. Do not send an inventory refresh merely to check that the entry was added. Field and control reference Field or control What it does Example or important detail Property name and ID Identifies the property receiving the selected channels. Check both before Save; selecting channels does not change the property. Ten Select channel... fields Each accepts one existing entry from the channel catalog. Each starts empty. Choose Booking.com in one slot and another intended channel in a different slot. Ten is the limit for one submission, not a total-property limit. Search inside a selector Filters the choices by their displayed text. Search for Booking and then check the complete entry name. Typing a new name does not create a new integration. Empty Select channel... option Leaves that slot unused. Empty slots are skipped; they do not remove existing channels. Save Validates the selected entries and saves the property assignments when the page's validation passes. Existing or repeated entries are skipped. Special Master Image setup can occur before the entire batch has passed validation. Cancel Leaves without submitting the current selections. Returns to Admin from the property-Admin form or Property Edit from the Org Admin form. It does not undo an earlier submission. Admin breadcrumb, property-Admin form Returns to the Channel Manager section of Admin for the same property. Use it to inspect the existing Channels list. Organization/property breadcrumbs, Org Admin form Provide links to OA , Accounts , the organization and the property's Property Edit page. The property-name/ID link returns to the property's channel list. Check context before moving to another organization or property. Common problems Add New is missing or saving is not permitted For the property-Admin route, ask your organization administrator to check Channel Settings permission and property access. For Org Admin → Property Edit, check Org Admin permission instead; the Org Admin menu can be visible without access to Property Edit. Being able to open a form does not establish permission to save it. Demonstration sign-ins can also prohibit configuration saves. You cannot find the intended integration Search by part of its name and check the full result names. If it is still absent, ask support which integration should be used. Do not select a similarly named test, numbered or generic API entry to work around the missing choice. “You can't add an additional channel instance (i.e. [2], [3]) without a previous instance.” Check the property's existing channel list and the exact instance names. Confirm the intended sequence before retrying. If the preceding instance is present but the message persists, contact support rather than adding unrelated entries. A generic PMS API entry is rejected on a production account Some generic ChannelRUSH API entries require an integration specific to the property or company. Ask support for the correct integration. Selecting a different API version is not a safe workaround. A test channel is rejected Certain test integrations can only be added to designated ChannelRUSH test organizations. Ask support to confirm the correct production entry. A test entry appearing in the selector does not mean it is suitable for your property. If the error names a different integration from the one you selected, stop and give support both the selected name and the exact error. Do not choose another test or API entry to work around it. Save returns an error, or the result is uncertain Record the error and inspect the property's Channels list through your entry path: Admin → Settings - CM, or Org Admin → Property Edit. Do not assume that the whole operation was undone, and do not delete/re-add a connection as a repair. If the outcome is unclear, contact support with the property name/ID, exact channel names, action time and time zone, and error text. Do not include passwords or guest/payment information. A channel appears but is not ready to use Adding the entry and completing its connection setup are separate steps. Open its settings and inspect the setup warnings. If the required property identifiers or mappings are unknown, stop and obtain those details rather than guessing. Related - Channel Settings — OTA field reference
Add channel rate plans
Add rate-plan entries to selected channel room types and connect them to your property's standard rate plans where needed. Before you start - Open the correct property's Channel Settings page for the channel you want to configure. From Accounts, you can open a channel by clicking its name beneath that property. - You need permission to edit Channel Settings to save. Ask your organization administrator if the form is disabled. Demonstration accounts cannot save these settings. - Have the channel's confirmed rate-plan names and IDs, the intended room types, and any required channel-specific settings ready. Do not guess IDs or reuse an ID across rooms unless the channel uses it for those rooms. - The channel room types must already be present. If you use standard rate plans, create them at property level before selecting their mappings here. - Check the existing rate plans first. This screen adds entries; it is not an editor for existing plans. If the channel settings show Add Unmapped Rate Plans, that is a separate workflow for importing plans already identified in the channel's mappings. Saving has consequences beyond filling in a form. Save stores the new plans in ChannelRUSH and, for channels that support it, can also send channel settings. That send can include existing settings, not only your new plans. Updating Enabled = No does not prevent a settings send and is not a stop-sell instruction. Add the plans 1. On Channel Settings, confirm the property and channel. Open Menu and choose Add Rate Plans. 2. Under Room Types, select the channel room types that should receive the new plans. Each label identifies the property's standard room type followed by the channel room name and ID. Virtual room types are identified separately when present. 3. In Rate Plan 1, enter the Name and Channel Rate Plan ID supplied for that channel. 4. Set Updating Enabled deliberately. It starts at Yes. Choose No if inventory updates must remain disabled for the new plan while you finish its setup. 5. If Standard Rate Plan Mapping is shown, select the corresponding property standard rate plan. Leave it blank only when that is the intended mapping for your setup. 6. Complete any additional required channel-specific fields shown for the plan. Use the channel's supplied values. If you do not know a field's meaning or expected value, stop and confirm with support before saving. 7. Fill further numbered sections as needed, up to Rate Plan 10. Leave both Name and Channel Rate Plan ID empty in every unused section. 8. Review the room selection and every populated plan section, then click Save once. The Save buttons at the top and bottom submit the same form. Every populated plan section is added to every selected room type. There is no separate room selection for each section. If different rooms require different plan IDs, mappings or settings, add them in separate batches with only the appropriate rooms selected. Add Rate Plans form showing room-type selection and the first plan's name, channel ID, updating choice and standard mapping Example from a demonstration property. Further numbered plan sections continue below; the available rooms, standard plans and extra fields depend on your setup. Selection and cancellation - All Room Types selects or clears the room choices in the group. Check the selected count and individual choices before saving. No rooms are selected on a fresh form. - Cancel returns to the same channel's settings without submitting this form. It does not undo a previous Save. If a leave-page warning appears after you edit fields, stay on the page unless you intend to discard those unsaved entries. - Entering values or selecting rooms does not itself submit this form. You must click Save to add the plans. Check the result After a completed Save, you return to Channel Settings. The confirmation says that a number of rate plans have been added and saved for a number of room types. The plan count is the number of populated plan sections, not the total number of entries across all selected rooms. 1. Review all messages, including any settings-send error alongside the saved confirmation. 2. Locate each selected room type and check the new plans' names, channel IDs, Updating Enabled values and Standard Rate Plan Mapping selections. 3. Look for [NOT SETUP], [INVALID MAPPING] or other configuration warnings. Do not start updates until the intended mappings and required settings are confirmed. Do not rely on this form to reject every incomplete or duplicate entry. 4. If a settings send failed, or the page timed out, inspect the channel settings before adding anything again. The plans may already be saved. Contact support if you cannot establish what completed. Saved in ChannelRUSH is not the same as accepted by the channel. A saved confirmation does not prove that the channel created a sellable plan, received rates or availability, or opened it for booking. Even a settings-send success message is not a general confirmation of those outcomes. Complete the channel's setup checks before beginning inventory updates. Field reference Room Types Select the destinations for the entire batch. The standard room name helps you recognize the property room; the accompanying channel name and ID identify its mapping. A blank or unexpected channel mapping needs investigation before adding plans. Selecting a virtual room type adds entries to that virtual room type, not automatically to its parent. Name The display name for the new channel plan, for example Flexible. Start with the channel's supplied name so you can recognize it during setup. The name does not replace the channel ID used for mapping. A completely unused section must have both its name and channel ID empty. An incomplete section with only one of them filled can still be processed; do not use partially completed sections as drafts when saving the rest. Channel Rate Plan ID The channel's identifier for this plan within the selected room types. Copy the confirmed identifier exactly, including any leading zeros or letters. It is not the property's standard rate-plan ID. A wrong ID can associate updates with the wrong plan or leave the plan incorrectly mapped. Check that the same ID is valid for every room selected in this batch. This form does not offer a different ID for each selected room. Updating Enabled Yes allows inventory updating for the plan when the other channel, room and setup requirements are met. No disables ordinary inventory updating for that plan. The initial value is Yes in every numbered section. This is not a command to close sales on the channel. It also does not suppress the channel-settings send that Save can perform. Setting it to No is therefore not a way to make an uncertain settings submission safe. Standard Rate Plan Mapping Select an existing property standard rate plan to associate with this channel plan. This allows updates directed to that standard plan to select the corresponding channel plans. The initial choice is blank. Blank leaves the plan without a named standard rate-plan mapping; it does not mean that all inventory updating is disabled. Room-level updates can still reach eligible plans. The control is absent when the property has no standard rate plans. Choosing an option here does not create or rename a property standard rate plan. Additional channel-specific fields Some channels show extra settings beneath each plan, using text, numeric, single-choice or multiple-choice controls. These values apply to that plan in every selected room. For a multiple-choice control, retain every value required by the channel. Use the exact choices or values required for your connection. If a required setting is missing from the form, do not assume a default or repeatedly add the plan to fix it. Ask support how that channel's setup must be completed. Common problems “No rate plan names have been entered.” No section contains a usable entry for the form to process. Enter the confirmed name and channel ID in at least one section, check the room selection, and save. Do not enter only an ID to bypass the message. “No room types have been selected.” The form has a plan entry but no selected destination room. Select the intended room types, recheck all populated sections, and save. If the required room is missing, return to Channel Settings and have its room mapping completed first. The form is disabled or saving is refused Your account may lack Channel Settings editing permission, or you may be using a demonstration account. Ask your organization administrator to confirm your access. Do not use another person's login or try a broader administrative route to bypass the restriction. A plan is saved but shows a setup or mapping warning Its identifiers or required settings may be incomplete or inconsistent with the channel. Review the existing entry and confirm the channel's values. Adding the same plan again is not a repair. Contact support if the correct mapping or required setting is unclear. A settings-send error appears, or the result is uncertain Local saving and sending settings are separate steps. A send failure does not undo the saved plans. Reload the channel settings, check for the new entries, and collect the message before asking support to investigate. Do not repeat Save merely because an error appeared; a repeat submission can add duplicate entries. The standard mapping choice is missing or the required plan is not listed The list comes from this property's standard rate plans. Check that you selected the correct property and that the required standard plan exists. Ask your organization administrator to complete the property setup rather than mapping to an unrelated plan. When contacting support, provide the property, channel, affected room and plan names/IDs, action time with time zone, and the exact error text. Do not send passwords, payment details or guest information. Related - Channel Settings Page — OTA
Find missing rates and availability
Use Missing Availability to identify gaps in stored rates or allocation for a property, find the affected dates, and decide what needs investigation. This is a stored-data check, not a live query to a booking channel or your PMS. A listed gap needs investigation; an empty report does not prove that every room is bookable or that an update reached a channel. Before you start - Sign in with access to the property you want to inspect. Viewing the report does not grant permission to change inventory. - Know whether your PMS or your team controls that property's rates and allocation. Investigate the responsible source before making a manual correction. - Allocation means the number of rooms recorded as available. A missing value is different from an explicit zero. Zero is recorded data, not a missing allocation. Open and run the report 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Missing Availability. 3. Enter a whole number from 1 to 24 in Number of Months. The default is 18. 4. Click View Report. 5. Check Next … months and, when findings are shown, Date Range to confirm the report loaded the intended period. The period starts today in your signed-in user's time zone. It includes today and the ending date the selected number of calendar months ahead. A channel with a shorter supported update horizon is checked only as far ahead as that channel permits, even though Date Range still shows the full report period. Changing Number of Months does not reload the report until you click View Report or press Enter in that field. Running the report does not submit inventory changes. Number of Months, Channels, Room Types and View Report controls The report controls, shown with a one-month period. Narrow the findings Use Channels and Room Types to focus on the findings already loaded: 1. Open Channels. 2. Leave checked the channels you want to see. 3. Open Room Types. 4. Leave checked the room types you want to see. 5. Close the dropdown to read the matching items. These selections take effect immediately. You do not need to click View Report to apply them. A row must match both selections when you narrow both controls. Select all toggles the options in that dropdown. Checking every option or clearing every option removes that filter; clearing all boxes does not mean “show nothing.” Only channels and room types with findings in the loaded report are offered. A dropdown can be absent when there are fewer than two choices. A channel absent from this list is not necessarily healthy: it may be outside the report's scope or not eligible for a particular check. Filtering does not recalculate the summary figures or group item counts. They still describe the loaded report, not only the rows you can currently see. Filtering also does not restrict the destinations of a later inventory edit. The dropdown selections and grouping choice are temporary. Reloading, clicking View Report, or opening New window loads the report again without retaining these display-only selections. If you opened a link that already restricts the report to particular channels or rooms, changing the month range retains that link's underlying scope; clearing the display filters cannot add products that were never loaded. Reopen the report from the menu when you need its default scope. Read the summary Missing Availability summary, grouping buttons, unique-day counts and date range These figures describe the loaded report. Display filters do not change them. Field What it tells you Days Missing Rates The number of distinct dates with at least one qualifying missing-rate finding. The same date counts once even if several products have a gap. It is not a count of missing rooms or room-nights. Days Missing Allocation The number of distinct dates with at least one qualifying missing-allocation finding. Dates are counted once across the report. Channels Affected The number of distinct channel names represented in the findings. Date Range The overall period requested. Individual channels may have a shorter effective horizon. By Channel Groups findings under each channel. This is the initial view. By Room Type Groups the same findings under each property room type. It changes presentation, not the underlying check. A zero missing-rate count does not prove that rates are complete. Where allocation is part of the check, missing rates are generally reported only when qualifying positive allocation exists. Missing or zero allocation can therefore prevent a missing-rate finding. Read an affected item In By Channel, each heading identifies the channel. The items count is the number of affected room-level or rate-plan-level entries in that group—not a count of dates. Each item shows: - The property's room-type name, followed by its channel room-type name in parentheses. - A channel rate-plan name after the slash, when the finding is at rate-plan level. This can differ from the property's mapped rate-plan name in Calendar. - days no rate and/or days no allocation badges for that item. - Missing Rates and/or Missing Allocation, with the affected date ranges beneath each label. In By Room Type, the group heading supplies the property room type. Each item then shows the channel and, where applicable, the rate plan. Use By Channel when you also need the channel room-type name to distinguish mappings. One affected Studio room and Standard Rate plan, showing missing allocation dates One demo finding from the Booking.com group: the property room is Studio, the channel room is Single, and the plan is Standard Rate. Consecutive missing dates are combined into one range. Both dates in a range are included. Separate ranges indicate gaps on different runs of dates. The item counts describe all of that item's qualifying dates, not only the first range shown. What qualifies as missing? The check depends on the channel's supported fields, configured mappings and room/rate-plan settings. It does not inspect every configured product in the same way. Booking-channel findings For supported outbound channels, the report checks the values stored for inventory requests alongside the stored channel-report values. It does not fetch fresh values from the channel when you open this page. - Missing allocation: neither stored source has an allocation at the checked level. At rate-plan level, a recorded parent-room allocation can also prevent a missing-allocation finding. - Missing rate: neither source has a sell rate or any recorded occupancy-specific sell rate at the checked level. One recorded occupancy-specific rate is enough to avoid this missing-rate check; it is not a completeness audit of every occupancy price. - Positive-allocation condition: when allocation is supported and applied at the same level, a missing rate is listed only if at least one source has allocation above zero there. For an outbound rate-plan rate check, parent-room allocation is not used as a substitute for plan-level positive allocation. A value can be present in the stored request data before delivery succeeds. Its presence does not confirm channel acceptance. Likewise, a stored channel-report value is not proof of a fresh observation made during this report run. PMS or other inventory-source findings For eligible incoming inventory connections, the report checks stored master inventory from that source, rather than querying the PMS live. At rate-plan level, parent-room data can satisfy the check: allocation is missing only when neither the plan nor its parent room has a value; a rate is missing only when neither has a sell rate or an occupancy-specific sell rate. Where allocation applies, positive allocation on the plan or parent room can qualify the rate gap for reporting. Important boundaries - Explicit zero rates or allocation count as present values. “Not missing” does not mean the value is valid for sale or accepted by a channel. - A recorded parent-room allocation of zero can prevent a plan-level missing-allocation finding. - Unsupported or unapplied fields, incomplete mappings, and ineligible room/rate-plan configurations are excluded from their respective checks. The report is not a setup-completeness audit. - A connection appearing in the report does not by itself prove it is currently enabled to send updates. - Stop Sell, arrival/departure restrictions and length-of-stay rules are not used to establish bookability here. Deliberately closed products can still have missing-data findings. - There is no observation timestamp or delivery outcome attached to each finding. Use the relevant inventory and update-status screens for those separate questions. Investigate the dates safely 1. Note the channel, property room type, channel room type, rate plan and full missing date range from the finding. 2. Click the relevant date-range link under Missing Rates or Missing Allocation. Calendar opens in a new tab; the report remains open. 3. Check the property and loaded dates in Calendar before continuing. 4. Select and load the appropriate room, rate plan and channel display criteria in Calendar, following the Calendar Update guide. 5. Compare the finding with the values and inventory source you intended to use. If the PMS controls those values, investigate its supplied data before overriding it manually. The date link carries the property and dates only. It does not select the finding's channel, room or rate plan. A long range opens only its beginning in Calendar; check the complete range in the report and review the remaining dates separately. Always verify Calendar's actual loaded dates, including when using a different display language. Opening Calendar does not submit an inventory update. Editing a Calendar cell can submit immediately, however. Do not type a trial value to inspect the screen, and do not use a broad master edit to work around a channel-specific restriction. Follow the Calendar guide's scope, permissions and result-check instructions before making an authorized correction. Check the result After the responsible source has been corrected and the relevant data is available in ChannelRUSH: 1. Return to Missing Availability for the same property. 2. Confirm Number of Months still covers the affected dates. 3. Click View Report to load the stored data again. 4. Reapply any display filters you need. 5. Check whether the affected item or date range remains. A disappearing finding means the report no longer finds that qualifying gap in its current scope. It does not prove that an update was accepted by the booking channel. Verify any update separately using the result-check procedure in the Calendar Update guide, or investigate requests with the inventory update investigation guide. If the page says No Missing Availability, interpret it as “no qualifying gaps found within this report's scope.” Do not treat its accompanying all-products message as proof of live availability, complete prices, successful delivery or correct restrictions. Open a separate report window Click New window to open the report without the normal application navigation. It retains the property, month range and any underlying URL scope, but not temporary checkbox filtering or grouping changes. This is another view of the report, not a download. The standalone page has no CSV, Excel or Copy to Clipboard control. Changing the month range with View Report from the separate window returns that tab to the normal application layout. Common problems Symptom Likely explanation and safe next action The figures stay the same when I filter. The dropdowns hide findings but do not recalculate totals or group counts. Read the visible item details for your selected subset. Clearing every checkbox shows more rows. No selected options means no narrowing. Select the specific options you want instead. A channel or room is absent from the dropdown. Choices come from loaded findings, and single-choice dropdowns may be omitted. Reopen from the menu, check the property and period, and review mappings/support if coverage is still unexpected. Do not infer success from absence. Changing the month number did not change the dates. Click View Report and check the resulting Date Range . Use a whole number from 1 to 24; if a valid value still fails to load, report the entered value and any error to support. Calendar shows other products or fewer dates. The link does not carry product filters and long ranges are shortened. Select the intended products and verify loaded dates before editing. If the dates still differ after using Calendar's controls, stop and contact support. A closed or disabled product is listed. Missing stored data and operational saleability are different questions. Confirm whether the product should be sold and which source owns its values; do not reopen it merely to remove a finding. Missing allocation is shown, but no missing-rate warning appears. Rate-gap checks may require positive allocation. Investigate the allocation/source first and rerun the report after an appropriate correction; the absent rate warning is not an assurance that a price exists. The finding remains after a correction. Re-run the report with the same scope and check the source and relevant update outcome. Do not repeatedly resend or broaden an edit based only on this report. Escalate if stored values and the finding remain inconsistent or the earlier action's outcome is unclear. The report is empty, but a room still cannot be booked. The report does not establish channel acceptance, restrictions, occupancy-price completeness or live bookability. Investigate those separately instead of repeating an inventory update without evidence. For support, provide the property, channel, affected room and rate plan, missing date range, report period, relevant action time and time zone, and any error text. Do not send passwords, payment information or unrelated guest details. Related guides - Update rates, availability and restrictions in the calendar - Read rates and availability in List View - Investigate inventory update requests across properties
Investigate inventory update status for a property
Find the requests behind a property's rate, availability or restriction change, read their processing results, and choose a safe next action. Before you start - Sign in with access to the property you want to investigate. Select that property in the application’s property selector before opening Updates → Status. The heading is Update Status. - This page shows outbound inventory update requests. It is not the reservation-delivery screen or a live comparison with a channel's current inventory. - Searching does not resend inventory. Search applies filters; Go runs the selected request action. Do not use Go to refresh results. - Retry, Archive and Un-Archive require an update permission for rates, availability or restrictions. Viewing the page does not grant those permissions. The public demo login can search but cannot run these actions or open the support form through Go. Find the affected requests 1. Select the affected property in the property selector. 2. Open Updates → Status. 3. Select the destination Channel, if known. 4. Select Status, or leave All if you are following a request whose status may change. 5. Select the relevant Room Type, Rate Plan, Sent By or Source, if needed. 6. Click Search. 7. Check the retained selections, Filtered by summary and matching request rows. The page loads requests when opened. Changing a filter does not load new results until you click Search. Clear Search Filter removes the search criteria, not the saved requests. Search Filters with status, channel, product, origin, data-type, archived, stay-date and timestamp controls. At narrower widths, the same controls stack vertically. The selected property is in the application’s property selector, outside this filter card. Use » and « to move through results, normally 50 requests at a time, with newer request IDs first. Paging retains the applied search criteria. Click a filter's remove control in Filtered by to remove that filter group and reload from the beginning. Removing the Data group removes all its data-type selections together. Find a known request ID 1. Select the correct property. 2. Click Clear Search Filter to start without conflicting criteria. 3. Enter the numeric ID from the request in Request ID. This is not a reservation number. 4. Leave Rates, Availability and Restrictions unticked, or tick all three. 5. Click Search. 6. Confirm the returned row has the intended ID. A Request ID search overrides most ordinary search filters, including status, channel, products, source, sender, date matching and the normal archived exclusion. However, a partial Data selection can still hide it, and reversed date ranges can prevent the search. The Request ID summary does not display those remaining constraints. Clear the ID before returning to an ordinary filtered search. Read a request and check the result The Channel / Room Type / Rate Plan column identifies the destination and product. The Updates column shows the stored request's affected dates, applicable weekdays and values. Those dates are different from when the request was created or processed. A stored demo request showing a room and rate plan, rates, Stop Sell, Min Nights, Successful status, attempt count, request ID and timestamps. This is historical request data. Successful processing is not a fresh check of the channel's current rates or availability. Read the information beneath the requested values: - Status: the recorded processing state. Read any accompanying message, not only the colored marker. - Attempts: the processing attempt count, not a count of confirmed successful deliveries. - Source and sender: where the request originated. For example, UI Quick in the filter appears as UI - Quick in a result. PMS-related requests can identify a PMS channel rather than a person. - Archived: when shown, the request is marked archived. This is separate from its processing status. - ID: the internal inventory request identifier to use for a precise search or support investigation. - Created: when the request was created. - Last Run: its recorded processing/edit time. Queuing a retry also changes this timestamp; a recent Last Run alone does not prove a completed send. - Logs: opens the available attempt log in a new tab. This link is not shown for every request. Missing or empty logs do not prove success or failure. See Inspect an inventory update request log. Created and Last Run use your user's time zone, shown beside the timestamps. Log message timestamps use UTC. Preserve the relevant zone when reporting a problem. Status reference Status What it tells you All No status restriction. Use it when following a request through state changes. Pending Waiting for processing; not confirmation of channel acceptance. Processing Processing is in progress. Investigate before requesting another attempt. Successful ChannelRUSH recorded successful processing. This does not establish that every current channel value matches your intended inventory. Unsuccessful Processing did not succeed. This filter includes failed processing requests as well. Read the message and investigate the cause before retrying. For a request you are following, search again by ID or with All status and inspect the latest status, message and logs. Disappearing from an unsuccessful-only search can mean its status changed. An empty list does not establish delivery. When channel confirmation is needed, check the intended product, dates and values in the channel as well. Filter reference Filters normally narrow one another: the matching request must satisfy each selected filter. A Request ID search has the exceptions described above. Destination, product and origin Field What it does Status Selects a processing state. All leaves status unrestricted. Unsuccessful includes failed processing results. Channel Selects the destination channel, not the PMS or workflow that originated the update. All leaves the destination unrestricted within the selected property. Room Type Matches the property's standard room type. It is not a search for a channel room code. Rate Plan Matches the property's standard rate plan. A result can show the corresponding channel rate-plan name instead. Sent By Matches the user associated with a request. Available choices can include PMS - … entries as well as property users. All leaves the sender unrestricted. Source Matches the originating workflow. For example, choose UI Quick to investigate a Quick Update. It is independent of Channel. Request ID Finds a specific internal inventory request. Use the known-ID procedure above rather than combining it with unrelated criteria. Source choices include PMS, UI Daily, UI Detail, UI Quick, UI Calendar, UI Bulk Import, Channel Refresh, Master Refresh, PMS Refresh, Reservation Adjustment, Office Hours and Future Limit Loader. These identify the origin, not a separate delivery-success state. Data and archived requests Control Meaning Rates Matches requests with recorded net/sell rate changes or additional rate parameters. Availability Matches recorded allocation or Stop Sell changes. Stop Sell belongs here, not under Restrictions. Restrictions Matches recorded arrival/departure closures, minimum/maximum nights, through-night restrictions or cutoff-day changes. Include Archived Updates Includes archived and nonarchived requests. Unticked normally excludes archived requests. This checkbox only changes visibility; it does not archive anything. With none or all three Data controls selected, there is no data-type restriction. Selecting one or two matches any selected type, not necessarily every selected type. The whole request is displayed, including its other values. Older requests without recorded change-type information can disappear under a partial selection; use none or all three when locating a known request. Channel-specific custom parameters alone are not one of these three data groups. Stay Dates Use Stay Dates for the dates whose inventory the request affects, not the day you sent it. - Enter both dates to find requests whose affected-date span overlaps that range, including spans beginning earlier or ending later. - Enter only the first date to find requests ending on or after it. - Enter only the last date to find requests starting on or before it. - Enter the same date at both ends to find requests covering that date; requests explicitly excluding its weekday are excluded. - Leave both blank for no stay-date restriction. For a multi-day range, inspect each request's displayed weekdays as well as its date span. Span overlap alone does not establish that every night in your search is included. Date and Time Use Date and Time for when the request was created or last processed/edited. This range is independent of Stay Dates, so you can use both together. 1. Choose Created or Last Run. 2. Enter the first and/or last date using the displayed date format. 3. Enter an optional time beside each date if you need a narrower window. 4. Click Search. Created is the default timestamp choice. Last Run includes the recorded edit time changed by a retry; it is not proof of a completed channel send. Times use your user's time zone, identified beneath the controls. Without a time, the entire date is included: a multi-day range includes the whole final day. With a time, the starting minute is included and the entire final selected minute is included. A time without its accompanying date does not narrow the search. Leave both dates blank for no timestamp restriction. For example, use Stay Dates for a weekend whose rates are wrong, and Created for the day your team submitted the change. These answer different questions and can be combined. If The End Date cannot be before the Start Date. or The last stay date cannot be before the first. appears, correct the relevant range and click Search again. Do not interpret the error-state list as a completed search. Requested values reference The values shown depend on what is stored in the request and supported by its channel. This screen is a viewer, not an inventory editor. Value Meaning in the stored request Sell Rate / Net Rate Requested amounts and currency. An asterisk marks the selected rate type. Allocation Available-room quantity carried by the request. Stop Sell Whether sales are closed or opened for the request's scope. CTA / CTD Closed to arrival / closed to departure. Cut Off Days Advance-booking cutoff value. Min Nights / Max Nights Minimum/maximum stay values. Min Nights Through / Max Nights Through Through-stay restriction values. Additional rate/channel parameters Channel-specific values shown when present and supported. A missing field is not automatically zero, No or a removal instruction. VRT identifies a virtual room type. [BLANK / NOT SET] indicates missing product-name information: check the setup before deciding to retry. Choose a safe next action The dropdown and Go controls above and below the results operate on the checked requests. The table-heading checkbox selects the requests on the current page, not every matching request across other pages. This page has no all-matching Retry or Archive action. First finish your search, inspect the rows, and tick the intended requests. Changing a search field without clicking Search does not replace the rows you are selecting. Do not assume Go will show a second confirmation before changing requests. Send evidence to support 1. Find the affected requests with Search. 2. Tick their checkboxes. 3. Select Send To Support. 4. Click Go to open the support form. 5. Review the selected request details, enter an appropriate Subject and describe the problem in Message. 6. Click Send when you intend to contact support, or Cancel to leave without sending. Opening the form does not send the message. Include the property, channel, affected inventory dates, request IDs, action time/time zone, expected result and relevant error text. Never include passwords, payment details or unnecessary guest data. The support message includes generated request details, not an automatic attachment of every raw attempt log. Its confirmation does not mean the inventory problem is resolved or guarantee that a person has received it. If the send outcome is unclear, check before sending the same message repeatedly. Returning to the list can restart on its first page; recheck the criteria and selected requests. Retry Retry can also requeue later overlapping requests for the same property, channel and mapped products. Those requests need not share your selected status or source. Processing can use current settings. If you are unsure which requests will be affected, contact support before retrying. 1. Read the error/message and resolve the underlying issue, or obtain support's recommendation. 2. Search again and check that the request is not already Processing and its affected dates are still relevant. 3. Tick the specific requests you intend to retry. 4. Select Retry. 5. Click Go. 6. Search again by the known IDs or with All status. 7. Inspect the resulting status, message and logs before considering another attempt. Requests requeued for retry become Pending and unarchived, and their previous message is cleared. The attempt count is not reset. Past-only requests may no longer be eligible. All requests marked to be retried confirms the retry action, not that every selected record changed or that the channel accepted the inventory. Do not repeat Retry merely because acceptance is not yet confirmed. Archive and Un-Archive Archive is not cancellation. It does not stop a pending send, prevent automatic retries, reverse inventory or delete the request. Automatic retry can unarchive it again. Archiving changes shared request state, not a private viewing preference. 1. Search for the requests and review their status and dates. 2. Tick the intended rows. 3. Select Archive or Un-Archive. 4. Click Go. 5. Find the known request IDs, or enable Include Archived Updates and click Search. 6. Check whether the Archived indicator is present as expected. Un-Archive removes the archive flag; it does not itself request a retry. Neither action changes the processing status or establishes that a delivery problem has been resolved. Common problems - No requests appear: filters may exclude the request. Clear the search, use a known Request ID, or broaden the relevant status, date, product, source, sender, archived and Data choices. If it remains missing, contact support with the property, channel, dates and action time; do not resend inventory solely because the list is empty. - A known ID is missing despite an ID-only summary: clear partial Data selections and conflicting/reversed dates, confirm the selected property, and Search again. If the row is still missing, escalate with the ID rather than changing inventory. - The request disappears after retry/archive: its status or archive flag may no longer match your search. Search by ID or use All status and Include Archived Updates. Disappearance alone is not proof of delivery. - Go reports no action or no requests selected: select the intended action and tick the intended rows. If Actions do not match appears, make the top and bottom dropdowns agree before continuing. - Some selected requests are left out: they are no longer valid requests of the current property. Reload and reselect the intended rows. Ask support if the scope remains unclear; do not switch property context to bypass the warning. - An action is denied: ask your administrator to check update permissions. Public demo accounts are restricted to searching here. - A request stays Pending/Processing, fails again, or reappears after archiving: Search again and inspect its message and timestamps. Archive does not stop processing or automatic retry. Contact support with the request ID before repeated manual retries. Related - Inspect an inventory update request log - Understand your inventory processing summary - Update rates, availability and restrictions with Quick Update
Check reservation delivery across properties
Find email and PMS delivery requests across your authorized properties, distinguish a failed attempt from a booking's status, and choose a safe investigation path. Before you start Use Org Admin → Reservations - Delivery Status for a cross-property search. This is different from Reservations → Delivery Status, which searches the selected property. The Org Admin menu is available to organization administrators and users with the relevant multi-property access. Your account's property and organization access still limits the results. If the menu or a required property is missing, ask your Org Admin to confirm your access. Search does not send or resend reservations. Opening an investigation link is different from submitting a new delivery. Sending requires the Reservations - Actions permission, including roles that grant it. Find the delivery requests 1. Open Org Admin → Reservations - Delivery Status. Check the heading Reservations - Delivery Status. 2. Choose Organization, if that field is available. Choose it before Property: changing organization clears the property selection. 3. Choose Property to investigate one property, or leave All to search the permitted scope. The property selected in the application's top bar is not itself this search's Property filter. 4. Enter the complete channel reservation number in Reservation ID when investigating one booking. Leave it blank to review multiple bookings. This field does not search PMS confirmation numbers. Numeric values can also match an internal reservation-version ID or a delivery-request ID, so check the displayed booking number, source and property. 5. Select Delivery Type: Email, PMS - All, PMS - Pickup / Confirm, or PMS - Push. Leave All to compare delivery methods. 6. Select Delivery Status. Use Unsuccessful to find failed requests; use All when looking for a later attempt after a failure. 7. Select Channel if needed. It matches either the reservation's source channel or the delivery destination. 8. Set the Created date range if needed. Use the left date/time for the start and the right date/time for the end. Move out of a typed date field before continuing. These are request-creation dates, not arrival, departure or processing-completion dates. 9. Select Search. Cross-property delivery-status filters with Unsuccessful selected, Property set to All, Organization set to ChannelRUSH Demo, and the Created date range Example filters for unsuccessful delivery requests in one organization. The layout can place more fields on one row on wider screens. Check the result After Search, check the retained fields and the Filtered by chips above the table. Confirm the organization, property or selected-property restriction before interpreting any result. Changing a control without selecting Search does not apply the search. A request row establishes that a delivery attempt was recorded. It does not, by itself, establish that the PMS accepted the booking or that an email recipient read it. An empty table does not prove successful delivery. Use a filter chip's remove control to remove that criterion. Clear Search Filter removes the search criteria while keeping your application's property context. Recheck scope afterwards: clearing criteria is not the same as limiting the search to that top-bar property. When a link limits the property selection A link from another report can open this page with Limited to N selected properties. In that case, Property → All means all properties in that retained selection, not every accessible property. Search and paging retain the selection. Choosing a single property replaces it. Choosing another organization, removing the Properties filter chip, or using Clear Search Filter removes the retained selection. Review the resulting scope before continuing. Read a delivery request One reservation can have several delivery requests, including separate destinations and repeated attempts. Do not count rows as unique bookings. Display What it tells you Reservation ID / Status The channel reservation number and booking status, such as New , Modified or Canceled . Select the number to open that reservation version. This booking status is not the delivery outcome. Source channel and property The channel below the reservation identifies its source. The property name is shown for organization/multi-property users. Check both when comparing bookings with similar numbers. Delivered To The destination PMS/channel or email address. This heading names the destination; it does not mean the attempt succeeded. Status beneath the request The delivery-processing state described below. ID beneath the request This delivery request's identifier. Keep it when asking support to investigate. It is not necessarily the channel reservation number. Date/time beside the request ID When the delivery request was created, displayed in your user time zone. It is not the time processing finished. Error or receipt information Additional outcome information when recorded. Read it together with the destination and delivery status. Delivery-processing states - Pending: the request is awaiting processing or pickup. This is not delivery confirmation. - Processing: processing or pickup has begun, but the delivery may still be waiting for a receipt or confirmation. A pickup integration can retrieve a request before confirming it. - Successful: ChannelRUSH records a successful outcome for this request. Confirm the correct destination. Email success does not establish PMS delivery or prove that a person read the message. - Unsuccessful: ChannelRUSH records a failed attempt. Read the available error, receipt or logs and check for other attempts before deciding to send again. There is no universal completion time to infer from these states. If the destination still lacks the booking, investigate the request rather than treating its presence as acceptance. Paging Results normally list the newest delivery requests first, up to 50 requests per page. » opens older requests and « returns to newer requests when available. Paging retains the search filters. A full page can offer » even when the next page is empty; return to the previous page in that case. A Reservation ID search can return more than 50 matching requests. There is no overall matching total on this screen. Investigate without creating another delivery 1. Check the booking number, property, source channel and Delivered To destination. 2. Read the delivery Status and any accompanying message. 3. Open History to review reservation history, or select the reservation number to inspect the version associated with the request. 4. Open Logs, when shown, for request diagnostics. Log timestamps are UTC, unlike the user-time-zone creation timestamp on Delivery Status. A visible Logs link does not guarantee stored log entries are available. 5. For an email request, expand Delivery Receipt or Opened Receipt when present. Delivery Receipt can contain failure information as well as delivery information. An absent Opened Receipt does not prove the email was unread. 6. Search again with Delivery Status → All to check for newer or successful requests for the same booking and destination. Email and PMS open send forms; opening them is not a resend. PMS is available only where reservation sending is enabled for that property. Actions opens a separate channel-specific reservation-action workflow when supported; it is not a delivery retry control and can require additional permission or channel eligibility. If another send is necessary Do not send again merely because an old unsuccessful request remains visible. First confirm the booking's current state at the destination and resolve the reason for failure. If the previous outcome is uncertain, ask support before repeating it. The Email and PMS send forms use the latest reservation version, which can differ from the version behind the failed request. Submitting PMS → Send creates requests for all currently enabled PMS push/pickup destinations for that property, not only the failed row's destination. Submitting Email creates requests for the entered recipients; it does not repair PMS delivery. Repeated submissions can create additional requests. After an authorized send, return to Delivery Status, choose the property and reservation number, select All statuses, and select Search. Inspect the new request ID and correct destination. A newly queued request is not yet proof of destination acceptance, and a separate new send does not remove the earlier failed request. Continue to a related screen Go To Reservations Go To Reservations carries the selected single property, organization, channel, reservation ID and date/time window into the reservation search. It does not carry delivery status or delivery type. Recheck scope and dates on the destination page. A retained multi-property selection is not carried across, so the search can broaden. The date window now means Received, not delivery-request Created; the two times can differ. When Reservation ID is populated on the Reservations page, it searches by that ID within the permitted property/organization scope and ignores the other search filters, including Channel and Received dates. Clear Reservation ID if you want those filters to restrict the search. This differs from Delivery Status, where the other filters still apply. Check its applied filters and use its Search control after making changes rather than expecting identical results. Reservation Delivery Failures Report With Delivery Status → Unsuccessful applied, a Reservation Delivery Failures Report link appears when the selected scope can be represented by that report. It carries the applicable property selection and a lookback derived from the start date; with no start date, the lookback is 30 days. It does not carry the complete search: reservation ID, channel, delivery type, end date and times are not preserved. Check the report's criteria. Its Timestamp is the request's last-updated time, not the creation time shown here. Use the delivery-failures guide for that separate report. Search field reference Field Values and behavior Example Reservation ID Blank searches multiple bookings. Otherwise, matches the complete channel reservation number, ignoring surrounding spaces. Numeric input can also match an internal reservation-version ID or request ID. Other filters still apply. Not a PMS-confirmation search. Enter the number supplied by the booking channel; verify the source and property in the result. Delivery Status All , Pending , Processing , Successful , Unsuccessful . Filters the delivery request, not the booking's New/Modified/Canceled status. Use All when checking whether a later request succeeded. Channel All or a listed channel. Matches either source or destination. Select the PMS to narrow to requests involving that destination. Delivery Type All ; Email ; PMS - All for both PMS methods; PMS - Pickup / Confirm for pickup requests; PMS - Push for push requests. Use PMS - All before narrowing to a specific integration method. Property All or one accessible property. All remains limited by the organization, your access and any retained selected-property list. Select one property when the same channel reservation number could occur elsewhere. Organization Shown when more than one organization is offered. All remains within your authorized access. Choosing another organization clears the property selection. Select the organization before choosing its property. Created — left date and From time Optional start boundary in your user time zone. A date without a time starts at local midnight. A time without its date does not restrict the search. A start date with 09:30 includes requests from that minute onward. Created — right date and To time Optional end boundary in your user time zone. A date without a time includes the whole final local day. An end time includes the whole specified final minute. A time without its date does not restrict the search. An end time of 17:00 includes that minute, not only exactly 17:00:00. Leave both dates blank for no creation-date restriction. You can use only a start or only an end date. Use the date format shown by your account's picker and check the retained value after Search. The help text under Created identifies the time zone. Common problems - No results: the current combination of scope, ID, delivery type, status and creation dates may exclude the request. Check the property and channel reservation number, select All statuses, and remove unnecessary restrictions before searching again. An empty list is not proof of successful delivery. Escalate if an expected request remains absent. - “The End Date cannot be before the Start Date.”: correct the Created boundaries, including times on the same date, then select Search. A Reservation ID does not bypass this validation or the other filters. - A typed date did not remain after Search: re-enter it in the displayed format, move out of the field, then search and check the retained date. Do not interpret results using a date that did not apply. - Property shows All but fewer properties are included: check for Limited to N selected properties and the Properties chip. Remove that restriction only when you intend to broaden the search. Missing access cannot be overridden with a filter. - The adjacent report shows different results: compare its property selection, time window and timestamp meaning. Go To Reservations and Reservation Delivery Failures Report do not preserve every criterion. - PMS, Logs or a receipt link is missing: availability depends on configuration, request state and recorded diagnostic/receipt information. Use the available history and ask your Org Admin or support when the expected path is unavailable. Do not infer success or failure from a missing link alone. - The booking is still missing, or the outcome is uncertain: provide support with the property, source channel, channel reservation number, destination, delivery-request ID, status/error text and action time with time zone. Do not send passwords, payment details or unnecessary guest information. Avoid another send until its scope and duplicate risk are understood. Related - Check delivery status for one property - Investigate reservation delivery failures - Find reservations and open their send forms
Compare reservation metrics across properties
Select properties, stay dates and a reservation feed, then read or export daily room-type metrics with the correct meaning for each figure. Before you start If you opened Excel from a single property’s report, use Read reservation metrics for a property for that entry path. The spreadsheet and CSV guidance below applies to both entry paths; Org Admin access is needed only for the organization selection described here. You need access to the properties you want to include. The Org Admin menu is available to Org Admin users and users with access to multiple properties. The report lists properties available to your account; the property selected in the application header does not replace the report's Properties selection. This is a whole-stay report, not revenue limited to the selected nights. It finds captured active reservations whose stays intersect your date range, then includes their supplied nightly rows—even nights outside that range. It uses mapped room types and skips room stays it cannot map. Confirm the currency and price basis before comparing money. The report does not show currency codes or convert amounts. Rows can combine prices from different feeds. Do not add or compare amounts unless you know they share the same currency and price basis. Running the report or downloading CSV does not change reservations, update inventory or resend anything. Choose the scope and open the report 1. Open Org Admin → Reports. 2. Under Reservations, select Reservations - Metrics. 3. Set Date Range using the start and end dates. Alternatively, select a month in Month / Year to use that whole month. 4. Choose a Channel, or leave All to combine captured feeds. 5. Under Properties, check each property to include. 6. Check the selected-property count and date summary beneath the controls. 7. Select List to open the table in a new tab, or Excel to open the spreadsheet view in a new tab. Date Range controls with a Month / Year shortcut and separate start and end dates Use the month shortcut for a calendar month, or choose your own start and end dates. The checkbox beside Properties selects the whole list when it is not fully selected; when everything is selected, it clears the list. At least one property must remain selected before you run the report. Changing a selection does not refresh a report tab that is already open—run List or Excel again. Selection field reference Control What it does Default or requirement Date Range Selects stays intersecting the start/end interval. This is not a booking-created-date filter. Both dates are required; the end must not precede the start. Without supplied dates, the initial range runs from today through 28 days later, based on the current property's local date. Month / Year Replaces the date range with the first and last day of the selected month. Optional shortcut, not a second independent filter. Channel Restricts the reservation feed used for the report. All combines feeds. A feed is not necessarily the reservation's original sales source. Properties Selects the properties included in the output. Initially all available properties are selected unless you arrive with an existing selection. Select at least one. List Opens the HTML table using the current selections. Opens a separate tab/window. Excel Opens an embedded spreadsheet using the current selections. This opens a view, not an immediate workbook download. CSV Downloads the report data using the current selections. Does not require opening List or Excel first. Cancel Returns to the organization Reports page. Does not change reservations. Understand the results The output is headed Reservations - N. The number counts the matching captured reservations loaded before room-mapping omissions. It is not the number of table rows, room stays, arrivals or room nights. In List view, check the statement beginning Selected stay dates, the Properties IDs and Reservation feed above the table. The smaller heading may show the current application property; use the explicit property IDs and row Property ID / Property Name columns to confirm the report's scope. Each row groups one property, one nightly date and one mapped property room type. Rate plans are combined. With All, channels are combined too, so Channel ID and Channel Name are blank. Selecting a specific channel fills those columns. Which reservations and nights are included? - Normal report selections use the latest captured version of each reservation with status New or Modified, rather than cancellation activity. Archived reservations are not automatically excluded. - The stay comparison includes both boundaries, including departure day. A reservation departing on the selected start date can qualify. - Once a reservation qualifies, the report processes its mapped room stays and all supplied nightly price rows. It does not trim the nights to your selected dates, and a multi-room reservation can contribute other room stays as well. - Missing channel settings or room mappings can leave a reservation out of the metrics even though it contributes to the heading's reservation count. - The report also supplies zero rows for configured room types on selected dates with no mapped nightly data. Zero does not establish that no bookings exist. The report does not expose price coverage, its run timestamp or the latest feed update. A freshly opened page is not proof that every channel's reservation data is current. On-screen column reference Column Meaning and how to read it Property ID ChannelRUSH property identifier for the row. Property Name Name of that property. Channel ID Selected feed's identifier. Blank when All is selected. Channel Name Selected feed's name. Blank when feeds are combined. Date Date of the supplied nightly row, or the selected date for a zero-filled row. It can fall outside your chosen interval when it belongs to a matching stay. Room Type ID Mapped property room-type identifier—not the channel's room code. Room Type Name Name of that property room type. Total Allocation Count of mapped nightly price rows. This is not available inventory, an occupancy percentage or a reservation count. Total Arrivals Room stays counted on their first supplied nightly date. One multi-room reservation can contribute more than one arrival. Total Revenue Sum of supplied nightly prices. The report does not separately add reservation-level totals, taxes, fees or add-ons; the supplied prices retain their own basis. Total ADR Total Revenue divided by Total Allocation, rounded to two decimal places. A zero-filled row displays zero; that is not evidence of a zero-price booking. ALOS Average length of stay: supplied nightly-row count per arriving room stay, rounded to one decimal. It is calculated on arrival rows only. Missing nightly data can make this differ from departure date minus arrival date. Zero can mean no arrivals. ADTA Average days to arrival: days from the selected reservation version's receipt date to its first supplied night, averaged over arriving room stays and rounded to a whole day. It is not necessarily lead time from the original booking. Zero can mean no arrivals or a rounded zero-day average. ADTA does not adjust the receipt date into your selected property's local timezone before this calculation. Use reservation details when you need to investigate an individual booking's timing. Use Excel and download files Spreadsheet view Excel opens a read-only spreadsheet. Its field names are compact—for example, TotalAllocation rather than Total Allocation—but the metric meanings are the same. To change its dates or channel: 1. Open Filters. 2. Change the date range or Channel. 3. Select View Report. 4. Check that the reloaded heading, filters and rows match your choice. The spreadsheet retains the original property selection. For an organization report, return to the original organization criteria tab to change properties, then run the report again. For a single-property report, select HTML to return to that property’s metrics page. Output/download controls use the loaded criteria, not unsubmitted edits in Filters. Use File → Save As to download a workbook, or File → Print to print the spreadsheet. Saving a workbook does not save changes to reservations. Do not use linked dates in the spreadsheet to open reservation details; use Reservations → Search instead. CSV download 1. On the organization criteria page, choose the dates, channel and properties. 2. Select CSV under Download. 3. Open the downloaded file and confirm its property IDs, dates and headers. You can also use CSV under Download on an opened result to export that result's loaded selection. The CSV header order is: PropertyId,PropertyName,ChannelId,ChannelName,Date,RoomTypeId,RoomTypeName,Total Allocation,Total Arrivals,Total Revenue,Total ADR,ALOS,ADTA CSV dates use yyyy-MM-dd; numeric values use a decimal point. Blank ChannelId/ChannelName under All and zero-filled metrics have the same meanings as in List view. There is no currency column. The exported dates can extend beyond the selected interval for the same whole-stay reason as the on-screen report. Check the result 1. In List view, confirm Selected stay dates, Properties and Reservation feed. 2. Locate a representative property, room type and date in the table. 3. Compare that same row in your CSV or spreadsheet, rather than comparing the reservation heading count with the file's row count. 4. If a known booking is missing or totals look wrong, check the property, captured feed, stay overlap and room mapping before drawing a conclusion. 5. To investigate a booking, open Reservations → Search for its property, enter the reservation criteria and select Search. Review the correct reservation version and its room/nightly information. A completed report confirms that ChannelRUSH produced that view of stored data. It does not confirm successful reservation delivery, complete price coverage or agreement with a channel's own financial statement. Common problems Symptom Likely explanation Safe next action Org Admin or a property is missing Your account may not have the required role or property access. Ask your organization administrator to confirm access. Contact support if the expected access is already assigned. List/Excel/CSV is unavailable Dates are incomplete or reversed, or no property is selected. Choose valid dates and check at least one property. If a date error remains, reselect the range with the picker rather than repeatedly submitting malformed text. List or Excel appears to do nothing The browser may have blocked the new tab, or page scripts did not complete. Check open tabs and allow popups for ChannelRUSH, then run the report again. If it still fails, capture the non-sensitive error text and contact support. Reservations - 0, or rows contain zeros No matching captured reservations or no mapped nightly data is represented for that scope. Recheck dates, feed and properties. Compare a known reservation and its mapping; do not treat zeros as proof of no bookings or successful delivery. A row's date is outside the selected range Matching reservations contribute whole-stay nightly rows. Use the date column to identify the nights included. Do not describe the untrimmed export total as revenue only within the selected interval. Reservation count differs from arrivals or allocation They count different units; unmapped room stays can also be omitted. Use the column reference before reconciling. Escalate with a representative property, room type, date and non-sensitive discrepancy if the difference remains unexplained. Excel dates look like reservation links The spreadsheet can display dates as links that do not identify a valid reservation. Do not use those links for investigation. Use Reservations → Search , then Search , or use the List/CSV output. Export fails or the dataset is too large The requested output may exceed what the export can generate. Reduce the date range or property selection and try again. If a small report also fails, contact support with the selected scope, format, action time/timezone and error text. Repeated report runs and downloads are observational. Do not resend or modify a reservation to make this report reconcile. Never send passwords, payment details or unnecessary guest information with a support request. Related - Review reservation details
Read and export reservations across properties
Choose properties, dates and reservation filters, then inspect captured reservations or download them for operational reconciliation. Before you start You need access to the properties you want to include. Open Org Admin → Reports → Reservations. The properties offered depend on your account's access. If you cannot see the menu or a required property, ask your organization administrator to check your access. The property in the application header supplies the page context. It does not replace the Properties selection in this report. This report shows the latest captured version of each reservation, not every change in its history or a snapshot as of a past date. New, Modified and Canceled describe reservation versions—not delivery success. Viewing and downloading the report does not change reservations or resend them. Reports and exports may contain booked-by names and confirmation numbers. Share them only with authorized recipients. Choose the properties and run the report 1. Open Org Admin → Reports → Reservations. 2. Set the start and end under Date Range. Use Month / Year to select a calendar month, or enter the dates you need. Check both dates before continuing. 3. Choose Booking Date Range, Arrival Date, Departure Date or Stay Date. Their meanings are explained below. 4. Choose a Channel, or leave All selected. 5. Choose a Status, or leave All selected to include New, Modified and Canceled versions. 6. In Properties, tick the properties to include. Use the checkbox beside the section heading to select or clear the list, then check the selected count. At least one property is required. Select no more than 200 properties for List. 7. Choose an output: - Under View, click List to open List & Export in another tab. - Under View, click Excel to open the spreadsheet view in another tab. - Under Download, click CSV to download the criteria page's CSV file. The original criteria page remains available when List or Excel opens. Cancel leaves the criteria page without running a report. Org Admin Reservations date range, date type, Channel and Status controls The top criteria section. Choose the properties below it before running a report. On a fresh page, the dates start at the context property's current local date and end 28 days later. Booking Date Range, Channel: All and Status: All are initially selected, and all offered properties are checked. Recheck these choices whenever you start a new report. Understand the date and status filters Control What it selects Important distinction Booking Date Range Receipt time of the latest captured reservation version. List calls this Booking date . It is not necessarily the original booking/sale date. A later modification can move the booking out of an earlier receipt-date report. Arrival Date Reservations with a room arrival in the selected date range. The reservation's displayed dates can cover additional rooms outside that range. Departure Date Reservations with a room departure in the selected date range. This is not a filter for occupied nights. Stay Date Reservations whose room date ranges overlap the selected dates. List calls this Stay overlap (checkout included) . Checkout is included. Records with incomplete room-date boundaries can also appear. This is not a room-night occupancy calculation. Channel The recorded reservation feed/channel. All removes channel narrowing. The criteria page offers channels across the properties available to you, including properties you have not checked. A choice need not have reservations in your selected properties. Status The latest captured version's New, Modified or Canceled state. All includes all three. A prior matching version is not restored when a newer version has a different status or falls outside your dates. Properties The checked properties. Clearing the list means no valid selection, not “all properties.” The selected dates determine which reservations qualify. They do not clip a reservation's dates, nights or monetary totals to that period. For receipt-date reconciliation, keep the output path consistent. List and the separate Excel/criteria CSV path handle date boundaries and displayed timestamps differently. They are not interchangeable accounting extracts. If a boundary reservation appears in one output but not another, retain both report selections and ask support to check the receipt-time boundaries rather than treating the difference as a missing booking. Work with List & Export Check the result Confirm the date basis, date range and matching-reservation count above the table. Open Filters to confirm the properties, channels and statuses. The list contains captured reservations only; neither a populated list nor zero matches proves that all bookings were received or delivered. Click a reservation's Confirmation link to open its details. Check the property as well as the confirmation number when investigating a record. For the individual detail fields, see Review reservation details. Change the report selection 1. Open Filters. 2. Change the dates or Date basis as needed. 3. Adjust Channels and Status. 4. Click Update report. 5. Check the resulting date basis, dates, count and rows before downloading. The List screen shows the selected properties but does not provide a replacement property picker. Return to the original Org Admin criteria page to change the properties and run List again. In List's checklists, keep at least one Status selected and at least one Channel when channels are offered. Checking every item removes narrowing for that list; clearing a required list prevents Update report. A property with no offered inventory channels can still have captured reservations from other feeds. A retained Recorded channel entry means the report URL names a channel that is no longer in the offered list; it remains a filter until you change the selection. Reset report retains the property/context selection but clears dates and other report/table choices. Select dates again before running. If an old link shows No date filter — the dates above are ignored, choose a date basis and click Update report; displayed dates alone do not establish that filtering is active. Narrow or arrange the table Open Table filters and sorting. Choose a sort column and direction, an optional Add filter field with Operator and Value, a Property/channel search, and the number of Rows. Click Apply table. - Property/channel search searches property and channel names, not guest names or confirmation numbers. Use a Confirmation or PMS confirmation column filter for those identifiers. - Internal ID, Property ID and Channel ID support Equals or Does not equal, with a positive whole-number value. Status supports the same two operators, with New, Modified or Canceled. - Confirmation, PMS confirmation, Property, Channel and Currency also support Contains. - Dates, amounts, stay nights and receipt timestamps support equality, inequality and range comparisons. The Operator list can show choices that are invalid for the selected field; choose from the supported combinations above. - Enter date filter values as YYYY-MM-DD. Use decimal-point numbers without grouping separators, such as 1250.50. Receipt-time filters require an explicit offset, for example 2026-10-21T12:00:00Z. - Booked by and Single rate plan cannot be filtered or sorted. - Additional table filters combine with AND: a row must satisfy every filter. Up to ten filters and three grid sorts are supported; search is limited to 100 characters and each filter value to 128 characters. Reset table clears table filtering, search, sorting and paging while retaining the report's properties, dates, channels and statuses. - The table form applies one sort column. Applying it replaces a multi-column sort previously chosen in the grid. - Rows offers 25, 50 or 100; the initial page size is 100. Paging limits what is on screen, not the full matching export. - Use Columns to show or hide table columns. Columns can also be resized and reordered. Density changes between Comfortable and Compact. These presentation choices do not remove fields from the default downloads. If an update fails, do not treat the old visible rows as the result of your pending changes. Check the error and retained filters. Retry, when offered, retries report retrieval; it does not resend a reservation. Download from List 1. Open Download. 2. Choose the required scope and format: - Full report CSV or Full report XLSX includes the report's selected properties, dates, channels and statuses, ignoring additional table search, filters and sorting. - Matching table CSV or Matching table XLSX keeps the table constraints and sort order. It includes all matching rows, not only the current page. 3. Check the downloaded file's headers and scope before using it. XLSX files include a Context sheet and reservation data sheets. The Context sheet records the selection, scope, row count, date basis and extraction information. CSV uses the fields described below instead of a separate Context sheet. Downloads retrieve the data again. A new reservation version arriving between viewing and downloading can change the result. New window opens the committed report selection in another tab. Use the separate Excel view and criteria CSV Excel on the original criteria page opens a spreadsheet viewer. It is not the same output as Full report XLSX in List's Download menu. - Open Filters to change the date range, date type, channel or status, then click View Report. The selected property list is retained. - HTML opens List for the current selection. CSV downloads the spreadsheet path's CSV schema. - The spreadsheet exposes a File menu with Save As and Print controls. Downloaded files and printed pages contain reservation data; handle them as confidential operational records. - This is a report viewer, not a reservation editor. Return to the original Org Admin criteria page to choose different properties. Prefer List's exports when you need explicit currency, internal version identity and UTC receipt/extraction fields. The separate spreadsheet and its CSV omit currency. Do not sum their amounts across properties or channels unless you have independently established a common currency and price basis. The spreadsheet's BookingDate displays the source's edit timestamp when available, otherwise the version's receipt timestamp. Its Timestamp is the version receipt timestamp. Both are displayed using the property selected in the application header, even in a multi-property report. These display fields do not redefine the Booking Date Range filter. List column reference Column Meaning and limits Confirmation The channel's reservation identifier; links to the captured reservation details. Booked by The supplied booked-by name. It is not necessarily every guest staying. Blank means no usable name is shown. Property / Property ID Property name and ChannelRUSH property identity. Channel / Channel ID Recorded feed/channel name and ChannelRUSH channel identity. Status New, Modified or Canceled for this captured version; not a delivery state. Arrival / Departure Whole-reservation date boundaries. A qualifying room can have different dates from these overall boundaries. Blank dates remain unknown. Stay nights Difference between the reservation's overall date boundaries, not summed room-nights or nights clipped to the report range. Missing endpoints can produce zero; zero is not proof of a zero-night stay. Currency Supplied currency. Missing currency is unknown; amounts are not converted to a common currency. Before tax / After tax Captured source totals on their respective tax bases. Blank means unavailable, not zero. Neither figure establishes accounting revenue or completeness. Version receipt UTC When ChannelRUSH received this version, displayed in UTC; not necessarily the original booking time. Internal ID ChannelRUSH's identifier for this reservation version. PMS confirmation Captured PMS confirmation when supplied. Its presence alone does not prove current delivery success. Single rate plan One channel rate-plan ID when the room stays resolve to a single plan; blank can mean multiple or missing plans. If the interactive grid cannot initialize, the fallback table combines these into Confirmation / status, Booked by, Property / channel, Arrival → departure, Stay nights, Amount / currency, and Version receipt UTC. The combined amount uses the applicable tax basis; it does not fill a missing amount by substituting the other total. Export field reference List CSV and XLSX The default headers, in order, are: contract,propertyId,propertyName,channelId,channelName,reservationId,confirmation,pmsConfirmation,guestName,ratePlan,status,currency,totalBeforeTax,totalAfterTax,arrival,departure,nights,receiptUtc,sourceEditedUtc,extractedUtc,dateBasis Field Meaning contract Export schema identifier, reservations-v1 . propertyId / propertyName Property identity and name. channelId / channelName Recorded channel identity and name. reservationId Internal ChannelRUSH version ID , not the channel confirmation. confirmation Channel reservation identifier. pmsConfirmation Captured PMS identifier, or blank if unavailable. guestName Booked-by name, or blank. ratePlan Single channel rate-plan identifier when available; not an inventory rate. status Captured version's New, Modified or Canceled state. currency Source currency; no currency conversion. totalBeforeTax / totalAfterTax Source totals; unavailable amounts remain blank. arrival / departure Whole-reservation date boundaries, formatted as dates. nights Whole-reservation date-envelope nights; missing endpoints can produce zero. receiptUtc Version receipt timestamp in UTC. sourceEditedUtc Source edit timestamp in UTC when supplied; otherwise blank. It is not replaced with receipt time. extractedUtc Time of this extraction, not a vendor response or delivery timestamp. dateBasis Meaning of the date filter used for the report. IDs are exported as text. CSV numbers use invariant decimal notation and dates use YYYY-MM-DD; UTC timestamp fields include their UTC offset. Formula-like text can have a protective leading apostrophe in CSV. Treat an identifier as text when importing it into other software. Criteria/Excel CSV and spreadsheet columns The CSV downloaded from the original criteria page or the Excel view has these headers, in order: PropertyId,PropertyName,ChannelId,ChannelName,ReservationId,ReservationIdPms,Status,Info,TotalBeforeTax,TotalAfterTax,NumNights,ArrivalDate,DepartureDate,BookingDate,Timestamp Field Meaning or difference from List exports PropertyId / PropertyName Property identity and name. ChannelId / ChannelName Recorded channel identity and name. ReservationId Channel confirmation , unlike List's reservationId . ReservationIdPms Captured PMS confirmation. Status Captured reservation-version status. Info Booked-by name, not a general diagnostic message. TotalBeforeTax / TotalAfterTax Source totals displayed to two decimal places; missing values are blank. Currency is not included. NumNights Whole-reservation date-envelope nights. ArrivalDate / DepartureDate Overall dates; CSV normalizes these to YYYY-MM-DD . BookingDate Source edit timestamp if available, otherwise version receipt; not necessarily the booking's original creation time. Timestamp Version receipt timestamp. The spreadsheet adds ReservationRatePlanId between ReservationIdPms and Status. That field identifies a single rate plan when available and is not included in this CSV. Spreadsheet date display follows the application's culture; CSV timestamp fields retain an explicit offset. This CSV has no internal version ID, currency, extraction time, contract or date-basis field. Common problems - List, Excel or CSV is unavailable: check that both dates are valid, the end is not before the start, and at least one property is checked. A property-selection error means you must choose a property; it does not mean the report is empty. If the controls still do not run, check browser popup blocking for List/Excel and contact support with the error and selection. - A property is missing or access is rejected: return to the criteria page and choose properties currently available to you. Ask your administrator to check access if a required property is absent. Do not edit property IDs in a URL to work around it. - Too many properties selected: run List with no more than 200 selected properties, dividing a larger portfolio into separate reports. - Zero matches: check the property selection, date basis, dates, channel and status. In List, try Reset table to remove additional table narrowing. A receipt-date report can exclude an older version after a newer version arrives. Zero matches does not prove there were no bookings or that delivery succeeded. - A file contains more rows than the visible table: check whether you selected Full report instead of Matching table. Matching table still exports all matching pages. Compare the recorded selection before assuming a scope error. - List and Excel/CSV differ: first check their date basis, channels, status and properties. Then check receipt-time boundaries and the different identifier/timestamp meanings above. Do not merge columns based only on similar header names. - A report update fails but rows remain visible: those may be the last successful results. Review the error and filters, then retry the read or reload the page. Do not use those rows as confirmation of a new selection. - An amount, date or PMS confirmation is blank: the captured record does not supply a usable value in that field. Do not replace it with zero or infer successful delivery. Open the reservation details and use the relevant delivery-status screen when delivery is the question. If the result remains unexplained, give support the selected properties, date basis and range, channel/status filters, output choice, action time and timezone, and the error text. Include a confirmation number only when needed to identify the affected reservation. Do not send passwords, payment details or unnecessary guest information. Related guides - Review reservation details - Check reservation delivery across properties - Compare reservation metrics across properties
Check inventory-report request status across properties
Use Report Status to find properties and channels with pending or unsuccessful inventory-report requests, then open the matching requests for investigation. These are requests to retrieve inventory information. They are not outbound rate or availability updates, reservation deliveries, or scheduled email reports. Refreshing this screen reloads stored request counts; it does not ask a channel for new inventory. Before you start - Sign in to the correct organization and select a property you can access. - This portfolio report requires organization-administrator access in a distributor or PMS Connect partner organization. Being an administrator of an ordinary property organization alone does not provide this access. If the report is refused, ask your organization administrator or ChannelRUSH support to confirm your account's scope. - The property selected in the application header provides navigation context. It does not restrict this report to that property: the report covers eligible properties in your organization's distributor portfolio. Open and filter the report 1. Open Org Admin. 2. Open Reports. 3. Under Inventory, select Report Status. 4. Choose a Status. The initial selection is Unsuccessful. 5. Choose a Channel, or leave Select ... to avoid narrowing by channel. 6. Click Refresh. Check that the status heading above the table matches your selection. Changing a dropdown without clicking Refresh does not reload the results. Report Status filters showing Failed, Booking.com and the Refresh button Choose the status and channel, then click Refresh. The example shows filter controls, not evidence of a failed request. Read the results Each row represents one organization, property and channel combination. Rows with the largest request counts appear first. Column What it means # Number of matching inventory-report requests for that combination. It is not the number of properties, inventory dates, rooms or processing attempts. Channel The channel associated with those requests. Select its name for the narrowest request investigation. Hotel The property. Select its name to inspect requests for that property across channels. Org The property's organization. Select its name to inspect requests across that organization. The report includes matching unarchived requests for active properties and active organizations with an existing property/channel connection. It does not apply a date window, so older retained requests can contribute to the count. It is not a daily total or a complete historical archive. There is no date filter, export control or automatic retry on this page. Use the request details screen when you need date filters or an individual request's message. Status reference Status Meaning and next check Pending The request is awaiting processing. Open its details to review when it was created and its recorded state. Processing The request is recorded as being processed. This does not confirm completion or establish a completion deadline. Unsuccessful Processing did not succeed. Read the request's available status message before deciding what to correct. Failed Processing encountered an error. Review the available message and involve support when the cause or recovery action is unclear. Unsuccessful and Failed are separate selections here. Selecting Unsuccessful does not include Failed. Check both when investigating problems. The label alone does not establish whether the cause is configuration, a connection problem or something requiring support. This summary does not offer Successful or All. An empty table means no requests match this summary's current status, channel and scope. It does not prove that inventory was retrieved successfully, that the channel has current inventory, or that an earlier problem was resolved. Investigate a matching request 1. Select the row's Channel name. The request list opens in a new tab, leaving the summary available. 2. Confirm that the page is Report Requests - Processing Status. 3. Check Property, Organization when shown, Status and Channel before interpreting the results. 4. If you need to narrow the list, choose the relevant filters and click Search. 5. Review the matching request's ID, covered dates, status and available message. Record the property, channel and request ID before contacting support. The summary's links deliberately carry different scopes: Link you select Scope opened in the request list Channel That organization, property, channel and status. Hotel That organization, property and status; the channel restriction is removed. Org That organization and status; both property and channel restrictions are removed. Consequently, a Hotel or Org link can show more requests than the row's # count. The request list also has broader search options than the summary. Check its selected filters rather than assuming every total is directly comparable. Counts can change while requests are processed. Useful investigation filters - Status: The request list also offers Successful and All. Choose the state you need, then click Search. The summary's Unsuccessful and Failed selections remain distinct on this list. - Stay Dates: Narrow by the inventory dates covered by the request. These are not its creation or processing timestamps. - Date and Time: Choose Created or Last Run and enter the relevant range. The page states your time zone. Without a time, a selected day includes the whole day. - Request ID: Find a known request within your accessible scope. An exact ID takes precedence over ordinary status, channel and date restrictions; check the returned request's identity rather than relying on those other filter values. - Room Type, Rate Plan and Requested By: Narrow the request list when the available choices match your investigation. Use Search, not Go, to apply filters. Go belongs to request actions such as retrying or archiving. Those actions are separate from reviewing the report; do not use them merely to refresh the screen or make a count disappear. The request list's Created timestamp identifies request creation. Last Run is the recorded request-update timestamp and can change with status changes; it is not proof that a channel retrieval completed. An Attempts value is also not proof of that many completed channel calls. This summary excludes archived requests. The request list has an Include Archived Reports option, but archived records are outside the summary's counts. If you investigate archived history, recheck the checkbox and returned scope after every search or page change; do not assume it remains selected. Check the result After Refresh, confirm the retained filters and the status heading. If rows appear, use the Channel link to inspect the narrowest matching request list. After changing that list's filters, click Search and check the Filtered by labels and the results together. A pending or processing request is not a completed retrieval. An unsuccessful or failed record is evidence of that recorded outcome, not a diagnosis by itself. A row disappearing from this summary is not proof of recovery: its status, archive state, property eligibility or connection may have changed. Do not treat a successful inventory-report request as proof that a separate outbound inventory update or reservation delivery succeeded. Investigate those workflows in their own status pages. Common problems The report link is visible, but access is refused The Reports menu can expose the link even when your account does not have the required distributor-portfolio access. Confirm the signed-in organization and ask your organization administrator or support to check your access. Do not switch to an unrelated organization to work around the restriction. The table is empty Check the selected Status and Channel, then click Refresh. Clear the channel selection back to Select ... when you want all matching channels, and check Unsuccessful and Failed separately. Archived requests and inactive properties or organizations are excluded. If you expected a particular request, investigate its ID in the request list or ask support; an empty summary is not a success confirmation. A channel is missing from the dropdown The available choices depend on your organization's channel configuration. A missing choice does not prove that no report requests exist for that channel. Leave Select ... and refresh, or ask support to check the connection and request scope. Do not add or change a channel connection solely to populate this dropdown. Counts differ after opening a row Check which link you used. Hotel removes the channel restriction; Org removes both property and channel restrictions. Also check the request list's status, dates and archive selection. Requests may have changed state between the two page loads. Escalate with the summary filters and a specific request ID if a difference remains unexplained. A request stays pending, processing, unsuccessful or failed Refresh the summary and inspect the request's recorded status and message. This page does not give a processing-time guarantee or establish that retrying is safe. If the message does not make the next action clear, contact support with the organization, property, channel, request ID, affected inventory dates, observation time/time zone and error text. Do not include passwords, payment details or unrelated guest information. Related - Check inventory update status across properties — for outbound inventory updates rather than report-retrieval requests. - Investigate inventory update requests across properties — for the separate update-request investigation workflow.
Investigate inventory-report requests across properties
Use Report Requests - Processing Status to find an inventory-report request, understand its current processing state, and decide whether to investigate, retry or archive it. These requests retrieve inventory information. They are not outbound rate or availability updates, reservation deliveries, or scheduled email reports. Search reloads stored request information. Go performs the chosen action; it is not another search button. Before you start - Sign in to the correct organization with access to the properties you need. The Org Admin navigation path below requires organization-administrator access. A directly shared request-status link still checks your authorized property scope. - The property in the application header is navigation context. Use Property in Search Filters to restrict this list to one property; do not assume the header selection does that for you. - Retry, archive and unarchive require permission to update at least one of rates, availability or restrictions. Ask your administrator if an action is refused. Public demonstration sessions can search but cannot perform these actions or submit support email. Find the requests 1. Open Org Admin → Home. 2. In the Channel Manager section, select Report Status. Check that the page title is Report Requests - Processing Status. 3. Choose Organization, if offered, and then Property. Leave unrelated filters at All for the first search. 4. Select Search. Choosing a property and searching loads that property's Room Type, Rate Plan and Channel choices. 5. Narrow the search using Status, Channel, the product fields, Requested By, or the date filters described below. 6. Select Search again to apply your changes. Inventory-report request Search Filters for a demo property, showing Failed, Booking.com, product filters, archive inclusion, stay dates and request timestamps The filter form in a narrower browser window. The example searches one demo property; it does not show a failed request or a completed retry. Review the applied Filtered by labels and the request rows before acting. Changing Organization clears the Property selection; changing Property clears Room Type and Rate Plan. Search again before selecting dependent product filters. Clear Search Filter removes the explicit search criteria; check the resulting scope and select Search when you are ready. It does not clear or delete requests. Go To Update Status opens the separate outbound-update screen. It does not carry this search across unchanged and does not show the result of a report retry. Find one known request Enter its numeric Request ID, choose the correct Property, and select Search. Request ID takes precedence over the ordinary status, channel, product, user, archive and date filters, but it does not bypass property access. You can use it to find an archived request without relying on the archive checkbox. Correct any date-order errors before taking an action, even when searching by ID. Understand the results Requests are listed newest ID first, normally 50 at a time. Use the previous/next arrows for other pages. The header checkbox selects only the requests on the displayed page, not all matching requests. A next-page arrow can lead to an empty page at the end; return to the previous page rather than treating that as a new processing outcome. The table's Hotel / Channel column identifies the property, channel and available room/rate-plan details. Channel and product links open channel settings. VRT identifies a virtual room-type mapping. Dates is the inventory date range requested, not when the request was created or processed. Each request also provides: Detail How to read it Status The processing state described below. Read the message beneath the request as well. Attempts Recorded processing attempts. Clicking Retry does not immediately increment this number. User name and ID, or API The recorded requesting user. API appears when no user is recorded; it does not identify a particular external application. ARCHIVED Hidden from ordinary searches unless included explicitly. Archiving does not resolve the underlying issue. ID The request identifier to keep for investigation and support. A retry reuses this ID. Created When the request record was created. Last Run The request's recorded last-update time. It can already be populated on a Pending request with zero attempts, and is not necessarily a channel-response or completion time. Message beneath the request Recorded processing information or an error. Preserve it before retrying because later processing can replace it. Created and Last Run use your signed-in timezone, also shown beside the date filters. A blank product name or [BLANK / NOT SET] is a reason to inspect the mapping, not proof of the request's processing outcome. This page has no request-delete or export action. Processing states Status Meaning and safe next step Pending Waiting for processing. Search again to check progress; do not repeatedly retry it. Processing Work is in progress. A processing timestamp is not completion. Preserve the request ID and contact support if progress cannot be established. Successful The request was recorded as processed successfully. This alone does not prove a fresh live channel read, matching inventory values, or that every retrieved inventory image was saved. Check the relevant inventory report when investigating values. Unsuccessful The operation did not complete as required. Read the message and review the named setup, mapping or date issue with an authorized administrator before retrying. Failed Processing recorded a failure. Preserve the message and request details for investigation; the label alone does not establish who can fix it or whether nothing happened. Unsuccessful and Failed are separate selections on this page. Search each when investigating both kinds of problem. Pending, Unsuccessful and Failed counters Some filtered searches show these three counters above the list. They count each status separately, exclude archived requests, and retain the other applicable search restrictions. They are not totals for the currently displayed page or a breakdown of every status. They may appear after choosing Channel and Status even when no requests match. The number in parentheses ending in p represents pages at the current page size, not a percentage or estimated processing time. Large counts are capped and displayed with +. For an exact Request ID search, rely on the row's Status rather than these counters: the ID overrides their status restrictions. Correct date errors before interpreting any counts. Retry only after investigating A retry is real processing, not a refresh. It can retrieve inventory and update stored report images. It is not an outbound rate update, and it does not guarantee that the original historical date span will be processed unchanged. 1. Record the request ID, property, channel, Dates, Status, Attempts, Last Run and message. 2. Resolve the cause with an authorized administrator or support, and confirm the request is still needed. Do not retry requests already Pending or Processing. 3. Apply the intended filters with Search and select the intended request checkboxes. 4. Choose Retry in the action selector. 5. Select the adjacent Go. 6. Search for the same Request ID to follow its progress. The confirmation means the selected requests were marked for retry, not completed. Retry sets them to Pending and removes their archived flag. Their old message, attempt count and Last Run can remain visible until processing updates the record. A Failed or Unsuccessful filter can hide a request as soon as it becomes Pending or Successful; disappearance from that list is not a success check. Use Retry All only when you intend to affect every matching request, including other pages. Select a specific Property, Channel and Status, apply Search, review the scope, then choose Retry All and Go. All three selections are required, even if an error message suggests Property or Status is optional. Changes to filters after Search can change the scope used by an All action. Do not use it when the scope is unclear. Archive and unarchive Archiving is shared request housekeeping, not a personal dismissal. It hides requests from ordinary searches; it does not delete them, fix their errors, or cancel Pending/Processing work. Work already eligible for processing may continue and become visible again. To archive reviewed requests, apply Search, select their checkboxes, choose Archive, and select Go. Confirm the banner, then search an individual Request ID if you need to check its ARCHIVED marker. Do not interpret an empty ordinary search as successful processing. To restore a known archived request, search its Request ID within the correct property, select it, choose Unarchive, and select Go. This restores ordinary visibility. It is not an immediate manual retry, but it can make a recent failed request eligible for automatic retry again. Confirm that renewed processing is wanted before unarchiving. Include Archived Reports is a viewing option: it includes archived and unarchived requests, not archived requests alone. It does not unarchive anything. There is a current limitation: after some searches the checkbox clears and the applied-filter labels omit it. Check it again before another archive-inclusive Search, and do not assume paging retains it. Use a known Request ID for reliable individual investigation; contact support if you need a complete archived list. Archive All and Unarchive All target all matching requests, not the checked rows. They require a single property and channel, but the current screen can still reject them after those selections. Use selected-row Archive or Unarchive instead of broadening the scope or repeatedly submitting an All action. Escalate the contradictory validation if a bulk operation is necessary. Send requests to support Send to SLS means send to second-level support. It starts a support-message workflow; selecting it does not retry the requests. 1. Search for and select the intended requests. 2. Choose Send to SLS and select Go to open the message form. This step does not send the email. 3. Review Subject and enter a useful Message: the problem, expected result, affected property/channel/dates, and relevant action time and timezone. 4. Review the included request list. 5. Select Send to submit the support email, or Cancel to return without sending. Request details are included in the message. Do not add passwords, payment details or unnecessary guest information. The confirmation reports submission to support; it does not establish that someone has read it or that the report failure is resolved. If the page reports an error or the outcome is uncertain, check with support before submitting duplicates. Filter reference Field What it changes Property Narrows the search to one authorized property. All means no single-property narrowing within your accessible scope; it is not the property selected in the application header. Organization Offered when more than one organization choice is available. Narrows organization scope; changing it clears Property. Status All, Pending, Processing, Successful, Unsuccessful or Failed. Unsuccessful does not also include Failed here. Channel Narrows to one listed channel. Its presence in this dropdown does not prove it supports a live inventory read. Room Type Select a Property and Search to load its standard rooms. All leaves the room unrestricted; a specific room matches requests recorded against that room, not requests with no room specified. Rate Plan Select a Property and Search to load its standard rate plans. A specific choice matches that standard plan. The row may display its channel-mapping rate-plan name. Requested By Filters by the recorded requesting user. All applies no user restriction. Available users depend on your scope. Request ID Exact numeric request identifier. Overrides ordinary search filters, including archive exclusion, while retaining authorized property scope. Leave blank for a list search. Include Archived Reports Off by default. When checked, includes archived as well as unarchived requests. See the retention limitation above before paging or taking actions. Stay Dates Filters the inventory dates requested. Either endpoint may be blank. Two dates match requests overlapping that period, not only requests entirely inside it. For example, a request spanning the whole month can match a two-day search. Date and Time: Created / Last Run Chooses which request timestamp to filter. Created is the initial choice; no timestamp restriction applies until a date is set. Last Run uses the recorded last-update time, not a guaranteed completion time. Date and Time dates and optional times Uses your signed-in timezone. Start without a time begins at the start of that local day; end without a time includes the entire final local day. A specified end time includes that whole minute. Either endpoint may be blank. A time without its date has no effect. Both date ranges are optional and distinct. Stay Dates answers “which inventory dates?”; Date and Time answers “when was the request created or last updated?” There is no Source or Rates/Availability/Restrictions filter on this screen. Common problems and result checks - No rows appear. Check Property, Request ID, Status, archive inclusion and both date ranges. Search Unsuccessful and Failed separately. Remove unnecessary product/user restrictions and Search again. An empty list is not proof of successful processing or that no earlier request existed. If a known ID remains absent in the correct scope, give it to support. - Room Type or Rate Plan contains only All. Select the intended Property and Search first. If expected products are still missing, ask your administrator to check the property setup rather than guessing a mapping. - “The End Date cannot be before the Start Date” or “The last stay date cannot be before the first.” Correct the corresponding range and select Search again. Rows can still appear with a date error; do not act on that result or rely on its counters. - An action reports no action or no requests selected. Choose the intended action and, for selected-row actions, tick the requests first. Use Search to refresh uncertain scope, not Go. If the top and bottom selectors disagree, make them consistent before submission. - Some selected requests were left out. They could not be resolved within your current authorized property scope. Re-search and confirm access with your administrator; do not substitute a broader selection. - A retry is confirmed but the old error remains. Confirmation is not completion. Search the same ID and review subsequent Status, Attempts, Last Run and message. Avoid repeated retries while it is Pending or Processing; escalate if progress cannot be established. - Archive inclusion clears or a bulk archive is refused despite selecting a property and channel. Use the individual-ID and selected-row procedures above. If those do not establish the needed scope, stop and contact support with the filters and error text. For escalation, include the request ID, property, channel, requested inventory dates, selected filters, relevant times/timezone and exact error text. Distinguish what you searched from any action you actually submitted. Related - Check inventory-report request status across properties - Investigate inventory update requests across properties - Choose filters for a rates and availability report
Review inventory update summaries for your organization
Use Updates Status - Summary to review recorded inventory update counts for your organization's properties and open the requests that need investigation. This page concerns outbound rates, availability and restrictions, not reservation delivery or inventory-report requests. Opening it, reloading it and following its count links do not retry updates. Before you start - Use an organization-administrator account with access to all active properties directly belonging to the organization. The summary does not limit itself to only the properties you can access; an access refusal for an included property can prevent the page from loading. Ask your administrator or ChannelRUSH support to confirm access if this happens. - Confirm the intended organization in Accounts. The normal organization summary includes its active properties directly belonging to that organization, not every property in child organizations. - The property selected in the application's top bar provides navigation context. It does not restrict this organization summary to that property. Read the property heading on each card. Do not use this page as proof that every queued update is shown or every channel is up to date. The current queue section can omit a channel that has Pending requests but no Processing requests. Some queue combinations can also prevent the summary from loading. For a queue investigation, use the request-search procedure below rather than relying on a missing row. Open the organization summary 1. Open Org Admin → Home. The OA breadcrumb on organization-admin pages also opens this home page. 2. Under Channel Manager, select Update Status - Summary - Per Org. 3. Confirm the heading is Updates Status - Summary. 4. Find the property card you want to review. 5. Read its Pending / Processing and Completed (last 90 days) sections using the definitions below. The summary loads when you open the page. It has no filter form, date selector, Search button, export control or pagination. Reload the browser page to read it again. Reloading does not force the completed counts to refresh immediately and does not initiate a channel send. Read a property card Organization update summary for a demo property, showing an empty Pending / Processing section and completed request counts for ChannelRUSH CRS and ChannelRUSH Booking Engine. Each card belongs to the property named at its top. This example shows recorded successful requests and no displayed queue; it is not a live check of channel inventory. Pending / Processing - Pending means the request is waiting to be processed. - Processing means the request is marked as being processed. - These are current stored request states, without the completed section's 90-day date restriction. Archived requests are included in these summary counts too. - Counts refer to requests, not rooms, affected nights or delivery attempts. One request can cover several inventory dates. The normal empty-state message is No updates are currently pending or processing. A missing channel row or a section containing only headers must not be treated as a complete queue check: use Org Admin → Updates, select the property and channel, and search Pending and Processing separately. The steps below explain how. A nonzero count alone does not establish that processing is overdue. Check the individual request and its timestamps before deciding what to do. Completed (last 90 days) The completed table has Channel, Successful, Unsuccessful and Failed columns. Column Meaning Channel A channel currently mapped to the property with qualifying completed-count data. It is not a list of every possible channel or only channels currently enabled for sending. Successful Requests with a recorded successful processing outcome. This is not an independent check of the channel's current selling values. Unsuccessful Requests with a recorded unsuccessful processing outcome. Read the request's message to investigate. This column does not include Failed. Failed Requests recorded separately as failed. Inspect their messages and contact support when the cause or recovery is unclear. A zero in an otherwise populated row means no requests are counted in that status for that channel in the summary period. Channels without qualifying completed-count data are omitted. The empty-state message is No updates are currently successful or unsuccessful. It does not establish that the channel received all intended updates. What “last 90 days” means here The period is based on when a request was created, not its affected stay dates or when it finished processing. It begins at the system reporting day's start 90 days ago, rather than exactly 90 × 24 hours before you opened the page. It is not calculated from your personal display time zone. Completed counts are periodically refreshed and include archived requests. They can lag behind the individual request screen. They summarize recorded request outcomes, not every historical processing attempt: a retried request can later be counted under a different outcome in its original creation period. Do not add queue and completed counts together to calculate unique requests. A previous completed outcome can remain in the summary while a retry is back in the queue. Archiving a request does not remove it from this summary or repair its delivery. Open and investigate requests 1. In the relevant property card, click the number under the status you want to investigate. 2. In the new tab, confirm the heading is Update Requests - Processing Status. 3. Check Property, Organization, Channel and Status in Search Filters before interpreting the results. 4. If you change any filter, click Search. 5. Inspect the request's affected inventory dates, room/rate plan, requested values, Status, Attempts, ID, Created, Last Run and any message. The summary remains open in its original tab. Opening a count does not retry or archive anything. Clicking a Channel name instead opens that property/channel's request search without selecting a particular status; use a status number when you want to retain that status. On the request screen, Created is the request's creation timestamp. Last Run is the stored update/processing timestamp; it does not by itself prove successful delivery. These timestamps are displayed in your signed-in time zone. The inventory dates shown beside requested values are the dates being changed, not those processing timestamps. Check a queue without relying on the summary table 1. Open Org Admin → Updates. 2. Select the affected Property inside Search Filters. 3. Select the affected Channel, or All to inspect the property's channels. 4. Select Pending in Status. 5. Click Search. 6. Check the retained property/channel/status selections and the returned requests. 7. Change Status to Processing. 8. Click Search again. This searches requests; it does not create or resend them. The request search excludes archived requests by default. Select Include Archived Updates and click Search if archived records are relevant. Recheck that selection before another search or paging: it can clear after results load. If scope or archive inclusion cannot be confirmed, contact support rather than treating an empty result as an all-clear. Why the number of detail rows may differ The summary and its linked search are not the same frozen result: - Count links retain the property, channel and chosen status, but do not carry the summary's 90-day date boundary or include-archived setting. - Completed counts use refreshed summaries; request rows reflect the current request records. - The request search excludes archived requests by default and shows a page of results, normally 50 requests at a time. Older detail records may no longer be available. - A request can change status between opening the summary and opening its details. - The Pending, Unsuccessful and Failed count panels on the request screen are separate, capped indicators. They are not a total for the summary number you clicked. Leave date filters blank for the initial investigation. If you need dates, Stay Dates filters the inventory dates affected by an update. Date and Time → Created or Last Run filters request timestamps instead. Click Search after changing them and check the resulting selections. A Failed filter can return a row whose displayed status says Unsuccessful. Keep the selected filter, request ID and message together when escalating; do not infer a different diagnosis from that row label alone. Check the result safely You have completed the investigation when you have identified the intended property/channel requests, checked their recorded status and message, and either understood the result or collected the context support needs. Successful confirms the recorded processing outcome, not an independent comparison with the channel's current inventory. An empty summary or request search does not prove an earlier failure was resolved. Use Search for investigation. The separate Select Action and Go controls can retry or archive requests and are not refresh controls. Do not retry solely because a count is nonzero or a request is old: a retry can also requeue later overlapping requests. If the intended scope or current values are unclear, stop and contact support before taking action. Common problems - The summary will not open, is blank, or has incomplete queue rows. Check that you entered through the intended organization's normal navigation. The current queue display has limitations described above. Use Org Admin → Updates to search the affected property and status directly. If the summary remains broken or request access is refused, send support the page URL, organization, property and observation time. - A property is absent. The normal organization view includes active properties directly belonging to that organization. Confirm the property's organization and active status in Accounts. If you expect it to be included but cannot explain the omission, contact your administrator or support; do not change configuration merely to make it appear. - A channel has no completed row. It may have no qualifying summary data or no longer be mapped to that property. Search the relevant requests and verify the intended channel with your administrator. An absent row is not evidence of delivery success. - A completed count does not change after reloading. Completed totals can lag behind request details. Inspect the individual request's message and timestamps. Escalate persistent unexplained differences rather than repeatedly retrying updates. - A count opens no matching requests. Recheck the property, channel and status, the date filters and archived inclusion. The summary/detail differences above can explain mismatches. If the record remains missing, ask support to investigate; do not assume the original issue repaired itself. For support, include the organization, property, channel, selected status, affected inventory dates, request ID when available, observation time/time zone and exact message. Do not include passwords, payment details or guest information. Related - Investigate inventory update requests across properties - Understand the separate single-property processing summary
Set rate-plan calculations and recalculate rates
Set a standard rate plan's four calculation steps, choose whether to recalculate stored base rates, and check any requested channel updates separately. Before you start - Select the correct property. You need its Channel Manager Update - Rates or Settings permission to save pricing calculations. A view-only user or public demo login cannot perform this workflow's saves. - Know the rate plan's intended source: a room type's rate or a configured parent rate plan's rate. These calculations modify that source; they do not create the missing source prices. - Before choosing recalculation, have your property administrator or support confirm that the plan's room-type rate inheritance is enabled and, if it has a parent rate plan, that parent-plan rate inheritance is also enabled. This editor does not show those switches. Do not change inheritance merely to make a recalculation run. - Re-Calculate Rates On Save is available only for properties with ChannelRUSH Master Image configured. Its absence does not prevent saving the calculation settings. Important: the full-plan recalculation on this page updates base sell rates, not stored occupancy-rate values. If your change must refresh occupancy prices, ask support to confirm the appropriate workflow before recalculating or pushing. Do not use a date-range override as a workaround. Open the rate plan 1. Select the property in the property selector. 2. Open Admin → Home. 3. In Channel Manager, open Rate Calculations. 4. In the rate-plan list, open the plan's name. 5. Check the plan name above Rate Calculation 1 before editing. The page heading is Edit Rate Plan. This editor changes calculation settings for the property's standard plan, not an individual channel's markup or a single room/date price. Set the calculation steps Changes are submitted only when you choose Save or Save & Refresh. Changing a number or calculation type does not itself save the form. 1. Enter the adjustment in Rate Calculation 1. 2. Choose % Percentage or Flat Fee beside it. The flat-fee choice displays the property's currency symbol, for example $ Flat Fee. 3. Complete Rate Calculation 2, 3 and 4 in the order you want them applied. 4. Enter 0 for each unused step. 5. Review Rate Calculations Overrides Per Date Range. A matching date rule replaces these four ordinary adjustments for that date; it is not added after them. 6. Choose what this save should do using the next section. Positive values increase the rate. Negative values reduce it. Enter a numeric amount without typing a percent sign or currency symbol into the amount box. Use 0 to remove a step's adjustment; the page also converts an emptied amount box to zero when its change handler runs. Explicit zero is the clearer reset. The steps run in order. Each uses the result of the previous step, with the property's rounding setting applied at each stage. For example, a source rate of 100 with 10% in step 1 and a 5 flat fee in step 2 becomes 115. Reversing those steps gives 115.50 when rounding to two decimals. Two percentage steps are compounded, not added into one percentage. The property's Do Nothing rounding option still rounds to two decimal places. This page does not change the rounding setting. Review the resulting price rather than assuming every entered decimal survives calculation. Rate-plan calculation form with four ordered adjustments, recalculation choice, date-rule section, Save and Cancel. The same form at a narrow screen width. This demo plan has a negative percentage in step 1 and no date overrides. Wider screens place the four steps side by side. Choose the save action When Re-Calculate Rates On Save is shown, review it for this submission. It starts at No when the editor is opened; it is not a permanent automatic-recalculation setting. Choice What this submission does What it does not establish No Saves the calculation configuration. It does not run this page's stored-rate recalculation or push operation. Existing stored prices need not change immediately. Yes - ReCalculate on Save Saves the settings, then recalculates eligible stored base rates for this plan across the property's room types. It does not refresh stored occupancy rates or request this page's channel push. Yes - ReCalculate on Save & Push Live to OTAs Saves, runs the same recalculation, then requests a rates-only refresh from the selected plan's master image to eligible configured destinations. It does not confirm that requests were created or accepted by every channel. Before choosing either Yes option: confirm the inheritance prerequisites above. Recalculation can be skipped when they are not met, even though the page displays a recalculation-success message. Recalculation works from stored source prices for current and future dates within its forward inventory window. It skips dates with no source sell rate. It is not a historical recalculation, and it does not promise that every date has inventory. Matching date overrides take precedence over the ordinary calculation steps. Before choosing Push Live: there is no room, date or destination selector on this page. It is a plan-wide master-image refresh, subject to channel setup and send eligibility, rather than a push limited to the dates where you changed a rule. Do not assume channel-specific price differences are preserved by a master-image refresh. Review that scope with support if you maintain channel-specific exceptions. 1. Choose the intended Re-Calculate Rates On Save option, when available. 2. Click Save to submit and return to Rate Calculations. 3. Alternatively, open the arrow beside Save and choose Save & Refresh to submit and return to this editor. Both save buttons use the selected recalculation option. Save & Refresh is not a preview and does not independently mean “push to channels.” Cancel returns to Rate Calculations without submitting this form's unsaved edits. It does not undo a previous save, recalculation or push request. Save your intended changes before following another editor link; those links do not submit this form. Check the result 1. Confirm the configuration Reopen the same plan from Rate Calculations, or inspect it after Save & Refresh. Check all four values and types. The recalculation selector returning to No is expected and does not mean your numeric settings were lost. A saved-settings message confirms a different stage from recalculation or channel delivery. Settings are saved before recalculation and dispatch begin. A later error does not undo that earlier save, and recalculation is not guaranteed to roll back across every room type. 2. Check stored base rates after recalculation 1. Open Reports → Rates & Availability for the same property. 2. Select a small affected date range, the relevant room types and this rate plan. 3. Include Rates and select ChannelRUSH Master Image under PMS, when offered. Clear other sources for a master-only check and leave Live Read clear. 4. Open List or Grid and inspect the actual plan/date values. 5. Compare representative dates with and without date overrides against the intended source and calculation. See Choose filters for a rates and availability report for the complete report controls. A blank result is not evidence that recalculation succeeded. A stored master price is not evidence of channel acceptance. 3. Check a requested push separately 1. Open Updates → Status for the same property. 2. Select the destination Channel and relevant Rate Plan, and use Status → All while following the operation. 3. Click Search. 4. Inspect matching requests' products, affected dates, values, creation time, status and messages. Repeat for the destinations you intended to update. 5. Confirm important live prices in the channel itself when channel-side confirmation is needed. Do not use Go to refresh the search; it runs request actions. The editor's “pushed live” message is not proof of queue creation or channel acceptance. An empty Status search is also not proof of success. Do not repeat the push merely because the banner appeared or the channel still differs. See Investigate inventory update status for a property. Field and section reference Field or section Meaning and interaction Plan name Identifies the standard rate plan you opened. It is not editable here. Rate Calculation 1 First adjustment to the source base rate. Choose its amount and type together. Rate Calculation 2 Adjustment to the result of step 1. Zero leaves that step without an adjustment. Rate Calculation 3 Adjustment to the result of step 2. Rate Calculation 4 Final ordinary adjustment to the result of step 3. % Percentage Adds or subtracts a percentage of the value entering that step. A negative percentage is a reduction. Flat Fee Adds or subtracts the numeric amount in the property's calculation currency. The displayed currency symbol is not a separate currency selector. Re-Calculate Rates On Save Controls recalculation and optional dispatch for this submission only. See the save-action table and prerequisites. Rate Calculations Overrides Per Date Range Lists separately saved date rules. Dates shows the range and any weekday narrowing; Rate Calculations summarizes the rule's adjustments. An empty table means this plan has no listed date overrides. Add New , and existing rows' Edit or Delete links, open separate screens; they do not save the four numbers above. Occupancy Rates Shown when occupancy rates are enabled for the property. Lists separately configured occupancy-rate calculation parameters by Name , with their calculation summaries. Add New , Edit and Delete lead to separate parameter screens where permitted. This page's full-plan recalculation does not refresh stored occupancy values. Date-rule and occupancy editors have their own save/delete behavior. This guide's full-plan recalculation instructions must not be assumed to apply to those separate operations. Ask support before using them to repair an unexpected stored price. Common problems Symptom Check and safe next action The form is read-only or Save is denied. Ask your administrator to check Channel Manager pricing permissions. Public demo access is read-only for these changes. Do not switch to a broader editor to bypass a restriction. The recalculation selector is missing. The property may not have ChannelRUSH Master Image configured. You can save the calculation configuration, but ask support how existing prices should be updated for that property's setup. Prices do not change after Save. Check whether you chose No , whether source rates exist, whether inheritance permits recalculation, and whether a matching date rule replaced the ordinary adjustments. Inspect stored master values before another submission. The recalculation message appears, but some dates or occupancy prices are unchanged. Missing source prices are skipped; the inheritance gate can skip the operation; occupancy values are not recalculated here. Stop and ask support if the result does not match that scope. The page rejects the form or displays a validation message. Recheck the numeric inputs and read the message. The plan and its existing date/occupancy rules are also validated, so the issue may not be one of the four visible amounts. If the message concerns an unavailable field or remains unexplained, contact support rather than changing unrelated settings. An error appears after saving, or you are unsure whether a push ran. Reopen the plan and check saved settings, master prices and Update Status before retrying. Earlier settings or some rates may already have changed. A repeat push can create additional work; do not assume a timeout means nothing happened. A channel price differs despite a “pushed live” message. Inspect the relevant request and its message, mapping/setup and affected dates, then confirm the channel value. Escalate unexplained missing requests or mismatches before resending. For support, include the property, rate plan, room type, destination channel if relevant, affected dates, selected save action, action time and time zone, and exact message. Include a request ID if one exists. Do not include passwords, payment details or unnecessary guest information.
Set date-specific room-type rate calculations
Save a room type's calculation rule for particular dates and weekdays, and check the saved settings without mistaking them for a rate update. Saving this page does not recalculate stored prices or send rates to channels. Do not use the saved-settings confirmation as evidence that your selling prices changed. Applying the dated calculation is a separate, administrator-controlled workflow; confirm that workflow before creating rules you expect to affect prices. Before you start - Select the correct property and an existing standard room type. These are property-level room calculations, not a channel's markup or a rate plan's calculation. - You need the property's Channel Manager Update - Rates or Settings permission to save. A view-only user or demonstration login cannot save these changes. - Agree on the date range, selected weekdays, calculation units and intended source rate with your administrator. A rule cannot supply a missing source price. - Review the room's existing dated rules. Use nonoverlapping date ranges. Different weekday selections do not guarantee that overlapping ranges will be accepted. When can a dated rule affect prices? The separate room-type recalculation workflow uses these rules when ChannelRUSH Master Image is configured and the room has a parent room with linked rates. For matching dates, the dated calculation replaces the room's default four-step calculation; it is not added on top of those default steps. Do not assume the dated rule also governs ordinary global-rate entry, PMS processing or every other rate-update workflow. Ask your administrator or support to confirm the applicable workflow and the affected room/rate plans before recalculating or sending anything. This page does not provide that recalculation or delivery action. Open the editor 1. Select your property. 2. Open Admin → Home. 3. In Channel Manager, click Rate Calculations. 4. Under Room Types, click the room type's name. 5. Find Rate Calculations Overrides Per Date Range. 6. Click Add New to create a rule, or Edit beside an existing rule. 7. Confirm the Edit Rate Calculation page and the room name above the form. Org Admin users may also reach this editor from the standard room-type settings page. The breadcrumb and return destination can differ, so check the property and room rather than relying on the breadcrumb alone. Set the dates and calculation These controls do not autosave. Your changes are submitted only by Save or Save & Refresh. 1. Enter Start Date using the date picker. 2. Enter End Date on or after the start date. Both endpoints are included. 3. Under Days, leave selected only the weekdays on which the rule should apply. At least one selected weekday must occur between the two dates. 4. Enter the first adjustment in Rate Calculation 1. 5. Choose its unit: % Percentage or Flat Fee, shown with the property's currency symbol. 6. Enter any further adjustments in Rate Calculation 2, 3 and 4, choosing the unit for each. 7. Leave unused calculation values at 0.00, rather than blank. 8. Review the dates, weekdays, signs, units and any Existing Rate Calculations before saving. A new rule starts with blank dates, all seven weekdays selected, four zero values and four Flat Fee units. The example below shows that unsaved starting state in a narrow layout; desktop controls can appear side by side. New room-type date calculation form with blank dates, all weekdays selected, four zero flat-fee adjustments, Save and Cancel How the four steps work The steps run in order: 1 → 2 → 3 → 4. Each step uses the preceding step's result. - Flat Fee: add the entered amount. A negative amount subtracts it. - % Percentage: add that percentage of the current amount. A negative percentage discounts it. - The property's rate-rounding setting is applied after each step. Do Nothing still rounds to two decimal places. For example, with a source rate of 100.00, step 1 of -10 % Percentage produces 90.00. Step 2 of 25 Flat Fee then produces 115.00. This illustrates the calculation, not a live rate preview or confirmation that a channel received that price. Zero is not deletion. Four zero values still leave a dated rule. When the separate recalculation uses it, that rule replaces the default calculation with no adjustment other than rounding. Use the deletion workflow to remove an unwanted rule; do not zero it merely to disable it. Save and check the result 1. Click Save to save the rule and return to the room-type page. Alternatively, open the arrow beside Save and choose Save & Refresh to save and remain in this calculation editor. 2. Check for the saved-settings confirmation. A redisplayed form with your typed values is not enough to establish a successful save. 3. If you used Save & Refresh, click Cancel to return to the room-type page; this does not undo your saved rule. Find the rule under Rate Calculations Overrides Per Date Range. 4. Reopen it with Edit. 5. Verify both dates, selected weekdays, all four values and their units. This confirms the saved configuration only. The list is not an effective-price preview. Save & Refresh changes where you return after saving; it does not add a recalculation or send. If you need to check actual stored rates after a separately agreed recalculation, use Rates & Availability — List View, selecting the correct property, source, room, plans and dates. Stored master rates, requested channel values and channel acceptance are different results. A settings row or stored rate does not prove acceptance by a channel. If the save response is missing or unclear, reopen the room's rule list before trying again. Do not click Add New repeatedly: the first submission may already have saved a rule. Edit, cancel or remove a rule - Edit: open the existing rule and change its fields, then save. Moving or shortening its dates does not itself restore prices previously calculated for the old dates. Agree on any required rate correction separately. - Cancel: leaves this editor without submitting the unsaved changes. It returns to the room-type page from which this workflow was opened. Cancel is not an undo for a previously saved rule. - Delete: available for an existing saved rule and opens a separate confirmation page. Check the room and rule shown before confirming deletion. After confirmation, check the room's list to verify the rule is gone. Removing the configuration does not itself restore stored rates or notify channels. If Existing Rate Calculations appears in the editor, it lists the room's other rules; the rule being edited is excluded. Its Dates column shows the date span and, when not every weekday is selected, the weekday pattern. Rate Calculations summarizes the adjustments. Edit and Delete refer to the rule on that row. Save or cancel your current work before navigating to another rule. Field reference Field or control What to enter or expect Room name Confirms which standard room type owns the rule. Choose a different room from the room list, not by changing calculation fields. Start Date Required first date, included in the range. A new rule leaves it blank. Use the displayed date format or picker. End Date Required last date, also included. Use the same date for a one-day rule and select that date's weekday. The rule is a dated interval, not an annually recurring season. Days — Mon to Sun All selected initially. Clear weekdays you do not want. At least one must remain selected and occur in the range; selecting none does not mean every day. Rate Calculation 1 First signed numeric adjustment and its unit. Default 0.00 Flat Fee. Rate Calculation 2 Adjustment to step 1's result. Default 0.00 Flat Fee. Rate Calculation 3 Adjustment to step 2's result. Default 0.00 Flat Fee. Rate Calculation 4 Adjustment to step 3's result. Default 0.00 Flat Fee. % Percentage Percentage of that step's input, not a percentage of the original rate at every step. Use a negative value for a discount. Flat Fee Signed amount in the property's displayed currency. The numeric controls support up to five decimal places, but the property's rounding applies to each calculated result. Existing Rate Calculations Other saved rules for this room, when any exist. Use them to check date conflicts; the summary does not verify stored or channel prices. Save Submit settings and return to the room-type page. Save & Refresh Submit settings and return to this calculation. Available in Save's arrow menu. Cancel Leave without submitting current edits. Delete For an existing rule, open deletion confirmation. It is not a rate-restoration action. Common problems Dates or weekdays are rejected Both dates are required. Check that the start is not after the end, at least one weekday is selected, and a selected weekday actually occurs in that span. For a one-day rule, select that day's weekday. If a valid combination is still rejected, send support the property, room, date range, weekday selection and error text. An overlap error appears even though the weekdays differ Overlapping date spans can be rejected even when the selected weekdays differ. Compare the full ranges against the other rules; do not assume that selecting Monday in one and Tuesday in another avoids the check. Do not delete valid rules or change their business dates merely to get past the message. Ask support to review the intended schedules before retrying. The form remains open but there is no clear save confirmation Check date formats and numeric entries, including any blank calculation value. Use explicit zero for an unused step. Reopen the saved rule list to establish what persisted before resubmitting. If the problem continues without a useful message, provide support with the field values, action time and time zone, and whether you used Save or Save & Refresh. Validation refers to a different rule Saving validates the room's other calculation and occupancy settings as well. An existing invalid setting can block your edit. Have the property administrator review the named setting; do not change unrelated pricing as a workaround. Escalate if the message does not identify what needs correction. The rule saved, but rates did not change That is not evidence of a failed save: this page saves configuration without recalculating or sending prices. Confirm the intended separate workflow with your administrator or support. Repeated saves are not a delivery remedy, and a global-rate update is not a substitute for applying a dated rule. Save is unavailable or refused Check your access to the selected property and the Update - Rates or Settings permission. Demonstration access does not permit settings saves. Ask your administrator to review access rather than using another property or a broader update screen to bypass the restriction. Related - Standard room-type settings - Read rates and availability in List View
Configure room-type rate calculations
Save a standard room type’s minimum-rate setting and four-step price calculation, and find its date-specific and occupancy rules. Saving this page changes configuration only. It does not recalculate existing stored prices or send rates to channels. Agree on the applicable update or recalculation workflow before expecting these settings to change selling prices. Before you start - Select the correct property and an existing standard room type. - You need the property’s Channel Manager Update - Rates or Settings permission to save. View-only and demonstration access cannot save these settings. - Agree on the intended source price, adjustments and minimum with your revenue administrator. This editor is not a channel-specific markup or a rate-plan editor. - Check whether your property uses occupancy pricing or linked parent-room rates before changing related rules. Open the room’s calculation settings 1. Select your property. 2. Open Admin → Home. 3. In Channel Manager, click Rate Calculations. 4. Under Room Types, click the room type’s name. 5. Confirm Edit Room Type and the room name above the fields. The parent Rate Calculations page also lists rate plans and the property’s Rate Rounding Setting. Those are separate settings; opening a room does not edit them. Set the minimum and four calculations These fields do not autosave. Changes are submitted by Save or Save & Refresh. 1. Enter a positive amount in Minimum Rate Allowed. 2. Enter the first adjustment in Rate Calculation 1. 3. Choose % Percentage or Flat Fee, shown with the property’s currency symbol. 4. Enter any further adjustments in Rate Calculation 2, 3 and 4, selecting the unit for each. 5. Set unused calculation values to 0.00. 6. Review the signs, units and order before saving. Do not use zero to disable the minimum. Zero or a negative minimum resolves to the system default of 40.00. Enter the positive minimum you intend and verify it after saving. The minimum is used in rate-update validation; it does not automatically raise a calculated price or repair existing prices. Room-type calculation editor showing Minimum Rate Allowed, four calculation values and units, date-range overrides, Occupancy Rates, Save and Cancel Example saved demo configuration in a narrow layout. Wider screens place the calculation fields side by side. The empty lists show that this room has no saved dated or occupancy rules; they are not a rate preview. How the four steps work The calculation runs 1 → 2 → 3 → 4. Each step uses the previous step’s result. - Flat Fee: adds the signed amount. A negative amount subtracts it. - % Percentage: increases the current amount by the entered percentage. A negative percentage discounts it. - 0.00: makes no adjustment at that step, apart from rounding. - The property’s rate-rounding setting applies after each step. Do Nothing still rounds to two decimal places. For example, with Rate Rounding Setting set to Do Nothing, starting from 100.00, step 1 of -10 % Percentage gives 90.00. Step 2 of 25 Flat Fee then gives 115.00. Reversing those steps gives 112.50, so their order matters. Other rounding settings can change these results. This is an arithmetic example, not a live-price preview. These room rules are used when the applicable workflow derives a room price from a source price—for example, when populating room prices from a global rate. Entering a price directly for a room is not a promise that the same room adjustment will be applied again. Rate-plan rules, occupancy rules and destination-channel calculations can affect later results. Review the intended products and final prices rather than assuming this form shows what every channel will receive. Save and check the result 1. Click Save to save and return to Rate Calculations. Alternatively, open the arrow beside Save and choose Save & Refresh to save and remain in this room editor. 2. Check for the saved-settings confirmation. 3. If you returned to Rate Calculations, find the room under Room Types and review its Rate Calculations and Min Allowed Rate columns. 4. Open the room again and check the minimum, all four values and all four units. A redisplayed form containing your typed values is not enough to establish a successful save. Reopening and checking the saved values is the result check. Save & Refresh changes the return destination; it does not add a recalculation or channel send. Cancel returns to Rate Calculations without submitting current edits. It does not undo an earlier save. Save or cancel your current edits before following Add New, Edit, or another navigation link. If you need existing dates to change Confirm the applicable workflow with your administrator. This editor has no date selector, recalculation button or delivery action. Repeated saves are not a remedy for unchanged prices. Where ChannelRUSH Master Image and linked parent-room rates are configured, the separate standard room-type settings workflow offers administrator-controlled recalculation. That workflow can affect forward room and rate-plan inventory; it is not a narrow date update on this page. Agree on its scope and any separate channel delivery before proceeding. After an agreed recalculation, use Rates & Availability — List View to inspect the correct property, source, rooms, plans and dates. Open Reports → Rates & Availability, select the criteria and click List. If changing criteria within List View, click Apply — reloads report or Load as appropriate and check the reloaded rows. Saved settings, stored master prices, requested channel values and channel acceptance are different results. Neither a saved-settings confirmation nor a stored report price proves a channel accepted an update. Date-specific calculations Rate Calculations Overrides Per Date Range lists this room’s saved dated rules. - Dates shows the date span and, when not every weekday is selected, the weekday pattern. - Rate Calculations summarizes the row’s adjustments. - Add New opens a separate dated-rule editor. - Edit opens the rule on that row. - Delete opens a separate confirmation page; it is not an immediate deletion link. In the applicable linked-parent room recalculation workflow, a matching dated rule replaces the default four-step calculation for that date. It is not added after the defaults. Do not assume it governs every global-rate entry or PMS update. Use Set date-specific room-type rate calculations for dates, weekdays, overlap checks, saving and deletion. Removing or shortening a rule does not itself restore prices already calculated for its former dates. Four zero steps still leave a dated override; they do not delete it. Occupancy calculations Occupancy Rates appears only when occupancy rates are enabled for the property. It holds separate rules for the named occupancy or additional-rate type; the four main room calculations do not themselves specify a guest count. - Name identifies the configured rate type; the adjacent calculation summary shows its adjustments. - Add New opens the occupancy-rule editor. - Edit opens an existing rule; Delete opens its confirmation page. These row actions require pricing-edit access. - An empty list means no rules are listed for this room. It does not prove that a channel has no occupancy pricing or that all occupancy prices are zero. Occupancy calculations depend on the enabled configuration and update workflow. For example, when populating room/plan prices in Quick Updates, an applicable rate-plan occupancy rule takes precedence over the corresponding room rule. Do not assume every occupancy value is recalculated whenever the main rate changes. Save your current room settings before opening an occupancy rule. Confirm the intended rate type and pricing basis with your administrator before creating or deleting one; an occupancy-total price is not interchangeable with an extra-person supplement. Verify the rule in this list after completing its separate editor. Saving or removing a rule is not proof of channel delivery. Field and control reference Field or control Meaning and accepted input Room name Identifies the existing standard room type. Choose a different room from the parent list; this editor does not rename it. Minimum Rate Allowed Positive monetary amount used in rate-update validation. Zero or negative resolves to 40.00, not “disabled.” Use an explicit number rather than blank. It does not clamp calculated prices to the minimum. Rate Calculation 1 First signed numeric adjustment to the workflow’s source rate. Rate Calculation 2 Adjustment to step 1’s result. Rate Calculation 3 Adjustment to step 2’s result. Rate Calculation 4 Adjustment to step 3’s result. Calculation units Percentage or flat monetary amount. Select independently for every step. Enter the number in the value box, not a currency or percent symbol. Calculation inputs support up to five decimal places; each result is rounded under the property setting. Unused calculation Use 0.00. Clearing a calculation value is converted to zero when its change handler runs; explicit zero avoids relying on that browser behavior. Existing saved values load when you open the editor. Rate Calculations Overrides Per Date Range Separate saved dated rules, with Add New and per-row Edit/Delete links. This is not a calendar of effective prices. Occupancy Rates Conditional list of separate occupancy/additional-rate rules. Hidden when the property’s occupancy-rate feature is off. Save Saves configuration and returns to Rate Calculations. Save & Refresh Saves configuration and stays in this editor. Found in Save’s arrow menu. Cancel Leaves without submitting current edits. No rollback of previous saves. Common problems The minimum returns as 40.00 Zero and negative values resolve to the default. Enter the intended positive minimum and reopen the room after saving. If another positive value changes unexpectedly, send support the property, room, entered value and saved value; do not lower the minimum merely to get a rate accepted. Prices did not change after saving This page saves settings only. Confirm the separate calculation/update workflow and source price with your administrator. Do not resend inventory or repeatedly save as a diagnostic step. Escalate with the property, room/plans, affected dates, intended source price and expected versus observed result. A rate fails minimum-rate validation Review the main and additional calculated prices, discounts, units and destination currencies. A minimum setting is not a substitute for checking those values. Check both stored results and any update error before retrying; an unsuccessful delivery does not establish that every earlier local change was rolled back. Ask support if the failing value or destination is unclear. The form remains open without a clear success message Check numeric entries, especially a blank minimum or a value containing a currency/percent symbol. Reopen the room to establish what persisted before retrying. If validation refers to another dated or occupancy rule, have the administrator review that rule: saving also validates those related settings. Do not alter unrelated pricing to get past an error. Save is unavailable, refused, or occupancy controls are missing Check the selected property and Update - Rates or Settings permission. Demonstration access cannot save. Occupancy Rates also requires the property feature to be enabled; pricing access alone does not make that section appear. Ask your administrator to review the intended setup rather than using another update screen to bypass a restriction. For support, include the property, room, affected dates, exact error, action time and time zone, and whether you used Save or Save & Refresh. Do not send passwords, payment details or guest information. Related - Set date-specific room-type rate calculations - Read rates and availability in List View
Review reservation settings and notification recipients
Review a property's reservation-handling settings and maintain the email recipients used for reservation notifications. Before you start Select the correct property in the property selector. To add, edit or delete recipients, you need both Property Settings and Channel Settings permissions. Ask your organization administrator if the management links are missing. Use only addresses authorized to receive the property's reservation information. Adding a recipient is an operational change, not a test message. Verified = No is not a reliable way to disable delivery: fallback delivery can use unverified addresses when no other delivery method is available. Open Reservation Settings 1. Open Admin → Settings - CM. 2. In the Channel Manager section, select Reservations. 3. Check General Settings and Reservation Notification Emails for the selected property. The page is an overview. Its three Yes/No settings are read-only, and it has no Save button. Opening it does not submit a reservation or resend an email. General Settings showing the three read-only reservation-handling values The values shown here are examples from a demo property, not recommended settings for every property. Understand General Settings Setting What it means Reservation Handling Enabled Shows the property's reservation-processing setting. Channel-level setup also matters. Yes is not proof that every channel is receiving or delivering reservations correctly; No is not a guarantee that no reservation can be stored or emailed. Availability Management Controls reservation-driven availability adjustments when property and channel reservation handling are enabled. A qualifying new reservation can reduce available rooms; mapping and channel configuration determine which updates can be produced. Auto-Replenish On Mod / Cancel Controls returning rooms to availability for a cancellation or the old room/date portion of an availability-changing modification. It operates with reservation handling and availability management, not as an independent channel reopen command. If these values do not match your intended PMS and channel workflow, have your administrator or Support review the configuration. Do not change recipient addresses to work around an availability-setting problem. This page does not show channel acceptance or prove that a particular inventory adjustment succeeded. Review notification recipients Column What to check Email The address configured for this property's reservation notifications. Confirm the mailbox is still authorized and monitored. Format HTML for formatted messages, or Text for plain text. Language The stored language locale, such as en-US . New recipients use your signed-in language. This editor does not offer a Language control; contact Support if the stored language needs correction. Verified Yes means a verification timestamp is recorded. It does not prove that a reservation email arrived in the inbox. The overview does not show Type. Select Edit beside an address to inspect whether it is Primary or Backup, then use Cancel if you are only checking. An empty table means no notification addresses are listed for this property. It does not establish that PMS delivery is absent or that reservations have failed. Primary versus Backup - Primary: each verified Primary address is eligible for normal reservation notification requests when email delivery is enabled for the reservation's channel. Primary is not a single preferred address and does not mean “email only if the PMS fails.” - Backup: verified Backup addresses can receive fallback notifications after an unsuccessful or expired primary delivery request, including a PMS/API request. They can also be used immediately when there is no API delivery and no verified Primary address. Channel email settings and delivery processing still apply. Choosing a type does not prove delivery or promise a particular failover time. Backup email does not repair a failed PMS delivery. Add and verify a recipient The form saves only when you select Save. Opening Add New, typing an address or changing a dropdown does not add the recipient. New Reservation Delivery Email form with Email, Type, Format, Save and Cancel 1. Under Reservation Notification Emails, select Add New. 2. Enter the authorized mailbox in Email. An address must be valid and unique within this property. 3. Choose Type: Primary or Backup. New recipients default to Primary. 4. Choose Format: HTML or Text. The default is HTML. 5. Select Save. 6. On the returned overview, check that the intended address appears with the correct format and language. Use Cancel instead of Save to return without adding the address. If the address is already verified elsewhere in the same organization, the new recipient can be marked verified automatically. Otherwise, the application attempts to send a verification email to that address. A saved or sent message on screen does not prove mailbox receipt. Before following the verification link: newly verifying an address can turn on the property's Reservation Handling if it is off. Confirm that the property is ready for reservation handling; ask your administrator or Support if that activation is not intended. When activation is appropriate, open the verification email in the intended mailbox and follow its link. Return to Reservation Settings, reload the page and confirm Verified = Yes. Complete this check before relying on the recipient for normal notifications. Do not leave an unwanted address configured on the assumption that an unverified address cannot receive anything. Edit an existing recipient 1. Select Edit beside the intended address. 2. Confirm the address displayed on Reservation Delivery Email. 3. Change Type or Format as required. 4. Select Save. 5. Confirm the returned overview's format. To confirm Type, reopen Edit, check the selection and select Cancel. The existing email address is read-only. To replace it, add and verify the new authorized address first, then remove the old recipient when the transition is ready. Coordinate the overlap: both addresses may receive notifications while both are configured. The existing-recipient form also shows Verified Timestamp, or Not Verified. The timestamp uses your signed-in time zone. Saving an existing recipient does not resend its verification email. Remove a recipient Keep a suitable delivery method in place before removing an address. Removing the configured recipient does not guarantee recall of delivery requests already created. 1. Select Delete beside the intended address on the overview. 2. Check the address on Delete Reservation Delivery Email. 3. Select Delete to confirm removal, or Cancel to leave it unchanged. 4. Check the returned overview and confirm that the address is no longer listed. Opening the confirmation page alone does not delete the recipient. Removing a verified recipient can also send a removal notification. Check the result Keep these checks separate: - Configuration saved: the intended row, format and language appear after reloading; Type is checked in Edit. A deleted address is absent. - Address verified: Verified shows Yes; the editor shows its timestamp. - Reservation delivered: inspect the particular reservation's delivery record and confirm receipt in the intended destination. Neither the recipient table nor a verification timestamp establishes this. Use Reservation delivery status for that investigation. Do not resend a reservation merely to test a recipient configuration. If delivery is uncertain, check the existing attempt first and follow the delivery guide's recovery steps. Common problems Symptom Safe next action Add New , Edit or Delete is missing, or the form is read-only Confirm the selected property and ask your organization administrator to check both Property Settings and Channel Settings permissions. Email is a required field or the address is not in a valid format Correct the new recipient's Email field. Recheck the whole address before saving. The address already exists for this hotel Return to the overview and inspect the existing row. Edit its Type/Format rather than adding a duplicate. No verification email arrives Check the saved address and mailbox spam/junk folder. Existing-recipient Save is not a resend control. Contact Support if the message remains unavailable; do not repeatedly delete and recreate the recipient. Verified = Yes , but a reservation email is missing Check the particular delivery record, recipient Type and channel email setup. Verification is not a delivery receipt. Escalate with the affected property, channel, reservation reference and action time/time zone. An error or interruption occurs after Save or Delete Reopen the overview before repeating. The row may already have been saved or removed before a later notification failed. Ask Support if the resulting state is unclear. The email address or language cannot be edited This editor exposes neither existing-address changes nor a Language control. Use the replacement-address workflow above; ask Support about a language correction. For support, include the property, affected recipient address, action time/time zone and visible error. Include a reservation reference only when investigating a particular delivery. Do not send passwords, payment details, verification-link tokens or unnecessary guest information. Related - Reservation delivery status - Check a property's setup status
Analyze booking patterns, length of stay and seasonal trends
Use Booking Patterns to compare captured room stays by full stay length, seasonal stay dates or the interval between first receipt and arrival, then export the selected aggregates. Before you start Select the intended property. You need access to that property and its reports. This report reads reservations already captured by ChannelRUSH; it does not change reservations, rates or availability. Each run covers one property and one Reservation feed. A feed identifies the channel through which ChannelRUSH received the reservation, not necessarily the original selling source. Do not add separate feeds together without checking for overlapping bookings. These are current captured booking results—not physical occupancy, realized accounting revenue, complete hotel production or a historical on-the-books snapshot. Open and run the report 1. Select your property in the property selector. 2. Open Reports → Revenue Analytics → Booking Patterns. This entry opens Booking Window × LOS × Weekday. The Length of Stay and Seasonal Trends menu entries open the other views of the same report. 3. Choose the view you want using the tabs above Filters. 4. Set Stay dates (through inclusive). You can choose Month to fill a whole month, or enter a start and end date. Use an ordered range of at most 366 days. 5. Select Reservation feed. Check it explicitly rather than assuming the default is the feed you want. 6. If needed, enter Channel room ID, Channel rate-plan ID or Currency. Leave these blank to avoid that restriction. 7. Select Booking status: Active only or Active and canceled, kept separate. 8. For Seasonal Trends, choose Group by and Compare with prior-year production. 9. Click View report. After a report has loaded, expand Filters, make your changes and click Update report. Changing a filter is not the same as running the report. Check the loaded dates and feed after submitting. Switching view tabs retains the current report selection and returns supporting detail to its first page. Submit changed filters before switching tabs. Reset report clears the selection while keeping the named view. The initial date range runs from today in the property's time zone through the following 29 days; it is not a lookback period. Check the result Confirm the property, feed, dates and active view before comparing figures. In Seasonal Trends, also check the actual comparison dates shown above the results. - The aggregate tables cover the full matching selection. Paging the supporting stays does not narrow those totals. - No captured stays match these filters means the query found no matching captured stays. It does not establish zero bookings or complete data coverage for the property. - Extracted is the report extraction time, not the latest reservation update or proof that the feed is current. Downloads rerun the query, so an export and an earlier screen can differ if reservations changed. - A dash (—) means unavailable, not zero. A recorded zero price can be valid data; it is different from a missing price. - Currency and current booking status stay separate. Do not add different currencies together or treat canceled value as active production. Expand How to read this report in Length of Stay or Seasonal Trends, or Definitions and coverage in the booking-window view, for the report's coverage qualifications. Choose the right view Length of Stay This view groups each room stay by its whole stay length, including nights outside your selected interval. Buckets are 1, 2, 3, 4–6, 7–13 and 14+ nights. Room nights and monetary values include only the nights inside your selected dates. Checkout is excluded. A multi-room reservation contributes separate room stays; it does not become one longer stay. The small bars beside Room stays show relative stay counts, not revenue. A booking with rooms in different buckets can appear in more than one row. Do not sum row booking counts and call the result a distinct-booking total. Seasonal Trends Use this view to group stay nights, rather than arrivals, by: - Calendar month: each calendar month touched by the interval. - Day of week: the weekday on which the stay night falls. - Weekday or weekend: Monday–Friday versus Saturday–Sunday. Under Compare with prior-year production: - No comparison shows only the selected interval. - Same calendar alignment starts one calendar year before the selected start and preserves the selected interval's length. - Aligned weekdays adjusts the prior-year start to the nearest matching weekday and preserves the interval's length. Read the displayed dates, especially around leap years. Selected and comparison periods appear separately and are extracted separately. This is current captured production for those periods, not the amount that was on the books at the same time last year. No percentage uplift is calculated for you. Edge months can be partial. Future stay dates contain current on-the-books business. Compare like-for-like intervals, currencies and statuses, and check coverage before drawing conclusions. Booking Window × LOS × Weekday This view crosses three dimensions: 1. Receipt window: days from the first retained receipt in ChannelRUSH to arrival, calculated using the property's local dates. 2. Full LOS: the entire room stay's length, not only the selected nights. 3. Arrival weekday: the weekday the guest arrives—not the weekday of every occupied night. Receipt bands are 0–3, 4–7, 8–14, 15–30 and 31+ days, plus Unknown receipt interval. Read the band labels; their displayed order is not necessarily chronological. First retained receipt is not the original sale time. Imports and missing retained history can shorten the measured interval. Missing timing, a first receipt after arrival, or timing without a verified UTC offset remains unknown. Do not turn unknown intervals into same-day bookings. Mean receipt lead days uses only timed room stays. Mean full LOS counts each room stay once within its dimension row, not once per selected night. The headline distinct bookings is calculated across the full selection; row booking counts can overlap. Understand counts, prices and coverage The report uses the current captured reservation version. Active includes current new or modified reservations; a reinstated booking is active. When canceled business is included, its available current-version stay dates are used. Booking Patterns does not recover missing pre-cancellation dates for you. A stay contributes nights only where its dates overlap the selected interval, excluding checkout. Valid nights remain included even when prices or current room mappings are missing. A priced night has exactly one recorded nightly price with a nonblank amount. Missing prices, null amounts and duplicate price records do not qualify as priced nights. A recorded zero amount does qualify. Monetary totals are more restrictive: qualified nights require a booking-engine feed price and a known currency. Other reservation feeds can show counts and priced-night coverage without qualified value or ADR. Booking-engine room-rate value includes any tax already embedded in the room rate and excludes separately stored fees and taxes. It is not collected revenue or profit. ADR divides known qualified room-rate value by qualified nights, not by every captured room night. A high ADR with low price coverage should not be treated as a complete average for the property. Unmapped room nights have no single resolved current standard room target. Missing or ambiguous current mappings do not remove otherwise valid nights. They also do not prove what the mapping was when the booking arrived. Known-value and night shares are calculated within the selected feed, currency and status. Known-value shares exclude unavailable amounts; a share is unavailable when its applicable value total is not positive. Source-exception messages describe records without booking identities, invalid room-stay dates or bookings without usable dates. These diagnostics cannot all be assigned to the selected stay period, can overlap and must not be added to dated totals as lost bookings. Inspect supporting room stays 1. Expand Selected feed room-stay detail below the aggregate report. 2. Review the dates, full stay length, clipped nights and recorded identifiers. 3. Use the pager when more matching stays are available. Each page contains at most 100 room stays; the aggregates above still cover the full selection. 4. Where a Reservation link is available, open it to inspect the supporting current reservation version. Supporting stays cover the entire selected report, not one LOS bucket or cross-analysis cell. The reservation screen shows the whole booking; the report counts only matching stay nights. Reconcile those different scopes before treating differing totals as an error. The detail is ordered by arrival and then its recorded identifiers. It is not an editable inventory grid, and this report does not provide configurable detail sorting, search or page size. Export or open a separate view After the report has loaded: - Choose CSV under Download for the full aggregate table. This is not a download of the supporting room-stay pages. Seasonal exports include both selected and comparison periods when comparison is enabled. - Choose New window for the same selection without the application's normal navigation. Check the dates and feed in that view too. An empty period still exports a row with RowState = No captured rows. Its blank aggregate fields are not measured zero values. The extraction timestamp belongs to that export run, not to a fresh vendor response. CSV uses invariant numeric formatting and ISO-style dates. Unavailable numeric values are blank. Text that could be interpreted as a spreadsheet formula can have a protective leading apostrophe. This report's download is CSV; it does not offer a dedicated Excel workbook, PDF or Copy to Clipboard control. Filter reference Field or control Meaning and accepted selection Property selector One property you are authorized to access. Verify it before opening the report. View tabs Booking Window × LOS × Weekday, Length of Stay or Seasonal Trends. Month Shortcut that fills a whole calendar month; run or update the report afterward. Stay dates (through inclusive) Start and end stay dates, including both bounds but excluding each reservation's checkout. Maximum 366 days; supported years are 2000–2100. Provide both dates. Reservation feed One recorded delivery feed. The report does not combine feeds. Channel room ID Exact channel-side room identifier, up to 200 characters. This is not the standard room name. Blank means all matching room IDs. Spaces are significant. Channel rate-plan ID Exact channel-side rate-plan identifier, up to 200 characters. Blank means no rate-plan restriction. Recorded nightly IDs can differ from the room's fallback plan; conflicting nightly identities remain unknown. Currency Recognized currency code, such as USD. Leading/trailing spaces are removed and letters are uppercased. Blank means no currency restriction; it does not convert currencies. Booking status Active only, or Active and canceled kept separate. No canceled-only option on this report. Group by Seasonal only: Calendar month, Day of week, Weekday or weekend. Initial choice is Calendar month. Compare with prior-year production Seasonal only: No comparison, Same calendar alignment or Aligned weekdays. Initial choice is No comparison. A retained comparison selection on another tab does not create a comparison table there. View report / Update report Applies the displayed criteria and reads the report. Reset report Clears the selection and retains the named view. On-screen column reference Length of Stay and Seasonal Trends aggregates Column What it measures Full-stay LOS / Stay-date period Whole-stay bucket for LOS; selected seasonal grouping for Seasonal Trends. Currency Recorded currency, or Unknown. If every row has the same currency, it appears above the table instead. Status Active or Canceled. If every row has the same status, it appears above the table instead. Bookings Distinct captured bookings in that row; counts across rows can overlap. Room stays Distinct room stays in that row. The adjacent bar represents this count. Room nights Nights inside the selected interval, excluding checkout. Priced nights / nights Nights with one recorded non-null price, beside all matching nights. Qualified priced nights Priced booking-engine nights with a known currency, used for monetary calculations. Unmapped room nights Matching nights without one resolved current standard room target. Known booked room-rate value Sum of qualified nightly prices, separated by currency and status. ADR on qualified nights Qualified value divided by qualified nights. Known value share LOS only: this row's percentage of qualified value within its currency/status group. Booking-window cross-analysis aggregates Column What it measures Receipt window × full LOS × arrival weekday First-retained-receipt band, whole-stay bucket and arrival weekday. Currency / Status Recorded currency and current booking status; these remain explicit columns. Bookings / Room stays Distinct bookings and room stays within the row. Clipped nights Matching nights inside the selected interval. Priced / nights Priced nights beside all matching nights. Qualified nights Nights eligible for monetary totals. Known booked room-rate value / Qualified ADR Qualified value and value divided by qualified nights. Night share Row's share of clipped nights within the same currency and status. Known value share Row's share of qualified value within the same currency and status. Mean full LOS Mean whole-stay length, counting each room stay once per row. Mean receipt lead days Mean receipt-to-arrival interval among timed stays only. Timed / room stays Stays with usable receipt timing beside all room stays in the row. Supporting detail Column What it identifies Reservation ChannelRUSH reservation-version identifier; where linked, opens its supporting reservation. Room-stay ID Recorded room stay within the reservation. Channel room ID Recorded channel-side room identifier, or Unknown. Arrival / Checkout Whole-stay dates, not the clipped interval. Full LOS Whole-stay night count. Clipped nights Nights matching the selected interval and product filters. Price rows Despite the label, this is the count of qualifying priced nights, not a raw count of stored price records. Status Current Active or Canceled state. Rate-plan ID Cross-analysis only: matching nightly plan identity, Unknown, or Mixed nightly plans. Receipt lead days Cross-analysis only: usable first-retained-receipt interval, or Unknown. Value/date source version Cross-analysis only: current reservation version supplying dates and value. Currency / Known value Cross-analysis only: recorded currency and the stay's qualified value for matching nights. CSV field reference These are export headers, not additional editable controls. Fields can be combined below for explanation, but their names are shown exactly. Fields in every Booking Patterns CSV Header Meaning Contract Export definition identifier; useful when comparing files or contacting support. Period Selected or Comparison. PropertyId / FeedId Property and reservation-feed identities for that period. Start / End Inclusive stay-date bounds for that period. View los, seasonal or crossanalysis. Grouping month, weekday or weekend; seasonal grouping setting, not an extra dimension on other views. ExtractedUTC UTC extraction instant for this period's query. Not feed freshness. Currency / Status / Bucket Aggregate row's recorded currency, current status and grouping label. Missing currency can be an empty field. Bookings / RoomStays / RoomNights Row booking, room-stay and clipped-night counts. PricedNights / QualifiedNights / UnmappedNights Price-record coverage, monetary-qualified nights and current room-mapping gaps. UnmappedNights is also exported for cross-analysis although its visible aggregate table omits it. KnownBookedRateValue / QualifiedADR Qualified value and value per qualified night; blank when unavailable. KnownValueSharePercent Qualified value share for LOS and cross-analysis. Blank for Seasonal Trends. RevenueBasis / Coverage Explanations of amount qualification and capture limitations. RoomFilter / RatePlanFilter / CurrencyFilter Applied optional filters; blank means that filter is unrestricted. IncludeCanceled True includes canceled business separately; False means active-only. ComparisonAlignment none, calendar or weekday. A setting retained on LOS or cross-analysis does not mean a comparison was run. UnattributedInvalidStays Diagnostic invalid-date room-stay count, not a dated production measure. UnresolvedSourceIdentityRecords Feed records lacking booking identity; not necessarily distinct bookings or records from this stay period. RowState Captured for an aggregate row, or No captured rows for an empty-period metadata row. Additional fields in cross-analysis CSV Header Meaning PropertyTimeZone Property time-zone identifier used for receipt-to-arrival dates. TimingBasis Qualification text explaining first retained receipt, missing timing and original-sale limits. MeanFullStayLOS / TimedRoomStays / MeanFirstReceiptLeadDays Row's mean full LOS, timed stay count and mean usable receipt lead. RoomNightSharePercent Clipped-night share within the same currency and status. FullScopeDistinctBookings / FullScopeCanceledBookings Distinct bookings and canceled bookings across the entire selected scope. These totals repeat on rows; do not sum them. UnattributedBookings Diagnostic bookings without usable stay dates; not an additional dated total. RecoveredBookings Zero on captured cross-analysis rows: this view does not recover pre-cancellation versions. Blank on an empty-period metadata row. Zero is not proof that cancellation history is complete. CohortCancellationPercent / FullScopeCancellationPercent Unused here and blank; shared with other reports' export schemas. CanceledBookingValue / CurrentHotelRatePlanMapping Unused here and blank. These fields do not establish recovered canceled value or current rate-plan mapping. On an empty-period metadata row, row-specific counts, labels and amounts are blank. Scope-level diagnostics and cross-analysis distinct-booking totals can still be zero. Read RowState before interpreting either. Common problems - No captured stays: the dates, feed or exact product filters may exclude the records you expected. Expand Filters, verify the feed, clear optional filters and choose a relevant stay interval; click Update report. If expected bookings remain absent, contact support with the property, feed, date range and report URL. Do not assume the property had no business. - Nights appear but value or ADR is a dash: the feed may not qualify for monetary totals, or price/currency coverage is missing. Inspect priced and qualified nights. Do not replace unavailable values with zero or use another currency as a substitute. Ask support to investigate unexpected missing booking-engine coverage. - Unknown receipt interval or unexpectedly short lead time: retained receipt timing is missing, invalid or later than the original sale. Imports can also shorten it. Inspect the supporting stay; use a qualified original-sale source for decisions requiring original booking lead time. Escalate unexplained timing with the property, feed and relevant reservation reference, not guest/payment details. - Selected dates differ from a reservation's dates: the report clips nights to its selection, while LOS and Reservation show the whole stay. Compare the same units and check the product filters before escalating. - Prior-year dates or figures look different: inspect the actual comparison bounds, alignment, partial months and retained coverage. Equal-length prior-year production is not a historical pace comparison. Repeated runs cannot manufacture missing history. - Dates, currency or another filter is rejected: correct the identified field and run again. Supply both dates, keep the end on or after the start, stay within 366 days and use a recognized currency code. If a copied URL contains unsupported controls, reopen the report through its menu or use Reset report rather than editing unfamiliar query options. - CSV and screen disagree: check property, feed, dates, view, status, currency and extraction times. CSV includes the complete aggregate selection; the supporting detail is paged. If equivalent runs still disagree, provide both selections and their extraction times to support. Rerunning this report is a read operation, not an inventory resend or a reservation correction. Do not change operational data merely to make a report warning disappear.
Analyze cancellation cohorts and canceled booking value
Use Cancellation Analysis to compare currently active and canceled bookings for selected stay nights, inspect the supporting room stays and export the aggregate results. The dates select nights of stay—not dates when cancellations happened. This is a current, restated view of captured bookings. It is not a cancellation-event ledger, a historical on-the-books snapshot or a measure of refunded money or lost revenue. Before you start Select the intended property. You need access to that property and its reports; an Org Admin role is not required solely to use this report. Each run covers one property and one Reservation feed. The feed is the channel through which ChannelRUSH received the reservation, not necessarily its original selling source. Separate feeds can contain overlapping business; do not add their totals without reconciling those bookings. Viewing, rerunning and downloading this report do not cancel reservations, send inventory, issue refunds or repair missing history. Open and run the report 1. Select your property in the property selector. 2. Open Reports → Revenue Analytics → Cancellation Analysis. 3. Set Stay dates (through inclusive) to the nights you want to analyze. You can use Month to fill a whole calendar month. 4. Choose the Reservation feed you want to inspect. 5. If needed, expand Narrow by product or currency and enter a Channel room ID, Channel rate-plan ID or Currency. Leave these blank for all products and currencies within the selected feed. 6. Select View report. 7. Check the property, feed and stay dates printed above the results. The initial date range is 30 days beginning on the property's current local date. Both endpoints are included, but a reservation's checkout date is not a stayed night. You can select up to 366 days. After the first run, expand Filters, change the selection and select Update report. Changing an input does not itself reload the results. Apply your changes before using CSV or paging links; those links use the last loaded selection, not pending form edits. Cancellation Analysis filters with stay dates, reservation feed and optional product and currency inputs Expanded filters on a demo property. Optional product and currency fields are blank in this example. Understand which bookings are counted A stay cohort is the captured bookings with at least one matching room night inside your selected dates and filters. Active and canceled bookings are included and shown separately; there is no status checkbox to turn one group off. - Active: the booking's current captured status is active. A reinstated booking is active even if it was previously canceled. - Canceled: the booking's current captured status is canceled. Removing one room from an otherwise active booking does not make the booking canceled. - Canceled booking dates and value: when retained history contains an earlier active version, the report uses the latest such version as one complete source for the pre-cancellation stay and prices. It does not combine different versions to fill gaps. If that version lacks usable stay dates, older or current dates are not automatically substituted. - No earlier active version: current canceled dates can still identify matching stay nights, but canceled value remains unavailable. The headline cancellation rate is: Distinct currently canceled bookings with matching stay nights ÷ all distinct active and canceled bookings with matching stay nights × 100. Bookings without usable dates or an identifiable booking record cannot be included in that dated denominator. A booking can contribute several room stays and many nights without becoming several bookings in the headline total. The cohort can change when captured dates or statuses change. Rerunning the same URL later does not reproduce an immutable snapshot. Check the result Check these items before interpreting a percentage or value: 1. Confirm the printed property, feed and stay dates match your question. 2. Read the full-selection distinct booking and canceled-booking counts above the table. 3. Check each currency separately. The report does not convert currencies or supply a combined monetary total. 4. Expand Definitions and coverage to review the timing and monetary qualifications. 5. Check any Source exceptions outside dated totals warning before treating the selection as complete. 6. Expand Selected feed room-stay detail to examine the contributing stays. No captured stays match these filters means this selection returned no matching captured stays. It does not prove the property had no bookings or cancellations. A dash is unavailable data, not a measured zero. With no bookings in the denominator, the cancellation percentage is unavailable even when the count is zero. Cancellation Analysis empty result with selected scope, coverage and room-stay detail controls Empty demo result. The scope, export and explanation controls remain available; this image does not illustrate populated totals. Read monetary values conservatively Qualified monetary totals use ChannelRUSH Booking Engine room rates as booked, including any embedded tax but excluding separately stored taxes and fees. Other feeds may have priced nights without qualified monetary totals. A qualifying night needs one unambiguous, nonblank stored nightly price and a known currency. Canceled value also needs the retained pre-cancellation source described above. A recorded zero price is a price; an absent, null or conflicting price is not zero. Canceled booking value is the qualified pre-cancellation room-rate value of the selected nights. It is not proven lost revenue, a refund, a cancellation fee, a no-show charge or an incremental financial loss. A partially selected stay contributes only its matching nights' value. Read timing and coverage correctly Receipt lead days measure the interval from the first retained receipt to arrival in the property's local time. This is not the OTA's original sale time or the cancellation time. Imports and missing history can shorten the interval. Missing receipts, receipts after arrival and timestamps without a verified offset remain unknown. The mean uses only timed room stays. Extracted identifies when that report query ran. It does not certify when the channel last supplied data or that its history is complete. Read the displayed offset with the timestamp. The exception warning can name invalid room stays, bookings without any usable stay dates and records without a booking identity. These are outside the dated totals; some are feed-wide rather than limited to your selected dates or product filters. They can overlap. Do not add them to the cohort counts to reconstruct a property-wide total. Inspect supporting room stays Expand Selected feed room-stay detail (N matching stays). It shows at most 100 stays per page, ordered by arrival and then reservation and room-stay identifiers. Use Previous page and Next page when available. The headline totals and aggregate table still cover the full selection. The detail identifies whether dates and value came from a current or pre-cancellation reservation version. “Pre-cancellation” means an earlier retained active source; it does not mean the booking was reinstated or money was recovered. Reservation identifiers in this report are displayed as text. To investigate the reservation itself, use the separate reservation search workflow described in Review reservation details, keeping the property and feed in mind. Do not treat an older value/date source as the current reservation status. Inventory and restriction context opens the property's rates and availability report. It does not carry this report's dates, feed or product filters; select the intended scope again there. It does not perform an inventory update. Export or open a separate window 1. Apply any pending changes with Update report. 2. Select CSV beside Download. 3. Check the exported property, feed, dates and extraction timestamp before comparing it with another run. The CSV contains the full aggregate selection, not the individual room-stay detail page. It is a fresh read, so newly captured changes can make it differ from an earlier on-screen result. The filename follows cancellation-YYYY-MM-DD-YYYY-MM-DD.csv. New window opens the current report selection in a separate, reduced-navigation window. A later filter submission or paging action can return that window to the normal application layout; the report remains a read-only view. Filter reference Field What it does Accepted values and example Month Fills the stay-date range with a whole calendar month. It is a shortcut, not a separate grouping. Choose the required month, then run or update the report. Stay dates (through inclusive) Selects nights inside the requested range; checkout is excluded. Supply both dates in order, spanning no more than 366 days. A stay checking out on the first selected date contributes no nights. Reservation feed Selects one captured reservation source for the current property. Check the selected name rather than assuming the default is the feed you want. A retained-history URL can name a feed no longer connected to the property. Channel room ID Narrows to the exact recorded channel room identifier. Blank means all; up to 200 characters. Use the ID, not the room name, and avoid added spaces. Channel rate-plan ID Narrows matching nights to the exact recorded channel plan identifier. A night's plan takes precedence over the room-level plan when present. Blank means all; up to 200 characters. This can retain only part of a stay when its nightly plans differ. Currency Narrows to one recorded currency without conversion. Blank means all; surrounding spaces are removed and letters uppercased. For example, usd becomes USD . Maximum 10 characters; entering a value does not establish that the feed contains it. Room and rate-plan identifiers are exact matches, including case and spaces. Product filters narrow the cohort; they do not introduce product-grouped rows. This report groups its Stay cohort by currency and current status, not month, channel source or cancellation-event date. On-screen column reference Aggregate table Column Meaning Cohort Stay cohort , defined by the selected matching nights. Currency Recorded currency; Unknown when absent. Status Current Active or Canceled classification. Bookings Distinct bookings represented in this currency/status row. Use the independently distinct headline total for the full selection. Room stays Distinct contributing room stays; one booking can have several. Clipped nights Matching nights within the selected date and product scope. Priced / nights Nights with one unambiguous stored price, followed by all matching nights. This is not necessarily monetary qualification. Qualified nights Nights eligible for the monetary totals described above. Booked value / canceled booking value Qualified room-rate value of the selected nights, separated by status. A dash is unavailable. Qualified ADR Qualified value divided by qualified nights—not all matching nights. Night share Share within the same feed, currency and status . With one Stay cohort bucket, a populated status row normally shows 100%; this is not the canceled share of active plus canceled nights. Known value share Share of qualified known value within the same currency and status. Unknown amounts are excluded. Normally 100% for this single bucket when the denominator is positive; unavailable otherwise. Mean full LOS Average full arrival-to-checkout length, counting each represented room stay once. It can exceed the selected interval because the nights, not the full LOS, are clipped. Mean receipt lead days Average first-retained-receipt-to-arrival interval for timed room stays only. Timed / room stays Stays with a usable receipt interval, followed by all represented stays. Cohort cancellation rate Canceled bookings divided by active plus canceled bookings within the same currency/cohort. It is repeated on the active and canceled rows; do not add the percentages. Bookings using pre-cancellation versions Bookings whose selected dates/value source is an earlier retained active version, not reinstated bookings or money recovered. Room-stay detail table Column Meaning Reservation Current stored reservation-version identifier. Room-stay ID Identifier of the contributing room stay in its selected source version. Channel room ID Recorded channel room identifier; Unknown when missing. Arrival Full stay arrival date. Checkout Full stay departure date; not counted as a stayed night. Full LOS Full stay length in nights. Clipped nights Matching nights retained by your date and product selection. Price rows Count of unambiguously priced nights, despite the column's name; not a count of all raw price records. Status Current booking classification, which can be Canceled while its date/value source is an older active version. Rate-plan ID Recorded nightly plan, Mixed nightly plans when several remain, or Unknown when absent. Receipt lead days The qualified first-receipt interval, or Unknown . Value/date source version Reservation version supplying the stay and value, marked current or pre-cancellation . Currency Source version's recorded currency, or Unknown . Known value Qualified room-rate value for this stay's matching nights; a dash is unavailable. CSV field reference Numbers use an invariant decimal format. Empty cells generally mean unavailable or not applicable, not zero. A real zero remains numeric zero. Text that could be interpreted as a spreadsheet formula is protected with an apostrophe. The following are the exact export headers, in file order. Several columns belong to the shared report format and are not separate controls or measurements on this page. Header Meaning in Cancellation Analysis Contract The export contract identifier, captured-focused-production-v1 . Period Selected ; this page does not load a comparison period. PropertyId Selected property's identifier. FeedId Selected reservation-feed identifier. Start First included stay date, yyyy-MM-dd . End Last included stay date, yyyy-MM-dd ; checkout remains excluded. View cancellation . Grouping Shared configuration metadata, normally month . It does not make this report monthly grouped. ExtractedUTC Extraction timestamp with its explicit offset; not channel-data freshness. Currency Row's recorded currency; blank when no row or no known currency. Status Row's Active or Canceled classification. Bucket Stay cohort . Bookings Distinct bookings in the row. RoomStays Distinct room stays in the row. RoomNights Clipped matching nights. PricedNights Nights with one unambiguous stored price. QualifiedNights Nights eligible for monetary totals. UnmappedNights Nights without exactly one current property-room mapping target. This is separate from monetary qualification. KnownBookedRateValue Qualified selected-night value for either status. QualifiedADR Qualified value divided by qualified nights. KnownValueSharePercent Qualified known-value share within the same currency/status. RevenueBasis Text explaining which money qualifies and what is excluded. Coverage Text explaining the limits of captured-feed coverage. RoomFilter Applied exact channel-room filter; blank means all. RatePlanFilter Applied exact channel-plan filter; blank means all. CurrencyFilter Applied normalized currency filter; blank means all. IncludeCanceled True : both active and canceled bookings participate. ComparisonAlignment Shared metadata, normally none ; there is no comparison result here. UnattributedInvalidStays Invalid-date room-stay exception count, outside dated totals. Not a count of all excluded bookings. UnresolvedSourceIdentityRecords Feed records without a usable booking identity. This can include multiple versions and is not a distinct-booking count. RowState Captured , or No captured rows for an empty selection. PropertyTimeZone Property's IANA time-zone name used for receipt timing. TimingBasis Text describing first-retained-receipt timing and its limitations. MeanFullStayLOS Average full stay length over represented room stays. TimedRoomStays Stays with usable receipt timing. MeanFirstReceiptLeadDays Average receipt interval over timed stays only. RoomNightSharePercent Matching-night share within the same currency/status. CohortCancellationPercent Currency/cohort cancellation percentage. FullScopeDistinctBookings Independently distinct booking total for the entire selection; repeated on each row. FullScopeCanceledBookings Entire selection's distinct currently canceled bookings; repeated on each row. RecoveredBookings Row's bookings using pre-cancellation versions. “Recovered” refers to historical attribution, not money or reinstatement. UnattributedBookings Feed-wide bookings with no usable dated stay in the selected source version; not restricted to the report's period and not necessarily canceled. FullScopeCancellationPercent Full-selection cancellation percentage; repeated on each row. CanceledBookingValue Repeats qualified value only for a Canceled row; blank for Active or unavailable amounts. Do not add it to KnownBookedRateValue. CurrentHotelRatePlanMapping Not applicable to Cancellation Analysis and left blank. This does not diagnose missing rate-plan mappings. Do not sum repeated full-scope counts or exception counts across rows. Do not add the repeated cancellation percentages. An empty export still contains one metadata row with RowState = No captured rows. Its aggregate measures are blank, while full-scope counts and exception counts remain present. The row is not a booking, and its timestamp is not evidence of a fresh vendor observation. Common problems - Nothing appears before the first run: select View report. Opening the page alone displays the criteria, not a completed query. - The results still show the old dates or feed: expand Filters and select Update report. Check the printed scope afterward; changed inputs alone are not a loaded result. - No captured stays match: check property, feed and dates, then clear exact product/currency filters or widen the date range within the limit. If expected bookings still do not appear, ask support to investigate capture/history coverage. Empty results are not proof of zero business. - A dash appears for value, ADR or a percentage: inspect qualified nights, feed and retained-history coverage. Other-feed monetary values, missing pre-cancellation prices and an absent percentage denominator can legitimately be unavailable. Do not replace the dash with zero in analysis. - Night share is 100% on both Active and Canceled rows: each share has its own status denominator. Use Cohort cancellation rate, not Night share, for the canceled-booking percentage. - A canceled booking is missing or has unknown value: its selected prior active source may lack usable dates/prices, or there may be no retained active version. Check the detail and exception warning. Do not assume missing history means no cancellation, and do not resend or alter reservations to populate this report. - “Provide both dates” or an ordered-range warning: fill both dates, put the start before or equal to the end, and keep the inclusive range within 366 days. Then update the report. - Invalid product/currency filter or detail-page warning: shorten the filter to the supported length, or reopen the report from the menu to leave an altered/stale paging URL. Reapply the intended scope. - CSV and screen disagree: compare property, feed, dates, filters and extraction times. The export rereads current data and contains aggregates, not just the visible detail page. If equivalent scopes still disagree, provide both selections and extraction times to support. For unresolved issues, provide the property, feed, stay-date range, relevant filters, extraction time with its offset and the exact warning. Keep guest names, contact details, payment details and passwords out of screenshots and messages. Related - Analyze booking patterns, length of stay and seasonal trends - Review reservation details
Compare rate-plan production and value
Use Rate Plan Performance to compare captured bookings, room nights and qualified booked room-rate value by channel rate plan, inspect the supporting stays and download the aggregate results. The dates select nights of stay—not booking dates or cancellation dates. This report shows the current captured booking state. It is not a historical on-the-books snapshot, posted revenue or proof of complete property production. Before you start - Select the intended property. You need access to that property and its reports. - Choose the reservation feed you want to analyze. A feed is the channel through which ChannelRUSH received a reservation; it is not necessarily the original selling source. - Have the exact channel product IDs if you want to narrow the report. Standard hotel rate-plan names and IDs are not substitutes for channel rate-plan IDs. Viewing, updating and downloading this report do not change reservations, send inventory or repair missing history. Run the report 1. Select your property in the property selector. 2. Open Reports → Revenue Analytics → Rate Plan Performance. 3. Set Stay dates (through inclusive). Use Month to fill a whole calendar month, or choose your own date range. Both endpoints are included; the range can contain at most 366 days. 4. Choose a Reservation feed. 5. Leave Comparison feed (kept separate) at No comparison, or select a different feed. 6. If needed, expand Narrow by product or currency. Enter a Channel room ID, Channel rate-plan ID or Currency. Leave these blank to include all matching products and currencies in the selected feed. 7. Select View report. 8. Check the property, feed and stay dates above the results before interpreting the figures. Rate Plan Performance filters with stay dates, reservation feed, a separate comparison feed and optional product and currency filters Use the filters to define one property's captured stay-night selection. A comparison feed remains separate. The Filters panel collapses after a successful run. Reopen it to change your selection, then select Update report. Changing a field alone does not update the displayed results. Apply your changes before downloading or opening a new window. A new report normally starts with a 30-day period beginning on the property's current local date. An existing report link can carry explicit dates and filters, so check the displayed selection rather than assuming the default. Check and interpret the result The report shows the selected feed first. If you requested a comparison, a separate Comparison feed section follows. Each section has its own full-selection distinct booking count, canceled booking count and current-cohort cancellation rate. The table separates rows by channel rate-plan identity, currency and current status. Active and canceled business are always included and shown separately. There is no active-only switch on this report. Stay nights, bookings and room stays are different measures - Clipped nights are the room nights inside your selected date range. The arrival night counts; the checkout date does not. A stay can contribute even if it arrived before the first selected date. - Full LOS is the length of the whole room stay, including nights outside your selection. - Bookings counts distinct bookings within a row. A booking with multiple rooms or multiple nightly rate plans can contribute to several rows. - Room stays counts the separate room stays represented in a row. One multi-room booking can contain several room stays. Do not sum the table's booking counts to reconstruct the full-selection distinct booking count. The latter counts each matching booking once. Room-stay counts and stay-based averages can also overlap across rate plans when a room stay uses more than one plan. Money is qualified, not assumed This report qualifies monetary totals from ChannelRUSH Booking Engine nightly room rates when a currency is recorded and exactly one nightly price record with a nonblank price is available for the stay night. Booked room-rate value includes any tax already embedded in that rate. Separately stored fees and taxes are excluded. Other feeds can contribute bookings, room stays, nights and price coverage without qualifying for monetary totals. A price being present does not make it comparable revenue. - Qualified ADR is known qualified booked room-rate value divided by qualified nights—not by all clipped nights. - Night share uses the selected feed's matching nights within the same currency and status. - Known value share uses the selected feed's qualified known value within the same currency and status. It excludes unknown amounts and is unavailable when the qualifying total is not positive. - Currencies remain separate. There is no currency conversion or combined currency total. - A dash means unavailable, not zero. A recorded zero price is different from a missing price and can qualify when the other conditions are met. These values are not settled revenue, profit, refunds, commissions or proven lost revenue. A small priced or qualified subset can produce an ADR or value share that does not represent all captured nights. Rate-plan identities and mappings The report attributes each night to its recorded nightly channel rate-plan ID. If there is no nightly ID, it falls back to the room stay's rate-plan ID. Conflicting nightly IDs remain Unknown rate plan rather than being assigned to a guessed plan. Current hotel rate-plan mapping shows the current standard hotel rate-plan target for each contributing channel room. It can show a target ID and name, No current target or Ambiguous current targets. A missing or ambiguous target is a finding to investigate, not automatically a setup fault. Mappings reflect current settings. Editing a mapping can change this explanation on a later run; it does not establish which mapping existed when the booking was made. Rate-plan mapping and room-mapping coverage are separate measures. Cancellation rates and receipt timing The Cohort cancellation rate is currently canceled bookings divided by all active and canceled bookings with matching stay nights in the same rate-plan and currency bucket. It is repeated on that bucket's active and canceled rows. The full-selection cancellation rate uses independently distinct bookings across the whole selection. These are current stay-cohort rates, not the percentage of cancellations that occurred during your selected dates. Reinstated bookings are active. Removing one room from an otherwise active booking does not make it a canceled booking. Rate Plan Performance uses the current captured reservation version. A canceled version without usable stay dates cannot enter its dated rate-plan totals. Cancellation Analysis is a separate report that can use retained pre-cancellation stays; its totals need not match this report. Mean receipt lead days measures the first retained ChannelRUSH receipt to arrival in the property's local time. It is not the original booking lead time. Imports and missing earlier history can shorten this interval. Missing receipts, receipts after arrival and timestamps without a verified UTC offset are unknown. The mean includes only timed room stays; use Timed / room stays to check coverage. Compare two feeds safely Choose a different Comparison feed (kept separate) and select Update report. Both sections use the same stay dates and the same raw room, rate-plan and currency filters. The same product ID is applied independently to each feed. It does not establish that the products are equivalent. If one feed has no matching ID, that section can be empty. Clear product filters for a broad comparison, or run each feed separately using its own IDs. The report does not deduplicate overlapping bookings across feeds, combine their totals or calculate matched-product uplift. Treat each section as its own captured scope. Do not add feed totals without separately reconciling overlap. To see the other feed's supporting stays, select Open the comparison feed's room-stay detail and export. This changes that feed into the selected Reservation feed, retains the dates and product/currency filters, removes the comparison and starts at the first detail page. It does not download a detail file. Use Download CSV afterward if you want that feed's aggregate export. Re-select a comparison if you want to return to a two-feed view. Inspect the supporting room stays Expand Selected feed room-stay detail beneath the results. Its heading gives the full count of matching room stays. The table shows at most 100 room stays per page, ordered by arrival and then reservation and room-stay identifiers. Use Next page or Previous page when available. These controls change the detail page, not the full aggregate scope. The supported detail page range is 1–10,000. If a copied link opens a page without detail rows, rerun the filters to return to the first page. The detail covers the full selected-feed selection, not a clicked rate-plan row. It can show Mixed nightly plans where the included nights use different plans. If you narrow by a rate-plan ID, its clipped nights and known value cover only the matching nights; full LOS still describes the whole room stay. Download or open another view - Download CSV downloads the full aggregate table, not only the current detail page. With a comparison selected, the file contains both feeds, identified by Period and FeedId. It does not export the room-stay detail table. - New window opens another copy of the report with the applied selection. It is not an Excel view or a saved historical snapshot. - Definitions and coverage expands the report's formulas, timing and monetary qualifications, current filters and coverage limits. - Inventory and restriction context opens the property's Rates & Availability Report. It carries the property, not this report's dates, feed or product/currency filters. Set and check that report's own selection before comparing results. Inventory or restrictions alone do not establish why a rate plan did or did not sell. Each report request or download reads current captured data. A later download or page can differ if reservations or mappings have changed. The extraction timestamp tells you when that result was read; it does not prove that the feed is complete or recently received every booking. Filter reference Field or control What it does and accepted values Filters Opens or collapses the filter form. The collapsed summary shows the stay range and selected feed; “narrowed” means a product or currency filter is in use. Open the panel to check the exact filters and comparison feed. Month Shortcut that fills both date endpoints for one calendar month. It does not group the results by month or run the report. A custom range need not have a month selected. Stay dates (through inclusive) Required start and end dates for the on-screen form, in the displayed date format. The end cannot precede the start. Maximum 366 inclusive days. These select stay nights, excluding checkout. If the enhanced date picker is unavailable, the form uses Start date and End date instead. Reservation feed One feed for the selected property. The initial choice uses an available connected feed when possible; check it before running. An existing link can retain a previously selected feed even if it is no longer connected. Comparison feed (kept separate) No comparison , or a different feed. The same feed cannot be selected for both roles. The comparison uses the same dates and raw product/currency filters, without cross-feed matching or deduplication. Narrow by product or currency Expands the optional filters. It opens automatically when one of those filters is in use. Channel room ID Exact recorded channel room ID, up to 200 characters. Blank means all rooms within the other filters. It is not a room-name search; case and spaces in the supplied ID matter. Channel rate-plan ID Exact attributed nightly channel rate-plan ID, up to 200 characters. Blank means all plans, including unknown identities. It is not a standard hotel rate-plan name or mapping filter. Case and spaces in the supplied ID matter. Currency Recorded currency code, such as USD , up to 10 characters. Surrounding spaces are removed and letters are converted to uppercase for matching. Blank includes all currencies, including unknown currency; it does not combine or convert them. View report / Update report Applies the filters and reads the current report. Use View report initially and Update report after a result has loaded. Active and canceled bookings remain included. Aggregate column reference The following columns appear for both the selected-feed and comparison-feed tables when rows are available. On-screen column Meaning Channel rate-plan identity Rate plan … for a recorded attributed channel ID, or Unknown rate plan . This is the grouping identity, not a standard hotel plan name. Current hotel rate-plan mapping Current target ID/name per contributing channel room, or No current target / Ambiguous current targets . It is not historical mapping evidence. Currency Recorded currency for the row; Unknown when missing. Status Active or Canceled , based on the current captured booking status. Bookings Distinct matching bookings in this rate-plan, currency and status row. Non-additive across plans. Room stays Distinct matching room stays in this row. A multi-plan stay can appear in more than one plan row. Clipped nights Matching room nights inside the selected dates, excluding checkout. Priced / nights Nights with exactly one nightly price record with a nonblank price, followed by all clipped nights. Duplicate or missing nightly price rows do not qualify as priced. Qualified nights Priced nights eligible for monetary totals: booking-engine feed, known currency and a usable nightly price. Mapping gaps do not by themselves remove a night from this monetary count. Known booked room-rate value Sum of qualified nightly booked room rates for this row. A dash means unavailable. Qualified ADR Qualified known value divided by qualified nights. A dash means no qualifying denominator. Night share Percentage of matching nights in the same feed, currency and status contributed by this row. Known value share Percentage of qualified known value in the same feed, currency and status contributed by this row. Unknown prices are excluded; an unavailable share is not zero. Mean full LOS Average whole-stay length, counting each room stay once within this row rather than once per night. Includes nights outside the selected dates. Mean receipt lead days Average first-retained-receipt-to-arrival interval among this row's timed room stays, using the property timezone. Timed / room stays Room stays with a usable receipt interval, followed by all room stays in the row. Cohort cancellation rate Canceled booking count divided by active plus canceled booking count for the same rate plan and currency. The same rate appears on both status rows. The distinct booking count, canceled booking count and cancellation rate above each table apply to the full filtered feed selection. The extraction line identifies that feed, the read time and the report definition version. If a Source exceptions outside dated totals message appears, inspect it separately from production totals: - Invalid room stays have missing or invalid arrival/checkout dates and cannot produce valid nights. The count follows the applicable room/currency selection, not a reliable stay-date cohort or rate-plan attribution. - Bookings without any usable stay dates cannot be assigned to the period. This is a feed-level exception count, not the selected rate-plan's canceled booking count. - Records without a booking identity cannot be safely grouped into distinct bookings. This feed-level count is records, not distinct bookings, and can include retained versions. These exceptions can overlap. Do not add them to dated totals or treat them as a count of missing sales in the selected period. Room-stay detail column reference On-screen column Meaning Reservation ChannelRUSH identifier for the current captured reservation version represented by the stay. Do not confuse it with a channel confirmation number. Room-stay ID Identifier for the individual captured room stay. Separate rooms in a booking can have separate rows. Channel room ID Recorded channel room identity, or Unknown . Arrival Full stay's arrival date, displayed as yyyy-MM-dd . Checkout Full stay's checkout date, displayed as yyyy-MM-dd ; checkout does not contribute a night. Full LOS Whole room-stay length, not just the nights within the report period. Clipped nights Matching nights inside the selected dates and product filters. Price rows Count of clipped nights with exactly one nightly price record with a nonblank price. Despite the label, it is not the count of all underlying price records. Status Current Active or Canceled booking status. Rate-plan ID Attributed plan for the included nights, Mixed nightly plans when those nights have more than one identity, or Unknown when the identity is blank. Receipt lead days First retained receipt to arrival in the property timezone, or Unknown . Value/date source version Reservation version supplying the stay dates and known value. Rate Plan Performance uses the (current) version; it does not recover a pre-cancellation version. Currency Recorded currency, or Unknown . Known value Qualified booked room-rate value for the matching nights of this stay. A dash means unavailable, not zero. CSV field reference The CSV uses a shared aggregate schema. It contains metadata and coverage fields in addition to the visible table columns. Dates use yyyy-MM-dd; ExtractedUTC includes its UTC offset. Monetary fields are numbers, with currency in a separate column. Percentage fields contain percentage values rather than fractions. A normal row has RowState = Captured. If a feed has no aggregate rows, the file still contains a metadata row with RowState = No captured rows; row-level counts and measures are blank. Full-scope counts can be zero, while percentages with no denominator remain blank. This is not a zero-valued rate-plan row. Scope and metadata headers Exact CSV header Meaning Contract Report definition identifier: captured-focused-production-v1 for this report. Period Selected or Comparison . Here “Comparison” means another feed for the same dates, not a prior-year period. PropertyId Property identifier for the result. FeedId Reservation-feed identifier for this row's section. Start First included stay date. End Last included stay date. Checkout remains excluded from each stay. View rateplan for Rate Plan Performance. Grouping Shared-schema setting, normally month . Unused for this report's grouping: rows are grouped by rate-plan identity, currency and status, not month. ExtractedUTC Time the feed's result was read, not reservation receipt time or a completeness watermark. RevenueBasis Explanation of which booked room-rate amounts qualify and which taxes/fees are excluded. Coverage Captured-feed coverage warning; property-wide completeness and historical coverage are unverified. RoomFilter Applied channel room ID; blank means no room narrowing. RatePlanFilter Applied channel rate-plan ID; blank means no plan narrowing. CurrencyFilter Applied normalized currency filter; blank means all currencies. IncludeCanceled True for this report. Active and canceled rows remain separate. ComparisonAlignment Shared-schema period-alignment setting, normally none . Unused for the feed comparison here: it does not describe matched products, prior-year alignment or source overlap. RowState Captured or No captured rows . Check this before interpreting blank row measures. PropertyTimeZone Property timezone used for receipt-to-arrival timing. TimingBasis Written qualification of the first-retained-receipt interval and unknown timing. Row identity and measure headers Exact CSV header Meaning Currency Row currency; blank means unknown on a captured row. Status Active or Canceled . Bucket Displayed channel rate-plan identity, such as Rate plan … or Unknown rate plan . Bookings Distinct bookings in this row, not an additive full-report total. RoomStays Distinct room stays in this row. RoomNights Clipped matching room nights. PricedNights Nights with exactly one nightly price record with a nonblank price. QualifiedNights Nights qualifying for monetary totals. UnmappedNights Nights whose channel room does not resolve to exactly one current standard room target. This measures room mapping , not the rate-plan target shown in CurrentHotelRatePlanMapping . It is not a count of unsent bookings. KnownBookedRateValue Qualified known booked room-rate value; blank if unavailable. QualifiedADR Qualified value divided by qualified nights; blank without a qualifying denominator. KnownValueSharePercent Row share of qualified known value within the same feed, currency and status; blank when unavailable. MeanFullStayLOS Average full room-stay length, counted once per stay within this row. TimedRoomStays Room stays with a usable first-receipt interval. MeanFirstReceiptLeadDays Average receipt-to-arrival days for timed room stays only. RoomNightSharePercent Row share of nights within the same feed, currency and status. CohortCancellationPercent Current canceled-booking share for the same rate-plan and currency bucket, combining its active and canceled counts. RecoveredBookings Shared recovery field. Unused here: zero on captured rate-plan rows because this report uses current versions, and blank on an empty metadata row. It does not prove that cancellation history is complete. CanceledBookingValue Shared Cancellation Analysis field. Unused here and blank , including canceled rate-plan rows. Read KnownBookedRateValue for this report's qualified current-version amounts; do not fill this placeholder with a guessed loss. CurrentHotelRatePlanMapping Current hotel rate-plan target explanation per contributing channel room, including missing or ambiguous targets. Full-scope and exception headers These values repeat on aggregate rows for the relevant feed. Do not sum the repeated values down the CSV. Exact CSV header Meaning UnattributedInvalidStays Invalid room-stay date count described under source exceptions. Not dated production and not necessarily attributable to the requested rate plan. UnresolvedSourceIdentityRecords Feed-level records without a usable booking identity; not distinct bookings or a period-specific count. FullScopeDistinctBookings Independently distinct bookings across this feed's full filtered selection. FullScopeCanceledBookings Independently distinct canceled bookings in that full selection. UnattributedBookings Feed-level current bookings without any usable stay dates. They cannot be assigned to the selected period; this count is not narrowed into a reliable product/date cohort. FullScopeCancellationPercent Full-selection distinct canceled bookings divided by full-selection distinct bookings. Blank if there are no matching bookings. Common problems Symptom What to check and what to do No captured stays match these filters Confirm the property and feed. Widen stay dates within the 366-day limit, clear product/currency filters and select Update report . Missing captured history does not establish zero property business. If you expect known captured stays to match, ask support to check the scope. Comparison is empty while the selected feed has rows Raw product IDs are applied independently. Clear those filters or inspect the other feed using its own IDs. Do not assume that matching text identifies equivalent products. Select a different comparison feed, or none. Choose another comparison feed or No comparison , then run the report again. Dates are rejected, or only one endpoint is present Set both dates, put the end on or after the start, and keep the inclusive range at 366 days or fewer. Rerun the form rather than editing a copied report URL. Invalid product or currency filter. Keep room and rate-plan IDs within 200 characters and currency within 10. Use the exact recorded IDs; remove unintended spaces from product IDs. Counts are present but value or ADR is a dash Check the feed, currency and Priced / nights / Qualified nights coverage. Other feeds' amounts do not qualify for monetary totals here. Do not replace unknown amounts with zero. A rate plan is unknown or has no clear current target Inspect the recorded nightly IDs, channel room and current mapping. Do not edit a mapping solely to make an analytical row disappear. Ask support if the identity or target cannot be reconciled. Booking counts do not add up to the headline total A booking can span rate plans. Use the independently distinct full-selection count; do not sum per-plan booking counts. Cancellation Analysis shows different canceled business Rate Plan Performance uses current versions; Cancellation Analysis can recover retained pre-cancellation stays. Check report definitions, dates, filters and extraction times before treating the difference as an error. Receipt lead days are unknown or unexpectedly short Check timing coverage. Missing history, imports or post-arrival receipts can prevent a usable original-length interval. Do not treat receipt timing as the original sale date. Property timezone is required for receipt timing. or Property timezone is not recognized. Ask your administrator or support to verify the property's timezone. Repeated report runs cannot repair that setting. Detail is empty on a later page Reopen Filters and select Update report to return to page one. The current matching stays may have changed since the earlier request. The CSV contains blank measures or repeated totals Check RowState and the shared unused fields above. A metadata-only empty row is not a captured zero-value row, and full-scope/exception figures must not be summed across rows. For unresolved issues, provide the property, feed, stay-date range, applied filters, extraction time with its offset and exact warning. Avoid guest names, contact details, payment information and passwords in screenshots or messages. Related - Analyze cancellation cohorts and canceled booking value - Choose filters for a rates and availability report
Analyze reservation trends with the Performance Report
Use the Performance Report to compare captured reservation activity, whole-stay room nights and after-tax booking amounts by receipt date or arrival date. This is a booking analysis, not a statement of earned revenue or complete property production. The two tabs select different groups of reservations. They can include the same booking, so do not add their totals together. Before you start Select the intended property. You need access to that property's reports. The report uses reservations already captured in ChannelRUSH; it does not retrieve missing bookings from a channel, resend reservations or change inventory. The channel list offers connections configured both to send inventory and to receive or monitor reservations. A historical or receive-only feed may not appear. All channels means all offered choices when the list contains choices—not necessarily every feed with stored reservations. Run the report 1. Select your property in the property selector. 2. Open Reports → Overview → Performance Report. 3. Set Date Range. A fresh visit normally starts with the property's current calendar month. Use Month / Year to fill a complete month, or select your own start and end dates. 4. Open Channels and check the feeds you want. All offered channels start selected. Select all selects or clears the offered list; when choices are available, leave at least one checked. 5. Select View Report. 6. Check the property, dates and Reservation feeds line under How to read this report. 7. Choose Currency for revenue and ADR, if results are available. 8. Select By Version Receipt Date or By Arrival Date to choose the chart basis. Performance Report filters showing Month / Year, the full date range, Channels, View Report and Cancel The controls stack on a narrow screen. Selecting dates or channels does not run the report; select View Report. After a data-bearing run, Filters collapses. Reopen it to change dates or channels, then select View Report again. Changing a filter alone leaves the previous results in place. If you type dates, leave the field and check both displayed endpoints before submitting; use the displayed date format rather than pasting an ISO date string. Changing the currency or chart tab updates the already loaded result immediately. It does not fetch newer reservations. A new report run starts on By Version Receipt Date again. Cancel returns to Reports; it is not a reset or undo control. Check what the result represents By Version Receipt Date This group contains the latest captured version of each reservation whose receipt timestamp falls in the selected period. A later modification or cancellation can change that version and move the reservation out of an earlier receipt period. Reservations Booked therefore does not mean only original new sales made during the period. Receipt can differ from the channel's original sale time. The report is not a historical “as of” snapshot or a booking-pickup calculation. By Arrival Date This group contains reservations with at least one room arriving in the selected period. It includes the whole reservation's rooms and nights, including nights outside the selected dates. For a multi-room booking with different arrival dates, the arrival charts use the first captured room's arrival date, which need not be the room that matched your date range. A plotted arrival can therefore fall outside the selected period. If the first room has no arrival date, the chart uses the reservation version's receipt date instead. What both tabs include - Noncanceled reservations contribute to ordinary booking counts, nights, amounts and patterns. Canceled reservations are counted separately in the summary. - Room nights cover each room's whole stay: checkout minus arrival, with checkout not counted as a night. Missing or nonpositive stay lengths do not add nights. - The same reservation can qualify for both tabs. Their totals are separate views, not quantities to combine. - A result shows captured data for the selected property and feeds. It does not establish that every booking was received or delivered successfully. - There is no displayed report extraction timestamp or latest channel-update timestamp. Rerun View Report to read current captured data; a later run can differ. The receipt filter uses the property's timezone to select its date window. Do not assume the daily chart labels or Receipt to Arrival (Days) use the same local-day boundary. For exact near-midnight reconciliation, ask support to check the receipt timestamp and property timezone rather than treating a one-day difference as a missing reservation. Read money and currency safely Currency for revenue and ADR changes monetary cards and charts only. Counts, room nights, length of stay and other nonmonetary measures continue to include all selected currencies. There is no currency conversion or combined-currency total. The initial currency is an available recorded currency, not necessarily your property's preferred currency. Check it on every run. A currency can appear because it has only arrival-period business or only canceled bookings; its receipt-based revenue card can legitimately be zero. Currency unknown means the reservation's currency was missing. These bookings remain in the counts, but monetary cards show a dash and monetary charts have no amounts. It is not an “all currencies” option. Revenue uses captured after-tax amounts. Reservation totals drive the summary and channel/time charts; room totals drive room-type charts. These amounts can differ, and missing amounts are treated as zero. A zero is therefore not proof of a free stay or no monetary value. Amount definitions can differ between channels; the report does not establish settled revenue, commissions, profit, refunds or accounting revenue for nights within the range. ADR divides the selected currency's captured amount by that currency's room nights. Do not divide a selected-currency revenue card by the all-currency Room Nights card to reproduce ADR. Summary card reference The cards do not switch their date basis when you change tabs. Only Arrivals in Period and Room Nights (Arrivals) use the arrival group; the other cards use the receipt group. Card What it means Room Nights Whole-stay nights across all rooms in noncanceled receipt-period reservations, across all currencies. ADR Selected-currency after-tax receipt-period amount divided by that currency's whole-stay room nights, rounded to two decimals. Zero when there are no contributing nights; a dash when currency is unknown. Revenue Selected-currency after-tax receipt-period reservation totals, excluding canceled bookings. The card displays whole currency units; missing amounts can contribute zero. Room Nights / Booking All-currency receipt-period room nights divided by noncanceled reservations, rounded to one decimal. This is nights per booking across all its rooms, not average stay length per room. Receipt to Arrival (Days) Average calendar-day interval from the selected version's receipt to its first room's arrival. Missing first-room arrival is omitted; negative intervals count as zero. Rounded to one decimal. It is not proven original-sale lead time. Cancellation Rate Currently canceled receipt-period reservations divided by all receipt-period reservations, as a percentage rounded to one decimal. This is not the percentage of stay nights canceled or a history of cancellation events. Reservations Booked Noncanceled reservations whose latest captured version was received in the selected period. A multi-room booking counts once. Arrivals in Period Noncanceled reservations with at least one room arriving within the range. This counts reservations, not arriving rooms. Room Nights (Arrivals) Whole-stay room nights across all rooms in the arrival group, including nights outside the range. Cancellations Currently canceled reservations whose latest captured version falls in the receipt period. A report containing only cancellations can show a cancellation count and rate while its ordinary charts remain empty. A report with arrival business but no receipt-period business can show arrival totals alongside zero receipt cards. Neither is automatically a loading failure. Chart reference Choose the date tab before interpreting a chart. Hover over a plotted bar or point to inspect its value. Channel and product labels come from captured feed information; they are not a guarantee that similarly named products from different channels are equivalent. Reservations by Channel chart showing one captured booking-engine reservation Example from the By Arrival Date tab in the demo property. The chart counts reservations, not rooms or nights. Channel Performance Chart Meaning Reservations by Channel Noncanceled reservation count by channel name, across all currencies. Room Nights by Channel Whole-stay room nights by channel, across all currencies. Revenue by Channel Selected-currency reservation-level after-tax amounts by channel. ADR by Channel (Average Daily Rate) Each channel's selected-currency amount divided by its same-currency room nights. Channels without contributing nights are omitted. Average Length of Stay by Channel (Nights) Average positive stay length per room, across all currencies. This differs from the summary's Room Nights / Booking denominator. Room Type Performance Chart Meaning Revenue by Room Type Selected-currency room-level after-tax amounts grouped by captured channel room name, or room code when no name is available. Unknown Room Type means neither is available. ADR by Room Type That room-name group's selected-currency room amount divided by its corresponding room nights. Groups without positive nights are omitted. Identical room names across channels can combine in one group. The room charts do not use the reservation-level total as a substitute for missing room amounts. Their totals need not match Revenue by Channel or the summary. Trend Analysis Chart Meaning Reservations Over Time Noncanceled reservation counts by version receipt day or first-room arrival day, depending on the tab. Counts include all currencies. Revenue Over Time Selected-currency whole-reservation amounts assigned to those receipt or arrival days. It is not revenue earned on each night of stay. ADR Over Time Each plotted date group's selected-currency amount divided by the whole-stay nights attached to that group. Dates without matching noncanceled reservations are omitted rather than filled with zero. Lines connect the available points; they do not demonstrate intervening daily activity. Labels show month and day without a year, so keep the selected range in view when comparing a period spanning years. Monetary and count charts can have different dates because the former use one currency. Booking Patterns - By Version Receipt Date → Lead Time Distribution (Days Before Arrival): groups bookings by the first room's arrival day minus the selected version's receipt day. Same Day also includes negative intervals. The other groups are 1–3 Days, 4–7 Days, 8–14 Days, 15–30 Days, 31–60 Days and 60+ Days. Despite the final label, 60 belongs in 31–60 Days; the last group starts at 61. Missing first-room arrivals are omitted. - By Arrival Date → Arrivals by Day of Week: groups noncanceled reservations by the first captured room's arrival weekday. When that arrival is missing, it uses the receipt date. It does not count each arriving room separately. Rate Plan Performance Top Rate Plans by Reservations shows the ten largest captured rate-plan-name groups. Despite the title, it counts room records, not distinct reservations: one multi-room reservation can contribute more than once. It falls back to the captured plan code, then Standard Rate, when a name is missing. Identical plan names across channels can combine. Plans outside the top ten are omitted, without an “Other” total. Do not add the bars to reconstruct the summary's reservation count. For a separate, qualified stay-night analysis with supporting detail and CSV output, use Rate Plan Performance. Its date basis and monetary qualifications differ from this report. Filter and control reference Control Values, defaults and effect Property selector Chooses the property context. Verify the property again after navigation; this report is not a multi-property comparison. Filters Opens or collapses the date/channel form. Usually collapsed after a data-bearing run; opening it does not reload results. Month / Year Optional shortcut that fills a calendar month into Date Range . It is not a monthly grouping control and does not run the report. Check the range after changing or clearing this shortcut. Date Range Both endpoints are required. Use the displayed date format, with the end on or after the start. Blank does not mean all dates. Receipt dates and arrival dates are evaluated separately against this period; stay nights are not clipped to it. Channels Checked feeds are applied when you select View Report . Fresh visits check all offered feeds. The closed label can say All channels even when none is checked, so open it to verify. Select all Selects all offered channels if any are unselected; clears them when all are selected. There is no channel-search box in this control. View Report Reads the current report using the displayed dates and channel choices. It does not save a report configuration or send anything to channels. Cancel / Reports Returns to the report catalogue. Currency for revenue and ADR Available recorded currencies from either date group, or Currency unknown . Updates money immediately without changing all-currency counts or fetching new data. By Version Receipt Date / By Arrival Date Changes the chart group immediately. Summary cards retain their explicitly described date bases. If the property offers no channel choices at all, the report can run without a channel restriction and include its stored feeds. That is different from clearing an available list, which is refused. There are no room-type, rate-plan or status filters on this page. It has no page-owned CSV/Excel download, saved-report schedule or paged detail list. Use a dedicated report for those tasks rather than assuming a chart is a downloadable reservation ledger. Common problems Symptom Check and safe next action No Reservation Data Found Read any validation message first. Confirm property, dates and actual channel checkboxes, then select View Report . If the inputs are valid, try another period or more offered feeds. An empty result does not prove there were no property bookings. Choose at least one channel. Open Channels , check one or more choices and rerun. The closed All channels label alone does not establish that any box is checked. Dates are blank, reversed or a typed date fails Re-select both endpoints using the calendar, confirm the displayed range and rerun. Do not rely on a reversed range being rejected rather than returning empty results. If valid inputs still fail, send support the exact range and error. Filters changed but figures did not Select View Report after changing dates or channels. Currency and tab changes are immediate, but they do not fetch new data. Counts appear but revenue is zero or unavailable Check the currency and the Currency unknown notice. Missing amounts can become zero; canceled-only or arrival-only currency groups can also leave receipt money at zero. Do not substitute a guessed amount. Room-type revenue differs from channel revenue The report uses room amounts for one and reservation totals for the other. Ask support to check captured amount coverage and source definitions; do not alter bookings to force agreement. Summary cards appear unchanged after selecting the arrival tab Expected: the tab changes charts. Use the explicitly arrival-labeled cards for arrival-group totals. Receipt timing, arrival plots or rate-plan counts look inconsistent Check the date and counting definitions above, especially first-room dates, multi-room bookings, latest versions and timezone boundaries. Escalate an unresolved discrepancy rather than assuming missing delivery. The report is slow or charts do not render Narrow the date range and channel selection, then rerun. There is no report row cap or pagination. If needed, reopen the report and enter the filters again. Escalate persistent failures with the scope and error; no load-time guarantee is provided. An expected feed is absent from Channels The offered list depends on the connection's inventory-send and reservation-receive/monitoring setup. Ask your administrator or support to confirm the intended reporting scope; do not change live connection settings merely to expose a filter choice. Rerunning this read-only report does not duplicate reservations or resend inventory. For unresolved issues, provide the property, date range, selected channels, currency, tab and exact warning or a relevant screenshot. Include the property timezone for timing discrepancies. Do not include passwords, payment details or unnecessary guest information. Related - Compare rate-plan production and value - Analyze cancellation cohorts and canceled booking value
Compare property performance with Portfolio Overview
Use Portfolio Overview to compare captured room nights, booked room-rate value and qualified ADR across selected properties, keeping currencies and active or canceled business separate. Before you start - Open Channel Manager > Reports > Portfolio Overview in the organization you want to review. - You can select active properties in the current organization. Organization administrators can select the organization's available properties; other users can select properties assigned to them. You must also have access to the property you are currently viewing. - Choose one reservation feed for each report. A feed offered in the list may serve only some of the available properties. This is a captured-business report, not a complete hotel-performance statement. It includes reservations received through the selected feed. It does not establish total property occupancy, RevPAR, settled revenue, profit or feed completeness. A property with no captured stays is not necessarily an empty hotel. Run a comparison 1. Open Channel Manager > Reports > Portfolio Overview. 2. In Filters, choose Stay dates (through inclusive). Use Month for a whole calendar month, or choose a custom start and end date. 3. Choose the Reservation feed. For booked room-rate value and ADR, select ChannelRUSH Booking Engine. Other feeds can provide counts, but their monetary value is not qualified in this report. 4. Choose Currency and Business status. Leave currency at All currencies, kept separate if you want separate totals for each captured currency. 5. Under Properties, tick the properties to compare. Review the selected count. You must select at least one and no more than 200. 6. Optionally enter a Country code, City (exact) or a different Opportunity creation window (days). 7. Click View report. The Filters panel collapses after the report loads. Reopen it to change the selection, then click Update report. Editing a date, feed or property checkbox alone does not update the results. Existing table searches and filters remain when you update the report; use Reset table if you want to remove them. Portfolio Overview Filters with stay dates, reservation feed and three selected demo properties Reopen Filters to review or change the report selection. Check the result Check the displayed stay dates, reservation feed, business status and property selection before comparing figures. The property name in the report card header is your current property context, not the full list of properties included in the report. You should see: - Summary cards with Room nights, Qualified nights, Known booked value and Weighted ADR, separated by currency, status and value basis. - A Properties table with the matching property rows. - Matching table totals, which reflect the table's search and column filters. - Feed-wide exceptions and an expandable Recent opportunity records section. After an update, check that the results reflect your selection. While an update is in progress, the previous results remain visible. If an update fails, those previous results are retained; do not treat them as the new selection. Extracted is when ChannelRUSH read the report data. It is not the time of the last reservation-feed update. Opening a report or downloading it again can produce different values if the underlying records have changed. Understand the figures Stay dates, bookings and nights The report uses each property's local stay dates. The start and end dates are inclusive, but checkout is excluded. Only nights that fall inside the selected period count; a reservation can contribute even if its arrival is before the start date. - Bookings counts distinct captured reservations contributing nights to a property/currency/status row. - Room stays counts the reservation's individual room-stay records contributing those nights. One booking can contain several room stays. - Room nights counts those room stays' nights inside the selected period. The report uses the latest captured reservation version for each source booking identity. It is a current view of the selected stay dates, not a historical snapshot of what was on the books on an earlier date. Active includes new and modified, noncanceled business. Canceled is reported separately and is not subtracted from Active. When both are selected, do not combine them as a net active total. Known value and ADR For ChannelRUSH Booking Engine, a night contributes to Known value only when it has exactly one recorded, nonblank nightly price and a recorded currency. The amount is booked room-rate value, including tax embedded in that rate and excluding separately recorded fees or taxes. - Priced nights have exactly one recorded, nonblank nightly price. - Qualified nights additionally meet the report's feed and currency requirements for monetary value. - Known value sums only qualified nightly prices. It can be a partial amount if other nights lack qualified prices. - Qualified ADR divides known value by qualified nights, not by all room nights. - Weighted ADR uses the combined known value divided by combined qualified nights within the same currency, status and basis. It is not an average of property ADRs. For other feeds, Counts only; monetary basis unqualified means that counts may be available but this report does not use their recorded prices for known value or ADR. An em dash (—) on screen or a blank monetary cell in an export means unavailable or unqualified, not zero. A recorded price of zero can be a valid known value. No currency conversion takes place: compare like currencies and value bases. Exceptions and coverage - Unmapped nights have no single unambiguous room-type mapping under the property's current mappings. The report uses current mappings, not historical ones. An unmapped night is not automatically excluded from the room-night count or from otherwise qualified value. - Invalid stays have missing arrival or departure dates, or checkout on or before arrival. They cannot contribute valid stay nights. This count follows the selected feed, status and currency, but cannot be limited to the selected stay dates. - Missing identity rows are captured reservation rows without a usable source booking identity. They are excluded from the booking/night calculation. This count is feed-wide for the property, not limited to the selected stay dates, status or currency, and is not a count of distinct bookings. Property exceptions can repeat on several currency/status rows. Do not add those repeated counts. The summary exception line counts each property's exception figures once. A No captured stays row preserves the property in the comparison when it has no valid matching nights. Its booking, room-stay and night counts are zero and its monetary values are unavailable. Invalid-stay and missing-identity exception counts can still be present. Check the feed, dates and filters before interpreting it. Refine the property table Report filters and table filters have different scopes. The report's summary cards and Download report files use the report selection. Searching or filtering the Properties table changes the matching rows, matching table totals and matching-table downloads only. It does not change the report totals or recent opportunity records. 1. In the table's Search box, enter part of a property name, country or city and press Enter. Search is case-insensitive and checks those three fields, not property IDs. 2. Use a column's filter menu to add a condition. All conditions must match. Use the Property ID column filter to find a specific ID. 3. Click a supported column heading to sort. You can use up to three sort fields. 4. Drag Country or City into the grouping area to group properties. These are the only grouping fields; both can be used. Group totals still keep currencies, statuses and value bases separate. 5. Choose 25, 50 or 100 rows per page and use the page controls. The default is 50. Totals and matching-table downloads include all matching rows, not only the visible page. Use Columns to show or hide columns. You can also resize or reorder them and choose Comfortable or Compact under Density. These presentation choices are remembered in the same browser for your user, organization and report. Hiding a column does not remove its data from the standard download. Reset table clears table searches, filters, sorts and grouping and restores the default page size without changing the report selection. Reset report starts a fresh report selection. New window opens the current report selection separately. A bookmarked report restores its selection, not a frozen copy of its data. If the interactive table is unavailable Use the full-page table and Property table controls: 1. Enter Find property, country or city, choose Rows per page and optionally Group properties. 2. Choose Sort by and up to two Then by fields. 3. Expand Filter matching rows to enter up to ten conditions. Leave unused conditions blank. 4. Click Update table. Text fields support equals, does not equal and contains. Numeric fields support equals, does not equal, at least and at most. IDs, currency and status support equals and does not equal. Enter positive whole-number IDs, a decimal point for amounts, and Active or Canceled for a status condition. Value basis cannot be sorted or filtered. Unknown monetary values do not match numeric conditions, including “does not equal.” The full-page table also shows bookings, room stays, priced nights and property exceptions under its combined column headings. Selected scope total covers the report selection; Matching table total covers the table selection; Full matching group total covers the entire matching group across pages. Open supporting detail Review a property's stay production Click the linked property name in the Properties table. In the full-page table, use View stay production or View related stay production. The link opens Daily Revenue / OTB for that property with the same stay dates and reservation feed. For a populated row with a recognized currency and Active or Canceled status, it also carries that row's currency and status. View related stay production indicates a broader related view rather than an exact row match, such as a row with no captured stays or an unsupported currency. Check the destination's filters before reconciling figures. Use Return to report when available to return to the comparison. Review recent opportunities Expand Recent opportunity records. Each row identifies the property, source channel, type/level and record count. Click the property's link to open the matching selection in Opportunity Center. These records use a separate creation-time window: - They belong to the selected properties after the report's country/city restrictions. - They are unarchived opportunity records created within the selected number of days before extraction. - They match your report language or have no language specified. - They include all property channels. Stay dates, reservation feed, business status, currency and property-table searches do not narrow them. Counts are message records, not necessarily independent incidents. The destination retains the originating channel, type, level, language and creation cutoff, but records can change after extraction. No recent records does not prove healthy distribution. Filter reference Control What it does and accepted values Month Sets the stay-date range to a whole calendar month. It is a shortcut for the date range, not an additional filter. Stay dates (through inclusive) Both dates are required together, or both can be blank. Choose an ordered range of at most 366 days, within years 2000–2100. If separate Start date and End date controls appear, enter both there instead. Days when both dates are blank Uses a period starting today in the current property's local date and continuing for this many days, including today. Default 30; accepted 1–366. It does not mean the previous 30 days. Ignored for the range when both explicit dates are supplied. Clearing this number restores the default. Reservation feed One source of captured reservations. The initial default is ChannelRUSH Booking Engine. The list includes feeds connected to available properties; a previously selected feed can remain named even if no longer connected. A listed feed is not proof that every selected property receives bookings through it. Currency All currencies, kept separate , or one recognized currency code. A single currency restricts captured business, not opportunities. Properties without matching nights can still appear as No captured stays . Business status Active by default, Canceled , or Active and canceled, kept separate . Country code Exact match against the property's recorded country code, ignoring case and surrounding spaces; for example, DE . Blank means no country restriction. Maximum 10 characters. This filters property geography, not guest nationality. City (exact) Exact match against the property's recorded city, ignoring case and surrounding spaces; for example, Berlin . Blank means no city restriction. Maximum 100 characters. Use table Search for a partial city match. Opportunity creation window (days) Independent recent-record window. Default 30; accepted 1–90. Clearing the number restores 30. Does not change stay-production dates. Properties Initially selects available properties. Tick individual properties or use the checkbox beside Properties to select or clear the list. If more than 200 are available, selecting all takes the first 200; check the count and desired properties before running. No selection is not “all”: the report requires 1–200 authorized properties. View report / Update report Runs the report selection. The button is disabled when no property is selected. Changing report filters is read-only: it does not alter reservations, inventory or channel settings. On-screen field reference Summary cards and Properties columns Field Meaning Property ID ChannelRUSH property identifier. Property Property name. A link opens its supporting stay-production view. Country , City Geography recorded on the property; blanks mean no recorded value. Currency Currency on the captured reservation. A blank or Unknown currency is not a default currency. Status Active , Canceled or No captured stays . A property can have several rows when currency or status differs. Value basis Booking-engine booked room-rate value or Counts only; monetary basis unqualified . This explains whether amounts are usable in this report. Room nights Captured nights inside the selected stay dates, excluding checkout. Qualified nights Nights eligible to contribute monetary value and ADR. Known value / Known booked value Sum of qualified booked room-rate prices; not necessarily the value of all counted nights. Qualified ADR / Weighted ADR Known value divided by qualified nights within the applicable row or separate total. Feed-wide exceptions Missing identity rows and invalid stays. See the exception rules above before adding or comparing them. Extracted Report data-read timestamp, not source freshness. Recent opportunity records Field Meaning Property Property ID; its link opens the corresponding Opportunity Center selection. Channel / Source channel Source channel ID; -1 means no source channel was recorded. It can differ from the selected reservation feed. Type / level Opportunity classification. Numeric type 1 means Opportunity; 2 means OpportunityChannel. Level 0 means Success, 1 Info, 3 Warn and 4 Error. Some views show names instead of codes. Records Number of matching message records in that property/channel/type/level group. Latest creation (stored) Latest recorded creation timestamp in the group, shown in the full-page table and exports. It is not a resolution or delivery timestamp. Download the right scope Wait for any report update to finish before downloading. Action Contents and scope Download report > Portfolio workbook XLSX with Context , Properties and Opportunities worksheets. Properties and opportunities use the full report selection, not property-table filters. Context explains the selection and coverage. There is no separate worksheet of summary-card totals. Download report > Properties CSV All property/currency/status rows in the report selection, with the property headers below. No opportunity rows or added total rows. Download report > Opportunities XLSX / Opportunities CSV All matching opportunity groups for the report selection and independent creation window. XLSX also includes Context. A CSV with only its header means no matching groups were found. Download matching table CSV / Download matching table XLSX Every matching property row across all pages, applying table search, filters and sort order. XLSX also includes Context. These are property rows, not group-heading or total rows. For example, if your report selects three properties and table Search leaves one matching property, Properties CSV still includes the report's property rows, while Download matching table CSV includes only the match. Downloads read the selection again. If data changes between viewing and downloading, compare the extraction timestamps and refresh before reconciling. An export is not a guarantee that the reservation feed is complete or current. Export headers: property and opportunity downloads Headers are case-sensitive as shown. Dates in CSV use YYYY-MM-DD. Unknown monetary values are blank, not zero. Properties CSV, the workbook's Properties sheet and standard matching-table downloads use this complete header sequence: contract,propertyId,feedId,start,end,extractedUtc,propertyName,country,city,currency,status,basis,bookings,roomStays,roomNights,pricedNights,qualifiedNights,knownValue,adr,unmappedNights,invalidStays,missingIdentities,qualification Opportunities CSV and the Opportunities sheet use: contract,propertyId,feedId,start,end,extractedUtc,channelId,type,level,count,latestCreated,language,createdSince,archived Header Meaning contract Export format identifier, currently report-pilot-v1 . Useful when identifying a file for support. propertyId Property represented by the row. feedId Selected reservation-feed ID. On opportunity rows this is report context, not the opportunity's channel; use channelId for that. start , end Selected inclusive stay-date boundaries. On opportunity rows these are report context only; createdSince defines their creation window. extractedUtc Data extraction timestamp in UTC. Not the latest source update. propertyName Property name. country , city Property geography. currency Captured reservation currency; blank when unknown or when the property has no matching captured stays. status Active, Canceled or No captured stays. basis Explanation of the monetary basis. bookings Distinct captured bookings contributing nights to the row. roomStays Distinct room-stay records contributing nights to the row. roomNights Nights clipped to the selected stay period. pricedNights Nights with exactly one recorded, nonblank nightly price. qualifiedNights Nights that qualify for monetary value. knownValue Sum of qualified nightly prices; blank if none qualify. adr Known value divided by qualified nights; blank if unavailable. unmappedNights Nights without a single unambiguous current room mapping. invalidStays Property's invalid-stay count for the selected feed/status/currency, outside a usable stay-date scope. Repeated across property rows; do not sum repetitions. missingIdentities Feed-wide captured rows without usable source booking identity, repeated across the property's rows. Not a distinct-booking count. qualification Known qualified booked room-rate value; captured feed only when the row has known value; otherwise Unknown or unqualified monetary value . The first label does not mean every counted night qualifies. channelId Opportunity's source channel ID, or -1 when not recorded. type , level Opportunity type and level codes listed in the on-screen reference. count Matching opportunity message-record count. latestCreated Latest stored creation timestamp in the opportunity group. Preserve the timestamp/offset as supplied; do not assume it has the same display format as extractedUtc . language Report language used to select opportunities. Language-neutral records are also included; this is not necessarily the language of every individual message. createdSince Extraction time minus the opportunity-window days. It is the inclusive creation-time cutoff, independent of stay dates. archived Always false in this download because only unarchived records are included. It does not mean that an opportunity is resolved. The Context worksheet contains key/value notes rather than property data. Its keys are Title, Contract, Generated UTC, Extracted UTC, Scope, Dataset, Selection, Basis, Coverage, Values, Counts and Opportunities. Scope distinguishes report from table; Dataset identifies the requested download. summary is the Portfolio workbook selection, not a separate Summary worksheet. Selection records the report link; Generated UTC is file-generation time, distinct from Extracted UTC. Older combined CSV files An older report link may download a combined portfolio.csv instead of the separate datasets above. Identify it by its capitalized headers and RowKind column. It includes Property, Total and Opportunity rows; when there are neither property nor opportunity rows, it includes a No matching rows marker. It covers the report selection, not the table search. Do not sum Property and Total rows together. Total rows are already grouped by currency, status and basis. Opportunity rows do not contain property-production metrics. The complete header sequence is: Contract,ScopePropertyIds,FeedId,StartDate,EndDate,IncludeCanceled,CurrencyFilter,CountryFilter,CityFilter,OpportunityDays,OpportunityLanguage,ExtractedUTC,RowKind,PropertyId,PropertyName,Country,City,Currency,CommissionCurrency,Status,Basis,Bookings,RoomStays,RoomNights,PricedNights,QualifiedNights,UnmappedNights,KnownValue,ADR,RecordedCommission,BookingsWithCostAmount,QualifiedNetBookings,QualifiedBookingValue,QualifiedNetValue,QualifiedNetCoveragePct,InvalidRoomStays,MissingIdentityRowsFeedWide,OpportunitySource,OpportunityType,OpportunityLevel,OpportunityCount,LatestOpportunityCreated Header or headers Meaning in a Portfolio file Contract captured-portfolio-production-v1 , identifying this combined report format. ScopePropertyIds Requested property IDs, separated by semicolons. Geography filters can narrow the properties represented by the rows. FeedId , StartDate , EndDate Selected reservation feed and inclusive stay dates. IncludeCanceled Whether canceled business is included. Both canceled-only and active-and-canceled selections can be true; use row Status to distinguish them. CurrencyFilter , CountryFilter , CityFilter Report restrictions; blanks mean no restriction for that field. OpportunityDays , OpportunityLanguage Separate opportunity creation-window length and report-language selection. Language-neutral records are also included. ExtractedUTC Report extraction timestamp, not source freshness. RowKind Property, Total, Opportunity or No matching rows. PropertyId , PropertyName Property identity for property rows. Opportunity rows carry a property ID but no property name. Total rows use ID 0 and name Selected scope total ; 0 is not a property to look up. Country , City , Currency , Status , Basis Same geography, currency, business status and value-basis meanings as the property export. Geography is blank on totals. Bookings , RoomStays , RoomNights , PricedNights , QualifiedNights , UnmappedNights The corresponding counts described above. Blank on opportunity rows. KnownValue , ADR Qualified booked room-rate value and ADR; blank when unavailable. CommissionCurrency , RecordedCommission Shared fields not populated by Portfolio Overview. Blank does not establish no commission or zero cost. BookingsWithCostAmount , QualifiedNetBookings Shared cost/net fields, not calculated by Portfolio Overview. Property and Total rows contain default zero values; these are not measured cost-coverage or net-booking counts. QualifiedBookingValue , QualifiedNetValue , QualifiedNetCoveragePct Shared net-revenue fields, not calculated by Portfolio Overview; blank. Do not use them to infer net revenue or profitability. InvalidRoomStays , MissingIdentityRowsFeedWide Property exception counts, repeated across currency/status rows and deliberately blank on Total rows. Not additive across repeated property rows. OpportunitySource , OpportunityType , OpportunityLevel , OpportunityCount , LatestOpportunityCreated Opportunity channel ID, type code, level code, record count and latest stored creation timestamp. Populated only on Opportunity rows. Common problems Symptom Likely explanation and safe next action A property is missing from the picker, or Select only currently authorized properties appears The property may be inactive, outside the current organization or no longer assigned to you. Check your organization and ask your organization administrator to verify access. Rebuild old bookmarked selections from the current picker. View report or Update report is disabled No property is selected. Tick at least one property and check the selected count. The date range is rejected Supply both dates or clear both. Keep the end on or after the start and the range within 366 days and years 2000–2100. Keep fallback days within 1–366 and opportunity days within 1–90. No property rows match, but summary cards still have values A table search or condition excluded the rows. Click Reset table . Report totals intentionally remain unchanged. A selected property is absent from the results Check Country code and City (exact) first, then table search/filters. Property geography restrictions can remove a selected property entirely. No captured stays , or zero nights with blank value Check the feed, stay dates, currency and business status. The property may have no matching valid nights in captured data. Do not interpret this as zero total hotel business. Nights are present but value or ADR is blank The feed's monetary basis may be unqualified, or nightly prices/currency may be missing or conflicting. Review Value basis , qualified nights and supporting stay production. Do not replace blanks with zero. Exception counts appear several times They repeat on the property's currency/status rows. Use the summary exception figures, not a sum of the repeated export values. No recent opportunity records Check the independent creation window, property geography and language context. Empty results do not establish healthy channels or resolved issues. Update failed. Previous results retained. The displayed results are still the earlier selection. For a temporary failure, use Retry update to retry the same selection. If you change or correct filters, click Update report to submit those changes. Retrying this report reads data; it does not resend reservations or inventory. Interactive table unavailable. Use the full-page table below. Use Property table controls and Update table . If the problem persists, report the browser and visible message to support. A table condition is rejected Use a supported field/operator, positive ID, decimal-point amount or Active/Canceled status. Keep within three sorts, two geography groups and ten conditions. Use Reset table to remove an invalid saved table selection. Too many result groups; narrow the selection or an overly long report-link warning Reduce selected properties, narrow report criteria, or remove table conditions/return steps. A report supports at most 200 selected properties and 10,000 result groups. A download differs from the table Check whether you chose Download report or Download matching table , then compare report criteria and extraction timestamps. Table pagination does not limit either export. If a discrepancy remains after checking the selection, contact support with the organization/property IDs, reservation feed, stay dates, currency/status, relevant table filters, extraction time and visible error text. Include whether the file came from Download report or Download matching table. Do not send passwords, payment details or unnecessary guest information.
Filter and export reservations for a property
Find captured reservations for one property, narrow the result and download either the complete report selection or the rows matching your table filters. Before you start - Select the property you want to investigate. You need access to that property. This report is available through Reports → Reservations → List & Export; it is separate from the Reservations → Search screen. - This page reports the current property only. Check the property shown under Filters → Properties. To change it, select the other property and reopen the report. For several properties together, use the organization reservations report. - Results contain the latest captured version of each reservation, not every modification or a historical snapshot. New, Modified and Canceled are reservation-version states, not delivery results. - Viewing, filtering and downloading this report does not change or resend reservations. Files can contain booked-by names and confirmation numbers; share them only with authorized recipients. Run the report 1. Select the intended property in the application header. 2. Open Reports → Reservations → List & Export. 3. Confirm the property under Filters. 4. Set both dates under Date range. Alternatively, use Month to select a whole month. If the enhanced date picker is unavailable, use the Start date and End date fields. 5. Choose Date basis. Use the reference below to distinguish receipt dates from stay dates. 6. Select the Channels and Status values you want included. 7. Click Update report. 8. Check the date basis, date range and matching-reservation count above the table before using or downloading the results. On a fresh page, the displayed dates start at the property's current local date and end 28 days later. Booking date is selected, with all offered channels and all three statuses checked. These are proposed criteria: the report does not run until you click Update report. Property reservation report filters with dates, date basis, channels, statuses and Update report Example from a demo property. Canceled is unchecked here, so this selection includes New and Modified versions only. Date and selection reference Control What it selects What to check Properties The current property. This is a scope label, not a multi-property picker. Confirm it before running the report. Month Sets the date range to a whole calendar month. Check the resulting start and end dates. Date range Both boundaries for the selected date basis. End must be on or after start. Dates alone do not select the meaning of the period. Booking date Receipt of the latest captured reservation version. This is not necessarily the original sale date. A modification can move a booking out of an earlier receipt-date selection. Arrival date Reservations with a room arrival within the selected dates, including both boundary dates. Other rooms in that reservation can have dates outside the range. Departure date Reservations with a room departure within the selected dates, including both boundary dates. This is not an occupied-night filter. Stay overlap (checkout included) Reservations whose room date ranges overlap the selected dates. Checkout counts. Incomplete room-date boundaries can also qualify. Do not use this as an occupied-room-night count. Channels The recorded reservation channel/feed. All checked means no channel narrowing. The offered list need not contain every historical or PMS-only feed. With all checked, those captured records can still appear. Status New, Modified and/or Canceled for the latest captured version. A newer version supersedes the earlier version even if it no longer matches your selected status or dates. Use the checkbox beside Channels or Status to select or clear that list, then confirm the selected count. Keep at least one status selected and at least one channel when channels are offered. A property with no offered channels can still have captured reservations. A retained Recorded channel entry means the report link names a channel no longer in the offered list; it remains a filter until you change the selection. The dates decide which reservations qualify. They do not clip a reservation's dates, stay nights or amounts to that period. For receipt-date reconciliation, retain the report URL and use the same output path. Version receipt UTC is displayed in UTC. Do not assume the calendar dates establish property-local midnight boundaries or that a separate legacy Excel/CSV report uses identical receipt boundaries. If a reservation near a date boundary differs between outputs, retain both selections and the receipt timestamp for support to compare; the difference alone does not prove a missing booking. Check and adjust the result A matching count means captured reservations matched the current selection. It does not establish that every booking has been received or delivered. Zero matches is not proof that the property has no business. Click a Confirmation link to open that captured reservation's details. Check the property and reservation identifiers before investigating. See Review reservation details for the detail fields. To change dates, channels or statuses, open Filters, make the changes and click Update report again. Existing table filters can remain active after changing report criteria; use Reset table if you want to remove that extra narrowing. - Reset report keeps the property context but clears the report selection and table choices. Choose the dates and run the report again; dates appearing in the controls do not mean results have loaded. - Reset table keeps report dates, property, channels and statuses while clearing table search, filters, sorting and paging choices. - New window opens the report in a separate tab/window, retaining its selection. - If a legacy link shows No date filter — the dates above are ignored, choose a date basis and click Update report. The visible dates alone do not establish that a date filter is active. If a refresh fails, the old rows can remain visible. Check the error and selected criteria rather than treating those rows as the result of your pending changes. Retry, when offered, repeats report retrieval; it does not resend a reservation. Narrow or arrange the table 1. Open Table filters and sorting. 2. Choose a Sort column and Direction, if needed. 3. To add a filter, choose its field under Add filter, then its Operator and Value. 4. Optionally enter a Property/channel search and choose Rows. 5. Click Apply table. 6. Check the resulting matching count and active selection before exporting. Property/channel search searches property and channel names, not guest names or confirmation numbers. For a booking identifier, add a Confirmation or PMS confirmation filter. Table-filter values Fields Supported operators Value example Internal ID, Property ID, Channel ID Equals; Does not equal A positive whole-number identifier. Status Equals; Does not equal New , Modified or Canceled . Confirmation, PMS confirmation, Property, Channel, Currency Equals; Does not equal; Contains A confirmation number or USD . Text matching is case-insensitive. Arrival, Departure Equals; Does not equal; At least; At most 2026-10-24 . Stay nights, Before tax, After tax Equals; Does not equal; At least; At most 3 or 1250.50 , without thousands separators. Version receipt UTC Equals; Does not equal; At least; At most 2026-10-24T12:00:00Z , or a timestamp with an explicit UTC offset. The operator menu can offer an operator that is invalid for the selected field. Use a supported combination from this reference. Booked by and Single rate plan cannot be filtered or sorted. Additional filters combine with AND: every condition must match. Up to ten filters and three distinct grid sorts are supported. Search is limited to 100 characters and an individual filter value to 128 characters. Applying the table form's single sort replaces any multi-column grid sort. Rows offers 25, 50 or 100; the initial page size is 100. Paging limits the displayed page, not the complete matching download. The initial order is Internal ID, ascending. Use Columns to show or hide columns; you can also resize and reorder them. Density → Comfortable / Compact changes presentation. These choices do not remove fields from the default CSV/XLSX downloads. Download the right selection 1. Confirm the property, date basis, dates and current result. 2. Open Download. 3. Choose the scope and file type: - Full report CSV or Full report XLSX includes the report's property, dates, channels and statuses. It ignores additional table filters, search and sorting. - Matching table CSV or Matching table XLSX retains table filters, search and sorting. It includes all matching pages, not only the page currently displayed. 4. Check the file's property, identifiers, currency and date basis before using its values. Downloads query the data again. A newly captured or modified reservation between viewing and downloading can change the result. A file is not a permanently frozen copy of an earlier screen. The XLSX file includes Context and Reservations 1 sheets, with additional reservation sheets when required. Context records the selection, scope, extraction time, row count and interpretation notes. The CSV includes the context fields described below on each data row. A no-match CSV can contain only its header. These downloads are not the separate legacy Excel View. If an old bookmark opens View - Excel or a different field layout, reopen Reports → Reservations → List & Export to follow this guide. Do not mix schemas or receipt-date boundaries without reconciling them. On-screen column reference Column Meaning Confirmation The channel's reservation identifier. The link opens the captured reservation version. Booked by The supplied booked-by name, not a list of every staying guest. Blank means no usable name is supplied here. Property The property associated with the reservation. Channel The recorded reservation channel/feed, which can differ from the booking's ultimate sales source. Status New, Modified or Canceled for the latest captured version. Not delivery status. Arrival / Departure The captured whole-reservation date envelope, not dates clipped to the filter period. Missing boundaries remain unknown. Stay nights The span of that date envelope, not summed room-nights. A zero can reflect incomplete dates; inspect the reservation before interpreting it as a zero-night stay. Currency The source currency. Amounts are not converted to a common currency. Before tax / After tax Captured source totals. Missing or unavailable amounts remain blank; zero is different from missing. These are not proof of collected payments or complete accounting revenue. Version receipt UTC When ChannelRUSH received this captured version, displayed in UTC. Not necessarily the original sale time. Internal ID ChannelRUSH's identifier for this captured reservation version. Different versions can have different IDs. Property ID / Channel ID ChannelRUSH identifiers for the property and recorded channel. PMS confirmation The captured PMS reservation identifier. Its presence does not prove the latest delivery succeeded. Single rate plan The channel rate-plan identifier when the reservation's room entries share one. Blank can mean missing or multiple rate plans. If the interactive grid is unavailable, the plain table groups some of these fields together. Its Amount / currency chooses one source total according to currency tax treatment; an unavailable chosen total remains missing rather than being replaced with the other total. CSV and XLSX field reference The default download fields are the same for both file types, in this order. Hiding a grid column does not remove its export field. Exact header Meaning contract Export schema identifier: reservations-v1 . propertyId ChannelRUSH property ID. propertyName Property name. channelId ChannelRUSH recorded channel ID. channelName Recorded channel/feed name. reservationId Internal captured-version ID—not the channel confirmation. confirmation Channel reservation identifier. pmsConfirmation Captured PMS identifier, if supplied. guestName Booked-by name. ratePlan Single shared channel rate-plan identifier; blank for missing/multiple plans. status New, Modified or Canceled. currency Source currency; missing is unknown. totalBeforeTax Source total before tax; blank when unavailable. totalAfterTax Source total after tax; blank when unavailable. arrival Captured reservation arrival date. departure Captured reservation departure date. nights Whole-reservation date span, with the missing-date limitation above. receiptUtc Receipt instant of the captured version, in UTC. sourceEditedUtc Source-supplied edit instant, in UTC; blank when absent. It does not fall back to receipt time. extractedUtc Report extraction time. Not a delivery time or proof of a fresh channel response. dateBasis The report's date-basis label. Dates use YYYY-MM-DD; timestamps include an explicit UTC offset. CSV numbers use a decimal point without grouping separators. Preserve identifiers as text when importing CSV so leading zeros and long IDs are not altered. Formula-like text can have a protective leading apostrophe in CSV; XLSX stores such text literally. Missing dates and totals remain blank rather than being invented as zero. Common problems Symptom Safe next action When to escalate No matching reservations Confirm property and date basis, widen dates if appropriate, include the required statuses/channels and use Reset table to remove extra narrowing. A known captured booking remains absent after its latest version and criteria are checked. A booking disappeared from an earlier report Check its latest captured version. A modification, cancellation or later receipt can move it outside the original selection. The latest version appears to satisfy every filter but is still absent. Update report cannot run Supply both dates, correct reversed dates and keep the required checklist selections. Valid criteria still produce an error. Retain the error text and report URL. An added table filter is rejected Check the field/operator combination and the value format in the table-filter reference. A supported combination still fails. Old rows remain after an update error Treat them as the previous successful result. Correct criteria or use Retry when offered. Retrieval continues failing; do not resend reservations to repair a report display. Download contains more rows or fields than expected Check Full report versus Matching table. Both export all matching pages; hidden columns remain in the default schema. Scope still differs after those distinctions are checked. Receipt-boundary results differ between extracts Keep the same report path and retain both URLs, date bases and the relevant UTC receipt timestamp. Ask support to compare the exact date boundaries before treating a difference as a missing booking. The property or report is unavailable Confirm the selected property and ask your organization administrator to check access. Access is expected but the page remains unavailable. For support, provide the property, recorded channel, appropriate reservation identifier, report URL, date basis, dates, action time/time zone and error text. Do not send passwords, card details or an unrestricted guest export. Related - Read and export reservations across properties - Review reservation details - Check reservation delivery status
Read reservation metrics for a property
Choose stay dates and a reservation feed, then read and export nightly reservation metrics for the property you are viewing. Before you start You need access to the property and its reports. Select the property first, then open Reports → Reservation Metrics. The page heading may read Reservations; the report reading note describes mapped nightly reservation metrics. This is a captured-reservation report, not an availability report or an accounting statement. It uses active New and Modified reservations, mapped rooms and the nightly prices supplied with those reservations. Canceled reservations are excluded from the normal report. The date range selects overlapping stays, not a strict revenue period. The stay-selection check includes the departure date, so a stay checking out on your selected start date can also qualify. Once a stay qualifies, the report includes its supplied nightly rows for the whole stay, even outside your selected dates. Choose Daily OTB from Reports instead when you need the report designed around nights inside the selected stay-date window. Choose the dates and channel 1. Confirm the selected property in the application navigation. 2. Open Reports → Reservation Metrics. 3. Expand Filters if the criteria are collapsed. 4. Set Date Range. You can also use Month / Year to select a calendar month. The initial range runs from today in the property's time zone through 28 days later. Both displayed endpoints are included when the report fills missing dates with zero rows. 5. Choose Channel. Select one feed for channel-specific results, or All to combine the property's feeds. All does not produce a separate row for each channel. 6. Click View. Changing an input alone does not reload the results. Reservation Metrics filters with Month / Year, Date Range, Channel, View, View - Excel and Cancel controls The controls stack vertically on a narrow screen; the same filters appear side by side on a wider screen. The HTML report appears below the filters on the same page. To change the search, reopen Filters, adjust the criteria and click View again. Cancel returns to the property's Reports page; it does not cancel reservations. Check the result Check the property, channel and dates in the report heading and the Selected stay dates reading line before using the numbers. A selected feed can also be identified by its numeric ID in that line. Rows are grouped by property, supplied night date and mapped room type. They are ordered by property, date and room-type ID. With All, the channel fields are blank; that means the amounts are combined, not that the reservation channel is missing. Keep these limits in mind: - Dates outside the range are expected for overlapping stays. The report does not clip those stays' nightly rows to the selected window. - Zero is not proof that there are no bookings. The report creates zero rows for property room types on selected dates without mapped nightly data. Reservations with missing channel settings or room mappings are omitted, as are room stays without supplied nightly rows. - Amounts keep the supplied price basis. There is no currency column or currency conversion. Do not combine or compare amounts unless you know they use the same currency and basis. The report does not establish whether the supplied price is gross, net or tax-inclusive. - There is no freshness confirmation. The report does not show price coverage, report run time or the latest feed update. Its totals do not prove that every booking was captured or delivered to a PMS. - ALOS and ADTA are arrival-row measures. They can be zero on a date with occupied nightly rows but no arrivals. They are not recalculated across every occupied night. If the report is empty or shows only zero rows, check the property, stay dates and channel. Then compare an expected booking in Reservations → Search and check its room mapping with your administrator if it is absent from the totals. Do not resend a reservation or change inventory to make this report populate. View a spreadsheet or download CSV Browser spreadsheet 1. From the criteria, choose View - Excel. If an HTML report is already open, you can also choose Excel in its View group. 2. Confirm the property, channel and dates in the spreadsheet heading. 3. Use the spreadsheet to inspect the same types of nightly metrics. Its headers use compact names such as TotalAllocation and TotalADR. The spreadsheet has its own Filters section and View Report submit control. To return to the HTML report, choose HTML in its View group. Do not use spreadsheet date cells to open a reservation. This report contains aggregates, not individual reservation IDs, and the current spreadsheet can attach an invalid reservation link to those cells. Open Reservations → Search separately when you need an individual booking. The number appended to the spreadsheet's Reservations heading is not a reliable count of displayed rows; it can show zero while the sheet contains data. Use the rows and their scope instead. CSV download 1. Load and check the report with your intended dates and channel. 2. Choose CSV under Download on the HTML report or spreadsheet. 3. Open the downloaded file and check its property, channel and dates before analysis. CSV dates use yyyy-MM-dd. The CSV contains the report rows, not a guest-level reservation list. It has no currency, capture-time or delivery-status fields. It follows the same whole-stay inclusion rule, so dates outside your selected interval can remain in the download. New window, when shown on the HTML result, opens another view of the current report. It does not refresh or resend reservations. Filter reference Control Meaning and use Property The current property is fixed for this page. Switch property in the application before running another property's report. For a portfolio selection, use the organization-level guide below. Month / Year Shortcut for filling a calendar month's Date Range. Check the resulting dates before View. Date Range Required stay-date selection. End must not precede start. The report uses whole qualifying stays, so displayed rows can extend beyond the selection. Channel One configured reservation feed, or All. A single selection fills Channel ID and Channel Name; All combines feeds and leaves those output fields blank. View Loads the HTML report beneath the criteria. View - Excel Opens the browser spreadsheet for the selected criteria. Cancel Returns to Reports without changing reservations. On-screen column reference The HTML table contains these columns. A row represents one mapped room type on one supplied night, not one booking. Column What it means Property ID The property's ChannelRUSH identifier. Property Name The property name. Channel ID The selected reservation-feed ID; blank when All combines feeds. Channel Name The selected feed's name; blank for All. Date The supplied nightly date, or a date inserted to fill an otherwise missing selected day. Display formatting follows the report's date formatting; CSV is explicitly yyyy-MM-dd . Room Type ID The mapped property room-type ID. Room Type Name The mapped property room-type name. Total Allocation Count of supplied nightly rows. This is not sellable inventory, remaining rooms or a quantity-weighted occupancy measure. Total Arrivals Count of room stays whose first supplied nightly row falls on this date. A multi-room booking can contribute more than one room stay; this is not a unique-booking count. Total Revenue Sum of the supplied nightly prices. Missing mappings are excluded. Currency and tax/net/gross basis are not normalized. Total ADR Total Revenue divided by Total Allocation, rounded to two decimals. Zero when there are no counted nightly rows. ALOS Average number of supplied nightly rows per arriving room stay, rounded to one decimal. Assigned only to the first supplied night; zero when there are no arrivals. Missing nightly rows affect this value. ADTA Average calendar-day difference between the first supplied night and the selected reservation version's receipt date, rounded to a whole day. It is not necessarily lead time from the original sale; a later modification can change the receipt basis. Zero when there are no arrivals. Export header reference The browser spreadsheet and CSV have the same field order and metric meanings as the table above, but their headers differ. CSV dates are invariant; the browser spreadsheet displays dates using its cell format. CSV header Browser spreadsheet header PropertyId PropertyId PropertyName PropertyName ChannelId ChannelId ChannelName ChannelName Date Date RoomTypeId RoomTypeId RoomTypeName RoomTypeName Total Allocation TotalAllocation Total Arrivals TotalArrivals Total Revenue TotalRevenue Total ADR TotalADR ALOS ALOS ADTA ADTA Common problems - View leaves the old result in place: reopen Filters, wait for the date controls to appear, confirm both dates and click View again. Compare the new heading with your inputs. If it still does not reload, record the selected property, dates, channel and visible message for support. - A date-range error appears: enter both dates, with the end on or after the start, and rerun the report. - Totals differ from another report: first compare the property, feed, dates and currency basis. This report includes whole overlapping stays and counts supplied nightly rows; a report limited to selected nights or unique bookings can legitimately differ. Escalate an unexplained difference with the report names, scope and affected dates. - Channel columns are blank: check whether Channel is All. Select one channel and click View if you need a feed-specific result. - A date cell opens an invalid reservation page: return to the report and use Reservations → Search. The aggregate row does not identify a reservation to open. - You cannot find the property or report: ask your administrator to check your assigned-property/report access. Do not switch to another property's data as a substitute. For support, include the property, channel, date range, report view, action time and time zone, and any visible error text. Do not send passwords, payment details or unnecessary guest information. Related - Review reservation metrics across properties - Find and work with reservations
Read booking pace and pickup
Compare captured room nights at two receipt cutoffs, explain the changes within a selected stay period, and export the report without confusing missing history with zero business. Before you start Select the property you want to review. You need access to that property and its reports. Open Reports → Revenue Analytics → Booking Pace / Pickup. Each report covers one property and one Reservation source. The source is the feed through which ChannelRUSH received the booking, not necessarily its original selling source. Do not add overlapping feeds together without reconciling their bookings. This report reads captured reservations. Running it, changing its filters and downloading it do not update inventory or resend reservations. Its historical comparisons depend on retained reservation versions; they are not a complete sales ledger or certified whole-property performance. Run the report 1. Confirm the selected property. 2. Set Stay dates (through inclusive). Choose Month for a calendar month, or enter both date bounds. Use an ordered range of at most 93 days. 3. Choose Reservation source. Check the selection rather than assuming the default is the feed you need. 4. Set As-of time (UTC or explicit offset; blank = now). Leave it blank for the current instant, or enter a timestamp with Z or an explicit offset, such as 2026-10-01T12:00:00Z. A future cutoff is not accepted. 5. If needed, enter Source room ID (optional), Source rate-plan ID (optional) or Currency (blank = separate currencies). Product fields require exact source identifiers, not standard room names. 6. Choose Movement interval: 1, 3, 7, 14 or 30 days. 7. Leave Prior-year alignment (history unavailable) at Calendar, or choose Weekday to change the requested comparison alignment. Neither option enables prior-year pace figures. 8. Click View report. After loading, expand Filters, make your changes and click Update report. Changing fields is not the same as running the report. Confirm the resulting dates, source and interval in the loaded report. If both stay dates are blank, Stay days when dates are blank selects a forward horizon from today in the property's time zone. Its default is 30 days. This is not a receipt-date lookback. A historical as-of time does not automatically move the stay dates into the past. Booking Pace filters showing stay dates, source, receipt cutoff and movement interval The Filters section after a report has loaded. The example selection does not establish that booking history is available for that source. Keep the cutoff deliberate A blank as-of becomes a fixed timestamp when the report runs. Refreshing that URL or changing an interval tab keeps the same cutoff. To obtain a new current cutoff, expand Filters, clear the as-of field and click Update report. The five interval tabs choose which movement detail to inspect; the summary still shows all five windows. Choose the interval before refining the movement table, and recheck table filters after switching tabs. Reset report starts a fresh selection for the current property. It is different from Reset table, which retains the report selection and clears movement-table search, filtering, sorting and paging choices. Check the result Read the property, source, stay dates, As-of and selected movement interval together. Then check History state before interpreting any number. - Retained reconstruction; completeness unverified means the available retained versions could be compared. It does not certify continuous history or complete property coverage. - Cutoff precedes the earliest retained receipt; an opening balance is unavailable means the report cannot establish the opening state. Dashes are not zero pickup. This can also appear when no retained receipt exists for the source. - No retained stays match these filters means no captured stays matched the selected scope. It does not establish that the property had no bookings. - No records to display in the movement table can mean no changed endpoint cells, or no rows matching its table filters. It is not proof that no reservation events occurred. - Extracted is the query time, not the latest reservation receipt or proof of a fresh channel synchronization. Inspect Earliest retained receipt, Latest retained receipt, Missing identity rows and Unusable receipt rows. These describe the selected source's retained data, not only the stay dates or products in your report. Zero diagnostic counts do not certify completeness. What opening, closing and pickup mean Closing is the captured booking state at the as-of cutoff. Opening is the state at the chosen number of days before it. The intervals are exact 24-hour periods in UTC, not property-local midnight boundaries. For each booking, the report uses the highest retained version received on or before each cutoff. A provider's earlier edit time does not move a later-received change back into an earlier snapshot. Imports first appear when received, not at an inferred original sale time. The report chooses the endpoint versions before applying stay and product filters. A cancellation or a move outside your selection does not make an older active version count again. - Bookings counts booking identities contributing matching nights at the endpoint. - Room stays counts contributing room-stay records, not occupied nights. - Room nights counts nights inside the selected stay range. Arrival is included; checkout is excluded. - Night change is closing nights minus opening nights. Moving a stay into or out of your selection can change this without a new sale or cancellation. Movement detail compares endpoint states, not every event between them. Intermediate changes can cancel each other out. An unchanged endpoint can therefore have no movement row even when reservation activity occurred. Movement classifications A classification is selected for the booking's filtered endpoint changes and applied to its changed date/product cells. A row is not necessarily a separate booking or separate event. Movement Meaning First retained observation There is no opening version and the closing version is not marked as an import. This is not proof of a new sale. Imported first observation There is no opening version and the closing version is marked historical/imported. Reinstated The booking changes from canceled to active. Canceled The booking changes from active to canceled; its opening nights are removed even if the cancellation has no room payload. Date / room / rate / currency change (may include repricing) Endpoint dates, source products, currencies or night counts differ. The same booking can also have price changes. A move across your filters may show only the entering or leaving side. Price coverage changed The date/product structure and night counts match, but the number of qualified priced nights changes. Repricing Remaining monetary changes where the structure and price-qualification counts match. Structural changes take precedence over price coverage and repricing. Do not interpret the absence of a separate Repricing label as proof that prices stayed unchanged. Read the summaries All movement windows All movement windows; full selected-scope night counts shows: Column Meaning Window 1, 3, 7, 14 or 30 days. These overlap; do not add them as independent production. Opening Opening cutoff timestamp, not the first booking receipt. Opening nights / Closing nights Selected room nights at those endpoints. Change Closing minus opening nights. History state Whether the comparison is available and its qualification or failure reason. Below it, the selected interval shows Bookings, Room stays, and Invalid room stays across both selected versions. The latter is not a unique issue count. These endpoint counts are different from the number of movement rows. Currency totals The Full-scope currency totals table retains the full report selection, regardless of movement-table filtering. Column Meaning Currency Recorded currency, or Unknown. Currencies are not converted or combined. Opening / closing nights Endpoint nights in that currency. Qualified nights Opening and closing nights qualifying for the monetary calculation. Opening known value / Closing known value The known, qualified portion at each endpoint; these can be partial values. Qualified value change Difference only when all endpoint nights in the included rows have qualified prices. Otherwise unavailable. Only the ChannelRUSH Booking Engine source qualifies monetary values in this report. Other sources can provide room-night counts while their amounts remain unavailable. A qualified night needs a recorded currency and exactly one nonblank recorded nightly price. Missing or duplicate price rows do not become zero prices. A recorded zero price can qualify, but qualification is not independent verification of its accuracy. Amounts are booked nightly room-rate value, including tax already embedded in that rate and excluding separately recorded charges. They are not payments collected, realized revenue, profit or commission-adjusted net revenue. A dash or blank amount means unavailable. Do not replace it with zero. A known endpoint amount can be partial even when displayed as a number; check qualified nights. Zero night change can still accompany a monetary change. Stay-date / source-product breakdown Expand Stay-date / source-product breakdown for the selected interval. - Date / room / rate identifies the occupied night and source product, not its current standard-property mapping. - Currency keeps monetary groups separate. - Opening, First retained, Imported, Reinstated, Canceled, Date/room/rate changes, and Closing reconcile night counts. Cancellation changes are signed reductions. - Qualified value change follows the price-coverage rules above. The displayed breakdown is limited to its first 100 rows. Paging the separate movement table does not advance this breakdown. Use Legacy CSV for the complete date/product breakdown. Prior-year pace Prior-year pace displays the requested comparable stay dates and receipt cutoff, but the historical comparison remains unavailable. Calendar and Weekday change alignment only. Prior-year final production is not substituted for what was on the books at that earlier time. Do not treat unavailable figures as zero or assume another filter enables them. Inspect and refine the movement table The movements section contains changed date/product cells for the selected interval. It does not contain all opening and closing business. 1. Confirm the opening and closing cutoffs above the table. 2. Use Search to find source room IDs, source rate-plan IDs or movement labels. Search is case-insensitive; it does not search guest details, currencies, amounts, dates or reservation-version IDs. 3. Use column sorting and filter controls to narrow supported fields. Text fields offer equality or contains matching; numeric fields offer equality or bounds; stay dates offer date comparisons. Identifier and currency filters use equality. Receipt/source timestamps are not sortable or filterable. 4. Use the pager and Items per page for 25, 50 or 100 rows. The default is 100. 5. Use Columns, column resizing/reordering, and Density to adjust presentation. These browser preferences do not change the underlying report or the standard download schema. 6. Where a version link is available, open Opening version or Closing version to inspect its referenced retained reservation. Current reservation-access and password checks still apply. Multiple column filters combine with AND. Unknown numeric values do not become zero and do not match a numeric comparison, including Not equal. Up to three sorts and ten column filters are supported; this table does not group rows. The matching-movement totals cover all matching pages, not only visible rows. They still cover changed cells only, so they are not a replacement for the full-scope OTB totals above. Interactive table refinements work on the loaded movement data; they are not a new reservation-history query. Movement column reference Column What it identifies or measures Stay date Occupied night inside the report range. Source room / Source rate plan Recorded source product identifiers. A unique nightly rate-plan ID takes precedence over the room-stay plan; conflicting nightly IDs remain unknown. Currency Recorded currency; no conversion. Movement Endpoint classification described above. Opening nights / Closing nights / Night change This changed cell's endpoint room nights and their difference. Opening qualified nights / Closing qualified nights Endpoint nights qualifying for monetary calculations. Opening known value / Closing known value Qualified known portion, potentially partial. Qualified value change Difference only with complete qualified prices at both endpoints. Opening version / Closing version Retained reservation-version identities, not channel booking confirmation numbers. Opening can be blank when no opening version exists. Opening receipt UTC / Closing receipt UTC Receipt time of the selected version, not the report cutoff. Closing source time UTC Supporting source-edit time, where available. It does not decide receipt-cutoff eligibility. Download the right scope Choose Download report for report-wide exports. Choose Download matching movements CSV or Download matching movements XLSX beside the table for its current matching selection. Download Scope Summary CSV / Summary XLSX All five windows, grouped by currency. Ignores movement-table search, filters and paging. Movements CSV / Movements XLSX All changed cells in the selected movement interval, ignoring movement-table refinements. Download matching movements CSV / XLSX All movements matching table search, filters and sorting, across every page—not only the visible page. Legacy CSV All five windows' complete date/product/currency breakdown and movement detail in one file. Ignores table refinements and paging. Columns and column order are display preferences; ordinary downloads retain their standard fields. Whole-window booking and room-stay counts repeat on currency/detail rows: do not sum the repeated values. In Legacy CSV, do not add Summary and Movement rows together; they describe overlapping business at different levels. Movement downloads are unavailable when the selected history window cannot be reconstructed. Summary and Legacy CSV retain unavailable-state markers. An available window with no movements yields a header-only movement CSV, not an invented zero movement row. Downloads rerun the report at its selected cutoff. Their extraction time can differ from the screen, and retention changes or corrections can change a later reconstruction. Compare scope, cutoff and extraction time when reconciling files. XLSX includes a Context sheet plus Summary or Movements. IDs remain text, date cells are dates, UTC timestamps are text and amounts/counts are numeric. Unavailable values are blank. CSV uses ISO dates and invariant numbers; formula-like text can carry a protective leading apostrophe. An empty movement CSV has headers but no data row carrying the repeated context fields. Use New window to open the same selection without normal application navigation. Confirm the property, dates and cutoff there too. Daily OTB opens a separate report; it is not a continuation of all your pickup filters. Filter reference Field Values and behavior Month Fills a calendar month's stay dates. Run or update the report afterward. Stay dates (through inclusive) Both bounds or both blank; at most 93 inclusive days, ordered, in years 2000–2100. Checkout remains excluded from each stay. Reservation source One source. The initial choice prefers a connected booking engine; otherwise another connected source is selected. Verify it. As-of time (UTC or explicit offset; blank = now) Blank resolves to a fixed current cutoff on execution. Nonblank requires an explicit UTC offset or Z, at most 64 characters, not before 2000 or in the future. Source room ID (optional) Exact source ID, up to 200 characters. Blank means no room restriction. Spaces are significant. Source rate-plan ID (optional) Exact effective nightly source plan ID, up to 200 characters. Blank means no rate-plan restriction. Spaces are significant. Currency (blank = separate currencies) Recognized code such as USD; trimmed and uppercased. Blank retains separate currencies, not currency conversion. Stay days when dates are blank 1–93; default 30. Forward horizon from property-local today. Explicit dates take precedence. Movement interval 1, 3, 7, 14 or 30 days; default 7. Selects detail while the summary retains every window. Prior-year alignment (history unavailable) Calendar or Weekday; default Calendar. Changes proposed alignment, not historical availability. Export field reference Header names below are exact. Modern Summary and Movements files begin with the common fields, then their dataset-specific fields. The workbook's Context sheet additionally explains selection and qualification. Common modern fields Headers Meaning contract Export-definition identifier, retained-receipt-pickup-export-v1 . propertyId , feedId Selected property and source identities. stayStart , stayEnd Inclusive stay-date selection. asOfUtc , windowDays , openingUtc Closing cutoff, interval length and opening cutoff. extractedUtc This query's extraction instant; not source freshness. roomFilter , rateFilter , currencyFilter Applied report restrictions; blank means unrestricted. comparison Calendar/weekday alignment request, not proof a prior-year comparison ran. historyState , historyBasis , amountBasis Availability reason and qualifications for history and monetary interpretation. oldestReceipt , newestReceipt Feed-wide retained receipt limits, where available. missingIdentities , untimedRows Feed-wide diagnostics, repeated on data rows; do not sum. stlyState Explanation of same-time-last-year unavailability. Summary fields Headers Meaning currency Currency group, possibly blank. openingNights , closingNights , nightChange Endpoint room nights and closing-minus-opening. openingQualifiedNights , closingQualifiedNights Nights with qualified recorded amounts. openingKnownValue , closingKnownValue , valueChange Known portions and fully qualified change. Blank is unavailable. openingWindowBookings , closingWindowBookings , openingWindowRoomStays , closingWindowRoomStays Whole-window counts repeated per currency row. Never sum across those rows. qualification Whether monetary change has complete qualified endpoint prices or remains unavailable. Unavailable windows have blank night/booking/stay counts. Available windows with no retained stays have zero counts but blank monetary values. Read history state before interpreting either. Movement fields Headers Meaning stayDate , room , ratePlan , currency , kind Date, source products, currency and movement label. openingNights , closingNights , nightChange Changed cell's endpoint nights and difference. openingQualifiedNights , closingQualifiedNights Changed cell's qualified nights. openingKnownValue , closingKnownValue , valueChange Known endpoint portions and qualified monetary change. openingVersionId , closingVersionId Supporting retained versions, not channel booking references. openingReceipt , closingReceipt , closingSourceEffective Selected version receipt/source lineage, in UTC; source time is not cutoff eligibility. qualification Monetary completeness qualification for the row. Legacy CSV fields Legacy CSV uses different capitalization and combines breakdown and movement rows. Headers Meaning Contract , PropertyId , SourceId Definition retained-receipt-pickup-v1 and selected identities. StayStart , StayEnd , AsOfUTC , WindowDays , OpeningUTC , ExtractedUTC Selection dates, cutoffs, interval and extraction instant. RoomFilter , RateFilter , CurrencyFilter , Comparison Report restrictions and requested prior-year alignment. HistoryBasis , State , AmountBasis Reconstruction, availability and monetary qualification. RowKind Summary, Movement, No retained stays in selected scope, or Unavailable. Summary here means date/product breakdown, not the modern currency summary. StayDate , Room , RatePlan , Currency Breakdown or movement cell identity. OpeningNights , ClosingNights , NightChange , OpeningQualifiedNights , ClosingQualifiedNights Cell counts and change. Blank on empty/unavailable marker rows. OpeningKnownValue , ClosingKnownValue , QualifiedValueChange Known portions and qualified monetary change. Movement , OpeningVersion , ClosingVersion , OpeningReceipt , ClosingReceipt , ClosingSourceEffective Movement category and lineage. Blank on Summary/marker rows means not applicable, not failed processing. OldestRetainedReceipt , MissingIdentityRows , UntimedRows , STLYState Repeated feed/history qualifications. OpeningBookings , ClosingBookings , OpeningRoomStays , ClosingRoomStays Repeated whole-window counts. Zero can be valid on available empty markers; blank denotes unavailable. Do not sum repeated counts. Common problems - Opening balance unavailable: the cutoff precedes retained history, or no history is retained for that source. Confirm the source and try a shorter interval or later cutoff only if that answers your question. If usable history is still absent, ask support about retained coverage. Repeated runs cannot recreate missing history. - Receipt timestamps, status or room dates prevent reconstruction: the report has rejected unusable retained evidence rather than returning partial totals. Some checks cover the broader source, so narrowing products may not remove the warning. Send support the property, source, stay dates, cutoff with time zone, interval and exact message. Do not edit bookings to suppress the warning. - No stays or no movements: check the report selection first, then Reset table to remove table restrictions. Remember that unchanged endpoints can hide intermediate activity. Escalate expected missing business with the selected scope and relevant booking reference, without guest/payment details. - Amounts are blank but nights exist: check the source, currency and qualified-night counts. Non-booking-engine sources do not qualify monetary values here. Unknown values are not zero; use a qualified accounting source for financial decisions the report cannot support. - Dates or cutoff rejected: supply both stay dates, keep the range within 93 days and use a nonfuture as-of with Z or an explicit offset. Correct the field and run again. If a copied or manually altered URL fails, reopen through the report menu instead of changing unfamiliar query parameters. - Report exceeds current limits: narrow the stay range and, where useful, source-product scope. Changing only the selected movement interval does not reduce all historical snapshots; narrowing one field may not resolve every bound. Contact support if a relevant bounded selection still fails. Do not assume a failed query returned complete totals. - Screen and file differ: compare property, source, dates, cutoff, interval, extraction times and report-wide versus matching-table scope. Standard downloads ignore visible-column choices. If those agree but results still differ, provide the report URL and export context to support. - Filters changed after switching interval tabs: recheck table search and filters, then apply them again. Choose the interval before refining the table. Do not resend reservations, alter prices or submit operational changes to make report warnings disappear. Related - Analyze booking patterns, length of stay and seasonal trends — current captured production and receipt-window analysis, not historical OTB snapshots.
Read daily on-the-books revenue
Use Daily Revenue / OTB to see captured room nights and available booked room-rate value for each stay date, then trace those figures to supporting room stays. This is current captured business for one property and one reservation feed. It is not hotel occupancy, available inventory, realized revenue or a historical “as of” snapshot. Do not add feeds together as if duplicate bookings had been removed across them. Before you start Sign in with access to the property you want to report on. The report does not require an Org Admin role. Reservation details remain subject to their own access checks. Check which reservation feed you want. ChannelRUSH Booking Engine can supply qualified monetary values; other feeds provide captured counts without qualified value or ADR. The feed initially selected is not evidence that it contains your property's reservations. Run the report 1. Select the property in Channel Manager. 2. Open Reports → Overview. 3. Open Daily Revenue / OTB. 4. In Filters, choose Stay dates (through inclusive). Use Month to fill a whole month, or choose a start and end date. 5. Select Reservation feed explicitly. 6. Choose Currency and Business status. Leave currency at All currencies, kept separate unless you need one currency. Active business is the default. 7. If needed, enter an exact Channel room ID or Channel rate-plan ID. 8. Click View report. For a later change, expand Filters, change the selection and click Update report. Changing a field alone does not run the report. After the first run, confirm that results and the selected scope appear. For subsequent interactive updates, wait for Report updated, then check the date range, feed and scope shown with the results. While an update is running, the displayed results still belong to the previous completed selection. If the update fails, the old results remain on screen; do not read them as the new selection. Daily OTB report filters in a narrow browser, showing stay dates, feed, currency, status, blank-date period and exact channel product filters The filters stack vertically in a narrow window. This example includes active and canceled business separately. Read the results Room nights and booked value Stay dates use the property's local calendar dates. Checkout is excluded. A stay arriving on Monday and checking out on Wednesday contributes Monday and Tuesday nights. Only nights inside the selected period contribute to its Clipped nights. If you set a report-level rate-plan filter, only nights matching that nightly rate attribution remain; these need not be every in-range night of the stay. The report uses the latest captured reservation version within the selected property/feed/source-booking identity. It is not a history of all versions. A multi-room booking can contribute several room stays. Do not sum daily Bookings or Room stays to calculate distinct bookings for the whole period: the same stay can appear on several dates. Active and canceled business are separate when you select both. Canceled means the latest captured version is canceled; it is not a measure of when the cancellation occurred. A canceled version without usable stay dates may contribute no daily nights. Money has a stricter coverage rule than room nights: - A priced night has exactly one usable nightly price. A stored price of zero is a valid price. - A qualified night also belongs to the booking-engine feed and has a known currency. - Known booked room-rate value sums qualified nightly prices. ADR on qualified nights divides that value by qualified nights, not by every captured room night. - Missing, null or duplicate nightly prices do not remove otherwise valid room nights. They leave those nights without qualified value. - A dash (—) means value or ADR is unavailable, not zero. Blank numeric export cells have the same meaning. Partial value covers qualified nights only. - Value includes tax already embedded in the room rate, but excludes separately stored taxes and fees. It is not net revenue after commission or profit. Currencies are kept separate; there is no currency conversion. Compare coverage as well as value before using the figures for revenue decisions. Different display and spreadsheet formats can round the same underlying value differently. Stay-date calendar Expand Stay-date calendar — captured room nights if needed. Each date shows nights by status and known value by currency. Darker shading means more captured nights relative to the displayed calendar, not higher occupancy. Click a date's status/night count to open supporting stays for that date and status. The selection retains your currency and product filters. Return to report, when shown, takes you back to the parent selection. One-day Daily OTB calendar with zero active nights, unavailable value and the explanation that zero captured nights is not hotel occupancy or availability This empty example shows how to read zero nights and unavailable value; it does not demonstrate populated production. The daily summary below the calendar shows counts, price coverage, mapping coverage, known value and ADR. Its date links also narrow to that row's currency and status when a link is available. A single currency or status may appear in the scope line instead of a separate column. Supporting room stays Use Supporting room stays to inspect the bookings behind the selection. A reservation link opens the retained reservation version; that page shows the whole booking while this report clips nights to the selected period. Opening a link does not resend or change the reservation. - Search finds substrings in channel room or room-stay rate-plan IDs. It is not a guest-name or reservation-number search. - Use column filters and sorting to narrow or order the table. Multiple filters are combined: a row must match every condition. - Choose 25, 50 or 100 rows per page. The default is 100. - Columns, column reordering/resizing and Density change presentation. They do not change the report selection or generated download columns. - Reset table clears table-specific narrowing and resets sorting and pagination; saved column and density preferences are separate. Reset report returns to the initial, unrun report selection. Table searches and column filters do not recalculate the daily summary or calendar. Matching-table totals cover all matching pages, not only the visible page, and stay separated by currency, status and value basis. If you change the report filters, existing table filters can remain; use Reset table when that narrowing is no longer wanted. If the enhanced table is unavailable, expand Supporting stay table controls, change the full-page controls and click Update table. Find room or rate-plan ID performs the same ID search. Expand Selected feed room-stay detail for the simpler fallback table. It has fewer columns than the enhanced table. Check and download your selection 1. Confirm the property, stay-date range, reservation feed, currency and business status in the report. 2. Check qualified-night coverage before interpreting value or ADR. 3. If the table is narrower than expected, review its search/filters or click Reset table. 4. Open Download report and choose the dataset you need: - Daily summary CSV or Daily summary XLSX: the daily report selection, unaffected by table filtering. - All supporting stays CSV or All supporting stays XLSX: all supporting stays for the report selection, ignoring table search, filtering and sorting. 5. For the table's current narrowing, use Download matching table CSV or Download matching table XLSX instead. These include all matching pages, not only the page on screen. XLSX contains a Context sheet and a Summary or Stays dataset. CSV contains dataset headers and rows. Empty exports can contain headers only. The current download menus do not insert a fabricated zero-value data row. Downloads read the data again. They are not a frozen copy of an earlier screen. If reservations change between viewing and downloading, refresh the report and compare extraction times. A report-update notice can also warn that summary and rows were read separately; refresh before reconciling a changing dataset. New window opens the report without the normal navigation. Inventory and restriction context opens a separate report for the same property; it does not carry your Daily OTB dates, feed or product filters. Set that report's own selection before comparing it. Daily OTB viewing and downloading do not update inventory or send reservations. Filter reference Field Meaning, defaults and accepted values Month Shortcut that fills a whole calendar month. Click View report or Update report to apply it. Stay dates (through inclusive) Both dates supplied, or both blank. Default displayed period starts today in the property's time zone and covers 30 days. Start must not follow end. Maximum range is 366 inclusive days; supported years are 2000–2100. With native date inputs, the labels are Start date and End date . Reservation feed One feed for this property. Check it before each run; do not assume the initial booking-engine selection is the feed you intend. Currency All currencies, kept separate , or one listed currency. No conversion or combined cross-currency value. Business status Active (default), Canceled , or Active and canceled, kept separate . These are latest captured states, not cancellation-event dates. Days when both dates are blank A whole number from 1 to 366; default 30, including when this field is cleared. With both dates blank, the period starts today and runs forward for this many days. It does not override explicit dates. Channel room ID Blank means all rooms. Otherwise an exact stored channel room ID, up to 200 characters; it is not a room name. Avoid accidental spaces. Channel rate-plan ID Blank means all rates. Otherwise an exact channel rate-plan ID, up to 200 characters. This report filter uses nightly rate attribution where available; the table's Room-stay rate ID can differ. Avoid accidental spaces. Daily summary columns Column What it means Stay-date period The stay date represented by the row. Currency Currency of the captured records; may be shown in the scope line when only one is present. Unknown currency cannot qualify money. Status Active or Canceled; may be shown in the scope line for a single status. Bookings Captured bookings contributing to this date/currency/status bucket. Not additive across dates. Room stays Room stays contributing to the bucket. Not additive across dates. Room nights Valid captured nights inside the selection. Priced nights / nights Nights with one usable nightly price compared with captured nights. Qualified priced nights Priced nights eligible for known value and ADR. Unmapped room nights Nights whose channel room does not resolve to exactly one mapped room. They remain in captured counts; mapping does not itself qualify or disqualify money. Known booked room-rate value Sum of qualified room-rate amounts in this currency, or a dash when unavailable. ADR on qualified nights Known value divided by qualified nights, or a dash when none qualify. Supporting-table columns Enhanced-table column What it means Reservation ID ChannelRUSH's internal ID of the retained reservation version, not the channel confirmation number. Room-stay ID Identifier of the room stay inside that retained reservation. Arrival , Checkout Full room-stay dates. Checkout is excluded from nights. Room ID Captured channel room ID. Room-stay rate ID Rate-plan ID recorded on the room stay; it may differ from nightly rate attribution used by the report filter. Currency , Status Currency and latest captured Active/Canceled state. Full LOS Full length of stay before clipping. This column cannot be sorted or filtered. Clipped nights Nights remaining inside the selected report period. Priced nights , Qualified nights Price coverage and the subset eligible for monetary totals. Known value Qualified room-rate value for those clipped nights, otherwise unavailable. The fallback table uses Reservation, Room-stay ID, Channel room ID, Arrival, Checkout, Full LOS, Clipped nights, Price rows and Status. Price rows is the usable priced-night count, not proof that all captured nights qualify for monetary totals. Table limits are three sorts, ten filters and 100 search characters; each filter value is limited to 128 characters. IDs, currency and status support equality/inequality. Room/rate text also supports contains; dates and numbers support range comparisons. Use Active or Canceled for status, YYYY-MM-DD for date filter values and a decimal point for numeric values. ID values must be positive. There is no grouping control on this report. CSV and XLSX field reference These are the exact headers used by the current download menus. The summary and supporting datasets have different schemas. Daily summary, in order: contract, propertyId, feedId, start, end, extractedUtc, stayDate, currency, status, basis, bookings, roomStays, roomNights, pricedNights, qualifiedNights, knownValue, adr, unmappedNights, qualification All supporting stays and matching table, in order: contract, propertyId, feedId, start, end, extractedUtc, reservationId, roomStayId, arrival, departure, room, ratePlan, currency, status, basis, los, roomNights, pricedNights, qualifiedNights, knownValue, adr, supportingVersionId, qualification Header(s) Meaning contract Export schema identifier; current menu downloads use report-pilot-v1 . propertyId , feedId Selected property and reservation feed IDs. start , end Inclusive report period, not full booking dates. extractedUtc Time this export was extracted, in UTC. Not the time the source reservation changed. stayDate Summary row's stay date. currency , status , basis Currency, captured status and monetary/counting basis. Keep these contexts separate when aggregating. bookings , roomStays Daily bucket counts, not distinct totals across the exported dates. roomNights , pricedNights , qualifiedNights Captured/clipped nights, usable priced nights and monetarily qualified nights. knownValue , adr Known qualified value and ADR on qualified nights. Blank is unavailable; numeric zero is a recorded/calculated zero. unmappedNights Summary nights without a unique room mapping. reservationId , roomStayId Retained reservation-version and room-stay identifiers. arrival , departure , los Full arrival/checkout dates and full stay length. room , ratePlan Channel room ID and room-stay rate-plan ID. supportingVersionId Retained reservation version supporting the row; for Daily OTB this matches reservationId . qualification Explanation of monetary eligibility/coverage. Read it with the numeric columns. Dates are exported as ISO dates. IDs remain text in XLSX. Potential spreadsheet formulas in CSV text are protected. Old bookmarked legacy CSV links can produce a different schema; use the current download controls for the headers above. Common problems - “No captured stays match these filters.” The selected feed and period have no matching captured stays. Check the feed, widen dates or clear exact room/rate filters. Zero calendar nights do not establish zero hotel occupancy or availability. If you expect a particular booking, verify it in Reservations and contact support with the property, feed, dates and relevant error—not payment details. - Room nights appear but value or ADR is blank/dashed. Check the feed, currency and qualified-night coverage. Non-booking-engine feeds are counts-only here. Missing or ambiguous nightly prices also leave value unavailable. Do not substitute zero or multiply ADR by every captured night. - The table and calendar show different totals. Table filtering affects supporting rows only. Clear table filters with Reset table before comparing. For a fresh download mismatch, refresh and compare extraction times. - “Update failed. Previous results retained.” The new selection was not committed. Retry update retries the report read, not a reservation or inventory send. If it persists, reload or sign in again, reselect the filters and report the error to support. - A date or table filter is rejected. Correct the reported field using the limits above, then resubmit. For an invalid copied/bookmarked URL, start again from Reports → Overview → Daily Revenue / OTB rather than repeatedly editing unsupported query values. An error screen can use the simpler fallback controls. - Invalid stays or missing source identities are reported. These are data-quality diagnostics, not additional in-period nights. Invalid stay dates cannot be assigned reliably to the selected period; missing source-identity counts can cover the whole property/feed. Give support the property, feed, selected dates and diagnostic text if reconciliation depends on these records. - A report or reservation link is unavailable. Confirm the selected property and your access. A reservation-detail link does not grant permissions. If repeated drill-downs reach a return-navigation limit, use Return to report to step back or reopen the report from Overview. For unresolved problems, include the property, reservation feed, selected dates, currency/status, action time and time zone, and exact error text. Do not send passwords or payment information.
Review channel settings and mappings
Use the Channel Settings report to review a property's saved channel configuration and identify room or rate mappings that need attention. The report does not edit configuration or send inventory. Its counts, badges and green checks describe stored settings—not a live connection test, successful inventory delivery or acceptance by a channel. Before you start - Sign in with access to the property you want to review. - Select that property before opening the report. Check its name above the results. - You do not need settings-edit permission to read this report. Changing configuration through a Settings shortcut requires the appropriate editing permission. Open and review the report 1. Open Reports. 2. Under Diagnostics, select Channel Settings. 3. Check the property name above Channel Configuration Overview. 4. Review the overview for channels and mapping gaps. 5. If Channels is available, open it and select the channels you want to inspect. 6. Review each visible channel's status, Hotel ID, Setup value and Mapping record timestamp. 7. Read Key Settings, then inspect Room Types & Rate Plans for Unmapped, Invalid Mapping or Not Setup entries. Channel Configuration Overview showing eight channels, eight active channels and zero unmapped room types or rate plans The overview always covers the property's included channels, even when the Channels filter hides some cards. Filter channels The Channels dropdown appears when the report has more than one channel. Every channel starts selected. - Selecting a subset immediately hides the other channel cards. There is no Search or Apply step. - Select all checks every channel if any are unchecked. Clicking it when every channel is checked clears the checkboxes. - No checked channels means no filter: all cards are shown. It does not mean an empty result. - The overview counts and attention message do not change with this filter. - Reloading the report or opening New window starts with all channels again. The current checkbox selection is not preserved. Expand details Channel and room details start expanded. Click a channel heading to collapse or reopen its body. Click a configured room's heading to collapse or reopen its rate plans and room settings. Toggle Details hides or shows the entire Room Types & Rate Plans list for that channel. These controls only change what is visible; they do not change setup or mapping counts. A yellow Unmapped room entry has no expandable rate-plan details. Expanded Mirage channel card with saved settings, Studio room details and Standard and Package rate-plan IDs This example shows the channel's saved settings and room/rate IDs. Fully Configured is not confirmation that every flow is enabled or has succeeded. Open the relevant settings Each channel card has a Settings link to that channel's configuration for the same property. The booking-engine card also has CRS Settings. These links open editors in the same tab. They are navigation shortcuts, not repair or retry buttons. Do not change mappings solely to remove a warning: first confirm the intended room, rate plan and channel IDs. Only someone with the appropriate permission should save changes. After an authorized configuration correction, return to Reports → Diagnostics → Channel Settings and review the affected card again. A report reload reads stored configuration; it does not request a fresh mapping catalog from the channel. Open a separate report window Click New window to open a navigation-reduced report in another tab or window, depending on your browser. The original report remains open. The new view keeps the property context, but not your current channel checkbox selection or collapsed sections. This report does not offer spreadsheet, CSV, PDF, clipboard or scheduled-email controls. There is no date range or historical view. Check the result For each channel you intended to review: 1. Confirm the Hotel ID and room/rate ID values match the intended channel products. A nonblank ID alone does not prove that it is the correct target. 2. Check the status and any Invalid Mappings, Unmapped Room Types or Unmapped Rate Plans counts. 3. Expand the relevant rooms and read their own Setup and Inventory Send Enabled values. A channel badge does not replace these checks. 4. Read Mapping record timestamp before treating the catalog comparison as current. Unavailable or zero reported issues is not a successful live channel check. A clean-looking report establishes only what this stored-configuration view checks. It does not confirm that rates or availability reached the channel, reservations were handled successfully, or the channel is selling. Verify those outcomes separately in the relevant operational records or with the channel. Field reference Property overview Field What it means Total Channels Number of channel cards included from the property's saved settings. It is not the number of all channels available in ChannelRUSH. Active Channels Included channels whose property-channel setup flag is on. It is not a count of successful connections or recently active channels. Unmapped Room Types Stored channel-catalog rooms with no matching local room setting for that channel ID. This is a channel-catalog-to-ChannelRUSH comparison, not a list of every property room missing a channel target. Unmapped Rate Plans Stored channel-catalog rates missing from a matching configured room. Rates beneath a wholly unmapped channel room are not included in this count. The same rate across different rooms or channels can contribute more than once. Attention message Appears for unmapped rooms, unmapped rates or invalid room mappings. It can therefore appear with both overview unmapped counts at zero. Check the channel cards for Invalid Mappings . Channel status badges The report uses the first applicable status in this order: Status Meaning Not Setup The channel's saved settings are not marked as set up. This badge takes precedence over mapping warnings. Invalid Mappings At least one configured room ID is missing from a nonempty stored channel room catalog. Incomplete No invalid-room finding takes precedence, but there are counted unmapped rooms or rates. Fully Configured Channel setup is on, there are no counted mapping issues, and at least one room is counted as mapped. Setup Channel setup is on with no counted issues, but no rooms are counted as mapped. Fully Configured is a limited structural result. It can coexist with disabled sending or handling, rooms or rates marked Not Setup, no mapped rates, or unavailable channel-catalog data. Rate IDs are not checked for an Invalid Mapping state. Channel header and counts Field What it means Channel name The channel whose saved settings are being shown. Hotel ID The hotel's identifier on that channel, not necessarily its ChannelRUSH property ID. Not Set means the saved channel hotel ID is blank. Currency Saved currency code for the channel configuration. Omitted when blank; it does not indicate a currency conversion. Setup: Yes/No Property-channel setup flag. The status badge uses the channel's saved settings and additional mapping rules, so read both rather than treating them as one health indicator. Mapping record timestamp Timestamp of the stored mapping record, shown with its recorded offset. Unavailable means no usable mapping-record timestamp is available. Stored mapping data may be cached; this is not a live channel verification time. Unmapped Room Types This channel's catalog rooms without matching local settings. Always shown, including zero. Unmapped Rate Plans This channel's catalog rates without matching settings beneath already matched rooms. Always shown, including zero. Invalid Mappings Count of configured room IDs absent from a nonempty stored channel room catalog. The tile appears only when the count is above zero. An absent or empty catalog skips this validity check; it does not confirm the IDs are valid. Key Settings These are display-only indicators, not editable switches. A green check means the saved setting is enabled; a red cross means it is off. An omitted indicator is different from a displayed red cross. Indicator What it means Inventory Send Saved channel-level inventory-send flag. Shown for channels with inventory-send capability. It does not prove an update was delivered. Inventory Receive Whether the saved receive mode is anything other than off. Shown for channels with inventory-receive capability. The indicator does not distinguish the enabled receive modes. Reservation Handling Saved reservation-handling flag. It does not show destinations, queue results or successful booking processing. Content Send Saved content-send flag. Shown for channels with content-send capability. It does not prove content delivery. Other channel and product requirements can affect operation even when an indicator is green. Room types Field or state What it means Room name and ID Saved room name and channel room ID. On yellow Unmapped rows, these come from the stored channel catalog. Unmapped A room exists in the stored channel catalog without a matching local room setting. No nested rate list is shown for that room. Confirm whether it should be distributed before treating its absence as an error. Invalid Mapping A configured room's channel ID is absent from a nonempty stored channel catalog. This state takes precedence over Not Setup . Green check / Not Setup When there is no invalid-room finding, the icon reflects the room's setup flag: green for on; a gray minus and Not Setup for off. N rate plans Number of local rate-plan settings for the room, including settings with blank channel rate IDs that are not displayed below. It can differ from the number of visible rate rows. Setup: Yes/No Saved room-level setup flag. Inventory Send Enabled: Yes/No Saved room-level inventory-send flag, separate from the channel-level setting. Allocation: n% Saved allocation percentage, when present. It is not available-room inventory. Its display alone does not establish that the percentage is applied to every update or property. Omission is not a displayed zero. Locally configured rooms with blank channel room IDs are omitted from the room list. The report is therefore not an exhaustive checklist of every property room or virtual product. Rate plans Field or state What it means Rate-plan name and ID Saved rate-plan name and channel rate ID. Yellow Unmapped entries use the stored channel-catalog name and ID. Unmapped A rate exists in the matching stored channel room catalog but has no local rate setting for that ID. Green check The local rate's setup flag is on. It does not verify that the ID still exists on the channel or that prices have been accepted. Gray minus and Not Setup The local rate's setup flag is off. Local rates with blank channel rate IDs are omitted. There is no separate invalid-rate-ID check, so a stale nonblank rate ID can still appear without a warning. Common problems No channels are shown No Channels Configured means the report has no channel settings to display for the selected property. Check the property name first. If channels should already exist for that property, ask your administrator or support to check its channel configuration. Clearing every checkbox is not how to produce this empty state; that shows all included cards. The Channels dropdown is missing It is not shown for zero or one included channel. Review the available card, or confirm that you selected the intended property if you expected more channels. Escalate if expected configured channels are missing. The overview does not match the visible cards The overview is property-wide; the dropdown only hides cards. Select every channel to compare the full set. If the attention message appears with zero unmapped counts, inspect Invalid Mappings on the cards. Fully Configured appears beside disabled or Not Setup details The badge does not test every operational flag or every child setup state. Review Key Settings, room setup and rate setup separately. Ask an authorized administrator to investigate any mismatch with the intended configuration; do not use the badge as a delivery result. A mapping looks wrong or the timestamp is unavailable Confirm the property, channel, Hotel ID and affected room/rate IDs. Compare them with the products you intend to use. The report compares stored data and cannot determine whether a chosen ID is the intended product. An old or unavailable mapping record can also limit the comparison. Use Settings to inspect the relevant configuration if you have access. Reloading the report is safe for viewing stored settings, but is not a forced channel refresh or repair. If the expected mapping remains unclear, ask support to review it before changing IDs. A room or rate list is empty, or its count looks different No room types have been mapped for this channel yet. appears when neither local room settings nor stored channel rooms are available. No rate plans configured for this room type. appears when neither local nor matching catalog rates are available. Blank-ID local entries are hidden, while the room's rate-plan count includes them. An empty-looking rate list can therefore have a count without the empty-state message. Check configuration through an authorized administrator rather than assuming that every underlying setting is absent. You can read the report but cannot save in Settings Report access and settings-edit permissions are separate. Ask your organization administrator to confirm who is authorized to make the change. Do not attempt a broader edit to work around a permission restriction. What to send support Provide the property, channel, relevant hotel/room/rate IDs, displayed status or warning, and Mapping record timestamp. Include when you observed the issue and your time zone if timing matters. A focused screenshot can help. Do not send passwords, payment details or unrelated guest information.
Review channel setup across your organization
Use Org Channels Summary to compare channel setup across the properties you can access and find the right settings or processing screen for follow-up. Set up is a configuration indicator, not confirmation that updates or reservations were delivered. A channel can be set up while individual products remain unmapped or a particular operation is switched off. Before you start - Select a property in the organization you want to review. The report covers eligible properties in that property's organization, not only the selected property and not every organization in your portfolio. - Organization administrators see eligible properties within their authorized organization scope. Other users see their assigned eligible properties. Inactive properties and properties with no attached channels are not shown. - Reading this summary does not grant permission to edit channel settings. Ask your organization administrator if you need access to a property or an editing screen. Open and review the summary 1. Select a property in the required organization. 2. Open Reports. 3. Under Diagnostics, select Org Channels Summary. 4. Find the property you want to review under Org - Channels Summary. 5. Read the setup count beside the property name. 6. Check the individual channel names and their Set up or Not set up labels. Properties appear in name order. A property's list can contain PMS, CRS and booking-engine connections as well as online travel agencies. It is a list of attached channels, not a catalogue of every channel you could add. There are no date filters, property checkboxes or editable configuration fields on this report. Selecting another property in the same organization does not turn it into a single-property report. Investigate a setup finding 1. Find the channel marked Not set up under the correct property. 2. Select its channel name to open Channel Settings in a new tab. 3. Confirm the property and channel on that screen. 4. Review its setup warnings and required information. If password re-verification is requested, complete that prompt using your own account. 5. Have an authorized administrator resolve the specific setup requirement, then reload Org Channels Summary to check the stored setup result. The summary does not identify which requirement is missing. Do not guess credentials, alter mappings or resend inventory solely because a channel says Not set up. Requirements differ by channel. Opening Channel Settings can initialize or refresh stored setup information. You do not need to submit a settings change merely to inspect the screen. Editing and saving settings is a separate task. Check processing separately Each property's card has two investigation links. Both open in a new tab for that property; neither starts a resend. - Processing Status - Summary opens Updates - Processing Summary, with inventory-update processing counts and links to detail. - Processing Status opens Update Status, where you can inspect individual inventory updates. The link does not select a channel or date range for you. Check the property's context, choose the relevant Channel and other search filters, and click Search before interpreting the results. Status on Update Status refers to update processing, not the setup flag in this summary. Review the relevant updates and their dates instead of treating Set up as proof of channel acceptance. These links investigate inventory updates; they do not confirm reservation delivery. An empty processing search does not prove successful delivery or that a problem is resolved. Do not choose a resend or retry action until you understand the affected scope and why it is needed. Check the result After a setup correction, reload this report and find the same property and channel. Set up means the stored configuration meets the channel's setup indicator. If every listed channel meets it, the property's heading shows N channels set up. That confirms the setup indicator only. It does not establish that every room and rate plan is mapped, all operations are enabled, or the latest inventory reached the channel. Use the relevant settings, mapping and processing screens for those separate checks. Reloading this report reads stored configuration again. It does not test a connection, request a fresh channel response or send an inventory update. The report does not show a setup-check timestamp. Open a separate report window Select New window in the report header to open the same organization-scoped summary without the main application navigation. Keep the original tab open if you need its navigation or property selector. The separate window retains the property cards and their investigation links. Reports in the breadcrumb returns to the report catalogue. New window is not an export: this report has no dedicated CSV, Excel, PDF or scheduled-email control. Field and link reference Item Meaning and use Property name The property whose attached channels appear in that card. N of M not set up N listed channels have a Not set up indicator, out of M attached channels. These are channel counts, not failed-update or missing-room counts. N channels set up Every listed channel has a Set up indicator. A single channel uses 1 channel set up . Channel name Opens that property's settings for the named channel in a new tab. Long names may be shortened visually; hover over the name to see its full text. Set up Stored setup readiness is present and the channel definition has an applicable enabled inventory or reservation capability. This is not a live connectivity check or a guarantee that each property-level operation is on. Not set up The setup indicator is not satisfied. Missing settings, an incomplete stored setup result or channel-level capability configuration can cause this. Open the channel's settings for the specific explanation. Processing Status - Summary Opens property-wide inventory-update processing counts. It is not limited to one channel. Processing Status Opens the property's inventory-update history. Apply the appropriate filters with Search on that screen. New window Opens the same report in a separate tab or window with reduced navigation. Reports Returns to the report catalogue for the current property context. Not set up findings are emphasized in amber. Read the label, rather than using colour as evidence of delivery health. Some channel names include markers such as [-R] or [-C]. These describe channel-level reservation or credit-card capabilities; they are not failed-delivery indicators and do not describe an individual reservation's card data. They are separate from the adjacent setup label. Common problems A property is missing Check that your selected property belongs to the intended organization. Only active, authorized properties with attached channels appear. If you are not an organization administrator, confirm that the missing property is assigned to you. Ask your administrator or support to check the property's active state, assignment and channel list if it still does not appear. A channel is missing This report lists channels attached to each property. Confirm the property's channel list with an authorized administrator. Reload after the attachment has been checked; do not add a duplicate connection merely to make it appear here. No eligible properties are available for this summary There are no properties in the report's eligible scope. Check the selected organization and your access. If the report area is blank without this message, eligible properties may have no attached channels; a blank area is not an all-clear result. Contact support if expected active properties with channels remain absent. A channel is set up, but updates are failing or reservations are missing Setup and delivery are different checks. For inventory updates, open the property's Processing Status link and search the relevant channel and dates. For missing reservations, use the reservation investigation workflow instead. Do not change setup or repeat an outbound action without understanding the actual failure. The setup label does not match what you expected The summary reads stored setup information and has no last-checked timestamp. Review the correct property's Channel Settings, then reload the summary. If the discrepancy remains, send support the organization, property, channel, label shown, time and time zone of your check, and the relevant warning text. Do not send passwords, payment details or guest information. A settings link is refused or asks for your password again The settings screen has its own access and password-verification requirements. Complete the normal verification prompt, or ask your administrator to confirm your permissions. Viewing this summary is not permission to change settings. Contact support if the prompt repeats or authorized access is still refused. Related guides - Review channel settings and mappings - Understand your inventory processing summary - Review booking-engine setup across your organization
Understand qualified channel net revenue
Use Channel Net Revenue to compare captured booking value with recorded commission, and see which bookings have enough compatible information to calculate net value. This report covers one property and one reservation source at a time. It is not settled revenue, profit, full return on investment, or a complete statement of distribution costs. Missing commission is not zero cost. Before you start Sign in with access to the property you want to review. You do not need an Org Admin role solely to read this report. Decide which reservation source and first-arrival period you want. A preselected source is not evidence that it contains the bookings you need. Sources can have different amounts and commission coverage; do not add overlapping feeds together as if duplicate business had been removed across them. Run the report 1. Select your property in Channel Manager. 2. Open Reports → Channel Analytics → Channel Net Revenue. 3. In Filters, choose First arrival dates (through inclusive). Select both dates, or use Month to fill a complete calendar month. 4. Select Reservation source explicitly. 5. Leave Currency blank to keep currencies in separate groups, or enter the booking currency you want, such as USD. 6. Select Include canceled business separately if you also want canceled bookings. They remain separate from active business. 7. Click View report. 8. Check the property, source and resolved dates above the results before interpreting amounts. If you leave both dates blank, Rolling days is used instead. It defaults to 30 and starts on today in the property's time zone, moving forward—not backward. The range includes today. Explicit start and end dates take precedence. To change a completed report, reopen Filters, change the inputs and click Update report. Editing an input alone does not update the displayed results. This report reads captured data; it does not send inventory, change reservations or add commission charges. Channel Net Revenue filters showing the source, rolling period, currency and separate canceled-business option Example after loading a report: Booking.com, 366 forward-looking days and canceled business included. These are example selections, not the initial defaults. Check the result The result heading identifies the source, resolved period, requested property and Extracted time. That time is when the report queried the stored data, with the displayed time-zone offset. It is not the last time the channel sent a reservation or proof that all channel bookings have arrived. Open Meaning and coverage for the report's interpretation notes. - Read Known value as the subtotal of available booking values, not necessarily the value of every counted booking. - Read Recorded commission as recorded cost evidence. Its presence alone does not establish that a deduction is qualified. - Read Known net value / coverage together. Net covers only the qualifying subset; coverage tells you how many bookings qualified. - An em dash (—) means unavailable, not zero. A genuine recorded zero can be valid information. - No matching captured business means no captured bookings matched this selection. It does not establish zero property business. For another property or source, run a separate report and retain its selection context. Keep different currencies, active/canceled groups and amount bases separate when comparing results. Understand the date and booking basis The report selects each booking's latest captured version before applying the date and status filters. A newer cancellation or arrival change can therefore change an earlier report's results. This is not an historical “as of” snapshot. A booking is included when its first known room arrival date falls inside the selected period, including both endpoints. Once included, the report counts all its room stays, valid full-stay nights and full booking value—not only nights inside the period. For example, a booking first arriving before your selected period is not included merely because it stays into that period. A booking first arriving inside the period can include nights after the end date. For nightly on-the-books analysis, use the separate Daily Revenue / OTB guide. Bookings without a usable channel booking identity or any known room arrival cannot establish this report's cohort. Missing or reversed room dates contribute no nights and can appear in the invalid-room-stay count. Nights are not occupancy or available rooms. When a net deduction is qualified The current qualified deduction is for Mirai bookings. It requires all of the following: - A known, nonnegative booking value. - A known, nonnegative reservation-level commission amount. - A known booking currency. - A commission currency matching that booking currency. For qualifying bookings, net is booking value minus reservation-level commission once. Mirai's stored commission is calculated from the percentage supplied by Mirai; the report does not invent a standard commission percentage. An explicit zero commission can qualify. An unknown commission cannot. A recorded commission greater than booking value can produce negative net; the report does not replace that result with zero. For other sources, recorded amounts may still appear, but the report does not calculate a qualified net deduction. In particular, an Expedia supplier amount is not treated as a gross amount from which commission can automatically be deducted again. Check Currency / basis rather than assuming all source values mean the same thing. Reservation and room commission evidence When a reservation-level commission is available, the report uses it and does not add room commission amounts to it. Otherwise, a complete set of room commission amounts may be shown as a recorded sum. That room sum does not qualify for net deduction. The count of bookings with a recorded cost amount is therefore different from the count of qualified net bookings. Currency compatibility and the source's amount basis still matter. Read coverage correctly Coverage is the percentage of bookings in the group that qualify for net deduction. It is based on booking counts, not revenue weighting or the percentage of all channel bookings captured. The compatible booking value beneath the net amount is the booking-value subtotal for that same qualified subset. Do not subtract all displayed recorded commission from all displayed known value to reconstruct net: those totals may cover different bookings or currencies. Summary column reference The summary covers the full selection, independently of the current booking-detail page. Column Meaning Property / status Property name and Active or Canceled grouping, with property location beneath. Selected scope total is a total row, not another property. Currency / basis Booking currency and the source amount basis. Unknown currency means the report cannot identify a currency for safe aggregation. A Mirai basis label alone does not prove every booking in the row qualifies. Bookings / stays / nights Booking count, room-stay count and valid full-stay night count, in that order. These are not guest counts or occupied physical rooms. Known value Sum of available nonnegative booking values where booking currency is known. It can be a partial subtotal. Recorded commission Sum of available selected commission amounts where commission currency is known. The column also names that currency, the number of bookings with a recorded cost amount and invalid room stays in the cohort. Known net value / coverage Qualified net subtotal, qualified bookings out of all bookings in the group, the count-based percentage and the compatible booking-value subtotal. Currencies, commission currencies, statuses and amount bases remain separated. Do not add property rows and Selected scope total rows together: that double-counts the same business. There is no currency conversion or subtraction of canceled totals from active totals. Booking-detail reference When matching bookings are available, Booking detail shows up to 100 per page. Use the previous/next page controls beneath the report when available. The full summary is not restricted to those visible detail rows. Column Meaning Reservation row / arrival ChannelRUSH's internal reservation-version row ID and the booking's first known room arrival. This ID is not the channel confirmation number; the cell is not a reservation-opening link. Status / units Active or Canceled, room stays and full-stay nights. Booking value Available stored booking value and its currency. A visible number with no currency is not a safely qualified monetary total. Recorded commission Available reservation amount or complete room sum, with the recorded commission currency. Known net Booking value less commission when qualified; otherwise — . Coverage The qualification result, followed by how commission evidence was selected. Coverage messages Message Interpretation and next check Feed deduction basis unqualified This source is not qualified for net deduction. A visible amount is not permission to deduct it again. Missing booking value A usable booking value is unavailable. Review the captured reservation information before comparing monetary results. Missing commission No usable reservation commission or complete room commission sum is available. Do not treat it as zero commission. Commission currency or authority unqualified An amount exists, but its currency or reservation-level authority does not satisfy deduction rules. Check for missing/mismatched currency or room-sum-only evidence. Stored supplied-percentage commission deducted once The captured booking meets the current deduction rules. This does not establish payment, settlement or all other distribution costs. These messages give the first applicable explanation, not a complete list of every data issue. The cost-source text distinguishes Reservation amount (room rollup not added), Complete room sum; currency/basis unqualified, and Unknown / incomplete. Download or open separately 1. Run the report and check its selection context. 2. In the Download group, select CSV. 3. Open channel-net-revenue.csv and check its source, property, dates, status option and extraction time. CSV contains the complete aggregate summary, including totals. It is not an individual-booking export, even when Booking detail is displayed. Paging changes the visible detail, not the aggregate export's scope. The download queries stored data again. Newly captured versions can change results between viewing and downloading. Keep the CSV's context and extraction time with your analysis. Select New window to open the current report separately. Check the selected property and filters again after further navigation; do not assume the separate-window layout is retained by every update or page link. Filter reference Control Values and behavior Month Fills the start and end with a whole calendar month. Click the report submit button afterward. First arrival dates (through inclusive) Supply both dates or leave both blank. Start must not follow end; the inclusive range is at most 366 days, within years 2000–2100. Reservation source One source at a time. The normal choices come from the property's connected channels; a source retained in an existing report link can also remain available after disconnection. Choose deliberately. Rolling days Whole number from 1 to 366; default 30. When both dates are blank, starts today in the property's time zone and extends forward. Keep a valid number even when explicit dates are supplied. Currency Blank means separate currency groups. Otherwise matches the booking currency after trimming spaces and ignoring letter case. Maximum 10 characters; an unrecognized code can return no rows rather than a validation error. This is not a currency-conversion control. Include canceled business separately Initially unchecked. Checked adds canceled bookings as separate groups alongside active business; it is not canceled-only selection. View report / Update report Runs the selected read-only report. Updating starts booking detail at its first page. It does not save a scheduled report. CSV field reference The file uses a shared schema. Some fields are not calculated for Channel Net Revenue. Zero in an unused field is not evidence of healthy pricing, mapping or booking capture. Unavailable money is blank in CSV rather than the screen's em dash. Selection and extraction fields Header Meaning in this report Contract Report definition identifier, supplied-commission-booking-value-v1 . ScopePropertyIds Selected property ID. FeedId Selected reservation source ID. StartDate Resolved inclusive first-arrival start, yyyy-MM-dd . EndDate Resolved inclusive first-arrival end, yyyy-MM-dd . IncludeCanceled Whether canceled business was included separately. CurrencyFilter Entered booking-currency filter; blank means no currency narrowing. CountryFilter Unused here; blank for ordinary requests. CityFilter Unused here; blank for ordinary requests. OpportunityDays Shared setting, normally 30; it does not define this report's booking period or query opportunities. OpportunityLanguage Report culture metadata; there are no opportunity rows in this report. ExtractedUTC Query extraction timestamp in ISO format. Respect the included offset; this is not channel-data freshness. Group, count and amount fields Header Meaning in this report RowKind Property , Total , or an empty-result marker, No matching rows . PropertyId Property ID on property rows; 0 on totals. The total is not a property with ID 0. PropertyName Property name or Selected scope total . Country Property country; blank on totals. City Property city; blank on totals. Currency Booking currency, or blank when unknown. CommissionCurrency Recorded reservation commission currency, or blank when unknown. Status Active or Canceled . Basis Source amount description; not a guarantee every booking qualified. Bookings Included booking count. RoomStays All room stays belonging to included bookings. RoomNights Valid positive full-stay nights, not clipped to the selected period. PricedNights Unused zero placeholder; not measured here. QualifiedNights Unused zero placeholder; not measured here. UnmappedNights Unused zero placeholder; not a mapping-health check. KnownValue Available booking-value subtotal where currency is known. ADR Unused; blank. RecordedCommission Available chosen commission subtotal where commission currency is known. BookingsWithCostAmount Bookings with a selected recorded cost amount, even if deduction is unqualified. QualifiedNetBookings Bookings that satisfy the net-deduction rules. QualifiedBookingValue Booking-value subtotal for the qualified subset. QualifiedNetValue Net subtotal for that subset. QualifiedNetCoveragePct Qualified booking count divided by all bookings in the group, expressed as a percentage. InvalidRoomStays Room stays with missing or invalid dates within included bookings. MissingIdentityRowsFeedWide Unused zero placeholder. Zero does not establish that every captured booking has a valid identity. Unused opportunity fields OpportunitySource, OpportunityType, OpportunityLevel, OpportunityCount and LatestOpportunityCreated are blank. Channel Net Revenue does not populate opportunity rows. For an empty report, the No matching rows record retains selection/extraction metadata; the group and amount fields are blank. Do not convert those blanks into measured zeros. Choose either property rows or total rows for summation, and retain the currency, commission currency, status and basis partitions. Common problems - No matching captured business: first check property and source. Check whether you intended first-arrival dates rather than stay overlap, and remember that blank dates look forward. Review the canceled option and currency filter, then click Update report. If an expected booking is still absent, give support the property, source, period and a suitable reservation reference—without guest or payment details. - Known value exists but Known net is unavailable: check the detail's Coverage message. The source may be unqualified, commission may be missing, or currency/authority may not match. Do not enter an assumed commission or interpret the missing net as zero. Escalate conflicting captured evidence to support. - Totals differ from another report: compare first-arrival versus stay-date selection, latest captured versions, status, source and currency. This report includes full booking amounts and full-stay nights. If those bases match and the difference remains unexplained, include both reports' selection context and extraction times in your support request. - “Provide both dates or leave both blank.”: complete or clear both endpoints, then rerun. - “Select an ordered date range of at most 366 days.”: correct date order, shorten the inclusive range and use supported years, then rerun. - “Check report filters, page and output.”: reopen the report from its normal menu and enter the selection again. A malformed or hand-edited URL can request an invalid page or output. If the ordinary form still fails, send support the error text and non-sensitive report context. - A narrow-screen table is wider than the page: scroll within the table to reach all columns. Do not infer missing values from columns that are offscreen. For support, include the property, source, resolved dates, currency filter, canceled-business option, extraction time with its offset, and relevant Coverage text. Never send passwords, payment-card details or unnecessary guest information. Related - Read daily on-the-books revenue - Compare property performance with Portfolio Overview
Compare channel production and booking-source mix
Use Channel Production & Booking Source Mix to compare captured bookings and room nights by source within one reservation feed, then export the matching totals. A reservation feed is how ChannelRUSH received a booking. A recorded source is the source attached to that booking, which may itself be an intermediary. This report does not establish the ultimate original sales channel, combine feeds or remove duplicates across feeds. Before you start Sign in with access to the property you want to review. You do not need an Org Admin role for this report. Select the property before opening it, and check which reservation feed contains the business you want to analyze. This is a current captured stay-date report. It is not a report of bookings made during the selected dates, cancellations received during those dates, or a historical snapshot of what you knew on an earlier day. It does not establish total hotel occupancy or complete property revenue. Run the report 1. Select the property in Channel Manager. 2. Open Reports → Channel Analytics → Channel Production & Booking Source Mix. 3. In Filters, choose Stay dates (through inclusive). Select both dates, or use Month to fill a whole month. The maximum range is 366 days. 4. Select Reservation feed explicitly. The initial selection is not proof that this feed contains the reservations you need. 5. If needed, expand Narrow by product or currency and enter an exact Channel room ID, Channel rate-plan ID, or Currency. Leave a field blank to apply no restriction for that field. 6. Click View report. 7. Check the property, transport feed and stay-date range above the result. After a report loads, expand Filters, change the required fields and click Update report. Changing an input alone does not update the result. Each submission reads the captured data again; it does not send inventory or change reservations. Expanded report filters with stay dates, reservation feed, exact product filters and Update report The filter form in a narrow window. Wider windows arrange controls side by side. The example uses Booking.com; select the feed appropriate to your property. Choose the view The menu opens Booking Source Mix. The two tabs use the same property, feed, dates and product/currency filters. Clicking a tab runs that view. - Channel Production separates individual source identities, such as ChannelRUSH Booking Engine, Booking.com and Expedia. An unrecognized recorded identity is labeled Unclassified recorded source with its ID; a missing source can appear as Unknown original source. - Booking Source Mix combines those identities into the reporting classes below. These are classification rules, not a guarantee about the original sale behind an intermediary. Class What it includes Direct ChannelRUSH Booking Engine source. OTA Booking.com and Expedia sources. Other (CRS interface) ChannelRUSH CRS source; the interface alone does not establish a direct booking. Unknown Other or missing source identities. A known source name or ID is not enough to classify it as Direct, OTA or GDS. When a booking has a recorded source, the report uses it. Without one, it can recognize the Booking Engine, Booking.com or Expedia feed as the origin. Other feeds remain unknown rather than being assigned an assumed source. Attribution tells you whether a row uses a recorded source, a recognized feed origin, an unknown original source, or mixed attribution evidence. Expand Source attribution, definitions and coverage to review these qualifications alongside the result. Check and interpret the result Check the property, transport feed and dates first. The heading gives distinct captured bookings and currently canceled bookings for the full matching selection. The aggregate table separates source, currency and status. - The report uses each booking's latest captured version in the selected feed. Changes or cancellations can therefore change the result of a later run for the same dates. - Stay dates include the selected final date; checkout is excluded. Only nights inside the range contribute. A stay can begin before the selected start or end after the selected end. - Active and canceled bookings are always included, but shown separately. There is no status selector on this report. - Canceled stays use their current captured dates. The report does not recover an earlier stay itinerary to reconstruct cancellation history. - Currency totals are separate. There is no currency conversion, and feeds are never pooled. No captured stays match these filters means no matching captured stays were found for this selection. It does not prove there were no bookings at the property, no channel sales, or successful reservation delivery. Empty Channel Production result showing the selected feed, date range, coverage section and room-stay detail An empty demo result in the standalone window. The coverage and detail sections remain available; this is not an example of populated production totals. Money and price coverage A priced night has exactly one captured nightly price record with a nonblank amount. A zero price is a valid recorded amount. A missing price, duplicate price records or a blank amount is not converted to zero. A qualified night must also come from the ChannelRUSH Booking Engine feed and have a recorded currency. Only qualified nights contribute to Known value and ADR. Other feeds can have priced nights while monetary totals remain unavailable. Known value represents booked room-rate amounts, including tax already embedded in those rates but excluding separately stored fees and taxes. It is not realized revenue, profit, commission-adjusted net revenue or all money collected from a guest. A dash means unavailable, not zero. Qualified zero-priced nights can produce a known value and ADR of zero. Value share is unavailable when the qualifying denominator is not positive. Missing room mappings do not, by themselves, remove valid captured nights or disqualify an otherwise qualified price. Shares and cancellation Booking share, night share and value share compare rows within the same currency and status. Do not read them as shares of all hotel sales or add percentages across currencies or active/canceled groups. Current cohort cancellation is canceled bookings divided by active plus canceled bookings in the same source bucket and currency, using the currently matching stays. The same percentage can appear on both that bucket's Active and Canceled rows. It is not the percentage of cancellations received during the selected dates. Coverage exceptions and extraction time The coverage section reports invalid stays and records without booking identity. Invalid or missing stay dates cannot establish production in a particular stay period. Records without booking identity are a property/feed data-quality count, not necessarily records from your selected dates. These exception counts are not extra nights to add to the report. Extracted is when the report read the captured records, not when the channel last updated them. A recent extraction does not establish fresh or complete channel data. Inspect supporting room stays 1. Expand Selected feed room-stay detail. 2. Check the matching-stay count and current page. 3. Use the available previous/next page controls when there are more results. Detail shows at most 100 room stays per page, ordered by arrival and then reservation/room-stay identity. The aggregate totals above it cover the full matching selection, not only the visible detail page. The Reservation value here is an internal captured-record reference, not necessarily the channel's booking number. This report does not provide a clickable reservation drilldown. Use Reservations → Search when you need to investigate a booking, choosing that screen's own search criteria and submitting its search. Inventory and restriction context opens the Channels report for the current property. It does not carry this report's dates, reservation feed or product filters; set the required scope again on that screen. It is contextual navigation, not evidence that inventory caused the booking pattern. Download or open separately - Click CSV in the Download area to export the current view's aggregate rows. The file includes the full aggregate selection, not the paged room-stay detail. It is not an Excel workbook or a guest/reservation-detail export. - An empty result exports a metadata row with RowState = No captured rows. Do not count it as a booking or replace its blank measures with assumed zeros. - Downloading runs the query again. The CSV can differ from an earlier screen if captured records have changed; compare ExtractedUTC and the scope fields. - Click New window to open the report separately while keeping the original page. It removes the ordinary navigation chrome. Subsequent tab, filter or detail-page navigation can return to normal chrome; use New window again if needed. There is no report-specific Copy to Clipboard or Excel control on this page. Filter reference Field Meaning and accepted input Property selector One property you can access. Check the property printed in the result; the report is not an organization-wide total. Month Shortcut that fills a whole calendar month into the stay-date range. Submit the report afterward. Stay dates (through inclusive) Both dates are required by the form. Start must not be after end; maximum 366 inclusive days. Initially covers the property's current date and the following 29 days. Checkout is excluded from occupied nights. Reservation feed One transport feed at a time. Initially favors the connected Booking Engine feed; otherwise a connected channel is selected. Check it rather than relying on the default. Channel room ID Exact channel room identifier, not a room name or standard-property room ID. Optional; maximum 200 characters. Blank removes this restriction. Channel rate-plan ID Exact channel rate-plan identifier. Applied to the captured nightly rate-plan identity, falling back to the room-stay identity when needed. A matching stay can contribute only its matching nights. Optional; maximum 200 characters. Blank removes this restriction. Currency Exact captured currency code, for example USD or EUR . Leading/trailing spaces are removed and letters normalized to uppercase. Maximum 10 characters; this is a filter, not a currency-conversion setting. A code with no matching captured data returns no rows. On-screen column reference Aggregate table Column Meaning Source Individual source identity in Channel Production; reporting class in Booking Source Mix. Class Direct, OTA, Other (CRS interface), or Unknown under the classification rules above. Attribution Recorded source, recognized feed origin, original source unknown, or mixed evidence. Recorded source may be an intermediary. Currency Recorded currency, or Unknown when absent. Separate currencies must not be totaled together. Status Active or Canceled, based on the latest captured booking version. Bookings Distinct captured bookings represented by this row. Booking share Percentage of bookings in the same currency/status group. Room stays Distinct room stays represented by this row. The meter compares the count with the largest row, not property capacity. Nights Matching stay nights clipped to the selected date range and product filters. Night share Percentage of nights in the same currency/status group. Priced / nights Nights with exactly one recorded nonblank price, followed by all matching nights. This is price coverage, not qualified monetary coverage. Qualified nights Priced nights eligible for monetary totals under the Booking Engine feed/currency rules. Known value Sum of qualified booked room-rate amounts. Dash means unavailable. Value share Percentage of known qualified value in the same currency/status group; unavailable without a positive denominator. ADR Known value divided by qualified nights, not by all nights. Current cohort cancellation Canceled bookings divided by active plus canceled bookings in the same source bucket and currency. Selected feed room-stay detail Column Meaning Reservation Internal reference for the current captured booking record. Room-stay ID Internal reference for this room stay. Channel room ID Room identifier recorded in the selected feed. Arrival / Checkout Full captured stay boundaries, not clipped to the report dates. Checkout does not count as an occupied night. Full LOS Full length of stay in nights, even when the selected range includes only part of it. Clipped nights Matching nights that remain inside the selected range and product filters. Price rows Despite the label, the count is priced nights within that clipped selection—not the total number of raw price records. Status Active or Canceled for the current booking version. Recorded source ID Source identity used by the report. It can be a recognized-feed fallback, not only an explicitly recorded source. Check aggregate Attribution before interpreting it. CSV field reference These are the exact export headers, in file order. They differ from the on-screen labels. Dates use yyyy-MM-dd; numbers use a decimal point. A blank amount means unavailable. Fields retained from the shared export format do not imply additional controls on this report. Header Meaning Contract Report definition identifier: captured-source-production-v1 . Period Selected for this report. PropertyId Selected property identity. FeedId Selected transport feed identity. Start First selected stay date. End Last selected stay date, inclusive. View production or source-mix . Grouping Shared-format metadata, normally month ; it does not make this report a monthly grouped report. ExtractedUTC Query extraction timestamp in UTC; not the last channel update. Currency Recorded currency; blank when unknown or when the row has no captured measures. Status Active or Canceled; blank for an empty-result metadata row. Bucket Individual source label or source-class bucket. Bookings Distinct bookings in the bucket/currency/status row. RoomStays Distinct room stays in that row. RoomNights Matching clipped nights. PricedNights Nights with exactly one recorded nonblank nightly price. QualifiedNights Nights qualifying for monetary totals. UnmappedNights Matching nights without a recognized current room mapping. These nights can still be counted; this is not a delivery-failure count. KnownBookedRateValue Sum of qualified booked room-rate values; blank when unavailable. QualifiedADR KnownBookedRateValue divided by QualifiedNights; blank when unavailable. KnownValueSharePercent Same-currency/status known-value share; blank when unavailable. RevenueBasis Explanation of the qualified monetary basis. Coverage Qualification that captured feed coverage and property-wide completeness are not established. RoomFilter Applied exact channel room filter; blank means unrestricted. RatePlanFilter Applied exact channel rate-plan filter; blank means unrestricted. CurrencyFilter Applied normalized currency filter; blank means unrestricted. IncludeCanceled True ; this report always includes canceled and active business separately. ComparisonAlignment Shared-format metadata, normally none ; this page has no prior-year comparison selector. UnattributedInvalidStays Invalid-stay exceptions that cannot be assigned to the selected stay period; not extra matching bookings. UnresolvedSourceIdentityRecords Records without a usable booking identity in the property/feed; not a count of unknown sales channels or a stay-date total. RowState Captured for an aggregate row; No captured rows for an empty-result metadata row. BookingSharePercent Booking share within the same currency/status group. RoomNightSharePercent Night share within the same currency/status group. RecordedSourceId Source identity when the bucket has one. Can be zero for unknown or blank when a source class combines identities. SourceClass Reporting class: Direct, OTA, Other (CRS interface), or Unknown. SourceAttribution Explanation of the source evidence used. CohortCancellationPercent Current matching cohort cancellation percentage for the same bucket and currency. Repeated scope and exception metadata belong to the report, not separately to every row. Do not sum those metadata fields across rows. Spreadsheet-sensitive text can carry a protective leading apostrophe in the CSV. Common problems No captured stays match these filters → The selected feed, dates or exact product/currency filters may not match retained data. Reopen Filters, verify the feed, clear optional narrowing and click Update report. If expected bookings remain missing, give support the property, feed, stay dates, filters and extraction time. Do not resend bookings or inventory to populate this report. Prices exist, but Known value or ADR is a dash → Priced nights are not necessarily qualified nights. Check the feed, currency and Qualified nights. Non-Booking Engine feeds do not supply qualified monetary totals here. If Booking Engine values still appear incomplete, ask support to examine the captured price coverage; do not treat missing amounts as zero. A source is Unknown or appears under an unexpected class → A recorded identity may be missing, unclassified or an intermediary. Compare Channel Production with Booking Source Mix and inspect Attribution. Ask support with the source label/ID and selected feed if the evidence remains unclear; do not relabel it as direct business based only on a name. “Select an ordered stay-date range of at most 366 days.” → Correct the date order or reduce the range, then submit again. For an incomplete range, supply both dates. The error is not a completed report. “Invalid product or currency filter.” → Shorten the room/rate-plan identifier to at most 200 characters or the currency filter to at most 10, verify the exact identifier and submit again. Clear the filter if you do not know it. Populated totals but empty room-stay detail, or “Invalid detail page.” → A copied or old URL may point beyond available detail. Reopen the report from Reports, reapply the filters and run it from the first page. If the mismatch persists, provide support the report URL, scope and extraction time. CSV and the screen differ → Check view, feed, dates and narrowing first. CSV contains aggregates rather than paged detail and is read again at download time. Run the report again and compare timestamps. If identical scope still produces an unexplained discrepancy, send support the relevant aggregate rows and timestamps, without passwords, payment details or unnecessary guest data. Related - Read daily on-the-books revenue - Understand qualified channel net revenue
Review departing reservations
Use Reservations - Departures to list the selected property's recorded departures for one date, inspect reservation details, and copy or export the list. Open the report 1. Select the property in the property selector. 2. Open Reports → Reservations → Departures. 3. Check Departure Date and choose the date you need. Check this explicitly rather than assuming the initial date matches the property's local day. 4. Select View Departures. 5. Check that the date remains selected and read the Departures count before using or exporting the results. You need access to the selected property. Viewing this report does not require an Org Admin role. Changing the date and selecting View Departures reads reservation records; it does not check guests out, change reservations, or send them to a PMS. The date field uses the displayed date format. Use the calendar picker if you are unsure of that format. Changing the field alone does not reload the report: select View Departures before choosing an export or changing view. Understand what is included The report uses the latest stored version of each channel reservation at this property. Canceled reservations are excluded. A reservation is included when at least one of its rooms has the selected departure date. The count is reservations, not rooms or guests. The count beside each channel is also a reservation count. The list is ordered by the booking contact's surname. A multi-room reservation appears as one entry, with information about all its rooms. For example, if one room departs on Monday and another on Tuesday, the reservation can appear in both dates' reports. Its displayed Departure is Tuesday—the latest departure in the whole reservation—even in Monday's report. Do not add consecutive daily counts together as a count of distinct bookings. These are recorded reservation dates, not confirmation that guests actually checked out. An empty report means no matching non-canceled reservations were found in ChannelRUSH. It does not establish that there are no departures in the PMS or another system. Read the HTML view Use HTML under View for the ordinary report table. The current view is highlighted. Column Meaning ID / Channel The channel reservation ID and originating channel. Select the ID to open that reservation's details in a new tab. Guest Info The booking contact's name, not a list of all occupants. It can be blank when the booking contact is unavailable. Total The whole reservation's recorded after-tax total, or its before-tax total when an after-tax total is unavailable, shown with the reservation currency. It is not an outstanding balance or revenue attributable to the departure day. A missing amount is not zero. Room Info All room entries in the reservation, grouped by room-type name. Repeated names include a quantity. These are room-type names, not assigned physical room numbers, and may include rooms departing on another date. Arrival The earliest recorded arrival among the reservation's rooms. Departure The latest recorded departure among the reservation's rooms. This can differ from the date you selected for a multi-room reservation. If a room-type name was not supplied with the reservation, the report tries the property's channel mapping. A blank name is not evidence that the reservation has no rooms. Open the reservation details to investigate missing or unexpected information. Copy the report 1. Load the required date in HTML view. 2. Select Copy to Clipboard. 3. Paste into your intended internal document and check the date, count and copied content. The copied text contains a report heading, date, count and a block for each reservation. It is not a spreadsheet-shaped table. An empty report copies No departures for this date. Copied totals do not include currency. Check the HTML totals and retain the correct currency alongside any amounts you share. Do not combine amounts from different currencies. The Copied! message is a prompt to check your pasted result, not a substitute for checking it. Copied reports and downloaded files can contain guest names and reservation identifiers. Share them only with people who need them for their work. Use Excel view or download a file Excel view 1. Load the required departure date. 2. Select Excel under View. 3. Check the retained date and Departures count. 4. Review the spreadsheet. Select HTML to return to the ordinary table. Excel opens a read-only spreadsheet in the page; it does not immediately download a workbook. The spreadsheet's File → Save As menu offers file-saving options. The separate CSV link under Download downloads comma-separated values directly from either view. With no matching reservations, the spreadsheet can be blank, without report-field headings. Use the displayed date and count to distinguish an empty report from an unexpected result. CSV download 1. Load the date you need with View Departures. 2. Select CSV under Download. 3. Open the downloaded file and confirm it corresponds to the property and date you loaded. The filename identifies the property and Reservations, but does not include the departure date. Retain the date separately or rename your local copy. An empty report produces an empty CSV file, without a header row. Spreadsheet and CSV field reference For populated results, the fields appear in this order. They describe the same whole-reservation entries as HTML, but their formatting differs. Field Meaning and important differences Channel Originating channel name. ReservationID Excel displays the channel reservation ID as a details link. CSV retains a combined value: channel reservation ID, property ID and internal reservation-record ID, separated by @ . Do not treat the complete CSV value as the channel confirmation number. GuestInfo Booking contact's formatted name, or blank when unavailable. Total After-tax total with before-tax fallback, formatted to two decimal places. Blank means no recorded amount. There is no currency field. Check the HTML view before comparing or combining monetary values. RoomInfo Room-type names with quantities for repeated names. A cell can contain several lines. ArrivalDate Earliest room arrival, in the application's short-date format. DepartureDate Latest room departure, in the application's short-date format. Do not assume exported dates are ISO-formatted or that decimal separators match your spreadsheet's import settings. Import identifiers as text if your spreadsheet would otherwise alter them. CSV quotes values containing commas, quotes or line breaks; it can also prefix formula-like text with an apostrophe for spreadsheet safety. Open a separate report window Select New window to open the currently loaded report without the main application navigation. Check the departure date in that window before using it. The standalone view does not offer another New window control. Switching between HTML and Excel can restore the normal navigation. The report is a snapshot when loaded. Reload it or select View Departures again to read the currently stored reservations. This does not request a fresh reservation from the channel. Check the result and resolve differences - Zero departures or an empty file: check the selected property and date, then select View Departures again. A cancellation or a newer reservation version with changed stay dates can remove an earlier match. If you expected a particular reservation, use Reservations → Search to find it and compare its latest details. - The displayed departure differs from the filter date: inspect each room's dates. The filter matches any departing room, while the displayed departure is the reservation's latest room departure. - The count differs from a room or guest list: this report counts reservations once per selected date and includes all their room information. Reconcile room-level departures in the reservation details or PMS. - Guest, room or amount information is missing or implausible: open the reservation details and compare the recorded information with the source booking. A blank amount is not a zero charge, and the report is not proof of settlement. Escalate unresolved source-data differences rather than changing a reservation to make a report match. - Copied text is missing: paste into an approved internal document to check the result. If copying fails, use CSV or the HTML view. Copying and downloading do not resend a reservation. - A spreadsheet reservation link does not open the intended record: return to HTML and use the reservation ID there, or use Reservations → Search. Do not infer that the reservation is missing from a failed spreadsheet link. For support, provide the property, selected departure date, channel, relevant reservation ID and what differs. Do not send passwords, payment details or unnecessary guest information. Related - Find and review reservations - Understand reservation details - Review the Dashboard
Read daily occupancy, arrivals, departures and stayovers
Use Occupancy Report to review daily reservation activity for one property, compare arrivals with stayovers and departures, and export the counts. These are reservation counts, not occupied rooms, guests or an occupancy percentage. Use your PMS or another verified room-based source when you need physical room occupancy. Before you start You need access to the selected property. An Org Admin role is not required. The report uses reservations already received by ChannelRUSH; it does not retrieve missing bookings from a channel or confirm actual check-in or checkout. The report has one property and one date range. It does not offer channel, room-type or reservation-status filters. Only the latest stored version of each channel reservation is considered, and only New or Modified reservations qualify. A later canceled version removes the earlier active version from these counts. Run the report 1. Select the property in the application header. 2. Open Reports → Reservations → Occupancy. 3. In Filters, choose Month / Year for a whole month, or enter both dates in Date Range. Use the displayed date format or the calendar picker. 4. Check the start and end dates before continuing. 5. Select View Report. 6. Check the property name and the date range printed above the chart, then read the daily table. Changing a date alone does not run the report. After a report loads, Filters collapses; expand it to choose different dates and select View Report again. Cancel returns to Reports without running the new criteria. Check the actual date range Both dates in the resulting report are included. Short selections are extended through the seventh day after the start date. For example, selecting October 1–2 produces October 1–8 in the report and export. The filter can still display October 1–2, so use the date range above the chart and the table's final date to establish what was reported. Enter the dates in chronological order. Do not rely on a reversed range being rejected. Understand the counts The report reads each reservation's recorded room-stay dates. Each of Arrivals, Departures and Stayovers counts a qualifying reservation once within that category for a given day, even if several rooms in that reservation meet the same condition. On-screen column Meaning Date The calendar date being counted, not the date the booking was created or received. Occupancy Arrivals plus Stayovers for that day. It is not a separate physical-room measurement. Arrivals Reservations with a room stay arriving on that date. Departure Reservations with a room stay departing on that date. The chart and exports call this Departures . Stayovers Reservations with a room stay arriving before that date and departing after it. Arrival and departure days are excluded from this category. A reservation can qualify for different categories on the same date. For example, if one room arrives while another room in the same booking is already staying over, that booking contributes to both Arrivals and Stayovers, and therefore contributes twice to their Occupancy sum. Do not interpret Occupancy as a deduplicated count of bookings across those two categories. Departures are shown separately; they are not subtracted from Occupancy. A same-day arrival and departure can contribute to both Arrivals and Departures, and to Occupancy through Arrivals. The report does not deduplicate bookings received under different channel identities. It also does not reconstruct what ChannelRUSH knew on an earlier reporting day: later modifications or cancellations can change counts for past stay dates. Read the chart The chart uses bars for Occupancy and lines for Arrivals, Departures and Stayovers. The colored strips beneath it identify the series; their full widths do not mean 100% occupancy. Chart date labels show day numbers. For a range crossing a month boundary, use the table's full dates to avoid confusing the same day number in different months. Use the daily table or spreadsheet when lines overlap or all counts are zero. Check the result Before using the figures for operational planning: - Confirm the property and the actual reported dates above the chart. - Check the rows for the dates you need, including any dates added by the short-range extension. - Treat 0 as no matching received reservations in that category. It does not prove that the property is empty or that all bookings have been received. - Do not use a report reload as proof of a fresh channel feed. The report does not show its run time or the latest feed-update time. To investigate an unexpected count, open Reservations → Search for the same property. Enter suitable reservation/date criteria and select Search. Review the latest booking status and each room's stay dates, using the reservation search guide. A search total with different criteria is not a direct reconciliation of this report. Running or exporting this report reads stored information. It does not change reservations, check guests in or out, update inventory, or resend bookings to a PMS. Change the view or export HTML and Excel views Select HTML or Excel beside View in the result header. The active format is marked. Both use the same date range and count definitions. HTML shows the chart and a daily table. Excel shows the chart and an embedded spreadsheet with the daily counts. The spreadsheet is read-only; it is not an editor for reservations or availability. For a workbook, use the spreadsheet's File → Save As controls and choose the required file format and name. Open the downloaded file and check its dates and counts before sharing it. Saving a report file is not a reservation or inventory update. Print belongs to the spreadsheet controls; use the print preview to check its scope rather than assuming it contains the whole report page. Download CSV 1. Run the report and check its property and actual date range. 2. Select CSV beside Download. 3. Open the downloaded file. 4. Check the first and last dates and the five column headers below. The filename includes the property name and Occupancy Report. The CSV contains daily rows, not the chart or the explanatory notes. Keep the property and count limitations with the file when sharing it. Dates use display formatting rather than a guaranteed ISO date format; verify how your spreadsheet imports them. Export field reference The embedded spreadsheet and CSV use these headers, in this order: Header Value Date Display-formatted calendar date. Occupancy Arrivals plus Stayovers. Arrivals Distinct qualifying reservations arriving that day. Departures Distinct qualifying reservations departing that day. Stayovers Distinct qualifying reservations spanning the day, excluding arrival and departure days. There are no guest, room-capacity, percentage, revenue or feed-freshness columns. A valid loaded range can contain daily rows of zeros; that is different from a report that has not been run. Open a separate report tab Select New window in the result header to keep the current page open and display the report without the main navigation. The property, dates and current format are carried over. Changing between HTML and Excel from that separate view can restore the ordinary application layout. Common problems Symptom Likely cause Safe next action Only Filters appears; no chart or table No complete date range has been submitted. Enter both dates and select View Report . If the page still has no result, record the displayed error and contact support. The result includes more dates than you selected The report extended a short range. Read the range above the chart and the last table/export date. Use only the dates needed for your analysis. All daily counts are zero No qualifying received reservations matched those dates, or expected bookings are not represented in ChannelRUSH. Verify property and stay dates, then use Reservations → Search and select Search . If expected bookings remain missing, contact support rather than creating or resending them to populate the report. Counts differ from PMS room occupancy This report counts reservations by category, not rooms; multi-room and cross-channel records can differ from a physical-room measure. Compare booking statuses and room-stay dates. Use a verified room-based report for occupied-room decisions. Escalate unexplained differences with the affected dates and report names. Past dates changed since the last export A later stored modification or cancellation changed the current reservation version. Review the affected reservation's latest details before treating the difference as a reporting error. Excel is blank or a file is unusable The spreadsheet did not load, or the downloaded file has not imported as expected. Check the HTML table and download CSV as an alternative. Confirm date interpretation. If the issue persists, give support the browser, property, date range, format and error text. The property or report cannot be opened Your current property access or session may not permit it. Check the selected property and sign-in state. Ask your administrator or support if expected access is missing; do not switch to an unrelated property to work around it. Viewing the report again is safe; it does not resend reservations. For support, provide the property, selected and displayed date ranges, action time and time zone, output format and exact error. Do not include passwords, payment details or unnecessary guest information. Related - Find and investigate reservations - Review departing reservations
Investigate discounted reservations
Use Discounted Reservations to find recently received bookings whose recorded nightly prices fall below a stored channel net rate, then investigate the booking before deciding whether anything needs correction. Before you start Select a property you can access. This report covers that property, not your whole organization. It reads stored reservations and inventory; running it does not change prices, amend bookings or resend anything to a channel. Use this as an investigation shortlist, not a complete discount audit. The report examines at most the newest 50 matching reservation records in the selected receipt window. Canceled bookings and bookings that cannot be compared can occupy places in those 50 before being excluded. There is no next page or truncation warning. Increasing Past Days does not remove that limit. A reported percentage is a comparison with stored net-rate data—not proof of a promotion, a pricing error, commission-adjusted profitability or the rate currently offered by the channel. Run the report 1. Select the intended property in the property selector. 2. Open Reports → Reservations → Discounted Reservations. 3. Set Min Discount % to the minimum difference you want to investigate. 4. Set Past Days to the receipt lookback you want to examine. 5. Select View Report. 6. Check that the two fields retain your choices and review the result below them. Discounted Reservations filters showing a 10 percent threshold, seven past days and an empty result The example shows an empty result. It does not establish that every booking was compared or that all rates are correct. The initial defaults are 10 for Min Discount % and 1 for Past Days. Changing an input alone does not reload the report. To keep a separate report tab, apply the filters first and then select New window. It opens the currently loaded criteria without the main navigation. Unsaved input changes are not carried into that tab. You can change the filters and select View Report there too. This page does not offer a CSV, Excel or clipboard export. Understand the comparison For each usable booked room-night, the report compares the nightly price recorded in the reservation with the stored net rate for its mapped channel room, rate plan and stay date: Comparison % = (1 − booked nightly price ÷ stored net rate) × 100 A booking qualifies when at least one comparable night reaches Min Discount %. Its displayed percentage is the largest qualifying nightly difference, rounded to a whole percent. It is not the average for the stay or a discount on the reservation total. Qualification uses the unrounded value, so a value just below your threshold is excluded even if it would round to that threshold. A rate-plan ID recorded on an individual night takes precedence over the room's rate-plan ID. Current mappings determine the comparison. For certain Expedia mappings, the report can use an enabled related rate-plan code with one additional character when the direct plan is missing or disabled. Ask support to confirm the comparison plan when a result is unexpected; do not assume the booking and comparison always use identical plan codes. The comparison does not convert currencies or reconcile tax and occupancy bases. The stored net rate is not a historical snapshot of what was offered when the booking was made, and the report does not retrieve a fresh rate from the channel. Check those differences before treating a percentage as a commercial discount. Read the results and check the booking Each result is a linked line containing: - Channel: the reservation's source channel. - ID: the channel reservation number. - Status: the stored booking status, not PMS delivery status or payment status. - Percentage: the largest qualifying nightly comparison for that booking. The report does not show the specific qualifying night, booked price, comparison rate, room or rate plan alongside the result. Results are grouped by channel rather than ranked by largest percentage. 1. Select the reservation's linked result. The stored reservation version opens in a new tab. 2. Check its property, source channel, reservation number and status. 3. Review every relevant room's Daily Rates, stay dates and rate-plan information. Keep nightly amounts separate from room totals and the whole-reservation total. 4. Check currency, tax treatment and occupancy before comparing prices. If the source of the stored comparison rate is unclear, ask support to identify the mapped room, plan, stay date and net rate used. 5. If the details show a previous-version warning, return to Reservations → Search, enter the reservation number and select Search. Review the latest stored version before acting. The result establishes that a stored comparison met your threshold. It does not establish a delivery failure, an incorrect guest charge or a need to resend inventory. Do not amend, cancel, charge, refund or resend a booking based only on this report. See Review reservation details for the booking document and its price fields. Missing comparisons and empty results Some runs show notices for skipped nightly comparisons: - Unresolved Expedia rate plan: the report could not resolve a usable comparison mapping through that lookup. - Missing or nonpositive comparison rate: a stored inventory row was found, but its net rate was missing, zero or negative. These counts describe room-night comparisons, not bookings. One booking can contribute more than one skipped comparison and can still appear because another night qualifies. The notices are not a complete coverage summary. Missing room mappings, unavailable inventory rows, unsupported comparison setup, some missing or disabled rate plans, and a recorded nightly booking price of zero can cause silent exclusions. A blank notice area therefore does not prove that every night was compared. No discounted reservations to report... means that none of the records actually examined produced a qualifying comparison. It can mean no recent bookings, no qualifying prices, unavailable comparisons or a combination of these. It does not mean zero discounts across your property. Field reference Control What it does Values and important limits Property selector Chooses the property whose stored bookings are examined. You need access to the property. Check the selected property before running the report. Min Discount % Minimum nightly difference from the stored net rate required for inclusion. Whole-number entry; default 10 . The form offers 1–100 . The threshold is checked before rounding. Past Days Looks back from the run time using reservation-record creation timestamps. Whole-number entry; default 1 , minimum 1 . Each day represents a rolling 24 hours, not a calendar day beginning at midnight. This is not an arrival, departure or stay-date filter, and a received modification can be included. The newest-50-record limit still applies. View Report Reloads the report with the selected filters. Applies both fields. It does not save inventory or send reservations. New window Opens the loaded report in a separate tab without the main navigation. Apply changed fields first. This control is available on the normal page, not repeated in the standalone view. Reservation result link Opens the specific stored version used by the report. Opens in a new tab. A later modification can make that version historical. Common problems - The result did not change after editing a filter: the inputs are not applied until you select View Report. Check their retained values after the page reloads. If they revert or an error appears, give support the property, filter values, action time with time zone and error text. - An expected booking is absent: check the property and receipt lookback, then use Reservations → Search with the reservation number and select Search. The report may exclude canceled bookings or lack a usable comparison. It may also have reached its 50-record examination limit. If the booking is present in Search but its omission remains unexplained, ask support to inspect its mapping and stored inventory; widening the lookback alone does not guarantee inclusion. - The percentage looks too high: compare the same night, currency, tax basis, occupancy and rate plan. The displayed percentage is the largest qualifying night, not a stay average. If the amounts still do not reconcile, give support the property, channel, reservation number, affected stay dates, filters and run time. Do not change prices to make the report match. - Skipped-comparison notices appear: a comparison was unavailable, not necessarily a failed update. Ask an authorized administrator or support to review the relevant mapping and stored net-rate data. Do not resend inventory merely to clear the notice. - A result link fails or shows an old version: search again from the correct property using the channel reservation number. If the current Search result also fails, report the visible error and relevant references. Do not recreate the booking. Keep guest details and payment information private. Do not send passwords, card data or full reservation screenshots with an investigation request.
Find recent multi-room bookings
Use Group Bookings to find recently received reservations with several rooms, then open the recorded booking to check whether it needs coordination. Before you start Select a property you can access. This report covers that property, not your whole organization. Running it reads stored reservations; it does not create a group block, change a booking, reserve additional inventory or resend anything. A qualifying booking is one reservation with at least the selected number of recorded rooms. Separate reservations are not combined because they share a guest, company or stay dates. This is not a group-block management or pickup report. Run the report 1. Select the intended property in the property selector. 2. Open Reports → Reservations → Group Bookings. The page heading is Group Reservations. 3. Set Minimum Rooms to the smallest booking size you want to find. 4. Set Past Days to the receipt lookback you want to examine. 5. Select View Report. Changing a field alone does not apply it. 6. Check that both values remain selected, then review the links or the empty-result message beneath the controls. The initial report uses Minimum Rooms = 6 and Past Days = 1 unless the link you opened supplies other values. Group Reservations with Minimum Rooms 2, Past Days 7, View Report, New window and an empty result Example: a demo-property report after applying Minimum Rooms 2 and Past Days 7. The empty result is not an example of a qualifying booking. Understand which bookings qualify The report considers the latest stored version of each channel reservation for the selected property. That version must be a new or modified reservation, fall within the receipt lookback, and meet the room threshold. A latest cancellation excludes the booking. Past Days is a rolling receipt window, not a stay-date filter. One day means the preceding 24 hours when the report runs; it does not mean yesterday or the current local calendar day. The window uses when ChannelRUSH recorded the reservation version, not necessarily when the guest originally booked. A recently received modification can therefore bring an older booking into the report. Arrival and departure dates do not determine inclusion. Minimum Rooms counts recorded room entries within one reservation version. The threshold is inclusive: a reservation with exactly six recorded rooms meets a minimum of six. This is not a guest count, room-night count or count of distinct room-type names. Read and check the result Each matching reservation appears as a link. The link text identifies its confirmation or modification, channel and channel reservation ID. The list does not provide separate columns for room count, stay dates, guest details, amounts or delivery status. 1. Select a reservation link to open its details in a new tab. 2. Check the property, channel reservation ID, status, rooms and stay dates before arranging any follow-up. 3. Use Review reservation details for the detail fields and access requirements. The link opens the stored version represented by that result. If the booking may have changed since the report loaded, rerun View Report and investigate the current result rather than treating an older detail tab as live status. A listed reservation is a candidate for review—not proof of a contracted group, a delivery failure or successful PMS delivery. Opening details does not amend, cancel or resend the booking. No group reservations to report... This means the report found no matching reservations for the selected property, room threshold and current rolling receipt window. It does not establish that the property has no future group stays or that every reservation has been delivered successfully. Check the selected property first. If appropriate, reduce Minimum Rooms, increase Past Days, and select View Report again. A booking can remain absent because its latest stored version is canceled, too old for the receipt window, or below the room threshold. Open the report separately Select View Report to apply any changes, then select New window. The report opens in a separate tab without the main application navigation, leaving the original page open. The new tab retains the loaded property and filter values; it does not apply unsent edits from the original form. You can change the two fields and select View Report in that tab. Close it to return to the original page. Each reload evaluates the moving receipt window again, so results can change over time. This page has no Excel, CSV or PDF export, clipboard control, or email-send action. A Group Reservations section in a saved report has separate configuration, including a Past Hours setting; running this standalone report does not change an email schedule. Field reference Control What it does Values and example Property selector Chooses the single property whose stored reservations are examined. Select the property before opening or running the report. Minimum Rooms Minimum number of recorded rooms in one reservation. The boundary is inclusive. Enter a whole number of at least 2 . Initial value: 6 . Use 2 to include bookings with two or more recorded rooms. Past Days Rolling lookback for when the latest reservation version was recorded in ChannelRUSH. Enter a whole number of at least 1 . Initial value: 1 , meaning the preceding 24 hours. Use 7 for the preceding seven 24-hour periods. View Report Applies the displayed criteria and reloads the result. Select it after changing either field. It does not save reservation changes or send messages. New window Opens the loaded report in a separate tab without the main navigation. Apply your criteria with View Report first. This control is not repeated inside the separate report tab. Reservation link Opens details for the stored reservation version shown in the result. Review the identity, status, rooms and dates; do not read confirmation/modification as a delivery outcome. Keep both numeric fields filled with ordinary whole-number values. The browser exposes minimums, but the page does not provide a documented maximum or comprehensive validation messages for manually altered URLs. Common problems - The report still uses the old criteria: changing a field does not reload the result. Select View Report, then confirm the retained values. If you opened New window first, return to the original tab, apply the changes and reopen it. - A known booking is missing: check the property, latest reservation status, recorded room count and receipt window. Separate booking IDs do not add together. For an individual booking, open Reservations → Search, enter its Reservation ID and select Search; a missing Group Bookings result is not proof that the reservation is absent from ChannelRUSH. - The browser refuses a value: use whole numbers of at least 2 for Minimum Rooms and at least 1 for Past Days. Do not bypass the form by editing the URL to force unsupported values. - The report shows an error or fails to load: an error is not an empty result. Reopen Reports → Reservations → Group Bookings to return to the default criteria, then try a modest lookback. Rerunning this report does not send or change reservations. If the failure persists, contact support with the property, both criteria, action time and time zone, and the visible error text. - Details request password verification or deny access: follow the normal ChannelRUSH verification prompt or ask your organization administrator to check property access. Do not send a password to support. Use the linked reservation-detail guide for protected payment fields. Do not include payment details, passwords, full reservation screenshots or unnecessary guest information in a support request.
Review recent manual inventory updates
Use Manual Inventory Updates to review a property's recent user-associated inventory requests, see their recorded values and identify what needs a separate delivery-status check. Open and load the report You need a sign-in with access to the property. You do not need an inventory-edit permission to view this report. 1. Select the property in the property selector. 2. Open Reports → Diagnostics → Manual Inventory Updates. The page heading is Manual Updates. 3. Enter a positive whole number in Past Days. The initial value is 1. 4. Select View Report. 5. Check the retained Past Days value, then read the summary and request cards below it. Changing Past Days alone does not refresh the results. View Report only reloads the report; it does not create, retry or send inventory updates. Past Days set to 2 beside the View Report button. Apply the lookback with View Report before reading the results or opening another window. What Past Days means Past Days is a rolling creation-time lookback, not a selection of calendar days or stay dates. 1 looks back over the preceding 24 hours from the time the report loads. It does not mean “since midnight.” The dates shown inside each card are the affected inventory dates and can extend into the future. Start with the smallest useful lookback and increase it if necessary. This report does not provide pagination or a separate channel, room, rate-plan or user filter. What is included The report looks for recorded inventory requests associated with an existing user in the property's organization. It is not restricted to requests associated with your own sign-in. It is not a complete audit of every inventory change. Automated requests without that user association, requests no longer retained in this report's records, and requests outside the lookback can be absent. The report does not select only successful requests. A listed request proves that a request record was found. It does not prove that it was sent, accepted by a channel, or is still the channel's current value. There is no processing-status filter or delivery-status indicator on this page. Read the summary The summary and By User section count requests, not edited nights, rooms sold, successful deliveries or clicks on Save. One operation can produce several requests for different channels and products. Summary Meaning Total Updates All requests loaded for the selected property and lookback. Rate Updates Requests containing the main rate pair or additional rate parameters, such as occupancy rates. Availability Updates Requests containing an allocation value. Restriction Updates Requests containing Stop Sell, arrival/departure closures, cutoff days, or minimum/maximum-night restrictions. By User The same request counts grouped by the associated user. Total , Rate , Availability and Restriction use the definitions above. The categories overlap. A request containing a rate, allocation and Stop Sell contributes to all three categories but only once to Total Updates. Do not add the category counts to calculate a total. These groups describe fields present in a request, not a comparison with earlier or channel values. An explicit No restriction or 0 allocation still counts. Additional channel-specific parameters are not necessarily represented by one of the three category counts. Read a request card A demo request card with channel, room, rate plan, affected dates, rate and restriction values, and creation timestamp. This is a recorded demo request, not a live channel-inventory check. The asterisk beside Sell Rate identifies the request's rate basis, not delivery success. Read each card from top to bottom: 1. Check the channel, followed by the room and rate plan where applicable. A room-level or property-level request may not have both product names. 2. Check the affected date range. If weekday abbreviations appear beside it, the request selects those weekdays within that range: Mo, Tu, We, Th, Fr, Sa and Su. 3. Read the Rate, Availability and Restriction badges as categories of included values, not processing states. 4. Read the values shown in the body. A missing field is not evidence of zero, No, or a default value on the channel. 5. Check the user and timestamp at the bottom. This is the request's creation time, displayed in your user's time zone, not its last processing time or the property's check-in date. Cards are not a before-and-after comparison. Product names and available additional-field labels reflect the current setup. They are not a permanent snapshot of all historical configuration. No restriction changes means the card has no standard restriction values to display; additional parameters can still be present. It does not mean that nothing changed or that delivery succeeded. Cards have no request-detail or retry link. Use the separate status workflow below when you need processing evidence. Check delivery separately 1. Keep the same property selected and open Updates → Status. 2. Select the destination Channel and leave Status as All initially. 3. If needed, narrow Room Type, Rate Plan, Sent By or Source. Use Stay Dates for the affected inventory dates; use Date and Time → Created for when the update was made. 4. Select Search. Changing those controls alone does not apply them. 5. Check the retained filters and matching values. Read the recorded Status, message and timestamps; inspect available request details or logs where needed. Search reads results. Go runs the chosen action and must not be used to refresh a search. Do not resend inventory merely because a card is missing here or a result is missing from a filtered status search. The two screens do not use identical categories or records. On Status, Created refers to the displayed change or older request. It may differ from the request creation time in this report. Start with the channel, product and affected dates, and avoid an overly narrow creation-time range. In this report, Stop Sell counts as a Restriction Update. The Status page's Availability data filter includes Stop Sell. Leave all Data boxes unticked when you need to avoid that narrowing. Do not expect the two screens' totals to reconcile automatically. A Successful status is recorded processing evidence, not an independent check of the channel's current inventory. For a current-value dispute, confirm the intended channel product and dates as well. See Investigate inventory update status for a property for detailed searching and safe recovery. Open a separate report window Select View Report first to apply any edited Past Days value. Then select New window to open the loaded property and criteria in a separate tab or window without the main application navigation. Your original page remains open. The separate window still has Past Days and View Report. Its results are loaded again, so new activity and the rolling time cutoff can change them. This is not a frozen snapshot. There is no Excel, CSV, PDF or email-send control on this standalone report page. Request-field reference Only applicable recorded fields are displayed. These descriptions identify the requested values; they do not establish which restrictions a channel ultimately accepted or how multiple channel rules combine. Field How to read it Channel / room / rate plan Destination channel and, where applicable, room type and rate plan. Room-level and property-level requests may omit product names. Date range Inventory dates affected by the request, separate from its creation timestamp. Weekday badge Selected weekdays within that range when the request is not set to every weekday. Sell Rate Recorded selling-rate value with its currency code. Net Rate Recorded net-rate value with its currency code. Rate asterisk * Marks the rate basis recorded for the request: Sell Rate or Net Rate. It is not a validation or acceptance marker. Allocation Recorded availability quantity. Zero is an explicit quantity, not a blank or omitted value. Stop Sell Yes requests a stop-sell restriction; No requests that this restriction be off. No does not prove the product is bookable, because availability and other restrictions can still prevent sales. CTA Closed to arrival: the recorded Yes/No arrival restriction. CTD Closed to departure: the recorded Yes/No departure restriction. Cut Off Days Recorded advance-booking cutoff in days. Min Nights / Max Nights Recorded minimum/maximum length-of-stay values for arrivals on the affected dates. Min Nights Thru / Max Nights Thru Recorded through-stay minimum/maximum-night restrictions for stays including the affected dates. Additional rate parameters Channel-specific rate fields, such as Occupancy1Rate or Occupancy2Rate , with the request currency. Which ones appear depends on the request and channel's supported fields. Other additional parameters Channel-specific recorded values, shown under their parameter labels when available. Ask support about an unfamiliar parameter rather than inferring its meaning from its position. User and timestamp Associated user and request creation time in your user's time zone. Not a processing result or completion time. This is a read-only report. Do not use a numeric zero seen here as a general instruction for clearing a restriction in an editor; accepted input and removal values depend on the field and workflow. Common problems - The results did not change after editing Past Days: the edit is not applied yet. Select View Report and check the retained value. If the report still does not reload, note the page URL and any error before contacting support. - No Manual Updates: no matching requests were loaded. Confirm the property, widen the lookback modestly and select View Report. Then check Updates → Status if you expected a particular change. An empty report does not prove that no inventory changed or that delivery succeeded. - A card is absent although you expect an update: the creation time, user association or retained records may be outside this report's scope. Search Status using the property, channel, product and dates. If still missing, give support the approximate action time and its time zone; do not submit the update again to create evidence. - Category counts exceed Total Updates when added together: requests can belong to several categories. Compare each count independently; this is not evidence of duplicate delivery. - Total Updates exceeds the number of visible cards: the summary can include a request whose current channel does not support this card display. Check Status and ask support to reconcile the discrepancy; do not infer that a missing card is a successful or failed update. - A Rate badge appears without ordinary Sell Rate / Net Rate lines: the request may contain additional rate parameters. Read those fields. If their meaning or display is unclear, ask support with the property, channel, affected dates and creation time. - Values or times differ from another screen: distinguish affected dates from creation time, verify your user's time zone, and compare the same product and request scope. Later changes can replace earlier inventory values. Escalate unresolved discrepancies without retrying blindly. For support, include the property, channel, room/rate plan, affected dates, Past Days, creation time/time zone and relevant error text. Include an identifier from Status if available. Do not include passwords, payment details or unrelated guest information.
Find and investigate inbound PMS inventory messages
Use PMS ARI Log to find messages received from your property management system (PMS), check their recorded processing status and collect useful information for an inventory investigation. ARI means availability, rates and inventory. Before you start Select the property you want to investigate. This log searches one property at a time, within your account's access. Admin → PMS ARI Log appears for properties with a PMS/inventory-receive connection. This is an inbound-message log, not an outbound channel-delivery report. A Successful message does not establish that a booking channel accepted an update. Some PMS connections are polled rather than sending messages directly; an empty log does not, by itself, mean the connection has stopped working. The page states that message history is limited to the past 90 days. Treat this as the normal searchable-history window, not a guarantee that every message is retained or that older records have been permanently deleted. Find a message 1. Select the intended property in the property selector. 2. Open Admin → PMS ARI Log. 3. Leave Status at All for an initial investigation, or choose the processing status you need. 4. Set Date and Time around when the PMS sent the message. These are message creation times, not the inventory's stay dates. Use the time zone named beneath the controls. 5. Add Search Text, Message Name, Message ID or Room Type only when you need to narrow the search. 6. Select Search. Editing a field alone does not apply it. 7. Check the retained fields and Filtered by chips, then review the Info and Message Text columns. All populated filters apply together. If you have an exact Message ID, clear unrelated filters first: that ID does not override Status, text, room or date filters. The ID is ChannelRUSH's log-message ID, not a reservation number or outbound update transaction ID. To remove one applied filter, select its Filtered by chip. Removing the date chip clears the date/time window. Cancel returns to Admin; it is not a clear-all-filters button. Read the results The log normally returns up to 50 messages per page, in descending message-ID order. The « and » paging controls, when available above and below the results, move toward newer and older messages respectively. Applied filters remain in effect. A full final page can lead to an empty next page; that does not mean messages were removed. - Info: message name, recorded processing status, creation timestamp in your user time zone, internal message ID and View link. - Message Text: the incoming request body, often XML or JSON. The list displays at most the first 1,000 characters of each message. The preview can end without an ellipsis; do not treat it as the complete request. - No rows beneath the headers: no messages matched the current property and filters in the searchable store. This is not a delivery-success indicator. What Status means Status Meaning What it does not establish Pending The message is recorded and awaiting processing. That its inventory has been applied or sent onward. Processing Processing has started. That processing will finish successfully. Successful The inbound processor recorded a successful outcome. That the message contained usable inventory for every product, generated outbound updates or was accepted by an OTA. Unsuccessful The row is displayed as unsuccessful. That nothing was saved, that the cause is still active or that repeating the PMS send is safe. If you know an unsuccessful message exists but cannot find it with Status = Unsuccessful, try All and its Message ID with other filters cleared. Some reviewed failures can still display as Unsuccessful without appearing in that filtered search. Open the complete message safely 1. Select View beside the relevant message. It opens a separate tab so you can retain the search results. 2. Check the message name, ID and timestamp before interpreting its contents. 3. Read REQUEST for the incoming message and RESPONSE for the stored response. 4. Use Save Log File only when you need a local copy for an investigation. The response can be an intake acknowledgment rather than the final processing outcome. It is not a separate guarantee of successful channel delivery. The downloaded log contains request and response sections and uses UTC timestamps; compare these carefully with the page's user-time-zone timestamp. The section timestamps refer to message creation, not separate request/response duration measurements. Treat message bodies and downloaded logs as confidential. They can contain credentials, tokens or other sensitive information. Before sharing a screenshot, search URL or file, remove secrets and unnecessary personal or commercial information. Prefer giving support the property, message ID, timestamp and time zone first. Do not paste raw payloads into a public conversation. If an old View link fails, return to the log and search again rather than changing IDs in the URL. Give support the known message ID and property if the record cannot be opened. Check the inventory outcome Finding the message establishes that a record is present; its status describes inbound processing only. 1. Check the expected PMS values in Reports → Rates & Availability, using the relevant PMS image and affected inventory dates. 2. Investigate any expected onward update in Updates → Status. Apply the relevant search filters and select Search on that page as well. 3. If the stored PMS values, outgoing update status and expected channel values disagree, collect the property, PMS/channel, room or rate plan, affected dates, message ID and action time/time zone for support. Do not resend PMS inventory solely because this log is empty or a message is marked Unsuccessful. Reconcile the stored inventory and outbound status first; this page has no retry or resend control. Field reference Field or control What it does Example or important detail Status Filters the stored inbound processing status. Defaults to All . Start with All when an exact message appears to be missing. Search Text Finds a case-insensitive text fragment in the request body. Does not search the stored response. Blank adds no text filter. Search a distinctive product code rather than a password or complete payload. Message Name Finds a case-insensitive fragment of the recorded message name. Blank adds no name filter. Use part of the name shown in an earlier result. Message ID Matches one internal numeric log-message ID for the selected property. Other filters still apply. Copy the ID from Info or the message viewer. Date and Time — first date/time Lower bound for message creation. A date without a time starts at midnight in the indicated zone. Leave blank for no lower bound; a time without its date has no effect. Date and Time — second date/time Upper bound for message creation. A date without a time includes the entire final day; a specified time includes its whole minute. Leave blank for no upper bound. Do not place it before the first endpoint. Room Type Searches request text for the selected PMS room code. Defaults to All and appears when room mappings are available. Text matching can also find that code elsewhere in a message; inspect the request to confirm the affected room. The choices are not a combined catalogue of every PMS connection. Search Applies the current filters and restarts at the first results page. Check the resulting chips and retained values. Filtered by Shows applied filters and lets you remove them. Removing the date chip clears the whole date/time window. Cancel Returns to Admin. Does not retry a message or change inventory. Text matching treats % as a wildcard for any sequence and _ as a wildcard for one character. Prefer a distinctive fragment without these characters when you want a straightforward lookup. The date controls are below the text filters; the time-zone note explains how to interpret them. PMS ARI Log date, time-zone and room-type filters Date/time and room filters in the demo property. Blank date/time controls add no date narrowing; select Search after changing them. Common problems - The results are empty. Check the selected property, remove restrictive chips and search again with Status All. Confirm the message falls within the normal searchable history. If it still cannot be found, ask support whether this PMS integration produces inbound log messages; provide the expected send time/time zone and affected products/dates, not credentials. - “The End Date cannot be before the Start Date.” Correct the date/time order, then select Search again. An exact Message ID does not bypass this check. - The Room Type choice is absent or unexpected. The choices depend on stored PMS room mappings. Use All and a distinctive Search Text fragment if appropriate; ask support to confirm the mapping rather than editing configuration to make a log appear. - Successful, but the channel still has different inventory. Compare the PMS image and outbound Updates Status. A successful inbound record is not channel acceptance. Escalate with both the message reference and the affected dates/products. - A message stays Pending or Processing, or repeats as Unsuccessful. Recheck the same ID and collect the current status and timestamp. Ask support to inspect processing before requesting another PMS send; no completion-time promise is implied by these states. - A preview seems incomplete or a response conflicts with the status. Open View for the full request. Remember that the response may record intake, while Status describes later processing. If that does not explain the discrepancy, send support the ID and a redacted description. Related - Investigate inventory update status for a property - Request support with useful diagnostic information
Find and check your channel promotions
Find a property's promotions, understand their displayed state, and decide whether to refresh the channel list or investigate an uncertain offer. Before you start - Select the correct property. Promotions on this page belong to that property, not every property in your organization. - Your property needs a supported channel connection. A channel can appear in the filter before its setup is complete; that does not guarantee a promotion card will appear. - Update - Rates or Channel Settings permission exposes channel promotion controls, including Refresh Promos List. Update - Rates or Booking Engine / CRS - Settings exposes Add New for CRS promotions. Access to a control does not establish that a channel will accept an operation. - This guide covers the Promotions list and list refresh. Creating or changing an offer's discount, booking dates, stay dates, products or blackouts happens in its separate editor. Do not save an offer merely to inspect its current state. Open the list and find an offer 1. Select the property in the property selector. 2. Open Channel Tools → Promotions. 3. Choose a Channel, or leave All selected. 4. Choose Enabled → All when you need to find disabled offers as well as enabled ones. 5. Find the offer in its channel's card. Changing either filter reloads the list immediately. There is no Search or Apply button. Refresh Promos List is a different operation: it contacts channels and updates stored records. The normal starting Enabled selection is Yes. Channel offers marked Unconfirmed remain visible under both Yes and No, so you do not lose track of unresolved work. CRS promotions follow the Enabled filter without that exception. Promotions filters with Channel and Enabled set to All, and the separate Refresh Promos List button. Filters change the displayed list. Refresh Promos List changes stored channel-promotion information. Check the filtered result Check that the selected Channel and Enabled values remain selected after the page reloads. Then inspect the relevant card and offer row. Card counts describe the rows currently displayed, not the total number of offers that exist at the channel. No promotions configured for this channel. can mean that no stored offers match the current filter. Set Enabled → All before concluding that an offer is missing. An empty card does not prove that the channel has no offers. When multiple channel cards are shown, Jump to links help you reach a channel section. These links can return Enabled to its default Yes selection. Recheck the filter after using one if you were looking for disabled offers. Read the cards and offer states Channel cards and the ChannelRUSH CRS card are related lists, but their identifiers and actions are not interchangeable. Demo promotion results showing a CRS offer and empty Booking.com and Expedia.com cards. This demo has one displayed CRS offer and no displayed offers in the two channel cards. It does not demonstrate a live channel confirmation. Channel promotion columns Column or state What it tells you Name The stored offer name. Select it to open that channel's offer editor. For a nonpending offer with a remote identity, opening the editor can retrieve channel details and update the stored copy; it is not a frozen historical view. Promo ID The offer's identifier at the channel. Use this with the property and channel when investigating an offer. A matching name alone is not enough. Enabled: Unconfirmed Local work is pending confirmation. This can include saved changes that were not sent as well as a submission whose outcome is uncertain. This label takes precedence over Draft and Yes/No. Do not assume the channel received the intended values. Enabled: Draft The stored offer has no channel Promo ID and no pending marker. This is not proof of a published channel offer. Enabled: Yes / No The stored enabled flag for an offer with a channel Promo ID and no pending marker. It is not a fresh channel lookup or proof that the offer is currently bookable. The number beside a channel name is its displayed row count. If a separate Enabled count appears, it counts displayed enabled records that are not pending. It is not a count of bookable offers. ChannelRUSH CRS columns Column or action What it tells you ID The local CRS promotion identifier. It is not an OTA Promo ID. Name Opens the CRS promotion editor, not the Booking.com or Expedia editor. Enabled The stored CRS enabled flag. Other promotion conditions still determine whether it applies to a booking. Delete Opens a separate deletion-confirmation page. Do not confirm deletion as a way to refresh or investigate an offer. Add New Opens the CRS promotion editor for a new offer. The identically named button in an OTA card opens that channel's editor instead. Refresh stored channel-promotion names and status Use Refresh Promos List when you intentionally want to retrieve the available channel lists and update ChannelRUSH's stored names and enabled flags. This is not a page reload or a full offer-detail synchronization. It can import previously unseen channel offers and update existing stored names and status. It does not submit new offer terms, activate or deactivate an offer at the channel. It does not refresh the CRS promotions card. 1. Select the correct property. 2. Choose the specific Channel you want to refresh. All can refresh multiple supported channel connections; it is not limited to the card you are looking at. 3. Confirm that you intend to update the stored list. The Enabled filter does not limit which offers are retrieved. 4. Select Refresh Promos List. 5. Read any error or warning at the top of the returned page. 6. Set Enabled → All if necessary, then compare the intended offer's Promo ID, name and displayed state. A list refresh does not replace pending local work. It also retains offers that were not returned by the channel and records associated with an earlier remote-property connection. Their continued presence is not proof that they still exist or are active remotely. Check the refresh result The returned list shows the stored outcome; it is not a receipt proving current bookability. Refresh updates names and enabled flags, not every discount, date or product condition. Connections are handled separately. If you refreshed All, a warning or failure for one connection does not undo successful updates to another. A failed list retrieval leaves that connection's stored list unchanged. A busy connection is skipped with a warning. For consequential decisions, match the exact property and Promo ID against the offer in the channel's own authorized interface. Inspect its dates, products and restrictions there. Do not use a Yes badge alone to promise a guest that a discount will apply. Investigate an unconfirmed or missing offer 1. Set Channel to the relevant connection. 2. Set Enabled → All. 3. Record the offer's displayed name, Promo ID if present, and state. 4. Check the exact offer and property in the channel's own interface, or ask support to help establish the outcome. Do not create another copy, delete the record or repeatedly save an uncertain submission. A timeout or error does not prove that the channel did nothing. If the editor offers Reload confirmed offer and discard local edits, treat it as a deliberate replacement of local values, not a harmless retry. It reads the confirmed remote offer and replaces local edits; it does not send a channel update. An uncertain creation may require the verified remote offer ID. If that identity is unknown, or an operation is still running, stop and ask support rather than guessing an ID or recreating the offer. Filter and control reference Control Values and scope Channel All or one available property connection. Choosing a value immediately reloads the list. Supported OTA connections need completed setup to display a card. CRS needs stored CRS settings. Enabled Yes on normal entry; No for disabled records; All for both. Pending OTA offers remain visible regardless of Yes/No. Each change reloads immediately. Refresh Promos List Retrieves supported channel lists and saves names/status locally. Channel limits its connection scope; Enabled does not limit retrieval. CRS is excluded. Jump to Shown when multiple setup OTA channel cards are displayed under All. Recheck Enabled after following a link. Add New Opens a new-offer editor for the card's channel or CRS. Opening it is not publication; saving may have live selling effects. Common problems - A channel is selectable but its card is missing. Its connection may not have completed setup, or its CRS settings may be missing. Confirm the property and connection with your administrator. If setup is complete and the card remains absent, contact support; do not add a duplicate connection. - An offer disappears after filtering. The stored enabled flag may not match the selection. Choose Enabled → All and verify the channel. If the offer is still absent, compare its exact remote ID before deciding whether to refresh the list. - Refresh says the list could not be retrieved. That connection's stored list was not changed by the failed retrieval. Check the connection/error with support if it persists. Do not recreate offers as a workaround, and check other connections separately if you refreshed All. - Another promotion operation is running. The affected connection was not refreshed. Let the current operation finish and re-open the list. If its state is unclear or the warning persists, ask support before repeating an action. - A saved offer was not returned, or belongs to a previous remote property. ChannelRUSH retains its identity rather than deleting or transferring it. Verify the old and current property/offer identities with support. Absence from a returned list does not establish deletion. - An offer remains Unconfirmed after refresh. List refresh deliberately preserves pending work. Follow the investigation steps above; do not treat another list refresh as confirmation of the pending submission. - Add New or Refresh is absent, or the editor refuses an operation. Ask your administrator to check the relevant pricing/settings permission. A visible control does not guarantee downstream permission or provider eligibility. If an operation failed after you tried to save, inspect the offer's state before retrying and give support the error text. For support, include the property, channel, local offer identity or Promo ID, displayed state, action time with time zone, and exact error text. Never send passwords, connection credentials, payment details or unrelated guest information. Related - Set up and maintain ChannelRUSH CRS
Create and edit a channel promotion
Create or change a Booking.com or Expedia promotion for one property, then check whether your changes were saved locally or confirmed by the channel. Before you start - Select the correct property and check the channel named at the top of Edit Promo. This guide covers the Booking.com and Expedia cards, not the separate ChannelRUSH CRS promotion editor. - The channel connection must be set up, with the room types and rate plans you intend to discount mapped to it. - Use an account with Channel Settings permission to publish channel changes. Update - Rates can expose the editor and Save controls, but does not by itself satisfy the channel-publishing permission check. Ask your administrator to confirm access before saving. - Decide the discount, eligible products, booking window and stay window before enabling the offer. Saving an enabled offer attempts to publish it; Save & Refresh is not a preview. - An existing offer may be read-only because its type or conditions are not supported here. Manage those conditions in the channel extranet or contact support; do not try another Save control as a workaround. Changing fields does not submit this editor. Save and Save & Refresh submit the form. Editing blackouts or deactivating an offer uses separate submit actions, explained below. Open or create an offer 1. Select the property in the property selector. 2. Open Channel Tools → Promotions. 3. Choose the relevant Channel. 4. Set Enabled → All if you need to find a disabled or draft offer. 5. Select the offer's name, or select Add New in that channel's card. 6. Check the channel name and Channel Promo Id before editing. The list filters reload immediately. Refresh Promos List is a different operation that contacts channels and updates stored list information; it is not needed to open a new form. Opening an existing confirmed offer can retrieve its channel details and refresh ChannelRUSH's stored copy. If the channel cannot be contacted, a warning says that you are seeing local values that may be out of date. An offer with pending work retains its local values instead of automatically replacing them. Complete and save the promotion 1. Enter Name. 2. Choose the promotion type and the channel-specific conditions in the field reference below. An existing channel offer's type cannot be changed here. 3. Enter the discount. For Expedia, choose Discount Type first: Day of Week, Single, or Multi-Night. 4. Set Booking Date Range for when bookings may be made, if required for the offer. 5. Set Stay Date Range for the eligible stay dates. 6. Complete any applicable stay or advance-booking restrictions. 7. Select the eligible Rate Plans. For Booking.com, also select Room Types and the stay Days. 8. Choose Enabled → No for a new local draft. If the offer needs blackout dates, save it disabled, add and verify those dates using Add or edit blackout dates below, then reopen the offer and select Enabled → Yes only when ready to publish. Otherwise select Yes when you intend to publish the offer. 9. Select Save to submit and return to Promotions, or open the arrow beside Save and select Save & Refresh to submit and reopen the editor. 10. Read the result message and follow Check the result below. Discount coupling: changing Discount Amount or its percentage selector clears the weekday amounts. Changing a weekday amount clears the single Discount Amount. This does not choose Expedia's Discount Type for you. Recheck both the type and amounts before saving. Product scope: Booking.com applies the offer to valid combinations of the selected rooms and rate plans. All Room Types and All Rate Plans select or clear their checklists; no selection does not mean all products. Selecting PromoNonRefundable → Yes changes the offer's booking policy to non-refundable. Persistence warning: ChannelRUSH can save your local changes before a later channel-access check or channel request fails. An error does not necessarily mean nothing was saved. Do not repeatedly save or create another offer when the outcome is uncertain. Cancel leaves the form without submitting the current edits. It does not undo an earlier save or a refresh of confirmed channel details. Check the result 1. Return to Promotions and select the same channel. 2. Set Enabled → All so disabled offers are not hidden. 3. Find the offer and inspect its Promo ID and displayed state. 4. Open the offer again and compare its settings with your intended values. Read any warning about local or unavailable channel data. 5. For a published change, check the same property and promotion ID in the channel extranet, including the discount, dates and products. Interpret the result carefully: - Draft: the stored offer has no channel identity and no pending marker. A newly saved disabled draft is local work, not a published channel promotion. - Unconfirmed: local work remains pending. It can mean changes were not sent or that a submission's outcome is uncertain. It does not prove the channel accepted the intended values. - Yes / No: the list shows the stored enabled flag for an offer with a channel identity and no pending marker. This is not proof that the offer is currently bookable. - A successful enabled save means either the channel acknowledged the operation or ChannelRUSH confirmed that the intended values already matched the channel offer. It does not establish current bookability. Other promotion conditions, product availability and the channel's selling rules still determine booking eligibility. If the channel cannot be read, reopening the editor does not establish a fresh confirmation. Keep the error and offer identity for support rather than assuming that the values on screen are the remote values. Deactivate without mixing in content changes For an existing channel offer, deactivate separately from changing its discount, dates or products. 1. Open the correct existing offer and leave its content unchanged. 2. If Deactivate is available, open it and review the separate confirmation page before confirming. Otherwise select Enabled → No and save that change alone. 3. Check the result in the Promotions list and the channel extranet. Opening the Deactivate link alone does not deactivate the offer. The record and remote identity are retained after deactivation. Setting Enabled to No on a new offer with no channel identity instead saves a local draft, subject to form validation. Add or edit blackout dates Stay Date Range Blackouts appears after the promotion has first been saved. A new unsaved form does not show it. Blackouts cannot be saved here on an inactive offer that already has a Channel Promo Id, or while the offer is read-only or has pending changes. Do not activate an offer merely to unlock blackout editing; use the channel extranet or contact support. 1. Save a new offer as a disabled draft before proceeding if you are not ready to publish it. 2. Reopen the offer and locate Stay Date Range Blackouts. 3. Select Add New, or Edit beside an existing range. 4. Set the blackout Start Date and End Date. 5. Select Save on the blackout form. For a disabled draft with no Channel Promo Id, this saves the exclusion locally without publishing it. For an enabled channel offer, it saves locally and attempts a channel update. Read the result before continuing. 6. Reopen the parent offer and verify the exclusion and channel result. A blackout form saves separately; you do not finish it by pressing Save later on the parent editor. Avoid leaving unrelated unsaved parent edits before navigating away. For a published Booking.com offer, removing or shortening existing excluded dates is refused here. Remove those exclusions in the Booking.com extranet, then reload the confirmed offer. The same removal restriction applies to published Booking.com additional dates. Expedia offers can expose a separate Delete confirmation for a blackout range; do not use deletion to investigate an uncertain save. Recover an uncertain outcome Do not repeat Save, recreate the promotion, or discard local work until you know which operation occurred. 1. Record the property, channel, Channel Promo Id, action time with time zone, and exact message. 2. Check the exact offer in the channel extranet. A matching name alone is not enough. 3. If the message says values were not sent, resolve the stated validation, access or connection problem. Reopen and inspect the retained local values before deciding whether to submit again. 4. If the outcome is unconfirmed, check with support before another write. List refresh does not resolve pending promotion details. 5. Use Reload confirmed offer and discard local edits only when you intentionally want to replace the local work with the channel's confirmed offer. That reconciliation button reads the channel and replaces local details; it does not publish your current edits. For an uncertain new offer without a channel ID, it asks for Verified promotion ID from the channel (check the exact property and offer; a name is not an ID). Obtain the exact ID for the correct property. Do not guess it or create another offer to obtain one. An operation still running, changed connection, or conflicting record can prevent reconciliation; contact support if the state remains unclear. Field reference: shared controls Field What to enter or check Name Required offer name. Booking.com allows up to 255 characters. Use a name that helps you identify the offer, but verify its remote ID before recovery actions. Channel Promo Id Display-only identifier at the channel; a dash means none is displayed. It is not the local list record's identity or the offer name. Enabled New forms start at No . Yes attempts publication on Save; No is a local draft when no remote identity exists. Deactivate an existing remote offer separately from content changes. Discount Amount Percentage, not currency: enter 15 for 15%. A single or nth-night discount must be greater than zero and no greater than 100. Leave this blank for Expedia Day of Week discounts. % Percentage The supported write format. Do not enter a monetary discount or use an imported flat-fee offer as a template for percentage editing. Booking Date Range — Start Date / End Date When the guest can book the offer. An end date cannot precede the start. Booking.com requires both dates or neither. For Expedia, use a complete intended window; blank dates are not a verified instruction to remove an existing remote window. Stay Date Range — Start Date / End Date Eligible stay dates. Both are required for enabled offers; Booking.com also requires them on a new disabled draft. The end cannot precede the start. Stay Date Range Blackouts Separately saved excluded stay ranges, available after first save. Existing Booking.com exclusions cannot be removed or shortened here once published. Rate Plans Select at least one applicable channel rate plan. Empty is not all. Existing imported selections can appear alongside current mapped products; investigate obsolete selections rather than assuming they are still sellable. All Rate Plans / All Room Types Bulk selection controls for their own lists. The selected count is draft form state until you save. Room Types is shown for Booking.com, not Expedia. Field reference: Booking.com Some labels currently display their compact names exactly as shown below. Field Meaning, choices and interactions PromoType Basic is the default; Last minute and Early booker add lead-time conditions. Create a separate offer to change the type of an existing channel promotion. Unsupported imported types must be managed in the extranet. PromoNonRefundable No by default. Yes changes the promotion's booking policy to non-refundable. PromoChannel Audience: Public or Subscribers . Blank omits the audience value; do not use blank as a guaranteed way to reset an existing audience to Public. PromoTime Lead time for Last minute or Early booker. Last minute accepts a nonnegative whole number. Early booker requires 1–365 days. Basic does not use this lead time. PromoTimeUnit PromoTimeUnitHour means hours; PromoTimeUnitDay means days. Last minute requires a unit. Early booker uses days only. PromoAdditionalDates Multiple additional stay dates, displayed as YYYY-MM-DD. Keep previously published dates unless you intentionally remove them through the channel extranet; removing them here is refused. PromoAdditionalDatesSelected Read-only imported date information, not a preview that confirms unsaved selections. Start Time / End Time Whole-hour booking-time restrictions. The hour choices run from midnight through 24:00 (end of day) ; the minute choice is 00 . Clearing both sends an empty time window. Recheck the intended time window at the channel. Stay Date Range — Days All weekdays start selected. Keep at least one selected weekday, and ensure the stay range actually contains one of those days. Min Nights Thru Nullable whole-number minimum stay from 0 to 7. Explicit zero is supported. Blank omits the minimum-stay value; do not assume blank removes an existing remote restriction. Room Types Select at least one channel room type. The offer applies to valid combinations of these rooms and your selected rate plans. To clear a Booking.com booking-date window, clear both booking dates rather than leaving one end populated. Confirm the resulting channel conditions after saving. Field reference: Expedia Field Meaning, choices and interactions Type Basic by default; Early booker , Multi-Night , or Same Day . An existing channel offer's type cannot be changed here. Discount Type Day of Week by default; Single or Multi-Night . This is separate from Type. An existing channel offer's discount type cannot be changed here. Mobile Only No by default; Yes restricts the offer to mobile users. Member Only No by default; Yes restricts the offer to members. Member Only - Addtl Discount Optional additional member discount for Single or Multi-Night discounts when Member Only = No . Not supported for Day of Week or Same Day offers. Blank omits the optional value, not a guaranteed remote-removal instruction. Confirm the intended member pricing with the channel before use. Multi Night - # Nights The discounted nth night, from 2 to 28, for a Multi-Night discount. For example, 3 targets the third night, not all three nights. Mutli-Night - Recurring The displayed label contains this spelling. Yes is the default and repeats the nth-night discount; No applies it without recurrence. SameDayBookingStartTime Same Day only: a time such as 15:00 , below 24:00. Leave it blank for other offer types. PromoSellStatus Read-only channel sell-status information. It is separate from the Enabled selection. Blank is not confirmation of bookability. PromoIsContracted Read-only channel contract status. Contracted offers cannot be edited here. Discount - Per Day Of Week For Day of Week discount type, complete every Monday–Sunday percentage from 0 to 100. Zero is allowed; blank is not zero. Leave the single Discount Amount blank. For Single or Multi-Night discounts, leave all weekday amounts blank. Min Nights / Max Nights Whole numbers from 1 to 28, with minimum no greater than maximum. Blank sends defaults of 1 and 28 respectively. Min Adv Booking Days / Max Adv Booking Days Nonnegative whole numbers, with minimum no greater than maximum. Blank sends defaults of 0 and 365 respectively, not an unlimited window. Booking Date Range Existing imported booking times are retained in the property's local time even though this form has no general time controls. When times are absent, supplied dates use 00:00 for the start and 23:59 for the end. Same Day checklist For Type → Same Day, use Discount Type → Single, matching booking and stay date windows, explicit 0 in both advance-booking fields, a valid SameDayBookingStartTime, and no additional member discount. The stay-window end must be no more than 364 days after its start. Blank advance bounds do not satisfy the explicit-zero requirement. Common problems - The form is visible but publishing is denied. Update - Rates alone can expose the form while publishing needs Channel Settings. Ask your administrator to verify that permission. Inspect saved local state before retrying; send support the exact error if access is already correct. - “Create a separate offer to change its type…” An existing offer's type or Expedia discount type was changed. Restore its original type. Create a distinct offer only when you deliberately need one, not to recover an uncertain submission. - “Each weekday percentage must be between 0 and 100.” Expedia Day of Week requires all seven values. Fill missing days, using zero where intended, and clear Discount Amount. For a single discount, select Single instead and leave weekday fields blank. - “Select at least one rate plan.” The product list is empty. Select the intended plans; for Booking.com also check rooms. If the correct products are missing, have the mapping checked rather than selecting unrelated products. - “A stay start and end date must be selected.” An enabled offer lacks one or both stay dates. Enter the intended complete range; also check selected Booking.com weekdays. - “Save deactivation separately from content changes…” Deactivation was mixed with edits. Reload and inspect current state, then deactivate without changing content. Do not assume the rejected action undid earlier saves. - The channel could not be contacted. The displayed copy may be stale. Check the same promotion in the extranet and retain the warning for support. Do not save merely to force a refresh. - An offer no longer exists on the channel, or the editor returns to the list. Verify the exact property and remote ID. Follow the list-refresh guide only when you intend to update stored list information; do not recreate the offer until its absence is established. - An offer changed, has an unconfirmed operation, or another operation is running. Stop repeat submissions. Compare the exact channel offer and contact support if the outcome is unclear. Reconciliation deliberately discards local edits; it is not a retry. - A read-only or contracted offer shows a Save control. The control is not evidence that the operation is supported. Follow the read-only explanation and use the extranet or support; do not try another Save button. For support, include the property, channel, offer name and remote ID if present, action time and time zone, and exact message. Do not send passwords, connection credentials, payment details or guest information. Related - Find and check your channel promotions
Find and manage channel contacts
Keep your property's channel market-manager details in one place, find the right person, and update or remove a local contact record. Before you start - Select the correct property. Contacts belong to that property, not to every property in your organization. - You need Channel Settings permission to add, change or delete contacts. Seeing an Edit or Delete link does not by itself confirm you can save changes. - Have the person's current business contact details ready. Use plain text, and do not store passwords, payment details or guest information in Notes. This is a local contact directory. Saving a contact does not update the channel's extranet, invite a user, send an email or add a reservation-notification recipient. Find a contact 1. Select the property in the property selector. 2. Open Admin → Home. 3. In the Channel Manager section of Settings, select Channel Contacts. 4. Leave Channel blank to see all contacts for the property, or select a channel to show only its contacts. Changing Channel reloads the list immediately; there is no separate Search button. Choose the blank option at the top of the selector to clear the filter. This changes what you see, not the contacts themselves. The list has Channel and Contact columns, with Edit and Delete beside each entry. Contact shows the name in last-name-first order, followed by any job title, phone number and email address. A blank Channel cell means the contact has no channel association. Notes are available in the editor, not in the list. An empty table means no saved contacts match this property and channel selection. It does not mean the channel has no market manager. Clear the filter and check the property before adding another entry. If an email address is present, its link opens your configured email application. Opening that link does not send a message from ChannelRUSH. Add a contact The editor saves only when you select Save. Changing fields or choosing a channel in this editor does not save immediately. 1. From Channel Contacts, select Add New. 2. Enter First Name, Last Name, or both. At least one name is required. 3. Enter the available Email, Phone Number and Job Title. 4. Select Channel if the contact belongs to a particular channel. 5. Add any useful business context in Notes. 6. Select Save. 7. Check the returned contact list and reopen the entry with Edit to confirm the saved details. Channel starts blank for a new contact even when you selected a channel in the list first. Select it explicitly if you want that association. Leaving it blank creates a property contact that is visible in the unfiltered list but not when you filter to a particular channel. New Channel Contact form with empty name, email, phone, job title, channel and notes fields, plus Save and Cancel controls The new-contact form starts empty. The list's channel filter is not copied into it. A successful Save returns you to the unfiltered Channel Contacts list with a success message. That confirms a local save, not that an email address works or a phone number is correct. Check those details against your source. Edit an existing contact 1. Open Channel Contacts for the correct property. 2. Select Edit beside the intended contact. 3. Check the existing name and channel before changing the details. 4. Change the relevant fields. 5. Select Save. 6. Reopen that contact from the returned list and verify the changes, including Notes. Changing Channel moves the contact's association to the selected channel. Choosing blank removes the association without deleting the contact. Clearing an optional text field removes its saved value when you save. Cancel from the editor returns to Settings without saving your edits. Use the Contacts breadcrumb to return to the contact list. If you changed fields, navigation may ask whether to discard those unsaved changes. Delete a contact Deletion removes the local contact record. It does not remove the property's channel connection or delete a user or contact in the channel's own system. There is no undo control on this page. 1. Find the record in Channel Contacts and verify its details with Edit if names are similar. 2. Select Delete beside the intended record, or select Delete in its editor. 3. Check the contact name on Delete Channel Contact. The confirmation asks, Are you sure you want to proceed with this delete? 4. Select Delete on the confirmation page only when you intend to remove that record. 5. Check the returned, unfiltered contact list to confirm the intended record is gone. Opening the confirmation page does not delete anything. Cancel returns to the contact editor; Contacts returns to the list. The confirmation identifies the contact by name, so return to Edit Contact first if you cannot distinguish duplicate names. Field reference Field What to enter and what it changes First Name The person's given name. Optional only when Last Name is filled in. Leading and trailing spaces are removed on save. Last Name The person's surname. Optional only when First Name is filled in. Leading and trailing spaces are removed. When both names are present, the list displays surname, then given name. Email Optional business email address, such as manager@example.com . Saved in lowercase with surrounding spaces removed. Check the spelling yourself; saving does not verify the address or send a confirmation. Phone Number Optional business number. Parentheses, hyphens and spaces are removed when the value is saved. Seven- and ten-character stored values are displayed with hyphens; other lengths are displayed without that automatic grouping. Include any needed country code and check the result after saving. Job Title Optional role, such as Market Manager. Displayed beneath the name in the list. Surrounding spaces are removed. Channel Optional association with one of this property's channels. Blank means no channel association. The list filter and this saved field are separate controls. Notes Optional multiline business context. Surrounding spaces are removed. Reopen Edit to read or verify notes; they are not shown in the contact list. All fields start blank on Add New. Only the name rule requires a value: First Name and Last Name cannot both be blank or contain only spaces. Common problems A contact is missing or the table is empty Check the selected property, then choose the blank Channel option. The record may be unassigned or assigned to a different channel. If it is still missing, confirm with a colleague whether it was added or deleted before creating a replacement. A channel is missing from the selector The selector lists channels associated with the current property. Check the property and ask your administrator to confirm its channel setup. Do not choose another channel merely to complete the form. Add New is missing, fields are disabled, or Save/Delete is refused Ask your administrator to check Channel Settings permission for the property. A demo login can browse contacts and use the list filter but cannot save or delete contacts. Do not treat a visible action link as proof of write access. Save returns to the editor Check that at least one name contains text and review any displayed message. Recheck the channel selection. If the form returns without a useful explanation, do not repeatedly submit it; contact support with the property, action time and error text, if any. Save or Delete gives an error or an uncertain result Return to the unfiltered Channel Contacts list for the same property and inspect the current record before retrying. An error after submission does not prove that nothing was saved. Repeating an uncertain Add New submission can create another contact rather than update the first one. If you cannot establish the result, ask support to check the property, channel, action and action time with time zone. Include the error text, but do not send passwords, payment details or unnecessary personal information. An old Edit/Delete link no longer opens Return through Admin → Home → Channel Contacts and select the current record. It may have been removed or the selected property may have changed. If a link from the current list still fails, report that page and the error to support rather than changing identifiers in the address.
Review channel opportunities and recommendations
Use Opportunity Center to review stored channel recommendations for a property, narrow the messages you see, and decide what needs investigation. These messages are not a live audit of every channel. A recommendation, an empty result or a recent refresh time does not by itself establish whether a room is currently bookable or a problem has been resolved. Before you start - Sign in with access to the property you want to review. You do not need Org Admin permission solely to view its opportunities. - To request a refresh, you need at least one of the permissions for updating rates, availability or restrictions. The public demo login can filter existing results but cannot submit Refresh Opportunities. - Check which system owns the rates or availability before acting on a suggestion. If your PMS supplies them, investigate there rather than entering a conflicting manual update. Open and filter opportunities Changing a dropdown applies the display filter immediately. There is no separate Search or Apply button. Refresh Opportunities is a different action: it requests new processing, not merely a filtered view. 1. Select the property in Channel Manager. 2. Open Channel Tools → Opportunity Center. You can also use Reports → Diagnostics → Opportunity Center. 3. Choose Channel, or leave All to include all matching channel and general messages. 4. Choose Room Type, or leave All to retain property-wide and channel-wide suggestions as well as room-specific ones. 5. Choose Level, or leave All to include every matching level. 6. After each selection, wait for the page to reload and check that the dropdown values and results match your selection. Opportunity Center filters for Booking.com and the Studio room type, including Last Refreshed and the separate Refresh Opportunities button Example from a demo property. The filters change what you see; they do not limit the scope of Refresh Opportunities. Selecting a room excludes messages that are not attached to a mapped room. A channel-wide recommendation can therefore disappear even when it is relevant to your property. Return Room Type to All before concluding that a channel has no recommendations. Read a recommendation Results are grouped under General or the channel name. Room-specific messages appear under the property room-type heading; the message may also show the channel's room name. Those names can differ—for example, your Studio may map to the channel's Single. Read the message and its Take Action guidance together. Some messages include a Click Here to Learn More link, which opens a separate tab. The destination depends on the message and may be the channel's own site. Review the destination and its requested action before making changes; opening a recommendation does not carry out its suggested fix. Booking.com opportunity grouped under Studio, showing the mapped channel room name Single, an availability warning, and Take Action guidance This captured message is an investigation prompt, not a live bookability check. The heading is shown exactly as it appeared in the demo. Availability-horizon messages An availability message may identify a last bookable date and a count of bookable days in the next year. This is calculated from stored inventory information. It does not establish that every date up to the stated date is available, that every rate plan is open, or that the channel has accepted a recent update. Before extending rates or availability: 1. Check the named channel and mapped room. 2. Inspect the affected dates in your source system and ChannelRUSH's rates-and-availability view. 3. Confirm whether a closure or limited booking horizon is intentional. 4. Use the appropriate inventory workflow only if a change is needed. The message can remain unchanged until opportunities are processed again. Its absence is not a substitute for checking the inventory itself. Close is not Resolve The Close control on a message is not a confirmation that its recommendation has been completed. Do not use it to track resolution or rely on it as a permanent dismissal. Record useful message details before closing; if a message disappears or returns, recheck the underlying issue rather than repeatedly closing it. Request updated opportunities Refresh Opportunities is property-wide. The selected Channel, Room Type and Level do not restrict it. It requests ChannelRUSH's local opportunity calculation and supported channel opportunity retrieval for the property's set-up connections. Not every configured channel provides remote recommendations. A refresh can replace the stored message set. Keep the relevant message text if you need it for investigation; this page is not a historical record of every recommendation. 1. Confirm the property and that you intend to request new opportunity processing. 2. Click Refresh Opportunities once. 3. Read the on-screen response. A refreshing message does not confirm that background processing completed or that a channel returned successfully. 4. Allow processing time, then reload the page with your browser. Browser reload rereads stored results; it does not request another refresh. 5. Reapply Room Type and Level if needed. The refresh redirect retains Channel but resets those two filters. 6. Compare the returned messages with the underlying inventory or channel information relevant to the issue. There is no guaranteed completion time shown by this workflow. Avoid repeated refresh requests solely because the message set has not changed. What Last Refreshed tells you Last Refreshed shows the recorded time of the property's general opportunity-processing pass, in your signed-in user's time zone. It is not a separate completion time for every channel, and it does not date each individual message. If no time is recorded, the label is absent. A newer time does not prove that every channel refreshed, that an inventory update was delivered, or that a recommendation was resolved. When you arrive from Portfolio Overview A link from Recent opportunity records in Portfolio Overview opens a narrower Opportunity Center selection. Instead of the normal filters and Refresh button, it shows: - Matching Portfolio opportunity records: the number of stored records matching the originating selection. It is not a count of distinct unresolved problems or a guarantee that the same number of message cards can be rendered. - The originating channel, message type, level, language and creation-time lower bound. Language-neutral records are also eligible; archived records are excluded. - Origin extracted and this read timestamps. This page reads the messages again, so they can differ from Portfolio's earlier count. - Return to Portfolio, when a return link is available. - Open Opportunity Center controls, which leaves the narrow Portfolio selection and opens the property's ordinary filters. Portfolio's creation window is not a stay-date filter. Ordinary Opportunity Center does not expose a date-range filter. Do not compare the two views as if they used the same selection. Field and control reference Field or control Meaning and behavior Example or caution Property Determines which property's stored opportunities you inspect. Check the property name above the filters. Channel Defaults to All . Choose one configured channel, or General for messages without a channel assignment. General does not include every locally calculated message; local suggestions can belong to a specific channel. Room Type Defaults to All . A selected property room matches messages through the channel-room mapping. Selecting Studio excludes roomless channel-wide suggestions. Level Defaults to All . Info , Warning and Critical each select that exact level. Warning does not also include Critical. All can include levels without their own dropdown choice. Last Refreshed General processing timestamp for the property, displayed in your user's time zone. Not proof that Booking.com or another individual channel completed a refresh. Channel and room headings Identify how messages are grouped; a channel room name may appear inside the message. Confirm the mapping when the property and channel use different names. Message and Take Action Explain a stored finding and its suggested next action. Read them as an investigation prompt, not proof of present channel state. Click Here to Learn More Optional message-specific link opening a separate tab. Available destinations and follow-up actions vary by message. Close A message-dismissal control, not a completed-task marker. Do not rely on permanent dismissal or use disappearance as evidence of resolution. Refresh Opportunities Requests a new opportunity-processing pass for the property and supported set-up channels. Display filters do not narrow the request. Requires update permission; unavailable to the public demo login. The ordinary view uses unarchived records for your current interface language or records with no language assignment. It has no selectable age window. Older messages can remain relevant—or stale—until the underlying collection is updated. This page has no dedicated Excel, CSV or clipboard export control; use the separate Portfolio or Custom Reports workflows where appropriate. Check the result After filtering, verify the property, selected values and channel/room headings together. No opportunities at the moment. means no message groups matched the current selection. It does not certify that the property has no distribution issues. After investigating or making a separate inventory/configuration change, check that change in its own workflow. Opportunity Center does not provide channel-acceptance confirmation for an inventory update. A missing message, a Close action, a refresh banner or a newer Last Refreshed time is not sufficient proof of success. Common problems Symptom What to check and safe next action No opportunities appear Verify the property, then return Channel, Room Type and Level to All . Language, stored data and room mappings also affect the results. If you expect a specific message and it remains absent, contact support with the channel, room and missing message details. A suggestion disappears after choosing a room It may be a property-wide or channel-wide message without a mapped room. Set Room Type to All . Escalate if a known room-specific message still cannot be found. A heading looks like AvailabilityBookableUntil-A-Title A readable message title was not supplied. Use the channel, room and message body for context; report the visible heading to support. Do not assume the unusual title changes the inventory state. Refresh is refused Check your update permissions. The public demo login is read-only for this action. Ask your administrator if an ordinary account needs the appropriate access; do not try a different route to bypass the restriction. Refresh says it is running, but the information is unchanged Reload the page rather than clicking Refresh repeatedly. The banner is not a completion receipt, and the general timestamp does not cover every channel. If the discrepancy persists, contact support with the request time and time zone. A dismissed message returns Treat the recommendation as unresolved until you verify the underlying issue. Dismissal is not a reliable resolution record, and refreshed messages can reappear. Portfolio's count differs from the visible messages Confirm that you followed the intended row. The page rereads stored records, and current channel/room mappings can affect which cards render. Return to Portfolio and follow a fresh link. Report persistent discrepancies with both views' timestamps and selection. A saved Portfolio link is rejected or the page fails to load Reopen it from the originating Portfolio report, or use Channel Tools → Opportunity Center . Do not repair selection parameters by hand. If the ordinary page also fails, send support the property, selected filters, action time and error text. When contacting support, include the property, channel, room type, selected filters, relevant message text and action time with its time zone. Do not send passwords, payment details or unnecessary guest information. Related guides - Compare property performance with Portfolio Overview - Custom Reports - Update rates, availability and restrictions in the calendar
Review reservations arriving on a selected date
Use Reservations - Arrivals to prepare an arrival list for one property and day, open reservation details, and copy or download the results. Before you start You need access to the property in ChannelRUSH. An Org Admin role is not required to view this report. Choose the property before opening Arrivals; this is not an organization-wide list. The report uses reservations already stored in ChannelRUSH. It does not retrieve missing bookings from a channel, check guests in, or send reservations to a PMS. An arrival in this list is a recorded stay date, not confirmation of actual check-in or successful delivery. Keep guest information private when copying, downloading or sharing a report. Use only approved recipients and storage locations. Open and run the arrival list 1. Select the property in the application header. 2. Open Reservations → Arrivals. You can also find Arrivals in the Reservations group under Reports. 3. Set Arrival Date using the date picker, or enter a date in the format shown. Check the prefilled day rather than assuming it is the property's current day, especially near midnight or when working across time zones. 4. Click View Arrivals. Changing the date alone does not load a new list. 5. Check the retained Arrival Date, the arrival count beside the button, and the results below before opening details or exporting. Arrival Date, View Arrivals and the loaded arrival count The date control loads one calendar day, not a date range. This example has no matching arrivals. Both /cm/reports/reservationsarrivals and /cm/reservations/arrivals open this report. Links can use either address. If you change properties after running a report, reopen Arrivals if needed and set the date again. Do not assume a property change retains the report or its previous criteria. Which reservations are included? - A reservation qualifies when at least one of its room stays arrives on the selected date. - Only the latest stored version for that property's channel reservation is considered. An older version is not a separate arrival. A modification can move a booking to another date; a latest Canceled version excludes it. - The count is a reservation count, not a room count or guest count. When results exist, the summary also breaks the reservation count down by channel. - The report has no separate Status, channel, room-type or multi-property selector. Use reservation search when you need to investigate a particular booking or its status. - Results are ordered by the booking contact's last name. Multi-room bookings need a detail check. The date selects the reservation, but the row summarizes all its room stays. Arrival is the earliest arrival in that reservation and Departure is the latest departure. The displayed Arrival can therefore be earlier than the selected day when different rooms arrive on different dates. The total is also for the reservation, not only the rooms arriving that day. These are stay dates, not receipt or processing timestamps. Changing the date does not ask when a booking was received. The list does not provide a last-synchronized timestamp or prove that ChannelRUSH has received every booking or amendment. Read the HTML columns Column What it means ID / Channel The channel's reservation ID, with the channel name below it. In HTML, click the ID to open that stored reservation version in a new tab. Guest Info The booking contact's formatted name. It is not a list of every room guest. A blank cell means that contact information is unavailable in this report. Total The reservation's after-tax total when available, otherwise its before-tax total, followed by the recorded currency. The column does not identify which tax basis was used. It is not an amount paid, an outstanding balance or a per-day charge. A missing amount is blank, not zero. Room Info Room-type names from the reservation, with the configured channel room name used as a fallback when necessary. Repeated entries with the same name are grouped and prefixed with their count. This summarizes room entries, not physical room assignments or guest occupancy. Arrival Earliest recorded room arrival in the reservation. Departure Latest recorded room departure in the reservation. To inspect a booking, use its ID in HTML. Check the rooms, dates, reservation version and currency in the detail view. The application may ask you to re-verify your password. Return to the original report tab when finished; opening details is not a check-in, modification or resend. When the list is empty An empty result shows 0 Arrivals and the table headings with no reservation rows. It does not need to display a separate “no results” banner. Arrivals report showing zero arrivals, output controls and the six HTML column headings Actual empty report. The blank table demonstrates the empty state, not populated booking details. Check the selected property and day first. Then use Reservations → Search to investigate a booking you expected to see. A changed arrival date or a later cancellation can explain its absence. If it is missing from ChannelRUSH entirely, reconcile with the source channel or PMS and contact support as needed. Repeatedly loading Arrivals does not import the missing reservation. Copy, download or open another view Load the date with View Arrivals before using any output control. Output links refer to the loaded report; an unsent edit in the date box is not confirmation that the export uses the new day. Copy to Clipboard In HTML, click Copy to Clipboard, then paste into your approved destination and inspect the text before sharing it. The button briefly shows Copied!. The copied output is a plain-text list, not a spreadsheet table. It includes the report title, selected date, arrival count and each reservation's ID, channel, available booking contact and total, arrival/departure dates and room information. For an empty list, it includes No arrivals for this date. The copied total does not include the currency code, and the copy does not identify the property. Add that context yourself from the report and reservation details. If nothing pastes, check browser clipboard permissions or use CSV instead; a button acknowledgement alone is not a check of the pasted content. Download CSV Click CSV under Download. This downloads the loaded arrival list without first switching to Excel. The file is named for the property and Reservations; rename it to include the arrival date if you need to retain several reports. If there are no matching arrivals, the download is an empty file with no header row. Check 0 Arrivals on the report before treating that file as a failed export. Excel view and Save As 1. Click Excel beside View. This opens a read-only spreadsheet in the current report tab; it does not immediately download an Excel file. 2. Open the spreadsheet's File → Save As menu. 3. Choose a format: Microsoft Excel (.xlsx), Microsoft Excel 97-2003 (.xls), Comma-separated values (.csv) or PDF Document (.pdf). 4. In Save As, check or enter the File Name, then click Save. Use a name containing the property and selected date. 5. Open the downloaded file and check its contents. Saving a file does not change the reservations. Excel view File menu with Save As formats The File menu in Excel view. The spreadsheet behind it is empty in this example. Use HTML to return to the ordinary list. An empty Excel report can show a blank worksheet without field headings. If a spreadsheet reservation link does not open the expected details, return to HTML and use the reservation ID there. The File menu also exposes Print. Inspect the print preview and page coverage before printing; do not assume a visible worksheet area represents every result. CSV is the more direct option when you need the report's row data rather than a formatted worksheet. Spreadsheet and CSV field reference The spreadsheet data and direct CSV use these field names when rows are present. They are different from the HTML headings. Field Contents and checks Channel Channel name. ReservationID The export value combines the channel reservation ID, property ID and stored reservation-version ID, separated by @ . It is not necessarily the plain channel confirmation number shown in HTML. Use HTML or reservation details to obtain the channel ID alone. GuestInfo Booking contact's formatted name, or blank when unavailable. Total After-tax amount when available, otherwise before-tax, shown to two decimal places; blank when neither exists. No currency field accompanies it. Keep the currency and tax-basis limitations in mind before combining or comparing amounts. RoomInfo Room-type names and repeated-name counts. Multiple entries can occupy separate lines within one exported cell. ArrivalDate Earliest arrival in the whole reservation, formatted as a short date. DepartureDate Latest departure in the whole reservation, formatted as a short date. Check the date and decimal format when importing a file into another application; do not assume ISO dates or a particular day/month order. Preserve reservation identifiers as text. The export does not add a reservation-status, currency, selected-report-date or delivery-status column. Spreadsheet Save As exports the worksheet; direct CSV is generated from the report rows, so do not assume the two files retain identical formatting or hyperlinks. New window Click New window to open the loaded report in a separate tab or window without the main application navigation. The original report stays open. The new view retains the loaded query, including an explicitly selected date; check that date there before using it. Choose a date explicitly before opening a copy you intend to keep across midnight. Check the result and resolve differences A successful View Arrivals reload leaves the chosen date visible and shows either matching reservation rows or 0 Arrivals. Compare the property, day and a sample booking's details before relying on the list for front-office work. A downloaded or copied list is a snapshot; reload the report and export again when you need a later view of stored reservations. Symptom Safe next action The date changed in the box but the report still looks unchanged Click View Arrivals and check the retained date after reload. Do this before copying, changing view or downloading. You cannot open the expected property or report Confirm the selected property and ask an Org Admin to check your property access. Do not change IDs in a shared link to work around access restrictions. An expected arrival is absent Check the property's date, latest reservation version and cancellation status in reservation search. Reconcile missing bookings with the source; this report cannot repair a feed or prove PMS delivery. A row's Arrival is not the selected day Open its details and check all room stays. Another room in the same reservation can arrive on the selected day. The name, room or amount is blank or unexpected Check the recorded reservation details. A blank value is not proof of zero charges, no guests or no rooms. The file is empty Compare with the loaded arrival count. Zero-row CSV has no headers, and zero-row Excel is a blank sheet. If HTML has rows but the same-date download does not, retain the property/date and error details for support. A copied amount lacks context or a spreadsheet link fails Check currency and the plain channel reservation ID in HTML/details. Do not treat exported internal identifiers as a new booking or resend instruction. If a discrepancy remains, contact support with the property, selected arrival date, source channel, action time and time zone, and exact error text. Provide a reservation reference only through an approved support channel when needed. Do not send passwords, payment details or unnecessary guest information. Related - Review reservation details - Read daily occupancy, arrivals, departures and stayovers - Create, share and schedule saved reports — a separate workflow if you need scheduled report email; Arrivals itself has no email-schedule control.