Processing system, information processing device, store operation support method and program

Abstract

To provide an order processing system and sales support methods that take into consideration the convenience of users when using stores. [Solution] A processing system comprising a mobile terminal owned by a user of a store, an information processing device, and a ticket issuing device that reads information output from the mobile terminal and issues tickets, wherein the information processing device receives a user ID and order information placed by the user with the store from the mobile terminal, stores the received user ID and order information in order history information, generates CRM information for the user from the order history information, and stores the generated CRM information.

Description

Technical Field

[0001] The present invention relates to a processing system, an information processing apparatus, a store business support method, and a program.

Background Art

[0002] There is known a ticket vending machine installed in a store that can purchase a sorting ticket by paying the price of a product or service. For example, Patent Document 1 describes a ticket vending machine "including output means for outputting a store arrival notice for a pre-order specified by the specific information when the specific information for specifying the pre-order received by the reception means is stored in the storage means".

[0003] However, since the ticket vending machine described in Patent Document 1 does not consider the attributes of users who use the store, there is room for improvement in the convenience of users in using the store. In addition, regarding the utilization of information about users obtained by improving such convenience and orders placed by the users, no consideration has been given at all.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The present invention has been made from the above-described background, and discloses a processing system, an information processing apparatus, a store business support method, and a program that provide high convenience to users who use a store and utilize information about the users and orders placed by the users.

Means for Solving the Problems

[0006] According to one aspect of the present invention, a processing system is provided that includes a mobile terminal owned by a user of a store, an information processing device, and a ticket issuing device that reads information output from the mobile terminal and issues tickets, wherein the information processing device receives a user ID and order information ordered by the user for goods or services of the store from the mobile terminal, stores the received user ID and order information in order history information, generates CRM information of the user from the order history information, and stores the generated CRM information.

[0007] According to one aspect of the present invention, an information processing device is provided which is connected via a network to a mobile terminal owned by a user of a store and a ticketing device that reads information output from the mobile terminal and issues tickets, characterized in that it receives a user ID and order information placed by the user with the store from the mobile terminal, stores the received user ID and order information in order history information, generates CRM information of the user from the order history information, and stores the generated CRM information.

[0008] According to one aspect of the present invention, a method for supporting store operations in a processing system including a mobile terminal owned by a user of a store, an information processing device, and a ticketing device that reads information output from the mobile terminal and issues tickets is provided, characterized in that the method includes the steps of: the mobile terminal transmitting a user ID and order information placed by the user with the store; the information processing device receiving the user ID and the order information; the information processing device storing the user ID and the order information in order history information; the information processing device generating CRM information for the user from the order history information; and the information processing device storing the generated CRM information.

[0009] According to one aspect of the present invention, a program is provided that causes the information processing device to perform the following processes via a network: receiving a user ID and order information placed by the user with the store from the mobile terminal; storing the received user ID and order information in order history information; generating CRM information for the user from the order history information; and storing the generated CRM information. [Effects of the Invention]

[0010] According to the present invention, it becomes possible to use a processing system, information processing device, store operation support method, and program that utilize information about users and their orders, while providing high convenience to users of the store.

[0011] The effects described above are merely illustrative for the sake of explanation and are not limiting. In addition to, or in lieu of, any of the effects described in this invention or any effects that would be obvious to those skilled in the art may be achieved. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a schematic diagram showing an overview of the ticketing process according to the processing system 1 according to an embodiment of the present invention. [Figure 2] Figure 2 is a conceptual diagram illustrating the configuration of a processing system 1 according to an embodiment of the present invention. [Figure 3A] Figure 3A is a block diagram showing an example of the configuration of a mobile terminal 100 according to an embodiment of the present invention. [Figure 3B] Figure 3B is a block diagram showing an example of the configuration of a ticket issuing device 200 according to an embodiment of the present invention. [Figure 3C] Figure 3C is a block diagram showing an example of the configuration of an administrator server device 300 according to an embodiment of the present invention. [Figure 4A]FIG. 4A is a diagram conceptually showing an order information table stored in the administrator server device 300 according to the present invention. [Figure 4B] FIG. 4B is a diagram conceptually showing a store information table stored in the administrator server device 300 according to the present invention. [Figure 4C] FIG. 4C is a diagram conceptually showing a user information table stored in the administrator server device 300 according to the present invention. [Figure 5] FIG. 5 is a diagram showing a processing sequence of the processing system 1 according to an embodiment of the present invention. [Figure 6A] FIG. 6A is a diagram showing a processing flow executed in the mobile terminal 100 according to an embodiment of the present invention. [Figure 6B] FIG. 6B is a diagram showing a processing flow executed in the administrator server device 300 according to an embodiment of the present invention. [Figure 6C] FIG. 6C is a diagram showing a processing flow executed in the administrator server device 300 according to an embodiment of the present invention. [Figure 7A] FIG. 7A is a diagram showing an example of the mobile terminal 100 on which a web page for purchasing a product is displayed on a display. [Figure 7B] FIG. 7B is a diagram showing an example of the mobile terminal 100 on which a ticket issuing image based on recording medium information is displayed on a display. [Figure 8] FIG. 8 is a diagram conceptually showing a user information table stored in the administrator server device 300 according to the present invention. [Figure 9] FIG. 9 is a diagram conceptually showing a user information table stored in the administrator server device 300 according to the present invention. [Figure 10] FIG. 10 is a diagram conceptually showing a user information table stored in the administrator server device 300 according to the present invention. [Figure 11] FIG. 11 is a diagram showing a processing flow executed in the administrator server device 300 according to an embodiment of the present invention. [Figure 12]FIG. 12 is a diagram showing a processing flow executed in the administrator server device 300 according to an embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing a processing flow executed in the administrator server device 300 according to an embodiment of the present invention. [Figure 14] FIG. 14 is a diagram showing a part of a processing sequence of the processing system 1 according to an embodiment of the present invention. [Figure 15] FIG. 15 is a diagram showing a part of a processing sequence of the processing system 1 according to an embodiment of the present invention. [Figure 16A] FIG. 16A is a diagram showing an example of a sorting ticket issued by the ticket issuing device 200 when payment processing is executed. [Figure 16B] FIG. 16B is a diagram showing an example of a sorting ticket issued by the ticket issuing device 200 when payment processing is executed. [Figure 16C] FIG. 16C is a diagram showing an example of a sorting ticket issued by the ticket issuing device 200 when payment processing is executed.

Mode for Carrying Out the Invention

[0013] Embodiments of the present invention will be described with reference to the accompanying drawings. In the drawings, common components are denoted by the same reference numerals.

[0014] <First Embodiment> 1. Outline of the processing system 1 according to the present invention The processing system according to the present invention is, for example, a system that issues sorting tickets based on order information ordered by a user operating a mobile terminal. In particular, the processing system in the first embodiment is preferably used in that it can be used in combination, for example, with the issuance of sorting tickets at a ticket vending machine and the issuance of sorting tickets based on order information ordered by a user operating a mobile terminal.

[0015] Figure 1 is a schematic diagram illustrating the outline of the ticketing process according to processing system 1 according to an embodiment of the present invention. Specifically, Figure 1 shows a series of schematic steps from when a user orders goods at a store until a queue ticket is handed to the store operator. According to Figure 1, the user lines up at the end of the queue extending from the ticket vending machine. Next, the user orders goods or services at the store by operating a mobile device owned by the user. The user is provided with ticketing information from an administrator server device managed by the administrator of processing system 1. This ticketing information is displayed, for example, on the display of the mobile device. When the user is at the front of the queue (i.e., the position closest to the ticket vending machine in the queue), the user has the ticketing device read the ticketing information and obtains a queue ticket issued by the device. The user then hands the obtained queue ticket to the store operator and receives the goods. Note that if the ticketing information is sent to the user in advance by email or other means and the user prints the information, the same process can be performed by reading the printed ticketing information.

[0016] In this invention, the processing system 1 includes, as an example, a mobile terminal (100) operated by a user, a ticket issuing device (200) that issues numbered tickets when it obtains ticketing information from the mobile terminal, and a ticket vending machine (400) that issues numbered tickets when operated by a customer other than the user. The present invention will mainly describe the case in which the mobile terminal operated by the user functions as a processing device. However, the processing device in this invention can be any device capable of issuing numbered tickets as described above, and naturally, any other terminal device other than the mobile terminal, the server device included in the processing system 1 (described later), and any other terminal device or server device, or any combination thereof, can preferably function as a processing device. In other words, in this invention, the names given to each device are merely used to distinguish them from each other, and other names may be used depending on the function of each device.

[0017] Furthermore, in this invention, "store" simply means a place where goods or services are provided. Specific examples of "stores" include, but are not limited to, restaurants or massage parlors operating in a room of a commercial facility or a detached building, temporary stalls operating outdoors, and mobile sales vehicles that provide goods to customers for takeaway.

[0018] Furthermore, in this invention, "ticket vending machine" simply means a device that provides customers with numbered tickets by allowing them to operate it upon entering a store. Specific examples of "ticket vending machines" include, but are not limited to, a food ticket vending machine that issues a numbered ticket made of paper or resin when a customer inserts cash and presses a button corresponding to the product, and a reception device that issues a numbered ticket with a serial number printed on it when a customer presses a button corresponding to the service they request. Moreover, a "ticket vending machine" may accept not only cash, but also, for example, a so-called credit card that advances the customer's payment, or so-called electronic money that can process payments when a magnetic medium is brought into close proximity.

[0019] Furthermore, in this invention, "user" simply means a customer who visits or is likely to visit a store. Similarly, "customer" as mentioned above simply means a person who visits a store. In other words, a specific "user" could be a person who visits a store and orders goods or services, a person who is planning to order goods or services, or a person who is likely to visit a store, but is not limited to these. Also, in this invention, "acquisition" simply means a means for temporarily or long-term storage of an object. In other words, "acquisition" could include, but is not limited to, means for generating, receiving, and inputting information or other objects.

