JP4450877B2 - Apparatus and method for correcting price lookup file in electronic price label system - Google Patents

Description

[0001]
[Industrial application fields]
The present invention relates to an electronic price label (hereinafter “EPL”) system, and more particularly to a system and method for determining price differences between price look-up (hereinafter “PLU”) files.
[0002]
[Prior art]
Traditional retail bar codes rely on price information maintained in PLU files. The PLU file is usually stored in a single location provided on the host server. However, some stores have an in-store processor (hereinafter referred to as “ISP”) and one or more point-of-sale (hereinafter referred to as “POS”) POS servers. In many cases, the ISP PLU file is the primary PLU file. The POS server acquires the PLU information from the ISP PLU file, and the chuck-out terminal acquires the PLU information from the POS server PLU file.
[0003]
Typically, an EPL system includes multiple EPLs for each item in the store. The EPL displays the price of the corresponding product on the shelf of the store, but is usually mounted on a rail at the leading edge of the shelf. EPL systems typically get their prices from the POS server PLU file. One store may have thousands of EPLs for displaying product prices. The EPL is connected to a central server, and information about the EPL is usually managed and maintained in an EPL data file. This EPL data file includes EPL identification information and EPL product information.
[0004]
[Problems to be solved by the invention]
In an EPL system that obtains price information from double PLU files, price mismatch can occur. POS server PLU files often lose synchronization with ISP PLU files. When such loss of synchronization occurs, an EPL that displays the wrong price occurs. Therefore, it is an object of the present invention to provide a system and method for determining a price difference between an ISP PLU file and a POS server PLU file.
[0005]
[Means for Solving the Problems]
In view of the above problems, the present invention has a first PLU data file. In-store processor When, A POS server that receives the first PLU data transmitted from the in-store processor, creates a second PLU data file, and stores it And the above two In the PLU data file of An electronic price label system having a plurality of electronic price labels for displaying commodity prices, wherein the computer of the electronic price label system includes means for reading the first PLU data file, Means for reading the PLU data file, means for comparing and comparing the commodity price in the first PLU data file with the commodity price in the second PLU data file, and the commodity in the first PLU data file Means for recording products having different prices and product prices in the second PLU data file, and PLU data relating to products having different product prices in the two PLU data files is stored in one of the PLU data files. To match the product price of In electronic price label system A PLU data file correcting apparatus and a correcting method thereof are provided.
[0006]
【Example】
Hereinafter, an electronic price label system according to the present invention will be described in detail with reference to the accompanying drawings. As shown in FIG. 1 to which reference is made, a preferred trading system 10 includes a POS computer system 12, a checkout system 14, an EPL system 16, and an ISP computer system 18.
[0007]
A preferred POS computer system 12 includes a bar code scanner 19 and a terminal 20.
[0008]
A preferred EPL system 16 includes an EPL 22, a host EPL terminal 24, and an EPL storage medium 26.
[0009]
Usually, the EPL 22 is mounted on a shelf in the store and includes a data register 54 and a display 56. The data register 54 normally contains data that is the price of the related product in the EPL provided on the shelf. This data is usually displayed on the display 56.
[0010]
The host EPL terminal 24 executes EPL software 30. This software manages and maintains the contents of the EPL data file 32. The EPL software 30 includes an application program interface (API) 33. This interface has a relay function for the operating system 52 or the POS software 31. For example, Novell and IBM's UNIX and OS / 2 operating systems and NCR Corporation's UNITY POS software have commercially available APIs for use therein. The EPL software 30 includes an independent set of applications 35 having a relay function for the API 33.
[0011]
The host EPL terminal 24 also executes a POS server PLU file reader (hereinafter referred to as POS server PLU file reader) 38, an ISP server PLU file reader 39, and a PLU verification application 48, all of which It is compiled so that it can be executed by the operating system 52 or the POS software 31 as required by the institution. The POS server PLU file reader 38 directly accesses PLU information in the PLU data file 44 resident in the POS computer system 12. The ISP server PLU file reader 39 directly accesses the PLU information in the PLU data file 60 resident in the ISP computer system 19. The PLU information is preferably product identification information and price information.
[0012]
The POS server PLU file reader 38 is linked to the API 33 via inter-process communication and includes a PLU file read routine 43. This PLU file reading routine 43 causes the POS software 32 or the operating system 52 to read the PLU data file 44 in cooperation with the API 33 and transfer the PLU information to the PLU collator 48. The PLU file read routine 43 also cooperates with the API 33 to pass the PLU information to the electronic price label (EPL) software in the POS software 31 or operating system 52 so that the EPL software 30 can manage the price displayed by the EPL 22. 30.
[0013]
The ISP server PLU file reader 39 is also linked to the API 33 via inter-process communication and includes a PLU file read routine 45. This routine 45 cooperates with the API 33 to cause the POS software 31 or the operating system 52 to read the PLU data file 60 and transfer the PLU information to the PLU collator 48.
[0014]
Advantageously, even if the PLU file readers 38, 39 are created and put into the system 10, none of the other applications 35 need to be changed. When the PLU reader 38 is connected to the API 33 via interprocess communication, the API 33 does not involve the application program 35 independent of the reader 38 in the details of the PLU management maintenance routine 50 and the PLU data file 44. PLU reader 38 masks the price information in PLU data file 44 into a displayable format for EPL system 16. In many EPL systems, data format 9 / 9.99 (9 versus 9.99) or format 99.99 is the maximum price indication. As another example, data format 2 / 12.40 is masked in displayable information 6.20, and data format 10 / 1.10 is displayable information. 11 is masked.
[0015]
This method is advantageous for processing an advanced pricing method. For example, one of the customers may desire to display price information for a product that “buys one for a purchase”, unlike price information for other products. Since the PLU reader 38 makes this change once, other applications that are not related to this change need not be modified.
[0016]
Similarly, when the PLU reader 39 is connected to the API 33 via interprocess communication, the API 33 does not involve the application program 35 unrelated to the reader 39 in the details of the price management application 58 and the PLU data file 60.
[0017]
The EPL storage medium 26 stores the EPL data file 32 and the log file 49, and is preferably a fixed display drive.
[0018]
The POS computer system 12 includes a PLU storage medium 36, a host PLU terminal 40, and an input device 42.
[0019]
The PLU storage medium 36 stores a PLU data file 44. The PLU file 44 contains price information that can be distributed to the POS terminal 20 by the host PLU terminal 40. A bar code scanner 19 for directly accessing the PLU file 44 from the host PLU terminal 40 is also prepared.
[0020]
The host PLU terminal 40 executes the POS software 31 and the PLU management maintenance routine 50. The PLU management and maintenance routine 50 is controlled by the POS software 31 to update the PLU file 44, prepare the system 12 for loss of the PLU data file 44, and execute a PLU data recovery procedure.
[0021]
A preferred input device 42 is a keyboard. The input device 42 makes a change to the PLU data file 44, and this change includes a price change that is necessary following the execution of the PLU collator 48.
[0022]
When a price change is input to the input device 42, the PLU management maintenance routine 50 directly sends the price change stored in the PLU file 44 to the EPL terminal 24 and the POS terminal 20 (immediately). Processing) or price changes can be stored in a batch file for later batch updates (batch processing).
[0023]
The ISP computer system 18 includes a PLU storage medium 59, a price management server 57, and an input device 55.
[0024]
The PLU storage medium 59 stores the PLU data file 60. The PLU data file 60 contains price information that can be distributed to one or more POS computer systems 12. The PLU data file 60 is a primary PLU file in the system 10. Changes to the PLU data file 60 are sent to all POS computer systems 12 in the system 10.
[0025]
The price management server 57 updates the PLU file 60 and sends changes to the PLU data file 60 to all POS computer systems 12 in the system 10.
[0026]
A preferred input device 55 is a keyboard. The input device 55 makes a change to the PLU data file 60, and this change includes a price change that is necessary following the execution of the PLU collator 48.
[0027]
When the price change is input to the input device 55, the price management application 58 can directly send the change of the price stored in the PLU file 60 to the POS server 40 (immediate processing), or a later batch. Price changes can also be stored in a batch file for update (batch processing).
[0028]
During normal operation, the EPL terminal 24 executes the POS server PLU file reader 38 to execute the PLU data file 44.
Get price information. The EPL software 30 sends the price information to the data register 54. The display 56 displays this price in the data register 54.
[0029]
The EPL terminal 24 also executes a price management server PLU file reader 39 and a PLU collator 48. The price management server PLU file reader 39 reads price information from the PLU data file 60.
[0030]
The PLU collator 48 compares the PLU data file 44 and the PLU data file 60 to determine a product that does not have the same price in both files 44 and 60. The PLU collator 48 stores the product and price in both files in the log file 49. Log file 49 can be viewed using display 37 or can be printed using printer 34.
[0031]
Here, although the terminals 20, 24, and 40 are illustrated as separate components connected by a network, they can also be combined in other ways. For example, the EPL terminal 24 and the host PLU terminal 40 can be combined to configure the POS terminal to also act as a network host computer for other POS terminals.
[0032]
Reference is now made to FIG. As shown in this figure, the components used to configure the POS server PLU file reader 38 and the price management server PLU file reader 39 include a template PLU file reader 63, an object code 62, mapping and translation. An example mapping and translations 64, a target routine 66, and a make file 68 are included. The template PLU reader 63 is an aggregate including a mapping / translation sample 64 and a target routine 66. The mapping and translation sample 64 and target routine 66 are edited and customized by the system developer to generate a customized mapping and translation routine 65 and customized target routine 67 (customized template PLU 61). PLU file read routines 43 and 45 are examples of customized target routines. Customized mapping and translation routine 65 and customized target routine 67 are sent along with object code 62 in makefile 68 to generate code that is executable for POS server PLU file reader 38 and price management server PLU file reader 39. It is done.
[0033]
The object code 62 includes a library 41 that provides an interface to the API 33 and isolates other EPL applications from the API 33. As a result of this isolation, the POS server PLU file reader 38 and the price management server PLU file reader 39 can work together. The functions included in the library 41 include module activation, opening a PLU data file, connecting an application to the PLU data file, closing an application connection to the PLU data file, closing a PLU data file, And application termination.
[0034]
The mapping and translation sample 64 provides information that cannot be displayed (in code or document form) and can be edited to customize the POS server PLU file reader 38 and price management server PLU file reader 39.
[0035]
The target routine 66 can be edited and customized to meet the requirements of the target trading institution.
[0036]
The make file 68 is a file for generating a target executable by passing the source code (template 63) through the compiler 72 and then passing the object code 62 through the linker 74.
[0037]
Reference is now made to FIG. As shown in this figure, the method for generating a general purpose POS server PLU file reader 38 and a price management server PLU file reader 39 begins at start step 80.
[0038]
At step 82, the independent application 35 is isolated from the PLU data file (ie, PLU data file 44 or PLU data file 60) through a hidden mapping determination and translation process. As a result, a mapping and translation sample 64 is obtained. This newly developed outcome is designed to allow customers to customize in the future.
[0039]
At step 84, a template 63 is provided. The template 63 is packaged in a format that can be distributed and placed on the target system.
[0040]
At step 85, a customized mapping and translation routine 65 and a customized target routine 67 are defined so that all information for the EPL can be displayed. The connection method adopted for the target system is also determined.
[0041]
In steps 86-92, a customized template 61 is generated by modifying the template 63 to reflect the customized mapping and translation routine 65. This work is performed by a developer in charge of integrating the target customer's EPL system 16. Integration and customization are performed according to customer instructions. This gives the customer the opportunity to build a competitive advantage by displaying the information necessary to provide better service to the customer.
[0042]
At step 86, the “read first” portion is changed. This “read first” portion is a routine that must be completed or customized to read the first price stored in the PLU data file.
[0043]
In step 88, the “read next” portion is changed. This “Read Next” part is completed to sequentially read the next price in the PLU data file, or
A routine that must be customized.
[0044]
In step 90, the “what to read” portion is changed. This “what to read” portion is a routine that must be completed or customized to read a particular PLU data file record.
[0045]
At step 92, the customized mapping and translation routine 65 and the customized target routine 67 derived from step 85 are applied to the template 63.
[0046]
At step 94, a new executable (POS server PLU file reader 38) is compiled from object code 62 and template 61 and linked using makefile 68, compiler 72, and linker 74.
[0047]
At step 96, the method ends.
[0048]
Reference is now made to FIG. This figure shows in detail the operations of the POS server PLU file reader 38 and the price management server PLU file reader 39 starting at step 100.
[0049]
At step 102, the PLU file reader (ie, PLU file reader 38 or 39) is activated and performs self-configuration.
[0050]
In step 104, the PLU file reader waits for an interprocess communication message from the API 33. Inter-process communication services (eg, “Queues” in UNIX, OS / 2 threads or pipes, etc.) are provided by the operating system 52. The API 33 calls the operating system 52 to send a request to the PLU file reader from one of the independent applications 35. For example, the independent application 35 is a price matching application program that compares the price in the PLU data file 44 with the price displayed on the EPL 22. The independent application program 35 issues a call to the API 33 to instruct the API 33 to perform a “direct reading” routine provided by the API 33. The API 33 calls the operating system 52 to send an interprocess communication message to the PLU file reader. If preferred, the API 33 sends this message to the library 41 in the PLU file reader.
When the PLU file reader receives such a message, it determines in step 105 whether the interprocess communication message includes an “exit loop” command. If so, the PLU file reader ends at step 116.
[0051]
If the interprocess communication message does not include an “exit loop” instruction, the library 41 calls a PLU file read routine (453 or 45) in the library 41 in step 106. This PLU file reading routine is customized according to the requirements of the trading institution.
[0052]
In step 108, the PLU file read routine uses the operating system 52 to obtain PLU information from the PLU data file.
[0053]
In step 110, the PLU file read routine masks the PLU information obtained from the PLU data file. For example, if the application program 35 is a program that controls price information displayed by the EPL 22, the PLU information is converted into information that can be displayed by the EPL 22 by masking.
[0054]
At step 112, the PLU file read routine ends.
[0055]
In step 114, the library 41 calls the operating system 52 and returns PLU information via interprocessor communication to the application 35 that has issued the request via the API 33. The PLU file reader returns to the standby state in step 104.
[0056]
After the PLU file reader sends PLU information to the API 33, the API 33 sends the PLU information to the requesting application 35. The application program 35 can then display the information based on its function, compare the information, or review the information.
[0057]
Please refer to FIG. This figure shows in more detail the operation of the PLU verifier 48 starting at start step 120.
[0058]
In step 122, PLU collator 48 reads a record in EPL data file 32.
[0059]
In step 124, the PLU collator 48 determines the product identification number in this record.
[0060]
In step 126, PLU collator 48 reads PLU data file 44.
[0061]
At step 128, PLU verifier 48 determines a first price associated with the product identification number in PLU data file 44.
[0062]
In step 130, PLU collator 48 reads PLU data file 60.
[0063]
At step 132, PLU collator 48 determines a second price associated with the product identification number in PLU data file 60.
[0064]
At step 134, PLU verifier 48 determines whether the first price is equal to the second price.
[0065]
If they are not equal, at step 136 the PLU verifier 48 stores the merchandise number, first price and second price in log file 49 and operation proceeds to step 138. If they are equal, operation proceeds directly to step 138.
[0066]
At step 136, PLU collator 48 determines whether the record is the last record in EPL data file 32. If it is not the last record, operation returns to step 122 to read the next record. If so, operation proceeds to step 140.
[0067]
At step 140, the operation ends.
[0068]
The operator can display or print the contents of the log file 49 and make any necessary corrections to the PLU data file 44 or 60 as required by the retailer. Retailers may or may not be aware of the difference, and the PLU data file is aware of the difference. 60 Can be updated, and the PLU data file 44 can be updated by recognizing the difference. In addition, the operator can set the PLU collator 48 to automatically update the contents of one of the PLU files 44 or 60 to the price in the other file. After the PLU price is updated, the EPL system 24 uses the normal method to update the displayed price.
[0069]
【effect】
As described above, according to the present invention, products whose product prices do not match between the PLU file of the POS server and the PLU file of the in-store processor can be identified, displayed, and recorded. Based on the display and record, the operator can take appropriate measures such as correcting the price erroneously displayed on the electronic price label.
[Brief description of the drawings]
FIG. 1 is a block diagram of a transaction management system.
FIG. 2 is a block diagram of a system for generating a PLU file reader program.
FIG. 3 is a flow diagram illustrating how a PLU file reader is generated.
FIG. 4 is an operational flow diagram illustrating the operation of the PLU file reader program.
FIG. 5 is a flow diagram illustrating the method of the present invention.
[Explanation of symbols]
10 Trading system
12 POS computer system
14 Checkout system
16 EPL system
18 ISP computer system
19 Barcode scanner
20 POS terminal
22 EPL
24 EPL terminal
26 EPL storage media
30 EPL software
31 POS software
32 EPL data file
33 API
34 Printer
35 Independent applications
36 PLU storage media
37 display
38 POS server PLU file reader
39 Price management server PLU file reader
40 Host PLU terminal
41 Library
42 Input devices
43 PLU file read routine
44 PLU data file
45 PLU file read routine
48 PLU collator
49 Log files
50 PLU management maintenance routine
52 Operating System
54 Data Register
55 Input device
56 display
57 Price management server
58 Price management application
59 PLU storage media
60 PLU data file
61 Customized template PLU
62 Object code
63 Template PLU file reader
64 Mapping and translation sample
65 Customized mapping and translation routines
66 Target routine
67 Customized target routines
68 Makefile
72 compiler
74 Linker

