JP7347846B2 - Information processing system, information processing method and program - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act [1] ▲1▼ Website publication date November 25, 2020 ▲2▼ Website address https://prtimes. jp/main/html/rd/p/000000091.000045433. html Other publications listed in the form for submitting exception certificate of loss dated December 17, 2021

The present invention relates to an information processing system, an information processing method, and a program.

Conventionally, in the case of a company that has a company cafeteria, cards that can be used at the company cafeteria are distributed (see Patent Document 1). On the other hand, in companies that do not have a company cafeteria, the company pays a subsidy for lunch.

Japanese Patent Application Publication No. 7-68984

Recently, the drastic drop in restaurant sales due to the novel coronavirus outbreak has become a social issue. In response to this problem, the inventor of the present application came up with a new idea of contributing to the sales of existing restaurants by having customers use them as if they were company cafeterias.

The present invention has been made in view of the above problems, and provides an information processing system, an information processing method, and a program that enable employees to use restaurants as if they were company cafeterias. The purpose is to

In the information processing system according to one aspect of the present invention, when an order menu is selected by an employee, information regarding tickets that can be used at a restaurant for a plurality of employees is stored in a storage device that is associated with the employee. and an output unit that outputs information for displaying a discount amount and/or a post-discount payment price by referring to information regarding the ticket assigned to the employee.

The information processing system includes an acquisition unit that acquires information for collectively allocating tickets that can be used at a restaurant to multiple employees; a storage unit that associates information regarding the ticket and stores it in the storage device;
Equipped with.

In the information processing system, the acquisition unit acquires the ticket granting method and settings corresponding to the ticket granting method, and the storage unit stores the reception unit for a plurality of employees to whom the tickets are granted. The ticket grant method and the ticket settings are stored in association with each other, and the output unit is configured to display a discount amount and/or a post-discount payment price based on both the ticket type and the ticket settings. Information may also be output.

In the information processing system, the acquisition unit acquires selection information as to whether each menu is to be ticketed or not, and the storage unit is configured to acquire selection information as to whether each menu is to be ticketed or not. , is stored in a storage device in association with company identification information that identifies the company of the person in charge of ticket management, and when the acquisition unit acquires search conditions from an employee, searches for restaurants that match the search conditions and generates search results. The search unit may also include a search unit that outputs.

In the information processing system, when receiving the input for the batch grant, the acquisition unit acquires the employment type of the employee to whom the grant is to be made, and the storage unit acquires the employment type of the employee corresponding to the acquired employment type. Information regarding the ticket may be associated with employee identification information for identifying the employee and stored in the storage device.

In the information processing system, the acquisition unit specifies a birthday or joining date and acquires a selection to grant the ticket for each birthday or joining date, and the storage unit specifies the accepted birthday or joining date. Information regarding the ticket may be stored in a storage device in association with employee identification information that identifies the relevant employee.

In the information processing system, the acquisition unit acquires the type of the ticket when acquiring information for the batch grant, and the storage unit acquires the ticket type for the plurality of employees to whom the ticket is granted. The type of the received ticket may be further associated and stored.

In the information processing system, the acquisition unit acquires the usable period of the ticket, and the storage unit stores the usable period of the ticket in employee identification information that identifies a plurality of employees to whom the ticket is granted. They may be stored in a storage device in association with each other.

In an information processing method according to another aspect of the present invention, when an order menu is selected by an employee, information regarding tickets that can be used at a restaurant for a plurality of employees is stored in association with each other. The method includes an output procedure for outputting information for displaying a discount amount and/or a discounted payment price by referring to information regarding the ticket assigned to the employee in the device.

In a program according to another aspect of the present invention, when an order menu is selected by an employee, information regarding tickets that can be used at a restaurant for a plurality of employees is stored in association with each other. A program for executing an output procedure for outputting information for displaying a discount amount and/or a post-discount payment price by referring to information regarding the ticket assigned to the employee in a storage device. be.

According to one aspect of the present invention, since it is possible to present a discounted amount and/or a discounted payment price to individual employees, it is possible to have employees use the restaurant like a company cafeteria. can be promoted.

1 is a schematic configuration diagram of an information processing system according to an embodiment. FIG. 1 is a schematic configuration diagram of an employee terminal according to the present embodiment. 1 is a schematic configuration diagram of a computer system according to an embodiment. FIG. 1 is a schematic configuration diagram of a company terminal according to the present embodiment. It is an example of the master table based on this embodiment. This is an example of a master table that is a continuation of FIG. 5. This is an example of the ticket management table T1-1. This is an example of the ticket management table T1-2. This is an example of ticket management table T1-3 and ticket management table T1-4. This is an example of a menu table for each restaurant and a menu table for company meals for each company. These are two examples of bulk ticket granting screens. These are two other examples of bulk ticket granting screens. These are still another example of the ticket batch granting screen and an example of the confirmation screen. 12 is a flowchart illustrating an example of the flow of processing for batch granting of tickets. This is an example of a menu selection screen for company meals. 12 is a flowchart illustrating an example of the flow of a company meal target menu selection process. This is an example of screen transitions on an employee terminal. This is a continuation of FIG. 17. It is a flowchart showing an example of the flow of search and order processing. This is a continuation of FIG. 19.

Each embodiment will be described below with reference to the drawings. However, more detailed explanation than necessary may be omitted. For example, detailed explanations of well-known matters or redundant explanations of substantially the same configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art.

In this embodiment, in order to encourage employees to use restaurants like company cafeterias, the company covers part of the cost of eating and drinking at restaurants, and offers discount tickets (hereinafter referred to simply as tickets). We will explain an information processing system that allows employees to eat and drink at a discounted price by issuing them a discounted price.

However, as the number of employees increases, the task of allocating tickets to each employee becomes complicated and labor-intensive. In addition, there is the problem that changing subsidy conditions such as subsidy rate depending on the employment type of the employee (for example, full-time employee, contract employee such as temporary worker, part-time worker, part-time worker, etc.) requires work and effort. . This embodiment solves these problems.

In this embodiment, as an example, an administrator using an administrator terminal will be described as being able to select a menu for company meals at a restaurant. Note that the present invention is not limited to this, and a person in charge of a restaurant using a terminal (not shown) may be able to select a menu for company meals at the restaurant.

FIG. 1 is a schematic configuration diagram of an information processing system according to this embodiment. As shown in FIG. 1, the information processing system S, for example, connects employee terminals 1-1 to 1-N (N is a natural number) and the employee terminals 1-1 to 1-N via a communication network CN. It includes a connected computer system 2 and company terminals 3-1, . . . , 3-M connected to the computer system 2 via a communication network CN.