[0020] Furthermore, even if the present invention includes descriptions such as "first" or "second," it does not mean that it is limited to only those two elements. Naturally, it may also include "third," "fourth," and more elements.

[0021] 2. Configuration of Processing System 1 Figure 2 is a conceptual diagram schematically showing the configuration of a processing system 1 according to an embodiment of the present invention. According to Figure 2, a mobile terminal 100 operated by a user who orders the desired products, a ticket issuing device 200 that issues numbered tickets, and an administrator server device 300 that manages information related to the processing system 1 are connected to each other so as to be able to communicate via a network. This network is composed of wireless, wired, or a combination thereof. The processing system 1 also includes a ticket vending machine 400. The ticket vending machine 400 is a so-called unmanned vending machine in which products can be selected by inserting, for example, cash. This ticket vending machine 400 is installed, for example, near the entrance of a store, and issues numbered tickets to users when operated by a user who has arrived at the store. In the example in Figure 2, only one unit each of the mobile terminal 100, ticket issuing device 200, and ticket vending machine 400 is shown, but the processing system can of course include two or more of each of these devices. Also, although the administrator server device 300 is shown as a single unit, it is possible to distribute the components and processing of each server device to multiple server devices or cloud server devices.

[0022] 3. Configuration of the mobile terminal 100 Figure 3A is a block diagram showing an example of the configuration of a mobile terminal 100 according to an embodiment of the present invention. The mobile terminal 100 does not need to have all of the components shown in Figure 3A; it is possible to omit some components or to add other components.

[0023] The mobile terminal 100 is typically a wireless communication terminal device such as a smartphone, but is not limited to such devices. For example, any device capable of executing the program according to the present invention can be suitably applied as a terminal device, such as a feature phone, tablet terminal, PDA, laptop computer, desktop computer, portable game console, or home game console, and it is even more preferable if the terminal device is portable. Furthermore, the mobile terminal 100 in the processing system 1 may include multiple terminal devices, but each terminal device does not need to be of the same type; they may be different types of terminal devices.

[0024] According to Figure 3A, the mobile terminal 100 includes an output interface 111, a processor 112, memory 113 including RAM, ROM, or non-volatile memory (or SSD in some cases), a communication interface 114 including a communication processing circuit and an antenna, and an input interface 115 including a touch sensor and hard keys. These components are electrically connected to each other via control lines and data lines.

[0025] The output interface 111 functions as an output unit that outputs images captured by the camera included in the input interface 115, or various displays output by executing the program according to the present invention, to devices such as displays and printers, in accordance with instructions from the processor 112. Such displays are composed of, for example, liquid crystal displays, organic EL displays, or electronic paper.

[0026] The processor 112 consists of a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 113. Specifically, the processor 112 reads and executes programs for running the application according to the present invention and programs for running the OS from the memory 113. In the present invention, the processor 112 executes each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.). The processor 112 may consist of a single CPU, or it may be composed of a combination of multiple CPUs and GPUs.

[0027] Memory 113 includes main memory such as ROM, RAM, and non-volatile memory, and auxiliary storage such as HDD and SSD, and functions as a storage unit. ROM stores instruction commands for executing the application and OS according to the present invention as programs. RAM is used for writing and reading data while the program stored in ROM is being processed by the processor 112. Non-volatile memory is memory in which data is written and read by the execution of the program, and the data written therein is preserved even after the execution of the program has finished. In the present invention, memory 113 particularly stores programs that execute each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.).

[0028] The communication interface 114 functions as a communication unit that sends and receives information to and from a remotely installed administrator server device 300 via a communication processing circuit and an antenna. The communication processing circuit processes information such as programs and various other information used in the processing system 1 to send and receive information from the administrator server device 300 as processing progresses. In this invention, the mobile terminal 100 sends an order request, described later, to the administrator server device 300 and receives an order response, etc., to the order request from the administrator server device 300.

[0029] The communication processing circuit processes data based on broadband wireless communication methods such as 5G and LPWA, but it can also process data based on narrowband wireless communication methods such as Wi-Fi (as represented by IEEE 802.11), infrared communication, and Bluetooth®, as well as contactless wireless communication methods. Furthermore, wired communication can be used in addition to or instead of wireless communication.

[0030] The input interface 115 consists of a touch panel, hard keys, a camera, a microphone, etc., and functions as an input unit that receives instruction inputs related to the execution of the program according to the present invention, as well as operation inputs for registering various information. The touch panel is arranged to cover the output interface 111 and transmits position coordinate information corresponding to image data output from the output interface 111 to the display to the processor 112. Known touch panel methods such as resistive touch, capacitive coupling, and ultrasonic surface acoustic wave touch can be used. In the present invention, the touch panel detects swipe and tap operations on each icon, etc., displayed on the output interface 111 by an indicator. In the present invention, an input interface 115 provided in the mobile terminal 100 is used, but it is also possible to use an input interface 115 that is wirelessly or wired connected to a main unit equipped with a processor 112, etc., such as a mouse. The camera and microphone included in the input interface 115 are devices capable of detecting external images and sounds. This camera and microphone may be built into the mobile terminal 100, or they may be external devices that are wirelessly or wired connected for communication.

[0031] Although not shown in the diagram, the mobile terminal 100 is equipped with various sensors. For example, the GPS sensor acquires the location information of the mobile terminal 100. This acquired location information is used for processing performed on the mobile terminal 100, or it is transmitted to an external device via the communication interface 114.

[0032] 4. Configuration of the ticket issuing device 200 Figure 3B is a block diagram showing an example of the configuration of a ticket issuing device 200 according to an embodiment of the present invention. The ticket issuing device 200 does not need to have all of the components shown in Figure 3B; it is possible to omit some components or add other components. The ticket issuing device 200 is installed, for example, near a ticket vending machine 400 installed in a store.

[0033] According to Figure 3B, the ticket issuing device 200 includes an output interface 211, a processor 212, a memory 213 including RAM, ROM, or non-volatile memory (or SSD in some cases), a communication interface 214 including a communication processing circuit and an antenna, and an input interface 215. These components are electrically connected to each other via control lines and data lines.

[0034] The output interface 211 functions as an output unit that outputs various information to a device such as a printer, which is output by executing a program according to the present invention in response to instructions from the processor 212. The printer is a device capable of printing on paper and issuing numbered tickets. The output interface 211 may be a printing press that consumes ink to print on paper, a so-called thermal printer that prints on thermal paper using heat, or a ticket dispenser that selectively ejects numbered tickets made of resin.

[0035] The processor 212 is composed of a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 213. Specifically, the processor 212 reads and executes programs from the memory 213 for running the application according to the present invention and programs for running the OS. In the present invention, the processor 212 stores programs that execute each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.). The processor 212 may be composed of a single CPU, or it may be composed of a combination of multiple CPUs and GPUs.

[0036] Memory 213 includes main memory such as ROM, RAM, and non-volatile memory, and auxiliary storage such as HDD and SSD, and functions as a storage unit. ROM stores instruction commands for executing the application and OS according to the present invention as programs. RAM is used for writing and reading data while the program stored in ROM is being processed by the processor 212. Non-volatile memory is memory in which data is written and read by the execution of the program, and the data written therein is preserved even after the execution of the program has finished. In the present invention, memory 213 particularly stores programs that execute each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.).

[0037] The communication interface 214 functions as a communication unit that sends and receives information to and from a remotely installed administrator server device 300 via a communication processing circuit and an antenna. The communication processing circuit processes information such as programs and various other information used in the processing system 1 to send and receive information from the administrator server device 300 as processing progresses. In this invention, the ticket issuing device 200 transmits the reading information described later to the administrator server device 300 and receives the order information described later from the administrator server device 300 as a response to the viewing request.

[0038] The communication processing circuit processes data based on wideband wireless communication methods such as 5G and LPWA, but it can also process data based on narrowband wireless communication methods such as Wi-Fi (as represented by IEEE 802.21), infrared communication, and Bluetooth®, as well as contactless wireless communication methods. Furthermore, wired communication can be used in addition to or instead of wireless communication.

[0039] The input interface 215 includes a barcode scanner and functions as an input unit that receives instruction inputs related to the execution of the program according to the present invention. The barcode scanner is a scanner capable of reading information recorded as a two-dimensional barcode, for example. In this invention, a barcode scanner is used as the input interface 215, but a camera may also be used, for example, as long as it can read information recorded as a two-dimensional barcode. Furthermore, in this invention, a two-dimensional barcode is used as the recording medium and the information recorded as a two-dimensional barcode is read, but if a magnetic medium is used as the recording medium, the information recorded on the magnetic medium may be acquired.

[0040] 5. Configuration of Administrator Server Device 300 Figure 3C is a block diagram showing an example configuration of an administrator server device 300 according to an embodiment of the present invention. The administrator server device 300 does not need to include all of the components shown in Figure 3C; it is possible to omit some components or add other components. Furthermore, the administrator server device 300 does not need to be housed in a single enclosure as shown in Figure 3C; it is possible to distribute each component and processing of the administrator server device 300 to multiple server devices or cloud server devices.

[0041] According to Figure 3C, the administrator server device 300 includes a processor 312 consisting of a CPU, RAM, ROM, and memory 313 including non-volatile memory and SSD, and a communication interface 314. These components are electrically connected to each other via control lines and data lines.

[0042] The processor 312 consists of a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 313. Specifically, the processor 312 reads and executes programs for running the application according to the present invention and programs for running the OS from the memory 313. In the present invention, the processor 312 executes each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.). The processor 312 may consist of a single CPU, or it may be configured by combining multiple CPUs and GPUs.

[0043] Memory 313 functions as a storage unit, comprising main memory such as ROM, RAM, and non-volatile memory, and auxiliary storage such as HDD and SSD. ROM stores instruction commands for executing the application and OS according to the present invention as programs. RAM is used for writing and reading data while the program stored in ROM is being processed by processor 312. Non-volatile memory is memory in which data is written and read by the execution of the program, and the data written therein is preserved even after the execution of the program has finished. In the present invention, memory 313 particularly stores programs that execute each of the processes described in the processing sequence of Figure 5 (details of the processes will be explained in Figure 5, etc.).

