Sales data processing device and program

Abstract

To utilize a plurality of media more suitably.SOLUTION: A sales data processing device used at a store where a plurality of media are available, comprises: reception means for receiving reading declaration operation of reading medium information of a medium from an operator; and read means for reading the medium information of the medium on the basis of a read operation of the operator, wherein the read means reads the medium information of one medium on the basis of the read operation after the reading declaration operation is received by the reception means, and then can read medium information on the basis of the read operation without receiving the reading declaration operation again with respect to other media having their medium information not read yet after the medium information of the one medium is read.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a sales data processing device and a program. [Background technology]

[0002] A system is known in which multiple point cards can be used in one transaction (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-307224 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for improvement in the operation when using multiple media.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique for more optimally utilizing a plurality of media. [Means for solving the problem]

[0006] One aspect for solving the above-mentioned problem is a sales data processing device used in a store where multiple media can be used, comprising a reception means for receiving a read declaration operation from an operator to read media information of a medium, and a reading means for reading the media information of a medium based on the operator's reading operation, wherein the reading means reads the media information of one medium based on the reading operation after receiving the read declaration operation by the reception means, and after reading the media information of one medium, is capable of reading media information of other media for which media information has not been read based on the reading operation without accepting another read declaration operation. [Brief description of the drawings]

[0007] [Figure 1] 2 is an example of the appearance of a registration and settlement device. [Diagram 2] 2 is a configuration example of a registration settlement device. [Diagram 3] 13 is a display example of a registration settlement device. [Figure 4] 13 is a display example of a registration settlement device. [Diagram 5] 13 is another display example of a registration settlement device. [Figure 6] 13 is another display example of a registration settlement device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] (Sales System) The registration and settlement device 10 of this embodiment is one of the devices constituting the sales system 1 (not shown). In addition to the registration and settlement device 10, the sales system 1 includes a transaction status management device 70 (not shown), a store controller 80 (not shown), and a headquarters server 90 (not shown). The sales system 1 can be introduced into various types of businesses (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.). The registration and settlement device 10, the transaction status management device 70, and the store controller 80 are installed in the store (product display area, accounting area, back yard, etc.). These are connected to be able to communicate via a LAN (which may be wired or wireless). The headquarters server 90 is installed outside the store (for example, a head office or a data center, etc.). The devices installed in the store and the devices installed outside the store can communicate (directly or via the store controller 80). The sales system 1 may be called a sales data processing system, a registration and settlement system, etc.

[0009] In the store (the store where the sales system 1 is installed), multiple point cards can be used. In addition, in the store, two or more point cards can be used simultaneously in one transaction. In other words, a customer can present two or more point cards in one transaction and earn points from each card. Details will be described later.

[0010] (Registration settlement device 10) The registration and settlement device 10 is a so-called self-service (full-self-service) device that registers products based on the customer's operation and settles the payment based on the customer's operation. In other words, the registration and settlement device 10 executes a registration process for registering products and a settlement process for settling the registered products, and both processes are basically executed based on the customer's own operation.

[0011] Although not shown in the figures, the registered settlement device 10 includes, for example, a CPU 101, a memory unit 102, a display unit 106 (touch panel), a scanner unit 107, a non-cash settlement unit (payment terminal) 108, a cash settlement unit (change machine) 109, a communication unit 110, a printing unit 111, an audio output unit 112, an imaging unit (camera) 113, a light emitting unit 114, a monitoring display unit 115, and a detection unit (human sensor) 120. These can communicate with each other via a bus. The audio output unit 112 (as well as the audio output units of other devices) may output directional audio toward the operator.

[0012] FIG. 1 is an example of the appearance of the registration settlement device 10. The registration settlement device 10 includes a main body 11, an upstream counter 12, and a downstream counter 13. The upstream counter 12 is a counter provided upstream of the main body 11 on the customer flow line. For example, products that have not yet been registered and shopping baskets containing products that have not yet been registered are placed on the upstream counter 12. The downstream counter 13 is a counter provided downstream of the main body 11 on the customer flow line. For example, products that have been registered and shopping bags (my bags, paid shopping bags, etc.) containing products that have been registered are placed on the downstream counter 13. The upstream counter 12 (as well as the downstream counter 13) may be a separate unit attached to the registration settlement device 10 (main body 11). A cash settlement unit 109 is provided at the lower part of the main body 11. The upper portion of the main body 11 is provided with a scanner unit 107, a printer unit 111, a display unit 106, a non-cash payment unit 108, an imaging unit 113, and a support pole unit 116. The support pole unit 116 is provided with, in order from the top, a light emitting unit 114, a monitoring display unit 115, and a detection unit 120.

[0013] For example, the display unit 106 displays various information (for example, various screens) to an operator (customer) and also accepts operations from the operator.

[0014] In addition, the scanner unit 107 optically reads various information. For example, the scanner unit 107 scans a barcode attached to a product and reads product identification information (JAN code). Also, for example, the scanner unit 107 scans a barcode attached to a point card and reads customer identification information (membership code).

[0015] Moreover, the non-cash payment unit 108 is a payment mechanism for non-cash payment (for example, credit card payment, electronic money payment, etc.). The non-cash payment unit 108 may be configured separately from the registration settlement apparatus 10, or may be configured integrally with the registration settlement apparatus 10. The non-cash payment unit 108 may include, for example, a reading unit, a communication unit (a communication unit that communicates with the registration settlement apparatus 10, a communication unit that communicates with an external server such as a credit server that executes credit card payment), an operation unit, and a display unit. The reading unit of the non-cash payment unit 108 may be capable of reading point cards in addition to cards related to non-cash payment (credit cards, electronic money cards).

