Sales data processing system and program

Abstract

This sales data processing system includes a terminal device that performs a process of receiving a customer's operation during shopping to register product information, and comprises a time limit checking unit that performs a process of checking whether or not time limit information included in the product information exceeds the current date and time, at least once between a first operation that is an operation for registering the product information on the terminal device, and a second operation that is an operation for starting a process related to payment for the registered product.

Description

Sales data processing system and program

[0001] FIELD An embodiment of the present invention relates to a sales data processing system and a program.

[0002] 2. Description of the Related Art Conventionally, there is a sales data processing system including a terminal device (see, for example, Patent Document 1) that performs a process of registering product information through operations by customers who are shopping around.

[0003] In the above-mentioned system, even if the expiration date of the product a customer is trying to purchase has passed, this is not discovered while the customer is shopping. For this reason, with the above-mentioned system, for example, the expiration date is discovered when the customer finishes shopping and leaves the sales floor, and it takes time and effort to bring a replacement product from the sales floor.

[0004] The problem to be solved by the present invention is to provide a sales data processing system and program that can reduce the number of steps required when the expiration date set for a product to be purchased has passed.

[0005] The sales data processing system of the embodiment includes a terminal device that performs a process of registering product information through operations by customers who are shopping around, and is equipped with a deadline check unit that performs a check process to determine whether the deadline information included in the product information exceeds the current date and time at least once between the time when a first operation is performed on the terminal device to register product information and the time when a second operation is performed to start processing related to payment for the registered product.

[0006] FIG. 1 is a diagram illustrating an example of the configuration of a sales data processing system according to an embodiment. FIG. 2 is a block diagram illustrating an example of the configuration of a server. FIG. 3 is a diagram illustrating an example of items included in a product master. FIG. 4 is a diagram illustrating an example of items included in a deadline master. FIG. 5 is a diagram illustrating an example of a screen displayed on a display unit by a web browser running on an attendant terminal. FIG. 6 is a diagram illustrating a barcode containing deadline information. FIG. 7 is a block diagram illustrating an example of the configuration of a mobile POS. FIG. 8 is a block diagram illustrating an example of the configuration of a store server. FIG. 9 is a block diagram illustrating an example of the configuration of an attendant terminal. FIG. 10 is a block diagram illustrating an example of various functional units included in each control unit and how they work together. FIG. 11 is a sequence diagram illustrating the flow of processing executed in a first example. FIG. 12 is a diagram illustrating an example of a screen displayed on a display unit of a mobile POS. FIG. 13 is a diagram illustrating an example of a screen notifying a customer of a deadline error. FIG. 14 is a diagram illustrating an example of a screen displayed on a display unit of a mobile POS. FIG. 15 is a diagram illustrating an example of a screen displayed on a display unit of an attendant terminal. FIG. 16 is a diagram illustrating another example of the screen illustrated in FIG. 14. FIG. 17 is a sequence diagram showing the flow of processing executed in the second example. FIG. 18 is a diagram showing an example of a screen notifying a customer of an error. FIG. 19 is a diagram showing an example of a screen displayed on the display unit of the attendant terminal. FIG. 20 is a diagram showing an example of a list screen. FIG. 21 is a diagram showing an example of a details screen. FIG. 22 is a diagram showing an example of a screen notifying a store clerk of the occurrence of an expiration error and how to deal with it. FIG. 23 is a diagram showing another example of the screen shown in FIG. 16. FIG. 24 is a sequence diagram showing the flow of processing executed in the third example. FIG. 25 is a sequence diagram showing the flow of processing executed in the fourth example. FIG. 26 is a diagram showing a screen displayed on the display unit of the mobile POS. FIG. 27 is a sequence diagram showing the flow of processing executed in the fifth example. FIG. 28 is a diagram showing a screen displayed on the display unit of the mobile POS. FIG. 29 is a diagram showing an example of a screen displayed on the display unit of the mobile POS. FIG. 30 is a diagram showing a screen displayed on the display unit of the mobile POS.

[0007] (First embodiment) An embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a sales data processing system according to this embodiment. The sales data processing system according to this embodiment includes a server 1, a mobile POS 3, a store server 4, an attendant terminal 5, a checkout machine 6, a POS terminal 7, a self-checkout 8, and a label printer 9. Note that "POS" is an abbreviation for "Point of Sale" and means "point of sale information management." The mobile POS 3, the POS terminal 7, and the self-checkout 8 constitute an embodiment of a sales data processing device that processes product registration, payment for registered products, and the like.

[0008] The mobile POS 3 is an example of a terminal device that registers product information through operations performed by customers while shopping. The mobile POS 3 is a mobile terminal (e.g., a smartphone or tablet terminal) on which a POS app (application software) runs. The POS app is provided by an external system. The mobile POS 3 provides POS functions by launching the downloaded and installed POS app.

[0009] The mobile POS 3 registers products in response to customer operation. The payment machine 6 processes the payment for products registered on the mobile POS 3 in response to customer operation. The POS terminal 7 registers products and processes the payment in response to store clerk operation. The self-checkout register 8 registers products and processes the payment in response to customer operation. The label printer 9 prints and issues labels to be affixed to products. The labels display the product name, product code, code symbol such as a barcode or two-dimensional code, selling price, production date and time, etc.

[0010] 2 is a block diagram showing an example of the configuration of the server 1. The server 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a communication unit 14, a storage unit 19, etc.

[0011] The CPU 11 is an example of a processor and performs overall control of each unit of the server 1. The ROM 12 stores various programs. The RAM 13 is a workspace for expanding the programs and various data. The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like to form a control unit 10 of a computer configuration.

[0012] The communication unit 14 is a communication interface that connects the control unit 10 to other devices (such as the mobile POS 3, the store server 4, and the attendant terminal 5) via the network 2 so that they can communicate with each other.

