Set Little Hotelier minimum stay and CTA with an AI agent

1. Open Front Desk > Inventory and switch the grid to All Fields so Min/Max Stay, CTA and CTD show next to availability and rates.
2. Click Bulk Update, choose the dates under When? and the weekdays under Which days?, and tick every room rate under Which room rates?
3. Under What changes? set Min Stay, tick CTA or CTD, or tick Close Channels or Close Website, then click Update.
4. Look for dashes in the grid: a dash means that channel does not take the restriction, so it has to be set in the channel's extranet.
5. To stop one channel only, go to My Apps > Channel Manager > Inventory > Bulk Update and use Stop Sell instead of Close Channels.
6. Restrictions set weeks ahead stay on after the event, and a minimum stay on a lone free night between two bookings keeps that room empty.

Set a 2-night minimum stay for arrivals on 30 and 31 Dec, close arrivals on 1 Jan, and warn me about nights that would be left empty.

1. 01

   Read what is set now

   The agent calls get_inventory for the event dates and lists the current min stay, CTA, CTD and closed flags per room rate, so it neither stacks a new rule on an old one nor undoes one you set on purpose.

2. 02

   Check what is already sold

   list_reservations with date_type check_in around the event shows which nights are taken. A single free night between two bookings is flagged instead of getting a minimum stay no guest could meet.

3. 03

   Choose the right restriction

   Minimum stay goes on the arrival nights only, and CTA on the night with no check-ins. Channels are closed only if you asked to stop selling, and the agent warns when a per-channel Stop Sell in Channel Manager would clash with Close Channels.

4. 04

   Apply per group of room rates

   update_restrictions runs once for each set of room rates that share the same rule and dates, after you confirm. Rates where a channel shows a dash are reported so you can set that channel in its extranet.

5. 05

   Plan when the rule comes off

   If you give a cut-off ("drop it 10 days before arrival"), a scheduled run checks the nights inside that window and removes a min stay only where the night is still unsold.

New Year 30 Dec to 2 Jan, 4 room rates
Min stay 2 on 30 and 31 Dec arrivals: Double, Twin, Family and Single, Standard Rate
CTA on 1 Jan for all 4 room rates
Not sent to Hostelworld: dash for min stay, set it in the Hostelworld extranet
Left alone: Close Channels already on for Family Room on 31 Dec
Watch: Double Room has 1 room free on 30 Dec only; a 2-night minimum may leave it empty

• Little Hotelier's release period (1 to 180 days) is set on the room rate in Front Desk > Setup > Property & Room Settings > Rooms & Rates, cannot be removed for single dates and shows as a stop sell in the grid.
• Close Channels in Little Hotelier Front Desk and per-channel Stop Sells in Channel Manager cannot be used together, and removing the Close Channels setting from Front Desk takes a request to support.
• The Little Hotelier Channel Manager inventory grid shows a stop sell on every channel with an orange background and a stop sell on only some channels with a lighter orange background.
• A room type's availability threshold in Little Hotelier applies Close channels and Close website by itself once the rooms left reach that number.
• A dash in a Little Hotelier inventory cell means the channel does not support that update type, so that restriction has to be set in the channel's extranet.

update_restrictions asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: Little Hotelier Help: inventory grid and Bulk Update · Little Hotelier Help: Release period · Little Hotelier Help: Stop sells for specific channels · Little Hotelier Help: Room closures and availability threshold

curl https://cotlet.dev/api/v1/little-hotelier/update_restrictions \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"room_rate_ids":["rr_20417"],"from":"2026-12-30","to":"2026-12-31","restrictions":{"min_stay":2}}'

{
  "status": "updated",
  "room_rates": 1,
  "dates": 4,
  "restrictions": {
    "min_stay": 2
  },
  "skipped": []
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is little-hotelier_update_restrictions. Example data.

• Check Little Hotelier arrivals and unpaid balances daily
• Bulk update Little Hotelier rates with an AI agent
• Reply to Little Hotelier guest messages with an AI agent
• Little Hotelier API and MCP server: every tool
• All use cases