JP2021089572A - Product sales data processing system, product sales data processing method, and program - Google Patents

Abstract

To provide a product sales data processing system that efficiently registers a product.SOLUTION: A product sales data processing system includes storage means for storing registered product information in a predetermined storage destination assigned to each mobile terminal. Each of a plurality of mobile terminals includes reading means and transmission means. The reading means reads the product information. The transmission means transmits the product information read by the reading means to the predetermined storage destination. One of the plurality of mobile terminals includes sharing means. The sharing means shares a storage destination assigned to the one mobile terminal with another mobile terminal.SELECTED DRAWING: Figure 12

Description

The present invention relates to a product sales data processing system, a product sales data processing method, and a program.

In recent years, so-called self-checkout, in which customers register products and make payments, has become widespread. For example, there is known a self-checkout that uses a mobile terminal owned by a customer to register and settle products (see, for example, Patent Document 1). Specifically, for example, the barcode attached to the product is read using a mobile terminal owned by the customer, and the read information is transmitted to the server to register the product, and the registered content is dealt with at the time of payment. There is known a self-payment method in which a barcode is displayed on a mobile terminal and read by a scanner in a store to perform payment.

Japanese Unexamined Patent Publication No. 2016-21903

However, in the conventional technology, when shopping with multiple people in a family or group, each person takes out the product from the product shelf, but each person scans the barcode of the product with one mobile terminal, so that the product can be efficiently used. There was a problem that registration could not be done.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique capable of efficiently registering a product.

In order to solve the above-mentioned problems, the product sales data processing system according to one aspect of the present invention sells products provided with a storage means for storing registered product information in a predetermined storage destination assigned to each mobile terminal. Each of the plurality of mobile terminals of the data processing system includes a reading means for reading the product information and a transmitting means for transmitting the product information read by the reading means to the predetermined storage destination. One of the mobile terminals is a product sales data processing system including a sharing means for sharing a storage destination assigned to the one mobile terminal with another mobile terminal.

It is explanatory drawing which shows the network configuration of the shopping system 1 which concerns on embodiment. It is explanatory drawing which shows an example of the appearance of a POS terminal 40. It is explanatory drawing which shows an example of the hardware composition of the POS terminal 40. It is explanatory drawing which shows an example of the hardware composition of the mobile terminal 30. It is explanatory drawing which shows an example of various information for each mobile terminal 30 managed by a transaction management apparatus 20. It is a sequence diagram which shows the flow of the process at the time of registering and paying a product for each mobile terminal 30 in a shopping system 1. It is a sequence diagram which shows the process flow at the time of performing registration and settlement in a parent-child interlocking mode in a shopping system 1. It is explanatory drawing which shows an example of the cart information 800 in a parent-child interlocking mode. It is a flowchart which shows an example of the processing about the parent-child interlocking mode performed by the master mobile terminal 30a. It is a flowchart which shows an example of the process about the parent-child interlocking mode performed by a slave mobile terminal 30b. It is a flowchart which shows an example of the processing about the parent-child interlocking mode performed by the transaction management apparatus 20. It is explanatory drawing which shows an example of the screen of the mobile terminal 30 at the time of group registration. It is explanatory drawing which shows an example of the screen during shopping displayed on the mobile terminal 30. It is explanatory drawing which shows an example of the notification screen during shopping displayed on the mobile terminal 30. It is explanatory drawing which shows an example of the notification screen which is displayed on the mobile terminal 30 when the upper limit amount is reached. It is explanatory drawing which shows an example of the screen at the time of performing group registration displayed on the mobile terminal 30 which concerns on modification 2 of embodiment. It is explanatory drawing which shows an example of the display screen at the time of settlement which concerns on modification 8. It is explanatory drawing which shows an example of the screen at the time of settlement displayed for each registrant.

(Embodiment)
(Network configuration of shopping system 1)
FIG. 1 is an explanatory diagram showing a network configuration of the shopping system 1 according to the embodiment. The shopping system 1 is an example of a product sales data processing system. In addition, in this specification, "customer", "customer", and "user" are synonymous unless otherwise specified.

In FIG. 1, the shopping system 1 includes a management device (store computer, store controller) 10, a transaction management device 20, a mobile terminal 30, and a POS (Point Of Sales) terminal 40.

The management device 10 is a computer device that manages the POS terminal 40. The management device 10 stores, for example, a product master or the like. The product master is a file that stores product information such as product identification information (for example, JAN code), product name, and selling price of each product.

The transaction management device 20 is a computer device (for example, a server device) including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like. The transaction management device 20 manages various types of information such as information about customers, information about stores, and information about products for each store. The information managed (generated and stored) by the transaction management device 20 will be described later with reference to FIGS. 5 and 8.

The mobile terminal 30 is a portable communication device provided with a display screen of a smartphone, a tablet device, a mobile phone, or the like, and is operated by a customer (a shopper who is a member of the store, etc.). The mobile terminal 30 includes a communication unit, an imaging unit (camera), a touch panel, and the like. The mobile terminal 30 scans the barcode attached to the product, reads the product code, and accepts the registration of the product. That is, the mobile terminal 30 has a recognition function for recognizing a barcode attached to a product.

The recognition function provided in the mobile terminal 30 may be any as long as it can read the product code attached to the product, and the product may not be identified from the read product code. That is, when the mobile terminal 30 has a barcode as an object in the captured image (image acquired as a through image) captured by the imaging function, the mobile terminal 30 may be able to read the product code from the barcode. ..

In addition, the mobile terminal 30 captures a product (for example, a peripheral portion with a barcode) and generates an captured image (image data). For example, the mobile terminal 30 generates an captured image by releasing the shutter at its own discretion. However, the mobile terminal 30 may generate a captured image by releasing the shutter according to the operation of the customer who is the operator.

Further, the mobile terminal 30 may be provided with an image recognition technique. Specifically, the mobile terminal 30 may be provided with an image recognition technique for extracting feature points from an image (through image, captured image) and recognizing an imaging target (object or the like). For example, the mobile terminal 30 may specify (estimate) the imaged product by using the image recognition technology. By using such an image recognition technique, the mobile terminal 30 can also identify fresh foods such as vegetables and fruits to which a barcode is not attached, for example.

In addition, application software (hereinafter, may be referred to as "this application") for registering and paying for products related to the shopping system 1 is installed in the mobile terminal 30. The mobile terminal 30 can read the barcode attached to the product by activating this application and transmit the read information to the transaction management device 20 to register the product corresponding to the barcode. It is possible. In addition, the mobile terminal 30 displays a code (for example, a two-dimensional code: QR code (registered trademark)) corresponding to the registered product when making a payment. When the two-dimensional code is read by the POS terminal 40, the POS terminal 40 can perform the settlement.

Further, although the mobile terminal 30 is owned by the customer, it may be a loaned item lent to the customer by the store. The number of mobile terminals 30 (the number in operation) changes according to the number of visitors. In FIG. 1, two mobile terminals 30 are illustrated, but in reality, the number may be tens, hundreds, or more.

The POS terminal 40 is a computer device capable of executing a settlement process (also referred to as an accounting process or a settlement process) for performing a settlement (settlement) of a product registered in the mobile terminal 30. However, in the present embodiment, the POS terminal 40 can execute a registration process for registering the purchased product in addition to the settlement process. The POS terminal 40, for example, is set to the accounting-only mode described later to settle the products registered in the mobile terminal 30. Although a plurality of POS terminals 40 are illustrated in FIG. 1, the number of POS terminals 40 may be one.

The management device 10, the transaction management device 20, the mobile terminal 30, and the POS terminal 40 are connected to each other so as to be able to communicate with each other via a network.

(Appearance of POS terminal 40)
FIG. 2 is an explanatory diagram showing an example of the appearance of the POS terminal 40. FIG. 2A is a perspective view of the POS terminal 40 as viewed from the customer side. FIG. 2B is a perspective view of the POS terminal 40 as viewed from the store clerk side. The POS terminal 40 may be of a type that is placed on a counter or a desk.

As shown in FIG. 2, the POS terminal 40 includes, for example, a customer side display unit 201, a customer side scanner unit 202, a card payment unit 203, an automatic change ticket machine 204, an audio output unit 205, and a printing unit. It includes 206, a store clerk side display unit 207, a key operation unit 208, and a store clerk side scanner unit 209. Since the POS terminal 40 only needs to have a function of performing settlement, it is not necessary to include the store clerk side display unit 207, the key operation unit 208, and the store clerk side scanner unit 209. Further, although not shown, the POS terminal 40 may include a barber's pole that lights in a predetermined lighting mode. The barber's pole is lit in any one of a plurality of lighting modes to call a store clerk or notify the usage status.

The customer side display unit 201 is a display for customers. The customer side display unit 201 is, for example, a touch panel. The customer side display unit 201 displays various information and receives various inputs from the customer. For example, a screen for accepting payment methods at the time of payment and a screen for guiding operation procedures are displayed, and various inputs are received from customers. The customer-side display unit 201 may display a preset key, which is a button for selecting a product, and accept an operation (press) of the preset key.

The customer side scanner unit 202 is a customer scanner unit. The customer side scanner unit 202 optically reads various kinds of information. For example, the customer-side scanner unit 202 optically reads the two-dimensional code displayed on the mobile terminal 30 when the settlement is performed. In the present embodiment, the customer-side scanner unit 202 can also optically read a code (bar code, two-dimensional code, etc.) attached to the product. In addition, the customer-side scanner unit 202 can also read, for example, a code (bar code, two-dimensional code, etc.) printed on various cards (for example, a membership card, a point card, etc.). ..

The card payment unit 203 makes a payment using various cards. The various cards referred to here are, for example, prepaid cards such as credit cards and transportation cards, point cards, and the like. Further, the various cards may be a contact type card (IC card, magnetic card) or a non-contact type card (IC card).

The card settlement unit 203 includes, for example, a card reading unit, a display unit, and an operation unit. The card reader reads information on various cards. The card reader magnetically reads the card information if it is a magnetic card, and electrically reads the card information if it is an IC card.

The display unit of the card payment unit 203 displays various information. For example, when a credit card is used, the display unit displays the payment amount and the masked PIN. In addition, the operation unit of the card payment unit 203 accepts various operations from customers or staff of stores and the like. For example, when a credit card is used, the operation unit accepts a switching operation for using the credit card from the staff and an input of a personal identification number from the customer.

The automatic change ticket machine 204 is a cash settlement unit that makes payments in cash. The automatic change bill machine 204 has a bill and coin slot and a bill and coin outlet. Each of the input port and the discharge port has a sensor for detecting bills and coins, and is arranged so as to face the customer side. The slot accepts cash from customers. In addition, the discharge port discharges change (banknotes and coins). The automatic change fishing ticket machine 204 calculates the total amount of cash inserted into the slot, calculates the change amount which is the difference between the total amount and the purchase amount, and discharges the change or the fishing tag from the slot.

The audio output unit 205 is a speaker that outputs audio. The voice output unit 205 outputs, for example, voice guidance and the like. The voice guidance is, for example, guidance for supporting the registration of products to customers and guidance for supporting payment.

The printing unit 206 is a printer device that issues various media such as receipts. The printing unit 206 has an issuing port for issuing a receipt. For example, the printing unit 206 is rotatable in parallel in the horizontal direction, and the direction of the issuing port can be changed from the store clerk side to the customer side and from the customer side to the store clerk side. The printing unit 206 may be manually rotated or may be rotated by the driving force of the motor. Further, in the case of a configuration in which the printing unit 206 is rotated by the driving force of the motor, the printing unit 206 may be rotated according to the operation mode of the POS terminal 40 described later.

The store clerk side display unit 207 is a display for the store clerk. The store clerk side display unit 207 is, for example, a touch panel. The store clerk side display unit 207 displays various information and accepts various inputs from the store clerk. For example, the store clerk side display unit 207 displays a preset key which is a button for selecting a product, and accepts an operation (pressing) of the preset key.

The key operation unit 208 is a hardware key and receives various inputs from the store clerk. For example, the key operation unit 208 has a key corresponding to a product and a key corresponding to a quantity, and receives a selection of a product and a selection of a quantity from a clerk.

The clerk side scanner unit 209 is a clerk's scanner unit. The clerk side scanner unit 209 optically reads various kinds of information. For example, the clerk side scanner unit 209 reads the code. The code is a bar code, a two-dimensional code, or the like. Codes include codes attached to products, codes attached to store clerk name tags, and codes printed on various cards (for example, membership cards, point cards, etc.).

(Hardware configuration of POS terminal 40)
Next, the hardware configuration of the POS terminal 40 will be described. FIG. 3 is an explanatory diagram showing an example of the hardware configuration of the POS terminal 40. In the following, the contents described in FIG. 2 will be omitted as appropriate. In FIG. 3, the POS terminal 40 includes a CPU 301, a ROM 302, a RAM 303, a hard disk 304, a communication unit 305, a customer side display unit 201, a customer side scanner unit 202, a card payment unit 203, and automatic change fishing. It includes a bill machine 204, an audio output unit 205, a printing unit 206, a store clerk side display unit 207, a key operation unit 208, and a store clerk side scanner unit 209. These can communicate with each other via the bus.

The CPU 301 is a central processing unit, and controls the operation of the POS terminal 40 by reading and executing a program (for example, a product sales data processing program) stored in the ROM 302.
The ROM 302 is a read-only memory, and stores various information used by the CPU 301 including a program.

The RAM 303 is a read / write memory and stores various information. For example, the RAM 303 includes registration information (registration data) generated in the registration process for registering products, settlement information (settlement data) generated in the settlement process for settlement (settlement) of purchased products, and external (for example, a receipt computer). Memorize the information obtained from.

The hard disk 304 stores various information. The hard disk 304 may store, for example, a program executed by the CPU 301 instead of the ROM 302. Further, the hard disk 304 may store information generated in various processes or information acquired from the outside instead of the RAM 303.

(About the operation mode of the POS terminal 40)
Next, the operation mode of the POS terminal 40 will be described. The POS terminal 40 operates in one of a plurality of operation modes. The plurality of modes include, for example, a normal mode (face-to-face self-mode), an accounting-only mode, and a full self-mode. These operation modes are operation modes related to registration processing and settlement processing during normal business. In the present embodiment, the POS terminal 40 is set to the accounting-only mode.

(About normal mode)
The normal mode (face-to-face self-mode) is an operation mode in which the product registration on the clerk side is enabled and the product registration on the customer side is invalidated. Specifically, in the normal mode, the product registration using the store clerk side display unit 207, the key operation unit 208, and the store clerk side scanner unit 209 is enabled, and the customer side display unit 201 and the customer side scanner unit 202 are used. This mode disables product registration. As a result, in the normal mode, it is possible for the store clerk to execute the registration process without executing the registration process on the customer side.

In addition, the normal mode is an operation mode in which the insertion of money is enabled. Therefore, in the normal mode, it is possible to accept the input of money even when the product registration process is being performed. In the normal mode, the settlement process is performed by inserting money into the automatic change ticket machine 204 and reading the card by the card settlement unit 203. The settlement process is performed after the registration process on the clerk side is executed.

