Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha Quick Service vs. Table Service

Status
Not open for further replies.

JRNYC

IS-IT--Management
Feb 9, 2016
45
US
I once again apologize for my ignorance and hope this awesome community can shed some light on things for me.

What exactly is the difference between Quick Service and Table Service? Are these completely separate products or just forms of configuration?

Here is my situation, my restaurant is a traditional fine dining environment. We use Aloha Table Service version 12, Manager version 15.

We are opening a fast casual breakfast/lunch restaurant which is physically part of our establishment. They will be using shared inventory, and we want to treat the fast casual as a different revenue center.

But the owners are concerned about our on screen ordering menus and how well they will function for the fast casual.

Our sales rep says we should be fine using a bar menu, and I am currently trying to teach myself the screen designer to make some custom submenus.

So I guess I am asking if this sounds plausible. Can we create some submenus that will allow us to operate our fast casual restaurant. Stylistically we will be like Chipotle. You choose a base food bowl and then we ring up several different custom modifiers and the cost changes appropriately.

Thank you in advance!
 
Quick Service and Table Service are separate products.
While it won't be as seamless and easy as using QS the submenus should work out pretty well.

Will the terminal in the QS area be dedicated to breakfast/ lunch or will it be converted in the evening?
 
We are installing 2 dedicated terminals in the new break/lunch service area. No current plans to use them for the evening service.

 
for the fast casual, set them to use tabs and not tables for faster ordering. like the bartenders. So the sales fall under a different revenue center. Create a new revenue center, create new job code and assign then that revenue center. then your sales by revenu center will separate the 2 entities

Quick service is used in places like Burger King. Starbucks, WhichWich, Noahs Bagels. places where you would order, pay and wait to get order. Using tabs will allow them to have the same speed by not first asking for name of customer before closing

AlohaRoss
3rd Party support
 
I was going to suggest assigning the revenue center to the terminal since they're going to be dedicated. That way you can use the same employees/ same jobcodes.
Either way will work out.

Good tip on using tabs Ross, I hadn't considered that.
 
I concur on the tabs. Been doing a lot of reading and haven't encountered that one yet!
 
Clay, I dont like to assign revenue centers to terminals as staff have a way of wondering to any open terminal to order. Having been a waiter, bartender and restaurant manager I have seen staff use whatever is fastest and convenient for them. Setting up revenue by job code eliminates those errors. Also I have used order panels instead of sub-menus for gift shops, fast casual ect. You have more options with button functions and order panels than with basic aloha sub-menus and tabs

AlohaRoss
3rd Party support
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top