Article sales data processor and program

Abstract

To provide an article sales data processor and a program capable of clarifying transaction contents for articles not registered in an article master.SOLUTION: The article sales data processor includes: an acquisition unit that acquires article identification information capable of identifying an article; a determination unit that determines whether the article identification information acquired by the acquisition unit is registered in an article master that is registered by associating the article identification information with a name of the article corresponding to the article identification information; a receiving unit that receives input of a tax category of the article corresponding to the article identification information acquired by the acquisition unit when the determination unit determines that the article identification information is not registered; and an output unit that outputs a name corresponding to the input tax category as the name of the article.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] An embodiment of the present invention relates to a product sales data processing device and a program. [Background technology]

[0002] Retail stores such as supermarkets and drug stores are equipped with product sales data processing devices such as POS (Point Of Sales) terminals that perform registration processing to register product information of products purchased by customers and transaction processing based on the registered product information. Such product sales data processing devices perform registration processing using a PLU table (hereinafter also referred to as product master) that stores product information such as product name, price, tax classification, etc. in association with product identification information (hereinafter also referred to as product code) that can identify a product.

[0003] For example, a product sales data processing device reads a product code from a code symbol such as a barcode attached to a product, and performs registration processing based on product information in a product master corresponding to the product code.

[0004] However, in a store, products that are not registered in the product master may be displayed for sale. Conventionally, when a product code of a product that is not registered in the product master is read in a product sales data processing device, the product can be registered by having a salesperson manually input the tax category and product price of the product. Conventionally, a method has been proposed in which, when a product that is not registered in the product master is read, provisional product information consisting of the classification code, unit price, tax category, and identification flag of the unregistered product is created, and the provisional product information is provisionally registered (for example, Patent Document 1).

[0005] However, in the above-mentioned conventional method, although it is possible to register a product that is not in the product master, a fixed name (e.g., "product") is displayed (printed) regardless of the input content. Therefore, in the above-mentioned conventional method, the transaction content is unclear, and further improvement is required. Summary of the Invention [Problem to be solved by the invention]

[0006] An object of the present invention is to provide a product sales data processing device and a program that are capable of clarifying the transaction details of a product that is not registered in a product master. [Means for solving the problem]

[0007] The product sales data processing device of the embodiment includes an acquisition unit that acquires product identification information capable of identifying a product, a judgment unit that judges whether the product information acquired by the acquisition unit is registered in a product master in which product identification information is associated with the name of the product corresponding to the product identification information, and if the judgment unit determines that the product information is not registered, a reception unit that accepts input of a tax category of the product corresponding to the product identification information acquired by the acquisition unit, and an output unit that outputs the name corresponding to the input tax category as the name of the product. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of a product sales data processing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the POS terminal according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a data configuration of the product master according to the embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a data configuration of an additional PLU table according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data configuration of a tax category table according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a functional configuration of the POS terminal according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a product registration screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a tax category input screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a tax category input screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of an amount input screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a product registration screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a product registration screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of receipt data generated by the payment processing unit according to the embodiment. [Figure 14] FIG. 14 is a flowchart showing an example of a process related to product registration and transaction performed by the POS terminal according to the embodiment. [Figure 15] FIG. 15 is a flowchart showing an example of a process related to product registration and transaction performed by the POS terminal according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of a product sales data processing device and a program will be described with reference to the drawings. Note that in the following embodiment, an example of application to a product sales data processing system introduced in a retail store (shop) such as a supermarket will be described, but the present invention is not limited to this embodiment.

[0010] Fig. 1 is a diagram showing an example of a system configuration of a product sales data processing system 1 according to the present embodiment. As shown in Fig. 1, the product sales data processing system 1 includes a POS terminal 10 and a store server 20. Here, the POS terminal 10 and the store server 20 are communicatively connected via a network N such as a LAN (Local Area Network). Note that the number of POS terminals 10 connected to the network N is not limited to the illustrated example.

[0011] The POS terminal 10 is an example of a product sales data processing device. The POS terminal 10 is operated by a store clerk and executes processes related to the registration or payment of products purchased by customers (hereinafter also referred to as users).

[0012] In addition, the POS terminal 10 may be a semi-self-service POS terminal equipped with a registration machine operated by a store clerk to perform processes related to product registration, and an accounting machine operated by a user to perform processes related to product payment, or it may be a full-self-service POS terminal in which product registration and payment are performed by the user himself / herself.

[0013] The store server 20 is, for example, a server device installed in a store. Specifically, the store server 20 distributes a product master 142 (described later) to the POS terminal 10 via the network N. The store server 20 also collects an additional PLU table 143 (described later) from the POS terminal 10, merges the collected additional PLU table 143, and distributes it to the POS terminal 10.

[0014] In addition, in the settlement process described below, the store server 20 may obtain the registration data for one transaction registered in the POS terminal 10 and a transaction ID assigned to each piece of registration data via the network N, and store them in the store server 20. Then, the store server 20 may transfer the registration data to the payment machine in response to a request from the payment machine.

[0015] In this embodiment, the store server 20 is realized by one server device, but the present invention is not limited to this and may be realized by a cloud server realized by the cooperation of a plurality of server devices.

