β¨ Please note: Multiple booking pages are only available on the Standard plan and above.
Testing schedule changes before applying them to your live events helps prevent mistakes and confusion. Understanding how to create a safe testing environment ensures you can experiment with updates confidently.
This article explains how to safely test schedule changes in Bookwhen without impacting your live schedule.
How to safely test schedule changes in Bookwhen
You can safely test schedule changes by using a separate test schedule page. This lets you experiment with events, tickets, and settings without affecting your live schedule.
Why use a test schedule
Bookwhen supports multiple schedule pages, making them ideal for testing. Use a test schedule to:
Try out new event setups
Experiment with ticket types and pricing
Evaluate major updates before applying them to your live schedule
Testing changes this way ensures your live schedule stays accurate while giving you the freedom to experiment.
Steps to create a test schedule
Create a new schedule page
βSet up a separate schedule page in your Bookwhen account specifically for testing.
Configure the test schedule
Add events, tickets, and settings you want to trial. This gives you a realistic environment to see how changes will work.
Best practices for testing π‘
Use entry passwords
Protect your test schedule with a password to prevent accidental bookings and restrict access to authorised users.
Remove your page from search engine results
Hide your page from search engines, to protect your page from being found.
Experiment freely
Try different configurations and make adjustments as needed. This ensures your changes are fully evaluated before applying them to your live schedule.
Limitations to keep in mind π
Entries cannot be moved across schedules
Once you create an entry on a schedule, you cannot move it to another schedule, so plan your tests carefully to avoid creating duplicates.
Return to the top β¬οΈ
