PageSourceSearch

https://resoflow-prod.web.app/assets/deposit-schedule-F2W6b69w.js

js resoflow-prod.web.app collected 2026-10-03 12:39:05 UTC 3,570 bytes, 2 lines download raw bytes

1!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{};e.SENTRY_RELEASE={id:"1.0.0"};var t=(new e.Error).stack;t&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[t]="2f7ec1e5-2741-43d8-b43f-097426e543a8",e._sentryDebugIdIdentifier="sentry-dbid-2f7ec1e5-2741-43d8-b43f-097426e543a8")}catch(s){}}();const e="__RESOFLOW_HELP_BODY__",t="Use the **Deposit: when you ask for one** section on **Settings → Payments and deposits → What guests pay** — its two rows are **Days and times** and **Event deposits**. The page spells out how the pieces fit: **Require deposits** applies **every day**; day and time rules **restrict** it to just those times; a date's own deposit **always applies** on its date — even when **Require deposits** is off. \"A special date beats your day-and-time rules, which beat your everyday rules.\" (Pay in full and pre-orders follow exactly the same model.)\n\nBoth come with deposits: *Available on Plus plan and above*. On a plan without deposits, the add buttons are replaced by a padlock chip; rules you already have stay listed — read-only, and not used — and can always be removed. Only Owners and Admins can open the page.\n\n## Deposits on certain days and times only\n\n1. In **Days and times**, click **Add day/time rule**.\n2. Pick the day, leave **All day** on, or switch it off and set a start and end time (e.g. Friday 18:00 to 23:00).\n3. Add as many rules as you like, then click **Save changes**.\n\nOnce any rule exists, deposits are only required on those days and times. With no rules, deposits apply to every eligible booking. Rules work **alongside** your party-size threshold — a deposit is taken only when both the time/day *and* the party size match.\n\n## Deposits on specific dates\n\nA date's own deposit — Valentine's Day, Hogmanay, a set-menu night — is set with the date's other rules on **Settings → Bookings → Special dates**:\n\n1. Add the date (or open it with **Change**).\n2. On its **Deposit**, choose **Custom** and set the amount — per person or per booking, following your deposit's own choice — and, if you like, a party size it starts from.\n3. Click **Save changes**.\n\n**Event deposits**, on What guests pay, then lists every date with a deposit of its own (the date, its name and its amount), with a link to Special dates — it's where you see them, not where you change them.\n\nA date's own deposit **overrides** your standard amount on that date — and applies **even if \"Require deposits\" is switched off**, so you can run deposit-free normally but still protect your biggest nights. Your refund rules (What guests pay → **Cancellations and refunds**) cover it too — and a date can also have its own refund cut-
1off (**Money back if they cancel**) — and it appears in your customers' terms. See [What's different about Christmas Day? (Special dates)](special-dates).\n\n[Pay-in-full bookings](pay-in-full-bookings) have their own matching day and time rules and dates of their own — and where pay in full applies, it takes priority over your deposit rules for that booking.\n\nRelated: [How do I take booking deposits?](deposits-setup) · [When do customers get their deposit back?](deposit-refunds) · [What can customers pay when they book? (What guests pay)](what-guests-pay) · [How do pay-in-full bookings work?](pay-in-full-bookings)";export{e as __helpBodySentinel,t as default};
2//# sourceMappingURL=deposit-schedule-F2W6b69w.js.map

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.