The practical answer
Partner booking acceptance starts with the restaurant's real service availability and a separate check of partner authorisation. Rezervem Manager manages normal booking rules and capacity, while Guest Network supports partner relationships, restaurant-level blocking and commission terms.
A bank programme and a hotel concierge may both refer guests for the same Friday evening. The dining room still has one finite capacity, so the host team needs a clear policy that applies to both requests.
Start with capacity, not partner promises
Check open days, meal periods, party sizes, table availability and cancellation or prepayment rules. Partner referrals do not generate capacity or guarantee a preferred table.
If the preferred time is unavailable, communicate that result or propose an alternative the guest accepts. Any priority-seat arrangement needs explicit restaurant agreement rather than an assumed software feature.
Evaluate the partner's permitted access
An integrated partner can access the venues and operations allowed by its credentials and configured relationship. Blocking a partner for a restaurant is a distinct capability from closing that venue for all reservations.
The present venue-access implementation distinguishes global and non-global partners. Enrolment enforcement remains a transition item, so confirm practical access in the actual environment before publishing partnership promises.
Separate hold, confirmation and checkout
An availability response does not secure a table. A temporary hold, confirmation and possible payment finalisation represent distinct points in the supported flow.
Make sure the guest understands which step has actually completed and which cancellations, deposits or extra conditions apply. Avoid turning a preliminary request into an apparent confirmation.
Measure the outcome independently
Partner-specific commission rules describe the economics of relevant activity; they do not override the restaurant's seating limits. Check-in and any qualifying bill records may be needed for a calculation.
Rezervem Manager supports the venue team with reservation operations. Guest Network and Partner API support authorised routing and technical access; evaluate booked parties, seated guests and ledger states separately.
Five checks before you launch
Apply these steps to a real venue and partner before promising guests a booking.
- Confirm actual availability for date, meal and party size.
- Check the partner's permissions and restaurant-level block.
- Distinguish requests, temporary holds and confirmations.
- Explain cancellation, payment and benefit terms to the guest.
- Report seated guests, commissions and collections separately.
FAQ: Does blocking a partner stop every booking channel?
No. It restricts the specified partner at the restaurant rather than closing all other routes.
FAQ: Does Guest Network automatically assign a daily quota per partner?
A default partner-specific daily quota is not verified in the reviewed code; use real availability and explicit agreements.
FAQ: Is a temporary hold a confirmed reservation?
No. Confirmation and any required checkout finalisation must succeed first.