Employee terminals 1-1 to 1-N (N is a natural number) are used, for example, by employees of one or more companies (for example, full-time employees, contract employees such as temporary employees, part-time workers, part-time workers, etc.). The terminal device is, for example, a mobile phone such as a multi-function mobile phone (so-called smart phone), a tablet, a notebook computer, or a desktop computer. For example, an application including a program according to the present embodiment is installed on the employee terminals 1-1 to 1-N, and by launching this application, information provided from the computer system 2 is displayed on the screen displayed by this application. Display the information that will be displayed. Note that the present invention is not limited to this, and the employee terminals 1-1 to 1-N may display information provided from the computer system 2 using, for example, a web browser. Hereinafter, in this embodiment, the employee terminal 1 will be explained as being a smartphone as an example.

The company terminals 3-1, ..., 3-M are, for example, terminal devices used by a person in charge of managing tickets in the company (hereinafter also referred to as a ticket management person), and are, for example, multifunctional mobile phones (so-called smartphones). mobile phones, tablets, personal computers (eg, laptops or desktop computers), etc. Here, as an example, the company terminals 3-1, . . . , 3-M will be explained as terminals of multiple companies, but one company may use multiple company terminals. Furthermore, if the system is dedicated to one specific company, the company terminals 3-1, . . . , 3-M may be terminals of that specific company. Hereinafter, in this embodiment, the company terminal 3 will be explained as a personal computer as an example.

Further, as an example, the computer system 2 is composed of one server. Note that the present invention is not limited to this, and the computer system 2 may be composed of a plurality of computers like a cloud service. Hereinafter, the employee terminals 1-1 to 1-N will be collectively referred to as employee terminals 1, and the company terminals 3-1, . . . , 3-M will also be collectively referred to as company terminals 3.

FIG. 2 is a schematic configuration diagram of the employee terminal according to this embodiment. As shown in FIG. 2, the employee terminal 1 includes, for example, an input interface 11, a communication module 12, a storage 13, a memory 14, a display 15, and a processor 16.
The input interface 11 receives input from a user and outputs an input signal to the processor 16 in accordance with the received input. The input interface 11 is, for example, a touch panel.
The communication module 12 is connected to the communication network CN and communicates with the computer system 2 connected to the communication network CN. This communication may be wired or wireless.

The storage 13 stores application programs and various data for the processor 16 to read and execute. This application was downloaded and installed on the computer system, for example via the cloud.
Memory 14 temporarily holds data and programs. The memory 14 is a volatile memory, such as RAM (Random Access Memory).

Display 15 displays information according to instructions from processor 16. Note that the display 15 may not be built into the employee terminal 1 but may be externally attached to the employee terminal 1.

The processor 16 loads the application program according to the present embodiment from the storage 13 into the memory 14, and executes a series of instructions included in the program, thereby creating a reception unit 161 that receives information from the employee terminal 1, etc. , a processing section 162, and a communication control section 163.

FIG. 3 is a schematic configuration diagram of a computer system according to this embodiment. As shown in FIG. 3, the computer system 2 includes an input interface 21, a communication circuit 22, a storage 23 that is an example of a storage device, a memory 24, an output interface 25, and a processor 26.
The input interface 21 receives input from the administrator of the computer system 2 and outputs an input signal to the processor 26 in accordance with the received input.
The communication circuit 22 is connected to the communication network CN and communicates with the employee terminals 1-1 to 1-N and company terminals 3-1 to 3-M connected to the communication network CN. This communication may be wired or wireless.

The storage 23 stores programs and various data for the processor 26 to read and execute.
Memory 24 temporarily holds data and programs. The memory 24 is a volatile memory, such as a RAM (Random Access Memory).
The processor 26 functions as an acquisition unit 261, a storage unit 262, an output unit 263, and a search unit 264 by loading a program from the storage 23 into the memory 24 and executing a series of instructions included in the program. The detailed processing will be described later.

FIG. 4 is a schematic configuration diagram of a company terminal according to this embodiment. As shown in FIG. 4, the company terminal includes, for example, an input interface 31, a communication module 32, a storage 33, a memory 14, an output interface 35, and a processor 36.
The input interface 31 receives input from a person in charge of ticket management at the company, and outputs an input signal to the processor 36 in accordance with the received input.
The communication module 32 is connected to the communication network CN and communicates with the computer system 2 connected to the communication network CN. This communication may be wired or wireless.

The storage 33 stores programs and various data for the processor 36 to read and execute.
Memory 14 temporarily holds data and programs. The memory 14 is a volatile memory, such as RAM (Random Access Memory).

The output interface 35 is connected to the external display 17 and outputs the video signal to the external display 17 according to instructions from the processor 36 . Note that the display 17 may be built into the company terminal 3 instead of being externally attached to the company terminal 3.

The processor 36 loads a program from the storage 33 into the memory 34 and executes a series of instructions included in the program, thereby providing a reception unit 361, a processing unit 362, and a communication control unit that accept information from the company terminal 3, etc. 363.
In this embodiment, as an example, the processor 36 displays information via a web browser.

Next, the master table will be explained using FIGS. 5 and 6. The storage 23 of the computer system 2 according to this embodiment stores a restaurant master table M1, a company master table M2, and an employee master table M3.

FIG. 5 is an example of a master table according to this embodiment. As shown in FIG. 5, the restaurant master table M1 includes the restaurant ID, which is an example of identification information for identifying a restaurant, the restaurant name, which is the name of the restaurant, the address of the restaurant, and the restaurant ID. URL, category tab representing the category of the restaurant, bank account information of the restaurant, photo (image) of the restaurant, email address of the restaurant, password for login, total number of users of the restaurant. A set of records is stored. As a result, for example, a person in charge of a restaurant can log into the system by entering an e-mail address and password at the time of login.

As shown in FIG. 5, the company master table M2 includes a company ID, which is an example of identification information for identifying a company, a company name, which is the name of the company, a password for login, an email address, and the address of the company. A set of records is stored. As a result, for example, a person in charge of ticket management at a company can log into the system by entering an e-mail address and password at the time of login.

FIG. 6 is an example of a master table that is a continuation of FIG. 5. As shown in FIG. 6, the employee master table M3 includes an employee ID, which is an example of identification information for identifying an employee, a company ID, a user name, a password, the employment type of the employee, and the birth of the employee. Records for the day group are stored. This allows, for example, an employee to log into the system by entering a username and password at login.

