Hi,
Thanks for your detailed questions. We are going to drop some comments to clarify some of the points you raised, but for any other technical or commercial question you may have on the Pro version of the plugin, we invite you to reach our to our team directly through our website where you will find an apposite contact form.
PIN Code:
The PIN code is a quite safe alternative to forcing the guests to create an account on your website to complete a reservation or to log into their existing account. The PIN code is a 10-digit unique and random number, and the probability to guess it is likely one in 10 billions (~10^10). Also, PIN codes are widely used among some OTAs too, even though they sometimes link the PIN codes to the reservation ID.
However, for a single-vendor website where Vik Booking would be installed, this is a very safe operation we guess. Moreover, in terms of security against brute-force attacks, we secure the AJAX endpoint with a CSRF token to prevent bots from trying to guess a PIN code.
Lastly, the PIN code will reveal just the latest billing information used, it will not grant access to any administrative section. As you’ve noticed, there’s a dedicated configuration setting in case you want to turn off this feature, and of course the PIN code is something that could be modified at any time for any customer from the apposite back-end customers management page, which is only available with the Pro version of our plugin.
If you visit the official demo website of Vik Booking you can see how the PIN codes can be modified for each customer.
Coupon codes:
The valid and accepted coupon codes must be saved on the same WordPress database where Vik Booking is installed. However, with a custom Cron Job you could have such codes imported from an external server and stored onto your database. With the Pro version of Vik Booking it is possible to declare a custom Cron Job by creating a custom WordPress plugin that uses a specific hook triggered by Vik Booking when loading the Cron Jobs framework, which is based on the official WP Cron system. We are about to release an update for Vik Booking (version >= 1.5.10) that will improve the whole Cron Jobs framework.
Changelog: we do have one, and you can find it in the official trunk directory of the plugin. The file is called changelog.md, and we have one for the whole plugin as well as one for our own PHP libraries.
Heavy or Lightweight: Vik Booking is definitely a lightweight plugin, which was coded with the attention to efficiency in over 10 years of experience with properties of any size. For example, we’ve got some clients that have been using our full solution comprehensive of the Channel Manager for years, who manage hundreds of Airbnb listings, something like 800+ listings or 200+ Booking.com accounts. They count millions of reservation records stored in Vik Booking, but the efficiency and the performances of our software are always at the top. Of course what gets bigger in these cases is the size of the database, but for regular properties with around 50 rooms or less, you can expect an average growth of the database by a few MBs per year.
For sure we cannot control the speed or the connectivity bandwidth at software-level, but we can guarantee our plugin is fast. Not sure what links or pages you saw, probably some staging websites from questions posted to this forum, but we do not have any public portfolio section on our websites because ours is a commercial plugin which is most of the times delivered to the property managers by webmasters, programmers, designers, web-agencies etc..
Community: we don’t have a community on our websites, but we do have a Support Board for our clients who can use it to open support tickets at any time.
Feel free to get in touch with our team should you have any other technical questions. Thank you!
The VikWP Team