Further, in the normal mode, when the registration process is completed, the POS terminal 40 can transmit the registration information of the registered product to the other POS terminal 40 (the POS terminal 40 in the accounting-only mode).

(About accounting mode)
The accounting-only mode is an operation mode in which the product registration on the clerk side and the product registration on the customer side are invalidated and the settlement is enabled. Specifically, in the accounting-only mode, the product is registered using the store clerk side display unit 207, the key operation unit 208, and the store clerk side scanner unit 209, and the product using the customer side display unit 201 and the customer side scanner unit 202. It is a mode that invalidates the registration of. As a result, in the accounting-only mode, it is possible to prevent the clerk side and the customer side from executing the registration process. Further, in the accounting-only mode, the customer-side scanner unit 202 can read the two-dimensional code for settlement displayed on the mobile terminal 30 at the time of settlement.

In the accounting-only mode, registration information is received from the transaction management device 20 based on the two-dimensional code read from the mobile terminal 30, and the settlement process is executed using the registration information. In the accounting-only mode, the settlement process is performed by inserting money into the automatic change ticket machine 204, reading the card by the card settlement unit 203, and the like.

(About full self mode)
The full self mode is an operation mode in which product registration on the customer side is enabled. Specifically, the full self mode is a mode in which product registration using the customer side display unit 201 and the customer side scanner unit 202 is enabled. As a result, in the full self mode, the registration process can be performed on the customer side.

Further, in the full self mode, the product registration on the clerk side may be valid. Specifically, in the full self mode, product registration using the clerk side scanner unit 209, the clerk side display unit 207, and the key operation unit 208 may be enabled. As a result, in the full self mode, the registration process can be performed on the store clerk side and the customer side. In the full self mode, the registration of the product on the clerk side may be enabled or disabled by the operation of the clerk.

Further, in the full self mode, it is possible to accept the input of money even when the product registration process is being performed. In the full self mode, the settlement process is performed by inserting money into the automatic change ticket machine 204 and reading the card by the card settlement unit 203. The settlement process is performed after the registration process on the customer side or the clerk side is executed.

(About switching each operation mode)
Next, switching of the operation mode of the POS terminal 40 will be described. The operation mode is switched, for example, in response to an explicit mode switching operation for switching the operation mode by the clerk or a reading operation of the clerk code. Further, the operation mode may be switched, for example, according to a time condition. The temporal condition is, for example, that a predetermined time has elapsed since the last operation, or that the switching time is set according to a preset schedule. In addition, the operation mode may be switched in response to a mode switching instruction from another device (another POS terminal 40, a management device 10, a specific mobile terminal owned by a clerk, etc.). The operation mode is switched by a clerk.

In addition to the above-mentioned operation modes, the plurality of operation modes include an aggregation mode, a maintenance mode, a training mode, and the like. The aggregation mode is a mode in which sales, sales, etc. are aggregated and inquired. The maintenance mode is a mode in which a store clerk, a maintenance clerk, or the like performs setting work or maintenance work. The training mode is a mode in which a new clerk trains on the handling of the POS terminal 40.

(Hardware configuration of mobile terminal 30)
FIG. 4 is an explanatory diagram showing an example of the hardware configuration of the mobile terminal 30. In FIG. 4, the mobile terminal 30 includes a CPU 401, a ROM 402, a RAM 403, a memory 404, a communication I / F (interface) 405, an operation unit 406, a camera 407, a microphone 408, a display 409, and a speaker 410. Each component 401 to 410 is connected by a bus 420.

The CPU 401 controls the entire mobile terminal 30. The ROM 402 records various programs. The RAM 403 is used as a work area for the CPU 401. That is, the CPU 401 controls the entire mobile terminal 30 by executing various programs recorded in the ROM 402 while using the RAM 403 as a work area.

The memory 404 stores various data. For the memory, for example, a flash ROM is used. The memory 404 stores various programs, this application, and the like.
The communication I / F 405 is wirelessly connected to the network and functions as an interface between the mobile terminal 30 and the CPU 401. Communication networks that function as networks include the Internet and mobile phone networks.

Examples of the operation unit 406 include a touch panel and hard keys having a plurality of keys for inputting characters, numerical values, various instructions, and the like.
The camera 407 reads a barcode attached to the product and various two-dimensional codes. The microphone 408 inputs the customer's voice.
The display 409 displays various data such as icons, cursors, menus, windows, characters, and images.
The speaker 410 outputs sound including voice. The mobile terminal 30 is provided with a GPS unit (not shown), and also has a function of receiving radio waves from GPS satellites and outputting information indicating the current position of the mobile terminal 30.

(About the functions of the transaction management device 20 and the mobile terminal 30 according to this embodiment)
Next, the functions of the transaction management device 20 and the mobile terminal 30 according to the present embodiment will be described. The transaction management device 20 includes a storage unit that stores registered product information in a predetermined storage destination assigned to each mobile terminal 30. The storage unit is realized by, for example, a memory such as a hard disk included in the transaction management device 20. The predetermined storage destination is a storage destination uniquely assigned to each mobile terminal 30, and the details will be described later with reference to FIG. 5 and the like, but the storage destination is identified by the cart identification information. The storage unit is not limited to being provided in the transaction management device 20, and may be provided in another device that can be accessed by the transaction management device 20 and the mobile terminal 30.

Each of the plurality of mobile terminals 30 uses a reading unit (for example, a camera 407) to read product information. The product information is, for example, a product code (bar code) attached to the product. Each mobile terminal 30 may receive product information from an operation unit 406 such as a touch panel.

Further, each mobile terminal 30 uses a transmission unit (for example, communication I / F 405) to transmit the product information read by the camera 407 to a predetermined storage destination assigned to each mobile terminal 30.

Here, in the shopping system 1 according to the present embodiment, shopping may be performed by a group such as a family member or a friend. When shopping in a group, if each person takes out the product from the product shelf and each person scans the barcode of the product with one mobile terminal 30, the product may not be registered efficiently.

Therefore, in the shopping system 1 according to the present embodiment, it is possible to link a plurality of mobile terminals 30 (hereinafter, may be referred to as "parent-child interlocking mode") and register products on each mobile terminal 30. ing. In the parent-child interlocking mode, at least one mobile terminal 30 becomes a master unit (hereinafter, may be referred to as "master mobile terminal 30a"), and another one or more mobile terminals 30 become slave units (hereinafter, "slave mobile phone"). It may be called "terminal 30b".) Further, in the present specification, the parent-child interlocking mode may be referred to as "group registration".

The master mobile terminal 30a has more authority to purchase than the slave mobile terminal 30b. For example, the master mobile terminal 30a is a terminal capable of performing settlement. Further, the master mobile terminal 30a can impose various restrictions on the slave mobile terminal 30b. On the other hand, the slave mobile terminal 30b is a terminal having no authority regarding purchase as compared with the master mobile terminal 30a. For example, the slave mobile terminal 30b is a mobile terminal 30 that cannot be settled.

Here, when the customer enters the store, the transaction management device 20 confirms the entry. Confirmation of entering a store is performed, for example, by receiving information for identifying a store (store identification information) or customer identification information for identifying a customer (or mobile terminal 30) from the mobile terminal 30. The transaction management device 20 confirms the customer's entry into the store by using the store identification information and the customer identification information. For example, when the transaction management device 20 confirms entry into the store, the transaction management device 20 generates cart information for registering product information for each mobile terminal 30. The cart information includes cart identification information for identifying the cart information. That is, the transaction management device 20 assigns a storage destination identified by the cart identification information to each mobile terminal 30. Hereinafter, the storage destination assigned to the master mobile terminal 30a may be referred to as a "first storage destination", and the storage destination assigned to the slave mobile terminal 30b may be referred to as a "second storage destination".

(About sharing of location information by master mobile terminal 30a)
The master mobile terminal 30a includes a sharing unit that shares the first storage destination assigned to the own terminal with another mobile terminal 30. For example, the sharing unit sets the first storage destination to the other mobile terminal 30 by outputting the location information indicating the first storage destination assigned to the own terminal so that the other mobile terminal 30 can input. share it. Specifically, the shared unit uses, for example, a display 409 to output location information indicating a first storage destination. Although the details will be described later in Modification 2, the sharing unit can also share the location information indicating the first storage destination with another mobile terminal 30 based on the history of group registration.

The location information indicating the first storage destination is, for example, cart identification information for identifying the cart information assigned to the master mobile terminal 30a. The location information output mode of the master mobile terminal 30a is, for example, an output mode in which a code (two-dimensional code or bar code) indicating the location information is displayed and output on the display 409. The code also includes information (such as the address of the transaction management device 20) for the slave mobile terminal 30b to request the transaction management device 20 to start the parent-child interlocking mode.

The output mode of the location information is not limited to the display output mode by the code. For example, it may be an output mode by communication (for example, infrared communication or communication via the Internet). In addition, the character or number indicating the location information may be displayed and output on the display 409, or may be output as voice from the speaker 410.

The slave mobile terminal 30b includes an input unit (for example, a camera 407) for inputting the location information output by the master mobile terminal 30a. Specifically, the slave mobile terminal 30b inputs the location information by reading the code indicating the location information displayed on the master mobile terminal 30a using the camera 407.

However, when the output mode of the location information by the master mobile terminal 30a is set to the output mode by transmission, the slave mobile terminal 30b may input the location information by reception by the communication I / F 405. Further, when the output mode of the location information by the master mobile terminal 30a is the output mode by the display output of characters and numbers, the slave mobile terminal 30b receives the location information by the operation unit 406 receiving the operation of the characters and numbers from the user. Just enter. Further, when the output mode of the location information by the master mobile terminal 30a is the output mode by voice output of characters and numbers, the slave mobile terminal 30b may input the location information by collecting the sound of the microphone 408.

(About the destination of product information of the slave mobile terminal 30b)
The transmission unit of the slave mobile terminal 30b transmits the product information to the storage destination corresponding to the first storage destination indicated by the location information input by the input unit. The storage destination corresponding to the first storage destination may be the first storage destination itself or another storage destination associated with the first storage destination (for example, a second storage destination).

When the location information is input by the input unit of the slave mobile terminal 30b, the storage control unit (for example, CPU) of the transaction management device 20 stores the product information stored in the first storage destination and the second storage destination. It is stored in association with the stored product information. For example, the transaction management device 20 stores the product information stored in the second storage destination in the first storage destination. That is, the transaction management device 20 stores the product information scanned by the slave mobile terminal 30b in the storage destination where the product information scanned by the master mobile terminal 30a is stored.

However, the transaction management device 20 may associate the first storage destination and the second storage destination so as to be storage destinations for which the settlement is the same. That is, the transaction management device 20 may associate the cart identification information that identifies the first storage destination with the cart identification information that identifies the second storage destination. In this case, at the time of settlement, the settlement may be performed by integrating the product information stored in the first storage destination and the product information stored in the second storage destination.

The storage control unit is not limited to the transaction management device 20, but may be provided in another device (for example, the mobile terminal 30). When the other device includes the storage control unit, the transaction management device 20 is associated with the product information stored in the first storage destination and the product information stored in the second storage destination. Information indicating instructions for memorizing may be transmitted.

(About settlement)
The master mobile terminal 30a includes a settlement unit (for example, CPU 401) that setstles the product information read by the master mobile terminal 30a and the slave mobile terminal 30b. When the master mobile terminal 30a receives the settlement start (pressing the settlement button) from the customer, the POS terminal 40 outputs the settlement information necessary for the settlement so that it can be input. The settlement information includes, for example, location information (cart identification information). The master mobile terminal 30a, for example, encodes the settlement information (two-dimensional code or bar code) and displays it on the display 409. The coded settlement information is not limited to being displayed on the display 409, and may be printed on a paper medium or the like.

The output mode of the settlement information is not limited to the output mode by the code, but may be the output mode by communication (for example, infrared communication or communication via the Internet). Further, the characters and numbers indicating the settlement information may be displayed and output on the display 409, a paper medium, or the like, or the characters and numbers may be output as voice from the speaker 410.

The POS terminal 40 inputs the settlement information output by the master mobile terminal 30a by being scanned by the customer side scanner unit 202. When the output mode of the settlement information by the master mobile terminal 30a is the output mode by transmission, the POS terminal 40 may input the settlement information by receiving the communication unit 305. Further, when the output mode of the settlement information by the master mobile terminal 30a is an output mode in which characters and numbers are displayed and output, the POS terminal 40 inputs the location information by receiving the characters and numbers by the operation unit for the customer. You may. In this case, the POS terminal 40 may be provided with an operation unit for customers. Further, when the output mode of the location information by the master mobile terminal 30a is an output mode in which the location information is output by voice in characters or numbers, the POS terminal 40 may input the location information by collecting the sound of the microphone. In this case, the POS terminal 40 may be provided with a microphone.

Further, the slave mobile terminal 30b does not have a function (settlement unit) for settlement of product information in the parent-child interlocking mode. For example, the settlement button is not displayed on the slave mobile terminal 30b. However, the slave mobile terminal 30b may have a function of performing settlement. Further, the master mobile terminal 30a may be able to select a slave mobile terminal 30b that can accept the user's operation and perform settlement and a slave mobile terminal 30b that cannot perform settlement.

(About cancellation of group registration)
The storage control unit (for example, the CPU) of the transaction management device 20 cancels the association between the first storage destination and the second storage destination when the settlement is performed by the settlement unit of the master mobile terminal 30a. The cancellation of the association is not limited to the case where the settlement is performed, but is also performed when the operation of canceling the parent-child interlocking mode by the master mobile terminal 30a or the slave mobile terminal 30b is accepted. The operation of canceling the parent-child interlocking mode may not be performed by the slave mobile terminal 30b, and may be performed by the master mobile terminal 30a.

(Prohibition of registration of product information on slave mobile terminal 30b)
Further, the storage control unit of the transaction management device 20 prohibits the registration of product information by the slave mobile terminal 30b when the start of settlement (accounting instruction) is received by the master mobile terminal 30a. Specifically, for example, when the master mobile terminal 30a receives the start of settlement, it transmits information indicating the start of settlement to the transaction management device 20. When the transaction management device 20 receives the information indicating the start of payment from the master mobile terminal 30a, the transaction management device 20 prohibits the slave mobile terminal 30b from registering the product information.

The prohibition of the registration of the product information is to prevent the product information from being stored in the second storage destination even if the slave mobile terminal 30b requests the registration of the product information. However, the prohibition of registration of product information is not limited to this, and for example, the reading function of the camera 407 of the slave mobile terminal 30b can be disabled (the imaging area is hidden), or the reading function of the read product information can be performed. You may not have it.

Further, when the registration of the product information is prohibited, the slave mobile terminal 30b displays or voices a notification (registration prohibition notification) indicating that fact. Specifically, when the transaction management device 20 receives the information indicating the start of settlement from the master mobile terminal 30a, the transaction management device 20 transmits information (registration prohibition information) to the effect that the registration of the product information is prohibited to the slave mobile terminal 30b. As a result, the slave mobile terminal 30b can give a registration prohibition notification.

