JP2744870B2 - Product sales data processing device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a merchandise sales data processing device such as a POS (Point of Sale Information) terminal used in a supermarket or a convenience store.

[0002]

2. Description of the Related Art Generally, a POS terminal is provided with a single item file in which unit price data and the like are previously set and stored in correspondence with a single item code attached to each product handled in a store, and a single item code input such as a keyboard or a bar code scanner. When the single item code of the product for sale is input by the means, the single item file is searched, unit price data corresponding to the input single item code is called, the unit price data is multiplied by the number of sales points, and the sales amount is calculated. Is stored in the storage unit.

[0003] In a retail store, for example, a bargain product may be sold at a reduced price for a certain period of time. In this case, the unit price data of the single item file and the price tag of the bargain product displayed on the sales floor are displayed before and after the bargain date. Need to change.

[0004] In this case, the unit price data of the single item file has been automatically and simultaneously changed at the scheduled date and time of the price change due to the operation of the host computer electrically connected to the POS terminal.

[0005] However, the task of changing the price tag of a bargain product displayed on the sales floor is left to the labor of the clerk.
It was difficult to change all at the scheduled date and time.

[0006]

As described above, conventionally, it was difficult to simultaneously change the price tag of a bargain product displayed on the sales floor to the scheduled date and time of the price change. In some cases, the price tag of the unit price was attached to the product, or the price tag of the old unit price was attached to the product even after the scheduled price change date and time. In such a case, since the price tag of the product does not match the unit price at the time of registration, the customer is distrusted.

Accordingly, an object of the present invention is to provide a merchandise sales data processing apparatus capable of eliminating inconsistency between a price tag of a merchandise and a unit price at the time of registration, and reliably preventing troubles with customers.

[0008]

According to the present invention, there is provided a single item file storing unit price data in advance corresponding to a single item code assigned to each product, and a single item file corresponding to a single item code of a product whose unit price is to be changed. A price change file for storing the new unit price data after the change is provided. Further, a price change completion notification detecting means for detecting a price change completion notification input from the outside, and a single item code inputting means for inputting a single item code of a sales product are provided.

When the single item code is input, the price change file is searched to determine the presence or absence of the input single item code, and when it is determined that there is no input single item code, the product is based on the unit price data corresponding to the input single item code in the single item file. Acquire sales data and process sales registration. On the other hand, if it is determined that there is an input single item code, it is determined whether a price change completion notification is detected. When it is determined that the price change completion notification is detected, the product sales data is obtained based on the new unit price corresponding to the input single item code of the price change file, sales registration processing is performed, and when it is determined that the price change completion notification is not detected, the value is determined. This is to notify that the replacement is in progress.

[0010]

According to the present invention having such a configuration, for a product whose unit price is changed due to bargain sale or the like, the product after the change corresponding to the corresponding single item code is stored in the price change file before the scheduled unit price change date. Set a new unit price. Also, when the unit price is scheduled to be changed and the price tag of the product is changed, a price change completion notification is issued from the outside.

In this way, after the price change completion notification, the price tag of the corresponding product is changed to the new unit price. At this time, when the single product code of the corresponding product is input by the single product code input means, the price is set in the price change file. Since the sales registration processing is automatically performed at the new unit price, the unit price of the price tag and the registration unit price match.

On the other hand, before the price change completion notification, it is unknown whether or not the price tag of the corresponding product has been changed to the new unit price. At this time, if the single product code of the corresponding product is input by the single product code input means, the price is being changed. Since it is notified that there is, for example, the sales clerk manually registers with the unit price printed on the price tag of the corresponding product, so that the unit price of the price tag and the registration unit price match.

[0013]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing the overall configuration of a POS system, in which a plurality of POS terminals 1 installed at a checkout place of a store and a store processor 2 composed of a host computer installed at an office of the store. Are connected in-line in a closed loop by a communication line 3 to construct a POS system.

FIG. 3 is a block diagram showing a main configuration of the POS terminal 1. The POS terminal 1 has a CPU (central processing unit) 11 as a control unit main body.

A ROM (Read Only Memory) 12 in which program data for the CPU 11 to control each section is stored in advance, and various memory areas for storing data to be processed by the CPU 11 are formed. A RAM (random access memory) 13 and a clock circuit 14 for measuring the date and time are provided.

