Blog›Connectivity

Creating and Deleting Rate Plans Safely: What Breaks on Channels When You Delete

Deleting a rate plan can silently break existing reservations and channel mappings if you don't check what's still attached to it first.

The Prime Host Partners team20 Nov 2026 · 7 min read

Creating a rate plan is usually the easy part. Deleting one safely is where properties run into trouble, because a rate plan that looks unused in your PMS can still have live reservations, channel mappings or pending commission calculations attached to it that a simple delete doesn't account for.

Full guide on this topic
Why deleting a rate plan is riskier than creating one

Creating a rate plan only adds a new option — nothing that already exists depends on it. Deleting one removes something that may already be referenced by existing reservations, by a mapping on one or more connected channels, and sometimes by a commission or payout record tied to a past booking. If any of those references aren't cleanly resolved first, the delete can leave a reservation pointing at something that no longer exists, or leave a channel still configured to sell a rate plan your PMS has already removed.

The failure mode is rarely immediate. It tends to show up later, when a channel tries to sync an update against a rate plan ID that's gone, or when a report tries to pull historical data from a reservation whose rate plan reference is now broken.

What's commonly still attached to a rate plan you want to remove

Future reservations already booked under that rate plan are the most obvious risk — deleting the plan doesn't cancel them, but it can orphan the record of what they were actually booked under. Channel mappings are the second risk: if the rate plan is still mapped to Booking.com, Airbnb or another channel, that channel may still be configured to sell it even after you've deleted it on your side, which creates a mismatch rather than simply closing it. Historical commission and payout records tied to past bookings on that rate plan are the third, quieter risk, since reporting that relies on the rate plan still existing can break.

Check these before deleting a rate plan
1Future reservations booked under itThese don't disappear with the rate plan — the reference they rely on does.
2Active channel mappingsA channel can still be configured to sell a rate plan you've already removed on your side.
3Historical records tied to past bookingsReports and commission calculations referencing that rate plan can break if it's removed outright.
The safer order to do it in

Close the rate plan to new sales first, on every channel it's mapped to, and confirm each extranet actually reflects it as closed rather than assuming the push worked. Check for any remaining future reservations under that rate plan and either migrate them to a replacement plan or let them run out naturally. Only once no channel is actively selling it and no future reservation depends on it should the rate plan itself be deleted, rather than deleting it first and discovering what was attached to it afterward.

A rate plan is rarely as isolated as it looks in the list — the delete button doesn't know what's still pointing at it.
Doing it without breaking anything downstream
Close the rate plan to new sales on every connected channel before deleting anything.
Confirm in each channel's extranet that the closure actually landed, not just that you clicked save.
Check for future reservations still booked under that rate plan and migrate or let them run out.
Wait until no channel is actively selling the rate plan and no future booking depends on it before deleting.
Keep a note of the rate plan's old settings somewhere, in case a historical report needs to reference what it used to be.
How Prime Host stops this from happening again

Read-back verification applies when a rate plan is closed or changed, not just when it's created — the system reads back what each channel actually stored and compares it to what was intended, so a channel still selling a rate plan you believe is closed shows up rather than going unnoticed. Activity history also keeps a record of rate plan changes, including closures and deletions, across four hundred days, so if something does break downstream later, there's a trail to trace it back to. You can see both in the public demo at try.primehostpartners.com without signing up.

Frequently asked
Can I delete a rate plan that still has future reservations under it?
You can, but it's risky — the reservations don't cancel, but the reference they rely on can break. Migrate or let them run out before deleting.
Will a channel automatically stop selling a rate plan I deleted?
Not reliably. Close it to new sales on each connected channel first and confirm the closure in the extranet, rather than assuming deletion on your side closes it everywhere.
Is it safer to deactivate a rate plan instead of deleting it?
Often yes, if your PMS supports deactivation — it preserves historical references while still removing it from new sales, which avoids most of the downstream risk of an outright delete.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service