Further, the slave mobile terminal 30b may notify that the product information cannot be registered when the product information is read when the registration of the product information is prohibited. Further, the master mobile terminal 30a may notify the slave mobile terminal 30b when the product information is read (registration request) in the slave mobile terminal 30b while the registration of the product information in the slave mobile terminal 30b is prohibited. Specifically, in this case, when the slave mobile terminal 30b requests the registration of the product information while the slave mobile terminal 30b is prohibited from registering the product information, the transaction management device 20 provides information indicating that fact. , It may be transmitted to the master mobile terminal 30a. As a result, the master mobile terminal 30a can notify that the registration request was made while the registration was prohibited in the slave mobile terminal 30b.

Further, the master mobile terminal 30a may be able to approve the registration request when the registration is requested while the registration is prohibited in the slave mobile terminal 30b. If the request for registration is approved, the settlement process will be performed again from the beginning.

(When the same product information is registered)
At least one of the master mobile terminal 30a and the slave mobile terminal 30b (for example, the master mobile terminal 30a) warns when the master mobile terminal 30a and the slave mobile terminal 30b are requested to register the same product information. (For example, a display 409 or a speaker 410) is provided. For example, when the transaction management device 20 receives a request for registration of the same product information, the transaction management device 20 provides notification information (hereinafter referred to as "same product notification information") for notifying the master mobile terminal 30a of a warning indicating that fact. Send. When the master mobile terminal 30a receives the same product notification information, it notifies a warning that the same product has been registered. The slave mobile terminal 30b may notify the warning, or both the slave mobile terminal 30b and the master mobile terminal 30a may notify the warning.

In the present embodiment, the master mobile terminal 30a can allow the registration of the same product information. On the other hand, the slave mobile terminal 30b cannot allow the registration of the same product information. However, it may be possible for the slave mobile terminal 30b to allow the registration of the same product information. Further, both the master mobile terminal 30a and the slave mobile terminal 30b may be able to allow the registration.

(About the maximum amount of money for the slave mobile terminal 30b)
Further, the master mobile terminal 30a includes a setting unit (CPU401) for setting an upper limit amount of money that can be registered by the slave mobile terminal 30b. The upper limit amount is set in units of 100 yen or 1000 yen, for example. When the upper limit amount is set, the master mobile terminal 30a transmits information indicating the upper limit amount (hereinafter referred to as "upper limit amount information") to the transaction management device 20. Upon receiving the maximum amount information, the transaction management device 20 sets the maximum amount that can be registered by the slave mobile terminal 30b.

Further, the slave mobile terminal 30b may notify the upper limit amount set in the master mobile terminal 30a and the transaction management device 20. Specifically, the slave mobile terminal 30b may notify the maximum amount of money by receiving the maximum amount of money information from the transaction management device 20. Further, the slave mobile terminal 30b may be able to request the change of the upper limit amount to the amount desired by the user. Upon receiving the request, the transaction management device 20 transmits information indicating that the request has been made to the master mobile terminal 30a. The master mobile terminal 30a may accept the change of the upper limit amount by receiving the information.

Further, the slave mobile terminal 30b includes a notification unit (for example, a display 409 or a speaker 410) that notifies a warning when a request for registration of product information is made in excess of the set upper limit amount. For example, when the transaction management device 20 exceeds the upper limit amount and is requested to register the product information, the information for causing the slave mobile terminal 30b to notify the warning about the upper limit amount (hereinafter, "upper limit amount notification information"). ") Is sent. When the slave mobile terminal 30b receives the maximum amount notification information, it notifies a warning that the product cannot be registered. The warning may be notified by both the slave mobile terminal 30b and the master mobile terminal 30a.

Further, even when the upper limit amount is reached, the product may be registered on the master mobile terminal 30a. Specifically, when the master mobile terminal 30a receives the maximum amount notification information, the master mobile terminal 30a confirms whether or not the registration of the product information is permitted by using the display 409 or the like. When the result of confirmation for permitting the product information is obtained, the master mobile terminal 30a transmits the permission information indicating that fact to the transaction management device 20. Then, when the transaction management device 20 receives the permission information from the master mobile terminal 30a, the transaction management device 20 registers the product information. As a result, even when the maximum amount of money is reached, the master mobile terminal 30a can register the product.

(About the maximum number of group registrations)
Further, the master mobile terminal 30a may be able to set the upper limit of the number of registered slave mobile terminals 30b capable of group registration. The upper limit of the number of registered units is, for example, 10. Further, the upper limit number may be changed each time.

(About the history of various settings)
Further, the above-mentioned restrictions imposed by the slave mobile terminal 30b such as the maximum number of registered units and the maximum amount of money may be stored in the transaction management device 20 as a history. Then, the history may be reflected in the initial setting contents at the next group registration.

Next, a case where the product is registered and settled for each mobile terminal 30 in the shopping system 1 (a normal mode other than the parent-child interlocking mode) will be described with reference to FIGS. 5 and 6.

(Example of information managed by the transaction management device 20)
FIG. 5 is an explanatory diagram showing an example of various information for each mobile terminal 30 managed by the transaction management device 20. The transaction management device 20 stores various information including (A) customer information, (B) store information, and (C) cart information.

(Customer information)
FIG. 5A shows an example of customer information. Customer information is information for managing individual customers. Specifically, the customer information includes customer identification information, a customer name, a customer registration date, a customer rank, and a number of points.

The customer identification information is identification information that uniquely identifies a customer. The customer identification information may be, for example, application identification information uniquely assigned to each installed shopping application when the shopping application of the present embodiment is installed. The application identification information may be, for example, a number uniquely (for example, sequentially) assigned to each installed shopping application. Alternatively, the application identification information may be terminal identification information unique to the mobile terminal 50 in which the shopping application is installed. The terminal identification information is hardware that is unique to the hardware of the mobile terminal 50, such as a telephone number assigned to a customer who is a user of the mobile terminal 50, a MAC (Media Access Control) address, and the like. It may be identification information.

The customer name is a customer's name, nickname, or the like.
The customer registration date is the date and time when the customer information is newly registered in the transaction management device 20.
The customer rank is a rank according to the purchase record of the customer. When generating customer information for a new customer, customer identification information, customer name, and customer registration date are generated, but since it is before the actual transaction (product registration) starts, other information (customer rank, etc.) Is not generated.

The number of points is the number of points given to the customer by shopping using this application. The number of points may include the number of points for each store. When the transaction management device 20 generates customer information of a new customer, it generates customer identification information, a customer name, and a customer registration date.

For example, the transaction management device 20 uses the shopping service by the transaction management device 20 from the outside (for example, a predetermined server that provides the entire application, the transaction management device 20) at the time of customer registration (for example, the mobile terminal 50 uses the shopping service by the transaction management device 20). Generate and store customer identification information (when downloading or installing a shopping application). Further, the transaction management device 20 acquires, for example, the information input in the name field of the registration form (input form) by using the mobile terminal 50 at the time of customer registration, and stores it as the customer name. Further, the transaction management device 20 acquires, for example, the current date and time at the time of customer registration and stores it as the customer registration date.

(store information)
FIG. 5B shows an example of store information. Store information is information for managing each store. Specifically, the store information includes the store identification information, the store name, the store identification information 1 (two-dimensional code information), and the store identification information 2 (location information).
The store identification information includes a store (store name) or company code and a branch code.
The store name is the name of the store, and is composed of, for example, a store name (store name) or a company name and a branch name.

The store identification information 1 and 2 are information for identifying the store (the store where the product is bought and sold) to be traded. The store identification information 1 is, for example, two-dimensional code information. The store identification information 2 is location information (GPS information) indicating the location of the store. In the example shown in FIG. 5B, the store identification information and the store identification information 1 are stored separately, but since both are information that can uniquely identify the store, at least one of them is used. It suffices if the information is stored.

The transaction management device 20 may acquire and store store information and the like from the outside (a server (not shown) of the headquarters that controls each store). Further, the transaction management device 20 replaces or additionally stores the store information in the storage unit in the own device, or a part of the store information or a part of the store information in another device (a file server or the like accessible to the transaction management device 20). You may memorize everything.

(Cart information)
FIG. 5C shows an example of cart information. Cart information is information about a customer's purchase at a store. Specifically, the cart information includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, and registered product information.
The cart identification information is information for identifying the cart information. Specifically, the cart identification information includes the store identification information, the date, and the serial number (for example, the serial number for each date of each store).

The transaction start date and time is the date and time when the transaction is started, for example, the generation date and time of the cart information. The transaction start date and time may be the registration date and time of one product (the date and time when the registered product information (registered product 1) shown in FIG. 5C is stored). Further, the registration date and time for each product may be stored separately.

The transaction end date and time is the date and time when the transaction was completed, and specifically, the date and time when the transaction was settled. For example, the transaction end date and time may be the date and time when the settlement is started or the date and time when the settlement is completed.
The customer identification information is information that identifies the customer who conducts the transaction. The transaction management device 20 generates cart identification information, transaction start date and time, and customer identification information when generating cart information, but since it is before the start of actual transaction (product registration), other information (transaction). End date and time, etc.) are not generated.

The registered product information (total) is information that is updated every time a product is registered. The registered product information (total) includes the number of products (number of products), the estimated subtotal amount, the subtotal amount, and the like. The registered product information (1) is the registration information of one product. The registered product information (2) is the registration information of two products. In the example shown in FIG. 5C, the registered product information (3) to the registered product information (N: N is an integer) are not shown. The registered product information (N) includes a product code, a product name (product name), a price, and the like.

The registered product information (N) may include the registration date and time of the product of the N item. That is, the transaction management device 20 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a material for determining the necessity of applying a service such as a time service and the effect after application.

Next, the reserved product will be described. The reserved product is, for example, a product to be purchased, but the registration is suspended without being normally registered. Here, the registered product information is a product that is stored when the product code is successfully scanned and the product can be identified based on the product code. On the other hand, the reserved product information is a product that is stored when the product code is not successfully scanned, or when the product code is successfully scanned but the product cannot be identified based on the product code.

The pending products include a pending product with a read NG and a reserved product with an inquiry NG. The pending product of reading NG is a reserved product that could not be registered because the scanning of the product code failed (the scanning by the scanner became NG). For example, if there are wrinkles on the product package, or if the barcode is printed with blur or stains, the barcode may not be recognized due to a timeout.

Here, it will be described in detail that the barcode is not recognized due to the timeout. The mobile terminal 50 is provided with various sensors (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.), and can determine that a barcode is being read by using the detection results of the various sensors and the imaging results of the camera 507. is there.

Specifically, the mobile terminal 50 is in a situation where the mobile terminal 50 is tilted using the detection results of various sensors, and the product exists at a position separated from the mobile terminal 50 by a certain distance. It is possible to determine the situation as if the barcode is being read. Then, after determining that the barcode is being read, the mobile terminal 50 identifies the read NG pending product as a timeout when the barcode cannot be read within a predetermined time.

Further, the reading NG may be, for example, a case where the product is put into the basket by pretending to read the barcode of the product. Therefore, since there is a possibility of unauthorized operation, the reserved product (reading NG) can be said to be a reserved product for confirming unauthorized operation, which requires confirmation of whether or not the operation is unauthorized.

The pending product of inquiry NG succeeded in scanning the product code (not reading NG), and although the product master was inquired about the product with the product code, the product identification failed (product inquiry was NG). ) This is a pending product that could not be registered.

The pending product information (total) includes the number of products (number of products) of the reserved products (reading NG, inquiry NG) and the number of products for which unauthorized operation is confirmed.

The reserved product information (pending product N: N is an integer) is information on the reserved product of N items, and includes the reserved product type of the reserved product of N items. The hold product type is information indicating whether the hold product is a hold product of reading NG or a hold product of inquiry NG. In this example, "1" of the reserved product type indicates read NG, and "2" of the reserved product type is inquiry NG.

Further, the reserved product information of the reserved product (reading NG) includes the image data of the reserved product of the read NG (image data captured at the time of reading NG) in addition to the reserved product type "1 (reading NG)". For example, the reserved product information (3) includes the reserved product type "1 (reading NG)" and image data.

Further, the reserved product information of the reserved product of the inquiry NG includes the product code of the reserved product of the inquiry NG in addition to the reserved product type "2 (inquiry NG)". For example, the reserved product information (1) includes a product code in addition to the reserved product type "2 (inquiry NG)".

In addition, the transaction management device 20 replaces or additionally stores the cart information in the storage unit in the own device, or a part of the cart information or a part of the cart information in another device (a file server or the like accessible to the transaction management device 20). You may memorize everything.

(Example of processing when registering and paying for products for each mobile terminal 30)
FIG. 6 is a sequence diagram showing a processing flow when registering and paying for products for each mobile terminal 30 in the shopping system 1. Note that FIG. 6 describes a flow from a customer visiting a store, registering a product to be purchased using his / her mobile terminal 30, and completing the settlement of the product on the POS terminal 40. ..

Step S601: First, the mobile terminal 30 acquires information that identifies the store (store identification information). Here, an example of the acquisition mode of the store specific information will be described. For example, a two-dimensional code indicating store identification information is displayed near the entrance of the store. The two-dimensional code may be displayed and output on a predetermined display device, or may be displayed and output by printing on a medium.

The printed medium is, for example, a paper medium. This paper medium may be affixed near the entrance of the store or may be distributed to customers at the store. The camera 407 of the mobile terminal 30 scans the two-dimensional code by the operation of the customer who visits the store. As a result, the mobile terminal 30 can acquire the store specific information. The two-dimensional code may include store identification information for identifying the store.

Further, the mobile terminal 30 may display a screen prompting the scanning of the two-dimensional code as the initial screen when the application is activated in response to the operation of the customer who visits the store. In addition, the mobile terminal 30 activates the application by scanning the two-dimensional code, connects to the transaction management device 20, and displays a screen notifying that the connection is being connected to the transaction management device 20 as an initial screen. You may try to do it.

In addition, as another example of the acquisition mode of store specific information, acquisition of location information can be mentioned. For example, the mobile terminal 30 acquires location information (GPS information) according to the operation of a customer who visits the store. This location information is information that replaces the store specific information. The mobile terminal 30 acquires location information and connects to the transaction management device 20 by activating this application in response to an operation of a customer who visits the store, and is connected to the transaction management device 20 as an initial screen. A screen for notifying the user may be displayed.

In addition, in the identification of the store using the location information, a plurality of stores may be specified. That is, it may not be possible to identify one store. In this case, the transaction management device 20 may transmit information indicating that fact or information prompting the identification of the store to the mobile terminal 30. Then, when the mobile terminal 30 receives the information from the transaction management device 20, it notifies that the customer is prompted to display a selection screen for identifying the store or to scan the two-dimensional code indicating the store identification information. You can do it.

The mobile terminal 30 that has acquired the store identification information requests the transaction management device 20 to start a transaction. Specifically, as shown in the transmission / reception data D1 of FIG. 6, the mobile terminal transmits the acquired store identification information and the customer identification information to the transaction management device 20. The customer identification information is information stored in the transaction management device 20 or the mobile terminal 30 when, for example, a new customer registration is performed (for example, when the application is installed on the mobile terminal 30). Specifically, the information such as the name entered in the registration form is stored in the transaction management device 20 and the mobile terminal 30 with the customer identification information attached by the transaction management device 20.

