Abstract: Systems and techniques for linking electronic shelf labels to and unlinking electronic shelf labels from a system. When a printed overlay for an electronic shelf label is prepared, a radiofrequency identification (RFID) tag is affixed as part of the overlay. The RFID tag provides an identifier associated with a product. When an ESL to which the overlay is affixed is to be linked, the RFID tag is read at substantially the same time the ESL is interrogated, and the product associated with the RFID tag identifier is associated with the ESL. When an ESL is to be unlinked, a communication including an identifier for the ESL is provided to a central data processor, with the communication having characteristics indicating that the ESL is to be unlinked. When a communication is received from an ESL, the characteristics of the communication are evaluated to determine if the ESL is designated for unlinking.

Abstract: Systems and techniques for locating designated electronic shelf labels. A locator device transmits commands to a designated label, causing a label to take on distinctive characteristics, for example showing a characteristic display. Alternatively or in addition, the locator device detects transmissions from labels within range and provides an indication, such as an audible tone or a serial number display, when an identified label is within range. A user may enter a serial number of one or more labels using a keypad, or may upload one or more serial numbers to the locator device. The user then moves with the locator device around a location where labels are in use. Depending on the design of the device, the device broadcasts commands to labels to cause the labels to take on identifiable characteristics, detects serial numbers of labels based on transmissions from labels within range, or both.

Abstract: Systems and techniques for calling attention to loss of communication with an electronic shelf label. One or more of a plurality of labels deployed in a location may be programmed with a message to be displayed or an action to be taken if communication is lost. The labels may be programmed with a scheduled action that will cause a label to take the programmed action or display the programmed message if communication with the label does not occur by a specified time. Communication with the label causes the action or event to be rescheduled.

Abstract: In one aspect, the ESL system automatically detects ESL communication errors which result in incorrect data in the ESL's registers, and then automatically takes corrective action to update the ESL's memory with the correct data. In one aspect, the host computer transmits a register update message to an ESL. If a negative acknowledgment message or no response is received, then the host computer resends the register update message, or takes other appropriate corrective action. If the host computer receives a positive acknowledgement message, the host computer then automatically transmits one or more messages to the ESL to verify the contents of the ESL's registers to ensure that a positive acknowledgement was actually transmitted.

Abstract: An electronic price label (ESL) system for performing recurring ESL transactions which occur in a periodic fashion. In one aspect, an ESL manager records and schedules messages to the ESL. When a transaction request directed to an ESL is created or issued by a client application, multiple pieces of information may be provided by that client to the ESL manager, indicating what action is to be taken. To allow for the scheduling of recurring transactions, recurrence information for the transaction may also be specified by the client application. The recurrence information may include a start date and time, and a recurrence period. After the transaction has been processed, the ESL manager looks at the recurrence period and if the recurrence period is a non-zero value, the ESL manager adds the recurrence period to the start date and time to generate a new start date and time.

Abstract: An electronic price label (ESL) system for performing recurring ESL transactions which occur in a periodic fashion. In one aspect, an ESL manager records and schedules messages to the ESL. When a transaction request directed to an ESL is created or issued by a client application, multiple pieces of information may be provided by that client to the ESL manager, indicating what action is to be taken. To allow for the scheduling of recurring transactions, recurrence information for the transaction may also be specified by the client application. The recurrence information may include a start date and time, and a recurrence period. After the transaction has been processed, the ESL manager looks at the recurrence period and if the recurrence period is a non-zero value, the ESL manager adds the recurrence period to the start date and time to generate a new start date and time.