Google Calendar support is built into SambaPOS giving you acccess to the API… however I think Google recently changed the way their API works so it may need modification. @emre you may or may not wish to look into this. I know very few people used the google api support.
From Google Calendar API website:
Support for the JSON-RPC protocol and Global HTTP Batch endpoint has been deprecated, and will be fully discontinued on March 25, 2019. This change is being made to the Google API infrastucture and as such affects multiple Google APIs, including Calendar v3.
@muthoga so what your asking is can you book a table that spans more than 1 day. You could book same person on multiple dates… but @emre that might be something to look into… allowing a date Range.
I’m not planning to implement allocating time spans for tables as I believe it is not very useful for most restaurant use cases. I’ll try to keep it as a plain list of reservations as much as I can. It might not be the case but this is where I’m inspiring from actually.
@emre Just a thought would the reservation module give any statistics at all. We use it quite heavily while taking bookings. Any chance it could link when was the customer last booked in.
We find using such information while taking a booking from a customer they love it.
@muthoga as we’re still on beta please don’t install it on production database. You can test it on a separate computer and let me know if you encounter issues with your setup.
Thankyou that so kind i will test it and let you know in case i have issues ,this will also serve as a way to reserve rooms in small bed and breakfast kind of hotel.
Just realised on creating a booking customer is not automatically added to the customer table. So past reservations cant be accessed to see customer history. Also if a customer calls back to cancel no provision found for cancelling the booking.
found another bug. Booking can be entered in the past dates.
Yes, These are considered as reservation contacts. That might be an agent or person. We need to discuss if we should consider reservation contacts as customers automatically or implement some other workflow.
That will have separate report probably. Based on {REPORT TASK DETAILS}
In fact these are different things but I didn’t implemented separate functions for Cancel and No-show as I’m not sure if it is necessary or not. As @Jesse suggested you can rename button as how customer wants to see.
Yes we’ll probably need a separate validation for editor widgets.
Hmm, maybe we’ll also need min max settings as it will also accept 999999 person. I’m trying to keep widget settings simple but … hmm
I am also unable to enter Order Tags screen for items on the “Reservation Tickets”. The default Order Tags I have assigned to menu items do show up on the order line.
On a side note, I vote to have contacts entered in as customers. It would save time entering info for repeat customers.
The ticket screen order colors are more than likely state formatting. The font color on the reservation screen can be edited by editing the widget settings. Each one is a label widget.
Example change this to black or some other color… but you might want to look at it to make sure you want to do that. I am sure there was a reason he set this to a White color… you might want to match the reason with an appropriate color for light theme.
Thanks kendash, I can confirm if I change the ‘color white’ to ‘color black’. It does show up correct. However if I clear all the format fields in “Reservation Item” state, it still shows up as white text. I’m not sure is a bug or by design. Again, this is just in the “Reservation Ticket” not in the normal POS screen.
Another observation, when closing a Reservation Ticket, would it be more convenient to go back to the Reservations screen? As of now, it go to the POS screen.
What he demonstrated was really a new feature that allowed us to build a reservation system. We can modify it to our own needs. Not everyone will want the same system.
Likely you need to log out and log back in for that to take affect or create a new ticket.
