Extended warranty management system, server, and program

Abstract

To provide an extended warranty management system, a server, and a program for enabling a purchaser of goods to centrally manage extended warranties for a plurality of goods.SOLUTION: An extended warranty management system 10 for managing an extended warranty against natural failure or product damage of goods is provided with a server 1 connected to a database 2 capable of storing purchaser information and warranty information and capable of writing and reading purchaser information and the like to and from the database 2. The server 1 has API cooperation means for enabling API cooperation with an EC site or the like 3 for selling goods, and causes the server 1 to execute extension warranty management processing based on an extended warranty purchased with the goods at the EC site or the like 3 through the API cooperation with the EC site or the like 3. The extended warranty management processing includes a process for associating the purchaser information with the warranty information, a process for transmitting the associated warranty information to a terminal of the purchaser of the goods, a process for receiving a warranty application, a process for recording history information of the warranty application, and a process for transmitting the history information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an extended warranty management system, a server, and a program for managing extended warranties for products. [Background technology]

[0002] Conventionally, it is known that a server owned by a seller of a product manages information on products purchased by users. For example, a system is known in which product identification information and warranty information are stored in a management server, and the system provides warranty information or determines whether or not the warranty contents can be fulfilled in response to a request from a user (Patent Document 1).

[0003] Also, there is known an extended warranty that provides free repairs for product failures that occur within a certain period after the expiration of the manufacturer's warranty (Patent Document 2).

[0004] Furthermore, an extended warranty system has been proposed in which, when a product purchaser purchases an extended warranty at the time of purchase, the burden on the product seller to manage and operate the extended warranty is reduced, and the operating company or warranty company providing the extended warranty can monitor the status of extended warranty subscription at any time, allowing product purchasers to easily subscribe to an extended warranty at the time of purchase (Patent Document 3). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2005-234981 A [Patent Document 2] JP 2018-032184 A [Patent Document 3] Patent No. 7164255 Summary of the Invention [Problem to be solved by the invention]

[0006] However, in the extended warranty system of Patent Document 3, it was necessary to check for each product whether the extended warranty had been subscribed to, whether the extended warranty period was in effect, the warranty period, the warranty fee, and other details of the extended warranty, making it cumbersome for product purchasers to manage the extended warranty.

[0007] Therefore, there is a demand for an extended warranty management system that allows a purchaser of a product to centrally manage extended warranties for multiple products. [Means for solving the problem]

[0008] The gist of the present invention is as follows. (1) An extended warranty management system for managing extended warranties for natural failures or physical damage of products, a server connected to a database capable of storing product information identifying the product, purchase information identifying a purchase action of the product, purchaser information identifying a purchaser of the product, and warranty information identifying details of an extended warranty linked to at least one selected from the group consisting of the product information, the purchase information, and the purchaser information, and capable of writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; The server has an API linking means capable of API linking with an EC site or a POS register that sells the product, and causing the server to execute an extended warranty management process based on the extended warranty purchased together with the product at the EC site or the POS register through the API linkage with the EC site or the POS register; The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product Extended warranty management system, including: (2) The extended warranty management system described in (1) above, wherein the historical information includes acceptance information of the warranty application, repair information of the product, shipping information after repair of the product, warranty completion information, or a combination thereof. (3) An extended warranty management system as described in (1) or (2) above, wherein the warranty application receiving process includes a slip information sending process for sending to the purchaser's terminal a reception number or information code linked to slip information for returning a product that has naturally failed or been damaged. (4) The purchaser information includes the following: (A) to (H): (A) An ID given to the purchaser, (B) the purchaser’s email address, social media address, or any combination thereof; (C) the purchaser's telephone number; (D) The name of said purchaser; (E) the purchaser's date of birth; (F) the address of said purchaser; (G) the purchaser's insurance policy number, and (H) The purchaser's My Number The extended warranty management system according to any one of (1) to (3) above, comprising at least one selected from the group consisting of: (5) An extended warranty management system according to any one of (1) to (4) above, wherein the product information includes at least one selected from the group consisting of the product's manufacturer, product name, model number, and product code. (6) An extended warranty management system described in any of (1) to (5) above, wherein the purchase information includes an ID of the EC site or POS register, and a purchase ID of the product, which includes the purchase date of the product and the purchase price of the product. (7) An extended warranty management system as described in any of (1) to (6) above, wherein the warranty information includes a warranty type, including replacement of the product, repair of the product, or refund of at least a portion of the purchase price of the product, a failure mode covered by the product's warranty, a warranty period, a warranty fee, a warranty number, or a combination thereof. (8) An extended warranty management system as described in any of (1) to (7) above, wherein the warranty application receiving process includes causing the server to determine whether the purchaser information included in the warranty application matches the purchaser information stored in the database. (9) The extended warranty management system described in (7) above, wherein the warranty application receiving process includes having the server determine whether the warranty number included in the warranty application matches the warranty number stored in the database. (10) The extended warranty management system described in (4) above, wherein the purchaser information includes the purchaser's email address or telephone number. (11) To the server (A) a coupon code issuance application process that, based on the warranty application, applies to the EC site or POS register via the API integration for the issuance of a coupon code that allows the purchase of an identical product or an alternative product free of charge or at a partial cost, the repair of the product free of charge or at a partial cost, or a refund of at least a portion of the purchase price of the product; A coupon code receiving process for receiving a coupon code created on the EC site or the POS register based on the issuance request through the API linkage; and A coupon code transmission process for transmitting the received coupon code to the purchaser's terminal; (B) a pseudo-order information transmission process for transmitting pseudo-order information for a product identical to or an alternative product to the product to the EC site or POS register via the API linkage based on the warranty application; or (C) A repair request notification process that notifies the terminal of the seller of the product using the API-linked EC site or POS register to send the same product as the product or a replacement product to the purchaser or to repair the product based on the warranty application. The extended warranty management system according to any one of (1) to (10) above, (12) The extended warranty management system described in (11) above, in which an application for issuance of a coupon code that allows the purchase of an identical product or an alternative product to the product free of charge or at partial cost includes the server transmitting coupon code information, including the product information, the purchase information, and the purchaser information, to the EC site or POS register via the API integration. (13) An extended warranty management system as described in any one of (1) to (12) above, wherein the server executes a calculation process to calculate the ratio of the warranty fee for the extended warranty purchased to the purchase price of the product based on the purchase price of the product and the warranty fee for the extended warranty purchased stored in the database. (14) An extended warranty management system as described in any one of (1) to (13) above, wherein the server executes a calculation process to calculate the participation rate of the extended warranty for each product based on the number of purchases of the product and the number of extended warranties purchased stored in the database. (15) The extended warranty management system according to any one of (1) to (14) above, wherein the server executes a calculation process to calculate a damage rate for each of the products based on the number of applications for extended warranties for each of the products stored in the database, the number of extended warranties fulfilled for each of the products, or a combination thereof. (16) The server, a calculation process for calculating the participation rate of the extended warranty for each of the products based on the number of purchases of the products and the number of the extended warranties purchased stored in the database; A calculation process for calculating a damage rate for each of the products based on the number of applications for extended warranties for each of the products stored in the database, the number of extended warranties fulfilled for each of the products, or a combination thereof; A change process for changing the warranty fee for each product based on the subscription rate, the loss rate, and the warranty fee for the purchased extended warranty. The extended warranty management system according to any one of (1) to (15) above, (17) A server in an extended warranty management system for managing extended warranties for natural failures or physical damage of products, a database capable of storing product information identifying the product, purchase information identifying the purchase of the product, purchaser information identifying a purchaser of the product, and warranty information identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information is connected; A means for writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; An API linking means capable of API linking with an EC site or a POS register that sells the product; an extended warranty management processing means based on the extended warranty purchased together with the product at the EC site or the POS register through the API linkage with the EC site or the POS register; Equipped with The extended warranty management processing means: A processing means for linking the purchaser information with the warranty information; A processing means for transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; a warranty application reception processing means for receiving a warranty application transmitted from a terminal of a purchaser of the product; A means for recording and processing the warranty claim history information in the database; and A processing means for transmitting the warranty application history information to a terminal of a purchaser of the product. Including, the server. (18) The server in the extended warranty management system for managing extended warranties for natural failures or physical damage of products A process of writing and reading, into a database connected to the server, product information for identifying the product, purchase information for identifying the purchase of the product, purchaser information for identifying the purchaser of the product, and warranty information for identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information; Extended warranty management processing based on the extended warranty purchased together with the product on an EC site or POS register through API integration with the EC site or POS register;