[0044] The communication interface 314 functions as a communication unit that transmits and receives information to and from a remotely installed mobile terminal 100 or ticketing device 200 via a communication processing circuit and an antenna. The communication processing circuit processes programs and various information used in the processing system 1 to transmit and receive information from the mobile terminal 100 or ticketing device 200 as processing progresses. In this invention, in particular, the communication interface 314 receives an order request, described later, from the administrator server device 300 and transmits an order response to the order request to the mobile terminal 100.

[0045] The communication processing circuit processes data based on broadband wireless communication methods such as 5G and LPWA, but it can also process data based on narrowband wireless communication methods such as Wi-Fi (as represented by IEEE 80311), infrared communication, and Bluetooth®, as well as contactless wireless communication methods. Furthermore, wired communication can be used in addition to or instead of wireless communication.

[0046] 6. Information stored in memory 213 (1) Figures 4A, 4B, and 4C are conceptual diagrams showing the order information table, store information table, and user information table stored in the administrator server device 300 according to the present invention, particularly the first embodiment.

[0047] According to Figure 4A, the order information table stores store ID information, user ID information, order information, recording medium information, and special offer information, etc., associated with the order ID information. "Order ID information" is information generated each time a new order is received as order information by the administrator server device 300 from the mobile terminal 100, and is unique information assigned to each order information, used to identify each order information. "Store ID information" is identification information pre-assigned to each store. "Store ID information" is generated when a store is registered in the processing system of the present invention. "User ID information" is identification information pre-assigned to each user. "User ID information" is generated when a user is registered in the processing system of the present invention. "Order information" is information that includes information identifying the goods or services that the user orders from the store. Specifically, "order information" includes information such as the name of the goods or services, the price of the goods or services, the date and time the goods or services were ordered, the quantity of goods or the time of service provision, and detailed requests regarding the goods or services. The "recording medium information" includes information that, when read by the ticketing device 200, allows the ticketing device 200 to obtain information including "order ID information". Specifically, the "recording medium information" is information for generating a two-dimensional barcode. That is, when the "recording medium information" is acquired by, for example, a mobile terminal 100, it is possible to generate image information of a two-dimensional barcode. Furthermore, by having the ticketing device 200 read the two-dimensional barcode thus generated, it is possible to allow the ticketing device 200 to obtain information including "order ID information". The "special offer information" includes information indicating special offers to the user, such as price reductions for goods or services, additional goods or services for goods or services. Although a two-dimensional barcode is given as an example of "recording medium information", it may also be a recording medium that records information using magnetism, or any medium that can record and read information.

[0048] According to Figure 4B, the store information table stores the store name, product information, inventory information, special offer information, payment information, and link information, etc., associated with the store ID information. "Store ID information" is, as described above, identification information that is pre-assigned to each store. "Store name information" is information that indicates the name of the store. "Product information" is information that indicates the products or services offered at the store. Specifically, "product information" includes the name, price, and type of the product, as well as the name, price, and type of the service. "Inventory information" includes information that indicates the number of products in stock (available quantity) at the store (available quantity information) and information that indicates the time period during which the service can be provided. "Special offer information" is, as described above, information that indicates preferential treatment for users, such as price reductions for products or services, additional products for products, or additional services for services. "Payment information" is information that indicates the recipient of the money to which the money for product purchases, etc., collected from the user on behalf of the store in the processing system 1 according to the present invention is transferred. Specifically, "transfer information" refers to the account number of a bank account set up with a financial institution. Note that "transfer information" may also refer to the account number of an account used to manage virtual currency, or the account number of an account used to accumulate points that are used in place of money when purchasing goods. "Link information" refers to the URL of the webpage for purchasing goods at each store.

[0049] According to Figure 4C, the user information table stores user information, held benefits information, and payment information, etc., associated with the user ID information. As mentioned above, "user ID information" is identification information pre-assigned to each user. "User information" is information that shows various information about the user. Specifically, "user information" includes information about the user's unique attributes such as the user's name, address, age, and gender. "Held benefits information" is information that shows the benefits information held by the user. "Payment information" is information used when the user pays for goods or services. Specifically, "payment information" is the account number of a bank account set up with a financial institution. Note that "payment information" may also be information that shows the account number of an account for managing virtual currency, an account for accumulating so-called points that are used in place of money when purchasing goods, or a so-called credit card registration number that advances the user's payment.

[0050] 7. Processing sequence (1) executed by processing system 1 Figure 5 is a diagram showing the processing sequence of the processing system 1 according to the present invention, particularly according to the first embodiment. Hereinafter, the process will be explained using the example of a store operator selling goods. According to Figure 5, first, the mobile terminal 100 sends an access request to the administrator server device 300 for the web page for purchasing goods at the store the user plans to visit, based on the user's operation (T11). The web page for purchasing goods is managed, for example, by the administrator server device 300. The administrator server device 300 sends an access response based on the access request received from the mobile terminal 100 (T12). Upon receiving the access response from the administrator server device 300, the mobile terminal 100 accesses the web page for purchasing goods, displays the web page on the display, and accepts the user's order operation for goods (S11).

[0051] When the mobile terminal 100 receives an order request from the user, it sends the order request to the administrator server device 300 (T13). The order request includes store ID information, user ID information, order information, and discount information. When the administrator server device 300 receives the order request from the mobile terminal 100, it performs accounting processing based on the order request (S12). Once the accounting processing is complete, it generates order ID information and recording medium information (ticketing information) (S13), and stores the generated order ID information and recording medium information, as well as the store ID information, user ID information, order information, and discount information included in the order request, in the order information table (S14). Subsequently, the administrator server device 300 sends the recording medium information to the mobile terminal 100 (T14). When the mobile terminal 100 receives the recording medium information, it displays a two-dimensional barcode on the display included in the output interface 111 based on the recording medium information (S15).

[0052] Subsequently, the ticketing device 200 reads the order ID information from the two-dimensional barcode displayed on the mobile terminal 100 using the barcode scanner included in the input interface 215 (S16). The ticketing device 200 transmits the read information, including the order ID information read from the two-dimensional barcode, to the administrator server device 300 (T15). Upon receiving the read information, the administrator server device 300 extracts the order information from the order information table based on the order ID information and transmits the order information to the ticketing device 200 (T16). Then, the ticketing device 200 issues a queue ticket based on the order information (S17). The user then hands the queue ticket to the operator. The operator, having received the queue ticket, provides the user with the product based on the order information.

[0053] Here, regarding the issuance of numbered tickets by S17, if multiple numbered tickets are issued as a result of purchasing multiple goods or services, it is possible to specify the order in which the numbered tickets are issued, for example, in ascending or descending order of the price of the goods or services. For example, if tickets are issued in ascending order of price, i.e., from lowest to highest price, the numbered tickets for the most expensive goods or services will be issued last. Since users are more aware of the most expensive goods or services, this prevents them from forgetting to take their issued numbered tickets. Furthermore, the number of numbered tickets to be issued at once and the current number of issued tickets may be printed on the numbered tickets. For example, "2 / 5" may be printed in the corner of the numbered ticket. This prevents users from forgetting to take their issued numbered tickets. Note that these processes may be performed by the ticketing device 200 after it receives the order information in T16, by referring to the order information to determine the order in which the numbered tickets are issued and printing the above information, or they may be included in the order information transmitted by the administrator server device 300 in T16.

[0054] Thus, for example, a user planning to visit a store can, before arriving at the store, operate the mobile terminal 100 to place an order for products (S11), complete the payment for the order (S12), and upon arrival at the store, have the two-dimensional barcode displayed on the mobile terminal 100 (S15) read by the ticket issuing device 200 installed in the store (S16) to receive a numbered ticket for the order (S17). Therefore, compared to a case where, for example, a user operates the ticket vending machine 400 to order products while other customers waiting to operate the ticket vending machine 400 are made to wait, the processing system 1 according to the present invention allows the user to calmly consider which products to order by operating the mobile terminal 100 before arriving at the store. Furthermore, by installing a ticket vending machine 400 in addition to the ticket issuing device 200 in the store, users can not only order products by operating the mobile terminal 100 as described above, but also by operating the ticket vending machine 400 after arriving at the store.

[0055] 8. Processing flow (1) executed by processing system 1 A. Processing flow executed on mobile terminal 100 The following describes in detail the processing flow performed in the mobile terminal 100 shown in Figure 6A. Figure 6A is a diagram showing the processing flow performed in the mobile terminal 100 according to the present invention, particularly according to the first embodiment. The following describes the processing according to the first embodiment of the present invention, using the example of a user visiting a ramen shop H1 that serves ramen as a product.

[0056] According to Figure 6A, first, the processor 112 of the mobile terminal 100 sends an access request to the product purchase web page of store H1 to the administrator server device 300 via the communication interface 114 (S101), and receives an access response from the administrator server device 300 via the communication interface 114 (S102). Based on the access response, the processor 112 of the mobile terminal 100 displays the product purchase web page on the display (S103).

[0057] Figure 7A shows an example of a mobile terminal 100 with a product purchase webpage displayed on its screen. The product purchase webpage displayed on the mobile terminal 100's screen includes a product description section 11, a quantity selection section 13, a detailed settings section 15, an additional settings section 17, and an order information transmission section 19. The product description section 11 is an item that shows a description of the product. For example, the product description section 11 includes the product name "J1 Ramen," a photo of the product, and a description of the product. The quantity selection section 13 is an operation section for the user to select the quantity of the product to order. For example, the quantity selection section 13 displays three icons for the product quantity: "Small Serving," "Regular Serving," and "Large Serving." The user can select one of the product quantities by tapping one of the icons on the screen. The detailed settings section 15 is an operation section for setting adjustments to the product. For example, the detailed settings section 15 displays icons indicating the noodle firmness, soup flavor richness, and amount of flavor oil for the ramen product. The user can select one of the respective items by tapping one of the icons on the screen. The additional settings unit 17 is an operation unit for setting up additional products that add value to the product. For example, the additional settings unit 17 displays multiple icons representing ramen toppings, and the user can select one or more toppings by tapping one or more icons on the display. The order information transmission unit 19 is an icon that the user taps when ordering, after completing the order and various settings.

