JP7127918B2 - Program, information processing method and information processing apparatus - Google Patents

Description

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

Patent Literature 1 discloses an information processing device that realizes systematization of tip payment.

JP 2019-139278 A

However, the invention according to Patent Literature 1 has a problem that it is not possible to distribute the chips acquired from the payers (customers) who pay the chips.

One aspect is to provide a program or the like capable of appropriately distributing acquired chips to a plurality of parties.

A program related to one aspect acquires the tip amount paid by a customer to a waiter for consumption at a restaurant, and calculates the total tip amount within a predetermined period for each restaurant based on the acquired tip amount. Then, the transaction fee related to the tip allocation is calculated according to a predetermined standard, and the calculated transaction fee is subtracted from the calculated total tip amount, and based on the tip allocation rules established for each restaurant, the tip is distributed to the restaurant. The computer is caused to execute a process of calculating the amount to be allocated to each of the recipients, and outputting the calculated total tip amount and the amount to be allocated to each recipient to the terminal of the restaurant.

In one aspect, earned chips can be appropriately distributed among multiple parties.

It is an explanatory view showing an outline of a chip distribution system. It is a block diagram which shows the structural example of a server. It is explanatory drawing which shows an example of the record layout of restaurant DB. FIG. 4 is an explanatory diagram showing an example of a record layout of an allottee DB and an allocation history DB; FIG. 4 is an explanatory diagram showing an example of record layouts of a payment history DB and an incentive history DB; FIG. 4 is an explanatory diagram showing an example of a record layout of a work management DB; 3 is a block diagram showing a configuration example of a customer terminal; FIG. It is a block diagram which shows the structural example of a store terminal. It is explanatory drawing which shows the processing operation of a chip distribution system. FIG. 10 is a flow chart showing a processing procedure for specifying incentives according to tip payments; FIG. FIG. 11 is a flow chart showing a processing procedure when displaying a tip payment history and an incentive acquisition history; FIG. FIG. 10 is a flow chart showing a processing procedure when allocating the amount of chips to a recipient; FIG. FIG. 10 is an explanatory diagram showing an example of a reception screen for selecting a waiter; FIG. 10 is an explanatory diagram showing an example of a reception screen for inputting a tip amount; FIG. 10 is an explanatory diagram showing an example of an incentive display screen; It is explanatory drawing which shows an example of the display screen of a payment history and an acquisition history. FIG. 11 is an explanatory diagram showing an example of a display screen of allocation history; FIG. 10 is a flow chart showing a processing procedure for displaying incentives and allocation ratios in accordance with the input timing of the tip amount; FIG. FIG. 11 is an explanatory diagram showing an example of a reception screen for inputting a tip amount according to the second embodiment; FIG. 10 is an explanatory diagram showing an example of a display screen of ranking results for restaurants; FIG. 11 is an explanatory diagram showing an example of a display screen of ranking results for allottees; FIG. 14 is a flow chart showing a processing procedure when specifying an incentive according to tip payment in Embodiment 4. FIG. FIG. 21 is an explanatory diagram showing an example of a display screen of ranking results for restaurants according to the fourth embodiment; 10 is a flow chart showing a processing procedure for calculating the allocation amount of a waiter; FIG. 12 is a block diagram showing a configuration example of a server according to Embodiment 6; FIG. 10 is an explanatory diagram showing an example of a record layout of a transfer history DB; FIG. 10 is a flow chart showing a processing procedure for transferring incentives; FIG.

Hereinafter, the present invention will be described in detail based on the drawings showing its embodiments.

(Embodiment 1)
Embodiment 1 relates to a mode of allocating the tip amount paid by a customer to a waiter at a restaurant. A waiter is a person who takes care of a customer's meal, etc. in a place where eating and drinking is provided, and is also called a server, a waiter, or a waitress. FIG. 1 is an explanatory diagram showing an overview of the chip distribution system. The system of this embodiment includes an information processing device 1, an information processing terminal 2, and an information processing terminal 3, and each device transmits and receives information via a network N such as the Internet.

The information processing device 1 is an information processing device that processes, stores, and transmits/receives various information. The information processing device 1 is, for example, a server device, a personal computer, or the like. In the present embodiment, the information processing device 1 is assumed to be a server device, which is replaced with the server 1 for the sake of brevity.

The information processing terminal 2 receives the selection of the waiter who serves the customer, receives the input of the tip amount to be paid to the waiter, and receives and displays incentives obtained in accordance with the payment of the tip. It is a terminal device that performs The information processing terminal 2 is, for example, an information processing device such as a smart phone, a mobile phone, a wearable device such as Apple Watch (registered trademark), a tablet, or a personal computer terminal. The information processing terminal 2 may be an ordering tablet or a self-ordering terminal installed in a restaurant. For the sake of brevity, the information processing terminal 2 is replaced with the customer terminal 2 below.

The information processing terminal 3 is a terminal device that receives and displays the total tip amount within a predetermined period for each restaurant and the amount distributed to each recipient of the restaurant. The information processing terminal 3 is, for example, an information processing device such as a smart phone, a mobile phone, a wearable device such as Apple Watch, a tablet, or a personal computer terminal. For the sake of brevity, the information processing terminal 3 is replaced with the store terminal 3 below.

The server 1 according to this embodiment acquires the accepted waiter information and the tip amount paid by the customer to the waiter from the customer terminal 2 . The server 1 identifies an incentive set according to the acquired tip amount, and transmits the identified incentive to the customer terminal 2 . The server 1 distributes the amount of chips obtained within a predetermined period to a plurality of recipients of the restaurant based on a tip distribution rule determined for each restaurant. The server 1 stores the allocation history of the amount of the tip in the storage unit.

FIG. 2 is a block diagram showing a configuration example of the server 1. As shown in FIG. The server 1 includes a control section 11 , a storage section 12 , a communication section 13 , an input section 14 , a display section 15 , a reading section 16 and a mass storage section 17 .
Each configuration is connected by a bus B.

The control unit 11 includes arithmetic processing units such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). , various information processing, control processing, etc. related to the server 1 are performed. Note that although FIG. 2 illustrates the controller 11 as a single processor, it may be a multiprocessor.

The storage unit 12 includes memory elements such as RAM (Random Access Memory) and ROM (Read Only Memory), and stores the control program 1P or data necessary for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data and the like necessary for the control unit 11 to perform arithmetic processing. The communication unit 13 is a communication module for performing processing related to communication, and transmits/receives information to/from the customer terminal 2, the store terminal 3, and the like via the network N.

The input unit 14 is an input device such as a mouse, keyboard, touch panel, buttons, etc., and outputs received operation information to the control unit 11 . The display unit 15 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the control unit 11 .

The reader 16 reads a portable storage medium 1a including CD (Compact Disc)-ROM or DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 16 and store it in the large-capacity storage unit 17 . Alternatively, the control unit 11 may download the control program 1P from another computer via the network N or the like and store it in the large-capacity storage unit 17 . Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

The large-capacity storage unit 17 includes a recording medium such as an HDD (Hard disk drive) or an SSD (Solid State Drive). The large-capacity storage unit 17 includes a restaurant DB 171 , an allotted person DB 172 , an allocation history DB 173 , a payment history DB 174 , an incentive history DB 175 and a work management DB 176 . The restaurant DB 171 stores information about restaurants. The allottee DB 172 stores information on allottees to whom the tip amount is to be allocated. The allocation history DB 173 stores the allocation history of tip amounts. The payment history DB 174 stores the payment history of tip amounts paid by customers to waiters. The incentive history DB 175 stores an incentive issuance history. The work management DB 176 stores information such as working hours of workers working at restaurants.

In addition, in this embodiment, the storage unit 12 and the large-capacity storage unit 17 may be configured as an integrated storage device. Also, the large-capacity storage unit 17 may be composed of a plurality of storage devices. Furthermore, the large-capacity storage unit 17 may be an external storage device connected to the server 1 .

In this embodiment, the server 1 is described as a single information processing device, but it may be distributed to a plurality of devices, or may be composed of virtual machines.

FIG. 3 is an explanatory diagram showing an example of the record layout of the restaurant DB 171. As shown in FIG. The restaurant DB 171 includes a restaurant ID column, a restaurant name column, a thumbnail image column, a dish type column, a tip allocation rule column, and an incentive condition column. The restaurant ID column stores unique restaurant IDs for identifying each restaurant. The restaurant name column stores the names of restaurants. The thumbnail image column stores thumbnail images of restaurants. The food type column stores the food type (genre) of the restaurant.

The tip distribution rule column stores tip distribution rules determined for each restaurant. The tip distribution rule is, for example, "Owner: 55% of the total tip amount, Waiter: 25% of the tip earned by himself, Chef: 15% of the total tip amount, weighted average of working hours, Transaction fee: 5% of the total tip amount. %” or the like.

The incentive condition column stores incentive conditions (issue conditions) for tips for each restaurant. The incentive conditions are incentive issuance conditions or details that are set according to the tip amount. For example, the incentive condition is "a meal coupon worth 200% of the tip amount". The incentive conditions are not limited to the tip amount, and may be set according to, for example, the number of tip payments.

