| Section | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
If you are adding a register you will want to start with entering a room and a register. You should have rooms already set up, but it you need to add one this can be done in the central table TRM, please follow this link Tasting Room Master (TRM). If you are adding a register just enter a number or letter that you are not already using. You will need to add a description, like our room 1, register $ is described as Wine Club Register. If you are editing you will need to choose the register that you would like to edit. You can use the drop down menu to help choose.
...
To learn more about the touchscreen itself, you can follow this link: Touchscreen Cash Register (TCH).
The Force clerk validation option, tells the system whether you would like the clerk to log in after every completed transaction. If you multiple clerks working from one register this feature helps you track what clerk rang through what order. If you have a register that is typically only used by one clerk, forcing the clerk to log back in after every transaction would be unnecessary.
...
Mode is how you want the register to process orders. If this is a back office register with no cash drawer you will want to have this option set to O for Order. This a basic setting; strictly for a register that processes back office orders. R for Register mode would be just your basic tasting room register, with a cash drawer. If you have selected T for table mode the register will behave more like a register would at a restaurant, see Tab Mode for more information on how this mode functions. P for tip mode will allow customers to leave a tip on their credit card, see Register in Tip Mode for more information on how this mode functions.
CC Verify Mode:
- S- swipe
- O- back office, processed as entered
- M- only manually processed- no swipe button
- B- batches for $ register
- A- auto verified- no card actually charged. For practice and fixit register.
Default transaction type- This an optional field. When filled in, the register will default to the transaction type so that clerks do not have to manually choose a transaction code when entering Cash Register (TCH).
Default Contra trans type-
Allow editing of line items- It is recommended that registers live with cash should say no and back office registers should say yes. Even if the clerk has permission to edit orders in the Maintain Clerk Master File (MCL), the register master will override this.
Allocations Check- This looks at wholesale or OE allocations to see if the part a clerk is ringing up is allocated to the OE customer on the Tasting Room Transaction Code (TTX) or the OE customer on the Customer Maintenance (Page 2). If the customer that is being rung up by the clerk has an OE number on page 2 of their customer record, this will override the OE customer on the Tasting Room Transaction Code (TTX). The options for the allocations check is to stop, warn or do nothing if allocations are not available for the OE customer.
Show cust tender info- This will just show the Tender type, last 4 digits of the credit card and expiration date on the Use Card on File button.
Print on act receipt- If the clerk gives a customer products for an on account order or enters in the on account transaction, this gives the clerk the option to print out a receipt if Yes is selected in this field
Default browse method for browse sales- When selecting browse sales on Cash Register (TCH), this field tells the system how to browse teh orders. The choices are to browse all orders by order number, not register specific or to browse the orders for the specific register the clerk is logged into.
AVS and CVV2- If Yes(Y) is selected, during the card process the billing address on file will be verified before the card is processed. There is also an option to only use AVS when manually entering cards. If a limit is entered in there, then the system will only check AVS on orders above the amount entered in the field. CVV2 can be required when the credit card is entered. There is also a field for limit so that if the CVV2 is set to Y and there is an amount entered in the limit field, then the CVV2 will only be required on orders over the amount entered in the limit field.
Touchscreen button code-This is the code that needs to be on the first column of the Touchscreen Button Programming (Button Spreadsheet) in order to load buttons on the register.