[0058] The webpage for purchasing products displayed on the mobile device 100's screen, although not shown in the illustration, displays icons that allow users to take action to receive special offers based on special offer information. Specifically, the special offer information is information indicating that the user will receive special offers such as free toppings or a reduction in the total price of ordered products. The webpage for purchasing products displayed on the mobile device 100's screen is not limited to the above; it may also display so-called product recommendations and information on limited-time products to the user. Other types of special offer information may include reductions of a certain percentage or amount on specific products or services.

[0059] In this way, by ordering products based on a webpage for purchasing goods displayed on the screen of a mobile device 100, for example, before visiting a store, users can take their time to consider even complex orders. Furthermore, operators can create complex menus for users without having to consider how to display them in a menu booklet or similar format.

[0060] Returning to Figure 6A, when the order information transmission unit 19 is tapped via the display, the processor 112 of the mobile terminal 100 sends an order request containing order information to the administrator server device 300 via the communication interface 114 (S104), and receives an order response from the administrator server device 300 via the communication interface 114, containing recording medium information as ticketing information (S105). The processor 112 of the mobile terminal 100 then displays a ticketing image based on the recording medium information on the display.

[0061] Figure 7B shows an example of a mobile terminal 100 in which a ticket image based on recording medium information is displayed on the display. The display of the mobile terminal 100 shows the recording medium section 21 and the order details section 23 as the ticket image. The recording medium section 21 includes, for example, a two-dimensional barcode based on the recording medium information included in the order response and the text "Please hold it over the scanner when you visit the store". In other words, the recording medium section 21 can guide the user to have the two-dimensional barcode read by the barcode scanner of the ticket issuing device 200 by making the user see the text "Please hold it over the scanner when you visit the store". Thus, the recording medium section 21 can cause the ticket issuing device 200 to acquire information including "order ID information" by having the user perform the operation of having the two-dimensional barcode read by the barcode scanner. The order details section 23 displays, for example, the order details based on the user's order request. As an example, the order details section 23 displays the amount of J1 ramen set by the user in the quantity selection section 13, the adjustments to the product set in the detailed setting section 15, the toppings set in the additional setting section 17, etc. In addition to these order details, the order details section 23 may also display information such as the price of the products, the date and time the order was placed, and the expiration date of the order.

[0062] B. Processing flow executed on the administrator server device 300 The processing flow executed in the administrator server device 300 shown in Figures 6B and 6C will be described in detail below. Figures 6B and 6C show the processing flow executed in the administrator server device 300 according to the present invention, particularly the first embodiment.

[0063] According to Figure 6B, first, when the processor 312 of the administrator server device 300 receives an access request from the mobile terminal 100 via the communication interface 314 (S111), it generates a menu based on the store information table, including the store name, product information, inventory information, and special offer information corresponding to the store ID related to the access request (S112). At this time, it is preferable that the processor 312 extracts inventory information from the store information table and displays the inventory status of the products on the menu.

[0064] Furthermore, it is preferable that the processor 312 extracts the user's preferred discount information based on the user information table and the store's preferred discount information based on the store information table, and includes only matching preferred discount information in the menu. Here, the preferred discount information includes, for example, preferred discount information obtained as a prize based on a predetermined online lottery performed by the user operating the mobile terminal 100 in advance, preferred discount information obtained when visiting the store in the past, and preferred discount information transferred from other users. This allows users to use preferred discount information without losing it, unlike paper service coupons. In addition, by providing preferred discount information online, such as by allowing users to obtain preferred discount information as a prize based on a predetermined online lottery as described above, it is possible to encourage users to visit specific stores.

[0065] Subsequently, the processor 312 sends an access response including a menu to the mobile terminal 100 via the communication interface 314 (S113). Then, the processor 312 receives an order request from the mobile terminal 100 via the communication interface 314 (S114) and determines whether payment for the order request is possible based on the payment process (S115). Specifically, the processor 312 identifies the payment information corresponding to the user ID based on the user information table and determines whether payment processing is possible based on the payment information. If it is determined that payment processing is possible (Yes), the processor 312 executes the payment process (S116) and proceeds to step S117. By executing the payment process in this way, the store operator can reduce the amount of change that needs to be prepared for customers paying for goods in cash. In step S117, the processor 312 generates recording medium information for electronic payment. Specifically, the recording medium information for electronic payment includes information indicating that the price of the goods can be settled by the payment process. On the other hand, if it is determined in step S115 that payment processing is impossible (No), the processor 312 generates recording medium information for cash payment (S118). Examples of cases where payment processing is impossible include cases where payment information is not stored in the user information table and cases where the account number or other information based on the payment information has expired. In other words, the recording medium information for cash payment includes information indicating that payment for the goods cannot be made through payment processing. After generating the recording medium information in step S117 or step S118, the processor 312 sends an order response including the recording medium information to the mobile terminal 100 via the communication interface 314 (S119).

[0066] According to Figure 6C, when the processor 312 of the administrator server device 300 receives read information from the ticket issuing device 200 via the communication interface 314 (S121), it proceeds to the steps from step S122 onwards. Specifically, when a user arriving at the store has the barcode scanner of the ticket issuing device 200 read the two-dimensional barcode on the recording medium unit 21 displayed on the display of the mobile terminal 100, the processor 212 of the ticket issuing device 200 transmits the read information to the administrator server device 300 via the communication interface 214. In other words, when the ticket issuing device 200 reads the two-dimensional barcode, the processor 312 of the administrator server device 300 receives the read information from the ticket issuing device 200 via the communication interface 314. Subsequently, the processor 312 of the administrator server device 300 extracts order information based on the order information table (S122) and transmits the order information to the ticket issuing device 200 via the communication interface 314 (S123). In other words, the processor 312 transmits order information to the ticket issuing device 200, which then issues a numbered ticket.

[0067] Alternatively, instead of executing the payment process at S116 in Figure 6B, the payment process could be reserved. Then, at S121 in Figure 6C, the administrator server device 300 could execute the reserved payment process upon receiving the read information. If the read information is not received after a predetermined period of time has elapsed since the reservation was made, the reservation could be canceled (i.e., the payment process would not be executed). In this way, if a user sends order information before visiting the store but is unable to visit for any reason, the payment process can be avoided, eliminating the need for refund responses and ultimately improving convenience for both the user and the store.

[0068] Figure 16A shows an example of a queue ticket issued by the ticket issuing device 200 when payment processing is performed. If it is determined that payment processing is possible (Yes in S122), the queue ticket 31 has a confirmation section 33 and an order details section 35 printed on it. The confirmation section 33 includes text including the price of the goods (for example, "Total: 1000 yen") and text indicating that payment has been completed (for example, "Payment completed"). In other words, when payment processing is performed, the user does not need to pay at the store, so by printing the confirmation section 33 on the queue ticket in this way, the user and the operator can be notified that payment at the store is not required. The order details section 35 displays the amount of J1 ramen set by the user in the quantity selection section 13, the adjustments to the goods set in the detailed setting section 15, the toppings set in the additional setting section 17, etc., similar to the order content section 23. This allows the user to confirm their order details by looking at the order details section 35.

[0069] Figure 16B shows an example of a queue ticket issued by the ticket issuing device 200 when payment processing is not performed. If it is determined that payment processing is impossible (No in S122), the queue ticket 31 will have a payment request section 43 printed on it instead of the confirmation section 33 described above. The payment request section 43 will contain text including the price of the goods (for example, "Total: 1000 yen") and text prompting payment (for example, "Please complete the payment."). In other words, if payment processing is not performed, the user will need to pay at the store, for example, in cash. By printing the payment request section 43 on the queue ticket in this way, the user and the operator can be notified of the need to pay at the store. Here, as an example, the payment request section 43 is printed instead of the confirmation section 33, but a two-dimensional barcode similar to the confirmation section 33 may be printed instead, or a two-dimensional barcode containing information to activate payment processing using a two-dimensional barcode may be printed.

[0070] 9. Effects of Processing System 1 Next, an example of the effects of the processing system 1 according to the first embodiment described above will be explained. Hereinafter, a user who orders products using the processing system 1 of this disclosure will be referred to as the first user, and a user who orders products using the ticket vending machine 400 will be referred to as the second user.

[0071] First, the second user, who arrives at the store before the first user, joins the end of the queue extending from the ticket vending machine 400 (i.e., the position furthest from the ticket vending machine 400 in the queue). Then, when the first user arrives at the store, they join the end of the queue (i.e., behind the second user in the queue). While in line, the first user operates the mobile terminal 100 to order products (processing up to T13 in Figure 5 and up to S104 in Figure 6A). This order enables the mobile terminal 100 to display the two-dimensional barcode of the recording medium unit 21 on its display (S14 in Figure 5 and S106 in Figure 6A). Then, when the second user is at the front of the queue (i.e., the position closest to the ticket vending machine 400 in the queue), they input order information (second order information) into the ticket vending machine 400 to order products. Subsequently, when the first user is at the front of the queue, they have the barcode on the recording medium unit 21 displayed on the mobile terminal 100's screen read by the barcode scanner of the ticketing device 200 (S15 in Figure 5 above). As a result, the first user obtains a queue ticket (first queue ticket) issued by the ticketing device 200. In other words, the second user obtains a queue ticket (second queue ticket) before the first user.

[0072] Here, for example, the first user might consider the time when they submitted their order request (T13 in Figure 5) to be the start of their queue to receive the goods. On the other hand, the second user, who is in line before the first user, might consider the time when they started to join the queue to be the start of their queue to receive the goods. Therefore, according to the processing system 1 of this disclosure, whether the first queue ticket is issued by the ticket issuing device 200 or the second queue ticket is issued by the ticket vending machine 400, the tickets are issued at the front of the queue, so the first and second users can easily understand the order in which they will receive the goods.

