after end work period reset ticket number automatically
You can’t reset ticket number. You will need to use update program setting action and generate your own number.
How To use update program setting action and generate your own number.
You used to to increase the setting by one on ticket created event.
Usually use that setting t add a ticket tag and use that tag on prints etc.
The make a work period ended/strted rule to clear the program setting back to one.
Its been covered several times on the forum.
Your not using the actual ticket number, this cannot just be reset like that as has to be unique for automations to work etc and database to work.
You making your own ticket tag with an increasing value which you reset each day.
I would maybe try and avoid calling it ticket number to save confusion.
Customer number or que number or something will help you keep it seperate in your head.
Emre quoted the following in another thread. Can we just do this instead? Is it a big deal that there is duplicate ticket numbers between each day since we use ticket ID to really track a ticket?
If you are familiar with SQL you can run this SQL Script to set Ticket Number generator value.
warning Never use it to update it to zero or past values on production system since it leads to duplicate ticket numbers
Update Numerators set Number = 29119 where Name = ‘Ticket Number Generator’
No. Don’t do that. You do NOT want duplicate Ticket Numbers as Emre warns …
WARNING: Never use it to update it to zero or past (previous) values on production system since it leads to duplicate ticket numbers
That is very bad. You do NOT want to be messing with the Ticket Number, nor the Ticket ID. You should be using a Ticket Tag instead if you want something you can reset.
Okay thank you for clearing that up.
Observing several other restaurants and posts here, I think there is a demand to have a number that resets every once a while like a work period and/or end of day…
However, since the facilitates provided in SambaPOS are all based on Ticket No. and Ticket ID, is there a possibility to consider this format to support both worlds?
date.period.count where count can be reset by user at will
The current ticket lister and such will use the count in the front end of SambaPOS with implied date and period info while using the full format when there is a need to id an unique ticket.
this should address the need for shorter no. (like in the credit card machine which only displays the sequence no. of the period) while maintaining a way to properly ID the unique ticket when needed to by display the suffice together
I see the current demand for a resetting no. is that many users want a shorter number to work with during normal operation especially for people who are general workers like a cashier rather than a programmer or tech guy like us who can appreciate the precision of a long number.
There is functionality to do it though… It just doesn’t come pre-setup…
You can setup a resetting number and it’s not too difficult. So to answer you, sambapos already has this feature available you just need to configure it.
I think you guys are talking about setting actions and rules to implement the “Order No” as in the earlier versions. However, I am more into talking about the number appearing in the build-in features of SambaPOS such as the Ticket No that appeared in the Ticket Lister and the Ticket No that appeared in the Order Screen when the ticket is Unpaid. My current length of the Ticket No is only 5 digits and my #@$%%^T cashier and #$%^# Mgr are already complaining, therefore I assume many users of SambaPOS will run into having similar workers. So I feel it would be helpful to be able hide the longer no. in the lister and use the shorter number for the daily work as build-in rather than program it using ticket tags. I understand, I can put ticket tag in prints easily but I have a hard time trying to put it on the top of the order screen as prominent as where the build-in Ticket No. is.
You can use a ticket header similar to what RickH does and display your resetting ticket No. There is absolutely no reason you can not configure what you want. I wouldnt hold my breath waiting for any built in turn key solution.
You do not have to use Ticket Tags, there are numerous other methods, including creating your own with scripting.
You will not be able to change that one, its hardcoded ticket number.
You do not want to have this resetting as will cause conflicts in your system.
A custom resetting ticket/ordernumber can be created and set through numorious ways (ticket tag, ticket state to name a couple)
I knew these two points
and I now know this part after you confirmed it.
LOL
You can create ticket header above and display whatever you want but that ticket number will always be there.
But you will still want to use a ticket tag or state or something in order to be able to use and report the resetting number.
It can go in the header aswell but header value will not be reportable or printable on its own.
That is a really old setup haha where you find that pic lol
Was going to say the same, a freshly created ticket doesn’t show the number but it’s there after closing the ticket.