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.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaUVDIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--ae98e08be63375eb9b9b13b4331f5dc76eea74f5/manual-inventory-updates-filters.png)

*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.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaUFDIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--9178deae87f0b50c2226488c04c0942c11971f01/manual-inventory-updates-request-card.png)

*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](https://help.channelrush.com/hc/channelrush/articles/update-status) 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.