FIG. 4 is an explanatory diagram showing an example of the record layout of the allocated person DB 172 and the allocation history DB 173. As shown in FIG.
The allocated person DB 172 includes an allocated person ID column, a name column, a photo column, a restaurant ID column, a type column, and an employee ID column. The allocated person ID column stores the unique ID of the allocated person in order to identify each allocated person. The recipient is the restaurant owner, the waiter who serves the customers, or the cook who prepares the food. The name column stores the names of allottees.

The photo column stores the photo of the allottee. In addition, a photograph is not essential, and an avatar (portrait) or a blank may be used. The restaurant ID column stores restaurant IDs for specifying restaurants. The type column stores the classification information of allottees. Types include, for example, owner, waiter and cook. The employee ID column stores employee IDs of waiters, chefs, and the like.

The allocation history DB 173 includes an allocation ID column, an allocation target year/month column, an allocation date/time column, a restaurant ID column, a total tip amount column, an allottee ID column, an earned amount column, an allocation amount column, and a transaction fee column. The distribution ID column stores IDs of uniquely specified distribution history data in order to identify each distribution history data. The allocation target year/month column stores the target year/month to which the tip amount is allocated. The allocation date and time column stores information on the date and time when the tip amount was distributed. The restaurant ID column stores restaurant IDs for specifying restaurants.

The total tip amount column stores the total tip amount obtained for each target year and month. The distributed party ID column stores the distributed party ID for specifying the distributed party. The earned amount column stores the amount of tips earned by each waiter for each target year and month. Note that if the recipient is the owner or the chef, 0 yen, "-", or a blank may be stored in the earned amount column. The distribution amount column stores the distribution amount to each distributed person for each distribution target year and month. The transaction fee column stores transaction fees associated with tip allocation.

FIG. 5 is an explanatory diagram showing an example of the record layout of the payment history DB 174 and the incentive history DB 175. As shown in FIG.
The payment history DB 174 includes a payment ID column, a customer ID column, a payee column and a payment date and time column. The payment ID column stores the ID of the payment history data that is uniquely specified in order to identify the payment history data of each tip amount. The customer ID column stores customer IDs for identifying customers.

The payment destination column includes a restaurant ID column, an employee ID column, and a tip amount column. The restaurant ID column stores the restaurant ID of the restaurant to which the waiter to whom the customer paid the tip belongs. The employee ID column stores the employee ID of the waiter. The tip amount column stores the amount of tip paid by the customer to the waiter. The payment date and time column stores the date and time information when the customer paid the tip amount.

The incentive history DB 175 stores the history of incentives obtained according to the amount of tip paid by the customer to the waiter. Incentives include, for example, coupons, exchange coupons, discount coupons, gift certificates, point rewards, and the like. The incentive history DB 175 includes an incentive ID column, a type column, a content column, an issue restaurant ID column, an issue date and time column, an expiration date column, a use state column, and a payment ID column.

The incentive ID column stores a unique incentive ID to identify each incentive. The type column stores types of incentives. Types of incentives include, for example, meal coupons and drink coupons. The content column stores the content of the incentive. The issuing restaurant ID column stores restaurant IDs for specifying restaurants that have issued incentives.

The date and time of issue column stores information on the date and time when the incentive was issued. The expiration date column stores the expiration date of the issued incentive. The usage status column stores the usage status of the issued incentive (for example, unused or used). The payment ID column stores payment IDs for specifying tip payment history data.

FIG. 6 is an explanatory diagram showing an example of the record layout of the work management DB 176. As shown in FIG. The work management DB 176 includes a restaurant ID column, a date column, an employee ID column, an office arrival time column, an office leaving time column, and a working time column. The restaurant ID column stores restaurant IDs for specifying restaurants. The date column stores the working days of the restaurant. The employee ID column stores employee IDs of waiters, chefs, and the like. The arrival time column stores the time when the employee came to work. The leaving time column stores the time when the employee left the office. The working hours column stores the number of hours the employee worked in one day.

FIG. 7 is a block diagram showing a configuration example of the customer terminal 2. As shown in FIG. The customer terminal 2 includes a control section 21 , a storage section 22 , a communication section 23 , an input section 24 , a display section 25 and a photographing section 26 . Each configuration is connected by a bus B.

The control unit 21 includes an arithmetic processing unit such as a CPU and an MPU, and reads out and executes the control program 2P stored in the storage unit 22 to perform various information processing, control processing, etc. related to the customer terminal 2 . In addition, although the controller 21 is described as a single processor in FIG. 7, it may be a multiprocessor. The storage unit 22 includes memory elements such as RAM and ROM, and stores the control program 2P or data necessary for the control unit 21 to execute processing. The storage unit 22 also temporarily stores data and the like necessary for the control unit 21 to perform arithmetic processing.

The communication unit 23 is a communication module for performing processing related to communication, and transmits/receives information to/from the server 1 or the like via the network N. The input unit 24 may be a keyboard, a mouse, or a touch panel integrated with the display unit 25 . The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 21 .

The imaging unit 26 is an imaging device such as a CCD (Charge Coupled Device) camera, a CMOS (Complementary Metal Oxide Semiconductor) camera, or the like. Note that the photographing unit 26 may be configured by a plurality of photographing devices. Note that the photographing unit 26 may not be built in the customer terminal 2, but may be directly connected to the customer terminal 2 externally so as to be capable of photographing.

FIG. 8 is a block diagram showing a configuration example of the store terminal 3. As shown in FIG. The store terminal 3 includes a control section 31 , a storage section 32 , a communication section 33 , an input section 34 and a display section 35 . Each configuration is connected by a bus B.

The control unit 31 includes an arithmetic processing device such as a CPU and an MPU, and reads out and executes a control program 3P stored in the storage unit 32 to perform various information processing, control processing, etc. related to the store terminal 3 . Note that although FIG. 8 describes the controller 31 as a single processor, it may be a multiprocessor. The storage unit 32 includes memory elements such as RAM and ROM, and stores the control program 3P or data necessary for the control unit 31 to execute processing. The storage unit 32 also temporarily stores data and the like necessary for the control unit 31 to perform arithmetic processing.

The communication unit 33 is a communication module for performing processing related to communication, and transmits/receives information to/from the server 1 or the like via the network N. The input unit 34 may be a keyboard, a mouse, or a touch panel integrated with the display unit 35 . The display unit 35 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 31 .

FIG. 9 is an explanatory diagram showing the processing operation of the chip distribution system. A customer terminal 2 accepts selection of a waiter who serves customers at a restaurant. The customer terminal 2 identifies the waiter based on the information about the selected waiter. Specifically, for example, the customer terminal 2 acquires the employee IDs of all the waiters at the restaurant from the distributed person DB 172 based on the restaurant ID. The customer terminal 2 acquires the waiter working that day from the work management DB 176 based on the acquired employee ID of the waiter. The customer terminal 2 displays the acquired wait staff working that day on a wait staff selection acceptance screen (FIG. 13), which will be described later. The customer terminal 2 acquires information about the selected waiter when receiving the waiter's selection from the reception screen for the waiter's selection by the customer (the waiter list of the restaurant). Information about the waiter includes, for example, an employee ID or name. In this embodiment, as an example, the information about the waiter is the employee ID. The customer terminal 2 identifies the waiter based on the acquired employee ID.

Alternatively, the waiter can be identified through a code describing the waiter's employee ID. The code is, for example, a two-dimensional code, a one-dimensional code, or the like. A two-dimensional code is a display type code that has information in the horizontal and vertical directions, as opposed to a one-dimensional code that has information only in the horizontal direction. Typical two-dimensional codes are, for example, QR Code (registered trademark), DataMatrix (registered trademark) or VeriCode (registered trademark). A one-dimensional code is, for example, a bar code.

For example, when a two-dimensional code describing an employee ID is distributed to each waiter working in a restaurant, the customer terminal 2, via the image capturing unit 26, sends the Read the two-dimensional code. The customer terminal 2 uses a two-dimensional code analysis library to acquire the employee ID of the waiter from the read two-dimensional code. The customer terminal 2 identifies the waiter based on the acquired employee ID.

The customer terminal 2 accepts the input of the tip amount to be paid to the selected (specified) waiter. The tip amount may be, for example, 15-20% of the meal price, or may be any amount. The customer terminal 2 transmits to the server 1 the employee ID of the selected waiter, the tip amount paid to the waiter, the restaurant ID to which the waiter belongs, and the customer ID.

The server 1 receives the employee ID of the waiter, the tip amount, the restaurant ID and the customer ID transmitted from the customer terminal 2 . The server 1 acquires (issues) an incentive set according to the amount of the received tip. Specifically, the server 1 acquires the pre-registered incentive conditions from the restaurant DB 171 based on the restaurant ID. The server 1 issues an incentive to the customer who paid the tip amount to the waiter based on the acquired incentive conditions. For example, assuming that the incentive condition is "a meal coupon for 200% of the tip amount", the server 1 determines that the received tip amount is "500 yen", for example, if the server 1 determines that the tip amount is "500 yen", We will issue a meal coupon for "Yen".

