"Spitter" ticket

I'm sure there are numerous solutions to this but my first thought would be a separate receipt template for the drink voucher that can be printed with the ticket.  It would however be less automatic as the ticket seller would have to know which orders should be printed with the special receipt.  You could always click print a second time to print out an actual receipt for the order if both are needed.

Or, as you suggested, setup a dummy event to print the drink voucher - which could be done as a package to make the order happen automatically without selecting a line-item for both the event and the drink voucher.

Hi Ellen,

Depending on your setup, I have an idea that might work. Our test environment is in a state of flux, so I cannot test this for you. Just a theory right now.

• Create a receipt ticket design that has all of the appropriate text/data you need.
• Create a payment method called "Drink Ticket".
• Attach the receipt to the payment method in References.
• Check the Copies on Save (when the order is printed) and make the amount one.
• Have your sellers add the payment method in the payment screen for each drink ticket. For example, $50 order total paid by cash, insert Drink Ticket at $0.00.
• Print order, and your spitter ticket prints after the tickets.

It isn't automatic, but ideally quicker than building a holding tank event, adding another line item in the order, etc. Not sure how you need this reported as well.

The only thing I'm unsure about is adding a receipt to a zero-value payment, and if anything pops out without an amount. It does at the MOS level for zero-value orders, which is another possibility (Drink Ticket Phone, Drink Ticket Counter). That could get messy though. Only one receipt format can be attached to the payment method or MOS at once, hence why I tried to think of a solution that could cross all bridges.

Worth a shot! Anyone, feel free to blow holes in this if I overlooked something.

Hi Ellen,

Depending on your setup, I have an idea that might work. Our test environment is in a state of flux, so I cannot test this for you. Just a theory right now.

• Create a receipt ticket design that has all of the appropriate text/data you need.
• Create a payment method called "Drink Ticket".
• Attach the receipt to the payment method in References.
• Check the Copies on Save (when the order is printed) and make the amount one.
• Have your sellers add the payment method in the payment screen for each drink ticket. For example, $50 order total paid by cash, insert Drink Ticket at $0.00.
• Print order, and your spitter ticket prints after the tickets.

It isn't automatic, but ideally quicker than building a holding tank event, adding another line item in the order, etc. Not sure how you need this reported as well.

The only thing I'm unsure about is adding a receipt to a zero-value payment, and if anything pops out without an amount. It does at the MOS level for zero-value orders, which is another possibility (Drink Ticket Phone, Drink Ticket Counter). That could get messy though. Only one receipt format can be attached to the payment method or MOS at once, hence why I tried to think of a solution that could cross all bridges.

Worth a shot! Anyone, feel free to blow holes in this if I overlooked something.