Next, the table will be explained using FIGS. 7 and 8. The storage 23 of the computer system 2 according to this embodiment stores ticket management tables T1-1, T1-2, T1-3, and T1-4, and a menu table T2-4 for each restaurant i (i is a natural number). i is memorized.

FIG. 7 is an example of the ticket management table T1-1. The ticket management table T1-1 is a ticket management table for "specifying ticket unit price and number of tickets". As shown in FIG. 7, the ticket management table T1-1 stores records including employee ID, company ID, ticket type, ticket price, number of tickets held, and valid period of use of the ticket. Thereby, for example, it is possible to manage tickets held by an employee who belongs to a company identified by a company ID and is identified by an employee ID. Here, the ticket types include, for example, "company meal (use of designated number of tickets)", which is a ticket with a specified number of tickets, and "internal exchange ticket", which is a ticket for internal exchange. The ticket price represents the subsidy amount that can be used for one meal.

FIG. 8 is an example of the ticket management table T1-2. The ticket management table T1-1 is a ticket management table for "specifying subsidy rate and specifying upper limit amount". As shown in FIG. 8, the ticket management table T1-2 includes employee ID, company ID, ticket type, discount rate, upper limit amount that can be used for the ticket, usage amount representing the amount that has already been used, and usage of the ticket. Records of possible period sets are accumulated. Thereby, for example, it is possible to manage tickets held by an employee who belongs to a company identified by a company ID and is identified by an employee ID. Here, the ticket type includes, for example, "company meal (specified upper limit amount)" which is a ticket with a specified upper limit amount.

FIG. 9 is an example of the ticket management table T1-3 and the ticket management table T1-4. The ticket management table T1-3 is a ticket management table for "specifying the number of times and specifying the upper limit price" for eating and drinking. As shown in FIG. 9, the ticket management table T1-3 includes the employee ID, company ID, ticket type, the maximum number of times the ticket can be used for food and drink, the number of times the ticket has already been used, the maximum amount of money that can be used with the ticket, Records are stored that include the amount of money used, which represents the amount of money that has already been spent, and the period during which the ticket can be used. Thereby, for example, it is possible to manage tickets held by an employee who belongs to a company identified by a company ID and is identified by an employee ID. Here, the ticket type includes, for example, "company meal (use specified number of times)," which is a ticket for which the number of times and the upper limit amount are specified.

The ticket management table T1-4 is a ticket management table for "specifying only the upper limit price (unlimited number of times)" for food and drink. As shown in FIG. 9, the ticket management table T1-4 includes the employee ID, company ID, ticket type, the upper limit amount that can be used for the ticket, the usage amount representing the amount that has already been used, and the usable period of the ticket. A set of records is stored. Thereby, for example, it is possible to manage tickets held by an employee who belongs to a company identified by a company ID and is identified by an employee ID. Here, the ticket type includes, for example, "company meal (specified upper limit amount)" which is a ticket with a specified upper limit amount.

FIG. 10 is an example of a menu table for each restaurant and a menu table for company meals for each company. As shown in FIG. 10, the menu table T2-i for each restaurant i (i is a natural number) includes a menu ID which is identification information for identifying the menu, a menu name which is the name of the menu, a photo of the menu, Records are stored including a description of the menu, a price (excluding tax) and a price (including tax) of the menu, a price flag, a company meal ticket target flag, a special allowance ticket target flag, and a reward ticket target flag. The price flag indicates whether to use the tax-inclusive price or the tax-exclusive price. The company meal ticket target flag indicates whether or not the menu is eligible for a company meal ticket. The special allowance ticket target flag indicates whether or not the menu is eligible for a special allowance ticket to be paid as a special allowance. The reward ticket target flag indicates whether or not the menu is eligible for a reward ticket given as a reward.

As shown in FIG. 10, the company meal target menu table T3-j for each company j (j is a natural number) includes, for example, a restaurant ID, a menu ID that identifies a company meal target menu, and whether or not it is a company meal target. A record of a set of company meal target flags indicating that the Thereby, the employee terminal 1 can store whether or not the menu in the company meal menu table T3-j of the company to which the employee belongs is eligible for company meals.

Next, an example of a screen displayed on the display 37 of the company terminal 3 when a ticket management person allocates tickets all at once from the company terminal 3 will be explained using FIGS. 11 to 13. FIG. 11 shows two examples of ticket batch granting screens. FIG. 12 shows two other examples of the ticket batch grant screen. FIG. 13 shows still another example of the ticket batch granting screen and an example of the confirmation screen.

The ticket batch granting screen G1 in FIG. 11 is a ticket batch granting screen when the ticket unit price and number of tickets are specified. On the ticket batch granting screen G1, a select box R1 for selecting an employment type is displayed, and tickets can be allotted for each employment type at once. Also displayed are radio buttons R2, R3, and R4 for specifying conditions for granting a ticket. The radio button R2 corresponding to "Do not specify date" is selected when the employee to whom the ticket is to be given is not specified based on the employee's birthday or joining date. The radio button R3 corresponding to "Specify by birthday" is selected when specifying the employee to whom the ticket will be given based on the employee's birthday. The birthday is specified in the select box R5. The radio button R4 corresponding to "Specify by joining date" is selected to specify the employee to whom the ticket will be given based on the employee's joining date. The joining date is specified in select box R6. This makes it possible to allocate tickets all at once for each employee's birthday or joining date.

On the ticket batch granting screen G1, a select box R7 for selecting a ticket type is displayed, and tickets can be assigned at once by specifying the ticket type.
Further, on the ticket bulk granting screen G1, a text box R8 for inputting a ticket price is displayed, and it is possible to designate a ticket price (that is, ticket unit price) and allocate tickets at once.
Further, on the ticket batch granting screen G1, a select box R9 for selecting the number of tickets to be given is displayed, and it is possible to designate the number of tickets to be given and allocate tickets at once.
In addition, on the ticket bulk grant screen G1, a total grant amount R10 is displayed, and when the ticket price and the number of tickets to be granted are specified above, this total grant amount R10 is displayed on the company terminal 3 or computer system 2. The amount multiplied by the ticket price and the number of tickets granted will be displayed.

In addition, a confirmation button R11 is displayed on the ticket batch granting screen G1, and when the confirmation button R11 is pressed, the record of tickets granted to each applicable employee is added to the ticket management table T1-1 by the computer system 2. will be generated and a confirmation screen will be displayed.