[0033] The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product Including, the program. Effect of the Invention

[0009] According to the present invention, it is possible to provide an extended warranty management system that enables a purchaser of a product to centrally manage extended warranties for a plurality of products. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram showing an example of the present extended warranty management system. [Diagram 2] Figure 2 shows an example of a display on an EC site that displays products and extended warranties through API integration with this extended warranty management system. [Diagram 3] Figure 3 shows an example of how a product and an extended warranty are displayed in a cart on an e-commerce site when the extended warranty management system is linked via API. [Figure 4] Figure 4 is an example of a graph that compiles the monthly extended warranty subscription rate, loss rate, and warranty fee obtained by this extended warranty management system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The present disclosure relates to an extended warranty management system for managing an extended warranty for a product's natural failure or physical damage, a server connected to a database capable of storing product information identifying the product, purchase information identifying a purchase action of the product, purchaser information identifying a purchaser of the product, and warranty information identifying details of an extended warranty linked to at least one selected from the group consisting of the product information, the purchase information, and the purchaser information, and capable of writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; The server has an API linking means capable of API linking with an EC site or a POS register that sells the product, and causing the server to execute an extended warranty management process based on the extended warranty purchased together with the product on the EC site or the POS register through the API linkage with the EC site or the POS register; The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product This applies to extended warranty management systems, including:

[0012] According to this system, the purchaser information of the product is linked to the warranty information, and the warranty information linked to the purchaser information is sent to the terminal of the purchaser of the product, so that the purchaser of the product on an EC site or the like (hereinafter, simply referred to as the purchaser) can check the extended warranty for one or more products on the purchaser's terminal, and can centrally manage the extended warranty for multiple products. For example, the purchaser can access the server of this system from the purchaser's terminal and centrally manage the warranty details of the extended warranty for multiple products, such as whether the purchased product has an extended warranty, whether it is within the extended warranty period, the extended warranty period, and the extended warranty fee.

[0013] In addition, purchasers can easily apply for an extended warranty at any time via the system from their own terminal, and can receive fulfillment of the warranty from e-commerce sites and other entities that are API-connected to the system.

[0014] This system also allows for API (Application Programming Interface) integration with EC sites or POS registers (hereinafter referred to as EC sites, etc.), allowing sellers of products on EC sites, etc. (hereinafter referred to as sales businesses) to easily introduce the extended warranty management system to EC sites, etc.

[0015] In addition, after introducing this system to an EC site, etc., a seller can easily provide extended warranties linked to products without having to manage and operate extended warranties. In addition, with this system, sellers can expect to increase sales by receiving a portion of the warranty fee for extended warranties, and to improve the satisfaction of after-sales service for product purchasers.

[0016] This system also allows a purchaser to easily subscribe to an extended warranty linked to a product. A purchaser can purchase an extended warranty by paying the extended warranty fee (warranty fee) in the same way as when purchasing a product on the same EC site, etc. A sales company can receive the product price (purchase price) and at least a portion of the warranty fee from a purchaser via an EC site, etc. An operating company of this system or a guarantee company for the extended warranty (hereinafter also referred to as the operating company, etc.) can receive the remaining warranty fee from the selling company.

[0017] That is, according to this system, a purchaser can centrally manage extended warranties for multiple products. Also, the purchaser can complete the procedure for joining the extended warranty on an EC site, etc., that is API-linked with this system, using the purchaser's terminal, and can receive the performance of the warranty from the EC site, etc., that is API-linked with this system, by submitting a warranty application to this system using the purchaser's terminal for a product that has naturally broken down or been damaged (hereinafter also referred to as broken down, etc.). In this way, according to this system, a purchaser can centrally manage extended warranties for multiple products using the purchaser's terminal, and further, the joining of the extended warranty, the application for the extended warranty, and the receipt of the performance of the extended warranty can be completed on this system and on the EC site, etc., that is API-linked with this system.

[0018] The EC sites with which the present system can be API-linked are not particularly limited, and API linkage is possible with various EC sites, preferably EC sites built with cloud services or cart systems of EC sites. The POS registers with which the present system can be API-linked are also not particularly limited, and API linkage is possible with various POS registers. Therefore, the present system can be easily incorporated into various EC sites or POS registers. Sales businesses can arbitrarily link the API provided by the present system to the EC site's cart system, payment service, security system, order management system, email distribution system, customer management system, POS register's core system, etc.

[0019] In this application, an EC site refers to a website that conducts e-commerce (electronic commerce), including online shopping sites (websites where you can shop), online auction sites, content distribution sites, online trading sites, etc., and preferably an online shopping site.

[0020] The EC site can be a mall-type site or a company's own EC site. A mall-type site is a shopping site to which many sellers belong, and examples thereof include Amazon (registered trademark), Rakuten (registered trademark), and Yahoo! Shopping (registered trademark). Examples of cart systems for EC sites include shopify (registered trademark), MakeShop (registered trademark), futureshop (registered trademark), EC CUBE (registered trademark), and ebisumart (registered trademark). Examples of POS registers include Smaregi (registered trademark). A company's own EC site is a shopping site operated by a single seller, and examples thereof include Uniqlo (registered trademark), Apple (registered trademark), and MUJI (registered trademark).