[0016] Next, the configuration of the above-mentioned POS terminal 10 will be described with reference to FIG.

[0017] Fig. 2 is a diagram showing an example of a hardware configuration of the POS terminal 10. As shown in Fig. 2, the POS terminal 10 includes a CPU (Central Processing Unit) 11, which is an example of a processor, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a memory unit 14, and the like.

[0018] The CPU 11 comprehensively controls each unit of the POS terminal 10. The ROM 12 stores various programs. The RAM 13 is a workspace in which programs and various data are expanded. The memory unit 14 stores various programs.

[0019] The CPU 11, ROM 12, RAM 13, and memory unit 14 are connected to one another via a bus 15, and the CPU 11, ROM 12, and RAM 13 constitute a computer-configured control unit 100. That is, the control unit 100 executes a control process of the POS terminal 10, which will be described later, by the CPU 11 operating in accordance with a program stored in the ROM 12 and memory unit 14 and loaded into the RAM 13.

[0020] The memory unit 14 is composed of a non-volatile memory such as a hard disk drive (HDD) or a flash memory that retains stored information even when the power is turned off. The memory unit 14 has a control program unit 141 that stores a control program, a product master 142, an additional PLU table 143, a tax classification table 144, and a product registration file 145.

[0021] The product master 142 stores product information of each product in association with product identification information that identifies the product. The additional PLU table 143 stores product information of a product not stored in the product master 142 in association with product identification information that identifies the product in a product registration process described later. The tax category table 144 stores the tax rate of a product and the name of each tax rate in association with a tax category code. The data configurations of the product master 142, the additional PLU table 143, and the tax category table 144 will be described later. The product registration file 145 is a file for the POS terminal 10 to record the product code, product information, etc. of a registered product in a product registration process described later. The product registration file 145 includes, for example, the product code, product name, unit price, quantity, tax category, etc. of a registered product.

[0022] The control unit 100 is also connected to a display unit 17, an operation unit 18, a scanner 19, a card reader 21, a printer 22, and a communication unit 23 via a bus 15 and a controller 16. The communication unit 23 is also connected to an external device such as a store server 20 via a network N so as to be able to communicate with the external device.

[0023] The controller 16 is connected to a display unit 17, an operation unit 18, a scanner 19, a card reader 21, and a printer 22. Based on instructions from a control unit 100, the controller 16 controls each of the connected units.

[0024] The display unit 17 is a display device such as an LCD (Liquid Crystal Display). The display unit 17 displays various information under the control of the CPU 11. The operation unit 18 is an input device such as a keyboard or a pointing device. The operation unit 18 outputs operation contents input via the input device to the CPU 11. The operation unit 18 may be a touch panel provided on the display unit 17.

[0025] The scanner 19 is a reading device that reads code symbols such as bar codes, two-dimensional codes, etc. For example, the scanner 19 reads product information of a product purchased by a customer from a code symbol attached to the product.

[0026] The card reader 21 is a reading device that reads information from a card medium such as an IC card, a magnetic card, etc. For example, the card reader 21 reads information registered on a point card, a credit card, an electronic money card, etc., held by a customer, such as attribute information of the customer, such as the age, sex, etc.

[0027] The printer 22 is a printing device such as a thermal printer, etc. Under the control of the control unit 100, the printer 22 issues a receipt on which product information related to the product for which payment has been processed, payment information, etc. are printed.

[0028] The communication unit 23 is a communication interface that can be connected to a network N such as a LAN. The communication unit 23 communicates with a store server 20 provided in a store via the network N. The communication unit 23 may also communicate with an external device such as an electronic payment server that provides an electronic payment service.

[0029] Next, the data configuration of the product master 142 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the data configuration of the product master 142. The product master 142 is a data table or database that stores information about products for sale. As shown in Fig. 3, the product master 142 stores product information of a product identified by a product code in association with the product code of each product.

[0030] Here, the product code is an example of product identification information that can identify the type of product, and product identification information such as a JAN code can be used. Each product sold in a store is affixed with a code symbol, such as a barcode or a two-dimensional code, that holds the product code of the product. In addition, the product can be identified by reading the product code from the code symbol affixed to the product.

[0031] The product information also includes information such as the product name, unit price, and tax category code. The tax category code is a code that identifies the tax category to which the product corresponding to the product code belongs. Tax categories can be categorized according to a combination of the taxation method (inclusive tax / exclusive tax) and the tax rate. For example, tax categories include "tax-exclusive 8% excluding tax," "tax-inclusive 8%," and "tax-exempt," and a different code is assigned to each tax category.

[0032] For specific products such as food and beverages, a tax corresponding to the standard tax rate may be imposed or a tax corresponding to the reduced tax rate may be imposed depending on the consumption pattern. The reduced tax rate is a taxation system that reduces the consumption tax rate for minimum necessities defined by the government. For example, when a purchased product (food and beverage) is eaten (eat-in) at a place where eating and drinking facilities are installed, a consumption tax corresponding to the standard tax rate (e.g., 10%) is imposed. On the other hand, when a purchased product (food and beverage) is taken home (take-out), a consumption tax corresponding to the reduced tax rate (e.g., 8%) is imposed. In this embodiment, a take-out tax rate is registered as a default tax category code in the product master 142 for a specific product, and when eat-in is instructed, a tax rate for eat-in is applied.

