JP4859911B2 - Product information providing server and product information providing program - Google Patents

Description

  The present invention relates to a product information providing server and a product information providing program, and more particularly to a product information providing server and a product information providing program that provide failure information related to a product to a user who purchased the product.

  For example, a manufacturer who manufactures a product (hereinafter referred to as a manufacturer) sells the manufactured product as a product to a purchaser (hereinafter referred to as a user). If a failure such as a defect is found in the sold product, the manufacturer needs to collect the product in which the failure is found from the user and resolve the failure by measures such as parts replacement.

  Therefore, when a failure is found in the sold product, the manufacturer notifies the user of the failure using mass media such as newspapers and televisions, and calls the user to collect the product in which the failure is found. The user confirms the content of the failure notified from the manufacturer, and if the content of the failure is related to a product owned by the user, the user has requested the manufacturer to solve the failure.

  The content of the failure to be notified to the user varies from a serious failure to a minor failure. However, when notifying the user of the content of the failure by using a mass media such as a newspaper or a television, the manufacturer has to pay for the advertisement fee regardless of the degree of the failure. In other words, there is a problem that there is an unbalanced cost for the contents of the failure. Furthermore, when notifying the user of the failure content using mass media, there is a problem that the certainty of information transmission is low.

  On the other hand, if the user cannot confirm the details of the failure notified from the manufacturer, he / she continues to have a product with a failure such as a defect, which may cause a secondary disaster. In addition, even if the user can confirm the failure content notified by the manufacturer, the user must confirm the detailed information such as the model name in order to determine whether the failure content is related to the product he / she owns. I had to.

  In addition, when a product manufactured in a specific period or at a specific factory is faulty for a certain product, the purchaser of the corresponding product checks whether or not the product he / she purchased is subject to the fault. Needed to check the purchase date or the serial number.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a product information providing server and a product information providing program capable of easily and reliably providing failure information related to a product to a user who has purchased the product.

  In order to solve the above problems, an embodiment of the present invention is directed to a manufacturer server managed by a manufacturer that manufactures a product, a store terminal managed by an organization that sells the product, and a purchase managed by a user who purchased the product A product information providing server that is connected to the purchaser terminal and provides failure information related to the product in response to an inquiry about the purchased product from the purchaser via the purchaser terminal, and is transmitted from the manufacturer server , A manufacturer code for identifying the manufacturer, a product code for identifying the product on the manufacturer side, and recall information registration means for registering fault information relating to the product in the recall information storage means, and purchasing the product input from the store terminal Product purchase history information storage means for storing the user information, the product code for identifying the product on the store side, and the purchase date in the product purchase history information storage means Conversion means for converting a product code for identifying a product on the store side with reference to the code conversion table into a product code for identifying the product on the manufacturer side, and a user who has received the inquiry from the purchaser terminal. Based on the product code for acquiring information and acquiring the product code for identifying the product on the store side stored in the product purchase history information storage unit based on the user information and identifying the product on the acquired store side Recall information acquisition means for converting to a product code for identifying a product on the maker side stored in the code conversion table and referring to the recall information storage means to acquire failure information related to the product, and for the acquired product Recall information notifying means for notifying trouble information to the purchaser terminal.

  As described above, according to an embodiment of the present invention, a manufacturer can improve the certainty of information transmission. In addition, the user can easily and surely obtain product information regarding the purchased product without being aware of the purchase history.

  Next, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, an example of notifying the user of recall information as an example of product information will be described, but any information related to products may be used.

  FIG. 1 shows a configuration diagram of an embodiment of a system including a product information providing server of the present invention. In the system of FIG. 1, one or more user terminals 10, one or more shop terminals 11, a product information providing server 12, and one or more manufacturer servers 13 are connected via a network 14 such as the Internet. Has been.

  The user terminal 10 is operated by a user who has purchased a product, and has a function for communicating with the product information providing server 12 via the network 14. The store terminal 11 is operated by a store clerk, such as a store that sells products or a credit participating store, and has a function for communicating with the product information providing server 12 via the network 14.

  For example, when the network 14 is the Internet, the user terminal 10 and the store terminal 11 are terminals that can be connected to the Internet and have a function of browsing a Web page stored in the product information providing server 12.

  The manufacturer server 13 is managed by a manufacturer that manufactures products such as electricity and furniture, and has recall information (failure information) of the manufactured products. The manufacturer server 13 stores and manages the recall information in a recall information database (hereinafter referred to as a recall information DB).

  The manufacturer server 13 has a function for communicating with the product information providing server 12 via the network 14. The manufacturer server 13 includes a search function for searching the recall information from the recall information DB as necessary.

  The merchandise information providing server 12 is managed by a third party such as a credit sales company or a dealer. The merchandise information providing server 12 is supplied with various information necessary for realizing the merchandise information providing method of the present invention from the user terminal 10, the shop terminal 11, and the manufacturer server 13.

  The merchandise information providing server 12 has a function of managing user merchandise purchase history information and acquiring recall information corresponding to a predetermined merchandise from the manufacturer server 13. The product information providing server 12 has a function of transmitting the acquired recall information to the user terminal 10. For example, when the network 14 is the Internet, the product information providing server 12 has a function of transmitting a Web page to the user terminal 10 and the store terminal 11.

  The merchandise information providing server 12 is configured, for example, as shown in FIG. FIG. 2 shows a configuration diagram of an embodiment of the product information providing server. The product information providing server 12 in FIG. 2 includes an input device 21, a display device 22, a drive device 23, a recording medium 24, an auxiliary storage device 25, and a memory device 26, which are mutually connected by a bus B. , An arithmetic processing unit 27, an interface unit 28, and a database (hereinafter referred to as DB) 29.

  The input device 21 includes a keyboard and a mouse that are operated by a user of the product information providing server 12 and is used to input various operation signals to the product information providing server 12. The display device 22 displays various windows and data necessary for operating the product information providing server 12. The interface device 28 is an interface for connecting the merchandise information providing server 12 to the network 14, and includes, for example, a modem (MODEM), a router (Router), and the like.

  The DB 29 stores various information necessary for realizing the product information providing method of the present invention, such as a user information DB, product number DB, product purchase history information DB, code conversion table, recall information DB, and the like. Details of the user information DB, product number DB, product purchase history information DB, code conversion table, and recall information DB will be described later.

  The product information providing program used by the product information providing server 12 is provided by a recording medium 24 such as a CD-ROM. The recording medium 24 is a CD-ROM, a recording medium for optically, electrically or magnetically recording information such as a flexible disk and a magneto-optical disk (MO), a ROM, a flash memory and the like. Various types of recording media such as a semiconductor memory for electrical recording can be used.

  The recording medium 24 on which the product information providing program is recorded is set in the drive device 23, and the product information providing program is installed from the recording medium 24 to the auxiliary storage device 25 via the drive device 23.

  The auxiliary storage device 25 stores the installed product information providing program and stores necessary files, data, and the like. The memory device 26 reads the product information providing program from the auxiliary storage device 25 when the product information providing server 12 is activated, and stores the read product information providing program. The arithmetic processing unit 27 executes processing related to the product information providing server 12 in accordance with the product information providing program read and stored in the memory device 26.

  Hereinafter, the process of the system 1 which implement | achieves the merchandise information provision method of this invention is demonstrated. First, in order to facilitate understanding of the present invention, the principle of the present invention will be briefly described with reference to FIG. FIG. 3 shows an example diagram illustrating the principles of the present invention.

  In step S <b> 1, the manufacturer 30 as an information sender registers the recall information in the recall information DB 31. The manufacturer 30 may register the recall information in the recall information DB 31 every predetermined period (for example, one day), or may register the recall information in the recall information DB 31 whenever a defect such as a defect is found in the sold product.

  The recall information DB 31 includes, for example, a manufacturer code that identifies a manufacturer, a product code that identifies a product, and the content of a failure. The recall information DB 31 can be accessed from a user, a credit sales company, or the like.

  Further, the credit sales company 32 as a product purchase history manager registers and manages product purchase history information in the product purchase history information DB 33. The product purchase history information DB 33 includes user information, product codes, purchase dates, and the like as items. The user information, product code, purchase date, etc. of the user who purchased the product are supplied to the credit sales company 32 from, for example, a store or a credit store.

  In step S <b> 2, the user 34 as an information receiver operates the user terminal 10, for example, and transmits a recall information acquisition request to the credit sales company 32. When the recall information acquisition request is received, the merchandise information providing server 12 of the credit sales company 32 proceeds to step S3 following step S2.

  The merchandise information providing server 12 of the credit sales company 32 reads the merchandise purchase history information of the user who transmitted the recall information acquisition request from the merchandise purchase history information DB 33, and recall information using the merchandise code included in the read merchandise purchase history information as key information. DB31 is searched.

  When the same product code as the product code included in the product purchase history information is stored in the recall information DB 31, it can be seen that the recall information is transmitted to the product purchased by the user. On the other hand, when the same product code as the product code included in the product purchase history information is not stored in the recall information DB 31, it is understood that the recall information is not transmitted to the product purchased by the user.

  For example, in FIG. 3, the recall information DB 31 is searched using the product code “asolf010” as key information, and the failure content “to spontaneously ignite” is acquired. If the recall information is not transmitted for the product with the product code “solfa300”, the failure information is not acquired even if the recall information DB 31 is searched using the product code “solfa300” as key information.

  After searching the recall information DB 31 using all the product codes included in the product purchase history information as key information, the product information providing server 12 of the credit sales company 32 proceeds to step S4 following step S3.

  In step S4, the merchandise information providing server 12 of the credit sales company 32 transmits the search result to the user terminal 10, for example. This search result includes, for example, the name of the product from which the recall information is transmitted, the content of the failure, and the like.

  Therefore, the user can easily refer to or obtain the recall information related to the purchased product without being aware of the product purchased in the past. In addition, since the user makes a recall information acquisition request according to his / her own intention, the oversight of the recall information can be reduced.

  In addition, the manufacturer 30 can increase the certainty of information transmission to a user who has purchased a product related to the recall information by disclosing the recall information to the credit sales company 32. Furthermore, since the credit sales company 32 can provide a service for selecting and notifying the recall information related to the product purchased by the user, it can be differentiated from other credit sales companies.

  FIG. 4 shows a flowchart of the first embodiment of the product information providing method of the present invention. In step S <b> 10, the product information providing server 12 receives product purchase history information from the store terminal 11. The merchandise information providing server 12 registers the input merchandise purchase history information in the merchandise purchase history information DB 40 as shown in FIG.

  FIG. 5 shows a configuration diagram of an example of the product purchase history information DB. The product purchase history information DB 40 in FIG. 5 includes items such as an information number, a user code, a purchase store, a manufacturer code, a local code, and a purchase date. The item “local code” is product identification information used by the credit sales company to identify the product.

  In step S <b> 11, the product information providing server 12 receives defect information related to a product failure from the manufacturer server 13. The merchandise information providing server 12 registers the input defect information as recall information in the recall information DB 41 as shown in FIG.

  FIG. 6 shows a configuration diagram of an example of the recall information DB. The recall information DB 41 in FIG. 6 includes items such as manufacturer code, global code, product name, production number, symptom, and countermeasure. The item “global code” is product identification information used by the manufacturer to identify the product. In addition, the item “symptom” is a failure content of the product. Furthermore, the item “handling” is a countermeasure content for a product failure.

  When a global code is input from the manufacturer server 13, the merchandise information providing server 12 converts the global code into a local code using a code conversion table 42 as shown in FIG. FIG. 7 shows a configuration diagram of an example of the code conversion table.

  The code conversion table 42 in FIG. 7 includes items such as a local code and a global code. That is, the code conversion table 42 associates local codes with global codes. By using the code conversion table 42, the merchandise information providing server 12 can convert the global code input from the manufacturer server 13 into a local code and register it in the recall information DB 41.

  In step S <b> 12, the merchandise information providing server 12 receives a defect inquiry about a defect in the merchandise from the user terminal 10. The merchandise information providing server 12 accepts the input defect inquiry. Note that the product information providing server 12 acquires the user code of the user who has input the defect inquiry through authentication processing or the like.

  In step S13, the product information providing server 12 searches the product purchase history information DB 40 using the user code acquired in step S12 as key information, and acquires a local code corresponding to the user code. That is, the local code of the product purchased by the user in the past is acquired.

  The merchandise information providing server 12 uses the code conversion table 42 to convert the acquired local code into a global code. The merchandise information providing server 12 searches the recall information DB 41 using the converted global code as key information, and acquires the recall information corresponding to the global code. That is, the recall information of the product purchased by the user in the past is acquired.

  In step S14, the merchandise information providing server 12 notifies the user terminal 10 of the recall information acquired in step S13. The user terminal 10 displays the notified recall information as an inquiry result as shown in FIG.

  FIG. 8 shows an image diagram of an example of the inquiry result screen. The inquiry result screen 43 in FIG. 8 displays items such as a product name, a manufacturer code, a purchase date, a symptom, a purchase store, and a countermeasure. That is, if there is recall information of a product purchased by the user in the past, the recall information is displayed on the inquiry result screen 43. Therefore, the user can easily inquire or acquire recall information of products purchased in the past.

  FIG. 9 shows a flowchart of the second embodiment of the product information providing method of the present invention. The merchandise purchase history information registration process in step S20 is the same as the merchandise purchase history information registration process in step S10, and thus description thereof is omitted. In step S <b> 21, the manufacturer server 13 receives defect information related to a product failure. The manufacturer server 13 registers the input defect information as recall information in the recall information DB 44 as shown in FIG. The recall information DB 44 is managed by the manufacturer.

  FIG. 10 shows a configuration diagram of another example of the recall information DB. The recall information DB 44 in FIG. 10 includes items such as a global code, a product name, a production number, a symptom, and a countermeasure. Since the recall information DB 44 is managed for each maker, the item “maker code” included in the recall information DB 41 is not included.

  Note that the defect inquiry reception process in step S22 is the same as the defect inquiry reception process in step S12, and a description thereof will be omitted. In step S23, the product information providing server 12 searches the product purchase history information DB 40 using the user code acquired in step S22 as key information, and acquires a local code corresponding to the user code.

  The merchandise information providing server 12 uses the code conversion table 42 to convert the acquired local code into a global code. The merchandise information providing server 12 can operate and query the recall information DB 44 managed by the manufacturer by using, for example, SQL (Structured Query Language).

  Therefore, the merchandise information providing server 12 searches the recall information DB 44 using the converted global code as key information, and can acquire the recall information corresponding to the global code. That is, it is possible to acquire recall information of products purchased by the user in the past. Note that the recall information notification process in step S24 is the same as the recall information notification process in step S14, and thus the description thereof is omitted.

  FIG. 11 shows a flowchart of the third embodiment of the product information providing method of the present invention. The product purchase history information registration process in step S30 is the same as the product purchase history information registration process in step S10. The recall information registration process in step S31 is the same as the recall information registration process in step S21. Since the inquiry reception process is the same as the defect inquiry reception process in step S12, description thereof is omitted.

  In step S33, the merchandise information providing server 12 queries the merchandise purchase history information DB 40, and obtains a local code corresponding to the user code obtained in step S32. That is, the local code of the product purchased by the user in the past is acquired.

  In step S34, the merchandise information providing server 12 uses the code conversion table 42 to convert the acquired local code into a global code. The merchandise information providing server 12 sends a global code as a search condition to the manufacturer server 13 to inquire the manufacturer about the recall information.

  In step S35, the manufacturer server 13 searches the recall information DB 44 using the global code as a search condition as key information, and acquires the recall information corresponding to the global code as a search result. In step S36, the manufacturer server 13 returns the recall information acquired as the search result in step S35 to the product information providing server 12.

  In step S <b> 37, the product information providing server 12 notifies the user terminal 10 of the recall information received from the manufacturer server 13. The user terminal 10 can display an inquiry result screen 43 based on the recall information notified from the product information providing server 12. The user can easily inquire or obtain recall information of products purchased in the past.

  Details of the flowcharts of FIGS. 4, 9, and 11 will be described below. FIG. 12 shows a flowchart of an example of the merchandise purchase history information registration process. In step S40, the store terminal 11 accepts product purchase information. Progressing to step S42 following step S41, the shop terminal 11 acquires the user code included in the product purchase information received in step S40, and whether or not the acquired user code is included in the user information DB 45 as shown in FIG. Determine whether.

  FIG. 13 shows a configuration diagram of an example of the user information DB. The user information DB 45 of FIG. 13 includes items such as a user code, a credit card number, an address, a telephone number, and a password code.

  If it is determined that the user code acquired in step S40 is not included in the user information DB 45 (NO in S41), the store terminal 11 is determined to be an unregistered user, and the process proceeds to step S42. In step S42, the shop terminal 11 registers user information in the user information DB 45, and proceeds to step S43. If it is determined that the user code acquired in step S40 is included in the user information DB 45 (YES in S41), the shop terminal 11 proceeds to step S43.

  In step S43, the shop terminal 11 creates product purchase history information using the user information DB 45 and the product number information DB 46 as shown in FIG. FIG. 14 shows a configuration diagram of an example of the product number information DB. The product number information DB 46 in FIG. 14 includes items such as product names, manufacturer codes, and local codes. Then, the store terminal 11 transmits the created product purchase history information to the product information providing server 12.

  In step S44, the product information providing server 12 registers the product purchase history information received from the store terminal 11 in the product purchase history information DB 40. Therefore, the product information providing server 12 can register the product purchase history of the user who purchased the product in the product purchase history information DB 40.

  FIG. 15 shows a flowchart of an example of the recall information and code conversion information registration process. The flowchart in FIG. 15 represents an example in which the product information providing server 12 has the recall information DB 41. That is, the recall information DB 41 is managed by a credit sales company or the like.

  In step S50, the merchandise information providing server 12 receives a global code from the manufacturer server 13. Since the global code is product identification information used by the manufacturer, the product information providing server 12 sets a local code corresponding to the input global code, and associates the input global code with the set local code. Are registered in the code conversion table 12. Therefore, the merchandise information providing server 12 can manage the recall information with a local code corresponding to the global code used on the manufacturer side.

  In step S <b> 51, the product information providing server 12 receives defect information related to a product failure from the manufacturer server 13. The merchandise information providing server 12 registers the received defect information in the recall information DB 41 as recall information.

  Therefore, the merchandise information providing server 12 can register the code conversion information in the code conversion table 42 and register the recall information in the recall information DB 41.

  FIG. 16 shows a flowchart of another example of the recall information and code conversion information registration process. Note that the flowchart of FIG. 16 represents an example in which the manufacturer server 13 has the recall information DB 44. That is, the recall information DB 44 is managed by the manufacturer.

  Since the code conversion table registration step in step S55 is the same as the code conversion table registration step in step S50, the description thereof is omitted. In step S56, the maker server 13 receives defect information related to a product failure. The manufacturer server 13 registers the input defect information in the recall information DB 44 as recall information.

  Therefore, the merchandise information providing server 12 can register the code conversion information in the code conversion table 42. The manufacturer server 13 can register the recall information in the recall information DB 44.

  17 and 18 show a flowchart of the first embodiment of the recall information inquiry / notification process. Note that FIG. 17 shows the former part of the recall information inquiry / notification process, and FIG. 18 shows the latter part of the recall information inquiry / notification process.

  In step S <b> 60, the merchandise information providing server 12 receives a defect inquiry regarding a defect in the merchandise from the user terminal 10. The merchandise information providing server 12 accepts the input defect inquiry. Note that the product information providing server 12 acquires the user code of the user who has input the defect inquiry through authentication processing or the like.

  Progressing to step S61 following step S60, the merchandise information providing server 12 searches the merchandise purchase history information DB 40 using the user code acquired in step S60 as key information, and whether there is merchandise purchase history information corresponding to the user code. Determine whether.

  If it is determined that there is product purchase history information corresponding to the user code (YES in S61), product information providing server 12 proceeds to step S62. In step S62, the product information providing server 12 acquires product purchase history information corresponding to the user code, and proceeds to step S63. If it is determined that there is no product purchase history information corresponding to the user code (NO in S61), the product information providing server 12 notifies the user terminal 10 that there is no product purchase history information and ends the process.

  In step S63, the product information providing server 12 determines whether there is a code conversion table corresponding to the product purchase history information acquired in step S62. Specifically, the product information providing server 12 determines whether or not a local code included in the acquired product purchase history information is registered in the code conversion table 42.

  If it is determined that there is a code conversion table corresponding to the acquired product purchase history information (YES in S63), product information providing server 12 proceeds to step S64. In step S64, the local code included in the product purchase history information acquired by the product information providing server 12 is converted into a global code.

  In step S65, the merchandise information providing server 12 searches the recall information DB 41 with the global code converted in step S64, and acquires the recall information corresponding to the global code. The merchandise information providing server 12 records the recall information acquired in step S65 in the temporary recording file 47.

  When the recall information inquiry step in step S65 is completed, or when it is determined that there is no code conversion table corresponding to the acquired product purchase history information (NO in S63), the product information providing server 12 acquires the product purchase acquired in step S62. It is determined whether the process for the history information has been completed. If the process for the acquired product purchase history information has not been completed, the processes in steps S63 to S65 are repeated.

  When the processing for the acquired product purchase history information is completed, the product information providing server 12 proceeds to step S66. In step S 66, the product information providing server 12 reads the recall information from the temporary recording file 47 and notifies the user terminal 10 of the read recall information. The user terminal 10 can display the inquiry result screen 43 according to the notified recall information.

  19 and 20 show a flowchart of the second embodiment of the recall information inquiry / notification process. Note that FIG. 19 shows the former part of the recall information inquiry / notification process, and FIG. 20 shows the latter part of the recall information inquiry / notification process.

  Since the processing of steps S70 to S72 is the same as the processing of steps S60 to S62, description thereof is omitted. In step S73, the product information providing server 12 refers to the manufacturer code of the product purchase history information acquired in step S72, and determines the manufacturer for which the recall information inquiry process is performed.

  In step S74, the product information providing server 12 selects product purchase history information corresponding to the manufacturer determined in step S73 from the product purchase history information acquired in step S72, and a code conversion table corresponding to the selected product purchase history information is displayed. It is determined whether or not there is.

  If it is determined that there is a code conversion table corresponding to the selected product purchase history information (YES in S74), product information providing server 12 proceeds to step S75. In step S75, the local code included in the product purchase history information selected by the product information providing server 12 is converted into a global code.

  In step S76, the merchandise information providing server 12 searches the recall information DB 44 with the global code converted in step S75, and acquires the recall information corresponding to the global code. The merchandise information providing server 12 operates / inquires the recall information DB 44 managed by the manufacturer by using, for example, SQL. The merchandise information providing server 12 records the recall information acquired in step S76 in the temporary recording file 47.

  When the recall information inquiry step in step S76 is completed, or when it is determined that there is no code conversion table corresponding to the selected product purchase history information (NO in S74), the product information providing server 12 purchases the product selected in step S74. It is determined whether the process for the history information has been completed. If the process for the selected product purchase history information has not been completed, the processes in steps S74 to S76 are repeated.

  When the process for the selected product purchase history information is completed, the product information providing server 12 determines whether the process for the product purchase history information acquired in step S72 is completed, and the process for the acquired product purchase history information must be completed. Steps S73 to S76 are repeated.

  When the processing for the product purchase history information acquired in step S72 is completed, the product information providing server 12 reads the recall information from the temporary recording file 47 and notifies the user terminal 10 of the read recall information. The user terminal 10 can display the inquiry result screen 43 according to the notified recall information.

  21 and 22 show a flowchart of the third embodiment of the recall information inquiry / notification process. Note that FIG. 21 shows the former part of the recall information inquiry / notification process, and FIG. 22 shows the latter part of the recall information inquiry / notification process.

  Since the processing of steps S80 to S83 is the same as the processing of steps S70 to S73, description thereof is omitted. In step S84, the product information providing server 12 selects product purchase history information corresponding to the manufacturer determined in step S83 from the product purchase history information acquired in step S82, and a code conversion table corresponding to the selected product purchase history information is displayed. It is determined whether or not there is.

  If it is determined that there is a code conversion table corresponding to the selected product purchase history information (YES in S84), product information providing server 12 proceeds to step S85. In step S85, the local code included in the product purchase history information selected by the product information providing server 12 is converted into a global code.

  In step S86, the merchandise information providing server 12 transmits the global code converted in step S85 to the manufacturer server 13 as a search condition, and inquires the manufacturer about the recall information. In step S87, the manufacturer server 13 receives a global code from the product information providing server 12 as a search condition.

  In step S88, the manufacturer server 13 searches the recall information DB 44 using the global code as the search condition as key information, and acquires the recall information corresponding to the global code. The manufacturer server 13 records the recall information acquired in step S88 in the temporary recording file 48.

  The manufacturer server 13 determines whether or not the processing for all the global codes accepted in step S87 has been completed. If the processing for all the accepted global codes has not been completed, the processing in step S88 is repeated.

  When the processing for all accepted global codes is completed, the manufacturer server 13 reads the recall information from the temporary recording file 48 and returns the read recall information to the product information providing server 12.

  In step S90, the merchandise information providing server 12 receives the recall information corresponding to the global code as the search condition from the manufacturer server 13. The merchandise information providing server 12 registers the recall information received from the manufacturer server 13 in the temporary recording file 47.

  When the recall information answer acceptance step in step S90 is completed, or when it is determined that there is no code conversion table corresponding to the selected product purchase history information (NO in S84), the product information providing server 12 acquires the product acquired in step S82. It is determined whether or not the process for the purchase history information has been completed. If the process for the selected product purchase history information has not been completed, the processes in steps S83 to S90 are repeated.

  When the processing for the product purchase history information acquired in step S82 is completed, the product information providing server 12 reads the recall information from the temporary recording file 47 and notifies the user terminal 10 of the read recall information. The user terminal 10 can display the inquiry result screen 43 according to the notified recall information.

  21 and 22, the product information providing server 12 collectively transmits a global code as a search condition to the manufacturer server 13 and receives the recall information as a search result collectively. However, a global code as a search condition may be transmitted one by one to the maker server 13 to accept recall information as a search result.