[0013] The storage unit 19 has a storage medium such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory, and maintains its stored contents even when the power is turned off. The storage unit 19 stores various setting information such as a program 191 executable by the CPU 11, a product master 192, and a term master 193. The storage unit 19 also stores transaction information 195 received from each store.

[0014] 3 is a diagram showing an example of items included in the product master 192. The product master 192 is an example of product information, and is information about products handled by a store (product information) compiled, for example, in the form of a table. Items in the product master 192 include, for example, the following: Product code Product name Category Unit price Image

[0015] The product code is an example of information (identification information) that can identify a product, such as a JAN code. Other information (product name, category, unit price, etc.) is stored in association with the product code.

[0016] The "product name" field records the name of the product. The "classification" field records the classification (department, category) of the product, with values ​​such as "fruit and vegetables," "prepared foods," "daily necessities," and "processed foods." The "unit price" field records the price of one product.

[0017] When registering a product, the mobile POS 3, POS terminal 7, and self-checkout 8 refer to the product master 192 stored in the server 1 to obtain product information.

[0018] Fig. 4 is a diagram showing an example of items included in the term master 193. Fig. 5 is a diagram showing an example of a screen 551 that the web browser running on the attendant terminal 5 displays on the display unit 55.

[0019] The expiration master 193 is a table containing information on how to handle products with expiration dates (use-by dates or best-before dates) when the expiration date approaches, among the products handled by the store. The expiration master 193 stores at least part of the product information (for example, product code) in association with expiration date information (described later). The expiration master 193 can be viewed and edited from the screen 551.

[0020] The items of the expiration master 193 are, for example, as follows: Product code Best before date Time / date Automatic expiration condition Condition Value

[0021] Screen 551 is a screen for referencing and editing the deadline master 193, and includes fields 5501, 5502, 5505, and 5511 to 5514 for accepting input or displaying information, and controls 5503, 5504, and 5506 to 5510. Field 5501 accepts and displays the input of a product code. The product code is the same as that described above.

[0022] Operators 5503 and 5504 on screen 551 are operators that determine whether the value that field 5505 accepts and displays is the number of hours or the date. The value of field 5505 (the number of hours or the date) is recorded in the "Best Before Date" item of the expiration date master 193. The value of the number of hours is, for example, "40" (unit: hours).

[0023] Operators 5503 and 5504 on screen 551 are so-called toggle buttons; selecting one releases the other. When operator 5503 is selected, "Time" is recorded in the "Time / Date" field of the expiration master 193. This indicates that the value recorded in the expiration date field of the expiration master 193 is the number of hours. Furthermore, when operator 5504 is selected, "Date" is recorded in the "Time / Date" field of the expiration master 193. This indicates that the value recorded in the expiration date field of the expiration master 193 is a date.

[0024] Operators 5506 and 5507 on screen 551 are so-called toggle buttons; selecting one releases the other. When operator 5506 is selected, "Not applicable" is recorded in the "Automatic Discount" field of the expiration master 193. When operator 5507 is selected, "Applicable" is recorded in the "Automatic Discount" field of the expiration master 193. When the value of the "Automatic Discount" field is "Applicable," automatic discounting is performed. Automatic discounting is a process that automatically discounts a product a specified time before the expiration date (use-by date or best-before date).

[0025] Operators 5508 to 5510 on screen 551 are so-called toggle buttons; when one is selected, the other two are deactivated. When operator 5508 is selected, "Discount" is recorded in the "Clearance Conditions" field of the term master 193. When operator 5509 is selected, "Price Discount" is recorded in the "Clearance Conditions" field of the term master 193. When operator 5510 is selected, "Set Price" is recorded in the "Clearance Conditions" field of the term master 193.

[0026] The discount defines a discount rate from the unit price, such as 30% off. The markdown defines an amount to be deducted from the unit price, such as 30 yen off. The set price defines an amount to be set as the selling price, such as 50 yen.

[0027] Column 5511 accepts and displays the input of a condition. For example, the condition is "1.0 (hours ago)." Columns 5512 to 5514 are columns that accept and display the input of a value for the condition, and one of them corresponding to the state of controls 5508 to 5510 is made inputtable. For example, when control 5508 is selected, column 5512 is made inputtable. The value input into column 5512 is, for example, "30 (% off)." The input content of column 5511 is recorded in the "Condition" field of the deadline master 193. Furthermore, the input content of columns 5512 to 5514 that matches the state of controls 5508 to 5510 is recorded in the "Value" field of the deadline master 193.

[0028] 6 is a diagram illustrating a barcode containing expiration date information. A barcode is an example of a code symbol and is displayed on a label attached to a product package, etc. In this embodiment, the barcode contains not only a product code but also expiration date information. Barcodes containing expiration date information are often attached to products with a relatively short expiration date of, for example, a few days, such as prepared foods prepared and sold in a store.

[0029] The barcode described above contains the following information: (1) Product code (2) Date and time (3) Date printing flag (4) Value discount processing flag (5) Value discount data (6) Check digit (C / D) The check digit is the same as the existing one, so a description thereof will be omitted.

[0030] (1) The product code is the same as that described above. (2) The date and time are the expiration date (use-by date or best-before date) and are an example of expiration date information. In the illustrated example, the year, month, and day are each shown in two digits.

[0031] (3) The date printing flag indicates whether or not the expiration date is printed on the label attached to the product. If this flag is, for example, "1," this indicates that (2) the date corresponding to the date and time is printed.

[0032] (4) The discount processing flag specifies the method of discount processing. The value of the discount processing flag is, for example, 0, 1, 2, or 3. (5) The discount data is one of the discount rate, discount amount, or selling price, and corresponds to the discount processing flag.

[0033] For example, a discount processing flag of "0" indicates that the product is subject to automatic clearance. The example shown in FIG. 5 is an example of setting a product that is subject to automatic clearance.

[0034] In addition, a value discount processing flag of "1" indicates that the selling price is the unit price discounted by the value (discount rate) of the (5) value discount data, "2" indicates that the selling price is the unit price discounted by the value (discount amount) of the (5) value discount data, and "3" indicates that the value of the (5) value discount data will be the selling price instead of the unit price.