[0021] In this application, a POS register refers to a register equipped with a POS (Point of Sales) function. In addition to accounting, a POS register can also identify popular products, manage inventory, and link with an order entry system.

[0022] 1 is a schematic diagram showing an example of an extended warranty management system 10 according to the present disclosure. The extended warranty management system 10 includes a server 1 and a database 2.

[0023] The database 2 can store product information that identifies the purchased product, purchase information that identifies the act of purchasing the product, and purchaser information that identifies the purchaser of the product. The database 2 can also store warranty information that identifies the content of an extended warranty linked to at least one selected from the group consisting of the product information, the purchase information, and the purchaser information.

[0024] The server 1 is connected to a database 2, and is capable of writing and reading data such as product information, purchase information, purchaser information, and warranty information to the database 2. There are no particular limitations on the connection form of the database 2 connected to the server 1, and it may be built into the server 1, may be a storage unit of the server 1, may be built into another server connected to the server 1 by wire or wirelessly, or may be included in another server or a cloud server connected to a communication network such as the Internet.

[0025] The server 1 is connected to a communication network such as the Internet and includes a communication unit, a storage unit, and a processing unit capable of transmitting and receiving data to and from an EC site or a POS register 3 (hereinafter also referred to as the EC site 3) and a purchaser terminal 4 of the product. The purchaser terminal 4 is a terminal owned by the purchaser, and may be a mobile terminal or an information terminal such as a smartphone, tablet, or personal computer. The purchaser terminal 4 may be connected to the server 1 and the EC site 3 via a network. In this application, the applicant for the extended warranty may be the same as the purchaser of the product, or may be a person acting on behalf of the purchaser or a person to whom the right to receive the extended warranty has been transferred from the purchaser. Therefore, in this application, the purchaser is a concept that includes not only the purchaser himself / herself, but also an agent or a transferee of the right, and the purchaser terminal 4 is a concept that includes not only the purchaser's terminal, but also the terminal of the person acting on behalf of the purchaser or the terminal of the person to whom the right to receive the extended warranty has been transferred from the purchaser.

[0026] The storage unit stores programs such as driver programs, operating system programs, application programs, etc. The storage unit may also store product information, purchase information, purchaser information, and warranty information to be transmitted and received.

[0027] The processing unit has one or more processors and their peripheral circuits. The processing unit centrally controls the overall operation of the server, and is, for example, a CPU (Central Processing Unit). The processing unit can control the operation of the communication unit, the storage unit, and the database 2 so as to transmit and receive product information, purchase information, purchaser information, and warranty information, store (register) the product information, purchase information, purchaser information, and warranty information in the database, and perform various calculations based on the product information, purchase information, purchaser information, and warranty information stored in the database.

[0028] The processing unit executes various processes based on programs (driver programs, operating system programs, application programs, etc.) stored in the storage unit. The processing unit can also execute multiple programs (application programs, etc.) in parallel. The database may be a storage unit of a server.

[0029] The server 1 has an API linking means capable of API linking with the EC site etc. 3, and the seller can operate the extended warranty via API from the EC site, the purchaser from the purchaser terminal, and the operator of the system etc. from the server 1. Since the server 1 of the system and the EC site etc. 3 can API link product information, product purchase information, purchaser information, and / or warranty information, the seller does not need to link the product and the extended warranty.

[0030] The product information is information for identifying the purchased product, and preferably includes at least one selected from the group consisting of the product manufacturer, product name, model number, and product code.

[0031] The purchase information is information that identifies a purchase action, and preferably includes an ID of an EC site, a purchase ID of a product, or a combination thereof. The purchase ID of a product includes a purchase date of the product, a purchase price of the product, or a combination thereof. The purchase information may further include a URL of the EC site where the product was purchased.

[0032] The purchaser information is information for identifying a purchaser, and is preferably the following (A) to (H): (A) An ID given to the purchaser, (B) the purchaser’s email address, social media address, or any combination thereof; (C) the purchaser's telephone number; (D) The name of said purchaser; (E) the purchaser's date of birth; (F) the address of said purchaser; (G) the purchaser's insurance policy number, and (H) The purchaser's My Number The compound includes at least one selected from the group consisting of:

[0033] More preferably, the purchaser information includes (A) an ID assigned to the purchaser, (B) the purchaser's email address or (C) the purchaser's telephone number, (D) the purchaser's name, (E) the purchaser's date of birth, and (F) the purchaser's address.

[0034] The warranty information is information that specifies the contents of the extended warranty, and preferably includes a warranty type, which may include replacement of the product, repair of the product, or refund of at least a portion of the product price, a failure mode covered by the product's warranty, a warranty period, a warranty fee, a warranty number, or a combination thereof.

[0035] The failure modes covered by the warranty are failure modes covered by the extended warranty for products purchased on EC sites, etc., and can be natural failures or physical damage. Natural failures are failures that occur during proper use in an environment in accordance with the instruction manual or manufacturer's warranty regulations, that is, electrical or mechanical failures caused by the product itself, and require part replacement. Physical damage is not a symptom caused by the inside of the product itself, but a failure caused by unexpected and sudden external factors such as breakage, external pressure, and water damage, and also includes failures caused by natural disasters such as loss, theft, and earthquakes. The failure modes covered by the warranty can be determined arbitrarily by the seller for each product, and can be, for example, only natural failures, natural failures and physical damage are covered by the warranty, but failures caused by natural disasters such as loss, theft, and earthquakes are not covered by the warranty, or all natural failures and physical damage are covered.

[0036] The failure modes covered by the warranty may also be, for example, a product purchased from an e-commerce site or the like not turning on, having no sound, no video, distorted video, not working, etc.

[0037] The warranty type includes replacement of the product purchased on the EC site, repair of the product, or refund of at least a portion of the product price. The at least a portion of the product price can be between more than 0% and 100% of the product price, for example, a 50% refund or a 100% refund. The warranty type may be uniform for each product at the time of warranty application, or may be determined based on the failure mode.

[0038] The warranty period of the extended warranty is a period calculated from the day after the expiration date of the product's manufacturer's warranty, and can be measured in months or years, for example.

[0039] The method of API integration between the server 1 and the EC site etc. 3 is not particularly limited, but can be achieved by, for example, installing the program of this system and embedding script code in the system of the EC site etc. 3, storing authentication information such as the authentication code of the EC site etc. 3 in the server 1 or database 2 using the external system integration function of the EC site etc. 3, or incorporating the API of this system in the server of the EC site etc. 3 to achieve integration.

