Routing Rules - improvements
The routing rules allows us to route the following options;
1 - Only reservations that are prepaid in online travel agency (OTA)
2 - All reservations with this company or travel agency attached
recommended improvement #1
we noticed that option 1 does not route prepaid reservations by VC.
As Bcom does indicate its a VC instead of a prepaid to TA. We cannot apply routing to this TA. As they do not have separate TA profiles for VC and CC as Expedia has, we currently cannot distinguish which ones should be routed.
Recommended improvement #2
As multiple company profiles might be used for several business types (extended stay, groups, hotel fe.), different routing may need to get applied.
Fe. an extended stay guest reservation by ING is on account, whereas a hotel guest need to pay himself. Therefore routing on a company profile does not give us enough granularity and we cannot apply the routing by company profile. We suggest to add an additional filter on the rate plan in the routing rule. So we can distinguish which ones can be routed fe. ING + EXTROAR will be routed company and ING + C05RO24CC will not be routed to company.
Ideally we can apply auto routing rules to paymasters, fe. for accounts that will have an invoice on a monthly basis.
Example; Company profile X, if rate X is attached, route to paymaster X.
We should be able to see which routing rule applies on a reservation level, as it is auto applied and have the opportunity to easily amend it. If it should not get applied.
(al details have been provided earlier in MVP stages to ilse & Vincent)
Hey Mewser, thank you so much for your suggestion. We’ve updated the status to ‘idea to upvote’ for the rest of the Mews community.
Tom Keller commented
To add up to Sharon, if you allow me Sharon :)
We wait to start a 100% online check in/out or check in/out via kiosk until a full routing-option is available. And routing should always be live and running, not only when the reservation is created. What we miss in certain examples:
- Expedia prepaid reservation, via virtual card: nights have to be automatically charged to virtual card in one bill (or window), city tax has to be charged to guest's card in a different bill. How does Mews know what card to charge for what bill/window? And which bill is per default viewable for the guest (in kiosk for example)?
- same goes for corporate and/or group bookings. Easy example is that the company pays for nights and city tax (and employer doesn't want employee to see which rate they contracted with hotel), but employee pays for own incidentals. So a personal credit card that should be charged, but also items that need to be moved to an invoice (paymaster account)
- in case of prepayment with Booking.com: virtual card can be charged for nights and 7% city tax, but not for €3 pppn because that's only paid upon arrival by guest personally (Mews cannot automatically charge city tax now...). Would be perfect if PMS could automatically split and have the right card charged for the right amount
Smaller error margin and automation are most important reasons for us to have and ask for this complete routing option, next to the fact for it to be a basic feature for self check in and check out.