[0035] Returning to Figure 2, the transaction information 195 is information about products purchased by customers, compiled, for example, in the form of a table. The server 1 stores (accumulates) new transaction information 395 (described later) received from the mobile POS 3 as transaction information 195 in the storage unit 19 and manages it. Items in the transaction information 195 include, for example, the following: Transaction ID Date and time Store ID Terminal ID Store clerk ID Product information Total

[0036] The transaction ID is an example of information (identification information) for identifying a transaction. The transaction ID is automatically assigned (numbered), for example, during the initial product registration process for the transaction. The date and time is the date and time when the transaction in the record was made. The store ID, terminal ID, and clerk ID are identification information for the store, terminal (such as the POS terminal 7), and clerk where the transaction in the record was made.

[0037] Here, for a combination of transaction ID, date and time, and store ID, there is one item in total, but multiple items of product information may be associated. Product information includes, for example, the following items: Product code Quantity Price

[0038] The total is the total price (total amount) of all products purchased in the transaction of the record. The product code is as described above. The quantity is the quantity (number, weight, volume, etc.) of the product indicated by the product code purchased in the transaction of the record. The price is the unit price (or selling price) multiplied by the quantity.

[0039] It is not necessary that the program 191 , the product master 192 , the term master 193 and the transaction information 195 are stored in the same storage unit 19 .

[0040] 7 is a block diagram showing an example of the configuration of the mobile POS 3. The mobile POS 3 is realized by, for example, a mobile terminal (such as a smartphone or a tablet terminal), and includes a CPU 31, a ROM 32, a RAM 33, a communication unit 34, a display unit 35, an operation unit 36, an audio output unit 37, an imaging unit 38, a storage unit 39, etc.

[0041] The CPU 31 is an example of a processor and controls all parts of the mobile POS 3. The ROM 32 stores various programs. The RAM 33 is a workspace for storing programs and various data. The CPU 31, ROM 32, and RAM 33 are connected via a bus or the like to form the control unit 30, which is a computer configuration.

[0042] The communication unit 34 is a communication interface that connects the control unit 30 to other devices (such as the server 1) via the network 2 so that they can communicate with each other.

[0043] The display unit 35 has a display device such as an LCD (Liquid Crystal Display), and displays various types of information under the control of the CPU 31 .

[0044] The operation unit 36 ​​has input devices such as a touch panel provided over the surface of the display unit 35 , a keyboard, and a pointing device, and outputs operation contents input via the input devices to the CPU 31 .

[0045] The audio output unit 37 has a speaker and a buzzer, and outputs audio under the control of the CPU 31 .

[0046] The imaging unit 38 is a camera installed in a device (such as a smartphone or tablet terminal) that implements the mobile POS 3. The mobile POS 3 has a function for decoding a code symbol (such as a barcode or two-dimensional code) included in the captured image output by the imaging unit 38. If the code symbol is, for example, an encoded product code, this function outputs the product code.

[0047] The mobile POS 3 may receive an output from a device such as a code scanner connected via a wired or wireless connection, and obtain a value obtained by the device reading and decoding a code symbol.

[0048] The storage unit 39 has a storage medium such as an HDD, an SSD, or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 39 stores a program 391 executable by the CPU 31, transaction information 395, and the like.

[0049] The program 391 is application software for making the mobile POS 3 function.

[0050] The transaction information 395 is information on the products registered by the customer for purchase (i.e., the products to be transacted), compiled, for example, in the form of a table. The items in the transaction information 395 are substantially the same as those in the transaction information 195, and therefore will not be described here. The mobile POS 3 obtains product information from the server 1 each time a product is registered.

[0051] The transaction information 395 may be stored in the RAM 33 instead of the storage unit 39. The storage unit 39 or the RAM 33 stores the transaction information 395, which is information about registered products (registered products), from the start to the completion of at least one transaction. A transaction is completed upon completion of the checkout process. The checkout process is a process in which payment for the registered products is received from the customer. Payment can be made at the checkout machine 6 by cash or electronic payment such as credit card payment or electronic money payment.

[0052] 8 is a block diagram showing an example of the configuration of the store server 4. The store server 4 includes a CPU 41, a ROM 42, a RAM 43, a communication unit 44, a storage unit 49, and the like.

[0053] The CPU 41 is an example of a processor and controls all parts of the store server 4. The ROM 42 stores various programs. The RAM 43 is a workspace for storing programs and various data. The CPU 41, ROM 42, and RAM 43 are connected via a bus or the like to form the control unit 40 of a computer configuration.

[0054] The communication unit 44 is a communication interface that communicatively connects the control unit 40 to other devices (such as the server 1) via the network 2. The communication unit 44 also communicatively connects the control unit 40 to other devices in the store (such as the accounting machine 6, POS terminal 7, self-checkout 8, label printer 9, etc.) via a network such as a LAN (Local Area Network) installed in the store.

[0055] The storage unit 49 has a storage medium such as an HDD, SSD, or flash memory, and maintains its stored contents even when power is cut off. The storage unit 49 stores various setting information such as a program 491 executable by the CPU 41, a product master 492, and a deadline master 493.

[0056] The storage unit 49 stores a product master 492 and a term master 493 so that they can be referenced by devices within the store. The product master 492 and the term master 493 contain substantially the same items as those in the product master 192 and the term master 193.