[0073] In particular, the ticket issuing device 200 can issue the first queue ticket by using a barcode scanner as the input interface 215 and a printer as the output interface 211. In other words, the ticket issuing device 200 can be configured at a lower cost compared to the ticket vending machine 400. Therefore, for example, in stores where a ticket vending machine 400 is already installed, the operator can introduce the processing system 1 related to this disclosure at a relatively low cost while using the existing ticket vending machine 400. Furthermore, by having the administrator server device 300 perform accounting processing (S16 in Figure 5), the first user can visit the store without having to prepare cash to purchase goods. In addition, the operator can reduce the amount of preparation required for preparing change and making money by having the goods accounted for by the accounting processing (S16 in Figure 5).

[0074] As an alternative to the above example, first, the first user operates the mobile terminal 100 to order a product (processing up to T13 in Figure 5 and up to S104 in Figure 6A). This order enables the mobile terminal 100 to display the two-dimensional barcode of the recording medium 21 on its display (S14 in Figure 5 and S106 in Figure 6A). Subsequently, when the first user arrives at the store, the mobile terminal 100 displays the recording medium 21 on its display at the first user's operation, and the two-dimensional barcode is read by the barcode scanner of the ticket issuing device 200 (S15 in Figure 5). As a result, the first user can obtain a numbered ticket (first numbered ticket) issued by the ticket issuing device 200 and join the queue (S17 in Figure 5).

[0075] On the other hand, if the second user arrives at the store before the first user, and the second user enters order information (second order information) into the ticket vending machine 400 to order products, the second user will obtain a numbered ticket (second numbered ticket) before the first user. As a result, even if the second user orders products after the first user, the second user will be able to obtain a second numbered ticket and join the queue before the first user because they arrived at the store before the first user.

[0076] Here, for example, the first user might consider the time when they submitted their order request (T13 in Figure 5) to be the start of their queue to receive the goods. On the other hand, the second user, who arrived before the first user, might consider the time of their arrival to be the start of their queue to receive the goods. Furthermore, when providing goods, it can be difficult for the operator to determine whether to provide the goods to the first user or the second user first. Therefore, according to the processing system 1 of this disclosure, whether the first queue ticket is issued by the ticket issuing device 200 or the second queue ticket is issued by the ticket vending machine 400, the tickets are issued after arrival at the store, so the operator, the first user, and the second user can easily understand the order in which they will receive the goods.

[0077] <Second Embodiment> 10. Overview of the Processing System 1 According to the Second Embodiment The processing system in the second embodiment is preferable in that it can effectively utilize, for example, information about a user who placed an order by operating a mobile terminal using the processing system in the first embodiment, and order information related to that order. Specific aspects of the second embodiment will be described below based on the attached drawings. In the following description, we will mainly describe configurations that differ from the first embodiment and configurations added to the first embodiment, and may omit descriptions of configurations common to the first embodiment.

[0078] 11. Information stored in memory 213 (2) Figure 8 is a conceptual diagram showing a user history purchase table stored in the administrator server device 300 according to the present invention, particularly the second embodiment. The user history purchase table stores store ID information, visit date and time information, purchased item information, payment amount information, weather information, and number of people information, associated with user ID information. "User ID information" is identification information pre-assigned to each user, as in the first embodiment. "Store ID information" is identification information pre-assigned to each store, as in the first embodiment. Specifically, in the user history purchase table, when a user places an order at a specific store, "Store ID information" indicating that specific store is assigned to the "User ID information" indicating that user. "Visit date and time information" is information about the time when the user visited the specific store. Whether a user has visited a specific store is determined by triggers such as whether the ticketing device performed the ticketing process (S17) in Figure 5, or whether the location information of the user's terminal device overlaps with the location information of the specific store or is within a certain distance. When it is determined that a user has visited a specific store, memory 213 stores the time information at the time the visit was determined as the visit date and time information.

[0079] "Purchased items information" is information about the goods or services that a user ordered when they visited a specific store. "Payment amount information" is information about the total amount to be paid for the ordered goods or services. For example, if a user purchases multiple items and the information for those multiple items is stored as "Purchased items information," the "Payment amount information" will store the total amount for the purchase of those multiple items. Note that "Store ID information," "Visit date and time information," "Purchased items information," and "Payment amount information" may be stored based on the order information table (particularly "Store ID information" and "Order information") of the first embodiment (Figure 4A).

[0080] "Weather information" refers to information about the weather near a store at the time a user visits the store, such as sunny, cloudy, rainy, or snowy. The administrator server device 300 retrieves and stores weather information from a weather server (not shown) connected via the network, using the user's visit date and time and the store's location information. This weather server has information about time, location, and weather, and may also include rainfall, humidity, and disaster prevention weather information. "Number of people information" refers to the number of people included in a group managed by the store as one unit when a user visits the store. Specifically, in the case of a restaurant, this refers to the number of people seated at a table or in a private room, and the information is retrieved and stored by referring to the number of appetizers included in the order information and the number of people who placed orders within a certain time. On the other hand, if people simply sit at the same table in a shared seating arrangement, they are not managed as being in the same group.

[0081] Figure 9 is a conceptual diagram showing an additional information table stored in the administrator server device 300 according to the present invention. The additional information table is an information table in which the conditions for generating additional information (conditions 1, 2, 3, etc.) are associated with each additional information ID. The "additional information ID" is identification information assigned to each piece of additional information. The additional information is incidental information related to the goods or services ordered by the user, such as a visit stamp that counts the number of visits to the store, a reward given when the number of visits to the store reaches a certain number (e.g., 2 times), a questionnaire that asks the visiting user for their impressions, fortune information, and trivia information about the goods or services provided by the store. This additional information is printed on the additional information ticket 137 issued by the ticket issuing device 200. The additional information ticket 137 is issued when the queue ticket 31 is issued by the ticket issuing device 200, for example, before the queue ticket 31 is issued. This additional information ticket 137 is printed on, for example, the roll paper which is the printing medium for the queue ticket 31. Furthermore, the additional information ticket 137 is connected to the numbered ticket 31 in such a way that it can be separated by perforated sections 139 formed by intermittently cutting the roll paper. The perforated sections 139 may be formed to facilitate separation by leaving a portion of the roll paper intact, and it is not necessary to form the perforated sections 139 between the numbered ticket 31 and the additional information ticket 137.

[0082] The conditions associated with each piece of additional information can be set individually or in multiple ways. The relationships between multiple conditions can be AND, OR, or a combination thereof. CRM information is primarily used for specific conditions. CRM stands for Customer Relationship Management, and CRM information refers to management information related to a user's purchasing behavior. This includes information such as the number of times a particular store is visited, the frequency of visits over a certain period, the average payment amount per visit, and the cumulative payment amount to a particular store.

[0083] Here are some specific examples of additional information and conditions. For example, suppose the additional information is a discount offer for a specific product, and the conditions are set as an OR condition: the customer must visit the store at least twice in a week, and the total amount paid must be 10,000 yen or more. In this case, if the user visits the store twice in a week and the total amount paid is 2,000 yen, the conditions will be met. Also, suppose the additional information is information related to a survey requesting feedback on the visit, and the condition is set as the number of visits must be at least twice. In this case, if the user visits the store for the second time, the conditions will be met. Furthermore, suppose the additional information is a discount offer for a specific product free of charge, and the condition is set as the person visiting the store for the first time being in the aforementioned group. In this case, if multiple people visit the store as a group, and at least one of them is visiting the store for the first time, the conditions will be met. Here, it is conceivable that the determination of whether or not someone is visiting the store for the first time is made based on the user purchase history table (Figure 8). Furthermore, the users who receive the preferential treatment information may be all members of the group, or it may be the person with the highest payment amount within the group.

[0084] Figure 10 is a conceptual diagram showing a recommendation information table stored in the administrator server device 300 according to the present invention. The recommendation information table is information for pre-storing specific conditions for recommendation information that is generated when a user meets certain conditions. Here, "recommendation information ID" is the ID information of the product that the store wants the user to purchase when the user places an order. "Conditions" is information about the conditions under which each product that the store wants the user to purchase is shown to the user. Multiple conditions can be set, and the relationships between multiple conditions are the same as in Figure 9. Specific conditions include, for example, information about product inventory (including information about best-before and expiration dates), information about the user's product purchase history, and information about target quantities or amounts set by the store.

[0085] Let's explain specific examples of conditions 1, 2, 3, etc. First, conditions can be broadly categorized into those attributable to the user, those attributable to the store, and those attributable to external factors. Conditions attributable to the user include, for example, the user's age, gender, and preferences. Conditions attributable to the store include, for example, the number of items in stock at the store, the expiration date of the items, the number of times the service can be provided, and the period during which the service can be provided. Conditions attributable to external factors include, for example, the weather and time of day.

[0086] Next, let's look at some specific examples of recommendation information and conditions. For example, suppose the recommendation information is a specific product, and the conditions are set as AND: the inventory is 10 or more, and the user has purchased it 5 or more times. In this case, if the user has purchased the product 6 times and the inventory is 15, the conditions will be met (i.e., the store wants to keep the inventory of a certain product below 10, and if the user has purchased the product more than 5 times, the store understands that the product matches the user's preferences and presents it to the user as a recommended product with the intention of reducing inventory). Alternatively, suppose the recommendation information is a specific service, and the condition is set as the amount being 100,000 yen or less per day (i.e., the target amount per day is 100,000 yen or more). In this case, if the cumulative sales amount of that specific service at the store on that day is 80,000 yen when the user visits the store, the conditions will be met.

[0087] Although the tables shown in Figures 4, 8 through 10 were described as being stored in the administrator server device 300, they may also be stored in a database (not shown) that is connected to the administrator server device 300 via a network for communication. In this case, the administrator server device 300 temporarily reads the information stored in the database into memory 311 within the administrator server device 300 as processing progresses. These tables may also be stored separately.