The server 1 stores a tip payment history and an incentive acquisition history corresponding to the tip payment. Specifically, the server 1 assigns a payment ID, and pays the customer ID, the restaurant ID, the waiter's employee ID, the tip amount paid by the customer to the waiter, and the payment date and time as one record. Stored in history DB 174 . The server 1 allocates an incentive ID, stores the type of incentive, its content, the restaurant ID that issued the incentive, the date and time of issuance, the expiration date, and the status of use as one record in the incentive history DB 175 in association with the payment ID. . Since the incentive is newly issued, "unused" or blank may be stored in the usage status column.

The server 1 transmits the incentive issued to the customer to the customer terminal 2 . The customer terminal 2 receives the incentive transmitted from the server 1 and displays the received incentive.

Next, processing for allocating the amount of chips acquired within a predetermined period to a plurality of recipients of the restaurant based on the tip distribution rule determined for each restaurant will be described. The recipient is the person to whom the tip amount is distributed. In the present embodiment, an example has been described in which the person to be allocated is the owner of a restaurant, a waiter who serves customers, or a cook who prepares food, but it is not limited to this. A person to be allocated may be, for example, a store manager who manages the operation of a restaurant, that is, it may be arbitrarily set according to actual needs.

The tip distribution rule describes information such as the distribution ratio for distributing the tip amount obtained from the customer to each recipient. The tip distribution rule is, for example, "Owner: 55% of the total tip amount, Waiter: 25% of the tip earned by himself, Chef: 15% of the total tip amount, weighted average of working hours, Transaction fee: 5% of the total tip amount. %” may be used. In this embodiment, an example in which a tip distribution rule is defined for each restaurant has been described, but the present invention is not limited to this, and a common tip distribution rule may be defined for the entire tip distribution system.

The server 1 acquires the tip distribution rule of the restaurant from the restaurant DB 171 based on the restaurant ID. The server 1 tabulates (calculates) the total tip amount within a predetermined period from the payment history DB 174 based on the payment date and time of the tip. The predetermined period of time may be, for example, one day, one week, one month or quarter. In this embodiment, an example in which the predetermined period is one month will be described.

The server 1 calculates a transaction fee related to tip allocation based on the acquired tip allocation rule. For example, if the tip distribution rule describes a fee collection standard of "5% of the total tip amount", a transaction fee of 5,000 yen will be collected for a total tip amount of 100,000 yen. The server 1 deducts the calculated transaction fee from the total tip amount. The server 1 calculates the amount to be distributed to each recipient based on the distribution ratio defined in the chip distribution rule.

Below, the calculation of the distribution amount based on the above-mentioned tip distribution rule (owner: 55% of the total tip amount, waiter: 25% of the tip earned by himself, chef: 15% of the total tip amount, weighted average of working hours) Processing will be explained. When the allocation ratio to the owner is 55% of the total tip amount, the allocation amount to the owner is 55,000 yen (100,000 yen×55%) for the total tip amount of 100,000 yen. Also, if the allocation ratio to the waiter is 25% of the amount of chips earned by the waiter, for example, the amount of chips earned by waiter A is 30,000 yen, and the amount allocated to waiter A is 7,500 yen (30,000 yen). circle x 25%).

In addition, the amount allocated to the chef is calculated by the weighted average of working hours, and is expressed by the following formula (1). Amount allocated to chefs = Total tip amount × Ratio allocated to chefs × (Working hours/Total working hours) …(1)

The working hours are the working hours of the target cook. Total working time is the working time of all the cooks working in the restaurant. For example, if three chefs (Mr. A, Mr. B, and Mr. C) are working at a restaurant AAA, the number of working hours of Mr. A within a predetermined period (for example, one month) is 60 hours, Mr. B's working hours are 100 hours, and Mr. C's working hours are 40 hours. For Mr. A, the working hours are 60 hours, and the total working hours are 200 (60+100+40) hours.

Based on the employee ID of each chef, the server 1 aggregates working hours of each chef within a predetermined period from the work management DB 176 . The server 1 calculates the amount to be allocated to each chef based on the aggregated working hours using the formula (1) described above. For example, with respect to the total tip amount of 100,000 yen, the amount to be distributed to Chef A is calculated to be 7,500 yen (100,000×25%×(60/200)).

The server 1 stores the chip allocation history in the allocation history DB 173 . Specifically, the server 1 allocates allocation IDs, allocation target year and month, allocation date and time, restaurant ID, total tip amount corresponding to allocation target year and month, allocationee ID, amount earned by allocationee, The allocation history DB 173 stores the allocation amount and the transaction fee to the allocation recipient as one record. The server 1 transmits the total tip amount within a predetermined period and the allocation amount to each recipient to the store terminal 3 of each restaurant. The store terminal 3 receives and displays the total amount of chips within a predetermined period transmitted from the server 1 and the amount to be distributed to each recipient.

The server 1 remits the total tip amount after deducting the transaction fee at a specified date and time (for example, at the end of the month) to the store account of each restaurant via a bank system, electronic money, QR code settlement, or the like. After that, the owner of each restaurant confirms the payment to the store account and remits to the account of each recipient. For example, the server 1 may directly remit money to each recipient's account without limiting to the batch remittance to the store account.

FIG. 10 is a flow chart showing a processing procedure for specifying incentives according to tip payments. The control unit 21 of the customer terminal 2 receives the selection of the waiter from the waiter list by the customer via the input unit 24 (step S201). The control unit 21 receives an input of the tip amount to be paid to the selected waiter through the input unit 24 (step S202). The control unit 21 transmits, via the communication unit 23, the tip payment information including the employee ID of the selected waiter, the tip amount paid to the waiter, the restaurant ID to which the waiter belongs, and the customer ID. is sent to the server 1 (step S203).

The control unit 11 of the server 1 receives the tip payment information transmitted from the customer terminal 2 through the communication unit 13 (step S101). The control unit 11 identifies an incentive set according to the tip amount included in the received tip payment information (step S102). Specifically, the control unit 11 acquires the pre-registered incentive conditions from the restaurant DB 171 of the large-capacity storage unit 17 based on the restaurant ID. The control unit 11 identifies the incentive to be issued to the customer based on the acquired incentive conditions.

The control unit 11 assigns a payment ID, and pays the payment history including the customer ID, the restaurant ID, the waiter's employee ID, the tip amount paid by the customer to the waiter, and the date and time of payment as one record. Store in the history DB 174 (step S103). The control unit 11 assigns an incentive ID, and associates the incentive acquisition history including the incentive type, content, restaurant ID that issued the incentive, issue date, expiration date, and usage status with the payment ID as one record. Stored in the incentive history DB 175 (step S104).

The control unit 11 transmits the specified incentive to the customer terminal 2 through the communication unit 13 (step S105). The control unit 21 of the customer terminal 2 receives the incentive transmitted from the server 1 by the communication unit 23 (step S204), displays the received incentive on the display unit 25 (step S205), and ends the process.

FIG. 11 is a flowchart showing a processing procedure for displaying tip payment history and incentive acquisition history. The control unit 21 of the customer terminal 2 transmits the customer ID to the server 1 through the communication unit 23 (step S211). The control unit 11 of the server 1 receives the customer ID transmitted from the customer terminal 2 through the communication unit 13 (step S111). Based on the received customer ID, the control unit 11 acquires the payment history of tips within a specified period (for example, one month, half a year, etc.) or the entire period from the payment history DB 174 of the large-capacity storage unit 17 (step S112). . The payment history includes information on the destination of the tip payment (for example, the name of the restaurant, the name of the waiter, the amount of the tip, etc.), the payment date and time, and the like.

Based on the payment ID included in the acquired payment history, the control unit 11 acquires the history of incentives issued by each restaurant from the incentive history DB 175 of the large-capacity storage unit 17 (step S113). The history of incentives includes incentive IDs, types (for example, meal coupons, etc.), contents, issuing restaurant IDs, issuing dates and times, expiration dates, usage states, and the like.

The control unit 11 transmits the acquired tip payment history and incentive acquisition history to the customer terminal 2 through the communication unit 13 (step S114). The control unit 21 of the customer terminal 2 receives the tip payment history and the incentive acquisition history transmitted from the server 1 through the communication unit 23 (step S212). The control unit 21 displays the received chip payment history and incentive acquisition history on the display unit 25 (step S213), and ends the process.

FIG. 12 is a flow chart showing the procedure for allocating the amount of chips to the recipients. Based on the restaurant ID, the control unit 11 of the server 1 acquires the tip distribution rule of the restaurant from the restaurant DB 171 of the large-capacity storage unit 17 (step S121). Based on the payment date and time of the tip, the control unit 11 aggregates the total tip amount within a predetermined period (for example, one month) from the payment history DB 174 of the large-capacity storage unit 17 (step S122).