[0040] When this system is incorporated into an EC site or the like 3, various permissions are given to the system by the EC site or the like 3. The permissions may include the permission to obtain product information, the permission to obtain purchase information, the permission to obtain purchaser information, the permission to issue a coupon to enable the purchase of the same product or an alternative product free of charge, and the like.

[0041] Through API integration, the server 1 can acquire purchaser information received by the EC site 3, product information on the EC site 3, product purchase information received by the EC site 3, etc., and store them in the database 2. In the API integration, preferably, an SDK (Software Development Kit) is incorporated into the EC site 3. By incorporating the SDK, the sales business operator can adjust the display of the extended warranty button on the EC site 3.

[0042] Extended warranty operations preferably include creating an extended warranty plan, applying for (purchasing) an extended warranty, canceling an extended warranty, filing a warranty claim, accepting (accepting) a warranty claim, fulfilling the warranty, and changing the price of an extended warranty.

[0043] The creation of the extended warranty plan can be performed from the server 1. The extended warranty plan preferably includes the failure mode to be guaranteed, the warranty period, the warranty type, and the warranty fee. The warranty type includes product replacement, product repair, or at least a partial refund of the product price. In this application, product replacement means that the same product or a replacement product can be purchased free of charge or at a partial cost. Free of charge means that there is no additional financial burden on the purchaser.

[0044] The warranty plan for the extended warranty provided through this system can be customized as desired by the seller of the EC site, etc. The warranty plan may, for example, set a low warranty fee if the failure mode is a natural failure, and a high warranty fee if the failure mode is physical damage, as described below.

[0045] A purchaser can apply for (purchase) an extended warranty on the EC site, etc. 3 using the purchaser terminal 4. Using the network-connected purchaser terminal 4, an extended warranty linked to a product can be selected and purchased on the EC site, etc. 3. When the purchased product is cooled off, etc., the sales business can cancel the extended warranty on the EC site, etc. 3.

[0046] According to this system, a button for purchasing the product and a button for purchasing the extended warranty can be displayed on the same screen of the EC site 3 so that the extended warranty linked to the product can be easily applied for. The product and the warranty content of the extended warranty are preferably linked by linking the product code given to the product with the ID of the EC site, etc. When the extended warranty is purchased, the linked product code and ID of the EC site, etc. are further linked with warranty information, preferably a warranty number.

[0047] According to this system, an extended warranty button showing the warranty period and application amount can be displayed on an e-commerce site or the like that displays products. Figure 2 shows an example of a display on an e-commerce site or the like that displays a product image and the available extended warranties "1 year warranty - 1,000 yen," "2 year warranty - 2,000 yen," and "3 year warranty - 3,000 yen," with "2 year warranty - 2,000 yen" selected. In the same way as when purchasing a product, the extended warranty can be purchased along with the product by selecting the extended warranty button and clicking the "Add to cart" button or the "Buy now" button.

[0048] A purchaser can use a purchaser terminal 4 to purchase the extended warranty fee (warranty fee) in a cart on an EC site, etc. 3, in the same way as the product price. According to this system, payment of the extended warranty fee by a product purchaser can be completed within the EC site, etc. 3, in the same way as payment of the product price. Fig. 3 shows an example of a display in which one pair of headphones priced at 11,000 yen and one one-year extended warranty priced at 1,000 yen have been placed in a cart on an EC site, etc. 3.

[0049] A purchaser can select the type of extended warranty according to the product to be purchased from the purchaser terminal 4 in the shopping cart on the EC site 3. A purchaser can also select the number of extended warranties from 1 or 2 or more according to the number of products to be purchased from the purchaser terminal 4 in the shopping cart on the EC site 3.

[0050] Preferably, the server 1 acquires, via API integration, warranty information for the extended warranty that the purchaser purchased (joined) on the EC site etc. 3 via the purchaser terminal 4, together with product information, purchaser information, and purchase information, and stores it in the database 2.

[0051] The purchase of an extended warranty through the purchaser terminal 4 can be completed on the EC site, etc. 3. When purchasing an extended warranty on an EC site, etc. where a product is being purchased for the first time, or on an EC site, etc. where purchaser information has not been registered, purchaser information can be entered on the EC site, etc. 3.

[0052] The purchaser information is the purchaser's contact information, such as the purchaser's name, email address, telephone number, address, etc. The address can be the country, address, and name, or any address where the purchaser can be contacted, such as the address where the purchaser resides, the billing address for invoices, etc. The contact information is preferably the purchaser's email address or mobile phone number. The purchaser information can be stored in an EC site, etc.

[0053] The extended warranty fee can be paid by any desired method, such as credit card, electronic money, or cash.

[0054] For example, after inputting purchaser information and credit card information or electronic money information, the purchaser can click a button such as "Pay now" on the EC site 3 to complete the purchase of the extended warranty for the product.

[0055] When the purchase of the product is completed, a confirmation notification email of the product purchase may be sent from the EC site etc. 3 to the email address entered as the purchaser information. The confirmation notification email may display the purchase number along with the purchaser information, product delivery address information, purchased product, product price, purchased extended warranty, extended warranty fee, delivery fee, and tax.

[0056] When the purchase of the extended warranty is completed together with the purchase of the product, an email notifying the purchaser of the extended warranty may be sent to the email address entered as the purchaser information. The email notifying the purchaser of the extended warranty may include product information, purchase information, purchaser information, warranty information, or a combination thereof, and may preferably display the warranty number, warranty fee, product name, product photo or image, warranty type, warranty period, detailed warranty information, a link (URL) to display them, or a combination thereof.

[0057] When multiple items are purchased, the purchaser can decide from the purchaser terminal 4 on the EC site 3 whether to apply extended warranties to some or all of the items. For example, when three of the same item are purchased, the number of extended warranties can be set to three, and extended warranties can be applied to all three items. Also, when three of the same item are purchased, the number of extended warranties can be set to two, and extended warranties can be applied to two of the three items. If the serial number of each item is linked to the extended warranty, it is possible to link and manage the extended warranty to each item even when multiple of the same item are purchased. If the purchased item breaks down, the purchaser can apply for a warranty from the purchaser terminal 4 based on the extended warranty that was purchased.

[0058] The server 1 executes an extended warranty management process based on an extended warranty purchased together with a product on the EC site 3 by being linked with the EC site 3 through an API.

[0059] The extended warranty management process is A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product Includes.

[0060] The process of linking the purchaser information with the warranty information includes having the server 1 execute a registration process in which the purchaser information and the warranty information are linked in the database 2 based on information about the extended warranty purchased along with the product transmitted from the purchaser terminal 4.