[0033] The data configuration of the product master 142 is not limited to the example shown in Fig. 3. For example, the product master 142 may store image data and weight representing the product in the product information.

[0034] Next, the data configuration of the additional PLU table 143 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the data configuration of the additional PLU table 143. The additional PLU table 143 is a data table or database for storing product information of products not stored in the product master 142 (hereinafter also referred to as unregistered products) in association with product identification information that identifies the products in a product registration process described later. As shown in Fig. 4, the additional PLU table 143 has the same data configuration as the product master 142, and stores product information of a product identified by a product code in association with the product code. The product information includes information such as the product name, unit price (price), and tax category code. The tax rate indicates the consumption tax rate corresponding to the tax category code.

[0035] Here, the additional PLU table 143 registers product information of products whose product codes are not registered in the product master 142. Specifically, when a product code not registered in the product master 142 is read, the additional PLU table 143 functions as a provisional PLU table that stores manually input product information in association with the product code. However, as described later, the name of the tax category corresponding to the input tax category code is automatically registered in the product name field.

[0036] For example, the POS terminal 10 may be configured so that the registered contents of the additional PLU table 143 can be modified from a setting screen for an administrator. This allows the user to modify the registered contents to any desired setting contents when there is an error in the registered contents of the additional PLU table 143 or when the registered contents need to be modified.

[0037] Next, the tax category table 144 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the data configuration of the tax category table 144. The tax category table 144 is a data table or database for storing the tax rate and name of a product in association with a tax category code. As shown in Fig. 5, the tax category table 144 stores the tax rate and name in association with the tax category code of each tax category.

[0038] Here, the tax category code is a code that identifies the tax category. The tax rate is information that indicates the tax rate and taxation method (i.e., the tax category) that is applied to the tax category corresponding to the tax category code. The name is registered with information that indicates the products and consumption patterns that are subject to the tax category corresponding to the tax category code. Note that the character string in parentheses written in the tax rate field is for explanatory purposes.

[0039] In the example of FIG. 5, "8% excluding tax" and "food" are set as the tax category and name corresponding to the tax category code "1". "10% excluding tax" and "alcohol, non-food, eat-in" are set as the tax category and name corresponding to the tax category code "2". "8% including tax" and "food" are set as the tax category and name corresponding to the tax category code "3". "10% including tax" and "alcohol, non-food, eat-in" are set as the tax category and name corresponding to the tax category code "4". In addition, "non-taxable" and "product" are set as the tax category and name corresponding to the tax category code "5". Note that the combinations of "tax category code", "tax category", and "name" stored in the tax category table 144 are not limited to the above examples.

[0040] Next, the functional configuration of the POS terminal 10 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the functional configuration of the POS terminal 10. As shown in Fig. 6, the POS terminal 10 includes a reading control unit 111, a registration processing unit 112, a display control unit 113, and a payment processing unit 114 as functional components.

[0041] Specifically, the control unit 100 (CPU 11) of the POS terminal 10 realizes the above-mentioned functional configuration by executing the control program unit 141 stored in the memory unit 14. Note that in this embodiment, the above-mentioned functional configuration is a software configuration realized by cooperation between the processor and the program of the POS terminal 10, but is not limited to this, and a part or all of the functional configuration may be realized as a hardware configuration using a dedicated circuit or the like.

[0042] The reading control unit 111 is an example of an acquisition unit. The reading control unit 111 reads information from a code symbol by cooperating with the scanner 19. Specifically, the reading control unit 111 reads a product code from a code symbol attached to a product, and acquires product identification information capable of identifying the product.

[0043] The registration processing unit 112 is an example of a determination unit, a reception unit, and a registration unit. The registration processing unit 112 executes a registration process for a product purchased by a customer. Specifically, when a product code is read by the reading control unit 111, the registration processing unit 112 reads information on a product corresponding to the product code from the product master 142 or the additional PLU table 143, and registers (stores) the read product information together with the product code, quantity, etc., in the product registration file 145 as registration data.

[0044] Furthermore, the registration processing unit 112 cooperates with the display control unit 113 described below to display the product names, quantities, etc. of products registered in the product registration file 145. Here, the quantity is the quantity (points) of products corresponding to the same product code, managed in units of registered data. For example, the quantity is input via the operation unit 18 when the product code is read. Furthermore, the quantity may be calculated by the registration processing unit 112 adding 1 to the quantity associated with the product code each time a product with the same product code is read. Note that the default value of the quantity is 1.

[0045] Furthermore, if the product corresponding to the product code read by the reading control unit 111 is an unregistered product, the registration processing unit 112 has the operator input information regarding the product, such as the tax classification, and based on the input information, registers registration data regarding the product in the product registration file 145. Furthermore, the registration processing unit 112 registers product information regarding the product in the additional PLU table 143 based on the input information. The reason for registering the product in the additional PLU table 143 here is to perform registration processing using the product information registered in the additional PLU table 143 from the next time onwards.