It is a block diagram of one Example of the system containing the merchandise information provision server of this invention. It is a block diagram of one Example of a merchandise information provision server. It is an example figure explaining the principle of this invention. It is a flowchart of 1st Example of the merchandise information provision method of this invention. It is a block diagram of an example of merchandise purchase history information DB. It is a block diagram of an example of recall information DB. It is a block diagram of an example of a code conversion table. It is an image figure of an example of an inquiry result screen. It is a flowchart of 2nd Example of the merchandise information provision method of this invention. It is a block diagram of another example of recall information DB. It is a flowchart of 3rd Example of the merchandise information provision method of this invention. It is a flowchart of an example of merchandise purchase history information registration processing. It is a block diagram of an example of user information DB. It is a block diagram of an example of product number information DB. It is a flowchart of an example of a recall information and code conversion information registration process. It is a flowchart of another example of a recall information and code conversion information registration process. It is a flowchart of 1st Example of a recall information inquiry and notification process. It is a flowchart of 1st Example of a recall information inquiry and notification process. It is a flowchart of 2nd Example of a recall information inquiry and notification process. It is a flowchart of 2nd Example of a recall information inquiry and notification process. It is a flowchart of 3rd Example of a recall information inquiry and notification process. It is a flowchart of 3rd Example of a recall information inquiry and notification process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 System 10 User terminal 11 Store terminal 12 Merchandise information providing server 13 Manufacturer server 14 Network 21 Input device 22 Display device 23 Drive device 24 Recording medium 25 Auxiliary storage device 26 Memory device 27 Arithmetic processing device 28 Interface device 29 Database ( DB)
31, 41, 44 Recall information DB
33,40 Product purchase history information DB
42 Code conversion table 45 User information DB
46 Part number information DB
47, 48 Temporary recording file B bus

