Ruth Mills
Well-Known Member
Also, access to the system at the salon would likely be either via a Web browser, or a dedicated "thin client" application (e.g. should additional functionality be required, such as integration with a till, barcode reader, receipt printer, etc) - so the salon's computer would always access the central server to retrieve data (although a well-designed client application would also "cache" data in the event of the Internet connection with the central server being broken - so the salon would be able to continue with "business as usual" if there was ever a problem with their broadband, for example).
Although that scenario does pose synchronisation issues; e.g. if the salon's broadband connection drops out for several minutes and they are operating off-line, then they are only operating using the latest "cache" of data - meaning that people could still be booking appointments online via the salon's website - and likewise, the salon's receptionist could be taking new bookings in person or on the phone, which are then stored locally on the salon's computer - but not on the database on the central server.
This could be alleviated by having the salon have to "confirm" all bookings made online via the website - e.g. when someone books an appointment via the website, it is initially added as a "provisional" appointment; if it turns out that it's OK, then the salon sends them a confirmation by email or text; if not, then the receptionist can phone the client to re-arrange the appointment slot. So any bookings made via the website while the salon's broadband is down would only subsequently be confirmed once the salon's broadband comes back up and the salon is able to access the central server again.