The answer
Rezervem Manager manages restaurant reservations and service capacity; Guest Network manages partner referral relationships; Partner API allows authorised external applications to access supported booking operations. The three can work together, but partner access, a temporary hold and a confirmed booking are different stages.
Suppose a bank app presents a restaurant to a cardholder. The cardholder chooses a date and party size, but only the restaurant's real availability and successful booking steps can produce a reservation the host team can expect.
1. Start from the restaurant's rules
Before opening a new partner route, the restaurant team verifies service days, table capacity, acceptable party sizes and any prepayment or cancellation conditions in Manager.
The partner-facing promise should fit those rules rather than assume separate inventory or guaranteed priority. A venue team may need to review how changes and cancellations appear during a busy service.
2. Separate network scope from technical permissions
Guest Network supports the relationship between restaurants and eligible referral partners. Partner API is the authorised connection for supported external interactions such as venue lookup, availability, booking and webhooks.
Partner scope is not identical for every integration. Global and non-global venue rules differ, and enrolment enforcement is in transition; verify the active configuration before asserting access.
3. Follow the reservation states
A partner may ask about a table, create a temporary hold, confirm and then complete additional checkout steps if payment is required. These states should not be collapsed into a single success signal.
The restaurant follows the resulting reservation within Manager. Partners should use only the status and guest data permitted by their credentials and applicable arrangements.
4. Reconcile operations and outcomes
Measure partner-sourced booking counts and actually seated guests separately. If commission applies, the calculated ledger entry, collection result and partner payout are distinct financial events.
Use the Guest Network programme for the commercial relationship and Partner API for integration planning, while keeping Manager as the host team's operational view.
A practical five-point comparison
Review these points with the restaurant and relevant partners before treating any referral as a confirmed booking.
- Verify Manager service and capacity rules.
- Define the Guest Network partner and commercial scope.
- Test Partner API venue access and availability permissions.
- Distinguish hold, confirmation and any payment finalisation.
- Compare the Manager booking, actual visit and commission record.
FAQ: Does Partner API automatically expose every restaurant?
No. Permissions, partner type and active venue-access rules determine which operations and venues are available.
FAQ: Does a booking hold guarantee a table?
No. A temporary hold must be followed by successful confirmation and any required checkout step.
FAQ: Does Partner API provide every POS and hotel PMS function?
No. POS partner permissions differ from Guest Network access, and hotel PMS functionality belongs to separate integrations.
