Agoda Rate Types and What Each One Maps To in a Channel Manager
Channel Management

Agoda Rate Types and What Each One Maps To in a Channel Manager

Localsbnb 内容团队2026年9月25日阅读约 8 分钟

Agoda sells more than one kind of rate, and each kind carries its own conditions. A rate plan can be mapped perfectly and still be the wrong one, and you won't find out until a guest disputes a cancellation.

Screenshot of the LOCALSBNB rate plans screen with a 'One rate, many names' headline overlay, listing the rate plan rows and their channel mappings
One rate plan can feed several rate types, and each type carries its own conditions.

Agoda sells more than one kind of rate. If two of them map onto the same plan, you will not notice until the first disagreement over a cancellation.

Last updated: September 25, 2026

A rate type isn't a price. It's a price plus a bundle of conditions — when the guest can walk away, whether breakfast comes with it, how many people the quoted number covers. Map your rate plan to the wrong type and the number still travels. What breaks is everything attached to it, and that only shows up when somebody asks for their money back.

This guide walks the shapes those rate types usually take, separates mapping from matching, and sets out the three choices that decide how cancellations and breakfast land. Names and availability differ by property and market, so treat the list as shapes rather than product names — your own partner portal and that platform's current terms are what apply.

Key Takeaways

  • A rate type is conditions, not a price. The number travels either way; the terms attached to it are what go wrong.
  • Two types can share one plan. That's the setup that looks fine and fails at the first dispute.
  • Mapped isn't matched. A technically valid mapping can carry cancellation terms you never sold.
  • Breakfast is a fork. It's either its own rate type or an add-on on an existing one, and the two behave differently on refunds.
  • Drift is weekly, not annual. Rate types get added by default; check what's live, not what you set up.

The rate types a new host is offered at sign-up, and which are genuinely optional

Sign-up tends to present more rate types than a host intends to sell. Here are the shapes they usually take. I'm describing the shape because that's what matters for mapping — the label on your screen will be whatever your market uses.

A standard or flexible rate. The default, with the most forgiving cancellation terms. Every property has one, and it's the one everything else is priced against.

A non-refundable rate. Cheaper, and the discount is paid for with the guest's right to cancel. This one is where most mismatches live, because the price difference is obvious and the conditions aren't.

A breakfast-included rate. Either a separate rate type at a higher price, or breakfast bolted onto an existing one. Those are genuinely different arrangements, and the second one is easy to forget you've switched on.

Packages and promotions. Bundled offers the platform runs — a stay-plus-something deal, a seasonal campaign. These come and go, and they overlay whatever rate you pushed.

Member-only or closed-group rates. Shown to a subset of users. Optional, and worth skipping until you've got the first four stable.

Long-stay rates. Triggered by length of stay rather than by date. Genuinely optional unless you actively want that segment.

Which of these are actually optional? The packaged and member-only ones, mostly — you can decline them and lose very little. The standard rate isn't optional, and the non-refundable one isn't really either: if you don't offer it, the platform will still show competitors who do. What shouldn't happen is drifting into six live rate types because each one was switched on separately and never reviewed together.

Why a mapped rate plan is not the same thing as a matched rate type

Mapping is a technical statement: this plan on my side is connected to that rate type on yours. It's binary. It's either linked or it isn't, and the connection screen will happily tell you it's linked.

Matching is a semantic question, and nobody's screen answers it. Do the conditions on both sides agree? Does the cancellation deadline on the channel equal the one on your plan? Does the refund window start at the same moment? Is breakfast quoted the same way? Does the headline number cover the same number of guests?

Here's the failure. Your "flexible" plan gets mapped to a non-refundable rate type, because the names lined up and nobody read the conditions. The price pushes fine. A guest books it, and they've bought a non-refundable stay at a price that implied flexibility. When they cancel on day three, they're quoting terms you never agreed to — and from their side, quite reasonably, because those were the terms on the page they bought from.

The reverse version is quieter but more expensive. Two rate types share one rate plan, so a single number feeds both. One of them now carries conditions that were never written for it. You won't see it. The guest will, on the confirmation page, and by then the only fix is a goodwill refund.

Card: the rate type shapes a channel offers and whether each one should be mapped or skipped
The label on your screen is a name; the shape underneath is what decides how a cancellation lands.
Card: the six checks that catch rate type drift before a guest finds it
Compare intent against what's live, on the same date, every week.

The three mapping choices that decide how cancellations and breakfast land

Which rate type carries your cancellation policy. Not whether you have one — every plan has one. The question is which rate type the guest actually buys when they click. Put your forgiving terms on the type that a guest sees first, and your strict ones where they're clearly labelled, or you'll spend the season arguing about which page they read.

Whether breakfast is its own rate type or an add-on. As a separate type, it has its own price and its own conditions, and a refund removes both together. As an add-on, the room and the meal can end up on different terms, and a part-cancellation gets fiddly. Pick one deliberately. The default is usually the one you didn't choose.

Whether the non-refundable discount is a rate type or a restriction. If it's a rate type, it has its own row, its own conditions and its own mapping. If it's a restriction sitting on your standard rate, then a change to your standard rate silently changes what non-refundable means. Hosts get caught here after a seasonal rate change, when the discount that used to be 12% off becomes 12% off a different base.

All three come down to the same thing: the guest reads the channel's page, not your calendar. Whatever's on that page is what you sold, regardless of what your side says. Airbnb, Booking.com, Agoda and Trip.com show the rate and the status each one is holding on a single calendar at localsbnb.com, which at least means you're reading the same numbers the guest is, rather than the ones you meant to send.

A weekly check that catches drift before a guest does

Ten minutes, same day each week, and it's mostly reading. Start by listing the rate types you intend to sell. Three, four, five — whatever it is, write it down, because the point is to compare intent against reality.

Then open the channel side and list what's actually live. Anything on the second list that isn't on the first is drift, and it usually got there by default rather than by decision. Anything on the first list that's missing from the second is a mapping that quietly stopped being sellable, which is worse: the rate is right and nobody can buy it.

Pick one date four to eight weeks out and check all of them on that same night. Same date, every week, so the numbers are comparable. You're looking for three things: the price, the cancellation line as a guest sees it, and whether breakfast appears where you expect it.

Then check the two conditions people skip — the guest count the headline price covers, and the refund deadline as written on the page rather than as configured on your side. Log the result in one place. Next week's check is only useful if there's something to compare it against.

LOCALSBNB — start free

FAQ

Can I run one rate type and ignore the rest?

You can, and for a single unit it's often the right call. You'll lose the non-refundable segment, which is a real segment. Two rate types — one flexible, one not — covers most properties without creating six things to check.

The price is right but the guest says their booking was refundable. Who's wrong?

Probably nobody, and that's the problem. If the rate type they bought carries looser terms than your plan, the page they bought from is what they'll hold you to. Fix the mapping rather than the argument.

Do I need to re-check after a seasonal rate change?

Yes, and specifically the non-refundable one. When your base moves, a discount expressed as a percentage moves with it, and any rate type derived from that base changes its meaning on the same day.

Rate types are conditions wearing a price tag. Map them deliberately, check what's live rather than what you set up, and keep the weekly comparison somewhere you can read it a month later. Four channels on one calendar at localsbnb.com, each showing the rate and status it's holding — which is the only way to notice that one of them drifted.


Rate type names, availability and conditions differ by property, market and platform, and change over time; this is general guidance rather than platform policy advice. Confirm against your own partner portal and that platform's current terms.

审核

Localsbnb 内容团队