Claims (4)

Connected to the manufacturer server managed by the manufacturer that manufactured the product, the store terminal managed by the organization that sells the product, and the purchaser terminal managed by the user who purchased the product, and from the purchaser via the purchaser terminal A product information providing server for providing trouble information related to the product in response to an inquiry about the purchased product,
A recall information registration means for registering in the recall information storage means a manufacturer code for identifying the manufacturer, a product code for identifying the product on the manufacturer side, and failure information relating to the product, transmitted from the manufacturer server;
Product purchase history information storage means for storing in the product purchase history information storage means the user information for purchasing the product input from the store terminal, the product code for identifying the product on the store side, and the purchase date;
Conversion means for converting a product code for identifying the product on the store side with reference to the code conversion table into a product code for identifying the product on the manufacturer side;
Receives an inquiry from the purchaser terminal, acquires user information for the inquiry, and acquires a product code for identifying the product on the store side stored in the product purchase history information storage unit based on the user information A failure related to the product by referring to the recall information storage means after converting the product code for identifying the product on the manufacturer side stored in the code conversion table based on the product code for identifying the product on the acquired store side Recall information acquisition means for acquiring information;
Recall information notification means for notifying the purchaser terminal of failure information related to the acquired product;
A product information providing server characterized by comprising: A manufacturer server having a recall information storage unit that stores failure information related to a product in association with a product code for identifying the product managed by the manufacturer that manufactured the product, a store terminal managed by an organization that sells the product, and the product A product information providing server connected to a purchaser terminal managed by a user who purchased the product and providing failure information related to the product in response to an inquiry about a purchased product from the purchaser via the purchaser terminal,
Product purchase history information storage means for storing user information purchased from the store terminal, product code for identifying the product on the store side, and purchase date in the product purchase history information storage means, input from the store terminal;
Conversion means for converting a product code for identifying the product on the store side with reference to the code conversion table into a product code for identifying the product on the manufacturer side;
Receives an inquiry from the purchaser terminal, acquires user information for the inquiry, and acquires a product code for identifying the product on the store side stored in the product purchase history information storage unit based on the user information In addition, based on the product code for identifying the product on the acquired store side, it is converted into a product code for identifying the product on the manufacturer side stored in the code conversion table, and the manufacturer's server is inquired about the trouble content related to the product. Recall information acquisition means to acquire;
Recall information notification means for notifying the purchaser terminal of failure information related to the acquired product;
A product information providing server characterized by comprising: Connected to the manufacturer server managed by the manufacturer that manufactured the product, the store terminal managed by the organization that sells the product, and the purchaser terminal managed by the user who purchased the product, and from the purchaser via the purchaser terminal In response to inquiries about purchased products, the product information providing server for providing failure information related to the product,
A recall information registration procedure for registering a manufacturer code for identifying a manufacturer, a product code for identifying a product on the manufacturer side, and a failure content relating to the product, in the recall information storage means, transmitted from the manufacturer server;
Product purchase history information storage procedure for storing user information for purchasing a product, a product code for identifying the product on the store side, and a purchase date stored in the product purchase history information storage means, input from the store terminal;
Receives an inquiry from the purchaser terminal, acquires user information for the inquiry, and acquires a product code for identifying the product on the store side stored in the product purchase history information storage unit based on the user information In addition, the product code for identifying the product on the store side with reference to the code conversion table is converted into a product code for identifying the product on the manufacturer side, and the recall information is stored based on the product code for identifying the product on the converted manufacturer side A procedure for referring to the means for obtaining the failure content related to the product,
Product information provision procedure for notifying the purchaser terminal of failure information related to the product,
Product information providing program to execute. A manufacturer server having a recall information storage unit that stores failure information related to a product in association with a product code for identifying the product managed by the manufacturer that manufactured the product, a store terminal managed by an organization that sells the product, and the product Connected to a purchaser terminal managed by the user who purchased the product, and in response to an inquiry about the purchased product from the purchaser via the purchaser terminal, a product information providing server for providing failure information related to the product,
Product purchase history information storage procedure for storing user information for purchasing a product, a product code for identifying the product on the store side, and a purchase date stored in the product purchase history information storage means, input from the store terminal;
Receives an inquiry from the purchaser terminal, acquires user information for the inquiry, and acquires a product code for identifying the product on the store side stored in the product purchase history information storage unit based on the user information A product code for identifying the product on the store side with reference to a code conversion table based on the product code for identifying the product on the acquired store side is converted into a product code for identifying the product on the manufacturer side, and the manufacturer server Recall information acquisition procedure to contact
Product information provision procedure for notifying the purchaser terminal of failure information related to the product,
Product information providing program to execute.

Images