Limit Rooms Per OTA and Set a Markup for Each One
Yes, you can limit how many rooms one OTA sells without touching your hotel inventory. In Frontdesko, open Rooms, then OTA Inventory, and add a per-OTA limit: a maximum, rooms held back, or a closed OTA. Rates, then OTA Pricing, adds a markup per OTA on top of one set of base rates. Both need the paid channel manager.
By the Frontdesko team · Last updated: November 18, 2026
What can you limit on one OTA?
The channel manager applies the rule to the room count it sends to that OTA. Your PMS inventory does not change, and when the hotel really fills, the OTA closes anyway, because a limit can only lower what an OTA sees, never raise it. Three rule types are available:
Worked example, not a customer result: with 10 Deluxe rooms and 8 still free, a max of 3 shows 3 on that OTA, and a hold-back of 2 shows 6. With only 2 left, the max rule shows 2.
How do you add a per-OTA limit?
Open Rooms, then the OTA Inventory tab. The Rooms offered per OTA panel sits above the per-date grid, which still applies to every OTA at once.
- Click Add per-OTA limit and choose what the OTA should see: max rooms, hold back rooms, or close.
- Enter the number of rooms (not needed for Close OTA) and tick the OTAs it applies to. The list comes from your connected channels.
- Tick the room types. A room type that is not mapped to the channel manager is labelled not mapped, and saving a rule for it fails.
- Set the From date and an optional To date (leave it empty to keep the rule running), the days of the week, and an optional name such as Agoda max 3 Deluxe.
- Click Save and apply. The rule shows a status: Live on OTA, Pending or Failed. A failed rule has a retry button, and any rule can be paused, edited or deleted. Deleting one sends the OTA your full availability again.
Per-OTA limits work on Channex connections. If your hotel is on a different connection, the screen says so and you can ask support to move it.
How do per-OTA markups work?
Keep one set of rates in Frontdesko and let the channel manager adjust what each OTA receives. Open Rates, then OTA Pricing, click Add OTA, pick the channel and choose Percent or Fixed amount. A positive value raises the OTA price and a negative one lowers it. For example, +10% on one OTA to help cover its commission.
- The markup applies to every rate plan and date, including every future edit, so you only ever edit your own base price.
- Each row shows Applied or Failed after you click Save and apply.
- Removing a row sends your plain rates to that OTA again. Fixed amounts are not offered on Aiosell connections, which take percentages only.
Check the parity terms in each OTA contract before you add a markup. Some require the same price as your direct site. The screen also lists how rate plans, calendar overrides and the markup combine; for setting base rates quickly see copying rates forward in the rate calendar.
Which rate plans each OTA is priced from
The markup is applied to a rate plan, so it matters which plans an OTA actually sells. OTA Pricing has a Rate plans the OTAs are priced from card that lists, per OTA, the Frontdesko plans its prices are built from, and those plans carry an OTA base badge in Rate Plans and on the rate calendar. Each markup shows which plans it applies to.
OTA Pricing also warns about OTA rates Frontdesko is not pricing: a plan that is switched off (its OTA prices are frozen at the last ones sent), a plan set not to sell on OTAs, or a rate created directly in the channel manager. If an OTA sent bookings in the last 30 days on a rate that is not linked to a plan, the warning says how many, because those rates get no price updates. To sell a Non-refundable rate that follows BAR automatically, see derived rate plans.
How fast do changes reach the OTAs?
Both screens show a sync status line: how many changes are on the way, when the last push happened, and any that failed. Edits leave Frontdesko within about a minute (the queue is checked every 30 seconds), and each OTA then takes seconds to a few minutes to show them. Failed changes notify Frontdesko support.
What does it cost?
The PMS, booking engine, guest app and POS are free forever with unlimited rooms. Per-OTA limits and markups are part of the channel manager, a paid plan together with the AI assistant: $35 a month for 0-10 rooms, $42 for 11-30 rooms and $54 for 31-50 rooms. See pricing and the channel manager page. Rooms you hold back from OTAs are best sold on your own booking engine; for the cost side see direct booking versus OTA costs. To connect channels first, see OTA connections.
Frequently Asked Questions
Can I limit how many rooms Booking.com can sell?
Yes. Add a per-OTA limit under Rooms, then OTA Inventory, choose Max rooms on OTA, pick Booking.com and the room types, and set the number. Booking.com never sees more than that, and sees less when your real availability is lower.
Does a per-OTA limit change my hotel inventory?
No. The channel manager applies the rule to what it sends to that OTA. Your PMS inventory and rates stay as they are, and the other OTAs and your booking engine keep selling normally.
What is the difference between max rooms and hold back rooms?
Max rooms caps the OTA at a fixed number. Hold back rooms subtracts a number from your real availability, so the OTA count moves with your inventory while the last rooms stay for direct guests.
Can I close one OTA for certain dates only?
Yes. Choose Close OTA, tick the OTA and room types, and set the date range and days of the week. Other OTAs and your own website keep selling those dates.
Can I add a markup for each OTA?
Yes. Under Rates, then OTA Pricing, add the OTA and a percent or fixed amount. The channel manager adds it on top of your base rates for every rate plan and date. Aiosell connections take percentages only.
How quickly do limits and markups reach the OTAs?
Changes leave Frontdesko within about a minute, and each OTA then shows them in seconds to a few minutes. The OTA Inventory and OTA Pricing screens show pending changes and the time of the last push.
What happens if a rule fails to apply?
It is saved with the status Failed and the error shown on hover. You can retry it from the rules list, and failed changes in the sync queue notify Frontdesko support.
Is this free?
No. It belongs to the channel manager, a paid plan with the AI assistant at $35, $42 or $54 a month by room band. The PMS and booking engine stay free forever.
Control what each OTA can sell
Free PMS and booking engine with unlimited rooms. Add the channel manager when you connect your OTAs.
Start Live DemoRelated guides
More on channels and direct bookings
Channel Manager
Two-way sync with your OTAs.
OTA Connections
Connecting your channels.
Booking Engine
Sell held-back rooms direct.
Copy Rates Forward
Set base rates quickly.
Direct vs OTA Costs
What commission really costs.
Out of Order Rooms
Dated blocks close rooms on every OTA.