Further, when the mobile terminal 30 acquires the store specific information, the mobile terminal 30 may output information on the service being implemented at the store (flyer information distributed on that day) and available coupon information on the display screen. For example, service-related information and coupon information may be received from the transaction management device 20 by the mobile terminal 30 making a transaction start request to the transaction management device 20.

The mobile terminal 30 also stores the destination information (address of the transaction management device 20) when newly registering a customer. The two-dimensional code displayed near the entrance of the store may include the destination information in addition to the store identification information. The mobile terminal 30 can also access the transaction management device 20 by acquiring the destination information as well as the store identification information by scanning the two-dimensional code.

Step S602: When the transaction management device 20 receives the customer identification information and the store identification information as a transaction start request from the mobile terminal 30, the transaction management device 20 generates cart information of the transaction. Specifically, as shown in FIG. 6C, the transaction management device 20 generates cart identification information, transaction start date and time, and customer identification information. Since the transaction management device 20 is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated at this timing.

Specifically, when the transaction management device 20 receives the store identification information and the customer identification information as a transaction start request from the mobile terminal 30, the transaction management device 20 refers to the store information (see FIG. 6B) and obtains the store identification information. Identify. When the transaction management device 20 receives the location information from the mobile terminal 30, the transaction management device 20 refers to the store identification information 2 of the store information to specify the store identification information corresponding to the location information. When the store identification information is included in the two-dimensional code, the transaction management device 20 can also acquire the store identification information by combining the received two-dimensional code.

Further, when the transaction management device 20 receives the transaction start request (store identification information and customer identification information) from the mobile terminal 30, the transaction management device 20 acquires the current date and issues (numbers) the serial number. Further, the transaction management device 20 combines the acquired store identification information, the acquired current date, and the issued serial number, and stores the acquired store identification information as cart identification information. Further, when the transaction management device 20 receives the transaction start request from the mobile terminal 30, the transaction management device 20 stores the current date and time in the transaction start date and time (generation date and time) in the cart information. Further, when the transaction management device 20 receives the transaction start request from the mobile terminal 30, the transaction management device 20 stores the customer identification information received from the mobile terminal 30 in the customer identification information in the cart information.

Step S603: When the transaction management device 20 generates the cart information of the transaction, the product registration initial screen information (screen information of the product registration screen which is the initial screen) is generated and transmitted to the mobile terminal 30. Specifically, the transaction management device 20 transmits the cart identification information to the mobile terminal 30 together with the product registration initial screen information (transmission / reception data D2 in FIG. 6).

Step S604: When the mobile terminal 30 receives the cart identification information and the product registration initial screen information from the transaction management device 20, the mobile terminal 30 stores the cart identification information and displays the product registration initial screen on the display unit.

Step S605: The mobile terminal 30 scans the bar code attached to the product and reads the product code in response to the operation of the customer. When the barcode scanning is successful, the mobile terminal 30 acquires the product code and transmits the acquired product code and the cart identification information to the transaction management device 20 (see transmission / reception data D3 in FIG. 6). When the read product is, for example, an age confirmation product (specific product), cart identification information and information indicating the specific product are transmitted as transmission / reception data D3.

Here, although the customer scans the barcode, the product may not be registered (there may be unscanned products). Unscanned merchandise (pending merchandise) may be caused by fraudulent activity by the customer. An unscanned product occurs rather than fraudulently, for example, when an unfamiliar customer attempts to scan a barcode, but the barcode cannot be scanned successfully. In addition to this, there is a case where the product to be registered as a product is a product (so-called NON file product) that is not registered in the product master even though the barcode is scanned.

On the other hand, the case where the unscanned product is caused by fraudulent activity is the case where the customer puts the product into the shopping cart without scanning the barcode or pretending to scan the barcode. The detection of fraud includes, for example, a scan result indicating whether or not a barcode has been scanned, a camera image image that captures the inside of a shopping cart, a detection result that detects the total weight of products in the shopping cart, and the like. Is done by using. The unscanned product is transmitted to the transaction management device 20 as a reserved product in the transmission / reception data D3. In this case, the cart identification information and the information indicating the reserved product are transmitted as the transmission / reception data D3.

Further, the product without the barcode may be a reserved product according to the operation of the customer. In this case, the customer may be urged to take an image of the reserved product, and the imaged result may be transmitted to the transaction management device 20 or the POS terminal 40. As a result, the store clerk can easily identify the reserved product by displaying the imaged result (image) and the reserved product in association with each other at the time of payment.

Step S606: When the transaction management device 20 receives the product code and the cart identification information from the mobile terminal 30, the transaction management device 20 identifies the cart information including the received cart identification information.

Step S607: The transaction management device 20 updates the registered product information included in the specified cart information. Specifically, when the transaction management device 20 receives the product code of N items, the transaction management device 20 stores the product code as the product code of the registered product information (registered product N). Further, the transaction management device 20 stores the product code, the product name, and the price in association with each other as product information (registered product N). Further, the transaction management device 20 updates the cumulative information (cumulative number of products, subtotal amount, etc.) of the registered product information in the specified cart information.

Step S608: When the transaction management device 20 updates the registered product information in the cart, the product registration update screen information (screen information of the product registration screen which is an update screen to which the registered product is added) is generated, and the mobile terminal 30 Send to. At this time, the transaction management device 20 transmits the cart identification information to the mobile terminal 30 together with the product registration update screen information (transmission / reception data D4 in FIG. 6).

Step S609: When the mobile terminal 30 receives the cart identification information and the product registration update screen information from the transaction management device 20, the mobile terminal 30 displays the product registration update screen in which the product is added to the registration screen. Although not shown in FIG. 6 for convenience of explanation, the processes of steps S605 to S609 are repeatedly executed every time the barcode attached to the product is scanned. That is, the processing of steps S605 to S609 loops until the accounting instruction of step S610 described later is received.

Step S610: The mobile terminal 30 receives an accounting instruction operated by the customer. For example, the mobile terminal 30 receives an accounting instruction by pressing the accounting button displayed on the display 409.

Step S611: When the mobile terminal 30 receives the accounting instruction, the mobile terminal 30 generates a two-dimensional code. This two-dimensional code includes information (for example, cart identification information) necessary for executing the settlement process on the POS terminal 40 for the product to be purchased. When the mobile terminal 30 generates the two-dimensional code, the generated two-dimensional code is displayed on the display 409.

Step S612: The customer who has completed the registration of the product goes to the POS terminal 40 and causes the customer side scanner unit 202 of the POS terminal 40 to scan the two-dimensional code displayed on the display 409 of the mobile terminal 30. As a result, the POS terminal 40 can acquire the cart identification information.

Step S613: When the POS terminal 40 reads the two-dimensional code displayed on the display 409 of the mobile terminal 30, the POS terminal 40 requests the transaction management device 20 to calculate the subtotal amount. For example, the POS terminal 40 transmits a calculation request (small calculation output request information) requesting the calculation of the subtotal amount and the cart identification information restored from the two-dimensional code to the transaction management device 20 (transmission / reception data D5 in FIG. 6). ).

Step S614: When the transaction management device 20 receives the cart identification information and the subcalculation request information from the POS terminal 40, the transaction management device 20 identifies the cart information including the received cart identification information.

Step S615: When the transaction management device 20 specifies the cart information, the transaction management device 20 calculates the subtotal amount (registered product information (total)) included in the cart information. If there is a discount for each product, the discount amount may be calculated for each product in step S615 to calculate the subtotal amount. If the tax rate is different for each product, the subtotal amount may be calculated in consideration of the tax rate for each product in step S615.

Step S616: The transaction management device 20 transmits subtotal information indicating the calculated subtotal amount to the POS terminal 40 together with the cart identification information (transmission / reception data D6 in FIG. 6). If the specified cart information includes a specific product such as an age confirmation product or a reserved product, the transmission / reception data D6 including the information of the specific product is transmitted to the POS terminal 40.

Step S617: When the POS terminal 40 receives the subtotal information from the transaction management device 20, the POS terminal 40 displays the subtotal amount on the customer side display unit 201. If there are reserved products, the subtotal amount excluding the reserved products may be displayed, or the subtotal amount may not be displayed. In addition, if there is a specific product such as an age confirmation product, notification processing is performed. In the notification process, the POS terminal 40 transmits, for example, information indicating that there is a reserved product or a specific product to a monitoring device or a terminal device owned by a store clerk, or information for sending the store clerk to the POS terminal 40. Further, in the notification process, the POS terminal 40 displays a notification screen indicating that there is a reserved product or a specific product on the customer side display unit 201 or the store clerk side display unit 207.

Step S618: The POS terminal 40 executes payment (settlement processing). In the settlement process, the POS terminal 40 accepts the selection of the payment type. The payment type may be registered in advance in this application. When the payment type is registered, the POS terminal 40 does not have to display the payment type selection screen. Even when the payment type is registered, the POS terminal 40 may display a screen for selecting the payment type.

Further, in the settlement process, the POS terminal 40 issues a receipt and transmits the settlement completion information together with the cart information to the transaction management device 20. Then, the transaction management device 20 stores the transaction end date and time (settlement date and time) of the cart. As a result, a series of processes is completed.

(About processing in parent-child interlocking mode)
Next, with reference to FIG. 7 and the like, a flow in the case of starting the parent-child interlocking mode at the time of entering the store to register and settle the product will be described. FIG. 7 is a sequence diagram showing a processing flow when registration and settlement are performed in the parent-child interlocking mode in the shopping system 1. In FIG. 7, the steps described in FIG. 6 are omitted as appropriate.

Step S701: First, the master mobile terminal 30a acquires store identification information. Then, the master mobile terminal 30a requests the transaction management device 20 to start a transaction.
Step S702: On the other hand, the slave mobile terminal 30b also acquires the store identification information. Then, the slave mobile terminal 30b also requests the transaction management device 20 to start the transaction. As for the slave mobile terminal 30b, at least it is sufficient to confirm the entry into the store, so it is not necessary to make a request to start a transaction.

Step S703: When the transaction management device 20 receives the transaction start request from the master mobile terminal 30a, the transaction management device 20 generates cart information corresponding to the master mobile terminal 30a. Further, when the transaction management device 20 receives the transaction start request from the slave mobile terminal 30b, the transaction management device 20 generates cart information corresponding to the slave mobile terminal 30b. As for the slave mobile terminal 30b, at least it is sufficient to confirm the entry into the store, so it is not necessary to generate the cart information. Although not shown, when the cart information is generated, the transaction management device 20 transmits the cart identification information for identifying the generated cart information to the master mobile terminal 30a and the slave mobile terminal 30b, respectively.

Step S704: The master mobile terminal 30a accepts the start of the parent-child interlocking mode. When accepting the start of the parent-child interlocking mode, the master mobile terminal 30a receives an output instruction of cart identification information that identifies a storage destination (cart information) of the registered product information of the master mobile terminal 30a.

Step S705: When the master mobile terminal 30a receives the start of the parent-child interlocking mode, it generates a two-dimensional code for registration and displays it on the display 409. The two-dimensional code for registration includes cart identification information and information for requesting the start of the parent-child interlocking mode.

Step S706: The slave mobile terminal 30b activates the camera 407 and reads the registration two-dimensional code displayed on the master mobile terminal 30a. As a result, the slave mobile terminal 30b can input the cart identification information of the master mobile terminal 30a.

Step S707: When the slave mobile terminal 30b reads the registration two-dimensional code, it automatically requests the transaction management device 20 for group registration. In the request for group registration, the slave mobile terminal 30b receives the cart identification information of the master mobile terminal 30a obtained from the reading result of the camera 407, the cart identification information of the slave mobile terminal 30b, the customer identification information of the slave mobile terminal 30b, and the like. Send information to request group registration. Further, the slave mobile terminal 30b stores the cart identification information of the master mobile terminal 30a obtained from the reading result of the two-dimensional code.

Step S708: When the slave mobile terminal 30b requests group registration, the transaction management device 20 performs group registration. When performing group registration, the transaction management device 20 causes the master mobile terminal 30a to display a confirmation screen as to whether or not to register the slave mobile terminal 30b as a group, and performs group registration according to the confirmation result on the confirmation screen. You may do it.

The group registration is, for example, set to store the product information read by the slave mobile terminal 30b in the cart information assigned to the master mobile terminal 30a. Since the transaction management device 20 does not use the cart information of the slave mobile terminal 30b when the group is registered, the cart information assigned to the slave mobile terminal 30b may be deleted.

The group registration may associate the cart information assigned to the master mobile terminal 30a with the cart information assigned to the slave mobile terminal 30b. In this case, the settlement of these cart information may be performed collectively.

Step S709: When the group registration is completed, the transaction management device 20 transmits a registration completion notification to the master mobile terminal 30a and the slave mobile terminal 30b. The transaction management device 20 may transmit the cart identification information assigned to the master mobile terminal 30a to the master mobile terminal 30a and the slave mobile terminal 30b together with the registration completion notification.

Step S710: The master mobile terminal 30a starts the parent-child interlocking mode when the group registration is performed in the transaction management device 20. Specifically, the master mobile terminal 30a displays a screen on the display 409 to the effect that the parent-child interlocking mode is started.

Step S711: The slave mobile terminal 30b starts the parent-child interlocking mode when the group registration is performed in the transaction management device 20. Specifically, the slave mobile terminal 30b displays a screen indicating that the parent-child interlocking mode is started on the display 409. When the parent-child interlocking mode is started, the slave mobile terminal 30b changes the transmission destination of the product information of the scanned product to the storage destination in which the product information of the product scanned by the master mobile terminal 30a is stored.

Step S712: The master mobile terminal 30a scans the bar code attached to the product and reads the product code in response to the operation of the customer. When the barcode scanning is successful, the master mobile terminal 30a acquires the product code and transmits the acquired product code and the cart identification information of the master mobile terminal 30a to the transaction management device 20.

Step S713: The slave mobile terminal 30b scans the bar code attached to the product and reads the product code in response to the operation of the customer. When the barcode scanning is successful, the slave mobile terminal 30b acquires the product code and transmits the acquired product code and the cart identification information of the master mobile terminal 30a to the transaction management device 20.

Step S714: The transaction management device 20 updates (stores) the registered product information included in the cart information. Specifically, when the transaction management device 20 receives the product code and the cart identification information from the master mobile terminal 30a and the slave mobile terminal 30b, the transaction management device 20 identifies and identifies the cart information assigned to the master mobile terminal 30a. Update the registered product information in the cart information you have created.

Step S715: When the transaction management device 20 updates the registered product information in the cart information, the product registration update screen information and the cart identification information of the master mobile terminal 30a are transmitted to the master mobile terminal 30a and the slave mobile terminal 30b. To do.

Step S716: When the master mobile terminal 30a receives the cart identification information and the product registration update screen information from the transaction management device 20, the master mobile terminal 30a displays the product registration update screen in which the product is added to the registration screen. For example, even when the registered product information of the cart information is updated by the slave mobile terminal 30b, the master mobile terminal 30a displays the product registration update screen to which the product is added.

Step S717: When the slave mobile terminal 30b receives the cart identification information and the product registration update screen information from the transaction management device 20, the slave mobile terminal 30b displays the product registration update screen in which the product is added to the registration screen. For example, even when the registered product information of the cart information is updated by the master mobile terminal 30a, the slave mobile terminal 30b displays the product registration update screen to which the product is added.

