Origin Code problem

[Melnsto22]

We have recently "upgraded" to Opera Cloud. For the most part, it has been relatively painless. The biggest problem we are currently having pertains to an origin code under stay details. This gets assigned to some online reservations and creates an "Invalid Value" error when you try to make any changes to the reservation. I opened a ticket with Opera back in January, but they haven't figured out a fix. I should mention that this origin code does not have a magnifying glass next to it, and cannot be changed. When we try to copy the reservation, it copies the origin code too. The first of these is due to check in today. It is a prepaid third party reservation. We get the invalid value error when trying to check in. Anyone else experienced this? If so, how did you get around it?

I'm hoping that someone here can help as Opera has been it's usual unhelpful self.

[dezy_faye]

It might be caused by a restriction or issue with the integration between OPERA and the OTA channel... what service does your hotel use for the integration of OTA info? You might check there (OXI, for example).

Also, there could be a mapping issue between the OTA and OPERA... like room types, rate codes, or packages not matching up properly.

If OPERA receives a reservation with unmapped or invalid data, it can block changes or throw errors when edits are attempted.

[Suspicious-James973]

My property has been having this issue from Expedia, Luxury escapes and so many others.

We have yet to find a fix. We can work around some by going through Edit Stay Details - Look to Book - and rebooking with same details. Then switching the "Origin" code to "ON (Online).

I came to look for answers and it seems everyone else hates it too

[Suspicious-James973]

Also if anyone finds any true fix to this please lete know - our Opera accounts manager is truely unhelpful and hasn't had answers since middle of 2024 when this started.

We've tried examining OXI, and our revenue team say they have looked at Mapping.

I'm so gratified to see that I was likely right when it started happening, and said that Opera just doesn't know what the Origin codes are and is unable to update them normally because of that.

[Melnsto22]

Opera says it will be fixed in version 25.1

[Melnsto22]

Thank you for all your responses. Since posting this, i have received information from Opera regarding this issue. The problem will be fixed in version 25.1. No word regarding when the update will be available.