How to Setup 2nd Terminal Drive Thru

I have a system setup with a normal register station and a drive thru station. I want the drive thru station to show only drive through orders in the ticket lister.

So I created 2 departments, one is called restaurant and is assigned to the register terminal only. The other department is called DriveThru and is assigned to the DriveThru terminal only.

My problem is that the restaurant department is still showing on the DriveThru terminal at the bottom of the screen. Its mainly a problem because the drive thru computer selects that department first.

@Jesse

any ideas?
Thanks

Try filtering by department id - Eg. DepartmentID is 3

@silentbob

I did that and it shows the tickets just fine. But the problem is that the bottom tab for restaurant department still shows and everytime someone logs out and back in it selects the restaurant department by default.

Rather than having 2 departments have two menus instead and set your drive through terminal to defualt to the drive through menu and your other terminal to your main menu

That way no tabs at the bottom and the correct menu will appear on the correct machine

1 Like

Sounds easy - Rick I quickly looked through Terminals and could not find where you set Menu? Under local settings you can set your terminal but only in department you can set your default Menu…

My menu is the same I just want the tickets to be separate. But I even had them setup with tickets all showing together under one department but im still having problems. The second terminal is not showing reports or even saving transactions. Ill process a ticket with $10 and the report on the main station wont even show that in reports.

@RickH

You could use separate User for that Department and in the User Role disable can switch department. Use Entities instead of Users for your staff. Your users become Terminal A and Terminal B and maybe an admin user for full access. You use Entities for the actual POS instead of users. Using Entities as users is the most flexible option.

Sorry think i was confusing setting menus to a ticket with to a terminal

What could be the issue as to why my 2nd terminal tickets dont update my reports or why cant I even view my reports on the second terminal?

Thanks

@kendash

Your probably not connected to the same database.

I hadn’t activated the license yet soon as I did it started working adding the funds properly. Still though reports aren’t showing up on the 2nd station. It’s connected to the same database for sure

Can you show the connection string for both?

Sorry but it definitely sounds like its not connected to same database. You could easily find out by using MSSMS and looking at the Tickets table. Or double checking your connection string. Its hard for us to help without seeing it so screenshots would be great.

1 Like

I was for sure on the same database. Reports started working like 5 hours after I activated the sambapos5 license.

By the way, what would be the easiest way to achieve this. I would like to know exactly how much cash and how much credit card processing was done on each register the main one and drive thru.

@kendash Found the problem. Drive Thru Register had the wrong time, So everything was being messed up with the reports.

1 Like

Make sure you setup terminal names on each computer. Change computer names below to match your computer name.

This report will add all payments on each terminal.

Script:

Script Name and Handle: @@PaymentsByTerminal

select PT.
Name,
SUM(Amount) as Amount
from Payments
inner join PaymentTypes as PT on PT.Id = PaymentTypeId
where TerminalId in (select Id from Terminals where Name = ‘@1’)
and Date > ‘{Start}’ and Date < ‘{End}’
group by PT.Name

Reports:

Report Name: Payments by Terminal
[Payments by Terminal:1, 1]

MAIN-COMPUTER-NAME|
@@PaymentsByTerminal:MAIN-COMPUTER-NAME

DRIVETHRU-COMPUTER-NAME|
@@PaymentsByTerminal:DRIVETHRU-COMPUTER-NAME

1 Like

By (.57) I’ll create a warning on user login if there is more than 1 hour difference between local and server computer’s times. I’ve added 1 hour tolerance as it may cause an issue during daylight saving switch.

I’ve also added {SERVER DATE:<format>} tag to print server time on tickets for security purposes.

3 Likes