[0088] 12. Processing flow (2) executed by processing system 1 Figure 11 shows the processing flow executed in the processor 312 of the administrator server device 300. First, CRM information is generated using the user purchase history table (Figure 8) (S131). Specifically, for example, if the CRM information is about the number of visits, the number of times a user has visited a particular store can be determined by referring to the store ID information and the visit date and time information and finding the number of specific store IDs with different visit date and time information. Also, for example, if the CRM information is the average payment amount, the average amount a user pays per visit can be determined by summing the payment amounts corresponding to specific store IDs and dividing by the number of visits mentioned above.

[0089] Next, the process of selecting additional information is performed (S132). The process of selecting additional information is performed by referring to the additional information table in Figure 9. Specifically, at the time this processing flow is executed, additional information that satisfies the conditions is extracted and the extracted additional information is treated as selected additional information. If multiple pieces of additional information are extracted, all of the extracted additional information may be treated as selected additional information, or the content that satisfies the conditions may be referred to, and the conditions may be weighted to prioritize the additional information, and a predetermined number of the highest-priority pieces of additional information may be treated as selected additional information. As for weighting, for example, if the condition is set to the number of visits and the value is 3, the greater the deviation of the number of visits by the user from 3, the more weight is given (i.e., the more visits, the more weight is given).

[0090] Next, it is determined whether or not a process to generate additional information (additional information generation process) is necessary (S133). For example, if additional information is extracted in S132, it is determined that an additional information generation process is necessary and the process proceeds to S134. If no additional information is extracted, it is determined that an additional information generation process is unnecessary and the process flow ends. Note that the determination of whether or not an additional information generation process is necessary may be made based on information in various information tables such as user information, payment information, and store information; it is sufficient as long as it is possible to determine whether or not an additional information generation process is necessary.

[0091] Next, if it is determined in S133 that additional information generation processing is necessary, processing is performed to generate additional information (S134). Specifically, information is created to be added to the order information when the user orders a product or service, while referring to CRM information, user attribute information, past preferential treatment information, etc. For example, suppose the preferential treatment information is that a specific product will be provided free of charge, and the condition is the number of visits. In this case, the additional information will include information about the specific product and information about the number of visits by the user. In this way, the user can understand what action of the user led to the generation of the preferential treatment information. Next, if the additional information generated in S134 is preferential treatment information, it is stored in the information tables explained in Figures 4A to C (for example, "Preferential Treatment Information" in the Order Information Table, "Preferential Treatment Information" in the Store Information Table, and "Owned Preferential Treatment Information" in the User Information Table) (S135). The additional information generated in this processing flow is generated as a single piece of information together with the order information, etc., when ticketing information is generated in S13 in Figure 5. In this way, the mobile terminal 100 can display information including additional information in S15, and the ticket issuing device 200 can read this information and issue a numbered ticket in S17 based on the information including the additional information.

[0092] In this processing flow, the first step is to perform the CRM information generation process, but this may be performed separately from the main processing flow. For example, it could be performed at predetermined regular intervals or whenever the purchase history table is updated. Alternatively, this processing flow could be performed at a predetermined specific time (for example, at night), and then direct mail containing additional information could be sent to the user while referring to the CRM information. This could, for example, encourage users who have not visited the store for a certain period of time to return.

[0093] Furthermore, the CRM information generated in this processing flow may be sent to another information processing device that is not displayed on processing system 1. For example, by sending it to the information processing device of an advertising provider, the advertising provider can use the received CRM information to select more effective advertisements and provide advertisements that are of higher value to the user.

[0094] Figure 12 shows the processing flow executed in the processor 312 of the administrator server device 300, which is, for example, a process that outputs candidate recommended products, which are goods or services that a store would like a user to purchase. First, CRM information is generated using the user purchase history table shown in Figure 8 (S141). This process is the same as S131 in Figure 11. Next, the recommended product selection process is performed (S142). Specifically, the recommended product selection process is performed by referring to the recommendation information table in Figure 10. More specifically, at the time this processing flow is executed, recommended products that meet the conditions are extracted, and the extracted recommended products are treated as selected recommended product information. If multiple recommended product information is extracted, all of the extracted recommended product information may be treated as selected additional information, or the recommended product information may be prioritized by referring to the content that meets the conditions and weighting the conditions, and a predetermined number of the highest-priority recommended product information may be treated as selected recommended product information. For example, if there are 5 recommended products that meet the conditions and the predetermined number is 2, the 2 highest-priority recommended products among the recommended products that meet the conditions will be selected as recommended product information. For example, weighting could be implemented by setting a condition that the inventory quantity is 10 or greater, and the greater the deviation of the inventory quantity of the recommended product from 10 at the time the processing flow is executed, the greater the weight (i.e., products with a larger inventory quantity are weighted because stores want to sell them more). Alternatively, the expiration date of the product to be recommended could be set as a time, and the less the time the processing flow is executed is from the expiration date, the greater the weight (i.e., products with a shorter expiration date are weighted because stores want to sell them sooner).

[0095] Next, it is determined whether a process to generate recommended product information (recommendation information generation process) is necessary (S143). For example, if recommended product information is extracted in S142, it is determined that a recommendation information generation process is necessary and the process proceeds to S144. If no recommended product information is extracted, it is determined that a recommendation information generation process is unnecessary and the process flow ends. Note that the determination of whether a recommendation information generation process is necessary may be made based on information in various information tables such as user information, payment information, and store information; it is sufficient as long as it is possible to determine whether a recommendation information generation process is necessary.

[0096] Next, if it is determined in S143 that a recommendation information generation process is necessary, the process of generating recommended product information is performed (S144). Specifically, while referring to CRM information, user attribute information, order history, etc., information (recommended product information) of products (recommended products) that will be displayed to the user as recommended products when the user displays the store's product purchase web page on the mobile terminal 100's display is created.

[0097] For example, suppose the condition for a specific recommended product is the cumulative number of times the user has purchased that product. In this case, the recommended product information includes information about the specific product and information about the user's cumulative number of purchases, and both pieces of information are displayed on the mobile terminal 100 through the process shown in Figure 15 below. In this way, the user can understand what action of theirs generated the preferential information. If there are conditions (e.g., inventory level or expiration date) that the store has that were met to generate the recommended product information, discount information for that recommended product may also be added. Next, the recommended product information generated in S144 is stored in the administrator server device 300 (S145). Note that the step in S145 may be omitted by executing this processing flow each time the user displays the store's product purchase web page.

[0098] Figure 13 shows the processing flow executed in the processor 312 of the administrator server device 300, which outputs proposed products that are candidates for consideration when a restaurant consultant proposes new products or services to a store. First, a persona is generated using the store information table shown in Figure 4B, the user information table shown in Figure 4C, and the user purchase history table shown in Figure 8 (S151). Here, a persona refers to a typical user profile that is likely to visit a particular store. Specifically, it is created by considering, for example, the product purchase history at a particular store, the attributes of the user who visits the store (e.g., age, gender, etc.), the store category (e.g., family restaurant, ramen shop, etc.), the product history at competing stores of the same category in the vicinity of the store, price range (e.g., high price, low price, etc.), business hours (e.g., daytime business, nighttime business, etc.), and business days (e.g., weekday business, closed on Sundays, etc.). Multiple personas may be generated, in which case they may be prioritized based on the average payment amount, etc. The generated persona may contain information such as age, gender, address, residential address, school or work address, annual income, disposable income, type of goods or services purchased, and the amount spent per payment for purchased goods or services.

[0099] Next, the process of selecting proposed products is performed (S152). The process of selecting proposed products is performed using the persona information generated in S151. Specifically, the products or services that the persona is likely to purchase are compared with the products or services that can be provided at the specific store, and products or services that the target store does not provide are selected as proposed products. Multiple proposed products may be selected, in which case priority may be given considering the unit price, the store's profit, the implementation cost, etc. For example, suppose a persona who operates in a specific area (e.g., within a 1km radius of a specific store) uses multiple target ramen restaurants as the target store, and at the specific ramen restaurant as the target store, they order alcohol along with their ramen, and it has been determined that ramen and alcohol are a combination of products that the persona is likely to purchase. In that case, if the target ramen restaurant does not provide alcohol, alcohol will be selected as a proposed product.

[0100] Next, it is determined whether a process to generate suggested product information (suggested product information generation process) is necessary (S153). For example, if a suggested product is selected in S152, it is determined that the suggested product information generation process is necessary and the process proceeds to S154. If no suggested product is selected, it is determined that the suggested product information generation process is unnecessary and the process flow ends. The determination of whether the suggested product information generation process is necessary may be made based on information in various information tables such as user information, payment information, and store information; it is sufficient if it is possible to determine whether the suggested product information generation process is necessary. Next, if it is determined in S153 that the suggested product information generation process is necessary, the process to generate the suggested product information is performed (S154). The generated suggested product information may be output separately from this process flow when the administrator server device 300 receives a command to output suggested product information, or it may be output by executing this process flow when the administrator server device 300 receives a command to output suggested product information, or it may be temporarily stored in the administrator server device 300 after generation. In addition, the persona information generated in this process flow may also be stored in the administrator server device 300 after generation and output along with the suggested product information. Additionally, the CRM information generated in S131 and S141 may be stored in the administrator server device 300 after generation and output in accordance with the proposed product information.

[0101] 13. Processing sequence (2) executed by processing system 1 Figure 14 is a diagram showing the processing sequence of the processing system 1 according to an embodiment of the present invention, and is a modified version of the processing from T13 to T14, which is part of the processing sequence described in Figure 5. When the mobile terminal 100 receives an order operation for a product through user operation, it sends the order request to the administrator server device 300 (T13). When the administrator server device 300 receives the order request from the mobile terminal 100, it performs accounting processing based on the order request (S12). Once the accounting processing is completed, it generates order ID information and recording medium information (ticketing information) (S13'), and stores the generated order ID information and recording medium information, as well as the store ID information, user ID information, order information, and preferential information included in the order request, in the order information table (S14'). S131 to S134 of the processing flow described in Figure 11 are executed as generation processing performed in S13', and S135 is executed as storage processing performed in S14'.