[0057] The product master 492 and the expiration master 493 are obtained by acquiring information for the store (i.e., records associated with the store's store ID) from the product master 192 and the expiration master 193 stored in the server 1. The store server 4 receives information for the store from the server 1 at a predetermined timing (for example, during the time period after closing time and before opening time) and updates the product master 492 and the expiration master 493.

[0058] 9 is a block diagram showing an example of the configuration of the attendant terminal 5. The attendant terminal 5 is realized by a device such as a PC (Personal Computer), and includes a CPU 51, a ROM 52, a RAM 53, a communication unit 54, a display unit 55, an operation unit 56, an audio output unit 57, a storage unit 59, etc.

[0059] The CPU 51 is an example of a processor and controls all components of the attendant terminal 5. The ROM 52 stores various programs. The RAM 53 is a workspace for storing programs and various data. The CPU 51, ROM 52, and RAM 53 are connected via a bus or the like to form a control unit 50 having a computer configuration.

[0060] The communication unit 54 is a communication interface that communicatively connects the control unit 50 to other devices (e.g., the server 1) via the network 2. The communication unit 54 also communicatively connects the control unit 50 to other devices in the store (e.g., the store server 4, the accounting machine 6, the POS terminal 7, the self-checkout 8, the label printer 9, etc.) via a network such as a LAN installed in the store.

[0061] The display unit 55 has a display device such as an LCD, and displays various information under the control of the CPU 51 .

[0062] The operation unit 56 has input devices such as a touch panel provided over the surface of the display unit 55 , a keyboard, and a pointing device, and outputs operation contents input via the input devices to the CPU 51 .

[0063] The audio output unit 57 has a speaker and a buzzer, and outputs audio under the control of the CPU 51 .

[0064] The storage unit 59 has a storage medium such as an HDD, an SSD, or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 59 stores a program 591 that can be executed by the CPU 51.

[0065] The program 591 is application software for making the attendant terminal 5 function.

[0066] 10 is a block diagram showing an example of various functional units and their cooperation in each of the control units 10, 30, 40, and 50. The control units 10, 30, 40, and 50 provide the various functional units shown in FIG.

[0067] The control unit 10 of the server 1 functions as a master linkage unit 101, a registration unit 102, a deadline check unit 105, a notification unit 106, and a deadline processing unit 107. The control unit 40 of the store server 4 functions as a master linkage unit 401. The control unit 30 of the mobile POS 3 functions as a reading unit 301, a checkout unit 309, and a notification unit 306. The control unit 50 of the attendant terminal 5 functions as a setting processing unit 501 and a notification unit 506.

[0068] The master data linking unit 101 achieves master data linking by transmitting (sending) updates to the product master data 192 and the expiration date master data 193 to the store server 4 at a predetermined timing (for example, during the time period between closing time and opening time). The master data linking unit 401 achieves master data linking by updating the product master data 492 and the expiration date master data 493 based on information transmitted (received) from the server 1.

[0069] The setting processing unit 501 accepts input, change, and update of settings via a screen 551 displayed on the display unit 55 .

[0070] The reading unit 301 outputs to the server 1 a value obtained by decoding the code symbol included in the captured image output by the imaging unit 38 .

[0071] When the registration unit 102 receives the value obtained by decoded the code symbol from the mobile POS 3, if the value contains a product code, the registration unit 102 performs product registration processing. That is, the registration unit 102 obtains product information that matches the received product code from the product master 192 and registers it as transaction information 195.

[0072] Furthermore, if the decoded value of the received code symbol contains expiration information, the registration unit 102 passes the decoded value of the code symbol to the expiration check unit 105 and waits for the result prior to the product registration process, and if the result is not an expiration error (described later), performs the product registration process.

[0073] The accounting unit 309 starts the accounting process in response to the customer's operation received via the operation unit 36. In this process, the accounting unit 309 displays on the display unit 35 a code symbol for linking information identifying the transaction (e.g., a transaction ID) to the accounting machine 6.

[0074] The accounting machine 6 reads the code symbol displayed on the display unit 35, references the record in the transaction information 195 that matches the information (e.g., transaction ID) obtained from the decoded value of the code symbol, and performs accounting processing for the transaction indicated by the information in that record (receives payment from the customer).

[0075] The expiration date check unit 105 checks at least once within a specified period to determine whether the expiration date included in the product information has passed the current date and time. The specified period is the period from the first operation, which is an operation for registering product information in the mobile POS 3, to the second operation, which is an operation for starting the payment process for the registered product. In this embodiment, the first operation is to have the image capture unit 38 capture an image of a code symbol. Furthermore, the second operation in this embodiment is an operation on an operator 3509 (see FIG. 12 and other figures, described below) that accepts an operation for starting the checkout process.

[0076] Specifically, when the expiration date check unit 105 receives the above information (the decoded value of the code symbol) from the registration unit 102, it checks the expiration dates of the products registered by the registration unit 102. Furthermore, the expiration date check unit 105 may perform an expiration date check on the products registered in the currently ongoing transaction upon receiving the above information from the registration unit 102. Furthermore, when the expiration date check unit 105 receives information from the accounting unit 309, it may perform an expiration date check process on the products related to the transaction that is the subject of accounting processing.

[0077] In the expiration date check process, the expiration date check unit 105 determines that an expiration date (use by date or best before date) (2) has passed (exceeded) the current date and time, and determines that this is an expiration date error. The expiration date check unit 105 passes the result of the expiration date check to the registration unit 102. Furthermore, if the result of the expiration date check is an expiration date error, the expiration date check unit 105 passes the result to the notification unit 106.

[0078] When the notification unit 106 receives information indicating a deadline error from the deadline check unit 105, it transmits (sends) information informing the mobile POS 3 and the attendant terminal 5 about the deadline error. When the notification unit 306 of the mobile POS 3 receives information from the notification unit 106, it notifies the customer of the information using the display unit 35 or the like. When the notification unit 506 of the attendant terminal 5 receives information from the notification unit 106, it notifies the store clerk of the information using the display unit 55 or the like.

[0079] Furthermore, if the (4) discount processing flag is “0”, the deadline check unit 105 acquires information on a record that matches the product code from the deadline master 193 and passes it to the deadline processing unit 107 .

[0080] When a first operation is performed, the expiration processing unit 107 performs discount processing based on the difference between the expiration date and time indicated in the expiration information of the product registered by the first operation and the current date and time. The discount processing is processing related to handling such as discounting products whose expiration date is approaching.

[0081] Specifically, when the deadline processing unit 107 receives information on the deadline master 193 from the deadline checking unit 105, it discounts the corresponding product based on the clearance conditions defined in the deadline master 193 and the combination of conditions 1 to 5 and values ​​1 to 5. Furthermore, the deadline processing unit 107 performs processing related to the handling of products that have been determined to have a deadline error by the deadline checking unit 105, such as selling them after receiving confirmation from the customer that the deadline has passed.

[0082] (First Example) FIG. 11 is a sequence diagram showing the flow of processing executed in the first example in the sales data processing system of this embodiment.

[0083] First, the server 1 (master data linking unit 101) and the store server 4 (master data linking unit 401) perform master data linking at a predetermined timing (for example, while the store is closed) (step S1).

[0084] When the store is open, a customer uses the mobile POS 3. The customer scans the code symbol using the mobile POS 3 (step S2). That is, the customer holds the label attached to the product over the imaging unit 38. The imaging unit 38 then outputs a captured image including the code symbol displayed on the label. The reading unit 301 reads the code symbol included in the captured image and outputs the decoded value of the code symbol to the server 1 (step S3).

[0085] The registration unit 102 performs product registration processing when the decoded value of the code symbol does not contain expiration information, or when the current date and time has not passed the expiration date and time indicated by the expiration information. The information added to the transaction information 195 in this processing is sent to the mobile POS 3 and added to the transaction information 395. The transaction information 395 is reflected on a screen 351, which will be described next.

[0086] 12 is a diagram showing an example of a screen 351 displayed on the display unit 35 of the mobile POS 3. The screen 351 displays information about registered products, and includes a total number of points 3501, a total amount 3502, information about registered products 3503 and the number of points for the products 3504, information about the most recently registered product 3505 and the number of points for the product 3506, and an operator 3509.

[0087] An operator 3509 accepts an operation to start the checkout process. When the operator 3509 is operated, the control unit 30 starts processing as the checkout unit 309. The total number of items 3501 is the number of all registered products. The total amount 3502 is the total selling price of all registered products. Product information 3503, 3505 is, for example, product name, taxation information (tax exclusive, tax included, tax rate, etc.), selling price, etc.

[0088] If the value obtained by decoded the code symbol contains expiration information, the registration unit 102 passes the value to the expiration check unit 105 and waits for the result. Upon receiving the value, the expiration check unit 105 performs expiration check processing (step S4) and returns the result to the registration unit 102.

[0089] When the registration unit 102 receives the result of the expiration check from the expiration check unit 105 and the result of the expiration check is an expiration error, that is, the current date and time has passed the expiration date and time, the registration unit 102 does not perform product registration processing for the code symbol.

[0090] Furthermore, if the result of the expiration check is an expiration error, the expiration check unit 105 passes the result to the notification unit 106. Upon receiving this, the notification unit 106 notifies the mobile POS 3 of the error (step S5) and also notifies the attendant terminal 5 of the occurrence of the error (step S6).

[0091] 13 is a diagram showing an example of the screen 361. When the mobile POS 3 receives an error notification (step S5) from the server 1, the notification unit 306 notifies the customer of the expiration error by, for example, displaying the screen 361 on the display unit 35.

[0092] Screen 361 is, for example, a pop-up window that is displayed over a screen (such as screen 352 shown in FIG. 14 ) currently being displayed on the display unit 35 of the mobile POS 3. Figure 14 is a diagram showing an example of screen 352 displayed on the display unit 35 of the mobile POS 3. Screen 352, like that shown in FIG. 12, displays registered product information, but is displayed when the information about the last scanned product (information 3505 and score 3506 in FIG. 12 ) has not been registered.

[0093] Screen 361 (FIG. 13) includes message 3601 informing the user of the error and an operator 3609 for accepting the message 3601. Message 3601 may be, for example, "The expiration date has passed. Please replace the product and register again."

[0094] The customer who has checked the message 3601 operates the operator 3609. When the operator 3609 is operated, the control unit 30 closes the screen 361. In this case, the screen 352 (FIG. 14) remains on the display unit 35.

[0095] Thereafter, the customer returns the product with the expiration date error to the display location (step S7), and returns to step S2 to scan a new code symbol.

[0096] 15 is a diagram showing an example of a screen 561 displayed on the display unit 55 of the attendant terminal 5. When the attendant terminal 5 receives a notification of the occurrence of an error from the server 1 (step S6), the notification unit 506 notifies the store clerk of the occurrence of the expiration error and how to deal with it by, for example, displaying the screen 561 on the display unit 55, and requests a confirmation operation.

[0097] Screen 561 is, for example, a pop-up window that is displayed on display unit 55 of attendant terminal 5, superimposed on the currently displayed screen. Screen 561 includes message 5601 indicating the content of the notification and an operator 5609 that accepts an operation indicating that message 5601 has been confirmed. Message 5601 is, for example, "A scan of an expired product has been detected. Please check the sales floor and remove the expired product." Screen 561 may further include an image 5605 or the like to attract attention.

[0098] As described above, the process shown in Figure 11 can avoid the inconvenience of mistakenly registering a product that has expired before the time of registration. Therefore, for example, a customer will no longer find out that the product has expired when they check out after they have finished shopping and left the sales floor, so there is no need to go through the trouble of retrieving a replacement product from the sales floor after the start of the checkout. Therefore, this process can reduce the amount of work required when the expiration date of the product you are trying to purchase has passed.

[0099] (Another Screen Example) Figure 16 is a diagram showing a screen 353, which is another example of Figure 14 (screen 352). Screen 353, like Figures 12 and 14, is a screen that displays information about registered products. In practice, as shown in Figure 16, information 3505 and the score 3506 of products that were not registered due to a deadline error may be displayed on screen 353 in a manner that allows them to be distinguished from information 3503 of registered products, etc.

[0100] To enable the above-mentioned distinction on screen 353, information 3505 and score 3506 of a product that was not registered due to a deadline error may be displayed in a lighter color than, for example, information 3503 of a registered product. Also, to enable the above-mentioned distinction on screen 353, information 3505 and score 3506 of a product that was not registered due to a deadline error may be accompanied by, for example, information 3511 indicating the reason for the error or a strikethrough 3512. Information 3511 indicating the reason for the error may be a concise statement surrounded by a graphic such as an elongated circle, or may be a symbol or mark that can be associated with the reason for the error.

[0101] (Variation) In the sales data processing system of this embodiment, when, for example, the display field for expired product information 3505 is tapped on the screen 353 shown in FIG. 16 , a screen asking whether the customer wants to purchase the product (a confirmation screen for purchasing the expired product) may be displayed on the display unit 35 of the mobile POS 3. When the customer indicates their intention to purchase via the confirmation screen, the sales data processing system re-displays (re-displays) the expired product information 3505 and its score 3506 in a format similar to the registered product information 3503. Specifically, re-displaying in a similar format means, for example, removing the strikethrough 3512 from the display field for expired product information 3505.

[0102] 17 is a sequence diagram showing the flow of processing executed in the second example in the sales data processing system of this embodiment. In the second example, the expiration dates of the registered products are rechecked at the time of payment in response to a case where at least one of the registered products has expired before the time of payment.

[0103] In this process, steps S1 to S4 are the same as those in the first example, and therefore will not be described here. After step S4, if the value obtained by decoding the code symbol includes expiration information and the current date and time has not passed the expiration date and time indicated by the expiration information, the registration unit 102 performs product registration processing (step S15).

[0104] When the customer operates the operator 3509 to make a payment (step S21), the accounting section 309 of the mobile POS 3 checks the information of all registered products, and if there are any products with expiration information, it sends a request to the server 1 to recheck all expiration dates, along with the transaction ID of the transaction being handled (step S22).

[0105] When the server 1 receives the request, the expiration date check unit 105 rechecks, in the transaction information 195, all products associated with the transaction ID received with the request and having expiration date information to see if the current date and time has exceeded the expiration date and time (step S24).

[0106] If the recheck results in a deadline error, the deadline check unit 105 passes the result to the notification unit 106. Upon receiving this, the notification unit 106 notifies the mobile POS 3 of the error (step S25) and also notifies the attendant terminal 5 of the occurrence of the error (step S26).

[0107] 18 is a diagram showing an example of screen 362. When the control unit 30 of the mobile POS 3 receives an error notification from the server 1 (step S25), the notification unit 306 notifies the customer of the error by, for example, displaying screen 362 on the display unit 35. Screen 362 is, for example, a pop-up window that is displayed over the screen currently being displayed on the display unit 35 of the mobile POS 3.

[0108] Screen 362 includes message 3602 requesting confirmation from the customer and an operator 3609 for accepting an operation to approve message 3602. Message 3602 is, for example, "This item requires confirmation by the cashier. Please ask a cashier."

[0109] The customer who has checked the message 3602 waits for confirmation and operation by the store clerk. When the operator 3609 is operated, the control unit 30 closes the screen 362.

[0110] 19 is a diagram showing an example of a screen 562 displayed by the display unit 55 of the attendant terminal 5. When the attendant terminal 5 receives a notification of the occurrence of an error from the server 1 (step S26), the notification unit 506 notifies the store clerk of the occurrence of the expiration error and how to deal with it by, for example, displaying the screen 562 on the display unit 55.

[0111] Screen 562 is, for example, a pop-up window that is displayed superimposed on the screen currently being displayed on display unit 55 of attendant terminal 5. Screen 562 includes wording 5602 indicating the content of the notification and an operator 5609 for accepting an operation to acknowledge wording 5602. Wording 5601 is, for example, "A scan of an expired product has been detected. Please check your cart, replace the expired product, and register again."

[0112] After checking message 5602, the store clerk operates operator 5609. When operator 5609 is operated, control unit 50 closes screen 562. Next, the store clerk operates operation unit 56 to cause list screen 552 ( FIG. 20 ) to be displayed on display unit 55.

[0113] 20 is a diagram showing an example of the list screen 552. The list screen 552 includes a table in which each row shows the operating status of each terminal (mobile POS 3). The table includes items such as the terminal code (an example of identification information), stay time, time of last operation, number of registered items, status (operating status), payment machine number (identification information of the payment machine 6), and transaction number (transaction ID).

[0114] The list screen 552 includes a link 5522 to a details screen 553 ( FIG. 21 ) along with a mark 5521 indicating that the line requires the attention of a store clerk. When the link 5522 is operated, the control unit 50 of the attendant terminal 5 displays the details screen 553 ( FIG. 21 ) on the display unit 55.

[0115] FIG. 21 is a diagram showing an example of the details screen 553. The details screen 553 includes header information 5531 and detailed information 5532. The header information 5531 includes, for example, the terminal code, the total price and total number of registered products, etc. The detailed information 5532 includes, for example, information on the scan order, product name, quantity, price, and tax. Furthermore, the detailed information 5532 includes a mark 5533 indicating that a line requires the clerk's attention, information 5534 indicating the reason for the error, and a check point 5535. The information 5534 indicating the reason for the error is, for example, a concise statement surrounded by a graphic such as a long circle.

[0116] After checking the information about the target mobile POS 3 on the list screen 552 and the details screen 553, the clerk goes to the location where the customer is waiting and operates the target mobile POS 3. Here, the clerk carries a clerk ID card while on duty. The clerk ID card displays the clerk ID as a character string or a code symbol. The clerk ID is an example of information that can identify the clerk. The code symbol is a coded version of the clerk ID.

[0117] The store clerk proceeds to the area where the customer is waiting and holds the code symbol displayed on the store clerk ID over the image capture unit 38 of the mobile POS 3 (step S27). This causes the reading unit 301 to acquire the store clerk ID. The control unit 30 of the mobile POS 3 then displays screen 363 (FIG. 22) on the display unit 35.

[0118] 22 is a diagram showing an example of screen 363. The information displayed on screen 363 is similar to that displayed on screen 562, and informs the store clerk of the occurrence of an expiration error and how to deal with it. Screen 363 is, for example, a pop-up window that is displayed on the display unit 35 of the mobile POS 3, superimposed on the screen currently being displayed.

[0119] Screen 363 includes message 3603 indicating the content of the notification and an operator 3609 for accepting an operation to acknowledge message 3603. Message 3603 is, for example, "There is a product whose expiration date has passed. Please replace the product and register again."

[0120] The store clerk, having checked message 3603, operates operator 3609. When operator 3609 is operated, control unit 30 closes screen 363 and displays screen 353 ( FIG. 16 ). Screen 353 displays information 3505 about products that were not registered due to a deadline error and their scores 3506 in a manner that allows them to be distinguished from information 3503 about registered products, etc.

[0121] The store clerk then scans the code symbol attached to the replacement product (step S28), which causes the control unit 30 of the mobile POS 3 to return the process to step S3.

[0122] As described above, the process shown in FIG. 17 can avoid the inconvenience of accidentally purchasing an expired product when at least one of the registered products has expired before the time of payment.

[0123] (Other Screen Examples) Figure 23 is a diagram showing screen 354, which is another example of Figure 16 (screen 353). Screen 354 is an example in which mobile POS 3 is implemented on a tablet terminal. Screen 354 can display more information than screen 353, and further includes, for example, text 3510 and controls 3515. For example, text 3510 is "Expired products are present. A cashier will check."

[0124] The operator 3515 accepts an operation to cancel the registration of the product indicated by the row on which the operator 3515 is displayed. Since the screen 354 displayed after step S27 is displayed in the presence of a store clerk, the screen 354 can include the operator 3515 for performing an operation to cancel the registration of the product.

[0125] 24 is a sequence diagram showing the flow of processing executed in the third example in the sales data processing system of this embodiment. In the third example, the expiration date of a registered product is rechecked when the product is registered, in order to deal with the case where any registered product has expired before the time of payment.

[0126] The steps up to step S15 are the same as those in the second case, so the explanation will be omitted.

[0127] When the customer scans the second or subsequent product (step S31), the control unit 30 of the mobile POS 3 outputs the decoded value of the code symbol read by the reading unit 301 to the server 1 and performs processing in step S32. In step S32, the control unit 30 checks the information of all registered products, and if there is a product with expiration date information, sends a request to the server 1 to recheck all expiration dates, along with the transaction ID of the transaction in progress.

[0128] When the server 1 receives the request, the expiration date check unit 105 rechecks, in the transaction information 195, all products associated with the transaction ID received with the request and having expiration date information to see if the current date and time has exceeded the expiration date and time (step S34).

[0129] If the recheck results in a deadline error, the deadline check unit 105 passes the result to the notification unit 106. Upon receiving this, the notification unit 106 notifies the mobile POS 3 of the error (step S35) and also notifies the attendant terminal 5 of the occurrence of the error (step S36).

[0130] When the mobile POS 3 receives an error notification from the server 1 (step S35), the notification unit 306 notifies the customer of the expiration error by, for example, displaying screen 361 (FIG. 13) on the display unit 35. After the customer checks message 3601 on screen 361, they operate operator 3609. When operator 3609 is operated, the control unit 30 closes screen 361. In this case, screen 352 (FIG. 14) or screen 353 (FIG. 16) remains on the display unit 35.

[0131] Thereafter, the customer returns the product with the expiration date error to the display location (step S37), and returns to step S31 to scan a new code symbol.

[0132] As described above, the process shown in Figure 24 can avoid the inconvenience of products that have expired after registration remaining registered until the time of payment. Furthermore, this process allows customers to notice the expiration date before the start of payment, i.e., when they can return to the product display area (sales floor), so they can exchange the expired product as appropriate.

[0133] 25 is a sequence diagram showing the flow of processing executed in the fourth example in the sales data processing system of this embodiment. In the fourth example, when a product is registered, a discount is automatically applied to a product whose expiration date is approaching.

[0134] In this process, steps S1 to S3 and steps S21 to S28 are the same as those in the second case, and therefore a description thereof will be omitted.

[0135] After step S3, in the server 1, if the value obtained by decoded the code symbol contains not only the product code but also expiration date information as shown in Fig. 6, the registration unit 102 passes the value to the expiration date check unit 105 and waits for the result. Upon receiving the value, the expiration date check unit 105 checks the expiration date and returns the result to the registration unit 102. In this expiration date check, the expiration date check unit 105 checks whether an automatic discount is set (step S44).

[0136] In step S44, if the (4) discount processing flag included in the value obtained by decoding the code symbol is "0 (automatic)", the expiration check unit 105 checks the (2) date and time, and if the current date and time is past the (2) date and time, it refers to the expiration master 193. Next, if "automatic clearance" is "applicable" in the record of the corresponding product code in the expiration master 193, the expiration check unit 105 reflects the discount in the selling price according to the "clearance conditions", "conditions", and "price" in the expiration master 193, and registers the product (step S45).

[0137] 26 is a diagram showing a screen 355 displayed on the display unit 35 of the mobile POS 3. Screen 355 displays information about registered products and is displayed after step S45. Screen 355 displays information 3507 about products that were discounted upon registration and their quantity 3508, along with information 3521 indicating that the product has been discounted, information 3522 indicating the discount rate or amount, and a strikethrough 3523 to cancel the unit price. Information 3521 indicating that the product has been discounted may be simple text surrounded by a shape such as an elongated circle, or it may be a symbol or mark that can be associated with the fact that the product has been discounted.

[0138] As described above, according to the process shown in Fig. 25, it is possible to automatically discount products whose expiration date is approaching, which can be expected to have an effect on sales promotions, etc.

[0139] 27 is a sequence diagram showing the flow of processing executed in the fifth example in the sales data processing system of this embodiment. In the fifth example, if there is a product that is past due at the time of payment, and the customer confirms that the product is past due, the product is sold.

[0140] In this process, steps S1 to S4, step S15, and steps S21 to S25 are the same as those in the second case, and therefore the description thereof will be omitted.

[0141] 28 is a diagram showing screen 364 displayed on the display unit 35 of the mobile POS 3. When the control unit 30 of the mobile POS 3 receives an error notification from the server 1 (step S25), the notification unit 306 confirms the customer's intention (step S51), for example, by displaying screen 364 on the display unit 35. Screen 364 is, for example, a pop-up window that is displayed over the screen currently being displayed on the display unit 35 of the mobile POS 3.

[0142] Screen 364 includes a message 3604 requesting confirmation from the customer, and an operator 3609 for accepting an operation to acknowledge message 3604. Message 3604 is, for example, "There are some products that have passed their expiration date. Please check the products."

[0143] The customer who has checked the message 3604 operates the operator 3609. When the operator 3609 is operated, the control unit 30 closes the screen 364 and displays the screen 356 (FIG. 29).

[0144] 29 is a diagram showing an example of a screen 356 displayed on the display unit 35 of the mobile POS 3. On screen 356, information 3505 of a product with an expiration error and its quantity 3506 are displayed along with a control 3515 in a manner that allows them to be distinguished from information 3503 of products that do not have an expiration error. The control 3515 accepts an operation to cancel the registration of the product shown in the row on which the control 3515 is displayed.

[0145] When the customer performs a transaction start operation (operates the operator 3509) without operating the operator 3515, the control unit 30 displays the screen 365 (FIG. 30).

[0146] 30 is a diagram showing a screen 365 displayed on the display unit 35 of the mobile POS 3. The screen 365 is, for example, a pop-up window that is displayed on the display unit 35 of the mobile POS 3, superimposed on the screen currently being displayed.

[0147] Screen 365 includes a message 3605 requesting confirmation from the customer, and operators 3606 and 3607 for accepting a response to message 3605. Message 3605 is, for example, "There are expired products. Do you really want to purchase them?" Operator 3606 accepts an operation to convey an intention to purchase expired products. Operator 3607 accepts an operation to convey an intention not to purchase expired products.

[0148] The customer who has checked the message 3605 operates the operator 3606 or the operator 3607. When the operator 3607 is operated, the control unit 30 closes the screen 365 and returns the display of the display unit 35 to the screen 356.

[0149] Furthermore, when operator 3606 on screen 365 is operated (step S52), control unit 30 closes screen 365 and displays screen 362 ( FIG. 18 ). After checking message 3602 on screen 362, the customer waits for confirmation and operation by the store clerk. When operator 3609 is operated, control unit 30 closes screen 362.

[0150] When the control unit 30 of the mobile POS 3 receives the response operation in step S52, it transmits a notification to that effect to the server 1 (step S53).

[0151] When the control unit 10 of the server 1 receives the notification in step S53, it transmits a notification indicating this to the attendant terminal 5 (step S54).

[0152] When the control unit 50 of the attendant terminal 5 receives the notification in step S54, the notification unit 506 notifies the store clerk of the occurrence of the expiration error and how to deal with it, for example by displaying screen 562 (FIG. 19) on the display unit 55.

[0153] After checking the message 5602 on screen 562, the clerk operates the operator 5609 to close screen 562 and then operates the operation unit 56 to display the list screen 552 ( FIG. 20 ) or the details screen 553 ( FIG. 21 ), where they can check the information on the target mobile POS 3. The clerk then proceeds to the location where the customer is waiting and holds the code symbol displayed on the clerk ID over the image capture unit 38 of the target mobile POS 3 (step S55). This allows the reading unit 301 to acquire the clerk ID. The control unit 30 of the mobile POS 3 then transmits transaction information (step S56). This transaction information is used to display a code symbol on the display unit 35 of the mobile POS 3, which can be read by the payment machine 6. This code symbol links information identifying the transaction (e.g., a transaction ID) to the payment machine 6.

[0154] As described above, according to the process shown in FIG. 27, it is possible to sell merchandise that is past due at the time of payment, after obtaining confirmation from the customer that the merchandise is past due.

[0155] The above-described embodiments can be modified as needed by changing part of the configuration or function of each of the above-described devices. Also, each example of the above-described embodiments can be implemented individually or in combination as needed.

[0156] The programs executed by each device in the above-described embodiments are provided by being pre-installed in a ROM, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0157] Furthermore, the programs executed by each device in the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device in the above-described embodiments may be provided or distributed via a network such as the Internet.