Subsequently, the ticket bulk granting screen G2 in FIG. 11 is a ticket bulk granting screen in the case where the subsidy rate and the upper limit amount are specified. On the ticket batch granting screen G2, a select box R21 for selecting an employment type is displayed, and tickets can be given for each employment type at once. Also displayed are radio buttons R22, R23, and R24 for specifying conditions for granting a ticket. The radio button R22 corresponding to "Do not specify date" is selected when the employee to whom the ticket is to be given is not specified based on the employee's birthday or joining date. The radio button R23 corresponding to "Specify by birthday" is selected when specifying the employee to whom the ticket will be given based on the employee's birthday. The birthday is specified in the select box R25. The radio button R24 corresponding to "Specify by joining date" is selected when specifying the employee to be given a ticket based on the employee's joining date, and when radio button R24 is selected, the option for selecting the joining date is The joining date is specified in the select box R26. This makes it possible to allocate tickets all at once for each employee's birthday or joining date.

On the ticket batch granting screen G2, a select box R27 for selecting a ticket type is displayed, and tickets can be assigned at once by specifying the ticket type.
Further, on the ticket bulk granting screen G2, a select box R28 for selecting a discount rate is displayed, and it is possible to designate the discount rate and allocate tickets all at once.
Further, on the ticket bulk granting screen G2, a text box R29 for inputting an upper limit amount is displayed, and tickets can be allotted at once by specifying the upper limit amount.
Further, on the ticket bulk grant screen G1, the grant amount is displayed in a text box R50, and the grant amount R30 is the upper limit amount input in the text box R29.

Also, on the ticket bulk granting screen G2, a confirmation button R31 is displayed, and when the confirmation button R31 is pressed, the computer system 2 creates a record of tickets granted to each applicable employee in the ticket management table T1-2. will be generated and a confirmation screen will be displayed.

Subsequently, the ticket batch granting screen G3 in FIG. 12 is a ticket batch granting screen in the case of specifying the number of times and specifying the upper limit amount. On the ticket batch granting screen G3, a select box R41 for selecting an employment type is displayed, and tickets can be given for each employment type at once. Also displayed are radio buttons R42, R43, and R44 for specifying conditions for granting a ticket. The radio button R42 corresponding to "Do not specify date" is selected when the employee to whom the ticket is to be given is not specified based on the employee's birthday or joining date. The radio button R43 corresponding to "Specify by birthday" is selected when specifying the employee to whom the ticket will be given based on the employee's birthday. The birthday is specified in the select box R45. The radio button R44 corresponding to "Specify by joining date" is selected when specifying the employee to whom the ticket will be given based on the employee's joining date. The joining date is specified in the select box R46. This makes it possible to allocate tickets all at once for each employee's birthday or joining date.

On the ticket batch granting screen G3, a select box R47 for selecting a ticket type is displayed, and tickets can be assigned at once by specifying the ticket type.
In addition, on the ticket bulk granting screen G3, a select box R48 for selecting the number of times is displayed, and it is possible to designate a discount rate and grant tickets all at once.
Further, on the ticket bulk granting screen G3, a text box R49 for inputting an upper limit amount is displayed, and tickets can be allotted at once by specifying the upper limit amount.
In addition, on the ticket bulk grant screen G3, the grant amount is displayed in a text box R50, and the maximum grant amount input in the text box R49 is displayed.

Also, on the ticket bulk granting screen G3, a confirmation button R51 is displayed, and when the confirmation button R51 is pressed, the computer system 2 creates a record of tickets granted to each applicable employee in the ticket management table T1-3. will be generated and a confirmation screen will be displayed.

Subsequently, the ticket bulk granting screen G4 in FIG. 12 is a ticket bulk granting screen when only the upper limit price for food and drink is specified and the number of times is unlimited. On the ticket batch granting screen G4, a select box R61 for selecting an employment type is displayed, and tickets can be given to each employment type at once. Also displayed are radio buttons R62, R63, and R64 for specifying conditions for granting tickets. The radio button R62 corresponding to "Do not specify date" is selected when the employee to whom the ticket is to be given is not specified based on the employee's birthday or joining date. The radio button R63 corresponding to "Specify by birthday" is selected when specifying the employee to whom the ticket will be given based on the employee's birthday. The birthday is specified in the select box R65. The radio button R64 corresponding to "Specify by joining date" is selected to specify the employee to whom the ticket will be given based on the employee's joining date. The joining date is specified in the select box R66. This makes it possible to allocate tickets all at once for each employee's birthday or joining date.

On the ticket batch granting screen G4, a select box R67 for selecting a ticket type is displayed, and tickets can be assigned at once by specifying the ticket type.
Further, on the ticket bulk granting screen G4, a text box R69 for inputting an upper limit amount is displayed, and tickets can be allotted at once by specifying the upper limit amount.
Further, on the ticket bulk grant screen G4, the grant amount is displayed in a text box R69, and the maximum amount inputted in the text box R49 is displayed as the grant amount.

Also, on the ticket bulk granting screen G4, a confirmation button R70 is displayed, and when the confirmation button R70 is pressed, the computer system 2 creates a record of tickets granted to each applicable employee in the ticket management table T1-4. will be generated and a confirmation screen will be displayed.

Subsequently, the ticket batch grant screen G5 in FIG. 13 is a ticket batch grant screen for specifying the ticket unit price, number of times, and usable period. On the ticket batch granting screen G5, a select box R71 for selecting an employment type is displayed, and tickets can be given to each employment type at once. Also displayed are radio buttons R72, R73, and R74 for specifying conditions for granting tickets. The radio button R72 corresponding to "Do not specify date" is selected when the employee to whom the ticket is to be given is not specified based on the employee's birthday or joining date. The radio button R73 corresponding to "Specify by birthday" is selected when specifying the employee to whom the ticket will be given based on the employee's birthday. The birthday is specified in the selection box R75. The radio button R74 corresponding to "specify by date of employment" is selected when specifying the employee to whom a ticket will be given based on the employee's date of employment. When radio button R74 is selected, the starting date of the joining date is specified in the select box R76 for selecting the starting date of the joining date, and the ending date of the joining date is specified in the select box R77 for selecting the ending date of the joining date. It is specified. This makes it possible to allocate tickets all at once for each employee's birthday or employment period.

