So I was thinking about it… and had a thought… what if we created a new Department called Time Clock… and we created tickets and a timeclock menu that only has clock in and out and break… this way we could track time clock with users instead of entities and also you could edit the time clock punches easier and all kinds of stuff. Not sure how well it would work or not but just a thought. What do yall think?
I do not understand what your saying. Are you saying use tickets to track punches? That doesnt sound like a good idea.
Maybe you missed what I said. You can use Users it just has to be linked to an Entity. Is there a reason you do not want to use Entities?
I dont understand how you would edit punches at all doing this.
Tickets are not designed for that purpose. Just like Tickets are not designed for purchasing Inventory.
What do you mean? Use Orders as Punches? Then void them to make corrections?
I beg to differ. IMO, the Timeclock and Punch Editor work great.
Give it a whirl. Show us what you come up with. 
1 Like
Im just asking if you guys think it will work? Tickets already keep time for being open and closed… they also keep track of who opened the ticket and who added orders or tags… and you can reopen a closed ticket and add another order or void one so you can even keep track of the mistakes with the voids… just an idea… i might give it a go and see what i can do. I just dont want to add employee entities because if you have a restaurant that has over 20 employees and they change every other week cause the servers and dish washers and cooks all cant keep a job longer than a year. Keeping track of employee entities is going to be a pain.
How is it different than keeping tack of users?
You have a point there… I thought that the reason everyone switch to entities was because they couldn’t keep track of a user without using entities.
Actually I switched because entities are better in fact Emre even discussed switching users over to entities. Entities are more flexible and offer so much better control. I have to say I would support Users being switched to Entities. It would simplify Time Clocks and you could allow Entities to Log in the system if you wanted. But right now its not that way.
You can link users to entities fairly easily. With Configuration Tasks you could automate the management of Employee Entities this is exactly what I have done with my latest Time clock. I never actually mess with Entities anymore I just use my Config Task it will add or remove the Employees and even create or remove their reports automatically with one operation.
Yea the main thing about the time clock that doesnt work for us is that you have to put in a pin every time you try to open the pos section to create tickets which means you need to setup a defualt user and keep them logged in the whole time… How would you link the entity to the user or just track the users time between clocking in and clocking out and be able to edit that if needed. Not sure… Really ive been looking into just doing a software called TimeClock MTS. Its only 80 dollars for the standalone version and its got a kiosk mode and touch screen compatible… ,Might just set it up on a cheap windows tablet and call it a day.
The time clock I posted is a highly customized one specific for my own needs. You could customize it to do just about anything you want, however @QMcKay has a very basic time clock you might want to look at his tutorial. Mine adds some very advanced customization and most people may not want it. It alters the entire flow of your POS.
I shared mine to show whats possible mostly but I didnt expect a lot of people to want that flow honestly. Mine is designed for strict Employee Accountability.
Which one is it?.. you have a few on here hahah.
There are only two tutorials in v5 tutorials category. His and Mine. Here is a link to his:
Here is a link to his punch editor tutorial as a supplement to his basic clock.
PS: Me and Q are the only two that has built a time clock or put any effort into it. So it should be easy to find them 
Our basic system works almost identical. It works very well and honestly I see no need to invest in third party software unless you want full complex payroll.
You could even make an Entity Screen and use Badges to swipe to clock in and out with. It would be the most basic form of time clock.
2 Likes
Hey, I followd the instructions and whenever I go and add an Employee to the config task it jsut says Task Cancelled
It’s possible it’s conflicting with something in your setup. I’ll test it with latest version to make sure something didn’t break it.
@the133448 I just tested the config task on a fresh database with latest version and it works just fine. So we would need to know more about your setup to understand whats causing your issue.
Ok I just made a fresh database, this is what happens.
Clic,k the configuartion task
Enter the employye number,pin,number,pay
Question> Do you want to enable time clock
Click yes
Message-> Task Cancelled
What version of SambaPOS are you using?
Also can you show your settings where you entered the GIST url.
Is it giving any kind of error?
I have tried to reproduce that behavior and it works just fine for me every time.
Latest realse, Havent changed any settings of the fresh database, should I?
Hmm I can’t figure out what’s going on with your system. I can’t reproduce that.
@Jesse, Finally got around to implementing this, thanks a lot for your work and the easy configuration task. Kudos.
Quick question,what’s the difference between “view original” and “view actual” punches. I assumed they were something to do if the admin edits a punch.
Can you take a quick look at the gif below and let me know if this is normal? The time and operator ID seems to change when i click view actual (or original) punch.
