A quick setup is useful only if the offer is correct when the first guest books. The practical goal is a working first release with clear responsibilities, rather than an untested copy of every product from the previous system.
Prepare one representative offer
Choose a course with the participant information, dates and price rules you really need. Add a rental example if rentals are central to the school. Bring the current descriptions, images and a representative export so import scope and field mapping can be checked.
Decide which system remains responsible for existing bookings during the switch. Do not assume that every historical field or attachment can be imported unchanged. Agree how missing and duplicate data will be handled.
Reuse pricing carefully
Shared Pricing Modes and rental price categories reduce repeated edits for related offers. First group items that genuinely follow the same pricing rules. Then test different durations, dates and quantities. A reusable rule is helpful only when the resulting customer price matches the intended offer.
Preview the supported customer views
Live Preview helps review supported catalogue and booking presentation before publishing. Check descriptions, images, choices and prices on desktop and mobile. It is not a universal preview of every account setting or every external website integration.
Finish with a complete rehearsal
Run a representative booking, verify payment setup and messages, then let staff find the booking and plan its delivery. Test with the permissions of the people who will do the work. Name an owner for price maintenance and a contact for launch questions.
The setup and import overview explains the preparation. Use pricing and capacity for the offer rules; current service fees belong on the pricing page.
How does this work at your school?
Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.
Request a demo →