A communication interface 1 for controlling data communication with the store processor 2
5. Keyboard controller 17 for controlling keyboard 16 to capture key signals corresponding to input keys, display 18
, A display controller 19 for displaying the product name and unit price of the product for sale, a printer controller 21 for controlling the printer 20 to print on receipt paper and journal paper, and a scanner 22 for optically reading bar codes.
A signal is input from a scanner controller 23 for controlling the bar code reading operation, and a mode switch 24 for selecting various business modes such as "registration", "inspection", "payment", "setting", etc., and accommodates cash and the like. And a signal input / output unit such as an I / O port 26 for outputting a drive signal to a drawer opening device 25 for opening the drawer for the operation.

The CPU 11, ROM 12, RAM 1
3. The clock circuit 14 and each signal input / output unit are mutually connected via bus lines 27 such as an address bus, a data bus, and a control bus.

FIG. 2 shows a main memory area of the RAM 13.
The AM 13 has an area for creating a single item file 31, an area for creating a price change file 32, and a flag area in which a price change flag (F) 33 is set.

The single item file 31 sets and stores the data of the item name and unit price of the corresponding item in advance corresponding to the single item code assigned to each item sold in the store, and stores the number of sales points and the accumulation area of the sales amount. This is provided separately for each product code.

The price change file 32 stores, in advance, an old unit price before change, a new unit price after change, and a scheduled price change date corresponding to a single item code of a product whose unit price is to be changed due to a bargain sale or the like among the products sold at the store. Are set and stored.

The price change flag 33 is stored in the value change file 32
Is set when the data of the unit price scheduled to be changed is registered, and reset when a price change completion notification is received from the store processor 2.

The CPU 11 is program-controlled to execute the processing shown in FIG. That is, it is determined whether or not a command from the store processor 2 has been received by the communication interface 15 in step ST1. Then, when the command is received, it is determined whether or not the command can be received. When the command can be received, the content of the command is analyzed.

In the case of the single item file creation command, the single item file data (single item code, item name, unit price, number of sales, sales amount) received thereafter is stored in the RAM 13.
The single item file 31 is set sequentially in the single item file area of
Create

In the case of a price change file creation command, the price change file data (single item code, old unit price, new unit price, scheduled replacement date) received thereafter are sequentially set in the replacement file area of the RAM 13. To create a price change file 32. Then, after the price change file is created, the value change flag 33 of the RAM is set to “1”.

In the case of a value change completion notification command, the value change flag 33 in the RAM is reset to "0" (value change completion notification detection means).

Next, in ST2, it is determined whether or not the single item code of the sales product has been input by the single item code input means of the scanner 22 or the keyboard 16. Then, if a single item code is input, it is determined whether or not single item registration is possible. If single item registration is possible, a predetermined single item sales registration process is executed.

FIG. 5 is a flowchart specifically showing the single item sales registration process. That is, when entering the single item sales registration process, first, the single item file 31 is searched using the input single item code as a key (FIG. 5-51).

If the input single item code does not exist in the single item file 31, it means that the item not registered in the single item file 31 is registered as a single item.

If the input single item code is present in the single item file 31, the price change file 32 is searched again using the input single item code as a key (FIG. 5-52).

If the input single item code does not exist in the price change file 32, it is a single item registration of a product that is not scheduled to be changed in unit price. Therefore, the data of the item name and unit price corresponding to the input single item code from the single item file 31 are stored. It is called and displayed on the display 18 and printed out on a receipt or the like by the printer 20. Further, the unit price data is added to the sales amount accumulation area corresponding to the input single item code of the single item file 31, and “1” is added to the sales point accumulation area (FIG. 5-53).

If the input single item code is present in the price change file 32, it is registered as a single item of a product whose unit price is to be changed, so the value change flag 33 is checked (FIG. 5-54).

Here, if the flag 33 is reset, the price change work of the product whose unit price is to be changed has been completed and the price change completion notification has been input from the store processor 2, so that the new unit price is validated. The new unit price data corresponding to the input single item code in the price change file 32 is called up, displayed on the display 18 together with the item name data corresponding to the input single item code in the single item file 31, and printed out on a receipt or the like by the printer 20. Further, the new unit price data is added to the sales amount accumulation area corresponding to the input single item code of the single item file 31, and "1" is added to the sales point accumulation area (FIG. 5-55).