[0016] (Transaction status management device 70) The transaction status management device 70 is a device that manages the devices installed in the store (monitoring and controlling the processing status, operation status, etc.). The transaction status management device 70 may also manage the operators of the devices installed in the store (monitoring and checking the customers, the contents of the customers' operations, etc.). The transaction status management device 70 comprises at least a CPU, a memory unit, a display unit (which may be configured as a touch panel), an operation unit (keyboard, mouse, etc.), and a communication unit. The transaction status management device 70 is used by store clerks.

[0017] (Store Controller 80) The store controller 80 is a server that mainly handles communication of information between devices installed inside the store and devices installed outside the store. The store controller 80 includes at least a CPU, a memory unit, and a communication unit.

[0018] (Points card) Although it has been explained that multiple point cards can be used at the store, in the following explanation, it is assumed that the following six types of point cards (Card A to Card F) can be used at the store.

[0019] Card A is a point card that is permitted to be used in conjunction (simultaneous use) with any of the other five types of cards. Card A is assumed to be a house card. Card B is a point card that is permitted to be used in conjunction with any of the other five types of cards. Card C is a point card that is permitted to be used in conjunction with any of the four types of cards other than card D. In other words, card C is a point card that is prohibited (restricted) from being used in conjunction with card D. Card D is a point card that is permitted to be used in conjunction with any of the four types of cards other than card C. In other words, card D is a point card that is prohibited from being used in conjunction with card C. Card F is a point card that is permitted to be used in conjunction with any of the other five types of cards.

[0020] In other words, at this store, among cards A to F, the combination of card C and card D is prohibited (the combination is not allowed), but the combination of other combinations is allowed (the combination is OK). For example, if a customer (customer a) is a point member for four cards A, B, C, and D (if he has cards A, B, C, and D), he can earn points for card A, card B, and card C in one transaction, or points for card A, card B, and card D in one transaction, but he cannot earn points for card C and card D in one transaction. In other words, since cards C and D can be used alternatively in one transaction, customer a can only earn points for either card C or card D.

[0021] For example, the registered settlement apparatus 10 may refer to a combination prohibition file (a file that stores information indicating that card C and card D are prohibited from being used together, a rule file related to the prohibition of combination) to determine combinations that are prohibited from being used together. Specifically, when the registered settlement apparatus 10 reads a certain card (card X), the registered settlement apparatus 10 may determine the presence or absence of a card that is prohibited from being used together with card X (if so, the type of card) based on the combination prohibition file. The combination prohibition file may be stored in a location that the registered settlement apparatus 10 can refer to (e.g., the memory unit 102 of its own apparatus or the memory unit of another apparatus) or in a location that another apparatus (e.g., the store controller 80, the headquarters server 90) can refer to (the memory unit of each apparatus or the memory unit of another apparatus).

[0022] For example, when the registered settlement device 10 reads card B, it determines that there is no card prohibited from being used in conjunction with card B based on the combination prohibition file. Also, for example, when the registered settlement device 10 reads card C, it determines that the card prohibited from being used in conjunction with card C based on the combination prohibition file is card D.

[0023] The registered settlement apparatus 10 may inquire of other apparatuses (e.g., the store controller 80, the headquarters server 90) about combinations that are prohibited from being used together. Specifically, when the registered settlement apparatus 10 reads a certain card (card X), it may inquire of the other apparatuses about the presence or absence of any cards that are prohibited from being used together with card X (if so, what is the type of card). When there is an inquiry from the registered settlement apparatus 10 about the presence or absence of any cards that are prohibited from being used together with card X (if so, what is the type of card), the other apparatus refers to the prohibited use file, determines whether or not there are any cards that are prohibited from being used together with card X (if so, what is the type of card), and responds with the determination result to the registered settlement apparatus 10.

[0024] For example, when the registered settlement device 10 reads card B, it inquires of the other devices as to whether or not there is a card prohibited from being used in conjunction with card B (if so, what type of card), and the other devices determine based on the prohibited use file that there is no card prohibited from being used in conjunction with card B, and respond to the registered settlement device 10 that there is no card prohibited from being used in conjunction with card B. Also, for example, when the registered settlement device 10 reads card C, it inquires of the other devices as to whether or not there is a card prohibited from being used in conjunction with card C (if so, what type of card), and the other devices determine based on the prohibited use file that the card prohibited from being used in conjunction with card C is card D, and respond to the registered settlement device 10 that the card prohibited from being used in conjunction with card C is card D.

[0025] In this example, the combination of two cards (card C and card D) is prohibited, but three or more cards may be prohibited. In other words, in this example, the combination of at most one card with a certain card X is prohibited, but the combination of two or more cards with a certain card X may be prohibited.

[0026] Also, it is assumed that the cards C and F of the same customer are linked to each other and managed. Specifically, it is assumed that the customer identification information of the card C and the customer identification information of the card F of the same customer are linked to each other and managed. For example, if a certain customer (customer b) is a point member of both cards C and F, and the customer identification information of the card C of customer b (membership code of customer b in card C) is "C000111" and the customer identification information of the card F of customer b (membership code of customer b in card F) is "F0582", the customer identification information "C000111" of the card C and the customer identification information "F0582" of the card F are linked and stored as linking information in a linking file (a file that holds linking information between the customer identification information of card C and the customer identification information of card F). The linking file may be stored in a location that can be referenced by the registered settlement device 10 or other devices (e.g., the store controller 80, the headquarters server 90).

[0027] Since cards C and F of the same customer are linked to each other and managed, for a customer who is a point member of both cards C and F, reading one of the cards makes it possible to identify the other card. For example, in the case of customer b who is a point member of both cards C and F, reading customer b's card C makes it possible to identify customer b's card F's customer identification information "F0582" from customer b's card C's customer identification information "C000111" by referring to the linking file, and reading customer b's card F makes it possible to identify customer b's card C's customer identification information "C000111" from customer b's card F's customer identification information "F0582" by referring to the linking file.

[0028] In this example, two cards (card C and card F) are linked and managed, but three or more cards may be linked and managed. In other words, although this example describes an example in which customer identification information of two cards of one customer is linked and stored as linking information in the linking file, customer identification information of three or more cards of one customer may be linked and stored as linking information.

[0029] For a customer who is a point member of both Card C and Card F, reading one card makes it possible to identify the other card, so for a customer who is a point member of both Card C and Card F, reading one card makes it possible to award points from the other card (i.e., reading one card makes it possible to award points from both cards).

[0030] The registered settlement device 10 omits reading of card F when it reads card C, and omits reading of card C when it reads card F. For example, the registered settlement device 10 may restrict the reading of card F (exclude it from being read) when it reads card C, and restrict the reading of card C when it reads card F.

[0031] For example, the registered settlement device 10 may refer to a reading omission file (a file that holds that card C and card F are a combination that can be omitted from reading, a rule file related to reading omission) to determine the combination that can be omitted from reading. Specifically, when the registered settlement device 10 reads a certain card (card X), the registered settlement device 10 may determine, based on the reading omission file, whether or not there is a card that can be omitted from reading by reading card X (if there is, what type of card). The reading omission file may be stored in a location that can be referenced by the registered settlement device 10 or a location that can be referenced by other devices (e.g., the store controller 80, the headquarters server 90).

[0032] For example, when the registered settlement device 10 reads card B, it determines, based on the reading omission file, that there is no card whose reading can be omitted by reading card B. Also, for example, when the registered settlement device 10 reads card C, it determines, based on the reading omission file, that the card whose reading can be omitted by reading card C is card F.

[0033] The registered settlement apparatus 10 may inquire of other apparatuses (e.g., the store controller 80, the headquarters server 90) about the combination of reading omission. Specifically, when the registered settlement apparatus 10 reads a certain card (card X), it may inquire of other apparatuses about the presence or absence of cards whose reading will be omitted by reading card X (if so, what type of card). When there is an inquiry from the registered settlement apparatus 10 about the presence or absence of cards whose reading will be omitted by reading card X (if so, what type of card), the other apparatus refers to the reading omission file, determines the presence or absence of cards whose reading will be omitted by reading card X (if so, what type of card), and responds with the determination result to the registered settlement apparatus 10.

[0034] For example, when the registered settlement device 10 reads card B, it inquires of the other devices whether or not there is a card whose reading can be omitted by reading card B (if so, what type of card), and the other devices determine based on the reading omission file that there is no card whose reading can be omitted by reading card B, and respond to the registered settlement device 10 that there is no card whose reading can be omitted by reading card B. Also, for example, when the registered settlement device 10 reads card C, it inquires of the other devices whether or not there is a card whose reading can be omitted by reading card C (if so, what type of card), and the other devices determine based on the reading omission file that the card whose reading can be omitted by reading card C is card F, and respond to the registered settlement device 10 that the card whose reading can be omitted by reading card C is card F.

[0035] In this example, the combination of reading omission is an example in which reading of two cards (card C, card F) is omitted, but reading of three or more cards may be omitted. In other words, in this example, an example in which reading of a certain card X results in omission of reading of at most one card, but reading of a certain card X may result in omission of reading of two or more cards.

[0036] As described above, when determining the combination of read-omissions, the read-omission file is referenced, but for customers who are point members of both card C and card F, it is necessary to award points on one card by reading the other card, so ultimately (when awarding points), the other card is identified by referring to the linking file.

[0037] When the registered settlement device 10 reads a customer's card C or card F, it refers to the linking file to determine whether the customer is a point member of both cards C and F, and if the customer is a point member of both cards C and F, it may specify the customer's card C or card F that has been omitted from reading. For example, when the registered settlement device 10 reads a customer's card C, it refers to the reading omission file itself (or queries another device that refers to the reading omission file) to omit reading the customer's card F, and refers to the linking file to determine whether the customer identification information of card F is stored in association with the customer identification information of the read card C. When the customer identification information of card F is stored in association with the customer identification information of the read card C, the registered settlement device 10 determines that the customer is a point member of both cards C and F, and specifies that the customer identification information of card F of the customer that has been omitted from reading is the customer identification information of card F that has been stored in association with the customer identification information of the read card C. Therefore, when the registered settlement device 10 reads card C (customer identification information "C000111") of customer b who is a point member of both card C and card F, it omits reading card F, determines that customer b is a point member of card F, and identifies customer identification information "F0582" of card F of customer b. When the registered settlement device 10 reads card C of a customer who is not a point member of card F, it omits reading card F of the customer, and determines that the customer is not a point member of card F. Similarly, when the registered settlement device 10 reads card F of a certain customer, it refers to the reading omission file itself (or queries another device that refers to the reading omission file), omits reading card C of the customer, and refers to the linking file to determine whether the customer identification information of card C is stored in association with the customer identification information of the read card F.When the customer identification information of card C is stored in association with the customer identification information of the read card F, the registered settlement device 10 determines that the customer is a point member of both card C and card F, and specifies that the customer identification information of card C of the customer for which reading was omitted is the customer identification information of card C stored in association with the customer identification information of the read card F. Therefore, when the registered settlement device 10 reads card F (customer identification information "F0582") of customer b who is a point member of both cards C and F, it omits reading card C, determines that customer b is a point member of card C, and specifies the customer identification information "C000111" of card C of customer b. Note that when card F of a customer who is not a point member of card C is read, the registered settlement device 10 omits reading card C of the customer, and determines that the customer is not a point member of card C.

[0038] Instead of the registered settlement device 10, another device (for example, the store controller 80, the headquarters server 90, a server that manages points for card C, or a server that manages points for card F) may refer to the linking file and determine whether the customer whose card C or card F was read by the registered settlement device 10 is a point member of both cards C and F, and if the customer is a point member of both cards C and F, may specify the card C or card F of the customer whose reading was omitted by the registered settlement device 10. For example, when the other device receives customer identification information of card C from the registered settlement device 10, it may refer to the linking file and determine whether the customer identification information of card F is stored in association with the customer identification information of the received card C. When the customer identification information of card F is stored in association with the customer identification information of the read card C, the other device may determine that the customer is a point member of both cards C and F, and may specify that the customer identification information of card F whose reading was omitted is the customer identification information of card F stored in association with the customer identification information of the read card C. Furthermore, when the other device receives customer identification information of card F from the registered settlement device 10, it refers to the linking file and determines whether customer identification information of card C is stored linked to the received customer identification information of card F. When customer identification information of card C is stored linked to the read customer identification information of card F, the other device may determine that the customer is a point member of both cards C and F, and may specify that the customer identification information of card C of the customer for which reading was omitted is the customer identification information of card C stored linked to the read customer identification information of card F.

[0039] (Display example / Configuration in which the point card is read immediately after the transaction begins) 2(A) to 4(B) are display examples (display examples on the display unit 106) of the registered settlement device 10 from the start of a transaction to the selection of a payment method. Specifically, Fig. 2(A) to Fig. 4(B) are display examples in a configuration in which a point card is read (registered) immediately after the start of a transaction (before product registration).

[0040] FIG. 2(A) is a transaction start screen (card presence / absence confirmation screen). Before the transaction starts (while waiting for a customer), the registered settlement device 10 displays the transaction start screen as shown in FIG. 2(A) as a standby screen. The transaction start screen in FIG. 2(A) displays a message MS10 instructing an operation according to the presence or absence of a membership card (point card). The transaction start screen in FIG. 2(A) also has a card to be read display area HR11 that displays the point card to be read. The card to be read display area HR11 in FIG. 2(A) displays icons of six types of point cards (cards A to F) that can be used at the store. The transaction start screen in FIG. 2(A) also has a card present button BT12 that is operated when a point card is held, and a card not present button BT13 that is operated when a point card is not held.

[0041] Before the start of a transaction, the registration settlement device 10 may display a transaction start screen (FIG. 5(A)) described below as a standby screen, and when the registration start button BT01 is operated on the transaction start screen (FIG. 5(A)), the registration settlement device 10 may display the card presence / absence confirmation screen of FIG. 2(A).

[0042] When the no card button BT13 is operated (touched) on the transaction start screen of FIG. 2(A), the registration and settlement device 10 displays an initial registration screen (a registration screen before registering one item of merchandise) as shown in FIG. 2(B). The initial registration screen of FIG. 2(B) is provided with a total amount display area HR50 that displays total information (total number of items purchased, total amount), and a product information display area HR51 that displays information on the registered merchandise. The initial registration screen (as well as the registration screen) of FIG. 2(B) is also provided with a checkout button BT52 that is operated when proceeding to checkout (payment) (i.e., when completing registration). Note that the checkout button BT52 is a button that becomes operable after the registration of one item of merchandise, and therefore on the initial registration screen, which is the registration screen before the registration of one item of merchandise, the checkout button BT52 is displayed in a display mode (grayed out, shown by a dashed line in the figure) indicating that it cannot be operated.

[0043] When the card present button BT12 is operated on the transaction start screen of FIG. 2(A), the registration and settlement device 10 displays a card reading screen as shown in FIG. 3(A). On the card reading screen of FIG. 3(A), a message MS14 instructing to register (read) a card (point card), a message MS15 regarding the use / registration of the card (specifically, a message that card C and card D cannot be used together, and that both cards C and F are registered by registering either one of them (the registration of the other is omitted)), and a reading guide image GA16 that guides the card registration method (reading method) are displayed. Also, on the card reading screen of FIG. 3(A), a card display area HR11 to be read is provided, and icons of six types of point cards are displayed, as on the transaction start screen of FIG. 2(A). Also, on the transaction start screen of FIG. 3(A), a card absent button BT13 to be operated when a point card is not held is arranged.

[0044] When card B is read on the card reading screen of FIG. 3(A) (when the scanner unit 107 reads the barcode of card B), the registered settlement device 10 displays a card reading screen as shown in FIG. 3(B). In addition to the card to be read display area HR11, the card reading screen of FIG. 3(B) is provided with a read card display area HR20 that displays the point card that has been read (or has not been read). The icons of card A, card C, card D, card E, and card F are displayed in the card to be read display area HR11 of FIG. 3(B). In other words, since the registered settlement device 10 has read the barcode of card B, the icon of card B is erased from the card to be read display area HR11. The icon of card B is displayed in the read card display area HR20 of FIG. 3(B). In other words, since the registered settlement device 10 has read the barcode of card B, the icon of card B is displayed in the read card display area HR20 of FIG.

[0045] When card C is read on the card reading screen of FIG. 3(B), the registered settlement device 10 displays a card reading screen as shown in FIG. 3(C). The icons of card A and card E are displayed in the card to be read display area HR11 of FIG. 3(C). That is, since the registered settlement device 10 has read the barcode of card C, the icon of card C, the icon of card D that is prohibited from being used in combination with card C, and the icon of card F whose reading is omitted due to the reading of card C are erased from the card to be read display area HR11. The icons of card B, card C, and card F are displayed in the read card display area HR20 of FIG. 3(B). That is, since the registered settlement device 10 has read the barcode of card C, the icon of card C and the icon of card F whose reading is omitted due to the reading of card C are additionally displayed in the read card display area HR20. In addition, in the read card display area HR20, the registered settlement device 10 displays the read point cards (card B, card C) and the point card (card F) that was not read in different display modes (card F is shown with a dashed line in the figure).

[0046] When the no card button BT13 is operated on the card reading screen in Fig. 3(C), the registration settlement device 10 displays an initial registration screen as shown in Fig. 3(D). The initial registration screen in Fig. 3(D) is provided with a card information display area HR60 that displays information about the read point card (or a point card that has not been read). "Card B, Card C, Card F" are displayed in the card information display area HR60 in Fig. 3(D).

[0047] If the customer (the customer who scanned card B and card C) is a point member of card F, the registered settlement device 10 displays "card B, card C, card F" in the card information display area HR60 as shown in FIG. 3(D), but if the customer is not a point member of card F, it displays "card B, card C" in the card information display area HR60. After reading card C, the registered settlement device 10 refers to the linking file and determines whether the customer is a point member of card F. After reading card C, the registered settlement device 10 may inquire of other devices (store controller 80, headquarters server 90, server that manages points for card C, server that manages points for card F) whether the customer is a point member of card F. The other devices may refer to the linking file and respond to the registered settlement device 10 whether the customer is a point member of card F.

[0048] Furthermore, the registered settlement device 10 may display the number of points held by each point card in the card information display area HR60 in addition to the type (name) of the point card. The registered settlement device 10 may inquire of another device (e.g., a server that manages points) about the number of points held by each point card displayed in the card information display area HR60. For example, the registered settlement device 10 may send inquiry information including the customer identification information of each point card to another device. The registered settlement device 10 may obtain the customer identification information of a point card that has not been read (card F in the case of FIG. 3(D)) by referring to the linking file or by inquiring of another device that can refer to the linking file.

[0049] When there are no more cards to be read (when all icons displayed in the card to be read display area HR11 are erased), the registration settlement device 10 may display the initial registration screen (i.e., transition to the next screen) without the operation of the no card button BT13. For example, when cards are read in the order of card A and card E from the card reading screen of Fig. 3(C), the initial registration screen of Fig. 3(D) may be displayed based on the reading of card E, which is the last card.

[0050] When a product (XX mayonnaise, XX nutritional drink) is registered from the initial registration screen of Fig. 3(D), the registration and settlement device 10 displays a registration screen as shown in Fig. 4(A). When the checkout button BT52 is operated on the registration screen of Fig. 4(A), the registration and settlement device 10 displays a payment method selection screen (payment type selection screen) as shown in Fig. 4(B). The number of points held on each point card may be displayed on the payment method selection screen of Fig. 4(B).

[0051] (Display example / Configuration in which the point card is read after product registration) Figures 5(A) to 6(C) are other display examples of the registered settlement device 10 from the start of a transaction to the selection of a payment method. Specifically, Figures 5(A) to 6(C) are display examples in a configuration in which a point card is read after product registration (before a payment method is selected). In other words, the registered settlement device 10 may read the point card before product registration as shown in Figures 2(A) to 4(B), or may read the point card after product registration (before a payment method is selected) as shown in Figures 5(A) to 6(C). The screen of Figure 6(D) will be described later.

[0052] Fig. 5(A) is a transaction start screen. Before starting a transaction, the registration settlement device 10 displays a transaction start screen as shown in Fig. 5(A) as a standby screen. On the transaction start screen of Fig. 5(A), a registration start button BT01 that is operated when starting a transaction is arranged.

[0053] When the registration start button BT01 is operated on the transaction start screen in Fig. 5(A), the registration settlement device 10 displays an initial registration screen (similar to the initial registration screen in Fig. 2(B)), and when a product (XX mayonnaise, XX nutritional drink) is registered from the initial registration screen, it displays a registration screen as shown in Fig. 5(B). The registration screen in Fig. 4(A) has a card information display area HR60, but it does not exist on the registration screen in Fig. 5(B).

[0054] When the billing button BT52 is operated on the registration screen of Fig. 5(B), the registration settlement device 10 displays a card presence confirmation screen as shown in Fig. 6(A). The card presence confirmation screen of Fig. 6(A) is provided with a payment amount display area HR30 and a back button BT31 (which, when operated, returns to the previous screen (the registration screen of Fig. 5(B))), but this does not exist on the transaction start screen (card presence confirmation screen) of Fig. 2(A).

[0055] When the no card button BT13 is operated on the card presence confirmation screen in Fig. 6(A), the registered settlement device 10 displays a payment method selection screen as shown in Fig. 6(B). The payment method selection screen in Fig. 6(B) is the same as the payment method selection screen in Fig. 4(B).

[0056] When the card present button BT12 is operated on the card presence confirmation screen in Fig. 6(A), the registered settlement device 10 displays a card reading screen (a card reading screen similar to the card reading screen in Fig. 3(A)), and when card B and card C are read on the card reading screen, it displays a card reading screen as shown in Fig. 6(C). The card reading screen in Fig. 6(C) is the same as the card reading screen in Fig. 3(C).

[0057] When the no card button BT13 is operated on the card reading screen of Fig. 6(C), the registered settlement device 10 displays a payment method selection screen as shown in Fig. 6(B). The number of points held on each point card may be displayed on the payment method selection screen displayed after the card is read (for example, the payment method selection screen of Fig. 6(B) transitioning from the card reading screen of Fig. 6(C)).

[0058] When there are no more cards to be read, the registered settlement device 10 may display the payment method selection screen (i.e., transition to the next screen) without the operation of the no card button BT13. For example, when cards are read in the order of card A → card E from the card reading screen of Fig. 6(C), the registered settlement device 10 may display the payment method selection screen of Fig. 6(B) based on the reading of card E, which is the last card.

[0059] The registration settlement device 10 may be capable of reading the point card before or after product registration. For example, when the checkout button BT52 on the registration screen in FIG. 4(A) is operated, the registration settlement device 10 may display a card presence / absence confirmation screen instead of a payment method selection screen.

[0060] The icon of the card remaining to be read (not corresponding to any of the following cards: cards read before product registration, cards prohibited from being used in conjunction with cards read before product registration, and cards whose reading was omitted due to the reading of another card before product registration) is displayed in the card to be read display area HR11 of the card presence / absence confirmation screen displayed after product registration (after operation of the checkout button BT52). For example, the icon of card A and the icon of card E are displayed in the card to be read display area HR11 of the card presence / absence confirmation screen transitioned to from the registration screen of Fig. 4(A). The same is true for the registered settlement device 20 (described later), the registered settlement device 30 (described later), the settlement device 50 (described later), and the settlement device 60 (described later).

[0061] (Configuration in which point cards are read during product registration) Although the configuration for reading the point card before product registration and the configuration for reading the point card after product registration have been described, the registration settlement device 10 may read the point card during product registration instead of or in addition to before or after product registration. For example, a card present button BT12 may be arranged on the registration screen (including the initial registration screen), and the registration settlement device 10 may display a card reading screen when the card present button BT12 on the registration screen (including the initial registration screen) is operated. If the point card can be read before and during product registration, the icon of the card remaining to be read (a card that does not fall under any of the following cards that have been read before product registration, cards that are prohibited from being used in combination with cards that have been read before product registration, and cards whose reading has been omitted due to the reading of other cards before product registration) is displayed in the card reading display area HR11 of the card reading screen displayed during product registration. The same applies to the registration settlement device 20 (described later) and the registration settlement device 30 (described later).

[0062] If the point card can be read both during and after product registration, the icon of the card remaining to be read (not including cards read during product registration, cards prohibited from being used in conjunction with cards read during product registration, or cards whose reading was omitted due to the reading of other cards during product registration) is displayed in the card display area HR11 of the card presence / absence confirmation screen displayed after product registration. The same applies to the registered settlement device 20 (described below) and the registered settlement device 30 (described below).

[0063] Furthermore, if point cards can be read before, during, and after product registration, the icon of the card remaining to be read (not including cards read before or during product registration, cards prohibited from being used in combination with cards read before or during product registration, or cards whose reading was omitted due to the reading of other cards before or during product registration) is displayed in the card display area HR11 of the card presence / absence confirmation screen displayed after product registration. The same applies to the registered settlement device 20 (described below) and the registered settlement device 30 (described below).

[0064] (Other devices) Devices other than the above-mentioned devices may be installed in the store. That is, the sales system 1 may include devices other than the above-mentioned devices. For example, instead of or in addition to the registration settlement device 10, a registration settlement device 20 (not shown, described later) may be installed. Also, instead of or in addition to the registration settlement device 10 or the registration settlement device 20 (not shown, described later), a registration settlement device 30 (not shown, described later) may be installed. Also, instead of or in addition to the above-mentioned devices, a registration device 40 (not shown, described later), a registration device 41 (not shown, described later), or a settlement device 50 (not shown, described later) may be installed. Also, instead of or in addition to the above-mentioned devices, a settlement device 60 (not shown, described later) may be installed. Also, a registration settlement device 100 (not shown) that executes registration processing and settlement processing based on the operation of a store clerk may be installed.

[0065] (Registration settlement device 20) The registration and settlement device 20 is a so-called self-service (semi-self-service) device that registers products based on the operation of a store clerk and settles the payment based on the operation of a customer. The registration and settlement device 20 has a display unit and a scanner unit on the store clerk side (one side of the housing) and a display unit, scanner unit, and settlement unit on the customer side (the other side of the housing).

[0066] Although not shown in the figures, the registration and settlement device 20 includes, for example, a CPU 201, a memory unit 202, a store clerk display unit 203, a store clerk scanner unit 204, an operation unit (one or more hard keys) 205, a customer display unit 206, a customer scanner unit 207, a non-cash payment unit 208, a cash payment unit 209, a communication unit 210, a printing unit 211, an audio output unit 212, and an imaging unit 213. The store clerk scanner unit 204 is mainly used by the store clerk to register products. The customer scanner unit 207 is mainly used by the customer to read point cards and the like.

[0067] The registration settlement device 20 may display a card presence / absence confirmation screen or a card reading screen, similar to the registration settlement device 10. For example, the registration settlement device 20 may display a card presence / absence confirmation screen as shown in FIG. 6(A) or a card reading screen as shown in FIG. 6(C) on the customer side display unit 206. That is, the registration settlement device 20 may display a card reading screen as shown in FIG. 6(C) before the selection of a payment method and read the point card. In addition, the registration settlement device 20 may display a card reading screen on the customer side and read the point card during product registration (during product registration by a clerk on the clerk side).

[0068] (Registration settlement device 30) The registration and settlement device 30 is a cash register that has multiple operating modes, for example, a normal mode (semi-self-service mode, in which, like the registration and settlement device 20, products are registered based on the operation of a store clerk and settlement is made based on the operation of a customer) and a full-self-service mode (in which, like the registration and settlement device 10, products are registered based on the operation of a customer and settlement is made based on the operation of the customer). In other words, when in the normal mode, the registration and settlement device 30 executes registration processing based on the operation of a store clerk and settlement processing based on the operation of a customer. When in the full-self-service mode, the registration and settlement device 30 executes both registration processing and settlement processing based on the operation of a customer. The registration and settlement device 30 has a display unit and a scanner unit on the store clerk side and a display unit, scanner unit and settlement unit on the customer side.

[0069] Although not shown in the figure, the registration and settlement device 30 includes, for example, a CPU 301, a memory unit 302, a store clerk display unit 303, a store clerk scanner unit 304, an operation unit 305, a customer display unit 306, a customer scanner unit 307, a non-cash payment unit 308, a cash payment unit 309, a communication unit 310, a printing unit 311, an audio output unit 312, an imaging unit 313, a light emitting unit 314, a monitoring display unit 315, and a detection unit 320. The store clerk scanner unit 304 is mainly used by the store clerk to register products in the normal mode. The customer scanner unit 307 is mainly used by the customer to read point cards and the like in the normal mode. The customer scanner unit 307 is mainly used by the customer to register products and read point cards and the like in the full self-service mode.

[0070] The registered settlement device 30 may display a card presence / absence confirmation screen or a card reading screen, similar to the registered settlement device 10. For example, when in the normal mode, the registered settlement device 30 may display a card presence / absence confirmation screen as shown in FIG. 6(A) or a card reading screen as shown in FIG. 6(C) on the customer side display unit 306. That is, when in the normal mode, the registered settlement device 30 may display a card reading screen as shown in FIG. 6(C) before selecting a payment method and read the point card. Also, when in the normal mode, the registered settlement device 30 may display a card reading screen on the customer side and read the point card during product registration (during product registration by a clerk on the clerk side), similar to the registered settlement device 20.

[0071] Furthermore, when the registration settlement device 30 is in the full self-service mode, it may display each screen as shown in Fig. 2(A) to Fig. 4(B) on the customer side display unit 306, similar to the registration settlement device 10, or may display each screen as shown in Fig. 5(A) to Fig. 6(C). That is, when the registration settlement device 30 is in the full self-service mode, it may display a card reading screen as shown in Fig. 3(A) to Fig. 3(C) before product registration and read the point card, or it may display a card reading screen as shown in Fig. 6(C) after product registration (before selecting a payment method) and read the point card. When the registration settlement device 30 is in the full self-service mode, it may display a card reading screen on the customer side and read the point card during product registration (during product registration by a customer on the customer side), similar to the registration settlement device 10.

[0072] (Registration device 40, settlement device 50) The registration device 40 is a device that registers products based on the operation of a store clerk. The settlement device 50 is a device that acquires registration information by the registration device 40 and settles the bill based on the operation of the customer. The registration device 40 and the settlement device 50 together constitute a semi-self-service system.

[0073] Although not shown in the figure, the registration device 40 includes, for example, a CPU 401, a memory unit 402, a store clerk display unit 403, a scanner unit 404, an operation unit 405, a customer display unit 406, a communication unit 410, a printing unit 411, and an audio output unit 412.

[0074] Although not shown in the figures, settlement device 50 includes, for example, a CPU 501, a memory unit 502, a display unit 506, a scanner unit 507, a non-cash payment unit 508, a cash payment unit 509, a communication unit 510, a printing unit 511, an audio output unit 512, an imaging unit 513, a light emitting unit 514, a monitoring display unit 515, and a detection unit 520. Scanner unit 507 is mainly used to read point cards and the like by customers.

[0075] The settlement device 50 may display a card presence / absence confirmation screen or a card reading screen, similar to the registered settlement device 10. For example, the settlement device 50 may display a card presence / absence confirmation screen as shown in Fig. 6(A) or a card reading screen as shown in Fig. 6(C) on the display unit 506. In other words, the settlement device 50 may display a card reading screen as shown in Fig. 6(C) and read the point card before the selection of a payment method.

[0076] (Registration device 41, settlement device 50) The registration device 41 is a device that registers products based on the customer's operation. As described above, the settlement device 50 is a device that acquires registration information from the registration device 40 and settles the bill based on the customer's operation, but it may also acquire registration information from the registration device 41 and settle the bill based on the customer's operation. The registration device 41 and the settlement device 50 constitute a full self-service system.

[0077] Although not shown in the figure, the registration device 41 includes, for example, a CPU 1401, a memory unit 1402, a display unit 1406, a scanner unit 1407, a communication unit 1410, a printing unit 1411, an audio output unit 1412, an imaging unit 1413, a light emitting unit 1414, a monitoring display unit 1415, and a detection unit 1420.

[0078] (Payment device 60) The settlement device 60 is a device that acquires registration information from a mobile registration terminal (smartphone, tablet terminal, etc., not shown) that registers products based on operations by customers at the product sales floor, and settles the payment based on the customer's operations. The mobile registration terminal and the settlement device 60 constitute a full-self system.

[0079] Although not shown in the figures, the settlement device 60 includes, for example, a CPU 601, a memory unit 602, a display unit 606, a scanner unit 607, a non-cash payment unit 608, a cash payment unit 609, a communication unit 610, a printing unit 611, an audio output unit 612, an imaging unit 613, a light emitting unit 614, a monitoring display unit 615, and a detection unit 620. The scanner unit 507 is mainly used to read point cards and the like by customers.

[0080] The settlement device 60 may display a card presence / absence confirmation screen or a card reading screen, similar to the registered settlement device 10. For example, the settlement device 60 may display a card presence / absence confirmation screen as shown in Fig. 6(A) or a card reading screen as shown in Fig. 6(C) on the display unit 606. In other words, the settlement device 60 may display a card reading screen as shown in Fig. 6(C) and read the point card before the selection of a payment method.

[0081] The above describes an embodiment, but according to the registered settlement device 10 of the above embodiment (the same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60), multiple media can be more suitably used in one transaction.

[0082] For example, in a method in which a point card to be read (a point card to be used) is specified and then the specified point card is read, if there are multiple point cards to be read, it is necessary to repeatedly specify the card and read the card, which is cumbersome. However, in the above embodiment, cards can be read one after another (Figures 3(A) to 3(C), Figures 6(A), 6(C)), making the operation simple (improved operability).

[0083] If there are many point cards to be read, there is a risk that after some of the cards have been read, confusion may occur as to which cards remain to be read. However, in the above embodiment, the display of the card to be read is updated (erased) each time a card is read (display area HR11 of the card to be read), so there is no confusion even if there are many point cards to be read.

[0084] If there are many point cards to be read, there is a risk that confusion will occur when some of the cards have been read and the user will not know which cards have been read. However, in the above embodiment, the display of the cards that have been read is updated (added) each time a card is read (read card display area HR20), so there is no confusion even if there are many point cards to be read.

[0085] (Variations, etc.) Although the embodiment has been described above, the device configuration, data configuration, processing flow, display and output aspects, etc. can be appropriately changed, for example, as shown in the following (1) to (11). In addition, the following (1) to (11) may be appropriately combined with each other.

[0086] (1) In the above embodiment, an example has been described in which point cards that are not to be read are erased from the card display area HR11 to be read (FIGS. 3(B), 3(C), and 6(C)), but they may be displayed in a manner indicating that they are not to be read (for example, grayed out) without being erased. For example, in the example shown in FIG. 3(B), the icon for card B may be displayed grayed out, and in the example shown in FIG. 3(C) (similar to the example shown in FIG. 6(C)), the icons for card B, card C, card D, and card F may be displayed grayed out.

[0087] That is, the registered settlement device 10 may erase the icon of the card that is not to be read, or may change the display mode of the icon of the card that is not to be read (for example, changing the display mode from a display mode indicating that the card is to be read to a display mode indicating that the card is not to be read). The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60. Note that one of the display modes indicating that the card is not to be read may be understood as not displaying the card (i.e. erasing the card).

[0088] (2) In the above embodiment, an example was described in which a read (or omitted reading) point card was displayed, but it is not necessary to display a read (or omitted reading) point card. In other words, although the card reading screens in Fig. 3(B), Fig. 3(C) and Fig. 6(C) are provided with a read card display area HR20, it is not necessary to provide the read card display area HR20.

[0089] This is also related to (1) and (2) above, but it may be possible to display in the display area HR11 of the card to be read that the card has been read (or reading omitted). For example, in the example shown in FIG. 3(B), the icon (grayed out icon) of card B may be marked with "read". Also, in the example shown in FIG. 3(C) (as well as the example shown in FIG. 6(C)), the icons (grayed out icons) of cards B and C may be marked with "read", the icon (grayed out icon) of card D may be marked with "cannot be used in combination", and the icon (grayed out icon) of card F may be marked with "read omitted".

[0090] (3) In the above embodiment, an example was described in which the presence or absence of a point card is confirmed on a screen separate from the screen for selecting a payment method as a configuration for reading a point card after product registration, but the presence or absence of a point card may be confirmed on the screen for selecting a payment method. For example, the card present button BT12 may be provided on the payment method selection screen (FIG. 6(B)), and when the card present button BT12 is operated, the card reading screen may be displayed (the payment method selection screen may be returned to by operating the card not present button BT13 on the card reading screen). The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0091] (4) In the above embodiment, an example was described in which an operation to declare card reading (operating the card present button BT12) was performed when starting card reading (before reading the first card), but the operation to declare card reading does not have to be performed.