Although not shown in FIG. 7 for convenience of explanation, the processes of steps S712 to S717 are repeatedly executed every time the barcode attached to the product is scanned. That is, the processing of steps S712 to S717 loops until the instruction to start the settlement in step S718, which will be described later, is received.

Step S718: The master mobile terminal 30a receives an instruction to start settlement by the operation of the customer. For example, the master mobile terminal 30a receives an instruction to start settlement by pressing the settlement button displayed on the display 409.

Step S719: When the master mobile terminal 30a receives the payment start instruction, the master mobile terminal 30a transmits the payment start information indicating that the payment start instruction has been received to the transaction management device 20 together with the cart identification information.

Step S720: When the transaction management device 20 receives the settlement start information from the master mobile terminal 30a, the transaction management device 20 transmits the registration prohibition information to the slave mobile terminal 30b, which indicates that the registration of the product information by the slave mobile terminal 30b is prohibited.

Step S721: When the slave mobile terminal 30b receives the registration prohibition information from the transaction management device 20, it gives a registration prohibition notification indicating that the product cannot be registered.

Step S722: When the master mobile terminal 30a receives the accounting instruction, the master mobile terminal 30a generates a two-dimensional code for settlement. The two-dimensional code for settlement includes information necessary for executing the settlement process on the POS terminal 40 for the product to be purchased. Specifically, the two-dimensional code for settlement includes the cart identification information of the master mobile terminal 30a. When the master mobile terminal 30a generates the two-dimensional code for settlement, the generated two-dimensional code for settlement is displayed on the display 409.

Step S723: The customer who possesses the master mobile terminal 30a goes to the POS terminal 40 and causes the customer side scanner unit 202 of the POS terminal 40 to read the two-dimensional code for settlement displayed on the display 409 of the master mobile terminal 30a. .. As a result, the POS terminal 40 can acquire the cart identification information of the master mobile terminal 30a.

At the time of payment, the clerk checks the items on hold and specific items. Therefore, at the time of payment, it is necessary that all the products scanned by the slave mobile terminal 30b and the products scanned by the master mobile terminal 30a are available.

Step S724: When the POS terminal 40 reads the two-dimensional code for settlement displayed on the display 409 of the master mobile terminal 30a, the POS terminal 40 requests the transaction management device 20 to calculate the subtotal amount. Specifically, the POS terminal 40 transmits a calculation request (subcalculation request information) requesting the calculation of the subtotal amount and the cart identification information restored from the two-dimensional code for settlement to the transaction management device 20.

Step S725: When the POS terminal 40 requests the calculation of the subtotal amount, the transaction management device 20 performs the subtotal amount calculation process. The subtotal amount calculation process identifies the cart information based on the cart identification information received from the POS terminal 40, calculates the subtotal amount included in the cart information, and adds the subtotal information indicating the subtotal amount to the POS terminal together with the cart identification information. This is a process of transmitting to 40.

Step S726: When the POS terminal 40 receives the subtotal information and the cart identification information from the transaction management device 20, the POS terminal 40 performs payment processing. The payment process is a process of displaying the subtotal amount on the customer side display unit 201 and making a payment.

Step S727: When the payment process is completed, the POS terminal 40 transmits a completion notification indicating that the payment process is completed to the transaction management device 20 together with the cart identification information.

Step S728: When the transaction management device 20 receives the cart identification information and the completion notification from the POS terminal 40, it stores the transaction end date and time (settlement date and time) of the cart information and cancels the group registered in this process.
Step S729: When the transaction management device 20 cancels the group, the transaction management device 20 transmits a cancellation notification to that effect to the master mobile terminal 30a and the slave mobile terminal 30b.

Step S730: When the master mobile terminal 30a receives the cancellation notification from the transaction management device 20, the master mobile terminal 30a ends the parent-child interlocking mode and ends a series of processes.
Step S731: When the slave mobile terminal 30b receives the cancellation notification from the transaction management device 20, it ends the parent-child interlocking mode and ends a series of processes.

(Example of cart information 800 in parent-child interlocking mode)
FIG. 8 is an explanatory diagram showing an example of the cart information 800 in the parent-child interlocking mode. Hereinafter, points different from the cart information shown in FIG. 5C will be described. Further, in FIG. 8, the reserved product information is not shown. The cart information 800 shown in FIG. 8 includes the registered product information of the product scanned by the master mobile terminal 30a and the registered product information of the product scanned by the slave mobile terminal 30b. The cart information 800 can store customer information 801 for a plurality of people as compared with the cart information shown in FIG. 5C, and customer information 802a and 802b are stored in the registered product information. It differs from the cart information shown in FIG. 5C in that the maximum amount information of the slave mobile terminal 30b is stored.

Specifically, in the cart information 800 shown in FIG. 8, the customer information 801 indicates the customer identification information registered in the group. The "master" shown in the customer information 801 indicates the customer identification information of the master mobile terminal 30a. Further, the "slave" shown in the customer information 801 indicates the customer identification information of the slave mobile terminal 30b. As a general rule, one master mobile terminal 30a is registered. However, when payment can be made with a plurality of mobile terminals 30, a plurality of master mobile terminals 30a can also be registered. One or more slave mobile terminals 30b are registered.

Further, in the cart information 800, customer information 802a and 802b are stored in the registered product information. The customer information 802a and 802b indicate the customer corresponding to the mobile terminal 30 that has scanned the registered product information. For example, the registered product 1 indicates that the product information has been scanned by the customer (master mobile terminal 30a) indicated by the customer information 802a. Further, the registered product 2 indicates that the product information has been scanned by the customer (slave mobile terminal 30b) indicated by the customer information 802b.

Further, the cart information 800 stores the upper limit amount information 803 of the slave mobile terminal 30b. The upper limit amount information 803 can be set to a different amount for each slave mobile terminal 30b depending on the master mobile terminal 30a. The maximum amount information 803 can be changed each time by the master mobile terminal 30a. Further, the upper limit amount information 803 stores the amount of money for each slave mobile terminal 30b set last time, and when the same slave mobile terminal 30b is registered as a group next time, the stored amount is used as the initial value. It may be set.

(An example of processing related to the parent-child interlocking mode performed by the master mobile terminal 30a)
Next, an example of processing related to the parent-child interlocking mode performed by the master mobile terminal 30a will be described with reference to FIG. FIG. 9 is a flowchart showing an example of processing related to the parent-child interlocking mode performed by the master mobile terminal 30a. The process shown in the flowchart of FIG. 9 is always (regularly) started at the master mobile terminal 30a (at a very short time interval).

In FIG. 9, the master mobile terminal 30a determines whether or not the start of the parent-child interlocking mode, that is, the output instruction of the cart identification information has been received (step S901). When the output instruction of the cart identification information is not accepted (step S901: NO), the master mobile terminal 30a proceeds to step S903. On the other hand, when the output instruction of the cart identification information is received (step S901: YES), the master mobile terminal 30a generates and displays the two-dimensional code for registration of the parent-child interlocking mode on the display 409 (step S902).

Then, the master mobile terminal 30a determines whether or not the registration completion notification of the group registration (parent-child interlocking mode) has been received from the transaction management device 20 (step S903). If the registration completion notification is not received (step S903: NO), the master mobile terminal 30a proceeds to step S905. On the other hand, when the registration completion notification is received (step S903: YES), the master mobile terminal 30a starts the parent-child interlocking mode (step S904).

Further, the master mobile terminal 30a determines whether or not the operation for setting the upper limit amount has been accepted (step S905). The operation for setting the upper limit amount may be performed before the start of the parent-child interlocking mode or after the start of the parent-child interlocking mode. When the operation for setting the upper limit amount is not accepted (step S905: NO), the master mobile terminal 30a proceeds to step S907. When the operation for setting the upper limit amount is accepted (step S905: YES), the master mobile terminal 30a transmits the upper limit amount information indicating the upper limit amount to the transaction management device 20 (step S906).

Then, the master mobile terminal 30a determines whether or not the product has been scanned by the function of the camera 407 (step S907). If the product is not scanned (step S907: NO), the master mobile terminal 30a proceeds to step S909. When the product is scanned (step S907: YES), the master mobile terminal 30a transmits the product information (product code) of the scanned product to the transaction management device 20 (step S908).

Then, the master mobile terminal 30a determines whether or not the same product notification information for notifying a warning about the registration operation of the same product has been received (step S909). When the same product notification information is not received (step S909: NO), the master mobile terminal 30a proceeds to step S911. On the other hand, when the same product notification information is received (step S909: YES), the master mobile terminal 30a notifies a warning indicating that the same product registration operation has been performed (step S910).

Then, the master mobile terminal 30a determines whether or not the permission for registration of the same product has been accepted (step S911). If the registration permission is not accepted (step S9111: NO), the master mobile terminal 30a proceeds to step S913. When the permission for registration is accepted (step S911: YES), the master mobile terminal 30a requests the transaction management device 20 to register the same product (step S912).

Then, the master mobile terminal 30a determines whether or not the settlement button has been pressed, that is, whether or not the settlement start has been accepted (step S913). When the settlement start is not accepted (step S913: NO), the master mobile terminal 30a proceeds to step S915. On the other hand, when the settlement start is accepted (step S913: YES), the master mobile terminal 30a generates and displays the settlement two-dimensional code (step S914).

Then, the master mobile terminal 30a determines whether or not a cancellation notification indicating the cancellation of the group has been received from the transaction management device 20 (step S915). When the cancellation notification is not received (step S915: NO), the master mobile terminal 30a ends a series of processes. On the other hand, when the master mobile terminal 30a receives the cancellation notification (step S915: YES), the master mobile terminal 30a ends the parent-child interlocking mode (step S916), and ends a series of processes.

(Example of processing related to parent-child interlocking mode performed by slave mobile terminal 30b)
Next, an example of processing related to the parent-child interlocking mode performed by the slave mobile terminal 30b will be described with reference to FIG. FIG. 10 is a flowchart showing an example of processing related to the parent-child interlocking mode performed by the slave mobile terminal 30b. The process shown in the flowchart of FIG. 10 is always (regularly) started at the slave mobile terminal 30b (at a very short time interval).

In FIG. 10, the slave mobile terminal 30b determines whether or not the two-dimensional code for registration of the parent-child interlocking mode has been read by the function of the camera 407 (step S1001). When the registration two-dimensional code is not read (step S1001: NO), the slave mobile terminal 30b proceeds to step S1003. On the other hand, when the registration two-dimensional code is read (step S1001: YES), the slave mobile terminal 30b transmits the cart identification information included in the registration two-dimensional code to the transaction management device 20, and also registers the group. (Step S1002).

Then, the slave mobile terminal 30b determines whether or not the registration completion notification of the group registration (parent-child interlocking mode) has been received from the transaction management device 20 (step S1003). If the registration completion notification is not received (step S1003: NO), the slave mobile terminal 30b proceeds to step S1006. On the other hand, when the registration completion notification is received (step S1003: YES), the slave mobile terminal 30b changes the cart information that stores the product information (step S1004). Specifically, the slave mobile terminal 30b changes the transmission destination of the product information to the cart information 800 (see FIG. 8) identified by the cart identification information read from the registration two-dimensional code. Then, the slave mobile terminal 30b starts the parent-child interlocking mode (step S1005).

Then, the slave mobile terminal 30b determines whether or not the product has been scanned by the function of the camera 407 (step S1006). If the product is not scanned (step S1006: NO), the slave mobile terminal 30b proceeds to step S1008. When the product is scanned (step S1006: YES), the slave mobile terminal 30b transmits the scanned product information (product code) to the transaction management device 20 (step S1007).

Then, the slave mobile terminal 30b determines whether or not the same product notification information for notifying a warning about the registration operation of the same product has been received (step S1008). When the same product notification information is not received (step S1008: NO), the slave mobile terminal 30b proceeds to step S1010. On the other hand, when the same product notification information is received (step S1008: YES), the slave mobile terminal 30b notifies a warning indicating that the same product registration operation has been performed (step S1009).

Then, the slave mobile terminal 30b determines whether or not the upper limit amount notification information for notifying the warning about the upper limit amount has been received (step S1010). When the upper limit amount notification information is not received (step S1010: NO), the slave mobile terminal 30b proceeds to step S1012. When the upper limit amount notification information is received (step S1010: YES), the slave mobile terminal 30b notifies that the product cannot be registered (step S1011).

Then, the slave mobile terminal 30b determines whether or not the transaction management device 20 has received the cancellation notification indicating the cancellation of the group (step S1012). When the cancellation notification is not received (step S1012: NO), the slave mobile terminal 30b ends a series of processes. On the other hand, when the slave mobile terminal 30b receives the release notification (step S1012: YES), the slave mobile terminal 30b ends the parent-child interlocking mode (step S1013), and ends a series of processes.

(Example of processing related to the parent-child interlocking mode performed by the transaction management device 20)
Next, an example of processing related to the parent-child interlocking mode performed by the transaction management device 20 will be described with reference to FIG. FIG. 11 is a flowchart showing an example of processing related to the parent-child interlocking mode performed by the transaction management device 20. The process shown in the flowchart of FIG. 11 is always (regularly) started in the transaction management device 20 (at a very short time interval).

In FIG. 11, the transaction management device 20 determines whether or not there is a request for group registration from the slave mobile terminal 30b (step S1101). If there is no request for group registration (step S1101: NO), the transaction management device 20 proceeds to step S1104. On the other hand, when there is a request for group registration (step S1101: YES), the transaction management device 20 integrates the cart information of the master mobile terminal 30a and the cart information of the slave mobile terminal 30b (step S1102). Specifically, the transaction management device 20 stores the product information scanned by the slave mobile terminal 30b in the cart information of the master mobile terminal 30a.

Then, the transaction management device 20 transmits a registration completion notification to the master mobile terminal 30a and the slave mobile terminal 30b (step S1103). Then, the transaction management device 20 determines whether or not the maximum amount information has been received from the master mobile terminal 30a (step S1104). If the maximum amount information is not received (step S1104: NO), the transaction management device 20 proceeds to step S1106. On the other hand, when the maximum amount information is received (step S1104: YES), the transaction management device 20 stores the maximum amount information 803 in the cart information 800 (see FIG. 8) (step S1105).

Further, the transaction management device 20 determines whether or not the product information has been received from the master mobile terminal 30a and the slave mobile terminal 30b (step S1106). If the product information is not received (step S1106: NO), the transaction management device 20 proceeds to step S1113. When the product information is received (step S1106: YES), the transaction management device 20 determines whether or not the product information is received from the slave mobile terminal 30b (step S1107).

When the product information is not received from the slave mobile terminal 30b (step S1107: NO), that is, when the product information is received from the master mobile terminal 30a, the transaction management device 20 proceeds to step S1110. On the other hand, when the product information is received from the slave mobile terminal 30b (step S1107: YES), the transaction management device 20 determines whether or not the upper limit amount is reached by registering the product information (step S1108). ).

If the upper limit amount is not reached (step S1108: NO), the transaction management device 20 proceeds to step S1110. On the other hand, when the upper limit amount is reached (step S1108: YES), the transaction management device 20 transmits the upper limit amount notification information for notifying the slave mobile terminal 30b of the warning about the upper limit amount (step S1109), and in step S1113. move on.