Claims (2)

An in-store processor (18) having a first PLU data file ( 60 ), and receiving the first PLU data transmitted from the in-store processor (18) to create a second PLU data file (44) a POS server (12) for storing this, composed of an electronic price label system (12), having a plurality of electronic price label indicating the product price in the second PLU data file (44) (22) System (10)
The electronic price label system computer (16) comprises:
Means ( 39 ) for reading said first PLU data file;
Means for reading the second PLU data file ( 38 );
Means (48) for comparing and comparing the product price in the first PLU data file with the product price in the second PLU data file;
Means (49) for recording products for which the product price in the first PLU data file is different from the product price in the second PLU data file;
An apparatus for correcting a PLU data file in an electronic price label system, wherein PLU data relating to products having different product prices in the two PLU data files is matched with a product price of one of the PLU data files. An in-store processor (18) having a first PLU data file ( 60 ), and receiving the first PLU data transmitted from the in-store processor (18) to create a second PLU data file (44) a POS server (12) for storing this, composed of an electronic price label system (12), having a plurality of electronic price label indicating the product price in the second PLU data file (44) (22) A method for correcting a PLU data file in a system (10), comprising:
(A) reading the first PLU data file;
(B) reading the second PLU data file;
(C) collating the product price in the first PLU data file with the product price in the second PLU data file;
(D) recording a product whose product price in the first PLU data file is different from the product price in the second PLU data file;
(E) matching the PLU data relating to the products having the different product prices in the two PLU data files with the product price of one of the PLU data files;
A method for correcting a PLU data file in an electronic price label system , comprising the steps of:

Images