[0092] For example, the registered settlement device 10 may display a transaction start screen (card reading screen) as shown in Fig. 6(D) as a standby screen instead of the transaction start screen (card presence confirmation screen) of Fig. 2(A). The registered settlement device 10 may display the transaction start screen (Fig. 5(A)) as a standby screen, and when the registration start button BT01 is operated on the transaction start screen (Fig. 5(A)), the card reading screen of Fig. 6(D) may be displayed. The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0093] On the card reading screen of Fig. 6(D), if the customer does not have a card to be read, the customer operates the no card button BT13, and if the customer has a card to be read, the customer simply has the card read without performing any special operation. When the no card button BT13 on the card reading screen of Fig. 6(D) is operated, the registration settlement device 10 displays an initial registration screen. When a card is read on the card reading screen of Fig. 6(D), the registration settlement device 10 changes the display of the card to be read display area HR11 and the card that has been read display area HR20, in the same way as the card reading screens of Figs. 3(A) to 3(C).

[0094] Also, during or after product registration, the card may be read without a declaration. For example, a message MS14 may be displayed on the registration screen or the payment method selection screen, and the card may be read without a declaration.

[0095] (5) In the above embodiment, it has been described that when card C is read, card D, which is prohibited from being used in combination with card C, is excluded from the reading targets (FIG. 3(B)→FIG. 3(C)), but card D may be readable even after card C is read, and when card D is read, the customer may select whether to use card C or card D. That is, in the above embodiment, when any card constituting a combination of cards prohibited from being used in combination is read, the other cards constituting the combination are excluded from the reading targets (the other cards are immediately rejected as excluded from the reading targets) in order to prevent a collision of prohibited combinations from occurring, but it is also possible to read the other cards without excluding them from the reading targets and then have the customer select one card to use from among the cards with which a collision of prohibited combinations is occurring (the card not selected by the customer may be rejected).

