Datalogic PreScan, Руководство по продвинутой настройке

Страница: 62 / 84

Using PreScan
60 PreScan™ Queue-Busting System
second customer in the queue will offer use of her card in order to obtain price discounts. If the
second customer received PreScan service tied to the loyalty card, all her purchases will be added
to the first customer's total. Stores planning to use loyalty cards for Prescanning should carefully
consider strategies for educating uninitiated customers.
Creating Control Card Bar Codes
The bar code on control cards should be Code128 at least 10 mil (ideally 13 mil or larger) and
preferably 25mm high to allow for most efficient scanning by the Magellan. It needs to contain
the following data with human-readable text below it:
<Header><Unique Code Number>
See above for an example of a completed control card.
Header:
<[FCN3][PSABCD]>
The header is code 128 special character
<FCN3>
which is unprintable, followed by the letters
PS
, then four alpha-numeric characters. The final four characters can be anything and are
ignored by the scanner.
Unique Code Number:
The unique code number can be any number in the range of 00001 to 99999. Each customer
using the system at a given time must have a unique number. Duplicate customer numbers
could cause potential loss of a customer's data or accidental merging of transactions.
Loyalty Cards
In-Store Loyalty Card:
EAN13 starting with “24”:
24<Customer ID Number>
or
UPCA starting with “4”:
4<Customer ID Number>
Magellan Programming
To configure the settings for how the Magellan handles Control Cards, see
Magellan Options for
PreScan Control Cards,
starting on page 49.
DO NOT scan the Switch Bar Code in conjunction with the Unique Cus-
tomer Bar Code. It is not a programming label.