[0046] Specifically, the registration processing unit 112 cooperates with the display control unit 113 described later to display a screen (a tax category input screen described later) for assisting in input of a tax category (tax category code) based on the tax category table 144. The registration processing unit 112 then registers the input tax category code, the name corresponding to the tax category, etc. in the product registration file 145, thereby performing a registration process for a product that has not been registered in the product master 142 (and the additional PLU table 143).

[0047] The display control unit 113 is an example of an output unit. The display control unit 113 controls the screens to be displayed on the display unit 17. Specifically, the display control unit 113 cooperates with other functional configurations to cause the display unit 17 to display various screens for supporting the operation of the POS terminal 10. For example, the display control unit 113 causes the display unit 17 to display a screen showing the product name, quantity, price, etc. of each registered product based on the registration data registered by the registration processing unit 112 (hereinafter also referred to as a product registration screen). Also, for example, the display control unit 113 cooperates with the payment processing unit 114 to cause the display unit 17 to display various screens related to product transactions.

[0048] The payment processing unit 114 is an example of an output unit. The payment processing unit 114 calculates the total price of the products based on the registration data registered in the product registration file 145. Specifically, the payment processing unit 114 calculates the total price of the products related to one transaction from the transaction information of the products registered up to that point in response to a closing operation that instructs the start of accounting. Here, the transaction information is the registration data for one transaction including the product code, product name, unit price, quantity, tax classification, etc. registered in the product registration file 145.

[0049] The payment processing unit 114 also executes a payment process in which the calculated total amount is settled with the amount paid by the customer (hereinafter, the payment amount). The method of depositing the payment amount (or the payment method) is not particularly important, and various methods can be adopted, such as cash, credit card payment, code payment, etc. The payment processing unit 114 may display a screen on the display unit 17 for selecting a payment method for the payment process.

[0050] When the payment process is completed, the payment processor 114 associates the transaction with an identifiable transaction number, and issues a receipt on which the transaction number and transaction data showing the details of the transaction are printed from the printer 22. Here, the transaction data includes, for example, the product code, product name, unit price, quantity, amount, tax rate, total amount, etc. of each product registered in the transaction, as well as information such as the payment amount and change.

[0051] The receipt issued by the printer 22 is handed over to the customer by the operator of the POS terminal 10 (e.g., a store clerk, etc.). In this embodiment, a paper receipt is provided to the customer, but this is not limiting, and the receipt may be provided to the customer as an electronic receipt. In this case, for example, during the transaction, customer identification information (e.g., a membership number, etc.) that can identify the customer is input to the POS terminal 10. Then, when the payment process is completed, the payment processing unit 114 sends an electronic receipt including the transaction number and data indicating the details of the transaction to a destination such as an email address corresponding to the pre-stored customer identification information.

[0052] Next, the product registration screen displayed on the POS terminal 10 will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of the product registration screen displayed on the display unit 17 of the POS terminal 10. As shown in FIG. 7, the product registration screen Ga has a first display area Fa, a second display area Fb, and a third display area Fc. In addition, the product registration screen Ga is provided with an eat-in registration button Br for selecting an eat-in mode (a mode for changing the tax rate of a specific product) when a customer uses an eat-in service. Note that the product registration screen Ga may have a screen configuration that omits the eat-in registration button Br.

[0053] The first display area Fa is an area for displaying information about the most recently registered product. Specifically, the first display area Fa displays the product name, quantity, unit price, amount, etc. of the registered product. The second display area Fb is an area for displaying a list of information about the registered product. Specifically, the second display area Fb has display columns for displaying the product name, quantity, unit price, amount, and a mark corresponding to the tax category of the registered product (for example, "incl." if tax included, no entry if tax excluded, "non" if tax exempt). The "No." column displays a number indicating the order in which the registration was made.

[0054] 7 shows a state in which the product name "Product A" is registered in "No. 1" in the second display area Fb. Here, Product A is a product registered in the product master 142. Specifically, the product name included in the product information of the corresponding product registered in the product registration file 145 is displayed.

[0055] Thereafter, when the product name "Product B" registered in the product master 142 is registered, information about Product B is displayed in the first display area Fa. Next, when the product name "Product C" registered in the product master 142 is registered, the information about Product B that was displayed in the first display area Fa is moved to "No. 2" in the second display area Fb, and the newly registered information about Product C is displayed in the first display area Fa.

[0056] The movement from the first display area Fa to the second display area Fb is not limited to the case where a new product is registered. For example, the movement from the first display area Fa to the second display area Fb may be triggered by the operation of a subtotal key (not shown).

[0057] The third display area Fc is an area for displaying the total number of registered products, the total price, and the amount of consumption tax on the total price. The calculation of the total number of registered products, the total price, and the amount of consumption tax on the total price may be performed by the registration processing unit 112 or another functional unit such as the display control unit 113.

[0058] Next, an example of operation when a product code of an unregistered product that is not stored in the product master 142 and the additional PLU table 143 is read will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of a tax category input screen displayed on the display unit 17 of the POS terminal 10. As shown in Fig. 8, the tax category input screen Gb has a fourth display area Fd, tax category input buttons Ba to Be for deciding the tax category of the product to be registered, and an input cancel button Bf.