[0061] The process of transmitting the warranty information linked to the purchaser information to the purchaser's terminal can be when the server 1 executes a registration process linking the purchaser information and the warranty information in the database 2, or at a predetermined timing after the execution of the registration process, or when the purchaser terminal 4 accesses the server 1 requesting linking information linking the purchaser information and the warranty information, and can display or notify the warranty information linked to the purchaser information on the purchaser terminal 4. Since multiple pieces of warranty information are attached to the purchaser information, a purchaser of a product can centrally manage extended warranties for multiple products.

[0062] The server 1 can display a list of one or more pieces of warranty information linked to the purchaser information on the purchaser's terminal, or can notify the purchaser of a file in which one or more pieces of warranty information linked to the purchaser information are compiled in a list.

[0063] The warranty application reception process includes having the server 1 receive a warranty application sent from the purchaser terminal 4 and execute a process of registering the warranty application in the database 2. When the server 1 registers in the database 2 that a warranty application has been made, it can notify the purchaser terminal 4 that the warranty application has been approved. Since the server 1 can receive warranty applications sent from the purchaser terminal 4 at any time, it can quickly perform the reception process of the warranty application.

[0064] If the product has a natural failure or is damaged, the purchaser can make a warranty claim based on the purchased extended warranty through the purchaser terminal 4. The purchaser can make a warranty claim by transmitting warranty contract information from the purchaser terminal 4 to the server 1.

[0065] A warranty application can be made from a warranty application screen provided by the server 1 via the purchaser terminal 4, such as a warranty application form or a chatbot. For example, the purchaser can transition to the warranty application screen by clicking a warranty application button displayed in the notification email of the extended warranty subscription sent from the server 1 to the purchaser terminal 4 when the extended warranty is subscribed, or by clicking the warranty number displayed in the notification email.

[0066] A warranty claim can be made using warranty contract information including the warranty number, the purchaser information, or a combination of these included in the warranty claim. A warranty claim can be made by inputting the warranty contract information on the warranty claim screen from the purchaser terminal 4 and sending it to the server 1.

[0067] The warranty claim reception process preferably includes having the server 1 determine whether the warranty number or purchaser information included in the warranty claim matches the warranty number or purchaser information stored in the database. If a match between the warranty number or purchaser information is confirmed, the server 1 can accept the warranty claim and notify the purchaser terminal 4 that the warranty claim has been accepted.

[0068] If the warranty number or purchaser information included in the warranty application does not match the warranty number or purchaser information stored in the database, the server 1 can notify the purchaser terminal 4 that the purchased extended warranty (warranty contract) cannot be found and provide a contact point. The contact point can be an email address, a phone number, or a combination of both.

[0069] The purchaser information preferably includes the purchaser's email address or phone number.

[0070] The warranty application receiving process preferably includes, upon receiving a warranty application transmitted from the purchaser terminal 4, having the server 1 display, on the purchaser terminal 4, one or more pieces of product information linked to the warranty contract information stored in the database 2. When the product information displayed on the purchaser terminal 4 is selected, the purchaser can input or select the date of the malfunction or the like (hereinafter also referred to as the malfunction date), details of the malfunction or the like such as whether it is a natural malfunction or physical damage, etc.

[0071] The warranty application receiving process preferably includes, upon receiving a warranty application sent from the purchaser terminal 4, having the server 1 send a notification to the purchaser terminal 4 to confirm whether there have been any changes to the purchaser information, such as the email address registered in the database 2. A response to the confirmation notification can be sent from the purchaser terminal 4 to the server 1. For example, when a warranty application is made using a warranty number, the server 1 can send a notification to the purchaser terminal 4 by email or chatbot to confirm whether there have been any changes to the purchaser information, and the purchaser can respond as to whether there have been any changes and the changed purchaser information by replying to the email sent or by entering the information into a website or chatbot linked to the email.

[0072] If the server 1 receives a response that there are no changes to the purchaser information, it can send an email notifying that the warranty application has been accepted to the email address registered in the database 2. If the server 1 receives a response notifying that there are changes to the purchaser information and the revised purchaser information, the revised purchaser information is registered in the database 2, and the server 1 can send an email notifying that the warranty application has been accepted to the email address included in the revised purchaser information.

[0073] The warranty application receiving process preferably includes having the server 1 execute a process of determining whether or not to accept the warranty application transmitted from the purchaser terminal 4 based on the contents of the warranty application and the extended warranty data stored in the database 2. If the contents of the transmitted warranty application match the extended warranty data stored in the database 2, the server 1 can accept the warranty application, and if they do not match, can reject the warranty application. When the server 1 accepts the warranty application, it can notify the purchaser terminal 4 that the warranty application has been accepted, and when the server 1 rejects the warranty application, it can notify the purchaser terminal 4 that the warranty application has been rejected. When rejecting the warranty application, it can notify the purchaser terminal 4 of an inquiry contact such as an email address, a telephone number, or a combination thereof (same below).

[0074] The warranty claim reception process preferably includes having the server 1 execute a process of determining whether the warranty claim date is within the warranty period of the warranty information stored in the database 2. When the server 1 determines that the warranty claim date is within the warranty period, it can accept the warranty claim and notify the purchaser terminal 4 that the warranty claim has been accepted. When the server 1 determines that the warranty claim date is outside the warranty period, it can reject the warranty claim and notify the purchaser terminal 4 that the warranty claim has been rejected because it is outside the warranty period.

[0075] The warranty claim reception process preferably includes having the server 1 execute a process of determining whether or not the failure date included in the warranty claim is within the warranty period of the warranty information stored in the database 2. When the server 1 determines that the failure date is within the warranty period, it can accept the warranty claim and notify the purchaser terminal 4 that the warranty claim has been accepted. When the server 1 determines that the failure date is outside the warranty period, it can reject the warranty claim and notify the purchaser terminal 4 that the warranty claim has been rejected because it is outside the warranty period.

[0076] The warranty application receiving process preferably includes having the server 1 execute a process of determining whether the details of the malfunction, etc. included in the warranty application are a malfunction mode covered by the extended warranty stored in the database 2. When the server 1 determines that the details of the malfunction, etc. are a malfunction mode covered by the warranty, it can accept the warranty application and notify the purchaser terminal 4 that the warranty application has been accepted. When the server 1 determines that the malfunction mode is not a malfunction mode covered by the warranty, it can reject the warranty application and notify the purchaser terminal 4 that the warranty application has been rejected because it is not covered by the warranty.

[0077] The warranty application receiving process preferably includes a slip information sending process for sending to the purchaser terminal 4 a reception number or information code linked to slip information for returning the broken or defective product to the sales company. By inputting the reception number or reading the information code into a terminal such as a multi-copy machine at a convenience store or the like, it is possible to output a waybill (slip) on which slip information including purchaser information and delivery address information is printed. The purchaser can affix the outputted waybill (slip) to the broken or defective product or its packaging material, etc., and carry out the procedure for returning the broken or defective product to the sales company.

