Specifies whether or not to maintain the entire items table locally. If TRUE, only those items that need to be present to support the local item tree are maintained. Retail salespoints don’t use the item tree to any extent, so their local item set doesn’t need to be limited, so this setting is usually FALSE. TRUE causes a salespoint to hold a local copy of only those items in its assigned item tree.

Based on the number most frequently used for tracking item barcode scanning, set the lookup order to speed lookups.

 

Barcode, UPC, Invent_ID, Multicode, etc. The system searches in the order specified and returns the first match found.

Note: Invent_ID is created by the system in the items table for tracking items and the i_items table for matrix items. Because they are created sequentially, it is possible for the Invent_ID to be the same for both a tracking and a matrix item. If Invent_ID is being used for only one inventory type, make sure that it is not in the lookup order for the other type. If there is a need to use the Invent_ID for both tracking and matrix items, the retail labels that encode the Invent_ID must have a -m prefix for matrix items and a -I prefix for tracking items.

Based on the number most frequently used for matrix item barcode scanning, set the lookup order to speed lookups.

 

Barcode, UPC, Invent_ID, Multicode, etc. The system searches in the order specified and returns the first match found.

Note: Invent_ID is created by the system in the items table for tracking items and the i_items table for matrix items. Because they are created sequentially, it is possible for the Invent_ID to be the same for both a tracking and a matrix item. If Invent_ID is being used for only one inventory type, make sure that it is not in the lookup order for the other type. If there is a need to use the Invent_ID for both tracking and matrix items, the retail labels that encode the Invent_ID must have a -m prefix for matrix items and a -I prefix for tracking items.

More than one operator may be using one Retail salespoint. If Closing by Operator, this helps keep things straight. Also important for security regardless of closeout method if the retail sales staff is on the floor and not always behind the sales counter.

If zip codes are being collected at admission salespoints, there is no need to do it again at Retail salespoints.

If one or more matrix items have a salespoint button, this entry must be used to sell.

If both include the entry <i_items->descrip> so that size, color, etc., display for matrix items.

Creates an Inv. Lookup button.

Used to maximize invoice space when item buttons are not a factor.