[0059] If the product corresponding to the product code read by the reading control unit 111 is an unregistered product that is not stored in either the product master 142 or the additional PLU table 143, the registration processing unit 112 works in cooperation with the display control unit 113 to display on the display unit 17 a tax category input screen Gb (see Figure 8) for entering the tax category of the unregistered product.

[0060] 8, the fourth display area Fd is an area for displaying information notifying that a product code on the tax category input screen Gb that is not stored in the product master 142 has been read. The fourth display area Fd is also provided with an input cancel button Bf. The input cancel button Bf is an operator for interrupting the registration process of the unregistered product and displaying the product registration screen Ga.

[0061] The tax category input buttons Ba to Be are operators for determining the tax category of a product. As shown in FIG. 8, for example, the tax category input button Ba is an operator for setting a tax category of 8% excluding tax. The tax category input button Bb is an operator for setting a tax category of 10% excluding tax. The tax category input button Bc is an operator for setting a tax category of 8% including tax. The tax category input button Bd is an operator for setting a tax category of 10% including tax. The tax category input button Be is an operator for setting a tax exemption category. Here, the tax category input buttons Ba to Be are displayed based on the tax category table 144.

[0062] Here, when any one of the tax categories is selected via the tax category input button, the registration processing unit 112 associates the tax category code and tax category name corresponding to the selected tax category with the product code of the unregistered product, and registers them in the additional PLU table 143 and the product registration file 145. In this embodiment, the tax rate for take-out (8%) is used as the default tax category code, so when the tax category input button Bb or the tax category input button Bd is selected, the registration processing unit 112 registers the tax category code and tax category name in which the 10% tax rate is replaced with 8% in association with the product code of the unregistered product in the additional PLU table 143.

[0063] It should be noted that the tax category input buttons displayed on the tax category input screen Gb do not necessarily have to be the five types of tax category input buttons Ba to Be described above.

[0064] For example, in a store that does not offer eat-in service, a tax category input screen Gc may be displayed that displays a tax category input button Ba for 8% excluding tax and a tax category input button Bc for 8% including tax, as shown in FIG. 9.

[0065] The tax category input screen Gc has a fourth display area Fd, tax category input buttons Ba and Bc for determining the tax category of the product to be registered, and an input cancel button Bf. For example, the tax category input button Ba is an operator for setting a tax category of 8% excluding tax. The tax category input button Bc is an operator for setting a tax category of 8% including tax. The input cancel button Bf is an operator for interrupting the registration process of an unregistered product and displaying the product registration screen Ga.

[0066] In this case, when one of the tax category input buttons is selected, the registration processing unit 112 associates the tax category code and tax category name corresponding to the selected tax category with the product code of the unregistered product and registers them in the additional PLU table 143 and the product registration file 145.

[0067] The tax category input screen Gc in Fig. 9 can also be used in stores that provide eat-in services. For example, after the eat-in tax rate of 10% is set by operating the eat-in registration button Br described in Fig. 8, the tax category input screen Gc in Fig. 9 may be displayed to allow the user to select whether the 10% tax rate should be applied excluding or including tax.

[0068] In this case, when the tax category input button Ba or the tax category input button Bc is selected, the registration processing unit 112 registers the tax category code and tax category name of the tax category corresponding to the combination of the selected application method and tax rate of 10% in association with the product code of the unregistered product in the product registration file 145. Also, in order to use the take-out tax rate (8%) as the default tax category code, the registration processing unit 112 registers the tax category code and tax category name corresponding to the tax category selected on the tax category input screen Gc in Fig. 9 in association with the product code of the unregistered product in the additional PLU table 143.

[0069] As another example, in a store that provides an eat-in service, the tax rate of the tax category input buttons Ba and Bc displayed on the tax category input screen Gc may be replaced with 10%.

[0070] In this case, when the tax category input button Ba or the tax category input button Bc is selected, the registration processing unit 112 registers the tax category code and tax category name of the selected tax category in association with the product code of the unregistered product in the product registration file 145. In addition, in order to use the take-out tax rate (8%) as the default tax category code, the registration processing unit 112 registers the tax category code and tax category name of the selected tax category with the tax rate replaced with 8% in association with the product code of the unregistered product in the additional PLU table 143.

[0071] Then, when any of the tax category input buttons is selected on the tax category input screen Gb (or Gc), the registration processing unit 112, in cooperation with the display control unit 113, causes the display unit 17 to display a price input screen Gd (see Figure 10) for entering the price of the unregistered product.

[0072] Fig. 10 is a diagram showing an example of an amount input screen displayed on the display unit 17 of the POS terminal 10. As shown in Fig. 10, the amount input screen Gd has a fifth display area Fe and an amount input field Fg.

[0073] The fifth display area Fe is an area for displaying a message to prompt the user to input the price of the product. The fifth display area Fe also displays the tax rate for the tax category corresponding to the tax category input button selected on the previous tax category input screen Gb (or Gc). The price input field Fg is an area for inputting the price (unit price) of an unregistered product.

