> ## Documentation Index
> Fetch the complete documentation index at: https://docs.riservahq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Switching from Tock or another system — what's different

Riserva starts empty: **nothing is imported from another system**. This page
lists, plainly, what works differently and what Riserva doesn't do, so you
can plan the switch.

## What carries over

Nothing is imported. Riserva has no import for reservations, guests,
experiences or settings from Tock or anywhere else. You build your venues and
experiences in Riserva. Reservations already booked in your old system stay
there, so plan how your team will honour them until those dates pass.

What you already have in Shopify is used as it is:

* **Customers.** Reservations link to your existing Shopify customers.
* **Member tags.** If your club software tags customers, Riserva reads those
  tags to recognise members. See
  [Members and members-only experiences](/memberships/member-benefits).
* **Products for add-ons.** An add-on, such as a cheese plate, can link a
  product you already sell. Each experience gets a new Shopify product of its
  own when you publish it.

## Deposits

Riserva takes no deposits. A guest pays the **whole** fee at checkout, or
saves a card that Riserva charges the whole fee later. There is no "part now,
the rest later".

The closest substitutes are paying in full at checkout under your
cancellation policy, or a card on file charged before the visit. See
[Coming from deposits?](/core-concepts/payment-policies#coming-from-deposits)
for each option side by side.

## No-show protection

Riserva charges no no-show fee. Marking a no-show never charges or refunds
anything. What you keep depends on when the experience is charged:

| When is it charged? | If the party doesn't come |
| - | - |
| **At booking — paid at checkout** | You keep what they paid. Only a cancellation refunds, and only what your cancellation policy allows |
| **Before the visit — charged automatically** | The card was charged before the visit, so you keep it |
| **At check-in** or **At the visit** | The card is never charged, so nothing is collected |
| A reservation your team booked, still [**Payment due**](/reference/glossary#payment-due) | Nothing was collected. You can still send a payment link |

See [Cancellations and refunds](/daily-operations/cancellations-and-refunds).

## Member pricing

Here is what Riserva does for club members today:

* recognises members from their Shopify customer tags
* shows a **Member** badge on their reservations, in the admin and on the
  register
* lets you make an experience **Members only**, so only recognised members
  can book it online. Your team can still book it for anyone.

Member discounts and free member tastings are not part of Riserva today. A
member books and pays the same price as any other guest.

## Text messages

Riserva sends no text messages (SMS). Every guest message is an email,
including the waitlist's "your table is ready".

If your store uses Klaviyo for texts, a Klaviyo flow can send one from
Riserva's five events: **Riserva Reservation Confirmed**, **Cancelled**,
**Rescheduled**, **Checked In** and **No-show**. Riserva identifies the guest to Klaviyo by email and
sends no phone number. So the text reaches a guest only when their Klaviyo
profile already has a phone number with SMS consent. See
[Klaviyo](/integrations/klaviyo).

## What Riserva doesn't do

* **No text messages.** Email only, as above.
* **No deposits.** The whole fee, now or later.
* **No no-show fees.** A saved card is never charged because a party didn't
  come.
* **No guest account area.** A guest opens one reservation at a time, from
  the link in their email or with their code and email.
* **No waitlist for future dates.** The online waitlist covers today only.
* **No bulk actions.** Reservations are changed one at a time. The list's
  **Export** can still download many at once.
* **No import.** Nothing comes over from another system.

## Staff permissions

Riserva has no roles or per-person permissions of its own. Shopify's staff
permissions decide who can open Riserva in your admin, and anyone who can
open it can use all of it.

Two things are limited, and one is recorded:

* **Refunds at the register.** Shrinking a paid party at check-in in Shopify
  POS refunds only what your cancellation policy allows. Tick **Allow POS
  check-in to refund beyond the policy** under **Settings → Policies →
  Refund overrides** to let the register go further. It's off unless you
  turn it on.
* **Renew now** on your plan appears only for the store owner. See
  [Plans and billing](/getting-started/plans-and-billing).
* **Who did what is recorded.** Changes land on the reservation's timeline
  with who made them.

## Related

* [Install Riserva and work through setup](/getting-started/install-riserva)
* [Payment policies and money states](/core-concepts/payment-policies)
* [Uninstalling Riserva and what happens to your data](/getting-started/uninstalling-and-your-data)
* [Troubleshooting and FAQ](/troubleshooting/troubleshooting)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.