[0102] Figure 15 is a diagram showing the processing sequence of the processing system 1 according to an embodiment of the present invention, and is a modified version of the processing from T11 to T12, which is part of the processing sequence described in Figure 5. The mobile terminal 100 sends an access request to the administrator server device 300 for the web page for purchasing products at the store the user plans to visit, based on user operation (T11). The web page for purchasing products is managed, for example, by the administrator server device 300. The administrator server device 300 sends an access response based on the access request received from the mobile terminal 100 (T12). The processing flow described in Figure 12 is executed by the administrator server device 300 between the processing of T11 and T12 (S18).

[0103] 14. An example of a numbered ticket output by the ticket issuing device 200 Figures 16A to 16C show examples of queue tickets issued by the ticket issuing device 200 when payment processing is performed. Hereinafter, the processing according to the second embodiment of the present invention will be explained using the example of a user visiting a store H1, which is a ramen shop that provides ramen as a product, as in the first embodiment.

[0104] The queue ticket 31 has a confirmation section 33 and an order details section 35 printed on it. The confirmation section 33 includes text including the price of the goods (for example, "Total: 1000 yen") and text indicating that payment has been completed (for example, "Payment Completed"). In other words, if payment processing has been completed, the user does not need to pay at the store, so printing the confirmation section 33 on the queue ticket 31 informs the user and the operator that payment at the store is not required. If payment has not been completed, text indicating that payment has not been completed (for example, "Not Paid") may also be included. The order details section 35 displays the amount of J1 ramen set by the user in the quantity selection section 13, adjustments to the goods set in the detailed settings section 15, and toppings set in the additional settings section 17, similar to the confirmation section 33. This allows the user to confirm their order details by looking at the order details section 35.

[0105] Figures 16A to 16C show examples of queue tickets 31 and supplementary information tickets 137 issued by the ticket issuing device 200 when payment processing is performed. Here, a specific example of supplementary information will be explained. As mentioned above, supplementary information includes store visit stamps, rewards, and questionnaires. According to Figure 16A, the store visit stamp 137A has the same number of stamp frames 141 as the number of visits for which a reward is awarded (e.g., 5 times), and the same number of stamps 143 as the number of visits are printed so that they fit inside the stamp frames 141. Here, the administrator server device 300 generates image data of the store visit stamp 137A while referring to the user purchase history table (Figure 8) stored in memory 313. Specifically, according to Figure 5, when the user has the barcode scanner of the ticket issuing device 200 read the two-dimensional barcode of the recording medium unit 21 displayed on the display of the mobile terminal 100 (S16), the administrator server device 300 receives the read information from the ticket issuing device 200 (T15). At this time, the processor 312 of the administrator server device 300 calculates the number of times the user related to the read information has visited the store related to the read information, based on the user purchase history table. That is, the processor 312 of the administrator server device 300 generates image data of a visit stamp 137A printed so that the same number of stamps 143 as the number of visits calculated in this way fit inside the stamp frame 141. Then, when the administrator server device 300 transmits this image data along with the order information to the ticket issuing device 200 as additional information (T16), the ticket issuing device 200 issues a queue ticket 31 and a visit stamp 137A as shown in Figure 16A.

[0106] On the one hand, when the number of visits for which a reward is given matches the number of times the user has visited the store, a reward exchange coupon 137B is printed as the additional information coupon 137. Specifically, in the additional information table (Figure 9) stored in the memory 313 of the administrator server device 300, an additional information ID associated with a reward (e.g., a coupon for seasoned eggs) as additional information is described. Also, corresponding to the additional information ID, as condition 1, the number of visits is stored. After the processor 312 of the administrator server device 300 calculates the number of times the user has visited the store, it determines whether the calculation result matches the above condition 1. Thus, when the processor 312 of the administrator server device 300 determines that the calculation result does not match the above condition 1, it generates a visit stamp 137A as the image data of the additional information coupon 137, and when it determines that the calculation result matches the above condition 1, it generates a reward exchange coupon 137B as the image data of the additional information coupon 137. Thereafter, the reward exchange coupon 137B is issued by the issuing device 200 in the same manner as the visit stamp 137A.

[0107] Here, in a food and beverage store, the operator's hands may be wet with water or the like, and when pressing a stamp on a so-called stamp card, it is conceivable that the stamp card will get wet. Also, for the user, it is conceivable that the stamp card will be lost. In contrast, in the processing system 1 according to the second embodiment, the issuing device 200 prints a visit stamp 137A with a stamp 143 printed thereon based on the user purchase history table (Figure 8) stored in the memory 313 of the administrator server device 300. Thus, by printing the visit stamp 137A with the stamp 143 printed thereon by the issuing device 200, the store operator can omit the operation of pressing a stamp on the stamp card. Also, for the user, it is possible to obtain the visit stamp 137A printed by the issuing device 200 without carrying the stamp card. Furthermore, in the processing system 1 according to the second embodiment, the administrator server device 300 can appropriately manage the number of visits of the user because it calculates the number of visits of the user based on the user purchase history table (Figure 8).

[0108] Furthermore, as shown in Figure 16C, an example of an additional information ticket 137 is shown. For example, if the additional information requests a survey about the store, ticket 137C is printed with a two-dimensional barcode containing the text requesting the survey and information about the URL to enter the survey. Here, the administrator server device 300 generates image data for the survey 137C while referring to the user purchase history table (Figure 8) stored in memory 313. Specifically, as shown in Figure 5, when a user has the barcode scanner of the ticket issuing device 200 read the two-dimensional barcode on the recording medium unit 21 displayed on the display of the mobile terminal 100 (S16), the administrator server device 300 receives the read information from the ticket issuing device 200 (T15). At this time, the processor 312 of the administrator server device 300 calculates the number of times the user related to the read information has visited the store related to the read information, based on the user purchase history table. The processor 312 of the administrator server device 300 generates a two-dimensional barcode containing information about a URL for entering a questionnaire if the number of times the user has visited the store is predetermined (for example, 2 times) or more. When the administrator server device 300 transmits this image data along with the order information to the ticket issuing device 200 as additional information (T16), the ticket issuing device 200 issues a queue ticket 31 and a questionnaire 137C as shown in Figure 16C.

[0109] Furthermore, regarding the numbered tickets 31 and supplementary information tickets 137 issued as shown in Figures 16A to 16C, it is preferable to print the supplementary information tickets 137 first, followed by the numbered tickets 31. This is because, for example, if a user only takes the supplementary information tickets 137 and forgets to take the numbered tickets 31, the store operator will feel uneasy if the user hands the supplementary information tickets 137 to the operator but there are no numbered tickets 31. In other words, by printing the numbered tickets 31 after the supplementary information tickets 137, this system can prevent users from forgetting to take the supplementary information tickets 137.

[0110] 15. Summary of Embodiments of the Disclosure With the configuration described above, the processing system according to the present invention is a processing system 1 that includes a mobile terminal 100 owned by a user of a store, an administrator server device 300 as an information processing device, and a ticket issuing device 200 that reads information output from the mobile terminal 100 and issues tickets. The administrator server device 300 receives a user ID and order information that the user has ordered for goods or services at the store from the mobile terminal 100 (T13), stores the received user ID and order information in an order information table (Figure 4A) as order history information (S14), generates CRM information for the user from the order information table (S13'), and stores the generated CRM information (S14').

[0111] As a result, the processing system according to the present invention receives a user ID and order information from a mobile terminal 100 to an administrator server device 300 upon a user's order, stores the user ID and order information in an order information table, and generates CRM information based on the stored user ID and order information, thereby generating CRM information for utilizing information about the user and the user's orders. In particular, the processing system 1 including the ticket issuing device 200 can be used in business types that operate using meal tickets, such as ramen shops, and is therefore suitable in that it can generate CRM information for such business types.

