Hi guys, I have a server (sql 2017 installed) and two terminals.
On the Server I have a usb printer called Till and Lan printer called Kitchen. Which works 100%.
Terminal 1 has a usb printer called (T1printer) and I connect to server by specifying the local db settings of the server. So on terminal 1 on sambapos I set T1 printer as default printer for customer receipts and save like normal then something weird happens this setting updates on the main server.
Am I nuts or is it because its running off the servers database and pulls all config/settings from the server and if yes how can I make the Terminal 1 print using the T1Printer instead of.
You need to ensure that the printer names are exactly the same on each terminal including the server, otherwise if it is different on one system, it will change it for the others once it a print has been performed on it and you will have printer not found issues too sometimes.
Yes it does but only prints when the terminal has been restarted. But I have gone into control panel and added it as a network printer and called it server. Shows gray at the moment and I’m suspecting that the Citizent et351 goes into a standby mode or something.
I’ve thought about it and it seems that it is better to give Terminal 2 its own usb printer. The reason that there is an issue is that Server has 3 printers that are defined ie its own usb printer and 2 Lan printers in the kitchen.
And Terminal 1 and 2 pulls that settings. I will play around with it some more as server and terminal 1 and 2 are customer facing.
I just want to make sure I/we understand everything…
Your using 2 servers and 2 databases. Correct? <===== Yes that it is correct
If it is correct, you have it set up this way because of printer issues…Correct? <===== Yes that it is correct, however it was also due to Delivery report by Deliverer, could not change Delivery terminals to reflect D & order tag resulting in D1. Most importantly on Delivery terminals my client wanted the Sales department to be hidden and the only way I could do that was to clear transactions then delete the Department.
Would you rather use 1 server/database for all your transactions? I would like to use 1 server, however my client wanted it separate. (but I recommended 1 ;))
Is one of your printers a kitchen printer and 2 customer receipt printers?<===== in the kitchen we have two printers one that prints fish and the other print everything else. Our customer facing tills have 3 receipt printers as they are all customer facing(we have added more printers). Delivery server also has a printer only for when we need to print a bill if there is a issue.
I think if we get your printers sorted out, we can then use 1 server/database, then use 1 set of order numbers and tackle the different order types. <===== Is it possible to have different kitchen order Templates just for delivery. All Delivery receipts just need to have a D in front of the order tag.
I don’t have a whole lot of experiences with shared & network printers in Samba (I only use local USB printers for receipts), but there are others here that will jump in and help out. <===== I appreciate it thanks a million. It would be easier if one could just define terminal printers in Sambapos whether network or USB. By define I mean when you select a printer in terminals it changes the server printer lol when you save it.
Maybe others on this forum can share a quick overview of how they layout their infrastructure/Design i.e 1 server printer connect this way, terminals like this etc.
Thank you for the information. That paints a better picture of what the setup is like.
It sounds to me the first thing that needs to try to be done, is convince the owner that using 1 database will be easier to deal with in the long run. You may have done such a good job of setting it up, that it might be difficult.
There are 3 common way to mark tickets by order types: Departments, Ticket Tags & Ticket Types. We know the owner doesn’t want department buttons, that means Departments are out. I think the next best way would be to use a Ticket Tag.
Again, this is only one way of adding Ticket Tags.
The other big advantage of running 1 database is reports. A report can be created show how much of an item has sold. Verses looking at 2 reports and adding them together with a calculator. With Ticket Tags, a report can created to show sales for each Ticket Tag.
Without the owner getting on board with using 1 database, there is not much that can be improve from what you have setup already.
It’s a pleasure. Hope the Network Diagram is clear lol as it seems like I was scribbling. It works flawlessly on the Delivery system its just now in need of some fine tuning to get it 100% and display delivered order per driver in each column.
I like your way of selecting Order Type and we have something similar but it does not pop up. We can use Departments its just that he does not wan’t it to be displayed next to Keyboard. on the customer facing terminals he does not wan’t Delivery to display and on the Delivery terminals D1 and D2 he does not wan’t Sales and Collection to display (So its just a question of I want it that way lol hehehehehe)
We will align ourselves with whatever you guys advise as much as possible.We are looking to make full use of Sambapos so that it can run smoothly without much issues.
@Bob_be have a question we have different Ticket Template + Kitchen Order Template for our Server, OP1 and OP2 we now want to push our previously created Delivery Ticket Template + Delivery Kitchen Order Template where ticket tag we have added the D in front of it.