Mapping a New Rate Type: Four Checks Before You Publish

A new rate type is easy to create and easy to publish to the wrong listings. Four checks sit between the wizard and a booking at a price you did not set.

Last updated: October 9, 2026

A new rate type is easy to create and easy to publish to the wrong listings. Four checks sit between the wizard and a booking at a price you didn't set. This guide runs them in order: what the rate type controls, which listings it should attach to, how to sequence the work, and how to confirm the change reached the right channel. Skip one, and the mistake won't show up until a guest has already booked.

Key Takeaways

• A rate type is a rule, not a price. It decides how a rate is calculated and where it applies, so a wrong attachment reaches further than a single wrong rate.
• Check the listings before the numbers. The most common accident is publishing a sound rate type to listings it was never meant for.
• Run the four checks in order. Controls, listings, dates, then confirmation. Each is quick, and each catches a different mistake.
• Confirm on the channel, not in the wizard. What the wizard shows and what a channel receives are two separate facts.
• One calendar shows each channel's own rate and status. That's where you see whether the change landed where you meant it to.

What a rate type actually controls

A rate type is a set of rules that produces prices. It holds the base rate, the adjustments, the length-of-stay conditions and the like. It doesn't hold one number. It holds the logic that makes numbers.

That distinction is what makes a new rate type worth a check. Change a single rate, and the blast radius is one listing on one night. Misconfigure a rate type and attach it widely, and the error repeats across every night it touches and every listing it's mapped to.

A rate type also decides which listings it applies to. A weekend type, a long-stay type, a low-season type: each is a rule meant for a certain set of listings and a certain window. The rule and its reach are set in the same place, which is exactly why the listing check comes before the number check.

There's one more layer. The same rule can behave differently once it's mapped to a channel. A condition that reads clearly inside the tool may land differently on a booking page. That's the reason the final check isn't in the wizard at all, and why confirming on the channel is a step of its own.

Keep the whole thing in proportion. A rate type isn't complicated to build, and that's the trap. The ease of creating one is what makes it easy to attach it to the wrong listings and publish.

Think of it the way you'd think of a template. A template saves you time on every document, and it also spreads a single typo across all of them. A rate type works the same way, in both directions.

Which listings it should attach to

Before you look at a single number, decide which listings deserve this rate type. Write the list down, then read it back against what the wizard has selected.

The common accident is a rate type meant for one unit being published across a whole group. A weekend rule built for a city apartment gets attached to a beach house, and the beach house now prices its Saturdays like the city. Nothing in the wizard flags it, because both listings were plausible selections to the tool.

Group your listings deliberately. By building, by neighbourhood, or by how they sell. A rate type usually belongs to one group, not to everything you own. When you can name the group in a sentence, you'll spot a listing that doesn't belong in it.

Then check the exclusions. If a listing shouldn't carry the rate type, make sure it isn't selected, and note why beside it. A short note next to each exclusion saves the next person from re-adding it by mistake, and it turns a silent decision into a visible one.

Two details are easy to miss at this step. A listing added since you last built a rate type may not sit in the group you're picturing, and a listing you renamed may now read as a different one. Scan the full list, not the part you remember.

A final pass helps: read the selected list out loud, listing by listing. If a name surprises you, that's the one to look at again. Surprise is a poor thing to feel for the first time when a guest quotes a price back to you.

Sequencing the four checks

Run the checks in the order that catches the cheapest mistake first. Each is quick, and stopping at any of them is better than publishing blind.

First, confirm what the rate type controls: the base, the adjustments and the conditions. Second, confirm the listings. Third, confirm the dates the rule applies to, so a weekend type doesn't quietly run every day of the week. Fourth, confirm the change once it's out, on the channel rather than in the tool.

The order matters because each check rules out a different class of error. If the controls are wrong, the listings don't matter yet. If the listings are wrong, the numbers don't matter yet. Checking in sequence keeps you from polishing a detail while a larger mistake sits underneath it.

Keep the pass short. Four checks, a few minutes, and a note of what you changed. A rate type published carefully once is cheaper than one republished every time a guest queries a price.

It also helps to run the checks at a calm moment rather than under pressure. A new rate type is often created in a hurry, before a weekend or a holiday, and that's when a listing gets attached without a second look. Doing the four checks as a habit removes the rush from the moment it matters most.

Confirming the change reached the right channel

The wizard confirms what you set. It doesn't confirm what a channel received. Those are two separate facts, and only one of them is visible from where you're standing.

After publishing, open each connected channel and find the listing that should carry the new rate type. Check that the rate it now shows matches what you intended, and that a listing you excluded still shows the old one. Both halves matter: a change that reached the right listing and a change that skipped the wrong one are equally part of the confirmation.

LOCALSBNB connects directly to four OTAs: Airbnb, Booking.com, Agoda and Trip.com. Because the calendar shows each connected channel's own source price and status, you can compare what every channel is showing without opening four separate logins. That's the fastest way to see whether a rate type landed where you meant it to, and where it didn't.

If a channel shows something unexpected, don't republish on top of it. Fix the mapping first, then confirm again. Layering a second change over a problem tends to hide the original mistake rather than solve it, and a buried mistake is the one that resurfaces with a guest attached.

Once the rate type is confirmed, add a line to a running note: the type, the listings it covers, and the date you published it. When a guest later asks about a price, that note tells you which rule produced it, and whether the answer is right. It also gives you something to check against the next time you change the same rule.

See the checks on your own listings at localsbnb.com.

FAQ

Where do most rate-type mistakes happen?

At the listing step, most often. The controls are usually set with care. The attachment is where a rule quietly reaches a listing it was never meant for.

How do I know a rate type reached the right channel?

Look at the channel, not the wizard. Each channel shows its own source price and status, and comparing those against what you set is the only real confirmation.

What if two rate types apply to the same night?

That depends on the rules you've set and on the channel. Decide which one should win before you publish, and confirm on the channel afterward.

A new rate type is a small piece of logic with a wide reach. Check the controls, the listings, the dates and the channel, in that order, and the wide reach works for you instead of against you. A few minutes of checks keeps a price you never set off a guest's booking. When you're ready to see each channel's own rate and status in one place, start at localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.