[0074] In the following, as an example of an unregistered product, we will explain how to register a product (let's call it Product X) shown in Figure 10, which has a price of 10,000 yen and a tax category code of "2", meaning that the tax rate is 10% excluding tax.

[0075] When the price of product X is entered into the price input field Fg via the operation unit 18 and an operation is performed to confirm the price, the registration processing unit 112 registers the price entered in the price input screen Gd in association with the product code of the unregistered product in the additional PLU table 143 and the product registration file 145.

[0076] Then, the registration processing unit 112 cooperates with the display control unit 113 to display the product information registered in the product registration file 145 in the first display area Fa of the product registration screen Ga. Here, the product names of the unregistered products displayed on the product registration screen Ga are names corresponding to the tax classification selected by the above operation, as shown in FIG.

[0077] Fig. 11 is a diagram showing an example of a product registration screen displayed on the display unit 17 of the POS terminal 10. Here, Fig. 11 shows a state in which an unregistered product (assuming product X) has been registered from the product registration screen Ga in Fig. 7. For example, when registering product X, if the tax category input button Bb (tax-excluded 10%, tax category code 2) is selected on the tax category input screen Gb in Fig. 7, and then the price of product X, 10,000 yen, is input from the operation unit 18 on the price input screen Gd in Fig. 9, the product registration screen shown in Fig. 11 is displayed.

[0078] As shown in the product registration screen Ga in Fig. 11, information (product information) based on the tax category selected by the operator and the product price entered is displayed in the first display area Fa. Specifically, the name of the tax category corresponding to the tax category code 2, "Alcohol, Non-food, Eat-in," is displayed as the product name. In addition, the entered price of 10,000 yen is displayed as the unit price.

[0079] In addition, when another tax category is selected, the name corresponding to the selected tax category is displayed as the product name. For example, when tax category code 1 or 3 is selected, the name of the corresponding tax category "Food" is displayed as the product name. When tax category code 5 is selected, the name of the corresponding tax category "Product" is displayed as the product name.

[0080] Additionally, the third display area Fc displays the total number of all registered products, the total price, and the amount of consumption tax on the total price.

[0081] Furthermore, when multiple unregistered products are registered, product information of the unregistered products is displayed in the second display area Fb, as shown in Fig. 12. Fig. 12 is a diagram showing an example of a product registration screen displayed on the display unit 17 of the POS terminal 10. Here, Fig. 12 shows a state in which a product that is not stored in the product master 142 has been registered multiple times from the product registration screen Ga of Fig. 7.

[0082] 12, when a product that is not registered in the product master 142 or the additional PLU table 143 is registered, the name corresponding to the tax category of the product is displayed. Therefore, the POS terminal 10 can clearly display and output the transaction details of the unregistered product that is not registered in the product master 142 (and the additional PLU table 143).

[0083] Next, receipt data output from the POS terminal 10 will be described with reference to Fig. 13. When a closing operation is performed on the above-mentioned product registration screen Ga to instruct the start of a transaction, the payment processing unit 114 calculates the total amount of the products related to one transaction from the transaction information of the products registered up to that point. Then, when the payment processing is completed in which the calculated total amount is settled with the amount paid by the customer, the payment processing unit 114 generates receipt data showing the breakdown of the transaction and prints it out as a receipt from the printer 22.

[0084] 13 is a diagram showing an example of receipt data generated by the payment processing unit 114. Here, the receipt data is, for example, text data and the like, and is used for printing by the printer 22.

[0085] As shown in Fig. 13, the receipt data includes product sales data D1. The product sales data D1 includes the product name and price of the product that was the subject of the payment, the total price by tax category, the total consumption tax by tax category, the total price of each product, the deposit amount paid by the customer, the change amount, etc., based on the registration data for one transaction registered in the product registration file 145. In addition, in the product sales data D1, products that are subject to reduced tax rates, such as general food and beverage products, are identifiable by adding a reduced tax rate mark "*" (asterisk) and include a note to that effect at the end of the line.

[0086] The receipt data also includes elements such as a company code (company name) D3 indicating the company that operates the store, a store code (store name) D4, the store's telephone number D5, address D6, transaction date and time D7, transaction number (receipt number) D8, register number D9, person in charge name D10, and business registration number D11. Here, the business registration number D11 is a registration number held by a business that is capable of issuing qualified invoices (qualified invoice issuing business).

[0087] The elements included in the receipt data are not limited to the example in FIG. 12, and other elements such as the business type and business model code may be included, and elements such as the telephone number D5 and address D6 may be removed.

[0088] Here, the product name of the unregistered product shown in the receipt data will be expressed in the name of the tax category, just like on the product registration screen. Therefore, by printing out the receipt data, the payment processing unit 114 issues a receipt in which the product name of the unregistered product is expressed in the name of the tax category related to the unregistered product.

[0089] Therefore, the POS terminal 10 can clearly print out the transaction details of an unregistered commodity that is not registered in the commodity master 142 or the additional PLU table 143.

[0090] Next, a description will be given of the process related to product registration and transaction performed by the POS terminal 10 with reference to Fig. 14. Fig. 14 is a flow chart showing an example of the process related to product registration and transaction performed by the POS terminal 10.

[0091] First, the reading control unit 111 operates the scanner 19 in response to an operation to instruct the start of a transaction, thereby starting reading of a code symbol via the scanner 19 (step S1). In addition, the display control unit 113 causes the display unit 17 to display a product registration screen Ga in response to the instruction to start a transaction.

[0092] Next, the read control unit 111 judges whether or not the product code has been read from the code symbol (step S2). If the product code cannot be read (step S2; No), the process proceeds to step S11.

[0093] Furthermore, when the reading control unit 111 reads the product code (step S2; Yes), the registration processing unit 112 judges whether or not the product code read by the reading control unit 111 is stored in the product master 142 or the additional PLU table 143 (step S3). If it is judged that the product code is stored in the product master 142 or the additional PLU table 143 (step S3; Yes), the registration processing unit 112 proceeds to step S9.

[0094] Furthermore, if the product code read by the reading control unit 111 is not stored in either the product master 142 or the additional PLU table 143 (step S3; No), the registration processing unit 112, in cooperation with the display control unit 113, causes the tax category input screen Gb to be displayed on the display unit 17 (step S4).

[0095] Next, when the display control unit 113 accepts the operation of the tax category input button based on the displayed tax category input screen Gb (step S5), it causes the display unit 17 to display the amount input screen Gd (step S6). Next, when the amount corresponding to the price of the product is input based on the amount input screen Gd (step S7), the registration processing unit 112 associates the product code read in step S2, the tax category (tax category code) corresponding to the tax category input button operated in step S5, and the amount (price) input in step S7, and registers them in the additional PLU table 143 (step S8).

[0096] Next, the registration processing unit 112 reads out product information of the product corresponding to the product code read in step S2 from the product master 142 or the additional PLU table 143, and registers the read out product information together with the product code, quantity, etc. in the product registration file 145 (step S9). Next, the display control unit 113 updates the product registration screen Ga by displaying the registration data of the product registered in step S9 on the product registration screen Ga (step S10).

[0097] Here, for products that are not registered in the product master 142 and the additional PLU table 143, the name of the tax category registered in the product registration file 145 is displayed as the name on the product registration screen Ga. Also, when the eat-in mode is selected, the tax category code for eat-in is registered in the product registration file 145.

[0098] Next, the payment processing unit 114 judges whether or not a closing operation to instruct the completion of product registration or the start of a transaction has been received via the operation unit 18 (step S11). If the closing operation has not been received (step S11; No), the payment processing unit 114 returns the process to step S2. On the other hand, if the payment processing unit 114 receives a closing operation (step S11; Yes), it executes the payment process based on the registration data for one transaction registered up to that point in the product registration file 145 (step S12).

[0099] When the payment process is completed, the payment processor 114 uses the printer 22 to output a receipt with the details of the transaction printed thereon based on the registration data registered in the product registration file 145 (step S13), and ends this process. Note that the reading controller 111 may stop the operation of the scanner 19 when the payment process is completed.

[0100] As described above, the POS terminal 10 of this embodiment acquires product identification information capable of identifying a product, and if the acquired product identification information is not registered in the product master 142, it accepts input of the tax category of the product corresponding to the acquired product identification information, and outputs a name corresponding to the input tax category.

[0101] As a result, in the product sales data processing device of this embodiment, even if an unregistered product that is not registered in the product master is registered as a purchase target, it is possible to output a name corresponding to the tax category set for the unregistered product, rather than outputting a predetermined fixed name. Therefore, in the product sales data processing device of this embodiment, it is possible to clearly output the transaction details of the product.

[0102] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of the above-described device. Therefore, some modified examples of the above-described embodiment will be described below as other embodiments. Note that the following mainly describes the differences from the above-described embodiment, and a detailed description of the common points with the contents already described will be omitted. The modified examples described below may be implemented individually or in appropriate combination.

[0103] (Variation 1) In the above-described embodiment, the POS terminal 10 is operated by a store clerk and performs processes related to the registration and payment of products purchased by customers, but the POS terminal 10 may be configured so that customers themselves perform processes related to the registration and payment of products to be purchased (e.g., a fully self-service register, etc.).

[0104] In the configuration of this modified example, when registering a product (say product X) that is not stored in the product master 142, the customer often does not know the correct price or tax category of product X, so a store clerk needs to take over the process related to product registration. Therefore, in the above-mentioned embodiment, it is preferable to interrupt the product registration process between steps S3 and S4 in Fig. 14, for example, and notify the customer to register the product again at a cash register where a store clerk is present, or to display a message on the display unit 17 calling a store clerk so that the store clerk will take over the process related to product registration up to step S9. This can achieve the same effect as the above-mentioned embodiment.

[0105] (Variation 2) In the above embodiment, the destination of the registration data for one transaction registered in the product registration file 145 sent from the POS terminal 10 was one accounting machine, but one or more accounting machines may be set as the destination of the registration data, and the registration data may be sent to an available accounting machine at the timing of sending the registration data. Alternatively, a server connected to the network N may be set as the destination of the registration data, and the registration data may be stored in the server in association with the transaction number for one transaction. The customer may then enter the transaction number at any accounting machine to obtain the registration data via the server.

[0106] (Variation 3) In the above embodiment, the POS terminal 10 is configured to register products and perform accounting, but this is not limited to the above. For example, there exists a checkout system called a semi-self-service type in which a store clerk operates the POS terminal 10 (registration machine) to register products, and a customer operates a separate accounting machine to perform accounting for the products. The configuration of the above embodiment can be applied to such a checkout system as well.

[0107] The process of registering products and processing a transaction performed by the POS terminal 10 according to this modification will be described below with reference to Fig. 15. Note that a description of steps common to Fig. 14 will be omitted.

[0108] First, when the payment processor 114 accepts a closing operation (step S11; Yes), it transmits the registration data for one transaction registered in the product registration file 145 to the separate payment machine (step S20). Next, the payment machine receives the registration data from the POS terminal 10 (step S21) and executes the payment process (step S12).

[0109] Here, with regard to the receipt issued in the payment process in step S12, the product name of the unregistered product shown in the receipt data is shown in the name of the tax classification, as in the above embodiment.

[0110] The destination of the registration data for one transaction sent from the POS terminal 10 is not limited to the accounting machine. For example, the destination of the registration data for one transaction sent from the POS terminal 10 and the transaction ID assigned to each piece of registration data for one transaction may be the store server 20. In this case, the store server 20 compares the transaction ID sent from the POS terminal 10 and stored in the store server 20 with the transaction ID sent from the accounting machine, and transfers the registration data for one transaction corresponding to the matching ID to the accounting machine. This can achieve the same effect as the above-mentioned embodiment.

[0111] (Variation 4) In the above embodiment, the tax category code of an unregistered product and the name of the tax category corresponding to the tax category code are registered in the product registration file 145, but this is not limited to the above, and the configuration may be such that only the tax category code is registered.

[0112] In this case, when the registration processing unit 112 receives a selection (input) operation of a tax category code for an unregistered product, it associates the received tax category code with the product code of the unregistered product and registers them in the product registration file 145. In addition, when outputting the product name of the unregistered product registered in the product registration file 145, the display control unit 113 and the settlement processing unit 114 read and output the name of the tax category corresponding to the tax category code from the tax category table 144. This makes it possible to achieve the same effects as the above-mentioned embodiment.

[0113] With the above-mentioned configuration, even a POS terminal 10 having only a product registration function can achieve the same effects as the above-mentioned embodiment.

[0114] The program executed by the POS terminal 10 of the embodiment is provided in an installable or executable format file recorded on a non-transitory computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disc (DVD).

[0115] The program executed by the POS terminal 10 of the embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. The program executed by the POS terminal 10 of the embodiment may be provided or distributed via a network such as the Internet.

[0116] Furthermore, the programs executed by the POS terminal 10 of the embodiment may be provided by being pre-installed in a ROM or the like.

[0117] Although the embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. These new embodiments and their modifications can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0118] 1. Product sales data processing system 10. POS terminals 17 Display section 20 Store Server 111 Reading control unit 112 Registration processing unit 113 Display control unit 114 Payment processing unit 142 Product Master 143 Additional PLU Table 144 Tax Category Table 145 Product Registration File [Prior art documents] [Patent documents]