[0078] The warranty application receiving process preferably includes causing the server 1 to transmit to the purchaser terminal 4 a link or information code for returning the defective product. By clicking on the link or reading the information code, the purchaser can transition to the delivery company's website. On the delivery company's website, the procedure for returning the defective product can be carried out.

[0079] The information code is preferably a one-dimensional code, a two-dimensional code, or a combination thereof. The one-dimensional code is preferably a barcode such as CODE39, CODE128, JAN, EAN, UPC, NW-7, ITF, or a combination thereof. The two-dimensional code is preferably a matrix code or a stack code. The matrix code is preferably a QR code, a micro QR code, a SP code, a VeriCode, a MaxiCode, a CP code, a Data Matrix, a Data Matrix ECC200, a Code1, an AztecCode, an Intacta Code, a Card e, or a Chameleon Code. The stack code is preferably a PDF417, a micro PDF417, a Code49, a Code16K, a Codablock, a SuperCode, an Ultra Code, an RSS Composite, or an AztecMesa.

[0080] The extended warranty management process includes a process of recording the warranty application history information in the database 2. The extended warranty management process also includes a process of transmitting the warranty application history information to the terminal of the purchaser of the product. This allows the purchaser to check the warranty application history information at any time from the purchaser terminal 4. The warranty application history information may be recorded in the database 2 when the status of the warranty application is updated. The warranty application history information may be displayed or notified on the purchaser terminal 4 when it is recorded in the database 2, or at a predetermined timing after it is recorded in the database 2, or when the purchaser terminal 4 accesses the server 1 to request the warranty application history information.

[0081] Preferably, the warranty application history information includes warranty application acceptance information, product repair information, product post-repair shipping information, warranty completion information, or a combination thereof. Warranty application acceptance information includes, for example, information indicating that the warranty application has not yet been accepted (under review) or has been accepted. Product repair information includes, for example, information indicating that the product is before repair, under repair, or has been repaired. Product post-repair shipping information includes, for example, information indicating that the repaired product or a replacement product is being prepared for shipping, has been shipped, is being shipped, or has arrived. Warranty completion information includes, for example, information indicating that the warranty application has not yet been completed or has been completed.

[0082] When the server 1 executes the warranty claim reception process, preferably when it executes the warranty claim reception process and the warranty claim acceptance process, it can execute (A) a coupon code issuance application process, a coupon code reception process, and a coupon code transmission process, (B) a pseudo order information transmission process, or (C) a repair request notification process, which will be described below.

[0083] (Coupon code issuance application process, coupon code reception process, and coupon code transmission process) Based on the warranty application, the server 1 can execute a coupon code issuance application process to make an application to the EC site 3 via API cooperation for the issuance of a coupon code that allows the purchase of the same product as the broken product or a replacement product free of charge or at a partial cost (also called an exchange), the repair of the broken product free of charge or at a partial cost, or a refund of at least a portion of the purchase price of the broken product. If the EC site 3 is an ASP cart system with an API that allows coupon codes to be issued from outside, the server 1 can execute the coupon code issuance application process. A replacement product is a similar product that can be purchased with a coupon code for the same amount or less when the same product is not sold on the EC site, and the purchaser can select a replacement product from one or more types of products displayed on the purchaser terminal 4.

[0084] The coupon code is a coupon for purchasing the same product as the broken product or a replacement product free of charge or at a partial cost, a coupon for repairing the broken product free of charge or at a partial cost, or a coupon for refunding at least a portion of the purchase price of the broken product. Repairs may include returning the broken product for repair, or sending a repair kit to the applicant. Refunds may be made by providing a coupon code, electronic money, cash, or the like equivalent to 50% or 100% of the product price, for example.

[0085] The coupon code issuance application process includes transmitting coupon conditions including purchasable products, maximum usable price, and usable period, or a combination thereof, from the server 1 to the EC site 3 via API integration. The EC site 3 creates a coupon code based on the coupon conditions included in the coupon code issuance application received via API integration, and transmits the created coupon code to the server 1. The server 1 transmits the transmitted coupon code to the purchaser terminal 4. The process of sending the coupon to the purchaser terminal 4 from the coupon code issuance application is automatically performed via API integration.

[0086] The server 1 executes a coupon code receiving process for receiving a coupon code created on the EC site 3 based on a coupon code issuance application through API cooperation.

[0087] The server 1 executes a coupon code transmission process for transmitting the received coupon code to the purchaser terminal 4.

[0088] As described above, in this system, the server 1 causes the EC site 3 to issue a coupon code that can be used on the EC site 3 via an API, and transmits the coupon code to the purchaser terminal 4. The coupon code transmitted to the purchaser terminal 4 preferably includes a link to a cart screen of the EC site or the like. Clicking on the coupon code including the link above transitions to the cart screen of the EC site or the like, making it easier to carry out procedures for exchanging or repairing the product, or for refunding the product price.

[0089] The purchaser can use the coupon code sent to the purchaser terminal 4 to purchase the same product as the broken product or a replacement product free of charge or at a partial cost on the EC site where the product was previously purchased, or to request the broken product to be repaired free of charge or at a partial cost, or to receive at least a partial refund of the purchase price of the broken product.

[0090] If the warranty type is replacement, the purchaser can purchase the same product or a replacement product again from the same EC site, etc., free of charge or at a partial cost. In this way, this system allows the purchaser terminal 4 to access the same EC site again, which can contribute to the creation of repeat customers. The operator of this system, etc., can cover all or part of the cost of the same product or a replacement product.

[0091] An embodiment in which the warranty type is replacement will be described. When the server 1 executes the warranty application receiving process, it can transmit to the purchaser terminal 4 that the warranty application has been accepted, and display a button for arranging replacement on the purchaser terminal 4. The button for arranging replacement can have a link to transition to a screen where the shipping address of the replacement product can be input.

[0092] When the button for arranging an exchange is pressed, a screen for inputting or confirming the delivery address of the exchange product is displayed on the purchaser terminal 4. The input or confirmation screen can be the same as the screen for inputting or confirming the delivery address when purchasing a normal product, except that the product price is displayed as 0 yen or a reduced amount. By inputting or confirming the delivery address and clicking the button to proceed to payment, delivery arrangements for the exchange product can be completed.

[0093] An embodiment in which the warranty type is repair will be described. When the server 1 executes the warranty application receiving process, it transmits to the purchaser terminal 4 a message that the warranty application has been accepted, and can display a link or information code for returning the broken or defective product for repair on the purchaser terminal 4. By clicking the link or reading the information code, it is possible to transition to the delivery company's website. On the delivery company's website, it is possible to carry out the procedure for returning the broken or defective product to the operator of this system or a repair company commissioned by the operator.