In step S1110, the transaction management device 20 determines whether or not the parent and child (master mobile terminal 30a and slave mobile terminal 30b) are requesting registration for the same product (step S1110). In step S1110, the transaction management device 20 refers to the cart information 800 and determines whether or not the product information requested to be registered this time is the product information already registered by the other mobile terminal 30.

When the request for registration of the same product is made (step S1110: YES), the transaction management device 20 provides the same product notification information for notifying a warning about the registration operation of the same product with the registered mobile terminal 30. , Is transmitted to the master mobile terminal 30a (step S1111), and the process proceeds to step S1113. On the other hand, if it is not a request for registration of the same product (step S1110: NO), the transaction management device 20 updates (stores) the registered product information in the cart information 800 (step S1112).

Then, the transaction management device 20 determines from the master mobile terminal 30a whether or not there is a registration request for the same product (step S1113). If there is no registration request for the same product (step S1113: NO), the transaction management device 20 proceeds to step S1115. On the other hand, when there is a request for registration of the same product (step S1113: YES), the transaction management device 20 registers the product information of the same product (step S1114). In step S1114, the transaction management device 20 updates the registered product information in the cart information 800 (addition of quantity, etc.).

Then, the transaction management device 20 determines whether or not there is a request for calculating the subtotal amount from the POS terminal 40 (step S1115). If there is no request to calculate the subtotal amount (step S1115: NO), the transaction management device 20 proceeds to step S1117. On the other hand, when there is a request to calculate the subtotal amount (step S1115: YES), the transaction management device 20 performs the subtotal amount calculation process (step S1116).

Then, the transaction management device 20 determines whether or not the completion notification indicating that the payment process has been completed has been received from the POS terminal 40 (step S1117). If the completion notification is not received (step S1117: NO), the transaction management device 20 ends a series of processes. On the other hand, when the transaction management device 20 receives the completion notification (step S1117: YES), the transaction management device 20 stores the transaction end date and time of the cart (not shown), and determines whether or not the parent-child interlocking mode is in progress (step S1118). ).

When not in the parent-child interlocking mode (step S1118: NO), the transaction management device 20 ends a series of processes. On the other hand, when the parent-child interlocking mode is in progress (step S1118: YES), the transaction management device 20 cancels the group (step S1119). Then, the transaction management device 20 transmits a cancellation notification indicating that the group has been canceled to the master mobile terminal 30a and the slave mobile terminal 30b (step S1120), and ends a series of processes.

(About an example of the screen displayed on the mobile terminal 30)
Next, an example of a screen displayed on the mobile terminal 30 in the shopping system 1 according to the present embodiment will be described with reference to FIGS. 12 to 15. FIG. 12 is an explanatory diagram showing an example of a screen of the mobile terminal 30 when performing group registration.

FIG. 12A shows the screen of the master mobile terminal 30a when a customer visits a store, activates the application, and performs group registration. As shown in FIG. 12A, the display 409 of the master mobile terminal 30a displays an imaging area 1201, a registered product display area 1202, a checkout button 1203, and a group registration selection area 1204. The imaging area 1201 is an area in which a barcode attached to a product can be imaged by the function of the camera 407 of the mobile terminal 30. The registered product display area 1202 is an area showing the total number of points and the total amount of various registered products. The checkout button 1203 is a button that receives an instruction to start payment.

The group registration selection area 1204 is an area that accepts the start of group registration. The group registration selection area 1204 includes a group registration button 1210, a code display button 1211, and a code reading button 1212. When the user presses the group registration button 1210 on a predetermined menu screen (not shown), a selection button including a code display button 1211 and a code reading button 1212 is displayed. The group registration button 1210 may be displayed in the imaging area 1201.

The code display button 1211 is a button that receives an instruction for displaying the registration two-dimensional code 1221 (see FIG. 12B). The code reading button 1212 is a button that receives an instruction for reading the registration two-dimensional code 1221. In FIG. 12A, when the code display button 1211 is selected by the user, the screen shown in FIG. 12B is displayed.

FIG. 12B shows the screen of the master mobile terminal 30a when the registration two-dimensional code 1221 is displayed. As shown in FIG. 12B, the display 409 of the master mobile terminal 30a displays a guidance display area 1220, a two-dimensional registration code 1221, and a shopping button 1222. In the guidance display area 1220, it is displayed that the slave mobile terminal 30b for group registration is urged to scan the registration two-dimensional code 1221. The registration two-dimensional code 1221 encodes the cart identification information of the master mobile terminal 30a and the information for requesting the transaction management device 20 to start the parent-child interlocking mode. The shopping button 1222 is a button that accepts the transition to the screen for registering product information (the screen during shopping).

When the registration two-dimensional code 1221 is read by the slave mobile terminal 30b and the registration completion notification is received from the transaction management device 20, the master mobile terminal 30a starts the parent-child interlocking mode. When the master mobile terminal 30a starts the parent-child interlocking mode, the master mobile terminal 30a notifies the display 409 that the parent-child interlocking mode is started. The screen during shopping in the parent-child interlocking mode of the master mobile terminal 30a will be described later with reference to FIG. 13A and the like.

FIG. 12C shows a screen of the slave mobile terminal 30b when a customer possessing the slave mobile terminal 30b visits the store together with the customer possessing the master mobile terminal 30a, activates the application, and performs group registration. Is shown. The screen shown in FIG. 12 (C) differs from FIG. 12 (A) in that the code reading button 1212 is selected. In FIG. 12C, when the code reading button 1212 is selected by the user, the screen shown in FIG. 12D is displayed.

FIG. 12D shows a screen for reading the registration two-dimensional code 1221 displayed on the slave mobile terminal 30b. As shown in FIG. 12D, the display 409 (screen) of the master mobile terminal 30a is displayed in the imaging region 1201 of the slave mobile terminal 30b. The slave mobile terminal 30b reads the registration two-dimensional code 1221 displayed on the master mobile terminal 30a by the function of the camera 407. When the slave mobile terminal 30b reads the registration two-dimensional code 1221, it transmits the cart identification information to the transaction management device 20 and requests the start of the parent-child interlocking mode.

When the slave mobile terminal 30b receives the registration completion notification from the transaction management device 20, the slave mobile terminal 30b starts the parent-child interlocking mode. When starting the parent-child interlocking mode, the slave mobile terminal 30b notifies the display 409 that the parent-child interlocking mode is started. The screen during shopping in the parent-child interlocking mode of the slave mobile terminal 30b will be described later with reference to FIG. 13 (C) and the like.

(About the screen during shopping in parent-child interlocking mode)
FIG. 13 is an explanatory diagram showing an example of a screen during shopping displayed on the mobile terminal 30. FIG. 13A shows a shopping screen displayed on the master mobile terminal 30a. As shown in FIG. 13A, the display 409 of the master mobile terminal 30a has an imaging area 1201, a registered product display area 1202, a checkout button 1203, a registered product display area 1301, and a mode content suggestion display 1302. Is displayed.

In the registered product display area 1202, it is displayed that 18 products are registered and that the total amount is 2630 yen. In the registered product display area 1301, the number and price of registered products are displayed.

The mode content suggestion display 1302 indicates that the parent-child interlocking mode is in progress. Further, the mode content suggestion display 1302 indicates the number of master mobile terminals 30a and the number of slave mobile terminals 30b registered in the group. Specifically, the mode content suggestion display 1302 indicates the type (master mobile terminal 30a or slave mobile terminal 30b) and the number of mobile terminals 30 in the parent-child interlocking mode. More specifically, "M1 / M1S5" is displayed on the mode content suggestion display 1302. Of the "M1 / M1S5", the leading "M1" indicates that this unit is the first master mobile terminal 30a. Of the "M1 / M1S5", the subsequent "M1S5" indicates the type and number of all mobile terminals 30 registered in the group. Specifically, one master mobile terminal 30a is registered. , Indicates that five slave mobile terminals 30b are registered.

When the checkout button 1203 is pressed in FIG. 13 (A), the screen transitions to the screen shown in FIG. 13 (B).

FIG. 13B shows a screen when the two-dimensional code 1321 for settlement is displayed on the master mobile terminal 30a. As shown in FIG. 13B, the display 409 of the master mobile terminal 30a displays a guidance display area 1320, a two-dimensional code 1321 for settlement, and a shopping button 1322. In the guidance display area 1320, it is displayed that the POS terminal 40 is to read the two-dimensional code 1321 for settlement. The settlement two-dimensional code 1321 encodes the cart identification information of the master mobile terminal 30a and the information for causing the transaction management device 20 to request the settlement start. The shopping button 1322 is a button that accepts the transition to the screen for emptying the product (the screen during shopping).

When the two-dimensional code 1321 for settlement is read by the POS terminal 40 and the settlement is completed, the parent-child interlocking mode ends, that is, the group registration is canceled. When the parent-child interlocking mode ends, the master mobile terminal 30a hides the mode content suggestion display 1302.

FIG. 13C shows a shopping screen displayed on the slave mobile terminal 30b. The screen shown in FIG. 13 (C) is different from the screen shown in FIG. 13 (A) in that the checkout button 1203 is not displayed and the mode content suggestion display 1332 is displayed.

The checkout button 1203 is not displayed on the shopping screen of the slave mobile terminal 30b. Further, "S2 / M1S5" is displayed on the mode content suggestion display 1332. Of the "S2 / M1S5", the leading "S2" indicates that this unit is the second slave mobile terminal 30b. Of the "S2 / M1S5", the subsequent "M1S5" indicates the type and number of all mobile terminals 30 registered in the group. Specifically, one master mobile terminal 30a is registered. , Indicates that five slave mobile terminals 30b are registered.

In FIG. 13C, when the checkout button 1203 (see FIG. 13A) displayed on the master mobile terminal 30a is pressed, the slave mobile terminal 30b transitions to the screen shown in FIG. 13D. To do.

FIG. 13D shows the screen of the slave mobile terminal 30b when the settlement is started in the master mobile terminal 30a. As shown in FIG. 13D, the guidance display area 1340 is displayed on the display 409 of the slave mobile terminal 30b. In the guidance display area 1340, it is displayed that the master mobile terminal 30a has started the settlement, so that it is impossible to register the product after that. When the settlement is started in the master mobile terminal 30a, the imaging area 1201 is not displayed, and the product cannot be registered.

When the settlement two-dimensional code 1321 displayed on the master mobile terminal 30a is read by the POS terminal 40 and the settlement is completed, the parent-child interlocking mode ends, that is, the group registration is canceled. When the parent-child interlocking mode ends, the slave mobile terminal 30b hides the mode content suggestion display 1332.

(About the notification screen during shopping in parent-child interlocking mode)
FIG. 14 is an explanatory diagram showing an example of a notification screen during shopping displayed on the mobile terminal 30. FIG. 14A shows a notification screen when the master mobile terminal 30a reads the same product (OO yogurt) as the already registered product. As shown in FIG. 14A, the warning area 1401 and the selection buttons 1402a and 1402b are displayed on the display 409 of the master mobile terminal 30a. In the warning area 1401, a warning is displayed to the effect that the same product information as the read product information has already been registered by the slave mobile terminal 30b.

In FIG. 14A, when the selection button 1402b indicating “No” is pressed, the product information read by the master mobile terminal 30a is not registered. On the other hand, when the selection button 1402a indicating "Yes" is pressed, the screen transitions to the screen shown in FIG. 14B, and the product information read by the master mobile terminal 30a is registered.

FIG. 14B shows a screen in which the same product as the already registered product is registered. In the registered product display area 1301, two "○○ yogurts" are registered and the prices for the two are displayed.

FIG. 14C shows a notification screen when the slave mobile terminal 30b reads the same product as the already registered product. As shown in FIG. 14C, the warning area 1411 and the selection buttons 1412a and 1412b are displayed on the display 409 of the slave mobile terminal 30b. In the warning area 1411, a warning indicating that the same product information as the read product information has already been registered by the master mobile terminal 30a is displayed.

In FIG. 14C, when the selection button 1412b indicating “No” is pressed, the product information read by the slave mobile terminal 30b is not registered. On the other hand, when the selection button 1412a indicating "Yes" is pressed, the screen shown in FIG. 14D is displayed on the master mobile terminal 30a.

FIG. 14D shows a screen displayed on the master mobile terminal 30a when the slave mobile terminal 30b requests registration of the same product. As shown in FIG. 14D, the display 409 of the master mobile terminal 30a displays the request content display area 1421 and the selection buttons 1422a and 1422b. In the request content display area 1421, it is displayed that the slave mobile terminal 30b has requested the registration of the same product as the already registered product.

In FIG. 14D, when the selection button 1422b indicating “No” is pressed, the same product read by the slave mobile terminal 30b is not registered. On the other hand, when the selection button 1422a indicating "Yes" is pressed, the same product (OO yogurt) read by the slave mobile terminal 30b is registered.

As described above, according to the above-described embodiment, the master mobile terminal 30a outputs the location information (cart identification information) indicating the storage destination assigned to the master mobile terminal 30a so that the slave mobile terminal 30b can input the location information (cart identification information). I tried to do it. Therefore, the slave mobile terminal 30b can transmit the product information read by the slave mobile terminal 30b to the storage destination identified by the cart identification information assigned to the master mobile terminal 30a. As a result, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination (cart information). Therefore, the product can be registered efficiently.

(Modified example of the embodiment)
A modified example of the embodiment will be described below. In the following modified examples, the same contents as those described in the above-described embodiment are designated by the same reference numerals, and the description thereof will be omitted.

(Modification example 1)
The modified example 1 will be described below. In the above-described embodiment, the configuration in which the registration of the product is prohibited in the slave mobile terminal 30b when the upper limit amount is reached has been described. In the first modification, in addition to or in place of such a configuration, a configuration that enables registration of a product even when the maximum amount of money is reached will be described. Further, although the details will be described later, in the modification 1, the registrant who registered each product is displayed.

(When the maximum amount is reached)
First, the case where the maximum amount of money is reached will be described.
FIG. 15 is an explanatory diagram showing an example of a notification screen displayed on the mobile terminal 30 when the maximum amount of money is reached. FIG. 15A shows a notification screen displayed on the slave mobile terminal 30b when the maximum amount of money is reached by the registration of the product this time. As shown in FIG. 15A, the warning area 1501 and the selection buttons 1502a and 1502b are displayed on the display 409 of the slave mobile terminal 30b. In the warning area 1501, a warning that the maximum amount of money has been reached and the read product information cannot be registered is displayed.

In FIG. 15A, when the selection button 1502a indicating “close” is pressed, the screen returns to the screen where the product information can be registered without registering the read product information. On the other hand, when the selection button 1502a indicating "change request" is pressed, the screen transitions to the screen shown in FIG. 15B.

FIG. 15B is a screen displayed on the slave mobile terminal 30b showing a request for changing the maximum amount of money. As shown in FIG. 15B, the change request area 1511 and the selection buttons 1512a and 1512b are displayed on the display 409 of the slave mobile terminal 30b. In the change request area 1511, it is displayed that a request for changing the maximum amount is made.

