Checklist: taking your environment live

The configuration is finished and tested. Go through this list before you let the first real customer book. Most of it is a quick check. The payment provider and the test data are where it usually goes wrong.

1. Payment provider from test to live

As long as your payment provider is in test mode, a booking looks paid, but no money comes in. So check every payment method in Configuration - Modules - Payment methods reservations:

• Mollie: set Processing type to Full processing and enter the Live API key, not the test key. The test key starts with test_, the live key with live_.
• Pay.: set Processing type to full processing. Check that the Service ID (starts with SL) belongs to the sales location of your real website, and that this location is active in your Pay. dashboard.
• At the provider itself: your account must be activated and verified, and the payment methods you want to offer (iDEAL, credit card, Bancontact) must be switched on.
• Make one real payment of a small amount, and check that it arrives as paid both at the provider and on the reservation in i-Reserve. If you no longer need it, refund the amount from the provider's dashboard.

2. Offer and schedules

• Is your offer complete? Compare your list of products, packages and activities with what you actually sell. Is anything missing that customers still book by phone or e-mail?
• Is the planning far enough ahead? Customers often book weeks or months in advance. Are activities or available times planned for the whole period in which you want to be bookable?
• Are your schedules correct? Opening hours, closing days, public holidays and season changes are in them. Are the right guides, staff or objects scheduled, and is nobody double-booked?
• Capacity: the maximum number of participants or places per activity or time slot is what you can really handle.
• Visibility: what should be bookable online is online. What is only booked internally, such as custom work or groups, is not on your website.

3. E-mail to your customers

• The sender address belongs to your own organisation, and replies arrive in a mailbox someone reads.
• Confirmations, reminders and invoices contain your real contact details, opening hours and terms, not text from the test period.
• Send yourself a confirmation and check that it does not end up in spam.

4. Website and booking module

• The booking module or widget is on your real website, not only on a test page.
• Prices, VAT, times, capacity and the period in which you can be booked are correct.
• Terms and conditions and the privacy statement are linked and reachable.
• Make one booking from start to finish, the way a customer does. Also try once to book something that should not be possible, such as on a closed day, and see that it is stopped.

5. Users and rights

• Every staff member has their own account, with a role that fits what they do.
• Temporary and test accounts from the setup period are removed or disabled.

6. Invoices and integrations

• Company details on the invoice (Chamber of Commerce, VAT number, IBAN) are correct.
• Integrations with your bookkeeping, calendar or sales channels point to that party's production environment, not their sandbox.

7. Clean up test data

Remove trial bookings, test customers and test invoices, and have your invoice numbering reset if needed. The latter is only possible while your environment is still on Implementation. See Removing test data before going live.

8. Status to Live

Your environment has a status: Implementation or Live. That status does not change what your customers see or how bookings work. It is a signal:

• For support: a report from an environment that is live gets more urgency than a question during setup, because real customers are booking.
• For the AI tools: the status helps decide which MCP tools an AI agent may use in your environment. During implementation there is more room to configure than on an environment that is live.
• For your administration: after the switch to Live, the invoice numbering can no longer be reset.

Let support know when you go live, and we switch the status.