There is no option for this for new items printed to the same printer. They are printed in the order they are added to the transaction, period. The only possible work-around would be to have a second printer — one that appetizers are routed to and one that mains are routed to. But that wouldn’t solve the problem when some people order appetizers as mains and when that happens then all bets are off, eh?
Having said all of that, are you saying that servers are just keying in entire orders — appetizers and mains, etc — at one time and firing them? If that is the case, Square for Restaurants has a coursing option that you could use, allowing servers to fire courses to the kitchen as needed. Otherwise, it seems that another easy solution would be the old-fashioned one — servers enter food and fire it as it is needed — appetizers first, then when the time is right, enter/fire the mains. You might find restaurant coursing feature works for you.
Unfortunately I don't use Square for restaurants, do you @TheRealChipA ?
It sounds like something that would definitely make sense
There is no option for this for new items printed to the same printer. They are printed in the order they are added to the transaction, period. The only possible work-around would be to have a second printer — one that appetizers are routed to and one that mains are routed to. But that wouldn’t solve the problem when some people order appetizers as mains and when that happens then all bets are off, eh?
Having said all of that, are you saying that servers are just keying in entire orders — appetizers and mains, etc — at one time and firing them? If that is the case, Square for Restaurants has a coursing option that you could use, allowing servers to fire courses to the kitchen as needed. Otherwise, it seems that another easy solution would be the old-fashioned one — servers enter food and fire it as it is needed — appetizers first, then when the time is right, enter/fire the mains. You might find restaurant coursing feature works for you.