In FIG. 15B, when the selection button 1502b indicating “No” is pressed, the screen returns to the screen where the product information can be registered without registering the read product information. On the other hand, when the selection button 1502a indicating "Yes" is pressed, the master mobile terminal 30a is requested to change the upper limit amount via the transaction management device 20.

FIG. 15C shows a screen displayed on the master mobile terminal 30a when the slave mobile terminal 30b requests to change the upper limit gold face. As shown in FIG. 15C, the request content display area 1521 and the selection buttons 1522a and 1522b are displayed on the display 409 of the master mobile terminal 30a. In the request content display area 1521, it is displayed that the slave mobile terminal 30b has requested to change the upper limit amount.

In FIG. 15C, when the selection button 1522b indicating "No" is pressed, the change in the maximum amount is not accepted. In this case, the master mobile terminal 30a transmits information indicating that the change in the upper limit amount cannot be accepted to the slave mobile terminal 30b via the transaction management device 20. Upon receiving the information, the slave mobile terminal 30b displays that the change in the maximum amount cannot be accepted. On the other hand, when the selection button 1522a indicating "Yes" is pressed, the screen transitions to the screen shown in FIG. 15 (D).

FIG. 15D shows a screen for changing the maximum amount of money displayed on the master mobile terminal 30a. As shown in FIG. 15D, the guidance display area 1531 and the amount selection button 1532 are displayed on the display 409 of the master mobile terminal 30a. In the guidance display area 1531, the effect of prompting the change of the upper limit amount and the currently set upper limit amount are displayed. The amount selection button 1532 can display a plurality of amounts so as to be selectable according to the scroll operation of the user, and accepts one amount from the user. When the user operates the amount selection button 1532 and the amount selection button 1532 accepts one amount, the upper limit amount is changed to the accepted amount.

When the upper limit amount is changed, the slave mobile terminal 30b notifies that fact. Further, in the slave mobile terminal 30b, product information can be registered within the range of the changed upper limit amount.

In FIG. 15B, only the request for changing the maximum amount is made, but the desired amount of change may be accepted and the request for change to the desired amount may be made. In this case, the master mobile terminal 30a shown in FIG. 15C may display the desired amount of change and notify whether or not the change to the desired amount is permitted.

According to the first modification, the upper limit amount of money in the slave mobile terminal 30b can be appropriately changed according to the shopping situation. Further, the upper limit amount can be changed even if the user of the slave mobile terminal 30b does not go to the location of the user of the master mobile terminal 30a. Therefore, the convenience of the shopping system 1 can be improved.

(About displaying registrants)
Next, in the modification 1, the registrant who registered each product is displayed, and this point will be described. As shown in FIGS. 15A and 15B, in the registered product display area 1301 of the slave mobile terminal 30b, in addition to the number and price of the registered products, the registrant displays 1550a to 1550c are displayed. Further, as shown in FIGS. 15C and 15D, the registered product display area 1301 of the master mobile terminal 30a also displays the number and price of the registered products, as well as the registrant displays 1550a to 1550c. ..

Specifically, "S5" of the registrant display 1550a indicates that the product is registered by the slave mobile terminal 30b registered in the fifth unit. “M1” of the registrant display 1550b indicates that the product is registered by the master mobile terminal 30a. “Mr. XX” in the registrant display 1550c indicates that the product is registered by the slave mobile terminal 30b of “Mr. XX”. In the slave mobile terminal 30b, the name of "Mr. XX" is registered corresponding to the identification information of the slave mobile terminal 30b. In this way, for the member whose name is registered, the name may be displayed instead of the number of the mobile terminal 30.

According to the first modification, by displaying the registrant, each member can easily grasp who is trying to purchase what. Therefore, the convenience of the shopping system 1 can be improved.

(Modification 2)
The second modification will be described below. In the above-described embodiment, the configuration in which the master mobile terminal 30a displays the two-dimensional code for registration and the slave mobile terminal 30b reads the two-dimensional code for registration to perform group registration has been described. In the second modification, in addition to or in place of such a configuration, the master mobile terminal 30a does not display the two-dimensional code for registration, and group registration (location with another mobile terminal 30). A configuration for sharing information) will be described.

FIG. 16 is an explanatory diagram showing an example of a screen for performing group registration displayed on the mobile terminal 30 according to the second modification of the embodiment. FIG. 16A shows a screen of the mobile terminal 30 when performing group registration. In FIG. 16A, the group registration selection area 1204 includes the group history button 1601. The group history button 1601 is a button that receives an instruction for displaying the history of members who have registered as a group in the past.

Here, the transaction management device 20 manages the group history for each user. The group history is a history of members registered in the past by the user of the mobile terminal 30. For example, the transaction management device 20 stores the number of times the group is registered, the date and time when the group is registered, and the type (master or slave) when the group is registered for each member registered in the group. For example, the transaction management device 20 may add a priority to each member and store the group history. Specifically, the transaction management device 20 stores the group history with high priority for the members who have recently registered as a group, the members who have become masters, and the members who have registered many times as a group. May be good.

In FIG. 16A, when the group history button 1601 is selected by the user, the mobile terminal 30 requests the transaction management device 20 to transmit the group history, and receives the group history from the transaction management device 20.

FIG. 16B is a screen showing the history of members who have registered as a group in the past. As shown in FIG. 16B, the display 409 of the mobile terminal 30 displays a group selection area 1610 and a guidance display area 1611. Members who perform group registration are displayed in the group selection area 1610 so that they can be selected. Each displayed member may be displayed in an order considering the latest history and the above-mentioned priority.

The members of Nos. 1 to 3 in FIG. 16B show the members who have started this application and have confirmed their entry into the store. The members of No. 4 indicate the members who have not been confirmed to enter the store, and indicate that they cannot be registered as the members this time.

Further, in the guidance display area 1611, a guidance prompting the selection of the member type is displayed. Specifically, the guidance display area 1611 prompts the selection of the member M of the master unit (master mobile terminal 30a), the member S of the slave unit (slave mobile terminal 30b), and the member F that does not belong to the group. Information is displayed.

The member M is a user of the master mobile terminal 30a. The master mobile terminal 30a can generate a two-dimensional code for settlement. The member S is a user of the slave mobile terminal 30b. The slave mobile terminal 30b cannot generate a two-dimensional code for settlement. Member F is a user of the mobile terminal 30 in the normal mode. The mobile terminal 30 in the normal mode can generate a two-dimensional code for settlement.

The mobile terminal 30 can display the name as shown in the figure when the member information of each member can be acquired. Further, since the display screen of the mobile terminal 30 is limited in size, it may not be possible to display the names of all the registered members. In this case, the icons of "S", "M", and "F" may be displayed, and when each of them is touched, the names of the members registered in each of them may be displayed.

When the user who operates the mobile terminal 30 selects the member type, the screen transitions to the screen shown in FIG. 16C. In FIG. 16C, the member type is not selected in advance, but the type according to the past history may be selected in advance. Further, in the modification 2, the group may have already been registered by another member. In this case, the member type may reflect the content already selected by the other member.

FIG. 16C shows a screen in which members registered as a group and their types are selected. As shown in FIG. 16 (C), NO. It is selected that the mobile terminal 30 of the member 1 becomes the master mobile terminal 30a and the mobile terminal 30 of the members Nos. 2 and 3 becomes the slave mobile terminal 30b. When the confirmation button 1620 is operated in FIG. 16C, the members registered in the group and their types are confirmed, and the screen transitions to the screen shown in FIG. 16D.

FIG. 16D shows a start screen of the parent-child interlocking mode displayed on the master mobile terminal 30a. As shown in FIG. 16D, the display 409 of the master mobile terminal 30a displays a mode content suggestion display 1630 and a shopping button 1631. "M1 / M1S2" is displayed on the mode content suggestion display 1630. Of the "M1 / M1S2", the leading "M1" indicates that this unit is the first master mobile terminal 30a. Of the "M1 / M1S2", the subsequent "M1S2" indicates the type and number of all mobile terminals 30 registered in the group. Specifically, one master mobile terminal 30a is registered. , Indicates that two slave mobile terminals 30b are registered.

The shopping button 1631 is a button that accepts the transition to the screen for registering product information (the screen during shopping). When the shopping button 1631 is pressed, the registration of product information in the parent-child interlocking mode is started.

According to the second modification, the group registration can be performed using the group history. Therefore, group registration can be performed simply by operating one mobile terminal 30 without operating each of the plurality of mobile terminals 30 (such as reading a registration two-dimensional code). Therefore, since group registration can be easily performed, the burden on the user related to group registration can be reduced.

(Modification example 3)
A modified example 3 will be described below. In the above-described embodiment, a configuration in which group registration is performed before registering product information has been described. In the third modification, in addition to or instead of such a configuration, a configuration in which the group registration is performed after the product information is registered in each mobile terminal 30 will be described.

Specifically, the transaction management device 20 stores cart information corresponding to each mobile terminal 30. Since the customer who owns each mobile terminal 30 has registered the product, the registered product information is stored in each cart information. Even when group registration is performed in this state, the master mobile terminal 30a displays the registration two-dimensional code when the group registration operation is accepted. The slave mobile terminal 30b reads the registration two-dimensional code displayed on the master mobile terminal 30a and requests the transaction management device 20 to register the group.

The transaction management device 20 may move the registered product information stored in the cart information of the slave mobile terminal 30b to the cart information of the master mobile terminal 30a. Further, the transaction management device 20 may associate the cart identification information corresponding to the slave mobile terminal 30b and the cart identification information corresponding to the master mobile terminal 30a as cart information for which the settlement is the same. In this way, even when the product is already registered in each mobile terminal 30, group registration can be performed.

According to the third modification, the registered product information can be integrated even after each of the plurality of mobile terminals 30 has registered the product information, and the settlement can also be performed collectively.

(Modification example 4)
The modified example 4 will be described below. In the above-described embodiment, when the master mobile terminal 30a starts the settlement, the slave mobile terminal 30b notifies that fact (FIG. 13 (D), etc.). In the modified example 4, when the master mobile terminal 30a starts the settlement in addition to or instead of such a configuration, the slave mobile terminal 30b is settled at the POS terminal 40 (cash register). The configuration for notifying the position of) will be described.

Specifically, when the POS terminal 40 reads the two-dimensional code 1321 for settlement displayed on the master mobile terminal 30a, the POS terminal 40 transmits the read cart identification information as well as the identification information of the own terminal to the transaction management device 20. .. The identification information of the POS terminal 40 is, for example, a registration number. The identification information of the POS terminal 40 may be location information. When the transaction management device 20 receives the identification information of the POS terminal 40, the transaction management device 20 transmits the identification information to the slave mobile terminal 30b. Upon receiving the identification information, the slave mobile terminal 30b notifies the user of the identification information (registration number) of the POS terminal 40. The POS terminal 40 may notify the user of the position of the POS terminal 40 in the store.

Further, when the transaction management device 20 transmits the identification information of the POS terminal 40 to the slave mobile terminal 30b, the transaction management device 20 transmits the information indicating that fact to the master mobile terminal 30a. Then, when the master mobile terminal 30a receives the information from the transaction management device 20, the master mobile terminal 30a notifies the slave mobile terminal 30b that the registration number has been notified. As a result, it is possible to encourage the user of the master mobile terminal 30a to join the user of the slave mobile terminal 30b.

According to the fourth modification, it is possible to support the user of the master mobile terminal 30a and the user of the slave mobile terminal 30b to join after the settlement. Therefore, it is possible to support more efficient shopping.

(Modification 5)
The modified example 5 will be described below. In the above-described embodiment, the configuration in which the master mobile terminal 30a displays the two-dimensional code for registration has been described. In the fifth modification, in addition to or in place of such a configuration, a configuration in which any of the mobile terminals 30 displays the two-dimensional code for registration will be described.

More specifically, in the modified example 5, neither the master mobile terminal 30a nor the slave mobile terminal 30b is determined at the stage where any of the mobile terminals 30 displays the two-dimensional code for registration. In the fifth modification, one mobile terminal 30 to which the cart identification information is assigned displays a two-dimensional code for registration in response to a user operation. Then, the other mobile terminal 30 reads the registration two-dimensional code displayed on one mobile terminal 30. Further, when the other mobile terminal 30 reads the two-dimensional code for registration, the other mobile terminal 30 requests the transaction management device 20 for group registration. The transaction management device 20 completes group registration by, for example, associating the cart information of one mobile terminal 30 with the cart information of another mobile terminal 30.

Then, when the group registration is completed, the user may be allowed to select which of the group-registered mobile terminals 30 is the master mobile terminal 30a or the slave mobile terminal 30b. .. The mobile terminal 30 that accepts the selection may be any mobile terminal 30.

According to the fifth modification, since the user can determine the master mobile terminal 30a and the slave mobile terminal 30b in the group registration, the convenience of the parent-child interlocking mode can be improved.

(Modification 6)
A modified example 6 will be described below. In the above-described embodiment, a configuration that can be freely performed by each mobile terminal 30 without any particular restriction is described for changing the quantity between the mobile terminals 30 and the like. In the sixth modification, a configuration in which restrictions are provided according to the type of the mobile terminal 30 (master mobile terminal 30a and slave mobile terminal 30b) for quantity change and the like will be described.

More specifically, in the sixth modification, the master mobile terminal 30a makes it possible to change or delete the quantity of the product information read by the master mobile terminal 30a and the slave mobile terminal 30b. On the other hand, the slave mobile terminal 30b makes it impossible to change or delete the quantity of the product information read by the master mobile terminal 30a. The slave mobile terminal 30b may also make it impossible to change or delete the quantity of the product information read by the slave mobile terminal 30b.

According to the modification 6, in the master mobile terminal 30a, the registration of the product in the slave mobile terminal 30b can be restricted. For example, when group registration is performed by a family with children, even if the child registers an unintended product, the registered contents can be easily changed on the master mobile terminal 30a. Therefore, the convenience of the shopping system 1 can be improved.

(Modification 7)
The modified example 7 will be described below. In the above-described embodiment, the product registered by the master mobile terminal 30a (hereinafter referred to as "master registered product") and the product registered by the slave mobile terminal 30b (hereinafter referred to as "slave registered product") are not distinguished. The display configuration has been described. In the modification example 7, a configuration in which the master registered product and the slave registered product are displayed separately will be described.

More specifically, in the modified example 7, the display mode of the product displayed on the master mobile terminal 30a and the slave mobile terminal 30b is different depending on whether the product is a master registered product or a slave registered product. May be good. For example, the display mode may be different between the master-registered product and the slave-registered product in terms of display color and size. Further, when a plurality of slave mobile terminals 30b are registered as a group, the slave registered products may also have different display modes for each registered slave mobile terminal 30b. For example, in the slave mobile terminal 30b, the slave registration product registered in the other slave mobile terminal 30b may be displayed more conspicuously than the slave registration product registered in the own terminal.

The display mode of the master registered product and the slave registered product may be different between the master mobile terminal 30a and the slave mobile terminal 30b. For example, the display mode may be such that the product registered by the other party is more conspicuous. Specifically, on the master mobile terminal 30a, the slave-registered product may be displayed more conspicuously than the master-registered product, and on the slave mobile terminal 30b, the master-registered product may be displayed more conspicuously than the slave-registered product. ..