[0096] The registered settlement device 10 may allow the customer to select one of the two cards (card C, card D) involved in the collision when a collision prohibiting concurrent use occurs (for example, when card D is read while card C is being read), or may allow the customer to select one of the two cards involved in the collision when an operation to complete card reading is performed while a collision prohibiting concurrent use occurs (when the no card button BT13 is operated while both card C and card D have been read).

[0097] When a combination of cards prohibited from being used together has three cards (e.g., card G, card H, and card I), the registered settlement device 10 may allow the customer to select one card to be used from among the two cards in the collision (two of card G, card H, and card I) when the collision of prohibited use of cards occurs (when the second card is read). The registered settlement device 10 may allow the customer to select one card to be used from among the three cards in the collision (card G, card H, and card I) when all the collisions of prohibited use of cards occur (when the third card is read). In other words, when all the cards that make up a combination of cards prohibited from being used together are displayed as options, the registered settlement device 10 may allow the customer to select one card when all the cards are displayed as options. When an operation to complete card reading (operation of the no card button BT13) is performed in a state where a prohibited combination collision occurs, the registered settlement device 10 may allow the customer to select one card to be used from the two cards (two of card G, card H, and card I) or three cards (card G, card H, and card I) involved in the collision. The same applies when there are four or more cards in the combination of cards prohibited from being used together.

