Changing a rate directly in Agoda's partner portal and changing it through your channel manager can disagree, and this explains why and which one should win.
You can change a rate two ways — log into the Agoda partner portal (YCS) and edit it there, or push the change from your channel manager and let it flow through to Agoda automatically. Both are legitimate, but using both at once, or not knowing which one last touched a date, is how a rate ends up different from what you think you set.
Editing directly in the Agoda partner portal changes the rate on Agoda immediately, for Agoda only. Editing through your channel manager changes the rate in one place and pushes it out to every connected channel, including Agoda, in a single step. Neither method is wrong on its own — the trouble starts when a property uses both, because the two paths don't know about each other.
The usual symptom is a rate that looks correct in your channel manager but shows differently on Agoda, or the reverse, with no error message pointing you toward why.
A channel manager generally treats itself as the source of truth and expects to be the only thing writing to the channel. If someone edits a rate directly in the Agoda partner portal, Agoda now has a value the channel manager never sent and doesn't know about, and depending on how your setup is configured, the channel manager's next scheduled push may simply overwrite that manual change without anyone noticing. The reverse also happens — a direct portal edit can sit in place and quietly outlive several channel manager pushes if the sync for that specific date or room type failed silently.
Open the Agoda partner portal and read the rate for the exact date and room type in question — that is what a guest searching right now would actually see. Then open your channel manager and check what it believes it last sent for that same date. If the two disagree, check your channel manager's change log, if it keeps one, to see whether its last push for that date actually succeeded or failed silently. Treat the partner portal's live value as the one to trust while you investigate, since that's what's being sold.
Read-back verification exists for exactly this gap — every rate pushed from the channel manager is read back from the channel afterward and compared against what was intended, rather than trusted because the push didn't return an error. That doesn't stop someone from editing directly in the Agoda partner portal, but it does mean the next scheduled push either confirms the live rate matches or flags that it doesn't, instead of silently overwriting a change nobody tracked. You can see it on the public demo at try.primehostpartners.com without signing up.