What the rule actually does
Rezervem's pricing rules use Manager booking details to calculate eligible restaurant prepayment or card-hold amounts by date, meal, area and party size, while Rezervem Pay serves the separate payment-request workflow. It is not an AI system that changes prices silently with demand; the restaurant configures the rules and transaction types.
A realistic service scenario
A restaurant may waive prepayment on weekday lunches but request TRY 750 per guest on Saturday evenings. That example produces TRY 3,000 for four guests. Where a dining area defines a fixed amount for the table, staff should not multiply it by guest count again.
The venue needs consistency between the amount explained during reservation selection and the amount requested at checkout. Testing a single day is not enough: conflicting rules and changes of dining area also matter.
The operational boundaries
Rule-based amounts are enabled per venue and may not be switched on for every restaurant. Overlapping rules, venue defaults and per-table versus per-person area pricing can produce different amounts.
A prepayment is collected money while a hold is a temporary authorisation. Recalculating after a party-size change does not itself perform a refund or collect an additional amount from the bank.
Five checks before launch
Verify the process with a test booking rather than relying on a button label.
- Define the dates, meal periods, service areas and party sizes that need a booking safeguard.
- Set the intended transaction type separately for prepayment and card authorisation.
- Check which amounts apply per person and which apply once per table.
- Test overlapping rules, changes of party size and different areas or booking dates.
- Compare the guest-facing preview with the payment request and do not assume prior charges are recalculated automatically.
How Rezervem handles the workflow
Rezervem Manager provides booking date, meal, area and party data. For enabled accounts, pricing rules determine a requested amount while Rezervem Pay and its payment infrastructure handle the resulting authorisation or collection.
A go-live check should verify that the relevant rule is enabled, that the final amount is correct and that the transaction type is appropriate. A correct calculated amount is not proof that the bank has charged it.
FAQ: Is this an AI-driven surge price?
No. It is a calculation based on rules configured by the restaurant.
FAQ: Is a fixed table amount multiplied by party size?
Not when the applicable area rule defines a single total for the table.
FAQ: Does changing the booking automatically adjust a past charge?
No. Repricing is separate from an additional charge or refund.
