Quick answer
Rezervem Manager supports transferring a reservation between restaurants that belong to the same account, while keeping the reservation on its original date. An authorized user verifies the destination restaurant, area, time and party size. This is a specific same-account, same-day operation; it does not establish that every branch is managed through a single consolidated dashboard.
A moment during service
An evening booking cannot be seated at the first restaurant, but another venue within the same account may have room. A host should not move the guest merely because someone said there is space. The destination area, opening time and real capacity must be checked. The source table also needs to be released correctly so the original service is not blocked by an outdated assignment.
1. Verify the account boundary and permission
Confirm that the source and destination restaurants belong to the same account. The transfer requires a user with the reservation transfer permission. Do not use the standard transfer for a different customer account. Ensure the reservation has not already been canceled or checked in, since those states are excluded from the normal transfer.
2. Select the destination restaurant and area
Check that the destination is open for the desired meal and the chosen area belongs to that restaurant. Assess the updated party size and actual availability. Where hotel capacity checks or overbooking permissions apply, respect those checks rather than assuming they can be overridden.
3. Confirm the time without changing the date
The transfer preserves the calendar day. If another time or shift is required, agree on it with the guest before submitting the change. Verify the correct destination restaurant, area, party size and time in the request. A request to move to a different date needs a separate change workflow.
4. Reassign tables at the destination
When the reservation moves, the source table assignment and waiter references are cleared. Do not expect an old table identifier to map to the new dining room. Refresh the source and destination views and confirm the booking did not leave a stale occupied table in the original service.
5. Confirm the outcome with guest and teams
Only announce the transfer after a successful result. Give the guest the new restaurant name, location, time and any confirmed special arrangements. Have both host teams check the updated record. A retained payment or hold still requires separate review of any financial terms; transfer is not itself a refund decision.
How we do it
In Rezervem Manager, we check the operator’s permission, the same-account boundary and destination availability before transferring the booking. The original day is kept, the source table and waiter references are cleared, and the transfer is recorded for reporting. Guest notifications depend on enabled channels. We have staff verify the new table assignment and both restaurant views after completion. The restaurant accepting the transferred booking should verify that any special seating requirement can actually be honored. That final service check matters even when the transfer transaction succeeds.
Important limitations
- Standard transfer does not move reservations between different Accounts or onto a different date.
- Same-account transfers do not prove a universal single-screen view across all branches.
Frequently asked questions
- Can the date change during transfer? — No. The date is fixed, although time and area can be reselected.
- Does the original table carry over? — No. Source table and waiter assignments are cleared.
- Does the operator need a permission? — Yes. Only users with the reservation transfer permission can transfer a booking.