If the price change flag 33 is set, it means that the product whose price is to be changed is in the process of being changed, so that the current date data measured by the clock circuit 14 and the input single item code of the price change file 32 are used. The corresponding price change date data is compared (FIG. 5-56).

If the current date data is smaller than (scheduled price change date data-1), the old unit price is validated because today is before the day before the scheduled price change date of the product whose unit price is to be changed. The old unit price data corresponding to the input single item code of the replacement file 32 is called up, displayed on the display 18 together with the item name data corresponding to the input single item code of the single item file 31, and printed out on a receipt or the like by the printer 20. In addition, the old unit price data is added to the sales amount accumulation area corresponding to the input single item code of the single item file 31, and "1" is added to the sales point accumulation area (FIG. 5).
57).

If the current date data is larger than the scheduled price change date data, the new unit price is valid since today is the next day after the scheduled price change date of the product whose unit price is to be changed. Is displayed on the display unit 18 together with the product name data corresponding to the input single product code of the single product file 31 and the printer 2
A value of 0 prints out on a receipt or the like. Further, the new unit price data is added to the sales amount accumulation area corresponding to the input single item code of the single item file 31, and “1” is added to the sales point accumulation area (FIG. 5-58).

If the relationship between the current date data and the scheduled price date data is not any of the above, today is the current or previous day of the scheduled price change date of the product whose unit price is to be changed,
Since it is unknown whether the price tag of the corresponding product has been changed to the one with the new unit price or the old unit price, the new and old unit price data corresponding to the input single item code of the price change file 32 is called up and displayed on the display unit 18 to display the unit price data. Force input (Fig. 5-
59).

In this state, when unit price data is input by key input on the keyboard 16, the input unit price is displayed on the display 18 together with the product name data corresponding to the input single product code in the single product file 31, and the receipt is received by the printer 20. And print it out. Further, the input unit price data is added to the sales amount accumulation area corresponding to the input single item code of the single item file 31, and "1" is added to the sales point accumulation area (FIG. 5-60).

In a store in which a POS system having such a configuration is constructed, data such as a single item code, a product name, a unit price, etc., respectively assigned to each product handled in the store in advance are input from the store processor 2 to each POS terminal 1 A single item file 31 is created in advance.

For example, when there is a plan to change the unit price for a bargain sale, the data of the old unit price, the new unit price, and the scheduled date of the price change of the unit price planned product are input from the store processor 2 in advance. A price change file 32 is created in the POS terminal 1.

Then, on the day before or on the day of the scheduled price change date, the operation of sequentially changing the price tag attached to the unit price scheduled to be changed to the new unit price is started. It is assumed that a price change completion notification is sent to the POS terminal 1.

Now, the clerk uses the scanner 22 or the keyboard 16 to enter the single item code of the item purchased by the customer into the POS.
Enter into terminal 1. Then, the POS terminal 1 determines whether the product is a unit price change planned product. If the product is not the unit price scheduled to be changed, the sales registration process is performed based on the unit price preset in the single item file 31.

On the other hand, if the purchased product is a product to be changed in unit price, it is determined whether or not there is a price change completion notification. Here, when the price change flag 33 is reset and after the completion of the price change notification, the sales registration process is performed based on the new unit price set in the price change file 32. In this case, since the price tag of the product has already been changed to the new unit price, it matches the unit price at the time of registration.

On the other hand, when the price change flag 33 is set and before the price change completion notification, the current date data measured by the clock circuit 14 and the input single item code of the price change file 32 correspond. The scheduled price change date data is compared.

If the current date data is smaller than (scheduled date data-1), sales registration processing is performed based on the old unit price set in the price change file 32. At this time, since the price change work has not been started since the day before the scheduled price change date of the registered product has been started and the price tag of the registered product remains at the old unit price, it matches the unit price at the time of registration.

On the other hand, if the current date data is larger than the scheduled price change date data, sales registration processing is performed based on the new unit price set in the price change file 32. At this time, it is after the day after the scheduled price change date of the registered product and there is no price change completion notification, but since the price change work has already been completed and the price tag of the registered product has been changed to the new unit price, it matches the unit price at the time of registration .