According to the modification 7, in each mobile terminal 30, the user can easily grasp which mobile terminal 30 is registered. Therefore, the members of the group can shop efficiently.

(Modification 8)
The modified example 8 will be described below. In the modified example 8, an example in which the registrant is displayed on the screen displayed on the POS terminal 40 at the time of payment will be described. FIG. 17 is an explanatory diagram showing an example of a display screen at the time of settlement according to the modified example 8. The screen shown in FIG. 17 shows, for example, a screen when the POS terminal 40 reads a two-dimensional code displayed by the master mobile terminal 30a after receiving an accounting instruction by a customer's operation.

In FIG. 17, the purchase list 1700 of the purchased product is displayed on the customer side display unit 201. The purchase list 1700 includes a total number display 1701, a total score display 1702, a total price display 1703, a detailed display 1704 of each product, a purchase number display 1705 for each price range, and the like.

The total number display 1701 indicates the total number of members of the group who performed the product registration operation. The total score display 1702 indicates the scores of all the products registered by all the members of the group. The total price display 1703 indicates the total price of all the products registered by all the members of the group. The detailed display 1704 of each product displays the product name, the registrant of the product, the quantity, and the price. The number of purchased items display 1705 for each price range indicates the number of reserved products and the number of purchased items for each price range. In addition, a reception button may be displayed so that the number of reserved products and the number of purchased products for each price range can be displayed for each registrant. That is, for example, a reception button may be displayed that makes it possible to display who purchased how many items for the number of purchased items of 1000 yen or more.

Further, in FIG. 17, changes in product registration may be accepted. For example, a change button may be displayed next to each product name shown in the detailed display 1704 of each product. As a result, changes in quantity and cancellations can be accepted even at the time of payment, so that it is possible to suppress the purchase of duplicate products and unnecessary purchases.

Further, in FIG. 17, the checkout button 1710 is a button that accepts the customer to insert money and shift to the checkout screen for making payments with various cards. The registrant-specific button 1720 is a button that accepts the transition to a screen that allows the registered products to be browsed for each registrant. When the registrant-specific button 1720 is pressed, the screen transitions to, for example, the screen shown in FIG.

FIG. 18 is an explanatory diagram showing an example of a screen at the time of settlement displayed for each registrant. The screen shown in FIG. 18 shows a list of individual purchases of products registered by the fourth slave mobile terminal 30b (member “S4”). The personal purchase list 1800 includes a registrant display 1801, a personal purchase number display 1802, an individual total price display 1803, a detailed display 1804 for each product, a switch button 1805 for other members, and the like.

The registrant display 1801 indicates the member "S4" to be displayed. The number of personally purchased items 1802 indicates the ratio between the number of items purchased by "S4" and the number of items registered by all members. The personal total amount display 1803 indicates the ratio between the amount purchased by "S4" and the total amount of all members. In addition, various ratios may be expressed in%. The detailed display 1804 of each product displays the product name, the number of products, and the price of the products registered by the member "S4".

The switch button 1805 to another member is a button that accepts a transition to a screen indicating the individual purchase of the registered product for each member. Further, in FIG. 18, the hold / amount-specific button 1820 is a button that accepts the return to the screen of the purchase list 1700 shown in FIG.

According to the modification 8, each member can grasp who registered each product registered by each member at the time of settlement. In addition, since the number of participating members is displayed at the time of settlement, it is possible to easily grasp how many people have registered the transaction. Further, since the registrant of the product is displayed on the detailed display 1704 of each product, it is possible to easily grasp who purchased the product. Further, since the screen for each registrant can be displayed as shown in FIG. 18, it becomes possible to easily grasp the products registered for each registrant. Therefore, since the members can monitor each other and shop, it is possible to support sound shopping.

The appendix is disclosed below.
(Appendix 1)
A product sales data processing system provided with a storage means for storing registered product information in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
With
One of the plurality of mobile terminals is
A sharing means for sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A product sales data processing system characterized by being equipped with.

Specifically, in Appendix 1, the master mobile terminal 30a shares the location information (cart identification information) indicating the storage destination (cart information) assigned to the master mobile terminal 30a with the slave terminal device 30b. .. As a result, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination or a related storage destination. Therefore, the user can efficiently register the product, and the shopping can be performed efficiently.

(Appendix 2)
The product sales data processing system according to Appendix 1, wherein the sharing means outputs location information indicating a storage destination assigned to the one mobile terminal.

Specifically, in Appendix 2, the master mobile terminal 30a outputs the location information (cart identification information) indicating the storage destination (cart information) assigned to the master mobile terminal 30a so that the slave mobile terminal 30b can input it. I did. Therefore, the slave mobile terminal 30b can transmit the product information read by the slave mobile terminal 30b to the storage destination assigned to the master mobile terminal 30a. As a result, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination or a related storage destination. Therefore, the user can efficiently register the product, and the shopping can be performed efficiently.

(Appendix 3)
The other mobile terminal includes an input means for inputting the location information output by the one mobile terminal.
The transmission means of the other mobile terminal transmits the product information to the storage destination corresponding to the storage destination indicated by the location information input by the input means.
The product sales data processing system according to Appendix 2, wherein the product sales data processing system is characterized in that.

Specifically, in Appendix 3, the slave mobile terminal 30b transmits the product information to the storage destination corresponding to the storage destination indicated by the location information output by the master mobile terminal 30a. Therefore, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination or a related storage destination. As a result, the product can be registered efficiently.

(Appendix 4)
The output means of the one mobile terminal outputs the location information in a code and outputs the location information.
The input means of the other mobile terminal inputs the location information by reading the code.
The product sales data processing system according to Appendix 3, wherein the product sales data processing system is characterized in that.

Specifically, in Appendix 4, the master mobile terminal 30a displays the two-dimensional code for registration, and the slave mobile terminal 30b reads the two-dimensional code for registration to input the location information. As a result, the slave mobile terminal 30b can receive a simple operation from the user and request group registration. Therefore, the convenience of the shopping system 1 can be improved.

(Appendix 5)
When the location information is input by the input means, the product information stored in the storage destination assigned to the one mobile terminal and the product stored in the storage destination assigned to the other mobile terminal. A memory control means that associates and stores information,
The product sales data processing system according to Appendix 3 or 4, wherein the product sales data processing system is provided.

Specifically, in Appendix 5, when the location information is input to the slave mobile terminal 30b, the product information stored in the storage destination of the master mobile terminal 30a and the product information stored in the storage destination of the slave mobile terminal 30b are stored. Changed to associate with product information. As a result, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination or a related storage destination. Therefore, the product information can be registered efficiently.

(Appendix 6)
The one mobile terminal includes a settlement means for settlement of product information read by the reading means of the one mobile terminal and the other mobile terminal.
The memory control means cancels the association when the settlement is performed by the settlement means.
The product sales data processing system according to any one of Appendix 3 to 5, wherein the product sales data processing system is characterized in that.

Specifically, in Appendix 6, the group registration is canceled when the payment is made by the master mobile terminal 30a. As a result, it is possible to eliminate the need for an operation for canceling the group registration by the user. Therefore, it is possible to reduce the load related to the user's operation in the shopping system 1.

(Appendix 7)
The other mobile terminal does not have the payment means.
The product sales data processing system according to Appendix 6, wherein the product sales data processing system is characterized in that.

Specifically, in Appendix 7, the slave mobile terminal 30b is prevented from having a settlement function. Therefore, the settlement function can be left to the master mobile terminal 30a. Further, even a user with a small amount of money can register product information using the slave mobile terminal 30b. Therefore, shopping can be performed efficiently.

(Appendix 8)
The memory control means prohibits the registration of product information by the other mobile terminal when the settlement is started by the settlement means.
The product sales data processing system according to Appendix 6 or 7, characterized in that.

Specifically, in Appendix 8, when the settlement is started, the registration of the product information by the slave mobile terminal 30b is prohibited. As a result, it is possible to prevent the slave mobile terminal 30b from newly registering the product during the settlement. Therefore, it is possible to prevent the settlement from becoming complicated.

(Appendix 9)
When there is a request for registration of the same product information between the one mobile terminal and the other mobile terminal, at least one of the one mobile terminal and the other mobile terminal is carried. The terminal is a warning notification means that notifies a warning,
The product sales data processing system according to any one of Supplementary Provisions 3 to 8, further comprising.

Specifically, in Appendix 9, when the same product is registered in the master mobile terminal 30a and the slave mobile terminal 30b, a warning is notified. As a result, it is possible to prevent the same product from being mistakenly registered in duplicate.

(Appendix 10)
The one mobile terminal can allow or cancel the registration of the same product information.
The product sales data processing system according to Appendix 9, wherein the product sales data processing system is characterized in that.

Specifically, in Appendix 10, the master mobile terminal 30a can allow or cancel the registration of the same product information. As a result, even if the same product is registered, the same product can be registered or canceled under the responsibility of the customer who owns the master mobile terminal 30a.

(Appendix 11)
The product sales data processing system according to any one of Supplementary note 3 to 10, wherein the one mobile terminal includes a setting means for setting an upper limit amount of money that can be registered by the other mobile terminal.

Specifically, in Appendix 11, the master mobile terminal 30a sets the upper limit amount of money in the slave mobile terminal 30b. Thereby, for example, it is possible to prevent the slave mobile terminal 30b from registering a high-priced product that is not intended by the user of the master mobile terminal 30a. Therefore, proper shopping can be supported.

(Appendix 12)
The one mobile terminal and the other mobile terminal
The first mode in which product information is sent to the storage destination assigned to each mobile terminal and payment is made on each mobile terminal, and
A second mode in which the other mobile terminal transmits product information to a storage destination corresponding to the storage destination indicated by the location information, and
Mode execution means to switch and execute each mode,
The product sales data processing system according to any one of Supplementary note 3 to 11, wherein the product sales data processing system is provided.

Specifically, in Appendix 12, the master mobile terminal 30a and the slave mobile terminal 30b can execute the normal mode and the parent-child interlocking mode, respectively. As a result, the user can select either a normal mode or a parent-child interlocking mode. For example, even when a group such as a family visits a store, the normal mode allows the payment to be made separately without integrating the registered product information. Therefore, the convenience of the shopping system 1 can be improved.

(Appendix 13)
The one mobile terminal and the other mobile terminal
A mode notification means for notifying that the second mode is being executed by the mode execution means, and
The product sales data processing system according to Appendix 12, wherein the product sales data processing system is provided.

Specifically, in Appendix 13, the master mobile terminal 30a and the slave mobile terminal 30b are notified that they are in the parent-child interlocking mode. As a result, the customer can easily grasp which mode the customer is shopping in. Therefore, the customer can shop according to the mode.

(Appendix 14)
A plurality of other mobile terminals can transmit the product information to the storage destination corresponding to the storage destination indicated by the location information.
The mode notification means is the number of a plurality of other mobile terminals capable of transmitting product information to a storage destination corresponding to the storage destination indicated by the location information when the second mode is executed by the mode execution means. To inform,
The product sales data processing system according to Appendix 13.

Specifically, in Appendix 14, the master mobile terminal 30a and the slave mobile terminal 30b are made to notify the number of slave mobile terminals 30b registered in the group during the parent-child interlocking mode. Thereby, in each mobile terminal 30, the number of slave mobile terminals 30b can be grasped.

(Appendix 15)
A storage means for storing registered product information is provided in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
It is a product sales data processing method of a product sales data processing system equipped with
One of the plurality of mobile terminals is
A sharing step of sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A product sales data processing method characterized by including.

(Appendix 16)
A storage means for storing registered product information is provided in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
It is a program of the product sales data processing system equipped with
To the computer of one of the plurality of mobile terminals
A sharing means for sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A program characterized by functioning as.

Specifically, in Appendix 15 and Appendix 16, the master mobile terminal 30a shares the location information (cart identification information) indicating the storage destination (cart information) assigned to the master mobile terminal 30a with the slave mobile terminal 30b. I did. As a result, the master mobile terminal 30a and the slave mobile terminal 30b can store the product information in the same storage destination or a related storage destination. Therefore, the product information can be registered efficiently.

The program for realizing the shopping system 1, the mobile terminal 30, and the POS terminal 40 described above is recorded on a computer-readable recording medium, and the program is read into the computer system and executed. May be good. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. Furthermore, a "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, it shall include those that hold the program for a certain period of time. Further, the program may be transmitted from a computer system in which this program is stored in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting a program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Further, the above program may be for realizing a part of the above-mentioned functions. Further, it may be a so-called difference file (difference program) that can realize the above-mentioned function in combination with a program already recorded in the computer system.

1 ... Shopping system 10 ... Management device 20 ... Transaction management device 30 ... Mobile terminal 30a ... Master mobile terminal 30b ... Slave mobile terminal 40 ... POS terminal 401 ... CPU
402 ... ROM
403 ... RAM
407 ... Camera 409 ... Display

Claims (10)

A product sales data processing system provided with a storage means for storing registered product information in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
With
One of the plurality of mobile terminals is
A sharing means for sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A product sales data processing system characterized by being equipped with. The product sales data processing system according to claim 1, wherein the sharing means outputs location information indicating a storage destination assigned to the one mobile terminal. The other mobile terminal includes an input means for inputting the location information output by the one mobile terminal.
The transmission means of the other mobile terminal transmits the product information to the storage destination corresponding to the storage destination indicated by the location information input by the input means.
The product sales data processing system according to claim 2, wherein the product sales data processing system is characterized in that. When the location information is input by the input means, the product information stored in the storage destination assigned to the one mobile terminal and the product stored in the storage destination assigned to the other mobile terminal. A memory control means that associates and stores information,
The product sales data processing system according to claim 3, wherein the product sales data processing system is provided. The one mobile terminal includes a settlement means for settlement of product information read by the reading means of the one mobile terminal and the other mobile terminal.
The memory control means cancels the association when the settlement is performed by the settlement means.
The product sales data processing system according to claim 4, wherein the product sales data processing system is characterized in that. The memory control means prohibits the registration of product information by the other mobile terminal when the settlement is started by the settlement means.
The product sales data processing system according to claim 5. When there is a request for registration of the same product information between the one mobile terminal and the other mobile terminal, at least one of the one mobile terminal and the other mobile terminal is carried. The terminal is a warning notification means that notifies a warning,
The product sales data processing system according to any one of claims 3 to 6, further comprising. The product sales data processing according to any one of claims 3 to 7, wherein the one mobile terminal includes a setting means for setting an upper limit amount of money that can be registered by the other mobile terminal. system. A storage means for storing registered product information is provided in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
It is a product sales data processing method of a product sales data processing system equipped with
One of the plurality of mobile terminals is
A sharing step of sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A product sales data processing method characterized by including. A storage means for storing registered product information is provided in a predetermined storage destination assigned to each mobile terminal.
Each of the multiple mobile terminals
A reading means for reading product information and
A transmission means for transmitting the product information read by the reading means to the predetermined storage destination, and
It is a program of the product sales data processing system equipped with
To the computer of one of the plurality of mobile terminals
A sharing means for sharing the storage destination assigned to the one mobile terminal with another mobile terminal,
A program characterized by functioning as.

Images