Button Spreadsheet Optional Codes
- Ernie Veniegas
- Samantha Speakes (Deactivated)
PART type buttons may be defined using optional codes or “Op Codes” in the definitions of "Button Value" in Column E of the spreadsheet.
Op Codes enable you to specify a value and have it applied to the named field. Op Codes are not case sensitive, and with the exception of Op Code @X for TTX codes, the sequence in which they are defined does not matter. For example, a button defined as @Dchard01@Q12@O10 to mean a 12-pack case of Chardonnay at 10% has the same meaning as @q12@o10@dCHARD01. When forcing a TTX code using the Op Code @X, it must be defined first, as shown in the image above.
Here is the complete list of Op Codes.
| Property/Field | Op Code |
|---|---|
| Customer Number | @C |
| Part Number | @D |
| Clerk ID | @L |
| Price | @M |
| Overall Discount | @O |
| Percent Discount | @P |
| Quantity | @Q |
| TTX Code | @X |
| Comment | @T |
| Promo Code | @Z |
| Coupon Code | @R |
| Event Code | @E |
| Tender Code | @A |
| Referral Code | @F |
The Customer Number @C and Part @D Op Codes have special search capabilities when defined as shown below. Usage of this feature will vary depending on your configuration and implementation.
9/7/2021 (ev) Search Customer Master also includes @C@7 - Launches the Add Partial Customer Record screen
To test the accuracy of your button definitions, you can type them directly into the touchscreen as shown below. When accurate, the item portion of the screen will show the result. Otherwise, the touchscreen will issue an appropriate message. Doing this will save you the exercise of uploading new spreadsheets repeatedly. There is a limit to how much can be programmed into a touchscreen button. We've not tried to figure out what that was – nor have we tried to break it -- but we have seen very sophisticated implementations in the field. Examples and words of cautions appear below.
Simple Examples:
To program a button that automatically sells two each of part BNCH01 at a 25% discount, enter Q2@P25@DBNCH01 in the “Button Value” column on the spreadsheet. Optionally, enter a meaningful description for the button in the “Button Text" column.
To program a button that applies a coupon code of XMAS10, enter @RXMAS10 in the “Button Value” column of the spreadsheet (Column E). Optionally, enter a meaningful description for the button in the “Button Text" column.
Suppose you are having are having a special event: event code HARVEST. On the same day, the Tasting Room is hosting its normal visitor traffic and you want to be able to track event sales and normal tasting room sales separately. Tagging event transactions with an event code would enable you to sort between the two. Define a button and enter @EHARVEST in the "Button Text" column on the spreadsheet.
Advanced Example
To change the type of an entire transaction, you would normally use the touchscreen's TRANS Selection button. This changes the transaction's TTX code. But suppose you wanted certain items in the transaction to identify with different TTX codes so you could report on them later. For example, Tastings or Tasting Fees where you want the TTX code to SA TF instead of the usual SA TR. If your part number for Tasting Fee is TASTE you could program a button by entering @XSATF@DTASTE in the "Button Value" column on the spreadsheet.
Words of Caution
TTX codes need to be compatible for them to be combined in a single Ship-to. TTX codes have default ship locations. Each location has a shipping point. If the shipping points of each location are identical, the two TTX codes may be combined. Otherwise, the @X Op Code will fail.
Once a button containing a TTX Op Code is used, that TTX code will apply to all parts added thereafter. Use the TRANS Selection button to change/restore prior TTX codes.
More Advanced Example
One common usage is defining buttons that contain all of the wines in the current wine club shipments. This is especially common when a new member joins in the Tasting Room and wants to take their club wines with them. Or, has them shipped along with other selections made that day. The examples shown force CARRY versus SHIP TTX codes, free-form text in the form of a @T comment, an @O overall discount of 15% and the quantity of each wine indicated.
