|
Linked and Group Reservations
|
Top |
| · | Synchronized -- The reservations keep their dates and status in sync automatically (for instance when you check in one, the rest are all checked in automatically), and are combined for billing purposes. They must all be under the same customer name.
|
|
|
| · | Non-synchronized -- Reservations linked this way can have different dates and have separate transactions for billing. They start out under then same customer name, but the customer for each one can be changed later through the "Change to a different Customer" function in Reservation Details.
|
|
|
| · | Sub-member -- Besides being "logically" a sub-member of the owner reservation, transactions (billing) will be combined with the "transaction master" reservation and the customer must be the same. However, it's not synchronized with the portfolio owner so the dates do not have to be the same as the owner reservation.
|
| = Synchronized
|
| # Non-synchronized
|
| > Sub-member
|
| RV 1 [Linked master]
|
| = RV 2 [synchronized with RV 1]
|
| > Stall 1 [sub-member of RV 2]
|
| = RV 3 [synchronized with RV 1]
|
| # RV 4 [not synchronized]
|
| > Boat slip 1 [sub-member of RV 4]
|
| > Kayak 1 [sub-member of RV 4]
|
| # RV 5 [not synchronized]
|
|
|
| · | RV 1 owns 2 portfolios -- a Synchronized portfolio containing RV 2 and RV 3, and a non-synchronized portfolio containing RV 4 ad RV 5.
|
| · | RV 2 owns 1 portfolio -- a Sub-member portfolio containing Stall 1
|
| · | RV 4 owns 1 portfolio -- a Sub-member portfolio containing Boat slip 1 and Kayak 1
|
| · | Since all synchronized and sub-member reservations are combined for billing (and any synchronized or sub-members of those, etc. all combined with their top-level owner), the reservation for RV 1 will also contain all transactions for RV 2, RV 3, and Stall 1. However, non-synchronized reservations are considered separate "sets" or "top-level reservations" for billing -- so the reservation for RV 4 will include transactions for Boat slip 1 and Kayak 1, and RV 5 will only contain transactions for itself. Thus by using appropriate link types, you can completely control which reservations are combined for billing.
|
| · | Only synchronized reservations will maintain identical dates and status. Thus RV 1, 2, and 3 will stay synchronized if a change is made (assuming the appropriate answers are given when prompted to keep them synchronized). But changes to any of the others will only affect that reservation.
|
| · | There are no date restrictions for sub-members (for instance it's not like a Guest reservation where the guest's stay can't be outside the host) -- so by using sub-member linking it's even possible to combine billing for separate stays (even on the same site!) for the same customer.
|
| · | Even Guest reservations can have sub-member reservations linked to it -- so for instance a Guest can rent a stall or canoe, which can be combined on the guest's bill and not affect the host reservation.
|
| · | Any synchronized link can be changed to non-synchronized (e.g. to separate the billing or change the customer) or a sub-member (to change dates independently while keeping the billing combined). However it cannot be changed back to synchronized (since there could be a conflict of dates, etc.). For the most part it wouldn't be necessary to re-synchronize it, since Sub-members have most of the same advantages.
|
| · | Any non-synchronized or sub-member link can be changed back and forth, so you can combine or separate billing at any time (but be sure to go back and re-calculate charges appropriately if you don't have auto-recalculation enabled).
|
| · | If the dates and/or the customer of any linked reservation is different than the master reservation, then the differences will be noted wherever the tree list is shown.
|
| · | If you need different customer names on each reservation, e.g. for groups, then they must be non-synchronized.
|