On the ticket batch granting screen G5, a select box R78 for selecting a ticket type is displayed, and tickets can be assigned at once by specifying the ticket type.
In addition, on the bulk ticket allocation screen G5, select box R79 for specifying the start date of the usable period and select box R79E for selecting the end date of the usable period are displayed. You can give tickets to.
Further, on the ticket bulk granting screen G5, a text box R80 for inputting a ticket price is displayed, and tickets can be allotted all at once by specifying the ticket price (ie, ticket unit price).
Further, on the ticket batch granting screen G5, a select box R81 for selecting the number of tickets to be given is displayed, and it is possible to designate the number of tickets to be given and allocate tickets at once.

In addition, on the ticket bulk grant screen G5, the total grant amount is displayed in a text box R82 in an uneditable manner, and when the ticket price and the number of tickets to be granted are specified above, the total grant amount is displayed on the company terminal 3. Alternatively, the amount is automatically displayed by outputting the product of the ticket price and the number of tickets given on the computer system 2.
In addition, on the ticket batch granting screen G5, the number of tickets granted R83 is displayed in a text box R82 in an uneditable manner, and when the employment type and conditions are specified above, the computer system 2 stores the number of tickets granted in the employee master. It is automatically displayed by searching for employment conditions and employees matching the conditions in table M3 and outputting the number of employees.
In addition, on the ticket bulk grant screen G5, the total ticket grant amount is displayed in a text box R84 in an uneditable manner, and the computer system 2 or company terminal 3 calculates the value obtained by multiplying the total grant amount by the number of tickets to be granted. It will be displayed automatically by calculating and outputting it.

Also, on the ticket bulk granting screen G5, a confirmation button R85 is displayed, and when the confirmation button R85 is pressed, the record of the ticket granted to each applicable employee is added to the ticket management table T1-1 by the computer system 2. For example, the confirmation screen G6 shown in FIG. 13 is displayed. On the confirmation screen G6 of FIG. 13, the information selected or input on the ticket batch granting screen G5 is displayed.

Next, the flow of the process for allocating tickets in bulk will be explained using FIG. 14. FIG. 14 is a flowchart illustrating an example of the flow of processing for allocating tickets at once. The explanation will be made assuming that a screen for selecting one of the plurality of ticket allotment methods described above is displayed on the company terminal 3.

(Step S10) First, the processing unit 362 of the company terminal 3 determines whether the ticket batch granting method has been selected. If the person in charge of ticket management using the company terminal 3 selects the ticket batch granting method, this determination becomes true.

(Step S20) When the ticket batch grant method is selected in step S10, the communication control unit 363 of the company terminal 3 transmits information identifying the selected ticket batch grant method to the computer system 2.

(Step S30) When the output unit 263 of the computer system 2 receives the information identifying the ticket batch assignment method, it generates information for displaying the ticket batch assignment screen.

(Step S40) Next, the output unit 263 of the computer system 2 transmits information for displaying the ticket batch assignment screen to the company terminal 3.

(Step S50) Next, when the processing unit 362 of the company terminal 3 receives the information for displaying the ticket batch assignment screen, it uses this information to display the ticket batch assignment screen. As a result, one of the ticket batch granting screens G1 to G5 shown in FIGS. 11 to 13, for example, is displayed. Next, the processing unit 362 of the company terminal 3 determines whether or not the confirmation button has been pressed.

(Step S60) When the confirmation button is pressed in step S50, the communication control unit 363 transmits the information (for example, conditions, etc.) input on any of the ticket batch granting screens G1 to G5 in FIGS. 11 to 13 to the computer. Send to system 2.

(Step S70) Next, the computer system 2 receives the above-mentioned input information (that is, information for allocating tickets that can be used at a restaurant to a plurality of employees at once). At this time, the acquisition unit 261 acquires information for allocating tickets that can be used at the restaurant to multiple employees at once. More specifically, the acquisition unit 261 acquires a ticket granting method and settings corresponding to the ticket granting method.
When the storage unit 262 acquires the above information, the storage unit 262 associates the information regarding the tickets with the plurality of employees and stores the information in the storage 23, which is an example of a storage device. More specifically, the storage unit 262 is an example of a storage device that associates the accepted ticket granting method with settings corresponding to the ticket granting method for a plurality of employees to whom the tickets are given. Save it in a certain storage 23.

(Step S80)
The output unit 263 generates information for displaying a confirmation screen, and transmits this information for displaying a confirmation screen to the company terminal 3.

(Step S90) Next, when the processing unit 362 of the company terminal 3 receives information for displaying a confirmation screen, it displays a confirmation screen using this information. Next, the processing unit 362 determines whether the new registration button has been pressed on this confirmation screen (for example, confirmation screen G5 in FIG. 13).

(Step S100) If it is determined in step S80 that the new registration button has been pressed, a notification to the effect that the new registration button has been pressed is transmitted to the computer system 2.

(Step S110) When the storage unit 262 of the computer system 2 receives the press of the new registration button, it stores the ticket information to be given in association with the instructor ID of the employee who meets the conditions.

Next, the company meal menu selection screen displayed on the company terminal 3 will be described using FIG. 15. FIG. 15 is an example of a menu selection screen for company meals. As shown in FIG. 15, the menu selection screen G7 for company meals includes a radio button R91 corresponding to "Apply all menus" and a radio button R91 corresponding to "Select target menu" as menu selection for company meals. A button R92 is displayed, and a confirm button R93 is displayed. When the confirm button R93 is pressed while the radio button R91 corresponding to "Apply all menus" is selected, all the menus registered in each menu table T2-i will be applied to the logged in menu. It is registered in the company meal menu table T3 as the company meal menu for the company of the person in charge of ticket management.

On the other hand, when the radio button R92 corresponding to "Select target menu" is pressed and the confirm button R93 is pressed, the menu selected in the search result area R110 will be changed to the company cafeteria of the company of the ticket manager who is logged in. It is registered as a target menu in the company meal target menu table T3.

The company meal target menu selection screen G7 in FIG. 15 displays a search setting area R100, and includes a select box R101 from which the address of the restaurant can be selected, and a distance range of the restaurant from the location of the target company can be selected. Displayed are a select box R102, a select box R103 in which a menu price range can be selected, a text box R104 in which a restaurant name can be input, and a text box R105 in which a menu name can be input. When the search button R106 is pressed with these selected and/or input, a search is executed using the selected and/or input conditions, and the search results are displayed in the search result area R110.

Next, the flow of the company meal menu selection process will be described using FIG. 16. FIG. 16 is a flowchart illustrating an example of the flow of the company meal target menu selection process. The explanation will be made assuming that the company meal menu selection screen G7 as shown in FIG. 15 described above is displayed on the company terminal 3.

