Computer program, information processing device, and information processing method
A computer program automates rebate calculations for products near expiration, addressing the inefficiency of manual data transmission in existing systems, and promotes the purchase of such items to reduce food waste by providing incentives to consumers and retailers.
Patent Information
- Application Number
- JP2022057146
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-03-30
- Publication Date
- 2025-08-15
- Estimated Expiration
- 2042-03-30
AI Technical Summary
Existing information processing systems provide benefits for purchasing products near expiration dates but require users to transmit purchase information manually, which is time-consuming.
A computer program that calculates rebate amounts based on product type, expiration date, and price, automatically determining eligible products for rebates and awarding benefits to users and stores, utilizing a network of store terminals, servers, and user terminals to streamline the process.
Enables efficient calculation and distribution of rebates for products nearing expiration, reducing user effort and encouraging the purchase of such items, thereby reducing food waste and providing incentives to both consumers and retailers.
Smart Images

Figure 0007724180000001 
Figure 0007724180000002 
Figure 0007724180000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a computer program for calculating a rebate amount associated with a product purchase. [Background technology]
[0002] With the SDGs (Sustainable Development Goals) gaining attention, there is growing interest in reconsidering mass production and mass consumption. In retail stores, if a product is not purchased within a certain period of time after it arrives, it is discarded. Discarding a product not only wastes the resources consumed before it is on the shelves, but also consumes new resources when it is discarded.
[0003] Among products, food products with expiration dates are distributed on a daily basis, and so public and private sectors are working together to reduce the amount of waste, but progress has not been sufficient.In response to this situation, Patent Document 1 proposes an information processing system aimed at preventing the expiration of products sold in physical stores. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent No. 6462105 Summary of the Invention [Problem to be solved by the invention]
[0005] The information processing system described in Patent Document 1 provides a special benefit when a user purchases a product that is close to its expiration date. However, in order for the user to receive the special benefit, the user must transmit purchase information of the product to a server computer, which is time-consuming for the user.
[0006] The present invention has been made in light of these circumstances, and its purpose is to provide a computer program or the like that calculates the amount of currency or the like to be returned as a reward when a user engages in consumption behavior that leads to product disposal. [Means for solving the problem]
[0007] A computer program according to one aspect of the present application acquires sales data including a product type, expiration date, price, and sales slip number acquired by a store terminal, and payment data including the sales slip number and a user identifier, calculates a rebate amount based on the acquired product type, expiration date, and price, and outputs the calculated rebate amount in association with the user identifier. The amount of return is tallied for each store, a store where the total amount of return exceeds a threshold is selected, and a special benefit is awarded to the selected store. The processing is executed by a computer. [Effects of the Invention]
[0008] In one aspect of the present application, it is possible to calculate the amount of currency or the like to be returned to a user as a benefit. [Brief explanation of the drawings]
[0009] [Figure 1] FIG. 1 is an explanatory diagram showing an example of the configuration of a food loss reduction support system. [Figure 2] FIG. 2 is an explanatory diagram illustrating an example of the hardware configuration of a support server. [Figure 3] FIG. 2 is an explanatory diagram illustrating an example of the hardware configuration of a POS server. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of the hardware configuration of a business server. [Figure 5] FIG. 2 is an explanatory diagram illustrating an example of the hardware configuration of a user terminal. [Figure 6] FIG. 2 is an explanatory diagram showing an example of the configuration of a rebate rule DB. [Figure 7] FIG. 10 is an explanatory diagram showing an example of the configuration of a settlement sales DB. [Figure 8] FIG. 10 is an explanatory diagram showing an example of the configuration of a POS sales DB. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a refund amount DB. [Figure 10]FIG. 10 is an explanatory diagram showing an example of a member performance DB. [Figure 11] FIG. 10 is an explanatory diagram showing an example of a member store performance DB. [Figure 12] 10 is a flowchart illustrating an example of a procedure for calculating a refund amount. [Figure 13] 10 is a flowchart showing an example of a procedure for member benefit granting processing. [Figure 14] 10 is a flowchart showing an example of a procedure for a member store benefit granting process. [Figure 15] 10 is a flowchart illustrating an example of a procedure for a point display process. [Figure 16] 10 is a flowchart illustrating an example of a procedure for displaying points for affiliated stores. [Figure 17] FIG. 10 is an explanatory diagram showing an example of a point display screen. [Figure 18] FIG. 10 is an explanatory diagram showing an example of a member store point display screen. [Figure 19] 10 is a flowchart showing another example of the procedure of the return amount calculation process. DETAILED DESCRIPTION OF THE INVENTION
[0010] An embodiment will be described below with reference to the drawings. Figure 1 is an explanatory diagram showing an example of the configuration of a food loss reduction support system. The food loss reduction support system 100 includes a support server 1, a POS server 2, a business operator server 3, a POS register (store terminal) 4, and a user terminal 5. The support server 1, the POS server 2, the business operator server 3, the POS register 4, and the user terminal 5 are connected to each other via a network N so that they can communicate with each other.
[0011] The support server 1 is a computer that handles the main processes required to operate the food loss reduction support system 100. The support server 1 may be a computer operated by a business that provides cashless payments. It may also have the functions of the business server 3 described below. For example, the support server 1 may be operated by a cashless payment company such as a credit card company or an electronic money settlement institution. The support server 1 is composed of a server computer, a workstation, a PC (Personal Computer), etc. The support server 1 may also be composed of a multi-computer consisting of multiple computers, a virtual machine constructed virtually by software, or a quantum computer. Furthermore, the functions of the support server 1 may be realized by a cloud service.
[0012] The POS server 2 is a computer that stores POS (Point Of Sales) data. It receives and stores actual product sales data from a POS register 4 installed in the store. The POS server 2 is composed of a server computer, a workstation, a PC, etc. The POS server 2 may also be composed of a multi-computer consisting of multiple computers, a virtual machine virtually constructed by software, or a quantum computer. Furthermore, the functions of the POS server 2 may be realized by a cloud service. Although three POS servers 2 are shown in FIG. 1, this is not limiting. The number of POS servers 2 may be one, two, or four or more.
[0013] The business server 3 is a computer operated by a business that provides cashless payments. Examples of such businesses include credit card companies and electronic money settlement institutions. The business server 3 stores the history of cashless payments. Although three business servers 3 are shown in FIG. 1, this is not a limitation. The number of business servers 3 may be one, two, or four or more. There are three types of cashless payments: postpay, such as with a credit card; prepay, in which money is deposited (charged) in advance; and real-time pay, in which money is debited directly from a savings account using a debit card or two-dimensional code, but this specification does not consider the type. Cashless payments using smartphones are also covered in this specification.
[0014] A store is a retail store that sells food. The food loss reduction support system 100 is a system that supports the reduction of food waste, so it does not target stores that do not sell food. Although only one store is shown in Figure 1, there may be multiple stores. In this specification, stores are referred to as affiliated stores, assuming that they are participating in the food loss reduction support system 100.
[0015] A POS register 4 is installed in the store. The POS register 4 reads barcodes and other items attached to products, stores sales information including the product code, sale date and time, sales price, and number of items sold, and transmits the sales information to the POS server 2 as needed. Furthermore, when a customer of the store wishes to pay for purchased products using a cashless payment service, the POS register 4 communicates with the business server 3 and performs the payment. Multiple POS registers 4 may be installed in one store.
[0016] The user terminal 5 is a terminal used by an end user. The end user is assumed to be an ordinary consumer who purchases food at a store. The user terminal 5 is composed of a smartphone, tablet computer, etc. In this specification, the end user is referred to as a member, assuming that the end user is participating in the food loss reduction support system 100.
[0017] Next, an overview of the processing performed by the food waste reduction support system 100 will be explained. When a member shops at an affiliated store, they select an item with the shortest number of days until its expiration date from the items on display. The member pays at the POS register. At this time, the POS register 4 reads the barcode or other data attached to the item. The member pays for the item using cashless payment. The POS register 4 sends POS data to the POS server 2. The POS data includes the product code, number of items sold, sales amount, expiration date, sales date and time, sales slip number, terminal code, store code, etc. The product code is a code that can uniquely identify the product. The terminal code is a code that can identify the POS register 4. The store code (store identifier) is a code that can identify the affiliated store. The POS server 2 stores the received POS data. Meanwhile, the POS register 4 sends payment data to the business operator server 3. The business operator server 3 performs payment. The business operator server 3 sends the payment data to the support server 1. If the support server 1 is acting as a payment agent, the POS register 4 sends the payment data to the support server 1. The support server 1 performs payment on behalf of the business operator. The support server 1 transmits payment data to the business operator server 3. The payment data includes the payment amount, payment date and time, sales slip number, terminal code, store code, etc.
[0018] The support server 1 acquires POS data from the POS server 2 using the sales slip number included in the payment data as a key. If the POS data contains a purchase history of a product that matches a predetermined rule, for example, a product whose expiration date is within three days of the date and time of sale, the support server 1 calculates the rebate amount. The support server 1 creates rebate amount data including the sales slip number and rebate amount and sends it to the business server 3. The business server 3 rebates the member based on the rebate amount data by cashback, awarding points, etc.
[0019] 2 is an explanatory diagram showing an example of the hardware configuration of the support server 1. The support server 1 includes a control unit 11, a main memory unit 12, an auxiliary memory unit 13, a communication unit 14, and a reading unit 15. The control unit 11, the main memory unit 12, the auxiliary memory unit 13, the communication unit 14, and the reading unit 15 are connected by a bus B.
[0020] The control unit 11 has one or more arithmetic processing devices such as a central processing unit (CPU), a micro-processing unit (MPU), a graphics processing unit (GPU), etc. The control unit 11 reads and executes a control program 1P (program, program product) stored in the auxiliary storage unit 13, thereby performing various information processing, control processing, etc. related to the support server 1, and realizing various functional units such as an acquisition unit, a calculation unit, an output unit, etc.
[0021] The main memory unit 12 is a static random access memory (SRAM), a dynamic random access memory (DRAM), a flash memory, etc. The main memory unit 12 mainly temporarily stores data required for the control unit 11 to execute arithmetic processing.
[0022] The auxiliary memory unit 13 is a hard disk or SSD (Solid State Drive), etc., and stores the control program 1P and various DBs (Databases) required for the control unit 11 to execute processing. The auxiliary memory unit 13 stores a rebate rule DB 131, a payment sales DB 132, a POS sales DB 133, a rebate amount DB 134, a member performance DB 135, and an affiliated store performance DB 136. The auxiliary memory unit 13 may be separate from the support server 1 and may be a storage device externally connected to the support server 1. The various DBs, etc. stored in the auxiliary memory unit 13 may be stored in a database server or cloud storage different from the support server 1.
[0023] The communication unit 14 communicates with the POS server 2 and the business server 3 via the network N. In addition, the control unit 11 may use the communication unit 14 to download the control program 1P from another computer via the network N or the like and store it in the auxiliary storage unit 13.
[0024] The reading unit 15 reads the portable storage medium 1a including a CD (Compact Disc)-ROM and a 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 15 and store it in the auxiliary storage unit 13. The control unit 11 may also read the control program 1P from the semiconductor memory 1b.
[0025] 3 is an explanatory diagram showing an example of the hardware configuration of a POS server 2. The POS server 2 includes a control unit 21, a main memory unit 22, an auxiliary memory unit 23, and a communication unit 24. The control unit 21, the main memory unit 22, the auxiliary memory unit 23, and the communication unit 24 are connected by a bus B.
[0026] The control unit 21 has one or more arithmetic processing units such as a CPU, an MPU, a GPU, etc. The control unit 21 reads and executes a control program 2P (program, program product) stored in the auxiliary storage unit 23, thereby performing various information processing, control processing, etc. related to the POS server 2 and realizing various functional units.
[0027] The main memory unit 22 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 22 mainly temporarily stores data necessary for the control unit 21 to execute arithmetic processing.
[0028] The auxiliary storage unit 23 is a hard disk or an SSD, etc., and stores the control program 2P and various DBs required for the control unit 21 to execute processing. The auxiliary storage unit 23 stores a POS sales DB 133. The auxiliary storage unit 23 may be separate from the POS server 2 and may be a storage device externally connected to the POS server 2. The DBs and the like stored in the auxiliary storage unit 23 may be stored in a database server or cloud storage different from the POS server 2.
[0029] The communication unit 24 communicates with the support server 1 and the business operator server 3 via the network N. In addition, the control unit 21 may use the communication unit 24 to download the control program 2P from another computer via the network N or the like and store it in the auxiliary storage unit 23.
[0030] 4 is an explanatory diagram showing an example of the hardware configuration of the business server 3. The business server 3 includes a control unit 31, a main memory unit 32, an auxiliary memory unit 33, and a communication unit 34. The control unit 31, the main memory unit 32, the auxiliary memory unit 33, and the communication unit 34 are connected by a bus B.
[0031] The control unit 31 has one or more arithmetic processing devices such as a CPU, an MPU, a GPU, etc. The control unit 31 reads and executes a control program 3P (program, program product) stored in the auxiliary storage unit 33, thereby performing various information processing, control processing, etc. related to the business entity server 3 and realizing various functional units.
[0032] The main memory unit 32 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 32 mainly temporarily stores data required for the control unit 31 to execute arithmetic processing.
[0033] The auxiliary storage unit 33 is a hard disk, an SSD, or the like, and stores the control program 3P and various DBs required for the control unit 31 to execute processing. The auxiliary storage unit 33 stores a settlement sales DB 331 and a rebate amount DB 332. The auxiliary storage unit 33 may be separate from the business operator server 3 and may be a storage device externally connected to the business operator server 3. The DBs and the like stored in the auxiliary storage unit 33 may be stored in a database server or cloud storage different from the business operator server 3.
[0034] The communication unit 34 communicates with the support server 1 and the POS server 2 via the network N. In addition, the control unit 31 may use the communication unit 34 to download the control program 3P from another computer via the network N or the like and store it in the auxiliary storage unit 33.
[0035] 5 is an explanatory diagram showing an example of the hardware configuration of a user terminal. The user terminal 5 includes a control unit 51, a main memory unit 52, an auxiliary memory unit 53, a communication unit 54, a short-range wireless communication unit 55, a display panel 56, and an operation unit 57. Each unit is connected by a bus B.
[0036] The control unit 51 has one or more arithmetic processing units such as a CPU, an MPU, a GPU, etc. The control unit 51 provides various functions by reading and executing a control program 5P (program, program product) stored in the auxiliary storage unit 53.
[0037] The main memory unit 52 is an SRAM, a DRAM, a flash memory, etc. The main memory unit 52 mainly temporarily stores data required for the control unit 51 to execute arithmetic processing.
[0038] The auxiliary memory unit 53 is a hard disk or SSD, etc., and stores various data necessary for the control unit 51 to execute processing. The auxiliary memory unit 53 stores a membership code (user identifier) 531. The membership code 531 is a code that can uniquely identify a member. The auxiliary memory unit 53 may be separate from the user terminal 5 and may be an external storage device that is externally connected. The various DBs, etc. stored in the auxiliary memory unit 53 may be stored in a database server or cloud storage.
[0039] The communication unit 54 communicates with the business server 3 and the like via the network N. In addition, the control unit 51 may use the communication unit 54 to download the control program 5P from another computer via the network N and the like, and store the control program 5P in the auxiliary storage unit 53.
[0040] The short-range wireless communication unit 55 communicates with other devices via wireless communication in accordance with the NFC (Near Field Communication) standard or ISO / IEC 18092 and ISO / IEC 21481. For example, the short-range wireless communication unit 55 communicates with the POS register 4 to perform cashless payment.
[0041] The display panel 56 is configured with a liquid crystal panel, an organic EL (Electro Luminescence) display, or the like. The operation unit 57 may be configured with, for example, a touch panel incorporated in the display panel 56, and the user can perform predetermined operations on the display panel 56. The operation unit 57 can also be used to perform operations on a software keyboard displayed on the display panel 56. The operation unit 57 may also be a hardware keyboard, a mouse, or the like.
[0042] Next, the databases provided in the support server 1 will be described. FIG. 6 is an explanatory diagram showing an example of the configuration of the rebate rule DB. The rebate rule DB 131 stores rebate rules. The rebate rules are rules for calculating the amount of money (rebate amount) to be rebated as a reward when a member purchases a product whose expiration date is approaching. The rebate rule DB 131 includes an item column, a remaining days column, and a coefficient column. The item column stores the item of the product eligible for rebate. The remaining days column stores the condition of the number of days until the expiration date. The coefficient column stores the coefficient used to calculate the rebate amount. For example, the rebate amount is calculated by multiplying the sales amount by the coefficient.
[0043] In FIG. 6, a coefficient is set for each item, but it may be a uniform coefficient regardless of the item, or may be set for each product in more detail than the item. Also, a rebate rule DB is stored to vary the rebate amount depending on the sales amount, but this is not limited to this. If a fixed rebate is provided regardless of the sales amount, the rebate amount is stored in association with the item. Furthermore, a configuration in which items associated with a coefficient and items associated with a rebate amount are mixed is also possible.
[0044] Figure 7 is an explanatory diagram showing an example of the configuration of a payment sales DB. The payment sales DB 132 stores the history of cashless payments. The payment sales DB 132 includes a payment amount column, a payment date and time column, a sales slip number column, a member CD column, a terminal CD column, and a store CD column. The payment amount column stores the paid amount. The payment date and time column stores the date and time of payment. The sales slip number column stores the number of the sales slip issued by the POS register 4. The member CD column stores a member code that identifies the member who electronically paid the purchase price. The member code is read from the credit card held by the member or from the user terminal. The terminal CD column stores the terminal code attached to the POS register 4. The terminal code is a code that identifies the POS register 4. The store CD column stores a store code that identifies the affiliated store.
[0045] FIG. 8 is an explanatory diagram showing an example of the configuration of the POS sales DB. The POS sales DB 133 stores sales data sent from the POS register 4. This sales data is a copy of the sales data stored in the POS server 2. The POS sales DB 133 includes a product CD column, a quantity column, a sales amount column, a sales date and time column, an expiration date column, a sales slip number column, a terminal CD column, and a store CD column. The product CD column stores a code that identifies the product sold. The quantity column stores the number of products sold. The sales amount column stores the sales amount for each product. If one product is sold, the sales amount column stores the unit sales price of the product. If multiple products are sold, the sales amount column stores the result of multiplying the unit sales price of the product by the number of products. The sales date and time column stores the date and time the product was sold. The expiration date column stores the expiration date of the product. The expiration date is included in information stored in barcodes, two-dimensional codes, IC tags, etc. These barcodes, etc. are affixed to the products. When a product is registered at the POS register 4, the barcode, two-dimensional code, IC tag, etc. is read and the expiration date is stored as one item of sales data. The sales slip number column stores the number of the sales slip issued by the POS register 4. The terminal CD column stores the terminal code attached to the POS register 4. The terminal code is a code that identifies the POS register 4. The store CD column stores the store code that identifies the affiliated store.
[0046] FIG. 9 is an explanatory diagram showing an example of a rebate amount DB. The rebate amount DB 134 stores rebate amounts for each sales slip. The rebate amount DB 134 includes a sales slip number column and a rebate amount column. The sales slip number column stores the sales slip number. The rebate amount column stores the rebate amount. If a sales slip contains multiple products eligible for rebates, the rebate amount column stores the total rebate amount.
[0047] FIG. 10 is an explanatory diagram showing an example of a member achievement DB. Member achievement DB 135 stores the achievement of a member receiving a rebate. Member achievement DB 135 includes a member CD column, a sales slip number column, a rebate amount column, and a rebate date column. The member CD column stores a member code. The sales slip number column stores a sales slip number. The rebate amount column stores the amount rebated to the member. The rebate date column stores the date of the rebate. If the member is rebated in the form of points or the like rather than cash, the number of points or the like rebated may be stored in member achievement DB 135. Furthermore, if the rebate amount for each sales slip is returned to the member as is, the member achievement DB includes the contents of rebate amount DB 134, so rebate amount DB 134 may not be necessary.
[0048] FIG. 11 is an explanatory diagram showing an example of an affiliated store performance DB. The affiliated store performance DB 136 stores the daily rebate performance of each affiliated store. The affiliated store performance DB 136 includes a store CD column, a rebate amount column, and a rebate date column. The store CD column stores the store code. The rebate amount column stores the rebate amount. The rebate date column stores the date the rebate was made. The rebate amount stored in the rebate amount column is the total rebate amount for each sales slip. If the rebate amount for each sales slip is shared between the affiliated store and the member, the rebate amount stored in the rebate amount column may be the total amount given to the affiliated store excluding the rebate amount to the member.
[0049] The POS server 2 includes a POS sales DB 231. The POS sales DB 231 has the same configuration as the POS sales DB 133 shown in Fig. 8, and therefore illustration and description thereof will be omitted.
[0050] The business operator server 3 includes a settlement sales DB 331 and a refund amount DB 332. The settlement sales DB 331 has the same configuration as the settlement sales DB 132 shown in Fig. 7, so illustration and description thereof will be omitted. The refund amount DB 332 has the same configuration as the refund amount DB 134 shown in Fig. 9, so illustration and description thereof will be omitted.
[0051] Next, the information processing performed by the food waste reduction support system 100 will be described. FIG. 12 is a flowchart showing an example of the procedure for the rebate calculation process. The rebate calculation process may be performed each time sales data is generated through electronic payment, or may be performed by batch processing, for example, once a day. The control unit 11 of the support server 1 acquires one POS sales data item (step S1). One POS sales data item consists of one or more records with the same sales slip number. The control unit 11 selects one record included in the POS sales data (step S2). The control unit 11 determines whether the sales data of the product included in the selected record is eligible for rebates (step S3). Based on the product CD included in the selected record, the control unit 11 references the product master (not shown) to acquire the product item. Based on the sales date and expiration date included in the record, the control unit 11 calculates the number of days before the expiration date that the product was purchased. The control unit 11 compares the product item and the number of days before the expiration date with the rebate rules stored in the rebate rule DB 131 to determine whether the sales data of the product is eligible for rebates. If there is a corresponding rebate rule, the control unit 11 determines that the item is eligible for rebate; if there is no corresponding rebate rule, the control unit 11 determines that the item is not eligible for rebate. If the control unit 11 determines that the item is not eligible for rebate (NO in step S3), the control unit 11 proceeds to step S6. If the control unit 11 determines that the item is eligible for rebate (YES in step S3), the control unit 11 calculates the rebate amount based on the rebate rule (step S4). The control unit 11 temporarily stores the calculated rebate amount in a temporary storage area (step S5). The temporary storage area is provided in the main storage unit 12 or the auxiliary storage unit 13. The control unit 11 determines whether or not there are unprocessed records (step S6). If the control unit 11 determines that there are unprocessed records (YES in step S6), the control unit 11 returns the process to step S2 and processes the unprocessed records. If the control unit 11 determines that there are no unprocessed records (NO in step S6), the control unit 11 determines whether or not to request payment sales data (step S7). If the refund amount is not stored in the temporary storage area, the control unit 11 determines that the POS sales being processed are not eligible for refund, and therefore does not request the settlement sales data.If the rebate amount is stored in the temporary storage area, the control unit 11 determines that the POS sales being processed are eligible for rebate and therefore requests payment sales data. If the control unit 11 determines that payment sales data is not being requested (NO in step S7), it proceeds to step S13. If the control unit 11 determines that payment sales data is being requested (YES in step S7), it sends a request for payment sales data to the business server (step S8). The request includes a sales slip number. The control unit 31 of the business server 3 receives the request (step S9). The control unit 31 reads the payment sales data, including the sales slip number included in the request, from the payment sales DB 331 and sends it to the support server 1 (step S10). The control unit 11 of the support server 1 receives the payment sales data (step S11). The control unit 11 stores the results (step S12). The control unit 11 calculates the total rebate amount stored in the temporary storage area, associates the total rebate amount with the sales slip number, and stores it in the rebate amount DB 134. The control unit 11 also calculates the refund amount (refund amount) to the member from the total refund amount, and stores the calculated refund amount in the member record DB 135 in association with the member code, sales slip number, and refund date. The refund date may be the date on which the refund calculation process was executed, the date on which the payment was made, or the date on which the sales slip number was issued (i.e., the date on which the product was purchased). The control unit 11 determines whether there is unprocessed POS sales data (step S13). If the control unit 11 determines that there is unprocessed POS sales data (YES in step S13), it returns the process to step S1 and processes the unprocessed POS sales data. If the control unit 11 determines that there is no unprocessed POS sales data (NO in step S13), it transmits the refund data newly stored in the refund amount DB 134 in this process to the business operator server 3 (step S14). The control unit 31 of the business operator server 3 receives the refund data (step S15). The control unit 31 stores the received refund data in the refund amount DB 332 (step S16). The refund calculation process ends.
[0052] Based on the rebate data stored in the rebate amount DB 332 of the business server 3, the business provides incentives to members, such as cash back, points, and waived annual membership fees. In addition, the business may provide rebates to affiliated stores, such as a reduction in the affiliated store commission rate, based on the rebate data.
[0053] In addition, in step S4 of the cashback calculation process, the cashback amount for the affiliated store may be calculated from the total cashback amount, and the calculated cashback amount may be stored in a temporary storage area in association with the store code. Then, between steps S13 and S14, the total cashback amount for each affiliated store may be calculated, and the calculated cashback amount may be stored in affiliated store record DB 136 in association with the store code and cashback date. The cashback date shall be the same date as the cashback date in member record DB 135.
[0054] Although the control unit 11 of the supporter 1 transmits the newly stored rebate data in the rebate amount DB 134 to the business operator server 3, this is not limitative. The control unit 11 may transmit the newly stored data in the member record DB 135 to the business operator server 3. In this case, for example, a member record DB similar to the member record DB 135 is provided in the auxiliary storage unit 33 of the business operator server 3, and the control unit 31 of the business operator server 3 stores the received data in the member record DB.
[0055] Next, we will explain the process of granting benefits based on the cashback status over a specified period. For example, we will explain the case where benefits are granted based on the number of cashbacks received per year. Figure 13 is a flowchart showing an example of the steps of the member benefit granting process. We will explain the process as being executed by the support server 1. The member benefit granting process is executed, for example, once a month. The control unit 11 of the support server 1 acquires the items to be counted (step S31). For example, it acquires the counting period and the membership codes of the members to be counted from the business server 3. The control unit 11 performs the counting (step S32). For example, the control unit 11 refers to the member performance DB 135 and counts the number of records of the target member during the counting period for each target member. The number of records can be considered as the number of times the member contributed to reducing food waste over a year. The control unit 11 selects members whose counted number of records exceeds a specified threshold (step S33). The control unit 11 sends the membership code of the selected member to the business server 3 (step S34) and ends the process. The business server 3 provides a benefit to the member whose membership code is received from the support server 1, such as free membership fees for the next year.
[0056] FIG. 14 is a flowchart showing an example of the procedure for the member store reward granting process. The support server 1 is assumed to execute the member store reward granting process. The support server 1 executes the member store reward granting process, for example, once every six months. The control unit 11 of the support server 1 compiles the results for each member store (step S41). For example, the control unit 11 compiles the total rebate amount for each member store during the compilation period. The control unit 11 selects a member store to which a reward is to be granted (step S42). For example, the control unit 11 selects a member store whose total rebate amount exceeds a predetermined threshold. The threshold may vary depending on the type of business or store size. Alternatively, the control unit 11 may select a member store whose total rebate amount divided by the total payment amount during the compilation period exceeds a threshold. By dividing by the total payment amount, it is not necessary to change the threshold depending on the store size. The control unit 11 grants a reward to the selected member store (step S43) and terminates the process. For example, the control unit 11 sends the store CD of the member store to the business server 3, requesting that the commission rate of the relevant member store be reduced by 0.5 points for the next six months. If the commission rate is 3%, it will be 2.5%.
[0057] Next, the display of benefits will be explained. In the following, it is assumed that points are awarded to both members and affiliated stores using the rebate amount as a source of funds. Points awarded to members are stored in the member record DB 135. Points awarded to affiliated stores are stored in the affiliated store record DB 136.
[0058] FIG. 15 is a flowchart showing an example of the procedure for point display processing. A member operates the user terminal 5 to instruct the display of points. The control unit 51 of the user terminal 5 sends a request to display points to the support server 1 (step S51). The control unit 11 of the support server 1 receives the request (step S52). The control unit 11 extracts the results required for display from the member result DB 135 (step S53). For example, the extracted results are those for the current month. The control unit 11 creates a screen based on the extracted results (step S54). The control unit 11 sends the screen to the user terminal 5 (step S55). The control unit 51 of the user terminal 5 receives the screen (step S56). The control unit 51 displays it on the display panel 56 (step S57), and the process ends.
[0059] FIG. 16 is a flowchart showing an example of the procedure for processing points display for affiliated stores. A store clerk at an affiliated store operates the POS register 4 to instruct the display of points. The POS register 4 sends a request to display points to the support server 1 (step S71). The control unit 11 of the support server 1 receives the request (step S72). The control unit 11 extracts the results needed for display from the affiliated store results DB 136 (step S73). For example, the extracted results are those for the current month. The control unit 11 creates a screen based on the extracted results (step S74). The control unit 11 sends the screen to the POS register 4 (step S75). The POS register 4 receives the screen (step S76). The POS register displays the received screen on an LCD display or the like (step S77), and the process ends.
[0060] FIG. 17 is an explanatory diagram showing an example of a points display screen. The points display screen d01 includes a total display d011 and a daily display d012. The total display d011 shows the total points awarded in the current month. The daily display d012 shows the points awarded in the current month by day. Note that the daily display d012 displays the date and number of points, but is not limited to this. Information such as the product for which points were awarded and the number of days before the expiration date when the purchase was made may also be displayed.
[0061] FIG. 18 is an explanatory diagram showing an example of a points display screen for affiliated stores. The points display screen d02 for affiliated stores includes a daily display d021 and a total display d022. The daily display d021 shows the points awarded for the current month by day. The total display d022 shows the total points awarded for the current month. Note that the daily display d021 displays the date and the number of points, but this is not limited to this. Information such as the product for which points were awarded, information about the member who purchased it, and the number of days before the expiration date on the purchase date may also be displayed.
[0062] The above-described embodiment has the following effects. By purchasing products with an approaching expiration date, members can receive benefits such as free annual membership fees, which encourages them to proactively purchase products with an approaching expiration date. Furthermore, affiliated stores can receive benefits such as a lower commission rate by having members purchase products with an approaching expiration date. This allows them to create sales areas and conduct educational activities, which is expected to increase sales of products with an approaching expiration date. As a result, it is expected that food waste will be reduced.
[0063] Furthermore, because the food loss reduction support system uses POS data, members do not need to take a photo of a receipt listing the item, price, purchase date, etc. with the user terminal 5, or enter accounting data into the user terminal 5. Members can easily receive benefits for purchasing products that are close to their expiration date.
[0064] In the rebate calculation process shown in Figure 12, the control unit 11 of the support server 1 acquires POS sales data, and then acquires payment sales data with a common sales slip number as needed. Alternatively, the control unit 11 may acquire POS sales data with a common sales slip number after acquiring payment sales data. The rebate calculation process in this case will be described below.
[0065] FIG. 19 is a flowchart showing another example of the procedure for the rebate calculation process. Similar to the rebate calculation process shown in FIG. 12, the rebate calculation process shown in FIG. 19 may be performed each time sales data is generated through electronic payment, or may be performed as a batch process, for example, once a day. The control unit 11 of the support server 1 acquires payment sales data (step S91). The control unit 11 sends a request for POS sales data corresponding to the sales slip number included in the payment sales data to the POS server 2 (step S92). The control unit 21 of the POS server 2 receives the request (step S93). The control unit 21 acquires POS sales data corresponding to the sales slip number from the POS sales DB 231 and sends it to the support server 1 (step S94). The control unit 11 of the support server 1 receives the POS sales data (step S95). The received POS sales data consists of one or more records with the same sales slip number. The control unit 11 selects one record from the POS sales data (step S96). The control unit 11 determines whether the sales data of the product included in the selected record is eligible for rebate (step S97). Based on the product CD included in the selected record, the control unit 11 references the product master (not shown) to acquire the product item. Based on the sales date and time and expiration date included in the record, the control unit 11 calculates how many days before the expiration date the product was purchased. The control unit 11 compares the product item and the number of days before the expiration date with the rebate rules stored in the rebate rule DB 131 to determine whether the sales data of the product is eligible for rebate. If there is a corresponding rebate rule, the control unit 11 determines that the product is eligible for rebate. If there is no corresponding rebate rule, the control unit 11 determines that the product is not eligible for rebate. If the control unit 11 determines that the product is not eligible for rebate (NO in step S97), the control unit 11 proceeds to step S100. If the control unit 11 determines that the product is eligible for rebate (YES in step S97), the control unit 11 calculates the rebate amount based on the rebate rules (step S98). The control unit 11 temporarily stores the calculated rebate amount in a temporary storage area (step S99). The temporary storage area is provided in the main storage unit 12 or the auxiliary storage unit 13. The control unit 11 determines whether or not there are any unprocessed records (step S100). If the control unit 11 determines that there are any unprocessed records (YES in step S100), the process returns to step S96, and the unprocessed records are processed.If the control unit 11 determines that there are no unprocessed records (NO in step S100), it stores the results (step S101). The control unit 11 calculates the total refund amount stored in the temporary storage area, associates the total refund amount with the sales slip number, and stores it in the refund amount DB 134. The control unit 11 also calculates the refund amount (refund amount) to the member from the total refund amount, and stores the calculated refund amount in the member results DB 135, associates it with the member code, sales slip number, and refund date. The refund date is the date the refund amount calculation process was executed, the date the payment was made, or the date the sales slip number was issued = the date the product was purchased, etc. The control unit 11 determines whether there is unprocessed payment sales data (step S102). If the control unit 11 determines that there is unprocessed payment sales data (YES in step S102), it returns the process to step S91 and processes the unprocessed payment sales data. If the control unit 11 determines that there is no unprocessed payment sales data (NO in step S102), it transmits the rebate data newly stored in the rebate amount DB 134 in this process to the business operator server 3 (step S103). The control unit 31 of the business operator server 3 receives the rebate data (step S104). The control unit 31 stores the received rebate data in the rebate amount DB 332 (step S105). The rebate amount calculation process ends.
[0066] The technical features (constituent elements) described in each embodiment can be combined with each other, and by combining them, new technical features can be formed. The embodiments disclosed herein are to be considered as illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]
[0067] 100 Food waste reduction support system 1 Support Server 11 Control section 12 Main memory 13 Auxiliary storage 131 Return Rules DB 132 Payment Sales DB 133 POS sales DB 134 Rebate DB 135 Membership performance database 136 Member store performance database 14 Communications Department 15 Reading unit 1P control program 1a Portable storage media 1b semiconductor memory 2. POS Server 21 Control section 22 Main memory 23 Auxiliary storage 231 POS sales DB 24 Communications Department 2P control program 3. Operator server 31 Control Unit 32 Main memory 33 Auxiliary storage section 331 Payment Sales DB 332 Rebate DB 34 Communications Department 3P control program 4. POS register 5. User terminal 51 Control section 52 Main memory 53 Auxiliary storage section 531 Membership Code 54 Communications Department 55 Near Field Wireless Communication Department 56 Display panel 57 Operation section 5P control program B Bus N Network
Claims
1. Acquire sales data including the product type, expiration date, amount, and sales slip number, as well as payment data including the sales slip number and user identifier, acquired by the store terminal; The amount of the refund will be calculated based on the purchased item, expiration date, and amount. outputting the calculated rebate amount in association with the user identifier; The amount of the return is tallied for each store, Select stores where the total amount of cashback exceeds a threshold, Give rewards to selected stores A computer program that causes a computer to perform a process.
2. A store is selected in which the value of the total amount of cashback divided by the total amount of payment at the store exceeds a threshold.
2. The computer program of claim 1.
3. After acquiring the sales data, the payment data corresponding to the sales slip number included in the acquired sales data is acquired.
3. A computer program according to claim 1 or claim 2.
4. After acquiring the payment data, the sales data corresponding to the sales slip number included in the acquired payment data is acquired.
3. A computer program according to claim 1 or claim 2.
5. The payment data is obtained from a database operated by a credit card company or an electronic money payment institution. A computer program according to any one of claims 1 to 4.
6. and providing a currency or points equivalent to the amount of the refund. A computer program according to any one of claims 1 to 5.
7. an acquisition unit that acquires sales data including the product type, expiration date, amount, and sales slip number acquired by the store terminal, and payment data including the sales slip number and user identifier; A calculation unit that calculates the amount of rebate based on the acquired item, expiration date, and amount; an output unit that outputs the calculated rebate amount in association with the user identifier; A counting unit that counts the return amount for each store; a selection unit that selects a store where the aggregated return amount exceeds a threshold; an awarding unit that awards a benefit to the selected store; An information processing device comprising:
8. The computer Acquire sales data including the product type, expiration date, amount, and sales slip number, as well as payment data including the sales slip number and user identifier, acquired by the store terminal; The amount of the refund will be calculated based on the purchased item, expiration date, and amount. outputting the calculated rebate amount in association with the user identifier; The amount of the return is tallied for each store, Select stores where the total amount of cashback exceeds a threshold, Give rewards to selected stores An information processing method that performs processing.
Citation Information
Patent Citations
Handy polisher
JP1989062105A
Information processing system
JP2012032904A
Output control method, output control device, and computer program
JP2013229066A
Point system
JP2014144374A
Settlement support system and portable terminal
JP2018025844A