[0112] Furthermore, in the processing system according to the present invention, the administrator server device 300 generates additional information to be added to the order information based on the user ID, order information, and CRM information (S134), generates ticketing information including the order information and additional information (S13'), and transmits the ticketing information to the mobile terminal 100 (T14). The ticketing device 200 receives the ticketing information (T16), refers to it, and issues a ticket (S17). As a result, even stores that only have ticket vending machines 400 that cannot connect to a network can introduce the processing system 1 without changing the ticketing operations at the store by installing the ticketing device 200. In particular, the processing system according to the present invention is preferable in that CRM information can be generated by the ticketing device 200 installed at the store.

[0113] Furthermore, the processing system according to the present invention includes the number of times a user has visited the store in the CRM information, and information requesting a survey from the user in the additional information, and the administrator server device 300 generates the additional information when the number of times a user has visited the store is equal to or greater than a predetermined value. This makes it possible for stores to narrow down the users they request surveys from. In particular, by setting the predetermined value to 2, it becomes possible to request surveys from users who have visited the store at least once, and it becomes possible to expect more detailed survey responses.

[0114] Furthermore, the processing system according to the present invention includes usage patterns of a user when using a store in CRM information, and preferential information that the store provides to the user in additional information, and the administrator server device 300 generates the additional information based on the user's usage patterns. This makes it possible to provide users with suitable preferential information based on their actual usage. In particular, by making the preferential information a product or novelty item at the store, it is expected that the frequency of the user's visits will increase. In addition, the CRM information includes weather information at the time the user visited the store, and the administrator server device 300 generates additional information based on the weather information. In this way, for example, when generating preferential information based on the number of times the user has visited the store, if the visit is during bad weather such as rain or snow, one visit will be counted as two visits, thereby giving the user an incentive to visit in bad weather. In addition, the CRM information includes information on the number of people guided as a group when the user visited the store, and the administrator server device 300 generates preferential information by referring to the number of people information. By doing this, if a customer visits in a group exceeding a predetermined number, the store can generate special offers such as discounts on goods or services (for example, one person free for groups of 5 or more), thereby encouraging visits in large groups.

[0115] Furthermore, the processing system according to the present invention determines whether or not there is a person in the group who is visiting the store for the first time, and if there is a person in the group who is visiting the store for the first time, it grants the preferential treatment related to the preferential treatment information to at least one of the users included in the group. This makes it possible to encourage users to bring in people who have never visited the store before.

[0116] Furthermore, the processing system according to the present invention includes preferential information that stores offer to users as additional information, and the administrator server device 300 generates preferential information by lottery. This provides users with an incentive to visit the store. In addition, the CRM information includes at least one of the number of times a user has visited the store, the frequency of visits, the average payment amount, and the cumulative payment amount, and the administrator server device 300 performs a lottery based on the CRM information. In this way, it is possible to make the lottery probability higher for those who contribute more to the store's sales, rather than just a simple lottery, thereby providing users with an even greater incentive to visit the store.

[0117] Furthermore, in the processing system according to the present invention, the administrator server device 30 identifies products that a user is likely to purchase based on CRM information (S142), and sends recommendation information to the mobile terminal 100 as products recommended to the user (T12). The recommended products are displayed on the mobile terminal 100 (S103), allowing the user to confirm the recommended products. In addition, by making the products that a user is likely to purchase products that match the user's preferences, the likelihood of the user purchasing the recommended products can be increased. Furthermore, the administrator server device 300 stores inventory information regarding the inventory of products that the store can provide, identifies products whose inventory quantity is above a predetermined value based on the inventory information, and makes the identified products recommendation information. In this way, the store can present products that it wants to reduce inventory of as recommended products to the user, increasing the likelihood of them being purchased. Furthermore, the inventory information also includes expiration date information regarding the expiration dates of products that the store can provide, identifies products that are nearing their expiration date based on the expiration date information, and makes the identified products recommendation information. In this way, the likelihood of products nearing their expiration date being purchased can be increased, preventing products from being discarded due to expiration.

[0118] Furthermore, in the processing system according to the present invention, the administrator server device 300 identifies products or services that the store does not offer based on order history information (S152), and generates proposal information that proposes the identified products or services to the store (S154). In this way, for example, restaurant consultants can use this as consideration material when proposing new products to stores.

[0119] Furthermore, the processing system according to the present invention transmits the generated CRM information to an information processing device managed by the advertiser, via the administrator server device 300. In this way, the advertiser can provide more effective advertisements based on CRM.

[0120] In the first and second embodiments described so far, the use of a two-dimensional barcode as the recording medium has been primarily explained. However, the invention is not limited to this, and a method related to narrowband wireless communication such as Bluetooth® or a method related to contactless wireless communication may be used to allow the mobile terminal 100 to obtain ticketing information, including order ID information, from the ticketing device 200. Furthermore, although the acquisition of order ID information, etc., from a two-dimensional barcode has been explained, for example, a picture or the like from which a serial number and feature quantities can be extracted may be displayed on the recording medium unit 21, and a camera may be used instead of the barcode scanner of the ticketing device 200, and the recording medium unit 21 may be photographed with the camera to extract character information and feature quantities and identify the order ID information. In addition, the mobile terminal 100 and the ticketing device 200 may communicate ticketing information by establishing an ad-hoc network via the communication interface 214.

[0121] Furthermore, it has been explained that the mobile terminal 100, the ticketing device 200, and the administrator server device 300 communicate via the Internet to execute each process of the processing system according to the present invention. However, the invention is not limited to this, and the mobile terminal 100 may receive order information for goods or services from users offline without using the Internet, and the ticketing device 200 may issue queue tickets offline without using the Internet (that is, the processing system according to the present invention may be configured as a so-called on-premise type). In this case, for example, the mobile terminal 100 may store information about the store's goods or services in advance in its memory 113, display an image on the display for ordering goods or services based on the information about the goods or services, and accept the order operation of goods or services through user operation, thereby receiving order information offline. In addition, the mobile terminal 100 may generate a recording medium on which the order information is recorded based on the order information received offline, and the ticketing device 200 may issue queue tickets by reading the order information from the recording medium.

[0122] The processes and procedures described herein can be implemented not only by those explicitly described in the present invention, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein can be implemented by implementing logic corresponding to the process on a medium such as an integrated circuit, volatile memory, non-volatile memory, magnetic disk, or optical storage. Furthermore, the processes and procedures described herein can be implemented as computer programs and executed by various computers, including terminal devices and server devices.

[0123] Even if it is stated that the processes and procedures described herein are performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software programs, multiple components, and / or multiple modules. Similarly, even if it is stated that the various types of information described herein are stored in a single memory or storage unit, such information may be distributed and stored in multiple memories within a single device or in multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein can be realized by integrating them into fewer components or by decomposing them into more components. [Explanation of symbols]

[0124] 100 mobile devices 200 ticket issuing machines 300 Operator Server Device (Information Processing Device) 400 ticket vending machines

Claims

1. A processing system including a mobile terminal owned by a user of a store, an information processing device, and a ticket issuing device that reads information output from the mobile terminal and issues tickets, The aforementioned information processing device is The mobile terminal receives the user ID and order information for goods or services ordered by the user at the store. The received user ID and order information are stored in the order history information. From the aforementioned order history information, the user's CRM information is generated. The generated CRM information is stored in A processing system characterized by the following:

2. A processing system as described in claim 1, The aforementioned information processing device further, Referencing the user ID, the order information, and the CRM information, generate additional information to be added to the order information for the user. The system generates ticketing information including the order information and the additional information, The ticketing information is transmitted to the aforementioned mobile terminal. The aforementioned ticket issuing device, Upon receiving the aforementioned ticketing information, The ticket is issued by referring to the aforementioned ticketing information. A processing system characterized by the following:

3. The processing system according to claim 2, The CRM information includes the number of times the user has visited the store. The aforementioned additional information includes information requesting the user to complete a survey. The aforementioned additional information is generated when the number of times the user has visited the store is equal to or greater than a predetermined value. A processing system characterized by the following:

4. The processing system according to claim 3, The predetermined value is 2 or more. A processing system characterized by the following:

5. The processing system according to claim 2, The CRM information includes the user's usage patterns of the store, The aforementioned additional information includes preferential information provided by the store to the user. The additional information is generated by referring to the usage pattern. A processing system characterized by the following:

6. The processing system according to claim 5, The aforementioned preferential information is a product or service or a novelty item thereof at the aforementioned store. A processing system characterized by the following:

7. The processing system according to claim 6, The CRM information includes weather information at the time the user visited the store. The aforementioned preferential information is further generated by referring to the aforementioned weather information. A processing system characterized by the following:

8. The processing system according to claim 7, The CRM information includes the number of people who were guided as a group when the user visited the store, The aforementioned preferential information is further generated by referring to the aforementioned number information. A processing system characterized by the following:

9. The processing system according to claim 8, Determine whether or not there is a person in the group who is visiting the store for the first time. If there is a person in the group who is visiting the store for the first time, the preferential treatment related to the preferential treatment information shall be granted to at least one of the users included in the group. A processing system characterized by the following:

10. The processing system according to claim 2, The aforementioned additional information includes preferential information provided by the store to the user. The aforementioned preferential information is generated by lottery. A processing system characterized by the following:

11. A processing system according to claim 10, The CRM information includes at least one of the number of times the user has visited the store, the frequency of visits, the average payment amount, and the cumulative payment amount. The aforementioned lottery is performed by referring to the CRM information. A processing system characterized by the following:

12. A processing system according to claim 1, The aforementioned information processing device further, Based on the CRM information, identify products or services that the user is likely to purchase, and send recommendation information to the user, recommending the identified products or services as recommended products or services. A processing system characterized by the following:

13. The processing system according to claim 12, The goods or services that the user is most likely to purchase are those that suit the user's preferences. The aforementioned recommendation information is transmitted to the mobile terminal. A processing system characterized by the following:

14. The processing system according to claim 12, The aforementioned information processing device further, The system stores information regarding the number of goods or services that the store can provide, Referencing the aforementioned information on the number of items that can be provided, identify the goods or services for which the number of items that can be provided is equal to or greater than a predetermined value. The aforementioned recommendation information includes the goods or services specified in relation to the number of items that can be provided. A processing system characterized by the following:

15. The processing system according to claim 14, The aforementioned availability information further includes expiration date information, which is information regarding the expiration date of the goods or services that the store can provide. The aforementioned information processing device further, Referencing the aforementioned expiration date information, identify the goods or services that are nearing their expiration date. The aforementioned recommendation information includes the goods or services specified with respect to the aforementioned deadline. A processing system characterized by the following:

16. A processing system according to claim 1, The aforementioned information processing device further, Referencing the aforementioned order history information, identify products or services not offered by the store, and transmit the identified products or services to the store as proposed products or services. A processing system characterized by the following:

17. A processing system according to claim 1, The aforementioned information processing device further, The CRM information is transmitted to an information processing device managed by the advertiser. A processing system characterized by the following:

18. An information processing device that connects via a network to a mobile terminal owned by a user of a store and a ticketing device that reads information output from the mobile terminal and issues tickets, The mobile terminal receives the user ID and the order information that the user has placed with the store. The received user ID and order information are stored in the order history information. From the aforementioned order history information, the user's CRM information is generated. The generated CRM information is stored in An information processing device characterized by the following:

19. A method for supporting store operations in a processing system that includes a mobile terminal owned by a user of the store, an information processing device, and a ticketing device that reads information output from the mobile terminal and issues tickets, The mobile terminal transmits the user ID and the order information that the user has placed with the store. The information processing device receives the user ID and the order information. The information processing device stores the user ID and the order information in the order history information. The information processing device performs the steps of generating the user's CRM information from the order history information, and The information processing device stores the generated CRM information. A method for supporting store operations, characterized by including the following:

20. In an information processing device that connects via a network to a mobile terminal owned by a user of a store and a ticketing device that reads information output from the mobile terminal and issues tickets, A process of receiving the user ID and order information placed by the user with the store from the aforementioned mobile terminal. The process of storing the received user ID and order information in the order history information. A process for generating the user's CRM information from the order history information, and The process of storing the generated CRM information, A program that causes an information processing device to execute.

Images