[0098] (6) In the above embodiment, an example was described in which an icon was erased in response to the reading of a card, but an icon may be displayed in response to the reading of a card. For example, in the case where there are six types of cards (cards A to F) as described above, the registered settlement device 10 may display no icons when none of the cards are read, and may display icons of the five types of cards (cards B, C, D, E, and F) together with a message such as "Do you have the following five types of cards?" when card A is read as the first card, and may display icons of the four types of cards (cards C, D, E, and F) together with a message such as "Do you have the following four types of cards?" when card B is read as the second card. For example, when card C is read as the first card, icons of the four types of cards (card A, card B, card D, card E) may be displayed along with a message such as "Do you have the following four types of cards? Please note that cards C and D cannot be used together. Also, customers who have card F can automatically earn a certain number of points on card F without having to read card F." If there are no more cards to be read after a card is read, the screen may transition to the next screen (for example, an initial registration screen or a payment method selection screen).

[0099] (7) In the above embodiment, an example was shown in which the barcode on the point card was read by holding it over a fixed scanner, but the barcode may also be read with a handheld scanner. The point card may also be a magnetic card or an IC card. That is, the card may be inserted into the card reading section to read customer identification information (membership code), or the card may be swiped in the card swipe section to read customer identification information, or the card may be touched to the card touch section to read customer identification information. The medium for point allocation is not limited to cards, and may also be a barcode or two-dimensional code displayed on a mobile terminal or the like. That is, a code displayed on an electronic device may also be read.