The control unit 11 calculates a transaction fee related to chip distribution based on the acquired chip distribution rule (step S123). For example, if the tip allocation rule describes a fee collection standard of "10% of the total tip amount", the transaction fee is 10,000 yen for the total tip amount of 100,000 yen. The control unit 11 subtracts the calculated transaction fee from the total tip amount (step S124). The control unit 11 calculates the amount to be distributed to each recipient based on the distribution ratio defined in the chip distribution rule (step S125). Note that the processing for calculating the allocation amount is the same as the processing described above, so the description is omitted.

The control unit 11 assigns an allocation ID, and the year and month to be allocated, the date and time of allocation, the restaurant ID, the total tip amount corresponding to the target year and month, the recipient ID, the amount earned by the recipient, and the amount to be paid to the recipient. The allocation amount and the transaction fee are stored as one record in the allocation history DB 173 of the large-capacity storage unit 17 (step S126).

The control unit 11 transmits the total tip amount within the period and the allocation amount to each recipient to the store terminal 3 of each restaurant through the communication unit 13 (step S127). The control unit 31 of the shop terminal 3 receives the total tip amount within the period and the allocation amount to each recipient from the server 1 through the communication unit 33 (step S321). The control unit 31 causes the display unit 35 to display the received total tip amount and the allocation amount to each recipient (step S322).

FIG. 13 is an explanatory diagram showing an example of a reception screen for selecting a waiter. FIG. 13 shows a screen on the customer terminal 2 for accepting selection of a waiter by the customer. The screen includes a selection button 11a, a code reading button 11b, and a restaurant display field 11c. The selection button 11a is a button for receiving the selection of the waiter. The code reading button 11b is a button for reading a code describing information about the waiter. The restaurant display field 11c is a display field for displaying the name of the restaurant.

The server 1 acquires the restaurant name from the restaurant DB 171 based on the restaurant ID. Based on the restaurant ID, the server 1 acquires a plurality of waiters whose type of distributed person is "waiter" from the distributed person DB 172 . The server 1 transmits the acquired restaurant name and the plurality of waiters to the customer terminal 2 . The customer terminal 2 displays the restaurant name transmitted from the server 1 in the restaurant display field 11c. The customer terminal 2 associates the plurality of waiters transmitted from the server 1, generates a selection button 11a for accepting the selection of the corresponding waiter, and displays it on the screen.