(Step S210) First, the processing unit 362 of the company terminal 3 determines whether or not the search button has been pressed on the company meal menu selection screen.

(Step S220) When the search button is pressed in step S210, the communication control unit 363 of the company terminal 3 transmits the search conditions input on the company meal menu selection screen to the computer system 2.

(Step S230) Next, when the output unit 263 of the computer system 2 receives the search condition, it generates information for displaying the search result screen according to the search condition. At this time, the output unit 263 extracts menus that match the search conditions from each menu table T2-i. At that time, if the address of a restaurant is included in the search conditions, the output unit 263 also refers to the restaurant master table M1, narrows down the restaurants to be searched, and menus of the narrowed restaurants. The search may be performed on table T2-i. In addition, if the search conditions include a distance range condition from the target company, for example, the output unit 263 uses the addresses in the restaurant master table M1 and the addresses in the company master table M2 to select individual restaurants from the target company. You may also determine the distance to. Then, for example, the output unit 263 may narrow down the search to restaurants whose determined distance falls within the distance range of the search condition, and search the menu table T2-i of the narrowed down restaurants.

The information for displaying the search result screen includes, for example, as shown in the search result area R110 of FIG. 15, information for displaying each menu item so that it can be selected whether or not to be included in a ticket. That is, the output unit 263 outputs information for displaying each menu item so that it can be selected as to whether or not it should be included in a ticket.

(Step S240) Next, the output unit 263 of the computer system 2 transmits information for displaying search results to the company terminal 3.

(Step S250) When the processing unit 362 of the company terminal 3 receives the information for displaying search results, it uses this information to display the search results as shown in the search result area R110 of FIG. Next, the processing unit 362 determines whether or not the confirm button has been pressed.

(Step S260) When the confirm button is pressed in step S250, the processing unit 362 determines, for example, whether the radio button R92 corresponding to "Select target menu" in FIG. 15 is selected. Alternatively, the processing unit 362 may determine, for example, whether the radio button R91 corresponding to "apply all menus" in FIG. 15 is selected.

(Step S270) If the radio button R92 corresponding to "Select target menu" in FIG. 15 is not selected in step S260 (that is, the radio button R91 corresponding to "Apply all menus" in FIG. 15 is selected) If the selected menu is selected), the communication control unit 363 sends a message to the computer system 2 that all menus have been selected.

(Step S280) When the storage unit 262 receives the notification that all the menus have been selected, it associates all the menu IDs with the company ID of the target company and stores them in the storage 23, for example.

(Step S290) If the radio button R92 corresponding to "Select target menu" in FIG. 15 is selected in step S260 (that is, the radio button R91 corresponding to "Apply all menus" in FIG. 15 is selected) If not, the communication control unit 363 transmits the company meal target flag for each menu ID to the computer system 2.

(Step S300) The acquisition unit 261 of the computer system 2 receives the company meal target flag for each menu ID, thereby providing selection information as to whether or not each menu is eligible for a ticket (here, as an example, the acquisition unit 261 for each menu ID Company meal target flag). Then, the storage unit 262 stores the company meal target flag for each menu ID in, for example, the storage 23 in association with the company ID that identifies the company of the person in charge of ticket management.

Next, screen transitions on the employee terminal will be explained using FIGS. 17 and 18. FIG. 17 is an example of screen transitions of the employee terminal. FIG. 18 is a continuation of FIG. 17.
As shown in FIG. 17, on the restaurant search screen G11, a select box R121 from which a ticket type can be selected is shown. This makes it possible to search for restaurants that have menus for the selected ticket type. On the restaurant search screen G11, a text box R122 is provided for inputting a keyword. This makes it possible to search using keywords (eg, "pasta", etc.). This makes it possible to search by menu name, for example. When the search button R123 is pressed, a search is executed and the search results are displayed.

When the employee selects one of the restaurants displayed in the search results on the restaurant search screen G11, the screen transitions to a menu list screen G12 of the selected restaurant. In this menu list screen G12, when a menu is selected from a plurality of menus, the screen transitions to a detailed screen G13 of the selected menu.

When the order button R124 on the menu details screen G13 is pressed, the screen changes to order screen information. Here, we will explain a case where the amount of subsidy (that is, the discount amount) from the company is set to be different for full-time employees and part-time employees even if they are in the same company. For example, if the employment type of the target employee is a full-time employee, a subsidy amount of 1,000 yen, for example, will be allocated, and if the target employee's employment type is part-time, a subsidy amount of 660 yen, for example, will be allocated. shall be.

In this case, if the target employee's employment status is full-time, order screen information G21 is displayed. In the order screen information G21, since the subsidy amount from the company is 1000 yen, the normal price is 1320 yen, but the subsidy amount of 1000 yen is subtracted and 320 yen is displayed as the payment amount at the store. The number of remaining tickets is also displayed. When the confirmation button R131 is pressed, the screen transitions to an order confirmation screen G22. For example, when the payment completion button R132 is pressed by the staff of the target restaurant, the screen transitions to the payment completion screen G41.

On the other hand, if the target employee's employment status is part-time, order screen information G31 is displayed. In the order screen information G31, since the subsidy amount from the company is 660 yen, the subsidy amount of 660 yen is subtracted from the normal price of 1320 yen, and 660 yen is displayed as the payment amount at the store. The number of remaining tickets is also displayed. When the confirmation button R141 is pressed, the screen changes to an order confirmation screen G32. For example, when the payment completion button R142 is pressed by the staff of the target restaurant, the screen transitions to the payment completion screen G41.

Next, the flow of search and order processing will be explained using FIGS. 19 and 20. FIG. 19 is a flowchart showing an example of the flow of search and order processing. FIG. 20 is a continuation of FIG. 19.

(Step S310) The processing unit 162 of the employee terminal 1 determines whether the search button has been pressed.

(Step S320) When the search button is pressed in step S310, the communication control unit 163 of the employee terminal 1 transmits the ticket type identification information and search conditions to the computer system 2.

(Step S330) When the output unit 263 of the computer system 2 receives the ticket type identification information and search conditions, it generates information for displaying search results.

(Step S340) The output unit 263 of the computer system 2 transmits the generated search result display information to the employee terminal 1.

(Step S350) When the processing unit 162 of the employee terminal 1 receives the information for displaying search results, it uses this information to display the search results on the restaurant search screen. As a result, a search result like the restaurant search screen G11 in FIG. 17 is obtained, for example. The processing unit 162 of the employee terminal 1 determines whether a restaurant has been selected on the restaurant search screen G11.