[0100] That is, the registered settlement device 10 acquires medium information (customer identification information) from a medium (card, device, etc.) so that points can be awarded to the customer, etc. The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0101] (8) In the above embodiment, an example of reading a point card has been described, but the object to be read may also be a coupon. The coupon may be a paper medium, or may be displayed on a mobile terminal or the like. In other words, the registered settlement device 10 may obtain medium information (information relating to a discount (or reduction)) from a medium (paper medium, device, etc.) so that a discount (or reduction) is applied to the customer. The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0102] The registered settlement device 10 may display icons corresponding to the coupons in the same manner as the point card. The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0103] In addition, coupons may not be used together or reading may be omitted. In addition, coupons may not be used together or reading may be omitted. The registered settlement device 10 may display icons of coupons that remain to be read, just like the point card. The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0104] For coupons with a usable period set, use outside the usable period (before or after the usable period) may be prohibited (for example, the coupon may not be accepted as an error).

[0105] (9) In the above embodiment, an example was described in which an icon corresponding to each card was displayed in the to-be-read card display area HR11, but information corresponding to each card (e.g., characters, symbols, images) may be displayed instead of icons. The same applies to the read card display area HR20.

[0106] Also, as long as the customer can recognize the read target and the read result (the medium that was actually read, or the medium whose reading was omitted due to the reading of another medium), the information does not have to be for each medium (such as an icon or letters corresponding to each card). For example, the read target and the read result may be notified collectively (notified in an integrated manner) using text, a list, audio, video (animation, etc.). For example, when card A is read, the registered settlement device 10 may display a message or output audio such as "Your card A has been read. If you have card B, card C, card D, card E, or card F, please allow us to read them," and when card C is subsequently read, the registered settlement device 10 may display a message or output audio such as "Your cards A and C have been read. If you have card B or card E, please allow us to read them."