[0094] If the warranty type is repair, the operating company of this system or a repairer commissioned by the operating company inspects the broken product, and if it is determined that the break is covered by the warranty, the server 1 may execute approval processing for the warranty application. The determination of whether the break is covered by the warranty can be made by determining whether the contents of the break are covered by the warranty and / or whether it is a break as claimed.

[0095] The warranty fee for the extended warranty paid by the purchaser of the product may be electronically deposited in the account of the seller via an EC site, etc. A portion of the warranty fee for the extended warranty electronically deposited in the account of the seller may be electronically deposited in the account of the operator of this system and / or the account of the guarantee company.

[0096] The server 1 can transmit an invoice for at least a portion of the warranty fee to a seller terminal 5 of an EC site or the like, based on the warranty fee for the extended warranty stored in the database 2. Based on the invoice transmitted to the seller terminal 5, the seller can electronically deposit the claimed amount into the account of the operator of this system and / or the account of the guarantee company.

[0097] Preferably, an application for issuance of a coupon code that allows the purchase of the same product or an alternative product free of charge or at partial cost includes the server 1 transmitting coupon code information, including product information, purchase information, and purchaser information, to an EC site etc. 3 via API integration.

[0098] (Pseudo order information transmission process) Based on the warranty application, the server 1 can execute a pseudo order information sending process for sending pseudo order information for a product identical to the broken or defective product or a replacement product to the EC site etc. 3 via API integration. In the case where the EC site etc. 3 is an ASP cart system having an order information creation API, the pseudo order information sending process includes the server 1 acting on behalf of the applicant for the extended warranty to the EC site etc. 3 via API integration to purchase the same product as the broken or defective product or a replacement product.

[0099] (Repair request notification processing) Based on a warranty application, the server 1 can execute a repair request notification process to notify the terminal 5 of a sales business using an API-connected EC site etc. 3 to send the purchaser an identical product to the defective product or a replacement product, or to repair the defective product.

[0100] The server 1 preferably performs a registration process of the fulfillment information of the extended warranty in the database 2. The fulfillment information may include a response status indicating whether the warranty is being handled before or after the warranty is handled, a method of handling repair, replacement, or refund, and a cost incurred in fulfilling the warranty. The fulfillment information may also include status information of the coupon code that has been issued or is not being issued, status information of the pseudo order information transmission before or after the processing of the pseudo order information transmission, or status information of the repair request notification before or after the processing of the repair request notification. For example, a coupon code issue button with a display such as "issue" may be displayed in an active state on a monitor that the server 1 may have before the coupon code is issued. When the operator of this system clicks the coupon code issue button, the server 1 executes a coupon code issue application process, and a coupon code for, for example, 12,000 yen is generated via the API and transmitted to the purchaser terminal 4.

[0101] The server 1 can continuously obtain data on product purchases and extended warranty subscriptions made on the EC site or the like 3 via API integration, and store the data in the database 2. Based on the data, the server 1 can grasp at any time the ratio of warranty fees to product sales, the subscription rate of extended warranties for each product, the damage rate for each product, etc., and can review the warranty fees, for example, amend the warranty fees at any time so as to maximize the warranty fees for extended warranties relative to product sales.

[0102] Preferably, the server 1 tallies the ratio of the warranty fee for the extended warranty to the purchase price of the product, based on the purchase price of the product and the warranty fee for the extended warranty stored in the database 2. According to this system, when a product is purchased on an EC site or the like, it is possible to know at any time whether an extended warranty has been purchased at the same time, and also to know at any time the ratio of the warranty fee to the sales of the product.

[0103] Preferably, the server 1 calculates the subscription rate of the extended warranty for each product based on the number of purchased products and the number of purchased extended warranties stored in the database 2. According to this system, it is possible to grasp at any time the number of products purchased on an EC site or the like and the number of purchased extended warranties, and it is possible to grasp at any time the subscription rate of the extended warranty for each product.

[0104] Preferably, the server 1 calculates the loss rate for each product based on the number of applications for extended warranties for each product, the number of extended warranties fulfilled for each product, or a combination thereof stored in the database 2. According to this system, it is possible to grasp at any time the number of applications for extended warranties for each product purchased on an EC site or the like, the number of extended warranties fulfilled for each product, or a combination thereof, and to grasp at any time the loss rate for each product.

[0105] Preferably, the server 1 changes the warranty fee for each product based on the participation rate of the extended warranty for each product, the loss rate for each product, and the warranty fee for the purchased extended warranty stored in the database 2. According to this system, the participation rate of the extended warranty for each product purchased on an EC site or the like, the loss rate for each product, and the warranty fee for the purchased extended warranty can be grasped at any time, so that the warranty fee can be changed at any timing, for example, by lowering the warranty fee when the participation rate is low, and by raising the warranty fee when the loss rate is high. The change in the warranty fee based on the increase or decrease in the participation rate and the loss rate can be made by multiplying the increase or decrease in the participation rate and the increase or decrease in the loss rate by a predetermined coefficient, respectively.

[0106] Figure 4 shows an example of a graph that compiles the monthly extended warranty subscription rate, loss rate, and warranty fee for a product with a purchase price of 6,980 yen obtained by this extended warranty management system. The warranty fee is adjusted so as to maximize the warranty fee based on the extended warranty subscription rate and loss rate.

[0107] The present disclosure also provides a server in an extended warranty management system for managing an extended warranty for a natural failure or physical damage of a product, a database capable of storing product information identifying the product, purchase information identifying the purchase of the product, purchaser information identifying a purchaser of the product, and warranty information identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information is connected; A means for writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; An API linking means capable of API linking with an EC site or a POS register that sells the product; an extended warranty management processing means based on the extended warranty purchased together with the product at the EC site or the POS register through the API linkage with the EC site or the POS register; Equipped with The extended warranty management processing means: A processing means for linking the purchaser information with the warranty information; A processing means for transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; a warranty application reception processing means for receiving a warranty application transmitted from a terminal of a purchaser of the product; A means for recording and processing the warranty claim history information in the database; and A processing means for transmitting the warranty application history information to a terminal of a purchaser of the product. This applies to servers, including:

[0108] The present disclosure also provides a server in an extended warranty management system for managing extended warranties for natural failures or physical damage of products, A process of writing and reading, into a database connected to the server, product information for identifying the product, purchase information for identifying the purchase of the product, purchaser information for identifying the purchaser of the product, and warranty information for identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information; Extended warranty management processing based on the extended warranty purchased together with the product on an EC site or POS register through API integration with the EC site or POS register;

[0033] The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product The program covers: [Explanation of symbols]

