Agoda's Partner Portal: Where the Old Settings Went

The settings did not disappear when the portal was renamed. They moved, and three of them sit somewhere new.

Last updated: October 31, 2026

Agoda's partner portal changed its name, and the login page wasn't the only thing that shifted. Nothing was deleted. What changed is the route you take to reach a setting, and three of the ones hosts touch most now sit a level away from where they used to be. Find them once, write down where they landed, and the whole episode costs you an afternoon.

Key Takeaways

• A rename isn't a deletion. A brand consolidation usually moves the route to a setting, not the value inside it. Check what the channel shows before you assume anything was lost.
• Three settings account for most of the hunting. Rate defaults, availability rules and notification contacts are the ones hosts report looking for.
• Verify the pushed rate, not the entered rate. The number in your portal and the number a guest sees are two different facts, and only the second one bills anyone.
• Re-typing is the expensive move. Overwriting a working setting to feel safe is how you create the outage you were trying to prevent.
• Snapshot the pages, with dates. One folder per property, one screenshot per tab, dated. It turns the next migration into a five-minute comparison.

What the rename actually changed

The consolidation was announced in a press release dated 17 August 2026, as published by PRNewswire on that date. Read at company level, it's a brand decision: one name, one logo, one set of product pages.

Read at desk level, it's a navigation event. A rebrand usually rebuilds the menu before it rebuilds anything else, because the menu is what carries the new vocabulary. Labels that used to be verbs turn into nouns. A tab you found by muscle memory now needs a second of thought.

That's the whole disruption, and it's worth naming plainly. Your property data, your rates and your booking history are records. They don't usually move because a logo did. The door to them does.

So the first useful question after a portal change isn't "what did they break". It's "which door did this setting move behind". Ask it about one setting at a time and you'll work through the list in a single sitting.

There's a second question that saves more time than the first. Ask whether the thing you're looking for was ever one setting. A nightly rate, a minimum stay and a weekend surcharge are three objects in most channel models, and a rebrand that re-groups them will scatter the three across two screens that no longer sit next to each other.

The three settings that moved

Three categories account for most of the hunting after a channel portal changes its shell. They moved for a shared reason. Each used to hang off the property record, and each now belongs to something narrower.

Rate defaults. A base nightly rate and a default minimum stay used to be property-level facts. Under a newer structure they usually attach to a rate plan, because the plan is the object a channel actually pushes. If you set a rate at property level and can't find it afterwards, look for the plan it was meant to live in, then for the date range it covers.

Availability and restriction rules. Closed-to-arrival days, a maximum stay, a gap between bookings. These are calendar facts, and calendar controls tend to sit with the calendar rather than with the property record. The label may not match the one you remember, which is why searching for the old term can come back empty while the control sits two clicks away.

Notification contacts. Who receives a new-booking mail, and which address gets the weekly summary. This one moves quietly and it's the one that hurts. A missing booking mail looks exactly like a missing booking until you check the address it was meant to reach.

None of this is a fault. It's what a rebrand does to a menu. The reason it matters is that hosts read "I can't find it" as "it's gone", and then act on that reading by re-entering data that was never lost.

There's a check that settles the question faster than any amount of clicking. A setting is only real once the channel has pushed it, and the calendar at localsbnb.com shows each connected channel's source price and status, so a rate that stopped matching is visible in one view instead of four dashboards.

What to re-check after a migration

Work through four checks in this order, and stop when each one answers.

Does the channel still show your rate? Open the calendar, not the editor. The editor tells you what you typed. The channel's source price tells you what it received, and those two can differ after any structural change.

Do the restrictions still hold? A minimum stay that quietly reset to one night will fill your calendar with single-night gaps before the lost revenue shows up anywhere you'd notice it.

Is the connection still live? A portal change may leave a property connected but not authorised, and an unauthorised connection looks identical to a quiet week until you try to push a rate through it.

Does the booking mail still arrive? Send a test booking if the portal allows it, or ask a returning guest to confirm that the confirmation email actually landed in an inbox someone reads.

Four checks, twenty minutes at most. Compare that with finding the third one three weeks later, on a night you thought you'd sold.

There's a fifth check worth adding once, and only once. Log in as the person who covers your days off, if the portal has a second seat, and walk the same four screens. A route you can find in the dark isn't a route your co-host can find at all.

Keeping a settings snapshot

The fix for the next rename is unglamorous. Screenshot the tabs you actually use, name each file with the property, the tab and the date, and keep one folder per property. Then write the four numbers that matter into a plain text file beside the images: base rate, minimum stay, cancellation terms, notification address.

Re-take the set once a quarter, and immediately after any portal change. A dated snapshot turns "did this move?" into a two-minute look instead of a memory test. It also ends arguments with a support desk, because you can say what the screen showed on a specific day rather than what you think it showed last spring.

A good snapshot also answers the questions you'd otherwise answer twice a month, which is why it's worth sharing with whoever covers the property when you're away.

Two habits keep the snapshot honest. Store it somewhere the owner can reach, not in your own downloads folder. And write the date the snapshot was taken, not the date you filed it, because the gap between those two is exactly where the confusion lives.

FAQ

Did the rename delete my settings?

Almost certainly not. A rebrand moves the route to a value far more often than it removes the value. Check the channel's live rate and the property's connection status first. If both still read the way you set them, nothing was lost and the only thing that changed is where you look for it.

Why can't I find a rate I set last month?

Usually because the field now attaches to a rate plan rather than to the property. Search for the plan, then the date range, then the channel. If the channel is showing the rate you expect, the field still exists and you simply haven't found its new home yet.

Should I re-enter everything after a portal change?

No. Re-enter only what you can't verify. Overwriting a setting that's already working is the one action here that can create a real problem, and it's the action people reach for when they're anxious. Verify first, retype second, and only for the fields that failed the check.

A rename is a small event with a long tail, and most of the tail is looking. Write down where the three settings live now and the next migration costs you a comparison instead of a hunt. Once the routes are mapped, localsbnb.com is where the rates and the calendar sit in one view, so the weekly check is a glance rather than a login.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Channel portals change their navigation without notice, and labels differ by market and account type. Confirm where a setting lives in your own account, and confirm any policy or fee question with the platform's current terms, before you act on it.