[0107] (10) The registered settlement device 10 does not have to include either the non-cash settlement unit (payment terminal) 108 or the cash settlement unit (change machine) 109 (it is sufficient to include either one). The same applies to the registered settlement device 20, the registered settlement device 30, the settlement device 50, and the settlement device 60.

[0108] (11) Some or all of the functions (input / output, storage, processing (including judgment)) of each device (registered settlement device 10, registered settlement device 20, registered settlement device 30, settlement device 50, settlement device 60, transaction status management device 70, store controller 80, etc.) may be realized in a device other than the device described as the entity that executes the function. Each device may function as a so-called thin client specialized for input / output interfaces, etc. For example, a cloud server may execute a program for controlling the operation of each device, and each device may display a screen (such as the screens shown in Figures 2 to 6) using a browsing function.

[0109] <Summary of the embodiment> [Technical field] The present invention relates to a sales data processing device and a program. [Background technology] A system is known in which multiple point cards can be used in one transaction (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2001-307224 A [Summary of the Invention] [Problem to be solved by the invention] However, there is room for improvement in the operation when using multiple media. The present invention has been made in consideration of such circumstances, and has an object to provide a technology for more suitably using multiple media. [Means for solving the problem]

[0110] (1) One aspect for solving the above-mentioned problems is a sales data processing device (e.g., registered settlement device 10, registered settlement device 20, registered settlement device 30, settlement device 50, settlement device 60, etc.) used in a store where multiple media can be used, and is equipped with a reception means for receiving a read-present declaration operation (e.g., operation of the card present button BT12) from an operator to read media information (e.g., customer identification information, discount (discount) information, etc.) of a medium (e.g., a card for points, coupons, etc., an electronic device displaying such information, etc.), and a reading means (e.g., a scanner unit) for reading the media information of a medium based on the operator's reading operation, wherein the reading means reads the media information of one medium based on the reading operation after receiving the read-present declaration operation by the reception means, and after reading the media information of one medium, is capable of reading media information of other media for which media information has not been read based on the reading operation without receiving another read-present declaration operation. According to the sales data processing device of (1), it is possible to more suitably use a plurality of media in one transaction. For example, the operation when handling a plurality of media in one transaction becomes simpler (operability is improved).

[0111] (2) A sales data processing device as described in (1), characterized in that it is provided with a display means for displaying corresponding information (e.g., icons, characters, etc.) corresponding to each of the available media, and a display mode changing means for changing the display mode of the corresponding information corresponding to the medium from which the medium information has been read by the reading means (e.g., graying out or not displaying the information). According to the sales data processing device of (2), a plurality of media can be used more suitably in one transaction. For example, the read media can be easily recognized.

[0112] (3) A sales data processing device as described in (1) or (2) is characterized in that, when the media information of one of the media constituting the combination whose combined use is restricted exists (for example, the combination of card C and card D), the display mode change means changes the display mode of the corresponding information corresponding to the one or more other media constituting the combination in addition to the corresponding information corresponding to the one or more other media constituting the combination when the media information of the one or more media constituting the combination whose combined use is restricted is read (for example, see Figure 3(B) → Figure 3(C)). According to the sales data processing device of (3), it is possible to more appropriately use a plurality of media in one transaction. For example, it is possible to easily recognize media for which concurrent use is restricted.

[0113] (4) A sales data processing device as described in any of (1) to (3), characterized in that, among the multiple media, there are combinations in which the respective media information is linked (for example, the combination of card C and card F), and when the media information of one of the media that constitutes the combination to which the media information is linked is read, the display mode change means changes the display mode of the corresponding information corresponding to the one or more other media that constitute the combination in addition to the corresponding information corresponding to the one or more media that constitute the combination (for example, see Figure 3 (B) → Figure 3 (C)). According to the sales data processing device of (4), it is possible to more appropriately use a plurality of media in one transaction. For example, it is possible to easily recognize linked media.

[0114] (5) The sales data processing device described in any of (1) to (4) is characterized in that the reception means is capable of receiving from an operator a no-read declaration operation (e.g., operation of the no-card button BT13) to indicate that the media information of the medium will not be read, and the reading means reads the medium information on a reading screen (e.g., the card reading screen shown in Figure 3 (A), Figure 6 (C), Figure 6 (D), etc.) that guides the reading operation, and when the reception means receives the no-read declaration operation or when the display mode change means changes the display mode of all corresponding information (i.e., when there are no media to be read), the reading screen transitions to another screen (e.g., an initial registration screen, a payment method selection screen). According to the sales data processing device of (5), a plurality of media can be used more suitably in one transaction. Operation becomes simpler.

[0115] (6) A sales data processing device according to any of (1) to (5), characterized in that it is provided with a display means for distinguishing and displaying (for example, displaying in different display modes, e.g., displaying one in the card to be read display area HR11 in FIG. 3(B) and not displaying the other in the card to be read display area HR20 in FIG. 3(B)) corresponding information corresponding to a medium whose medium information has not been read by the reading means (for example, the icon of card A in FIG. 3(B)) from information corresponding to a medium whose medium information has been read by the reading means (for example, displaying in different display modes, e.g., displaying one in the card to be read display area HR11 in FIG. 3(B) and not displaying the other. Also, for example, displaying in different display positions, e.g., displaying one in the card to be read display area HR11 in FIG. 3(B) and displaying the other in the card that has been read display area HR20, etc.). According to the sales data processing device of (6), a plurality of media can be used more suitably in one transaction. For example, the read media can be easily recognized.

[0116] (7) One aspect for solving the above-mentioned problem is a program (e.g., a program operating on a sales data processing device, a program operating on a cloud server) that causes a computer to function as a sales data processing device used in a store where multiple media can be used, and causes the computer to function as a reception means that receives a read declaration operation from an operator to read media information of a medium, and a reading means that reads the media information of a medium based on the operator's reading operation, wherein the reading means reads the media information of one medium based on the reading operation after receiving the read declaration operation by the reception means, and after reading the media information of one medium, is capable of reading media information of other media for which media information has not been read based on the reading operation without accepting another read declaration operation. Program (7) can achieve the same effect as program (1).

[0117] In addition, a program for implementing the functions of each of the above-described devices (registered settlement devices 10, 20, 30, registered devices 40, 41, settlement devices 50, 60, transaction status management device 70, store controller 80, headquarters server 90, etc.) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing of each of the above devices. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including the Internet, a WAN, a LAN, a dedicated line, and other communication lines. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. In addition, the recording medium also includes a recording medium provided inside or outside and accessible from a distribution server to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network. The above program may also be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0118] 1...Sales system, 10...Registration and settlement device, 20...Registration and settlement device, 30...Registration and settlement device, 40...Registration device, 41...Registration device, 50...Settlement device, 60...Settlement device, 70...Transaction status management device, 80...Store controller, 90...Head office server