When receiving a touch (click) operation on any of the selection buttons 11a, the customer terminal 2 receives selection of the corresponding waiter. The customer terminal 2 acquires information about the selected waiter (for example, waiter's employee ID, etc.). Alternatively, when the customer terminal 2 accepts the touch operation of the code reading button 11b, the imaging unit 26 reads a code (for example, a QR code) describing information about the waiter. The customer terminal 2 uses a code analysis library to obtain information about the waiter from the read code. The customer terminal 2 transfers the information about the selected waiter, restaurant ID and restaurant name to a reception screen (FIG. 14) for inputting the tip amount. The customer terminal 2 displays a reception screen for inputting the tip amount.

FIG. 14 is an explanatory diagram showing an example of a reception screen for inputting the tip amount. FIG. 14 shows a screen on the customer terminal 2 for accepting the input of the amount of the tip to be paid by the customer to the waiter. The screen includes a waiter display field 12a, an amount input field 12b, a confirmation button 12c, and a restaurant display field 11c. The waiter display field 12a is a display field for displaying the name of the waiter to whom the tip is to be paid. The amount input field 12b is an input field for receiving the input of the tip amount. The confirm button 12c is a button for transmitting to the server 1 the selected waiter information and the tip amount paid by the customer to the waiter. The restaurant display field 11c is the same as in FIG.

The customer terminal 2 displays the restaurant name received from the previous screen (FIG. 13) in the restaurant display field 11c. When the customer terminal 2 accepts the touch operation of the confirmation button 12c, the restaurant ID, the amount of tip entered in the amount input field 12b, and the information on the waiter passed from the previous screen are transmitted to the server 1. do.

FIG. 15 is an explanatory diagram showing an example of an incentive display screen. FIG. 15 is a screen for acquiring and displaying an incentive set according to the tip amount paid by the customer on the customer terminal 2 . Note that FIG. 15 illustrates an example in which the incentive is a coupon, but the same applies to other types of incentives.

The screen includes a coupon display field 13a, a coupon use button 13b, and a restaurant display field 11c. The coupon display field 13a is a display field for displaying a coupon set according to the amount of tip paid. The coupon use button 13b is a button for using the issued coupon. The restaurant display field 11c is the same as in FIG.

The server 1 receives from the customer terminal 2 the restaurant ID, the information about the waiter, and the When receiving the tip amount paid to the client, an incentive set according to the received tip amount is obtained. Specifically, the server 1 acquires the pre-registered incentive conditions from the restaurant DB 171 based on the restaurant ID. For example, the acquired incentive condition is "a meal coupon worth 200% of the tip amount". The server 1 issues meal coupons to customers based on the obtained incentive conditions. As shown in the figure, a meal coupon for "1,000 yen" is issued according to the tip amount of 500 yen paid.

The server 1 transmits the issued coupon to the customer terminal 2 . The customer terminal 2 receives the coupon sent from the server and displays it in the coupon display field 13a. When receiving the touch operation of the coupon use button 13b, the customer terminal 2 performs coupon payment processing via a payment application, a payment server, or the like. Note that payment processing may be performed by reading a QR code, bar code, or the like displayed on the coupon. After the coupon settlement process is performed, the server 1 updates the usage status column of the incentive history DB 175 to "used" in association with the incentive ID.

FIG. 16 is an explanatory diagram showing an example of a display screen for payment history and acquisition history. FIG. 16 is a screen for displaying the tip payment history and the incentive acquisition history for each restaurant on the customer terminal 2 . The screen includes a payment information display field 14a, an incentive link 14b, an expiration date display field 14c, and a restaurant name display field 14d.

The payment information display field 14a is a display field for displaying information on tip payment including the name of the waiter, the amount of tip paid by the customer to the waiter, and the date and time of payment of the tip. The incentive link 14b is a link for transitioning to an incentive display screen. The expiration date display column 14c is a display column for displaying the expiration date of the incentive. The restaurant name display field 14d is a display field for displaying the name of the restaurant.

Based on the customer ID, the server 1 acquires from the payment history DB 174 the tip payment history for a specified period (for example, one month) or for the entire period. The server 1 acquires the history of incentives issued by each restaurant from the incentive history DB 175 based on the payment ID included in the acquired payment history. The server 1 transmits the acquired tip payment history and incentive acquisition history to the customer terminal 2 .

The customer terminal 2 receives the tip payment history and the incentive acquisition history transmitted from the server 1 and displays them on the screen. As shown, the customer terminal 2 displays the name of the restaurant included in the payment history in the restaurant name display column 14d, and displays the name of the waiter who was the target of the tip payment, the amount of the tip, and the date and time of the payment. It is displayed in the payment information display column 14a. In addition, the customer terminal 2 displays the types of incentives included in the incentive acquisition history in the incentive link 14b, and displays the expiration date of the incentive in the expiration date display field 14c.

When the customer terminal 2 receives a touch operation on the incentive link 14b, the customer terminal 2 may display detailed information including, for example, the incentive ID, content, issuing restaurant, issuing date and time, expiration date, usage state, etc. on a pop-up screen, or You may change to an incentive display screen (FIG. 15).

FIG. 17 is an explanatory diagram showing an example of a display screen of allocation history. FIG. 17 shows a screen for displaying the total amount of chips within a predetermined period and the amount to be distributed to each recipient on the store terminal 3 . The screen includes an allocation history display field 15a, a target year/month display field 15b, a previous month button 15c and a next month button 15d.

The distribution history display field 15a is a display field for displaying the distribution history for each restaurant. The target year/month display column 15b is a display column for displaying the target year/month of allocation. The previous month button 15c is a button for displaying the distribution history of the previous month of the target year and month. The next month button 15d is a button for displaying the distribution history of the next month of the target year and month.

The store terminal 3 transmits the allocation target year and month (for example, the current month) to the server 1 . Based on the allocation target year and month transmitted from the store terminal 3, the server 1 determines the name of each recipient, the amount earned when the recipient is a waiter, the amount distributed to each recipient, and the allocation amount. The allocation history including working hours when the allocator is a waiter or a chef is acquired from the allocated person DB 172, the allocation history DB 173, and the work management DB 176.

The server 1 transmits the acquired distribution history to the store terminal 3 . The store terminal 3 receives the distribution history transmitted from the server 1 and displays it in the distribution history display field 15a. The store terminal 3 acquires from the server 1 the distribution history of the previous month of the target year and month when the touch operation of the previous month button 15c is received. The store terminal 3 acquires the allocation history of the next month of the target year and month from the server 1 when the touch operation of the next month button 15d is received. It should be noted that the allocation history acquisition process is the same as the process described above, so description thereof will be omitted.

According to this embodiment, it is possible to distribute the tip amount paid by a customer to a waiter after consumption at a restaurant to a plurality of recipients of the restaurant.

According to the present embodiment, it is possible to realize a tip distribution system that ensures transparency by automatically allocating the amount of the tip based on the tip distribution rule determined for each restaurant.

According to this embodiment, it is possible to pay an arbitrary amount of tip to the waiter who served the customer at the restaurant according to the satisfaction level of the customer.

According to this embodiment, it is possible to increase the ability to attract customers by issuing an incentive to the customer that is set according to the tip amount paid by the customer to the waiter.

According to this embodiment, it is possible to ensure fairness by distributing the amount of tips acquired by the waiter to other recipients than the waiter.

(Embodiment 2)
In the second embodiment, the incentives set according to the amount of the tip and the distribution ratio to be distributed to a plurality of recipients (owners, waiters, and chefs) of the restaurant in accordance with the input timing of the amount of the tip. and the forehead are automatically displayed in synchronization with each other. In addition, description is abbreviate|omitted about the content which overlaps with Embodiment 1. FIG.

The customer terminal 2 transmits the restaurant ID to the server 1 . Based on the restaurant ID transmitted from the customer terminal 2, the server 1 acquires from the restaurant DB 171 the conditions of the incentive of the restaurant and the distribution ratio to be distributed to each recipient. The server 1 transmits the acquired incentive conditions and distribution ratio to the customer terminal 2 . The customer terminal 2 receives the incentive conditions and allocation ratios transmitted from the server 1 .

A customer terminal 2 accepts selection of a waiter who serves customers in a restaurant, and accepts an input of a tip amount to be paid to the selected waiter. In this case, the customer terminal 2 specifies the incentive according to the entered tip amount based on the conditions of the incentive. The customer terminal 2 calculates an allocation amount to be allocated to a plurality of recipients based on the allocation ratio. The customer terminal 2 simultaneously displays the entered tip amount, the specified incentive, and the allocation ratio and amount to be allocated to each recipient on the screen.

In the present embodiment, an example in which the customer terminal 2 acquires in advance the incentive conditions and distribution ratios of the restaurant from the server 1 has been described, but the present invention is not limited to this. For example, each time the customer terminal 2 receives an input of the tip amount, it may communicate with the server 1 to synchronously acquire the incentive conditions and allocation ratio.

In accordance with the above-described process, the incentives to be issued, the allocation ratio and amount to be distributed to each recipient are automatically displayed according to the timing of inputting the tip amount, so that the customer can select the appropriate tip amount according to the level of satisfaction. You can adjust and pay the waiter.

FIG. 18 is a flow chart showing a processing procedure for displaying incentives and distribution ratios in accordance with the input timing of the tip amount. The control unit 21 of the customer terminal 2 transmits the restaurant ID to the server 1 through the communication unit 23 (step S241). The control unit 11 of the server 1 receives the restaurant ID transmitted from the customer terminal 2 through the communication unit 13 (step S141).

Based on the received restaurant ID, the control unit 11 acquires the conditions of the incentive of the restaurant and the distribution ratio to be distributed to each recipient (step S142). Specifically, the control unit 11 acquires the tip distribution rule and incentive conditions from the restaurant DB 171 of the large-capacity storage unit 17 based on the restaurant ID. The control unit 11 extracts an allocation ratio for allocating the tip amount to each recipient (owner, waiter, and chef) from the acquired tip allocation rule.

The control unit 11 transmits the obtained incentive conditions and distribution ratio to the customer terminal 2 through the communication unit 13 (step S143). The control unit 21 of the customer terminal 2 receives the incentive conditions and allocation ratios transmitted from the server 1 through the communication unit 23 (step S242). Incidentally, the incentive conditions and distribution ratios may be stored in advance in the storage unit 22 of the customer terminal 2 . The control unit 21 receives the selection of the waiter by the customer via the input unit 24 (step S243). The control unit 21 receives input of the tip amount to be paid to the selected waiter via the input unit 24 (step S244).

Based on the conditions of the incentive, the control unit 21 specifies the incentive according to the input amount of the tip, as in the first embodiment (step S245). The control unit 21 calculates an allocation amount to be allocated to a plurality of recipients based on the allocation ratio (step S246). The control unit 21 simultaneously displays the incentive, the allocation ratio, the amount, and the inputted tip amount via the display unit 25 (step S247), and the control unit 21 returns to the process of step S244.

FIG. 19 is an explanatory diagram illustrating an example of a reception screen for inputting a tip amount according to the second embodiment. Note that the same reference numerals are given to the contents that overlap with those in FIG. 14, and the description thereof is omitted. The screen further includes a planned incentive display field 12d and an allocation ratio display field 12e. The planned incentive display field 12d is a display field for displaying an incentive set according to the input amount of the tip. The allocation ratio display field 12e is a display field for displaying the allocation ratio and the amount to be allocated to each recipient.

Based on the restaurant ID, the customer terminal 2 synchronously acquires from the server 1 the conditions of the incentive of the restaurant and the distribution ratio to be distributed to each recipient. When the customer terminal 2 receives the amount of tip input in the amount input field 12b, the customer terminal 2 specifies an incentive set according to the input amount of tip based on the acquired incentive conditions. . The customer terminal 2 displays the specified incentive (scheduled to be obtained) in the scheduled incentive display field 12d.

For example, the incentive condition is "a meal coupon worth 200% of the tip amount". As shown in the figure, when a tip amount of 500 yen is entered, a meal coupon for '1000 yen' is specified and displayed. When a tip amount of 1,000 yen is entered, a meal coupon for '2,000 yen' is specified and displayed. In other words, an incentive set according to the input amount of chips is automatically displayed in the scheduled incentive display field 12d.

The customer terminal 2 creates a chart showing the allocation ratio and amount based on the acquired allocation ratio. The customer terminal 2 displays the created chart in the distribution ratio display column 12e. As shown in the figure, the allocation ratios and amounts to be allocated to a plurality of recipients including restaurant owners, waiters and chefs are displayed in the form of pie charts. It should be noted that the expression format of the allocation ratio and amount is not limited to the pie chart, and may be text, table or other statistical graph.

According to the present embodiment, the incentive set according to the tip amount and the allocation ratio and amount to be allocated to a plurality of recipients of the restaurant are automatically displayed in accordance with the input timing of the tip amount. becomes possible.

According to this embodiment, by displaying incentives to be issued in accordance with the amount of tip input by the customer, it is possible to stimulate the customer's willingness to pay the tip.

According to the present embodiment, by issuing incentives to customers, it is possible to increase the repeater rate (return rate) of customers.

(Embodiment 3)
The third embodiment relates to a mode of outputting evaluation information according to the total amount of chips within a predetermined period or the amount of allocation to each recipient for each restaurant. Note that the description of the contents overlapping those of the first and second embodiments will be omitted. The server 1 can evaluate each restaurant according to the total amount of tips within a predetermined period, or can evaluate according to the amount distributed to each recipient of the restaurant. The evaluation is, for example, ranking, word of mouth, or the like. An example of a ranking evaluation method will be described below.

When ranking restaurants, the server 1 acquires the total tip amount within a predetermined period (for example, the previous month, the current month, or the next month) for each restaurant from the distribution history DB 173 . The server 1 ranks the acquired total tip amount of each restaurant, and outputs the ranking result to the customer terminal 2 or the store terminal 3 .

When ranking the recipients, the server 1 acquires the allocation amount to each recipient within a predetermined period from the distribution history DB 173 based on the restaurant ID. The server 1 ranks the obtained allocation amount to each recipient, and outputs the ranking result to the customer terminal 2 or the shop terminal 3 .

FIG. 20 is an explanatory diagram showing an example of a display screen of ranking results for restaurants. FIG. 20 shows a screen displaying the result of ranking based on the total tip amount of each restaurant within a predetermined period (for example, one month). The screen includes a ranking display field 16a, a thumbnail image display field 16b, a restaurant information display field 16c, a chip star mark 16d, a word-of-mouth star mark 16e, and a word-of-mouth link 16f.

The ranking display field 16a is a display field for displaying the ranking ranking based on the total chip amount. The thumbnail image display field 16b is a display field for displaying thumbnail images of restaurants. The restaurant information display column 16c is a display column for displaying information about the restaurant. The chip star mark 16d is a display field for displaying a star mark evaluated according to the total chip amount. The word-of-mouth star mark 16e is a display field for displaying star marks evaluated by word-of-mouth. The word-of-mouth link 16f is a link for transitioning to word-of-mouth. Word of mouth may be a part of this system or an external system.

The server 1 acquires from the distribution history DB 173 the total tip amount within a predetermined period for each restaurant. The server 1 ranks the obtained total tip amount. The server 1 acquires the name of the restaurant, the type of food, and the thumbnail image of the restaurant from the restaurant DB 171 based on the restaurant ID of each restaurant. The server 1 transmits to the customer terminal 2 or the store terminal 3 the ranking result including each restaurant name, food type, thumbnail image, tip total amount and ranking.

For example, when receiving the ranking result transmitted from the server 1, the customer terminal 2 displays the received ranking result on the screen. Specifically, the customer terminal 2 displays the rankings included in the ranking results in the ranking display field 16a, and displays thumbnail images of restaurants in the thumbnail image display field 16b. The customer terminal 2 displays the name of the restaurant and the type of food included in the ranking results in the restaurant information display field 16c.

The customer terminal 2 obtains a star mark and score corresponding to the total tip amount included in the ranking result based on a predetermined rule. The predetermined rule is, for example, to determine points based on the amount of chips and to determine the number of star marks based on the points. Specifically, for example, the predetermined rule is "If the total tip amount is 50,000 yen or more, give 5 points, if the total tip amount is between 49,000 and 50,000, give 4.9 points, ..." and "If the score is 5, 5 black stars will be displayed, and if the score is between 4.5 and 5, 4 black stars and 1 A meteor-shaped star mark may be displayed, such as "...". The customer terminal 2 displays the obtained star mark and score on the chip star mark 16d.

Note that relative evaluation, which is an evaluation method based on statistical normal distribution, may be used for ranking restaurants. For example, the server 1 calculates the deviation value of the tip amount within a predetermined period of a plurality of restaurants to be evaluated for each type (genre) of restaurants, and uses the calculated deviation value as a relative evaluation value. Send to customer terminal 2 . The customer terminal 2 may perform ranking based on the relative evaluation value transmitted from the server 1 for each type of restaurant.

The customer terminal 2 acquires, for example, from a word-of-mouth system that cooperates with the outside, star marks and points corresponding to the word-of-mouth of the restaurant, and the number of word-of-mouth. The customer terminal 2 displays the star mark and score corresponding to the acquired word-of-mouth on the word-of-mouth star mark 16e. The customer terminal 2 displays the number of acquired word-of-mouth on the word-of-mouth link 16f. When the customer terminal 2 receives the touch operation of the word-of-mouth link 16f, the customer terminal 2 transitions to a screen or web page displaying word-of-mouth of the corresponding restaurant.

FIG. 21 is an explanatory diagram showing an example of a display screen of ranking results for the recipients. FIG. 21 is a screen that displays the result of ranking based on the amount of allocation to each recipient within a predetermined period. The screen includes a title display field 17a, an allottee ranking display field 17b, a photo display field 17c, an allottee information display field 17d and a distribution star mark 17e.

The title display field 17a is a display field for displaying the restaurant name, which is the title. The allocated person ranking display field 17b is a display field for displaying the ranking performed based on the amount allocated to each allocated person. The photo display column 17c is a display column for displaying the photo of the recipient. The recipient information display column 17d is a display column for displaying information about the recipient. The allocation star mark 17e is a display column for displaying the star mark evaluated according to the allocation amount.

The server 1 acquires the restaurant name from the restaurant DB 171 based on the restaurant ID. Based on the restaurant ID, the server 1 acquires the allocation amount to each recipient of the restaurant from the distribution history DB 173 . The server 1 ranks the acquired allocation amount. The server 1 acquires the names, photographs, and occupations of the recipients from the DB 172 of the recipients based on each recipient ID. The server 1 transmits to the customer terminal 2 or the store terminal 3 the ranking result including the name of the restaurant, the name of each recipient, the photograph, the type of job, the amount of allocation and the ranking.

For example, when receiving the ranking result transmitted from the server 1, the customer terminal 2 displays the received ranking result on the screen. Specifically, the customer terminal 2 displays the name of the restaurant included in the ranking result in the title display field 17a, and displays the ranking in the recipient ranking display field 17b. The customer terminal 2 displays the photo of the recipient included in the ranking result in the photograph display column 17c, and displays the name and occupation in the recipient information display column 17d.

The customer terminal 2 acquires a star mark and a score corresponding to the allocation amount included in the ranking result based on a predetermined rule. The customer terminal 2 displays the acquired star marks and points on the distribution star mark 17e. Note that the display processing of the star mark is the same as in FIG. 20, so the description is omitted.

According to this embodiment, it is possible to output evaluation information according to the total tip amount within a predetermined period for each restaurant or the amount distributed to each recipient of the restaurant.

(Embodiment 4)
Embodiment 4 relates to a form in which the tip amount paid to a delivery person who delivers food from a restaurant is distributed to a plurality of recipients of the restaurant. Note that the description of the contents overlapping those of the first to third embodiments will be omitted.

When a customer receives food from a restaurant from a delivery person, the customer's customer terminal 2 reads a code (for example, a two-dimensional code or a barcode) describing the employee ID of the delivery person, and based on the read code Identify the delivery person. Note that selection of a delivery person may be accepted from the delivery person list screen. The customer terminal 2 accepts the input of the tip amount to be paid to the delivery person selected by the customer. The customer terminal 2 transmits to the server 1 the employee ID of the accepted delivery person, the tip amount paid to the delivery person, the restaurant ID, and the customer ID.

The server 1 receives the delivery person's employee ID, tip amount, restaurant ID, and customer ID transmitted from the customer terminal 2 . The server 1 assigns payment IDs and stores the customer ID, restaurant ID, delivery staff ID, tip amount and payment date and time as one record in the payment history DB 174 . The server 1 identifies an incentive set according to the received tip amount. Note that the incentive specifying process is the same as that of the first embodiment, so the description is omitted. The server 1 transmits the identified incentive to the customer terminal 2 . The customer terminal 2 receives and displays the incentive transmitted from the server 1 .

Also, the amount of chips obtained within a predetermined period (for example, one month) can be distributed to a plurality of recipients of the restaurant. The recipients in this embodiment are the owner of the restaurant, the delivery person who delivers the food of the restaurant, or the cook who prepares the food. Specifically, the server 1 acquires the tip distribution rule of the restaurant from the restaurant DB 171 based on the restaurant ID. The tip distribution rule is, for example, "Owner: 55% of the total tip amount, Delivery staff: 25% of the tip earned by the chef, Cook: 15% of the total tip amount as a weighted average of working hours, Transaction fee: 5% of the total tip amount. %”.

The server 1 aggregates the total tip amount within a predetermined period from the payment history DB 174 based on the payment date and time of the tip. The server 1 calculates a transaction fee related to tip allocation based on the acquired tip allocation rule. For example, if the transaction fee is "5% of the total tip amount", the transaction fee of 5,000 yen is collected for the total tip amount of 10,000 yen. The server 1 deducts the calculated transaction fee from the total tip amount.

The server 1 calculates the amount to be distributed to each recipient based on the distribution ratio defined in the chip distribution rule and the total amount after deducting the transaction fee. Note that the processing for calculating the allocation amount is the same as in the first embodiment, so the description is omitted. The server 1 stores the chip allocation history in the allocation history DB 173 . The server 1 transmits the total tip amount within a predetermined period and the allocation amount to each recipient to the store terminal 3 of each restaurant. The store terminal 3 receives and displays the total amount of chips within a predetermined period transmitted from the server 1 and the amount to be distributed to each recipient.

FIG. 22 is a flow chart showing a processing procedure for specifying an incentive according to tip payment according to the fourth embodiment. In addition, the same code|symbol is attached|subjected about the content which overlaps with FIG. 10, and description is abbreviate|omitted. The control unit 21 of the customer terminal 2 reads the code describing the employee ID of the delivery person, and identifies the delivery person based on the read code. (Step S251). The control unit 21 receives an input of the tip amount to be paid by the customer to the delivery person through the input unit 24 (step S252).

The control unit 21 transmits tip payment information including the employee ID of the specified delivery person, the tip amount paid to the delivery person, the restaurant ID, and the customer ID to the server 1 via the communication unit 23 ( step S253). The control unit 11 of the server 1 receives the tip payment information transmitted from the customer terminal 2 through the communication unit 13 (step S151). After that, the control unit 11 executes the process of step S102.

Note that the processing procedure for allocating the amount of chips to the recipients is the same as the allocation processing in FIG. 12 of the first embodiment, so the description is omitted.

FIG. 23 is an explanatory diagram showing an example of a display screen of ranking results for restaurants according to the fourth embodiment. In addition, the same code|symbol is attached|subjected about the content which overlaps with FIG. 20, and description is abbreviate|omitted. The tip star mark 16d is a display column for displaying a star mark evaluated according to the total tip amount earned inside the restaurant. In addition, FIG. 23 further includes a home delivery chip star mark 16g. The delivery tip star mark 16g is a display column for displaying a star mark evaluated according to the total tip amount paid to the delivery person who delivered (takeout) the food from the restaurant.

When the customer pays the delivery person the amount of the tip, the server 1 assigns a payment ID, the customer ID, the restaurant ID, the employee ID of the delivery person, and the amount of the tip paid by the customer to the delivery person. The amount and date of payment are stored in the payment history DB 174 as one record. When this screen is displayed, the server 1 stores the total amount of tips paid to the delivery staff within a predetermined period (for example, one month) for each restaurant based on the payment date and time of the tip. 17 payment history DB 174. The server 1 acquires the total tip amount as the total tip amount for home delivery.

20, the server 1 acquires the total tip amount obtained inside each restaurant, and ranks the acquired total tip amount inside the restaurant. The server 1 acquires the name of the restaurant, the type of food, and the thumbnail image of the restaurant from the restaurant DB 171 based on the restaurant ID of each restaurant. The server 1 transmits to the customer terminal 2 or the store terminal 3 the ranking result including the name of each restaurant, the type of food, the thumbnail image, the total tip amount in the store, the total tip amount for home delivery, and the order.

In this embodiment, an example in which the total amount of chips in the store is ranked is explained, but the present invention is not limited to this. For example, the total tip amount for home delivery, or the total tip amount for the store and the total tip amount for home delivery may be ranked.

For example, when receiving the ranking result transmitted from the server 1, the customer terminal 2 displays the received ranking result on the screen. Specifically, the customer terminal 2 displays the rankings included in the ranking results in the ranking display field 16a, and displays thumbnail images of restaurants in the thumbnail image display field 16b. The customer terminal 2 displays the name of the restaurant and the type of food included in the ranking results in the restaurant information display field 16c.

Based on a predetermined rule, the customer terminal 2 acquires the star marks and points corresponding to the total tip amount in the store and the total tip amount for home delivery included in the ranking results, as in the process of FIG. The customer terminal 2 displays the star mark and points corresponding to the acquired total tip amount in the store on the tip star mark 16d. The customer terminal 2 displays the star mark and score corresponding to the total tip amount of the home delivery obtained on the home delivery chip star mark 16g.

According to this embodiment, it is possible to distribute the tip amount paid to a delivery person who delivers food from a restaurant to a plurality of recipients of the restaurant.

According to this embodiment, it is possible to realize a tip distribution system in a restaurant that provides a home delivery service.

(Embodiment 5)
Embodiment 5 relates to a mode of distributing the tip amount paid to a waiter who is a payee and a waiter who works on the day other than the waiter. Note that descriptions of the contents overlapping those of the first to fourth embodiments will be omitted.

Multiple waiters at a restaurant may serve customers at the same time. Alternatively, a customer may be served by multiple waiters, including a main waiter and other waiters who provide support, assistance, etc. to the main waiter. The customer selects a waiter (first waiter) to whom the tip is to be paid from a plurality of waiters at the restaurant, and pays the tip amount to the selected first waiter. The tip amount paid by the customer is distributed to the first waiter based on a predetermined tip distribution rule, and is also distributed to other waiters (second waiters) working on the day.

For example, the tip distribution rule for the distribution to the waiter is "Amount allocated to the first waiter (payee): 20% of the tip earned by himself, Total amount distributed to the second waiter (work on the day): 1st 5% of the tip earned by the waiter". When waiter A, waiter B, and waiter C are working at a restaurant on the day, for example, the customer pays the first waiter (waiter A) a tip of 1000 yen. Based on the tip distribution rule described above, the amount of tip allocated to the first waiter (waiter A) is 200 yen (1000 x 20%), and a plurality of second waiters (waiter B and waiter The total amount allocated to person C) is 50 yen (1000×5%).

Then, based on the total amount to be allocated to the plurality of second waiters working on the day, the amount to be allocated to each of the second waiters is calculated. For example, the total amount of distribution may be equally divided according to the number of second waiters. That is, the total allocation amount is divided by the number of second waiters to calculate the allocation amount for each of the second waiters. In the above example, 25 yen is allocated to each of the second waiters on duty that day, namely waiter B and waiter C, for the total amount of 50 yen.

Note that the allocation process for the owner and the chef is the same as in the first embodiment, so the explanation is omitted.

FIG. 24 is a flow chart showing the processing procedure for calculating the allocation amount of the waiter. The waiters include the first waiter to whom the customer paid the tip amount, and the second waiter on duty on the day other than the first waiter. FIG. 24 is a flow chart showing a processing procedure for calculating the allocation amount for each of the first waiter and the second waiter.

The control unit 11 of the server 1 acquires the tip distribution rule of the restaurant from the restaurant DB 171 of the large-capacity storage unit 17 based on the restaurant ID (step S161). Based on the restaurant ID, the control unit 11 acquires a plurality of first waiters working at the restaurant from the distributed person DB 172 (step S162). The control unit 11 acquires one first waiter from the plurality of acquired first waiters (step S163). Based on the restaurant ID and the acquired employee ID of the first waiter, the control unit 11 calculates the tip amount paid by the customer to the first waiter within a predetermined period (for example, one month). are aggregated from the payment history DB 174 (step S164).

The control unit 11 calculates the allocation amount to the first waiter based on the acquired tip allocation rule (step S165), and calculates the total allocation to the plurality of second waiters working on the day other than the first waiter. The amount is calculated (step S166). For example, the tip distribution rule states "Amount allocated to the first waiter: 20% of the amount of chips earned by himself, Total amount allocated to the second waiter: 5% of the amount of chips earned by the first waiter". In this case, the control unit 11 calculates the total amount of 200 yen distributed to the first waiter and 50 yen distributed to the second waiters (plurality) for the tip amount of 1000 yen earned by the first waiter. calculate.

Based on the working days of the first waiter, the control unit 11 acquires a plurality of second waiters working that day from the work management DB 176 of the large-capacity storage unit 17 (step S167). The control unit 11 calculates the obtained allocation amount to each of the second waiters according to the calculated total amount allocated to the second waiters (step S168). For example, the control unit 11 divides the total amount of distribution by the number of second waiters working that day to calculate the amount of distribution to each of the second waiters. It should be noted that the process of calculating the amount to be distributed to each of the second waiters is not limited to equally dividing the amount according to the number of people. For example, when the allocation rate is set based on the working hours, the allocation amount may be calculated according to the working hours of each second waiter. The control unit 11 determines whether or not the first waiter is the last among the plurality of first waiters (step S169). When the control unit 11 determines that the first waiter is not the last one (NO in step S169), the control unit 11 returns to the process of step S163 and acquires the next first waiter.

When the control unit 11 determines that the first waiter is the last one (YES in step S169), the controller 11 stores the calculated allocation amounts of the first waiter and the second waiter in the allocation history DB 173 (step S170). . Specifically, the control unit 11 calculates the total amount of the allocation amount allocated as the first waiter and the allocation amount allocated as the second waiter for each waiter. The control unit 11 stores the calculated total amount as the allocation amount for each waiter in the allocation amount column of the allocation history DB 173 .

According to this embodiment, it is possible to improve fairness by including the first waiter who is the payee and the second waiter who is on duty on the day other than the first waiter. .

<Modification 1>
The process of paying tip amount to each of the first and second waiters selected by the customer according to the level of satisfaction will be explained.

The customer selects the first waiter with the highest degree of satisfaction from a plurality of waiters at the restaurant, and pays the tip amount to the selected first waiter. The customer selects the second waiter with the next highest level of satisfaction from a plurality of waiters at the restaurant, and pays the tip amount to the selected second waiter. Note that the tip amount paid to the first waiter or the second waiter is not limited, and may be any amount. For example, the customer may pay a tip of 1000 yen to the first waiter and a tip of 500 yen to the second waiter. Alternatively, the customer may pay the same tip amount to each of the first and second servers.

There is no limit to the number of waiters to whom the tip is to be paid, and in addition to the first and second waiters, the customer may pay the amount of the tip to, for example, the third waiter according to the level of satisfaction. good.

The server 1 acquires the amounts of tips paid by the customer to the first and second waiters and stores them in the payment history DB 174 . The server 1 distributes the acquired tip amount to a plurality of recipients (owners, waiters, and chefs) of the restaurant based on the tip distribution rule determined for each restaurant. Note that the allocation process is the same as that of the first embodiment, so the description is omitted.

According to this modified example, the customer can pay any amount of tip to a plurality of waiters according to the degree of satisfaction.

(Embodiment 6)
Embodiment 6 relates to a form in which the incentive acquired by the customer is transferred to another person. Note that the description of the contents overlapping those of the first to fifth embodiments will be omitted.

FIG. 25 is a block diagram showing a configuration example of the server 1 of the sixth embodiment. In addition, the same code|symbol is attached|subjected about the content which overlaps with FIG. 2, and description is abbreviate|omitted. A transfer history DB 177 is stored in the large-capacity storage unit 17 . The transfer history DB 177 stores a transfer history of incentives.

FIG. 26 is an explanatory diagram showing an example of the record layout of the transfer history DB 177. As shown in FIG. The transfer history DB 177 includes a transfer ID column, a transferor ID column, a transferee ID column, a target incentive ID column, a transfer amount column, and a transfer date and time column. The transfer ID column stores the ID of history data that is uniquely specified in order to identify the history data of each transfer.

The transferor ID column stores the customer ID of the transferor who transferred the incentive. The transferee ID column stores the customer ID of the transferee (transferee) who has received the incentive. The target incentive ID column stores incentive IDs for specifying incentives to be transferred. The transfer amount column stores the transferred incentive amount. The transfer date and time column stores information on the date and time when the incentive was transferred.

Customers earn incentives based on the amount of tips they pay to waiters. A portion of the earned, unexpired incentives may be transferred to others (eg, friends or colleagues, etc.). If a part of the incentive owned by the transferor (for example, 50% of the amount) is transferred, the server 1 extends the expiration date of the incentive for a predetermined period. The predetermined period is, for example, two weeks, one month, three months, or the like. The server 1 updates the amount of the incentive extended for the predetermined period and outputs it to the customer terminal 2 of the transferor. The server 1 also issues the incentive transferred from the transferor to the transferee (transferee), and transmits the issued incentive to the transferee's customer terminal 2 .

For example, if the incentive is a coupon, and 50% (1,000 yen) of a 2,000-yen coupon owned by Mr. A (transferor) is transferred to Mr. B (transferee), the server 1 The transfer will be processed in accordance with the transfer instructions of (Transferor). The server 1 updates the coupon of 2,000 yen to the coupon of 1,000 yen for Mr. A (transferor), and extends the expiration date of the incentive for a predetermined period. The predetermined period is, for example, two months. The server 1 outputs the coupon, which has been extended for a predetermined period, to the customer terminal 2 of customer A (transferor).

The server 1 issues a new 1,000-yen coupon to customer B (assignee). In this case, the expiration date of the coupon issued to Mr. B (transferee) may be set to be the same as the expiration date of the coupon after transfer to Mr. A (transferor). Alternatively, the expiration date of the coupon issued to Mr. B (transferee) may be set longer than the expiration date of the coupon after transfer to Mr. A (transferor). For example, the expiration date of the coupon issued to Mr. B (transferee) is set to be one month longer than the expiration date of the coupon after the transfer of Mr. A (transferor).

FIG. 27 is a flow chart showing a processing procedure for transferring incentives. The control unit 11 of the server 1 acquires information regarding the transfer of the incentive from the transferor's customer terminal 2 through the communication unit 13 (step S181). Information about the transfer includes the transferor's customer ID, the transferee's customer ID, the incentive ID, and the amount of the transfer. Based on the acquired incentive ID, the control unit 11 acquires the expiration date (expiration date), usage status, and issue date and time of the incentive from the incentive history DB 175 of the large-capacity storage unit 17 (step S182).

The control unit 11 determines whether or not the acquired usage status of the incentive is unused (step S183). When the control unit 11 determines that the usage state is used (NO in step S183), the communication unit 13 transmits an error message indicating that the transfer is not possible to the transferor's customer terminal 2 (step S191). When the control unit 11 determines that the usage state is unused (YES in step S183), based on the expiration date of the incentive, it determines whether or not the incentive is within the expiration date (step S184).

If the transferor has used a portion of the incentive amount, it may be determined whether or not the transfer is possible based on the balance of the incentive. For example, when the control unit 11 determines that the incentive balance is less than a predetermined amount (for example, 300 yen or 1000 yen), it executes the process of step S191 (error message transmission process). If the control unit 11 determines that the incentive balance is equal to or greater than the predetermined amount, the control unit 11 executes the processing of step S184 (expiration date determination processing).

If the control unit 11 determines that the incentive is not within the expiration date (NO in step S184), the process proceeds to step S191. If the control unit 11 determines that the incentive is within the expiration date (YES in step S184), the control unit 11 acquires a predetermined expiration extension period (for example, one month) stored in the storage unit 12 (step S185).

The control unit 11 updates the transferor's incentive acquisition history (step S186). Specifically, the control unit 11 calculates the expiration date of the incentive after the transfer by adding a predetermined extension period to the expiration date of the incentive before the transfer. The control unit 11 updates the incentive history DB 175 of the large-capacity storage unit 17 by associating the calculated expiration date of the incentive after the transfer and the amount of the incentive after the transfer with the incentive ID.

The control unit 11 stores the transferee's incentive acquisition history in the incentive history DB 175 of the large-capacity storage unit 17 (step S187). Specifically, the control unit 11 allocates an incentive ID, and the incentive acquisition history including the incentive type, contents, the restaurant ID that issued the incentive, the date and time of issuance, the expiration date, and the usage status as one record. Store in DB 175 . The term of validity of the incentive issued to the transferee may be set in the same manner as the term of validity of the incentive after the transfer by the transferor.

The control unit 11 stores the transfer history in the transfer history DB 177 of the large-capacity storage unit 17 (step S188). Specifically, the control unit 11 assigns a transfer ID, and stores the customer ID of the transferor, the customer ID of the transferee, the incentive ID to be transferred, the amount of transfer, and the date and time of transfer as one record in the transfer history DB 177. do. The control unit 11 transmits the incentive after the transfer to the transferor's customer terminal 2 via the communication unit 13 (step S189). The control unit 11 transmits the incentive issued to the transferee to the transferee's customer terminal 2 via the communication unit 13 (step S190), and ends the process.

According to this embodiment, it is possible for the customer to transfer the incentives obtained in response to the tip payment to others.

According to this embodiment, by transferring an incentive whose expiration date is approaching, it is possible to extend the expiration date of the incentive.

According to this embodiment, the transferee who has received the incentive can use the incentive at the restaurant to attract more customers.

The embodiments disclosed this time are illustrative in all respects and should be considered not restrictive. The scope of the present invention is indicated by the scope of the claims rather than the above-described meaning, and is intended to include all modifications within the scope and meaning equivalent to the scope of the claims.

1 Information processing device (server)
11 Control Unit 12 Storage Unit 13 Communication Unit 14 Input Unit 15 Display Unit 16 Reading Unit 17 Mass Storage Unit 171 Restaurant DB
172 Allocated party DB
173 Allocation history DB
174 Payment History DB
175 Incentive History DB
176 Work Management DB
177 Transfer History DB
1a portable storage medium 1b semiconductor memory 1P control program 2 information processing terminal (customer terminal)
21 control unit 22 storage unit 23 communication unit 24 input unit 25 display unit 26 photographing unit 2P control program 3 information processing terminal (store terminal)
31 control unit 32 storage unit 33 communication unit 34 input unit 35 display unit 3P control program

Claims (9)

Acquire the tip amount paid by the customer to the waiter at the restaurant,
Based on the acquired tip amount, calculate the total tip amount within a predetermined period for each restaurant,
calculating a transaction fee related to the chip allocation according to a predetermined standard;
Subtract the calculated transaction fee from the calculated tip total amount,
Based on the tip distribution rules defined for each restaurant, calculate the amount to be distributed to each recipient of the restaurant,
A program that causes a computer to execute processing for outputting the calculated total tip amount and the amount to be distributed to each recipient to the terminal of the restaurant. Allocating the tip amount after deducting the transaction fee to a plurality of the allottees, including a waiter who serves the customer or a cook who prepares the food, in a predetermined ratio;
2. The program according to claim 1, which causes execution of a process of storing the allocation history of the chip amount in a storage unit. Register incentive conditions for tips for each restaurant,
identifying an incentive according to the conditions of the incentive when the amount of the tip is obtained;
3. The program according to claim 1 or 2, wherein the specified incentive is output to the terminal of the customer who paid the tip amount. extending the expiration date of the incentive for a predetermined period if the customer transfers part of the incentive that is still valid;
4. The program according to claim 3, which causes execution of a process of outputting the incentive extended for a predetermined period to the terminal of the customer. 5. The program according to claim 3 or 4, which causes execution of a process of outputting the payment history of the tip and the acquisition history of the incentive according to the payment of the tip to a customer's terminal. 6. The program according to any one of claims 1 to 5, which outputs evaluation information according to the total tip amount within a predetermined period or the amount of allocation to each recipient for each restaurant. Each restaurant is ranked based on the total tip amount within a predetermined period or the amount distributed to each recipient,
7. The program according to claim 6, which causes execution of a process of outputting the result of the ranking as evaluation information. Acquire the tip amount paid by the customer to the waiter at the restaurant,
Based on the acquired tip amount, calculate the total tip amount within a predetermined period for each restaurant,
calculating a transaction fee related to the chip allocation according to a predetermined standard;
Subtract the calculated transaction fee from the calculated tip total amount,
Based on the tip distribution rules defined for each restaurant, calculate the amount to be distributed to each recipient of the restaurant,
An information processing method characterized by causing a computer to execute a process of outputting the calculated total tip amount and the amount to be distributed to each recipient to a terminal of a corresponding restaurant. an acquisition unit that acquires the tip amount paid by the customer to the waiter for consumption at the restaurant;
a first calculation unit that calculates the total tip amount within a predetermined period for each restaurant based on the acquired tip amount;
a second calculation unit that calculates a transaction fee related to the chip allocation according to a predetermined standard;
a subtraction part that subtracts the calculated transaction fee from the calculated tip total amount;
a third calculation unit that calculates an amount to be distributed to each of the allottees related to the restaurant based on a tip distribution rule determined for each restaurant;
An information processing apparatus, comprising: an output unit for outputting the calculated total tip amount and the amount to be distributed to each recipient to a terminal of a corresponding restaurant.

Images