[0158] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims.

[0159] Japanese Patent Application Laid-Open No. 2023-003118

Claims

1. A sales data processing system including a terminal device which registers product information through operations by customers while shopping around, the sales data processing system comprising an expiration date check unit which performs a check process to determine whether expiration date information included in the product information exceeds the current date and time at least once between the time when a first operation is performed on the terminal device to register product information and the time when a second operation is performed to start the process of paying for the registered product.

2. A sales data processing system according to claim 1, wherein the expiration check unit performs the check process when the first operation is performed.

3. A sales data processing system according to claim 1, wherein the expiration check unit performs the check process when the second operation is performed.

4. The sales data processing system of claim 2, wherein the expiration date checking unit further performs a check process to determine whether expiration date information contained in the registered product information exceeds the current date and time when the first operation is performed.

5. The sales data processing system of claim 1, further comprising a deadline processing unit which, when the first operation is performed, performs discount processing based on the difference between the deadline date and time indicated by the deadline information of the product registered by the first operation and the current date and time.

6. A program for causing a computer provided in a sales data processing system including a terminal device which performs a process of registering product information through operations by customers while shopping around to function as an expiration date checking unit which performs a check process to determine whether the expiration date information included in the product information exceeds the current date and time at least once between the time when a first operation is performed on the terminal device, which is an operation for registering product information, and the time when a second operation is performed, which is an operation for starting the process of paying for the registered product.

Images