Claims

1. A sales data processing device for use in a store where multiple media are available, a reception means for receiving a read declaration operation from an operator to read medium information of the medium; a reading means for reading medium information of the medium based on a reading operation by an operator; Equipped with The reading means includes: A sales data processing device characterized in that after the reading declaration operation is accepted by the accepting means, media information of one medium is read based on the reading operation, and after the media information of one medium has been read, media information of other media for which media information has not been read can be read based on the reading operation without accepting the reading declaration operation again.

2. a display means for displaying corresponding information corresponding to each of the available media; a display mode changing means for changing a display mode of corresponding information corresponding to the medium from which medium information is read by the reading means; 2. The sales data processing device according to claim 1, further comprising:

3. There are some combinations of media that are restricted from being used together. The display mode changing means is A sales data processing device as described in claim 2, characterized in that when medium information of one medium that constitutes a combination whose use is restricted is read, in addition to the corresponding information corresponding to that medium, the display mode of the corresponding information corresponding to each of the other one or more media that constitute the combination is changed.

4. Among multiple media, there are combinations in which the media information is linked to each other, The display mode changing means is A sales data processing device as described in claim 2, characterized in that when medium information of one medium that constitutes a combination to which the medium information is linked is read, in addition to the corresponding information corresponding to that medium, the display mode of the corresponding information corresponding to each of the other one or more media that constitute the combination is changed.

5. The receiving means is A non-reading declaration operation to the effect that the medium information of the medium is not to be read can be accepted from an operator, The reading means includes: reading medium information on a reading screen that guides the reading operation; A sales data processing device as described in claim 3 or claim 4, characterized in that when the reception means receives the no-reading declaration operation or when the display mode change means changes the display mode of all corresponding information, the reading screen is transitioned to another screen.

6. a display means for displaying, in a distinguishable manner, correspondence information corresponding to a medium whose medium information has not been read by said reading means and correspondence information corresponding to a medium whose medium information has been read by said reading means.

2. The sales data processing device according to claim 1, further comprising:

7. A program for causing a computer to function as a sales data processing device used in a store where multiple media are available, comprising: The computer, a reception means for receiving a read declaration operation for reading medium information of the medium from an operator; A reading means for reading medium information of a medium based on a reading operation of an operator. Functioning as a The reading means includes: The program is capable of reading media information of one medium based on the reading operation after the receiving means receives the read-presence declaration operation, and after reading the media information of the one medium, reading media information of other media whose media information has not been read based on the reading operation without receiving the read-presence declaration operation again.

Images