[0119] [Patent Document 1] Patent Publication No. 04-065795

Claims

1. An acquisition unit that acquires product identification information capable of identifying a product; a determination unit that determines whether the product identification information acquired by the acquisition unit is registered in a product master that associates product identification information with a name of a product corresponding to the product identification information; a reception unit that receives an input of a tax category of a product corresponding to the product identification information acquired by the acquisition unit when the determination unit determines that the product identification information is not registered; an output unit that outputs a name corresponding to the input tax category as a product name; A product sales data processing device comprising:

2. and a registration unit that, when it is determined by the determination unit that the product identification information is not registered, registers the product identification information acquired by the acquisition unit and the tax category accepted by the acceptance unit in an additional master different from the product master in association with each other, the determination unit determines whether the product identification information acquired by the acquisition unit is registered in the product master or the additional master. The product sales data processing device according to claim 1 .

3. When the determination unit determines that the product identification information is registered, the output unit outputs a name of the product corresponding to the product identification information acquired by the acquisition unit based on the registered information.

3. A product sales data processing device according to claim 1 or 2.

4. The reception unit displays a screen on a display unit on which one tax category can be selected from a plurality of tax categories, and receives an input of the tax category selected from the screen. The product sales data processing device according to claim 1 .

5. The output unit displays or prints out a name corresponding to a tax category registered in the product master or the additional master. The product sales data processing device according to claim 1 .

6. A computer of a product sales data processing device, An acquisition unit that acquires product identification information capable of identifying a product; a determination unit that determines whether the product identification information acquired by the acquisition unit is registered in a product master that associates product identification information with a name of a product corresponding to the product identification information; a reception unit that receives an input of a tax category of a product corresponding to the product identification information acquired by the acquisition unit when the determination unit determines that the product identification information is not registered; an output unit that outputs a name corresponding to the input tax category as a product name; A program that makes a computer function as a

Images