(Step S360) When a restaurant is selected in step S350, the communication control unit 163 of the employee terminal 1 transmits the restaurant ID that identifies the selected restaurant to the computer system 2.

(Step S370) When the output unit 263 of the computer system 2 receives this restaurant ID, it generates information for displaying a menu list screen of the restaurant identified by the restaurant ID.

(Step S380) The output unit 263 of the computer system 2 transmits the generated menu list screen display information to the employee terminal 1.

(Step S390) When the processing unit 162 of the employee terminal 1 receives the information for displaying the menu list screen, it displays the menu list screen using this information. As a result, the menu list screen G12 shown in FIG. 17, for example, is obtained. The processing unit 162 of the employee terminal 1 determines whether a menu is selected on the menu list screen.

(Step S400) When a menu is selected in step S390, the communication control unit 163 of the employee terminal 1 transmits a menu ID that identifies the selected menu to the computer system 2.

(Step S410) When the output unit 263 of the computer system 2 receives this menu ID, it generates information for displaying the menu details screen of the menu identified by this menu ID. At this time, the output unit 263 refers to the information regarding the ticket assigned to the employee and outputs information for displaying the discount amount and/or the discounted payment price. As an example, the output unit 263 outputs information for displaying the discount amount and/or the discounted payment price based on both the ticket type and ticket settings.

(Step S420) The output unit 263 of the computer system 2 transmits the generated information for displaying the menu details screen to the employee terminal 1.

(Step S430) When the processing unit 162 of the employee terminal 1 receives the information for displaying the menu details screen, it uses this information to display the menu details screen. As a result, the menu details screen G13 shown in FIG. 17, for example, is obtained. The processing unit 162 of the employee terminal 1 determines whether or not the order button has been pressed on the menu details screen.

(Step S440) If the order button is pressed in step S430, the communication control unit 163 of the employee terminal 1 transmits a notification to the computer system 2 that the order button has been pressed.

(Step S450) When the output unit 263 of the computer system 2 receives the press of the order button, the output unit 263 of the computer system 2 inputs, for example, the ticket management table T1-1 into the set of the employee ID and company ID of the target employee who uses the employee terminal. order screen information including the associated ticket price (i.e., subsidy amount or discount amount) is generated.

(Step S460) The output unit 263 of the computer system 2 transmits the generated order screen information to the employee terminal 1.

(Step S470) When the processing unit 162 of the employee terminal 1 receives the order screen information, it displays the order screen using this information. As a result, for example, the order screen G21 or the order screen G31 shown in FIG. 18 is obtained. The processing unit 162 of the employee terminal 1 determines whether or not the confirmation button has been pressed on the order screen.

(Step S480) If the confirmation button is pressed in step S470, the communication control unit 163 of the employee terminal 1 transmits a notification to the computer system 2 that the confirmation button has been pressed.

(Step S490) When the output unit 263 of the computer system 2 receives the press of the confirmation button, the output unit 263 of the computer system 2 stores the ticket associated with the set of the employee ID and company ID of the target employee in the ticket management table T1-1, for example. The number of sheets is reduced by one, and order confirmation screen information including the in-store payment amount is generated.

(Step S500) The output unit 263 of the computer system 2 transmits the generated order confirmation screen information to the employee terminal 1.

(Step S510) When the processing unit 162 of the employee terminal 1 receives the order confirmation screen information, it uses this information to display the order confirmation screen. As a result, for example, the order confirmation screen G22 or the order confirmation screen G32 shown in FIG. 18 is obtained. The processing unit 162 of the employee terminal 1 determines whether the payment button has been pressed on the order confirmation screen.

(Step S520) If the payment button is pressed in step S510, the communication control unit 163 of the employee terminal 1 transmits to the computer system 2 a notification that the payment button has been pressed.

(Step S530) When the output unit 263 of the computer system 2 receives the notification that the payment button has been pressed, it generates payment completion screen information.

(Step S540) The output unit 263 of the computer system 2 transmits the generated payment completion screen information to the employee terminal 1. When the processing unit 162 of the employee terminal 1 receives the payment completion screen information, it uses this information to display the payment completion screen. As a result, for example, the order confirmation screen G41 shown in FIG. 18 is obtained.

As described above, when an order menu is selected by an employee, the computer system 2 according to the present embodiment has a storage device (where information regarding tickets that can be used at a restaurant for a plurality of employees is stored in association with each other). Here, as an example, an output unit 263 that outputs information for displaying the discount amount and/or the discounted payment price by referring to information regarding the ticket assigned to the employee in the storage 23); Equipped with

As described above, the computer system 2 includes an acquisition unit 261 that acquires information for allocating tickets that can be used at a restaurant to multiple employees at once; The storage unit 262 may be provided to associate information regarding the ticket with respect to the employee and store it in a storage device (here, the storage 23 as an example).
With this configuration, by simply allocating tickets that can be used at a restaurant to multiple employees at once, it is possible to present discounted amounts and/or post-discount payment prices to individual employees. , it is possible to reduce the labor involved in issuing tickets that can be used at restaurants. This can encourage employees to use the restaurant like a company cafeteria.

As described above, the acquisition unit 261 acquires the ticket granting method and the settings corresponding to the ticket granting method, and the storage unit 262 stores the above-mentioned acceptance method for a plurality of employees to whom the tickets are given. The output unit 263 associates and stores the ticket granting method and the ticket settings, and the output unit 263 displays the discount amount and/or the discounted payment price based on both the ticket type and the ticket settings. Information may also be output.

Further, the acquisition unit 261 acquires selection information as to whether or not each menu is to be covered by a ticket, and the storage unit 262 is stored in the ticket manager When the acquisition unit 261 acquires a search condition from an employee, the search unit 264 searches for a restaurant that matches the search condition. You can also output the results.

In addition, when receiving the input for the batch grant, the acquisition unit 261 acquires the employment type of the employee to whom the grant is to be made, and the storage unit 262 identifies the employee corresponding to the acquired employment type. Information regarding the ticket may be associated with the employee identification information and stored in the storage device.

Further, the acquisition unit 261 specifies a birthday or joining date and acquires a selection to give the ticket for each birthday or joining date, and the storage unit 262 stores the ticket for each employee whose birthday or joining date corresponds to the received date. Information regarding the ticket may be associated with employee identification information for identifying the ticket and stored in the storage device.

Further, the acquisition unit 261 acquires the type of the ticket when acquiring information for the batch grant, and the storage unit 262 stores the received ticket for a plurality of employees to whom the ticket is granted. The type may be further associated and saved.