If the relationship between the current date data and the scheduled date with price data is not one of the above, the price change file 3
The new and old unit price data corresponding to the input single item code 2 are displayed on the display unit 18, and the unit price entry is compulsory. At this time, it is the current day or the day before the scheduled price change date of the registered product, and it is not known whether the price tag of the registered product has been changed to a new unit price or remains at the old unit price.

Then, the clerk manually inputs the unit price printed on the price tag of the product. Then, the registered merchandise is subjected to sales registration processing based on the input unit price, so that the price tag and the unit price at the time of registration match.

As described above, according to the present embodiment, since the price tag of the product and the unit price at the time of registration surely coincide with each other, it is possible to completely prevent the occurrence of trouble with the customer due to the mismatch.

In the above embodiment, the old unit price data and the new unit price data are set in the price change file 32 in correspondence with the single item code of the product whose unit price is to be changed, but only the new unit price data is set and the old unit price data is set. May be set using the unit price set in the single item file 31. In this case, the new and old unit prices cannot be simultaneously displayed on the day before or on the day of the scheduled price change, but the effect of the present invention can be achieved simply by providing guidance display indicating that unit price input is compulsory because the price is being changed. So there is no problem.

In addition, it goes without saying that various modifications can be made without departing from the spirit of the present invention.

[0052]

As described above in detail, according to the present invention, a single item file storing unit price data in advance corresponding to a single item code attached to each product and a single item code of a product whose unit price is to be changed are provided. Correspondingly, a price change file for storing the new unit price data after change is provided in advance, and a price change completion notification input from the outside can be detected. When a single item code is input, the price change file is searched and input. If it is determined that there is no single item code, sales registration processing is performed based on the unit price data corresponding to the input single item code in the single item file.
When it is determined that a price change completion notification has been detected, sales registration processing is performed based on the new unit price corresponding to the input single item code of the price change file. When it is determined that no price change completion notification has been detected, it is notified that the price change is in progress. Therefore, it is possible to provide a product sales data processing apparatus capable of reliably preventing troubles with customers due to a mismatch between a price tag of a product and a unit price at the time of registration.

[Brief description of the drawings]

FIG. 1 is an overall view of a POS system according to an embodiment of the present invention.

FIG. 2 shows a RAM of the POS terminal in the embodiment.
FIG. 2 is a schematic diagram showing a main memory area formed in FIG.

FIG. 3 is an exemplary block diagram showing the configuration of the POS terminal in the embodiment.

FIG. 4 shows a CPU of the POS terminal in the embodiment.
4 is a flowchart showing the main part program processing executed by the user.

FIG. 5 is a flowchart specifically showing a single item sales registration process shown in FIG. 4;

[Explanation of symbols]

 1 POS terminal, 11 CPU (central processing unit), 14 clock circuit, 15 communication interface, 16 keyboard, 18 display, 20 printer, 22 scanner, 31 single file, 32 price change File, 33 ... price change flag.

──────────────────────────────────────────────────続 き Continued on the front page (58) Fields surveyed (Int. Cl. ⁶ , DB name) G06F 17/60 G07G 1/00-5/00

Claims (1)

(57) [Claims] 1. A single item file for storing unit price data in advance corresponding to a single item code attached to each product, and a new unit price data after the change in advance corresponding to a single item code of a product whose unit price is to be changed is stored. Price change file to be changed, price change completion notification detecting means for detecting a price change completion notification input from the outside, single item code inputting means for inputting a single item code of a sales product, and a single item code is input by this inputting means. And a file search means for searching the price change file to determine the presence or absence of an input single item code, and when the search unit determines that there is no input single item code, based on unit price data corresponding to the input single item code of the single item file. A set unit price registration processing means for acquiring product sales data and performing a sales registration process, and when the search means determines that there is an input single item code, the price change is completed. Completion notification judging means for judging whether or not the price change completion notice is detected by the end notice detecting means; and when the judgment of the price change completion notice is made by the judging means, the input single item code of the price change file A new unit price registration processing means for acquiring and selling the product sales data based on the new unit price corresponding to (i), and notifying that the price change is being performed when the determination means determines that the price change completion notification has not been detected. And a price change notifying unit.