Reservat Core
This is a scratchpad to work out the core mechanics of reservat.
Feel free to change/PR as appropriate, we need to work fast and break things as we go, mappings etc are subject to change, as will be queries
until we find the fastest method by which to serve the appropriate user data through the API., (*1)
Request config settings from me :D, (*2)
Why?
I believe that people want to ability so that they can outcome, and they would pay good money for that because value., (*3)
Startup from Scratch, (*4)
I believe that people want to serve reservations to online customers so that they can reduce friction with todays generation of phonophobes and have better oversight of their restaurant, and they would pay good money for that because the chances for upselling and trying to fill their restaurant, using accurate and realtime reporting will make them more profitable., (*5)
If you value, you can ability with reservat so that you can outcome, (*6)
If you don't offer online bookings or have used a system like OpenTable that feels inflexible, expensive and hard to use, you can use a cheaper and smarter solution that puts the power back in your hands, using our table management and API's to make booking for your restaurant bespoke and beautiful, whilst relying on realtime reporting and statistics for you and realtime response to your customers with Reservat so that you can improve your booking rates and analyse busy periods to better make use of your table space whilst providing a better experience for your customers., (*7)
Wallogit.com