Further, the acquisition unit 261 acquires the usable period of the ticket from the administrator terminal, and the storage unit 262 stores the usable period of the ticket in employee identification information for identifying a plurality of employees to whom the ticket is given. may be stored in a storage device in association with each other.

Note that at least a part of the computer system 2 described in the above embodiment may be configured with hardware or software. When configured with software, a program for realizing at least part of the functions of the computer system 2 may be stored in a recording medium such as a flexible disk or a CD-ROM, and may be read and executed by the computer. The recording medium is not limited to a removable one such as a magnetic disk or an optical disk, but may also be a fixed recording medium such as a hard disk device or memory.

Furthermore, a program that implements at least some of the functions of the computer system 2 may be distributed via a communication line (including wireless communication) such as the Internet. Furthermore, the program may be distributed in an encrypted, modulated, or compressed state via a wired or wireless line such as the Internet, or stored in a recording medium.

Furthermore, the computer system 2 may be operated by one or more information processing devices. When using a plurality of information processing devices, one of the computer systems 2 may be a computer, and the computer may execute a predetermined program to realize the function as at least one means of the information processing system 1.

Further, some or all of the functions of the information processing system S may be executed by the terminal 1.

As described above, the present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the constituent elements can be modified and embodied without departing from the scope of the invention. Moreover, various inventions can be formed by appropriately combining the plurality of components disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments. Furthermore, components from different embodiments may be combined as appropriate.

1 Terminal 11 Input interface 12 Communication circuit 13 Storage 14 Memory 15 Display 16 Processor 161 Reception unit 162 Processing unit 163 Communication control unit 2 Computer system 21 Input interface 22 Communication circuit 23 Storage 24 Memory 25 Output interface 26 Processor 261 Acquisition unit 262 Storage unit 263 Output unit 264 Search unit S Information processing system

Claims (9)

When an order menu is selected by an employee, the information regarding the ticket assigned to the employee is stored in a storage device that stores information regarding tickets that can be used at a restaurant for multiple employees in an associated manner. an output unit that refers to the information and outputs information for displaying the discount amount and/or the discounted payment price;
an acquisition unit that acquires information for allocating tickets that can be used at a restaurant to multiple employees at once;
a storage unit that associates information regarding the ticket with the plurality of employees and stores it in the storage device when the information is acquired;
Equipped with
The acquisition unit displays a list of a plurality of menus of restaurants that match the search conditions specified by the ticket management person, and sends selection information as to whether or not each menu is eligible for a ticket to the ticket management person. Obtained by accepting the selection of the menu from the person in charge,
The storage unit stores, in a storage device, selection information as to whether or not each menu is eligible for a ticket in association with company identification information that identifies a company of the person in charge of ticket management;
An information processing system further comprising: a search unit that, when the acquisition unit acquires a search condition from an employee, searches for a restaurant that matches the search condition and outputs a search result. The search conditions include at least one of the location of the restaurant, the distance from the employee's company to the restaurant, the price range of the menu, the store name of the restaurant, and the name of the menu. The information processing system according to item 1. The acquisition unit acquires the ticket granting method and settings corresponding to the ticket granting method,
The storage unit associates and stores the received ticket granting method and the settings of the ticket for a plurality of employees to whom the ticket is granted;
The information processing system according to claim 1 or 2, wherein the output unit outputs information for displaying a discount amount and/or a discounted payment price based on both the ticket type and the ticket settings. When receiving input for the batch grant, the acquisition unit acquires the employment type of the employee to whom the grant is to be made;
The information processing according to any one of claims 1 to 3, wherein the storage unit associates information regarding the ticket with employee identification information for identifying an employee corresponding to the acquired employment type and stores it in a storage device. system. The acquisition unit specifies a birthday or a joining date and acquires a selection to grant the ticket for each birthday or joining date,
The storage unit stores information about the ticket in a storage device in association with employee identification information that identifies an employee whose date of birth or joining date corresponds to the received date of employment. information processing system. The acquisition unit acquires the type of the ticket when acquiring the information for the batch grant,
The information processing system according to any one of claims 1 to 5, wherein the storage unit further associates and stores the type of the received ticket with respect to a plurality of employees to whom the ticket is given. The acquisition unit acquires the usable period of the ticket,
The storage unit stores employee identification information for identifying a plurality of employees to whom the ticket is granted in a storage device in association with the usable period of the ticket. Information processing system. When the order menu is selected by the employee, the computer is assigned to the employee in a storage device in which information regarding tickets available at the restaurant for multiple employees is associated and stored. an output step of outputting information for displaying a discount amount and/or a post-discount payment price with reference to information regarding the ticket;
an acquisition step in which the computer acquires information for collectively allocating tickets that can be used at a restaurant to multiple employees;
a storage step in which, when the information is acquired, the computer associates information regarding the ticket with the plurality of employees and stores it in the storage device;
Run
The acquisition procedure includes displaying a list of multiple menus of restaurants that match the search conditions specified by the ticket management person, and selecting information as to whether or not to include each menu as a ticket object. Obtained by accepting the selection of the menu from the person in charge,
The storing step stores selection information as to whether or not each menu is to be ticketed in a storage device in association with company identification information that identifies the company of the person in charge of ticket management;
An information processing method further comprising : when a computer acquires a search condition from an employee in the acquisition step, a search step of searching for a restaurant that matches the search condition and outputting a search result. to the computer,
When an order menu is selected by an employee, the information regarding the ticket assigned to the employee is stored in a storage device that stores information regarding tickets that can be used at a restaurant for multiple employees in an associated manner. an output procedure for outputting information for displaying a discount amount and/or a post-discount payment price by referring to the information;
an acquisition procedure for acquiring information for allocating tickets that can be used at a restaurant to multiple employees at once;
When the information is acquired, a storage step of associating information regarding the ticket with the plurality of employees and storing it in the storage device;
including;
The acquisition procedure includes displaying a list of multiple menus of restaurants that match the search conditions specified by the ticket management person, and selecting information as to whether or not to include each menu as a ticket object. Obtained by accepting the selection of the menu from the person in charge,
The storing step stores selection information as to whether or not each menu is to be ticketed in a storage device in association with company identification information that identifies the company of the person in charge of ticket management;
A program for causing a computer to execute a procedure further comprising: a search procedure for, when the computer acquires a search condition from an employee in the acquisition procedure, searching for a restaurant that matches the search condition and outputting a search result.