A hotel stop sale is easy to acknowledge and harder to finish. Someone reads the supplier's email, changes a setting and returns to the booking they were handling. Meanwhile, another colleague may still have a quote open for the affected dates. Your process needs to follow the instruction through to the places where that room can actually be sold.

For a small tour operator, this is a handover problem as much as a software task. One person needs to know what has closed, another needs to understand which enquiries are affected and somebody must own the reopening decision. A shared inbox alone won't settle those questions. Give each notice a record that stays open until the required checks are complete.

Turn the supplier notice into a precise instruction

Record the property reference, affected room type and rate plan before changing availability. Copy the relevant dates exactly and clarify whether the instruction concerns arrivals or any stay touching those dates. A hotel name without its supplier reference can be ambiguous when you buy the same property through several sources. Keep the original notice attached to the working record.

Mews' close-restriction documentation illustrates why the distinction matters. A closed-to-arrival rule concerns when the stay begins, while its stop-sell rule concerns nights within the restricted period. Those settings can produce different results for the same holiday. Ask the supplier to clarify an ambiguous notice before translating it into your system's controls.

Separate an immediate stop sale from a routine allocation release. The first is an instruction to restrict selling; the second follows the agreed treatment of unused inventory. Our guide to managing direct hotel rates covers release periods and contract loading. Keep that agreement available, but use the stop-sale record to document this particular change and its scope.

Give the closure an owner and a visible status

Name the person making the change and the colleague covering their absence. Use plain statuses such as received, clarification needed, applied and checked. Record when the instruction arrived, when it took effect and who confirmed the result. A message saying "done" should point to those details rather than replace them.

If an instruction arrives outside normal hours, your team needs an agreed escalation route. Decide which notices require immediate attention and who can restrict the affected sales while a detail is checked. That is an operational decision to make with your suppliers and platform provider. It should not depend on whichever adviser happens to glance at their phone.

Keep the action proportionate to the notice. Closing every room at a property may remove legitimate options when only one allocation is affected. Equally, changing a single rate can leave another sale route open if both draw on the same restricted stock. Trace the instruction to the inventory you control before deciding which settings need changing.

Check the selling routes individually

List where the affected product is sold, including the public website, agent portal and any manual quotation process. Apply the appropriate closure in each relevant place or confirm how your central setting reaches it. Record any route that needs a separate action. Avoid treating the appearance of a saved setting as proof that every channel has received it.

Cloudbeds' allotment guidance makes one useful scope distinction: its distribution allotment setting affects connected channels rather than direct booking sources. That control has a defined reach, so don't assume a similar setting in your system affects every selling route. Ask the same scope question about the controls your business uses. Document the answer beside the selling routes.

Run searches that should now be unavailable and nearby searches that should remain open. In a fictional test, a closure affects a particular room for the nights of 12 and 13 November. Check a stay crossing those nights as well as one entirely outside them, using the supplier's actual restriction scope. These are illustrative dates, not a live hotel instruction.

Separate existing bookings from unfinished sales

Review confirmed reservations, supplier requests awaiting a response and quotes that have not become bookings. Those states need different treatment. Don't cancel a confirmed reservation simply because new sales have stopped. Ask the supplier explicitly whether the notice affects existing bookings, then record any action against the relevant references.

Temporary holds need a clear answer too. Establish whether a hold survives the closure and what happens if the customer completes checkout during the change. That answer depends on the supplier agreement and the system's behaviour. Give your technology provider a concrete scenario to demonstrate rather than accepting a general assurance about availability.

Travelgenix's Luna Contracting pricing and inventory page describes inventory holds, room closures and a search or price-check view. Use a demonstration to establish how those controls work for your directly contracted accommodation. The documented controls do not replace checking a supplier notice or inventory maintained elsewhere. Keep the observed result with your closure record.

Reopen only the inventory that has been released

Treat reopening as a new authorised action. Keep the supplier's confirmation, the scope of the release and the time it becomes effective. Check whether any room types or dates remain closed. Reversing every restriction from the earlier notice can be wrong when the hotel reopens only part of its stock.

Repeat the selling-route checks after the change and tell the advisers handling affected enquiries. Where the available offer has changed, they should recheck the details before contacting customers. Close the operational record only when the reopened product can be sold as intended and any exceptions have an owner. Take your next supplier notice and follow it all the way through this process, including the eventual decision to reopen.