Review recorded restrictions with Restriction Coverage

Marcus Cole

Marcus Cole

Last updated on Nov 18, 2026

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