[0109] 10 Extended warranty management system 1 Server 2 Database 3. E-commerce site or POS register 4. Purchaser terminal 5. Sales company terminal

Claims

1. An extended warranty management system for managing an extended warranty for a product's natural failure or physical damage, a server connected to a database capable of storing product information identifying the product, purchase information identifying a purchase action of the product, purchaser information identifying a purchaser of the product, and warranty information identifying details of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information, and capable of writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; The server has an API linking means capable of API linking with an EC site or a POS register that sells the product, and causing the server to execute an extended warranty management process based on the extended warranty purchased together with the product at the EC site or the POS register through the API linkage with the EC site or the POS register; The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product Extended warranty management system, including:

2. The extended warranty management system of claim 1 , wherein the history information includes information on acceptance of the warranty application, information on repair of the product, information on shipping of the product after repair, warranty completion information, or a combination thereof.

3. The extended warranty management system of claim 1, wherein the warranty application receiving process includes a slip information sending process for sending a reception number or information code linked to slip information for returning a product that has naturally failed or been damaged to a purchaser's terminal.

4. The purchaser information includes the following (A) to (H): (A) an ID given to the purchaser; (B) the purchaser's email address, SNS address, or a combination thereof; (C) the purchaser's telephone number; (D) the name of the purchaser; (E) the purchaser's date of birth; (F) the address of the purchaser; (G) the purchaser's insurance policy number; and (H) The purchaser’s My Number The extended warranty management system according to claim 1 , further comprising at least one selected from the group consisting of:

5. The extended warranty management system according to claim 1 , wherein the product information includes at least one selected from the group consisting of a manufacturer, a product name, a model number, and a product code of the product.

6. The extended warranty management system according to claim 1 , wherein the purchase information includes an ID of the EC site or POS register, and a purchase ID of the product including a purchase date of the product and a purchase price of the product.

7. 2. The extended warranty management system of claim 1, wherein the warranty information includes a warranty type including replacement of the product, repair of the product, or refund of at least a portion of the purchase price of the product, a failure mode covered by the warranty of the product, a warranty period, a warranty fee, a warranty number, or a combination thereof.

8. 2. The extended warranty management system of claim 1, wherein the warranty application receiving process includes causing the server to determine whether the purchaser information included in the warranty application matches the purchaser information stored in the database.

9. 8. The extended warranty management system of claim 7, wherein the warranty application receiving process includes causing the server to determine whether the warranty number included in the warranty application matches the warranty number stored in the database.

10. The extended warranty management system according to claim 4 , wherein the purchaser information includes an email address or a telephone number of the purchaser.

11. To the server (A) a coupon code issuance application process that, based on the warranty application, applies to the EC site or POS register via the API linkage for the issuance of a coupon code that allows the purchase of an identical product or an alternative product to the product free of charge or at a partial cost, the product to be repaired free of charge or at a partial cost, or at least a portion of the purchase price of the product to be refunded; A coupon code receiving process for receiving a coupon code created on the EC site or the POS register based on the issuance application through the API linkage; and A coupon code transmission process for transmitting the received coupon code to the purchaser's terminal; (B) a pseudo-order information transmission process for transmitting pseudo-order information for the same product or an alternative product to the EC site or POS register through the API linkage based on the warranty application; or (C) A repair request notification process that notifies the terminal of the seller of the product using the EC site or POS register linked to the API to send the same product as the product or a replacement product to the purchaser or to repair the product based on the warranty application. The extended warranty management system according to claim 1 , wherein the extended warranty management system executes the following steps.

12. The extended warranty management system of claim 11, wherein an application for issuance of a coupon code that allows the purchase of an identical product or an alternative product to the product free of charge or at partial cost includes the server transmitting coupon code information, including the product information, the purchase information, and the purchaser information, to the EC site or POS register via the API connection.

13. The extended warranty management system according to any one of claims 1 to 12, wherein the server executes an aggregation process to aggregate the ratio of the warranty fee for the extended warranty purchased to the purchase price of the product based on the purchase price of the product and the warranty fee for the extended warranty purchased stored in the database.

14. The extended warranty management system according to any one of claims 1 to 12, wherein the server executes a calculation process to calculate the participation rate of the extended warranty for each of the products based on the number of purchases of the products stored in the database and the number of the extended warranties purchased.

15. The extended warranty management system according to any one of claims 1 to 12, wherein the server executes a calculation process to calculate a damage rate for each of the products based on the number of applications for extended warranties for each of the products stored in the database, the number of extended warranties fulfilled for each of the products, or a combination thereof.

16. The server, a calculation process for calculating the participation rate of the extended warranty for each of the products based on the number of purchases of the products and the number of the extended warranties purchased stored in the database; A calculation process for calculating a damage rate for each of the products based on the number of applications for extended warranties for each of the products stored in the database, the number of extended warranties fulfilled for each of the products, or a combination thereof; A change process for changing the warranty fee for each product based on the subscription rate, the loss rate, and the warranty fee for the purchased extended warranty. The extended warranty management system according to any one of claims 1 to 12, further comprising:

17. A server in an extended warranty management system for managing extended warranties for natural failures or physical damage of products, a database capable of storing product information identifying the product, purchase information identifying the purchase of the product, purchaser information identifying a purchaser of the product, and warranty information identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information is connected; A means for writing and reading the product information, the purchase information, the purchaser information, and the warranty information to and from the database; An API linking means capable of API linking with an EC site or a POS register that sells the product; an extended warranty management processing means based on the extended warranty purchased together with the product at the EC site or the POS register through the API linkage with the EC site or the POS register; Equipped with The extended warranty management processing means: A processing means for linking the purchaser information with the warranty information; A processing means for transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; a warranty application reception processing means for receiving a warranty application transmitted from a terminal of a purchaser of the product; A means for recording and processing the warranty claim history information in the database; and A processing means for transmitting the warranty application history information to a terminal of a purchaser of the product. Including, the server.

18. A server in an extended warranty management system for managing extended warranties for natural failures or physical damage of products, A process of writing and reading, into a database connected to the server, product information for identifying the product, purchase information for identifying the purchase of the product, purchaser information for identifying the purchaser of the product, and warranty information for identifying the content of an extended warranty associated with at least one selected from the group consisting of the product information, the purchase information, and the purchaser information; Extended warranty management processing based on the extended warranty purchased together with the product at an EC site or a POS register through API linkage with the EC site or a POS register; Includes having the The extended warranty management process includes: A process of linking the purchaser information with the warranty information; A process of transmitting the warranty information linked to the purchaser information to a terminal of the purchaser of the product; A warranty application receiving process for receiving a warranty application transmitted from a terminal of a purchaser of the product; Recording the warranty claim history information in the database; and A process for transmitting the warranty claim history information to a terminal of a purchaser of the product Including, the program.

Images