...
| Section | ||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Tip | ||
|---|---|---|
| ||
When creating a new register, it It is easier to model an existing one, rather register when creating a new register than starting from scratch. To do so...
Modify the new register's description and save as usual. Before processing transactions with the new register, contact AMS to complete setup and associate the new register to the appropriate winery Merchant ID. |
...
Every register has a unique three-digit terminal number. Its number identifies it to peripheral hardware attached to your system. The number can be arbitrary as long as it is unique and is a numeric value. A common practice is to assign terminal numbers based on its tasting room and register ids. For example, Tasting Room 1 Register 3 would get Terminal Number 103. Tasting Room 2, Register 1 would get terminal number 201, etc. Of course, this will not work with Tasting Rooms or Registers that are not numeric values. In which case, assign the register a unique numeric value.
...
- If set to No, the entered line item cannot be changed. If corrections are required, the line item must be voided and completely reentered instead.
- If set to Yes, the already-entered line item can be selected and changed. This register-level setting overrides clerk-level permissions explained in the Maintain Clerk Master File (MCL) documentation.
| Info | ||
|---|---|---|
| ||
"Yes, allow editing" is how the majority of users define their registers. Why would the system behave this way in the first place? Experienced users will likely find this setting a nuisance. Mistakes happen. And it's infinitely easier to correct an existing entry, rather than having to void the entire line item and start over. However, this register behavior is particularly helpful when training or onboarding new staff. A review of their transactions will reveal where additional training may be required. The setting also provides management with a more detailed audit trail of transaction entry activity. The system maintains a record of every line item that was entered, voided, and reentered, providing a visual record of what took place during order entry. Such an audit trail helps management recreate the steps the clerk went through before tendering the order for payment. |
Default browse method
The touchscreen Cash Register (TCH) provides clerks with a way to browse for entered orders. This option determines the default browse method. That is, to scroll orders by an order number, or to scroll orders by the register ID the clerk is logged into.
Allocations check
(After successful payment processing and saving the order, this setting also prevents the register from accessing "order options" and making any changes.
Default browse method
The touchscreen Cash Register (TCH) provides clerks with a way to browse for entered orders. This option determines the default browse method. That is, to scroll orders by an order number, or to scroll orders by the register ID the clerk is logged into.
Allocations check
(unedited original text) 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 are to stop, warn or do nothing if allocations are not available for the OE customer.
...
| Tip | ||
|---|---|---|
| ||
Using this register option will grow your direct email list and enhance maintaining order history. The system saves every email address used to send a receipt into the CRM database. Over time, this will result in the growth of your direct email list. Here's how.
|
Print "On Account" Receipt
This Yes/No option controls whether or not the register gives the clerk the option of printing receipts for transactions tendered "On Account." This is a seldom-used feature and is reserved for CRM customers that are set up in advance with an OE A/R Order Entry Accounts Receivable account number. OE A/R information is defined on Page 2 of the MCM Tasting Room Customer Maintenance Screen as shown below.
Remind Clerk of Register's Identity in CRM and ORM
This register setting controls whether or not to alert or remind the clerk of their register's identity when used to add or edit orders. Why? Each register identifies with a Merchant ID Code. It defines the account where transactions processed by the register will post.
- For wineries having only a single Merchant ID, this register option is best set to "N, No, don't display alert."
- For wineries having multiple Merchant IDs, use register option 1 or 2.
| Info | ||
|---|---|---|
| ||
This setting may or may not be of value to you. For example, if transactions for a winery's Retail, Wine Club, and eCommerce businesses identify with different merchant ID Codes, this register setting will cause the system to display a screen, reminding the clerk of the register they are using to process transactions. This is of value if you want to remind clerks to use a register that has the same merchant ID code when making additions or corrections to process orders. For example, a wine club order rung under the $ Register, and the wine club's merchant ID should be modified or credited with another register having the wine club's merchant ID. Doing so ensures all debits and credits occur in the same merchant account. Not doing so will result in transaction amounts posting across multiple merchant accounts. |
Codes
Touchscreen button code
...
Default trans type/cat (opt)
This optional code pair tells the system what is the register's default TRT and TTC together referred to as the TTX code.
When initiating transactions, a default TTX code makes it unnecessary for clerks to have to choose one manually. For example, tasting room registers are typically set up with a default TTX code like SA TR meaning a "Carry sale from the Tasting Room" because that is the most common transaction type and category for the tasting room. In contrast, back-office and customer service registers are typically set up with a TTX code like SH WC or SH TS meaning a "Ship Sale from the Wine Club" or "Ship Sale from Telesales" because SHIP transactions are the most common transaction type used. See Cash Register (TCH) for more information.
Default contra trans type/cat (opt)
(Adeptus Astartes - please help here) This optional code defines what would be the opposite of the default transaction type/cat (TTX). In the example, TRT SH (Ship) is the default "contra" of TRT SA (Carry).
Or, it is used when the default TTX code is not itself defined in Central Table TTX with a return transaction type/cat code??
(original docsite text) 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.
|
Print "On Account" Receipt
This Yes/No option controls whether or not the register gives the clerk the option of printing receipts for transactions tendered "On Account." This is a seldom-used feature and is reserved for CRM customers that are set up in advance with an OE A/R Order Entry Accounts Receivable account number. OE A/R information is defined on Page 2 of the MCM Tasting Room Customer Maintenance Screen as shown below.
Remind Clerk of Register's Identity in CRM and ORM
This register setting controls whether or not to alert or remind the clerk of their register's identity when used to add or edit orders. Why? Each register identifies with a Merchant ID Code. It defines the account where transactions processed by the register will post.
- For wineries having only a single Merchant ID, this register option is best set to "N, No, don't display alert."
- For wineries having multiple Merchant IDs, use register option 1 or 2.
| Info | ||
|---|---|---|
| ||
This setting may or may not be of value to you. For example, if transactions for a winery's Retail, Wine Club, and eCommerce businesses identify with different merchant ID Codes, this register setting will cause the system to display a screen, reminding the clerk of the register they are using to process transactions. This is of value if you want to remind clerks to use a register that has the same merchant ID code when making additions or corrections to process orders. For example, a wine club order rung under the $ Register, and the wine club's merchant ID should be modified or credited with another register having the wine club's merchant ID. Doing so ensures all debits and credits occur in the same merchant account. Not doing so will result in transaction amounts posting across multiple merchant accounts. |
Codes
Touchscreen button code
This code tells the system what Touchscreen Button Programming (Button Spreadsheet)to load when the register is used.
Default trans type/cat (opt)
This optional code pair tells the system what is the register's default TRT and TTC together referred to as the TTX code.
When initiating transactions, a default TTX code makes it unnecessary for clerks to have to choose one manually. For example, tasting room registers are typically set up with a default TTX code like SA TR meaning a "Carry sale from the Tasting Room" because that is the most common transaction type and category for the tasting room. In contrast, back-office and customer service registers are typically set up with a TTX code like SH WC or SH TS meaning a "Ship Sale from the Wine Club" or "Ship Sale from Telesales" because SHIP transactions are the most common transaction type used. See Cash Register (TCH) for more information.
Default contra trans type/cat (opt)
(Adeptus Astartes - help here)
Sales Channel Code
(copy needed - none in original docsite)
...
Credit Cards
CC verify mode
(Adeptus Astartes Astartes - I need some help here.)
CID/CVV2 prompt, at amount (optional)
...