Parts information management device, parts information management method, and parts information management program

Abstract

To provide a component information management device that can promote sales of a vehicle component in a plurality of sales sites.SOLUTION: A component information management device 1 registers component information on a vehicle component to be sold in a storage unit, and with the registration, outputs first sales information based on the component information to a first sales site, thereby allowing the sales on the first sales site. The component information management device further registers, in the storage unit, component supplementary information supplementing the component information registered in the storage unit, generates component related information on the vehicle component to be sold on the basis of vehicle information stored in the storage unit, and outputs second sales information based on the component information, the component supplementary information, and the component related information to a second sales site, thereby allowing the sales in the second sales site. At this time, the component information management device 1 generates component related information including a related vehicle component and an alternative vehicle component for the vehicle component to be sold on the basis of the vehicle information stored in the storage unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a parts information management device, a parts information management method, and a parts information management program, and more particularly to a parts information management device, a parts information management method, and a parts information management program that register part information on vehicle parts sold at multiple sales sites and manage sales at the sales sites. [Background technology]

[0002] Conventionally, a vehicle parts sales system has been known that includes a first sales server that provides sales information for vehicle parts through a sales site for professionals, a second sales server that provides sales information for vehicle parts through a sales site for general consumers, and a parts information management device that is connected to these sales servers via a network and that comprehensively manages the sales of vehicle parts at multiple sales sites (see, for example, Patent Documents 1 and 2). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2017-228207 [Patent Document 2] Japanese Patent Application Publication No. 2019-66897 Summary of the Invention [Problem to be solved by the invention]

[0004] In the vehicle parts sales system described above, vehicle parts are sold on a sales site for professionals and a sales site for general consumers, and the buying and selling of these vehicle parts is managed. However, when operating multiple sales sites for different users, there was a need to further promote the sales of vehicle parts. In addition, compared to sales sites aimed at specialists, sales sites aimed at general consumers needed a system that could supplement information aimed at general consumers who have less specialized knowledge, allowing them to better understand and purchase vehicle parts.

[0005] The present invention has been made in consideration of the above-mentioned problems, and an object of the present invention is to provide a parts information management device, a parts information management method, and a parts information management program that are capable of managing the sales of vehicle parts at multiple sales sites and promoting the sales of vehicle parts. [Means for solving the problem]

[0006] The above problem is solved by the parts information management device of the present invention, car Part information for both parts The tube A parts information management device for managing parts information, before Selling the vehicle part using first sales information based on the part information The first sales site and a sales site different from the first sales site, which sells the vehicle parts using second sales information based on the part information and supplemental part information related to the part information and supplementing the part information; and a second sales site that can connect to the car a storage unit that stores vehicle information relating to vehicles and vehicle parts; car a part information registration unit that registers part information relating to both parts in the storage unit; before First sales information based on the registered part information is displayed on the first sales site. force a first output section; before a part supplemental information registration unit that registers part supplemental information that supplements the part information in the storage unit; before Based on the vehicle information, Recorded car a part-related information generating unit that generates part-related information regarding both parts; and outputting second sales information based on the part information, the part supplemental information registered by the part supplemental information registering unit, and the part-related information generated by the part-related information generating unit to the second sales site. force and a second output unit configured to output a vehicle information corresponding to the vehicle part, the second output unit being ... Recorded car The related vehicle parts and / or Recorded carThis problem is solved by generating the part-related information including the alternative vehicle parts that are substitutable for both parts.

[0007] As described above, the parts information management device outputs first sales information based on part information of vehicle parts to a first sales site (e.g., a sales site for professionals), stores vehicle information related to vehicles and vehicle parts, generates part-related information related to the vehicle parts to be sold based on the vehicle information, and outputs second sales information based on the part information, supplementary part information, and part-related information to a second sales site (e.g., a sales site for general consumers). By doing so, for example, on a second sales site primarily targeting users (general consumers) who lack information on vehicle parts, vehicle parts can be listed with the part-related information required by general consumers. Specifically, related vehicle parts and replacement vehicle parts can be added to the listing.

[0008] Furthermore, the above-mentioned problem is solved by the parts information management method of the present invention, car Part information for both parts The tube A parts information management method executed by a computer that processes a part, comprising: car The computer has a storage unit for storing vehicle information relating to the vehicle and vehicle parts. ,car registering part information relating to both parts in the storage unit; before First sales information based on the above parts information and selling the vehicle part using first sales information based on the part information. First sales site force registering supplemental part information related to the part information and supplementing the part information in the storage unit; and Recorded car generating part-related information about both parts; and providing second sales information based on the part information, the part supplemental information, and the part-related information to a sales site different from the first sales site. The 2 sales sites forceand storing the vehicle information in which the vehicle parts are associated with related vehicle parts and / or alternative vehicle parts that can be substituted for the vehicle parts in the storage unit. and before When the computer generates the part-related information, the computer performs the following steps based on the vehicle information stored in the storage unit: Recorded car The related vehicle parts and / or Recorded car The problem is also solved by generating the part-related information including the alternative vehicle part that is substitutable for both parts.

[0009] Further, according to the parts information management program of the present invention, the above-mentioned object is achieved by providing a storage unit for storing vehicle information relating to a vehicle and vehicle parts. , the above Vehicle parts information The tube Reason Ruko To the computer, car A process of registering part information relating to both parts in the storage unit; before First sales information based on the above parts information and selling the vehicle parts using first sales information based on the parts information. First sales site force a process of registering supplemental part information related to the part information and supplementing the part information in the storage unit; and a process of calculating a previous vehicle information based on the vehicle information stored in the storage unit. Recorded car A process for generating part-related information about both parts, and a process for generating second sales information based on the part information, the part supplemental information, and the part-related information from a site different from the first sales site. The 2 sales sites force The process of ,car The vehicle information in which both parts are associated with related vehicle parts related to the vehicle parts and / or alternative vehicle parts that can be substituted for the vehicle parts is stored in the storage unit. and before The computer generates the part-related information based on the vehicle information stored in the storage unit. Recorded car the related vehicle parts associated with both parts and / or The aforementioned The above-mentioned problems can also be solved by executing a process for generating the part-related information including the alternative vehicle part that can be substituted for the vehicle part. [Effects of the Invention]

[0010] According to the parts information management device, parts information management method, and parts information management program of the present invention, it is possible to manage the sales of vehicle parts at a plurality of sales sites and promote the sales of vehicle parts. Furthermore, on sales sites primarily targeted at users with little specialized knowledge, vehicle parts can be listed with the part-related information required by the user, allowing the user to better understand and purchase the vehicle parts. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating the overall configuration of a parts information management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating the hardware configuration of a parts information management device and each sales server. [Figure 3] FIG. 2 is a diagram illustrating the hardware configuration of a part information management device and each user terminal. [Figure 4] FIG. 2 is a diagram illustrating functions of a parts information management device and first and second sales servers. [Figure 5] FIG. 2 is a diagram illustrating the functions of a parts information management device, a third sales server, and each user terminal. [Figure 6] FIG. 10 is a diagram showing an example of a first sales information input screen. [Figure 7] FIG. 10 is a diagram showing an example of a second sales information input screen. [Figure 8] FIG. 10 is a process flow diagram showing a parts information management method (sales registration method). [Figure 9] FIG. 10 is a process flow diagram showing a parts information management method (sales management method). DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to FIGS. As shown in FIG. 1, the parts information management system S of this embodiment is mainly composed of a parts information management device 1 that manages the sales of "vehicle parts" at multiple sales sites, a first sales server 100 that is connected to the parts information management device 1 via a network and provides sales information for vehicle parts through the "first sales site," a second sales server 200 that provides sales information for vehicle parts through the "second sales site," a third sales server 300 that provides sales information for vehicle parts through the "third sales site," a first user terminal 400 used by a "parts seller," and a second user terminal 500 used by a "parts purchaser (potential purchaser)."

[0013] Here, "vehicle parts" refers to used parts that have been used in existing vehicles, including recycled vehicle parts. Note that this is not limited to used parts, and may also include new parts. A "parts seller" is, for example, a used parts seller (used parts producer). The used parts seller checks the condition of the used vehicles received, and if there are any used parts that can be resold, dismantles them in accordance with the Recycling Act. During the dismantling process, the used parts are removed, their quality is checked, and an inspection record book is created. The used parts to be sold are then registered as products in the parts registration database of the parts information management device 1. In addition to selling registered vehicle parts to professionals, the parts seller also lists the vehicle parts on sales sites for general consumers and sells them to general consumers. A "parts purchaser" is, for example, a parts purchaser, such as a repair shop, a sheet metal shop, a gas station, a leasing / rental business, or a wholesaler such as a parts dealer. Alternatively, it could be a general consumer. Parts purchasers check the inventory of used parts for sale through a sales site for specialists, and if there is a used part that meets their desired purchase conditions, they check the condition of the used part, negotiate the purchase conditions, and then place an order (request to purchase) and purchase the used part. On the other hand, general consumers check the inventory of used parts through a sales site for general consumers, and if there is a used part they desire, they check the detailed description of the used part and purchase it (immediately purchase) without any special negotiations.

[0014] The "first sales site" is a sales site (electronic commerce site) for used vehicle parts primarily targeted at users with information (specialized knowledge) about vehicle parts, such as a "sales site for experts." Note that, because it is used exclusively for sales transactions between experts (in the same trade), the sales information for the vehicle parts being sold can be the bare minimum information (for example, the part name of the vehicle part, part identification information, and, if the vehicle part is a used part, information about the vehicle before dismantling, etc.). With only this sales information, the contents of the vehicle part can be understood, and a sale can be concluded. A "secondary sales site" is a sales site other than the primary and tertiary sales sites that sells used vehicle parts and targets a larger number of users (general consumers, including professionals) than the primary sales site by providing more information than is provided to users of the primary sales site. Secondary sales sites are also called "sales sites for general consumers" and are used to expand sales channels for vehicle parts. The information provided on the second sales site is supplemented (added) with information that makes it easier for the general consumer to buy and sell, including determining the intended use and vehicle compatibility, compared to the information provided when selling the same used vehicle parts on the first sales site, and does not exclude the same sales information provided on the first sales site. This information may include information specific to the sales site (setting information such as shop category, store category) or information specific to the user (user's past transaction evaluations, or supplementary information such as compatible vehicle models and models of vehicle parts). A "third sales site" is a sales site other than the first and second sales sites, which is a site (matching site) where parties directly trade used parts. In other words, it is a site where users who have registered on the site in advance can trade used parts on a more individual basis. For example, it is a site that matches parts sellers who want to sell used parts with parts buyers who want to purchase those used parts, as well as a site that matches parts sellers with general consumers to enable transactions. It is also called a "direct sales site."

[0015] The parts information management device 1 is a device that registers parts information about vehicle parts sold at a plurality of sales sites and manages sales at the sales sites. The parts information management device 1 is a device that provides software services related to sales management of vehicle parts to a first sales server 100, a second sales server 200, a third sales server 300, a first user terminal 400, and a second user terminal 500 that are connected via a network. More specifically, as shown in Fig. 2, the parts information management device 1 is connected to each sales server 100, 200, 300 that operates and manages sales sites for vehicle parts, and manages the sales information of vehicle parts at each sales site in an integrated manner. Note that the illustration of the sales server 300 is omitted in Fig. 2. For example, as shown in Fig. 2, the parts information management device 1 outputs sales information for vehicle parts to a first sales server 100 and a second sales server 200. Then, the part information management device 1 manages in real time the sales status of vehicle parts sold at multiple sales sites, receives notifications regarding the sales status of vehicle parts (that there has been a purchase request) from a predetermined sales server (sales site), updates the sales status of the vehicle parts, and notifies other sales servers (sales sites) of the sales status of the vehicle parts (that there has already been a purchase request).

[0016] In addition, as shown in FIG. 3, the parts information management device 1 is connected to a first user terminal 400 used by a parts seller and a second user terminal 500 used by a parts buyer, and manages transactions of vehicle parts between the parts seller and the parts buyer. For example, the part information management device 1 receives part information of a vehicle part to be sold from the first user terminal 400, registers the part information, and outputs sales information based on the part information to a sales server (sales site).Then, the real-time sales status of the vehicle part is presented to the first user terminal 400 (second user terminal 500). In addition, the parts information management device 1 is connected to each sales server that operates and manages sales sites for vehicle parts, and performs management (integrated management) regarding billing processes and billing methods when using each sales site. It also manages sales for parts sellers (first user terminals 400) and purchase costs for parts purchasers (second user terminals 500).

[0017] The parts information management device 1 communicates data with the first sales server 100, second sales server 200, and third sales server 300 that operate each sales site, and comprehensively manages (indirectly manages) the sales (sales status) of vehicle parts at each sales site, but is not limited to this. For example, the parts information management device 1 may operate each sales site, perform direct data communication with these sales sites, and directly manage the sales of vehicle parts at each sales site. Alternatively, the parts information management device 1 may have a sales information database (parts inventory database) that stores all sales information (parts inventory information) for vehicle parts sold at each sales site, and may perform the operation and management of each sales site in a unified manner.

[0018] The first sales server 100 operates and manages the first sales site under the management of the parts information management device 1, and provides a sales market for vehicle parts to the first user terminal 400 (parts seller) and the second user terminal 500 (parts purchaser). In detail, the first sales server 100 updates the sales status of the vehicle parts at the first sales site and transmits updated information regarding whether the sale of the vehicle parts has been completed, whether the sale has not been completed, or whether sales negotiations are underway to the parts information management device 1. In addition, the first sales server 100 receives updated information from the parts information management device 1 regarding whether a sale of a vehicle part has been completed, whether a sale has not been completed, or whether sales negotiations are ongoing at other sales sites, and performs processing to terminate, resume, or suspend sales of the vehicle part at the first sales site. The first sales site operated by the first sales server 100 is a "sales site for professionals." Therefore, in order for a sale of a vehicle part to be concluded on the first sales site, certain "sales conclusion conditions" must be met between the parts seller and the parts purchaser.

[0019] The second sales server 200 operates and manages the second sales site under the management of the parts information management device 1, and provides a sales market for vehicle parts to the first user terminal 400 (parts seller) and the second user terminal 500 (parts purchaser). More specifically, the second sales server 200 updates the sales status of the vehicle parts at the second sales site, and transmits updated information regarding whether the sale of the vehicle parts has been concluded or not to the parts information management device 1. In addition, the second sales server 200 receives updated information from the parts information management device 1 regarding whether a sale of a vehicle part has been completed, whether a sale has not been completed, or whether sales negotiations are ongoing at other sales sites, and performs processing to terminate, resume, or suspend sales of the vehicle part at the second sales site. The second sales site operated by the second sales server 200 is a "sales site for general consumers." Therefore, when a request to purchase a used part is received, the sale is immediately concluded regardless of the "conditions for the conclusion of the sale," as compared with the first sales site. The second sales site may also be an auction-style sales site.

[0020] The third sales server 300 operates and manages the third sales site under the management of the parts information management device 1, and provides a sales market for vehicle parts to the first user terminal 400 (parts seller) and the second user terminal 500 (parts purchaser). More specifically, the third sales server 300 updates the sales status of the vehicle parts at the third sales site, and transmits updated information about the sales of the vehicle parts to the parts information management device 1. In addition, the third sales server 300 receives updated information regarding the sales of vehicle parts at other sales sites from the parts information management device 1, and performs processing to end, resume, or suspend sales of the vehicle parts at the third sales site. The third sales site operated by the third sales server 300 is a "direct sales site for professionals." Therefore, the sales of vehicle parts may be started at a higher priority than the first and second sales sites. In other words, the parts information management device 1 may notify a specific parts purchaser that a vehicle part is being put up for sale, or a parts dealer may select a specific parts purchaser (such as a regular customer), and transactions of vehicle parts may be conducted with priority given to that parts purchaser (potential purchaser).

[0021] The first user terminal 400 is an information terminal operated by the parts seller, and specifically, is a computer such as a PC, a tablet terminal, or a smartphone. The first user terminal 400 is connected to the part information management device 1 and each sales server, and receives software services from the part information management device 1. For example, on the display screen (first sales information input screen) shown in Fig. 6, input or selection of "vehicle part information" by a user operation can be accepted to register a new vehicle part for sale and put the vehicle part up for sale on the first sales site. In other words, the "parts information registration data" shown in Fig. 3 can be sent to the parts information management device 1, making the vehicle part available for sale on the first sales site. Furthermore, the device can accept a user operation input to request viewing of the purchaser's evaluation information of the vehicle part, and display the "purchaser's evaluation information" on the display screen. In other words, the device can transmit the "view request data" shown in Fig. 3 to the parts information management device 1, obtain the "purchaser evaluation data" shown in Fig. 3 from the parts information management device 1, and display the data.

[0022] The second user terminal 500 is an information terminal operated by a part purchaser (a person who wishes to purchase), and is a computer similar to the first user terminal 400, and receives software services from the part information management device 1. For example, on a display screen (parts search screen) not shown, the inventory status of vehicle parts to be purchased can be searched for by accepting input or selection of "vehicle part identification information," "vehicle part purchasing conditions," etc. by user operation. In other words, the "target part request data" shown in Fig. 3 can be sent to the parts information management device 1, the contents of the search results can be obtained from the parts information management device 1, and the contents of the search results can be displayed. Alternatively, on a display screen (parts reservation screen) not shown, the vehicle parts to be reserved can be pre-registered, and a "user notification" can be received when a new reserved part is registered later. In other words, the "reserved parts request data" shown in Fig. 3 can be sent to the parts information management device 1, and when a new reserved part is registered later, the "user notification data" shown in Fig. 3 can be received from the parts information management device 1. Note that parts purchasers who can use the search function and reservation function are parts purchasers who are registered as members of the first sales site (third sales site). In other words, in the case of parts purchasers (general consumers) who exclusively use the second sales site, the second user terminal 500 does not necessarily need to receive software services from the parts information management device 1.

[0023] In addition, after sales of vehicle parts begin at each sales site, the first user terminal 400 and the second user terminal 500 may exchange data communications with each sales site or the sales servers 100, 200, and 300 that operate each sales site regarding specific transactions.

[0024] Additionally, for the sake of convenience of explanation, the above configuration has been described in which the first user terminal 400 and the second user terminal 500 are provided separately, but the first user terminal 400 and the second user terminal 500 may be the same terminal. In other words, there may be a user who is both a parts seller and a parts buyer. In this case, the first user terminal 400 can execute all of the functions and processes of the second user terminal 500, and the second user terminal 500 can execute all of the functions and processes of the first user terminal 400.

[0025] <Hardware configuration of parts information management system> As shown in Figures 2 and 3, the part information management device 1 is a computer equipped with a CPU as a data calculation and control processing device, ROM, RAM, and HDD (SSD) as storage devices, and a communication IF for sending and receiving information data via the Internet. The memory device of the parts information management device 1 stores a parts information management program in addition to a main program that performs the functions necessary for a computer, and the functions of the parts information management device 1 are realized by executing these programs by the CPU. Alternatively, it may be executed by a semiconductor integrated circuit equipped with a CPU or an FPGA (Field-Programmable Gate Array). The first sales server 100, the second sales server 200, the third sales server 300, the first user terminal 400, and the second user terminal 500 are also computers with similar hardware configurations.

[0026] <Functions of the parts information management system> As shown in FIG. 4, from a functional perspective, the parts information management device 1 mainly comprises a memory unit 10 that stores various programs and data such as “parts inventory data,” “first sales data,” “second sales data,” “purchaser attribute data,” “related parts list data,” and “substitute parts list data,” a parts information registration unit 11, a first output unit 12, a parts supplemental information registration unit 13, a parts-related information generation unit 14, a second output unit 15, a sales status management unit 16, an instruction unit 17, an evaluation information acquisition unit 18, an evaluation information output unit 19, a response information generation unit 20, and a response information transmission unit 21. These are composed of a CPU, ROM, RAM, HDD, communication interface, various programs, etc. The storage unit 10 (vehicle information database) stores "vehicle information" relating to vehicles and vehicle parts. The "vehicle information" is, for example, information relating to vehicles and vehicle parts required in the vehicle aftermarket. In this embodiment, the information includes the above-mentioned "related parts list data" and the above-mentioned "alternative parts list data."

[0027] Explaining the first sales server 100, the second sales server 200, and the third sales server 300 from a functional perspective, as shown in Figures 4 and 5, the main components are memory units 110, 210, 310 that store various programs and various data, communication units 111, 211, 311 that send and receive various data to and from the parts information management device 1, sales information reception units 112, 212, 312 that receive sales information of vehicle parts output from the parts information management device 1 and make it available for sale on the sales site, and sales status notification units 113, 213, 313 that notify the parts information management device 1 of the sales status of the vehicle parts. The first sales server 100 further includes a trade completion determination unit 114 that determines whether or not the "trade completion conditions" are met for the vehicle parts being sold at the first sales site. On the first sales site, the sale of a vehicle part is completed when the "conditions for the sale and purchase" are met, whereas on the second sales site, the sale of a vehicle part is completed regardless of the "conditions for the sale and purchase."

[0028] As shown in FIG. 5, the third sales server 300 further includes a user notification unit 314 that notifies the second user terminal 500 that is the target of notification when a sales registration (listing) of a vehicle part that has been reserved (reservation for purchase) on the third sales site is made, and a priority sales setting unit 315 that sets priority sales of the vehicle part for the second user terminal 500 that is the target of the user notification. When the priority sales setting unit 315 sets a "priority sales flag" for the user account of a specific second user terminal 500, that second user terminal 500 (parts purchaser) is granted the right to purchase vehicle parts (can perform vehicle part purchase operations) for a certain period of time. On the other hand, if that period has elapsed or if the sale has not been concluded, other second user terminals 500 (parts purchasers) can purchase the vehicle parts at each sales site. This sales management is performed under the management of the parts information management device 1. In other words, the parts information management device 1 instructs each sales site to update from a "sales suspended state" in which vehicle part purchase operations cannot be performed to a "sales state" in which purchase operations can be performed.

[0029] Explaining the first user terminal 400 and the second user terminal 500 from a functional perspective, as shown in FIG. 5, the main components are memory units 410, 510 that store various programs and various data, communication units 411, 511 that send and receive various data to and from the parts information management device 1, display units 412, 512 that display on a screen the service details related to the registration and sales management of vehicle parts provided by the parts information management device 1, and operation execution units 413, 513 that accept user operation input and execute operation processing.

[0030] The functions of the part information management device 1 will be described in detail below. In the following explanation, the registration and sales management of vehicle parts sold at the first sales site and the second sales site will be explained in detail, and an explanation of the third sales site will be omitted.

[0031] <<Various Data>> The "parts inventory data" stored in the storage unit 10 is data indicating inventory information for vehicle parts to be sold. This parts inventory data is stored by associating at least a vehicle part ID that identifies the vehicle part with a quantity. In addition, it is also possible to associate a vehicle model ID (alternative vehicle model ID) that identifies the vehicle model in which the vehicle part was installed or a vehicle model (alternative vehicle model) in which the vehicle part can be installed, the registration date of the vehicle part, etc. The parts inventory data is updated as needed, for example, by receiving information on new vehicle parts to be sold (parts information registration data) from the first user terminal 400, and the information on all vehicle parts is stored in a centralized manner so that it can be uniquely identified. By referencing this data, the parts information management device 1 can grasp the inventory information of all vehicle parts sold at multiple sales sites and perform the function of presenting inventory information of specified vehicle parts.

[0032] The "first sales data" is data indicating sales information of vehicle parts sold at the first sales site, and is data output to the first sales server 100. This first sales data is sales information based on part information etc. received from the first user terminal 400. The "parts information" of a vehicle part includes, for example, "identification information" of the vehicle part and "sales conditions information" of the vehicle part. That is, as shown in FIG. 6, the "first sales data (first sales information)" includes at least the "identification information" of the vehicle part and the "information on sales conditions" of the vehicle part.

[0033] The "identification information" of a vehicle part includes information about the vehicle such as the model name, type, chassis number, year, grade, engine displacement, fuel, etc., as well as information about the vehicle part such as type, vehicle part name, product number, part details, etc. The "sales condition information" for vehicle parts includes information such as an image of the vehicle part, part condition, price (new price, selling price), quantity, quality, shipping fee, and mileage. In addition, if the vehicle part is a used vehicle part, the "first sales data" may include vehicle information before the vehicle is dismantled. Furthermore, if necessary, the "first sales data" may include information on related vehicle parts and alternative vehicle parts for the vehicle part. By referring to this data, the parts information management device 1 can grasp sales information of the vehicle parts being sold at the first sales site and execute the function of managing the sales of the vehicle parts. Furthermore, looking at the "First Sales Information Input Screen" shown in Figure 6, it can be seen that the vehicle part name "Front Bumper AA" used for the vehicle model name "AA-Wagon" and model number "AA-**" is shown as an example of a vehicle part. It can also be seen that the part condition is "Damaged", the selling price is "15,000 (yen)", and the quantity is "1".

[0034] The "second sales data" is data indicating sales information of vehicle parts sold at the second sales site, and is data output to the second sales server 200. This second sales data is sales information based on the part information received from the first user terminal 400, the part supplementary information, and the part-related information generated by the part-related information generation unit 14. As shown in FIG. 7, the "second sales data (second sales information)" includes information similar to the "first sales information" described above, as well as "supplementary parts information" for vehicle parts and "parts-related information" for vehicle parts. More specifically, the information included in the "first sales information" includes the vehicle part name, quantity, part information (part condition), and an image of the vehicle part. The remaining information in the "first sales information" is input (automatically input) into the box for part information (part condition) shown in FIG. 7. The "supplementary parts information" for vehicle parts includes site information such as sales price (secondary sales price, sales price multiplier), shop category, category ID, store category, etc., which is information specific to the second sales site, and information for users (parts purchasers) such as part rank and part condition (details), which is information specific to the user. The "parts-related information" of a vehicle part includes information on related vehicle parts related to the vehicle part being sold and information on substitute vehicle parts (compatible vehicle parts) that can be substituted (compatible) for the vehicle part. In addition, information on non-compatible vehicle parts that are not compatible with the vehicle part may also be included. Note that some information may overlap between the "part information," "part supplementary information," and "part related information" of a vehicle part. For example, information such as a vehicle part ID, a vehicle part name, and a part number for identifying and associating a vehicle part may overlap.

[0035] By referring to the second sales data, the parts information management device 1 can execute the function of managing the sales of vehicle parts sold at the second sales site. 7, it can be seen that "Sales Site A" and "Sales Site B" have been selected from among multiple second sales sites. It can also be seen that the vehicle part name is "Front Bumper AA," the selling price is "20,000 yen" as supplementary part information, and the part rank is "A," and that "Related Vehicle Parts" and "Alternative Vehicle Parts" are displayed as part-related information.

[0036] The "purchaser attribute data" is data in which identification information for identifying a purchaser of a vehicle part whose sale was concluded at the first sales site is associated with evaluation information regarding the purchaser's sale. More specifically, the purchaser attribute data is stored in association with at least the purchaser's identification ID (user account), the purchaser's attribute information (personal information), the purchaser's evaluation information, and the purchase history information. "Purchaser attribute information" includes, for example, information on whether the company is a competitor or not, information on whether the company is located in a distant area from the company, and the like. "Purchaser evaluation information" refers to evaluations of past purchases of vehicle parts received from parts sellers, specifically evaluation points and evaluation comments. Evaluation comments may include positive comments as well as negative comments such as a certain number of missed payments in the past or slow transaction response times. "Purchase history information" is a correspondence between a vehicle part ID that identifies the vehicle part purchased by the purchaser, the vehicle part name, the purchase date and time of the vehicle part, and attribute information of the part seller who sold the vehicle part.

[0037] By referring to the purchaser attribute data, the parts information management device 1 can execute the function of acquiring evaluation information of the prospective purchaser when there is a desire to purchase a vehicle part at the first sales site (third sales site) and presenting the evaluation information to the first user terminal 400 (parts seller).

[0038] The "related parts list data" is data that indicates the relationship between a vehicle part to be sold and related vehicle parts related to the vehicle part. This related parts list data is stored in association with a vehicle part ID that identifies the vehicle part and a related vehicle part ID that identifies the related vehicle part related to the vehicle part identified by the vehicle part ID. Here, "related vehicle parts" refers to vehicle parts that are purchased together with a specific vehicle part, and are assumed to be parts that are frequently purchased as a set, for example, based on the nature of the part replacement work. By referring to this data, the parts information management device 1 can output second sales information including related vehicle parts to the second sales server 200 (second sales site) as shown in Fig. 7. That is, at the second sales site for general consumers, general consumers with little specialized knowledge can better understand and purchase vehicle parts. Furthermore, looking at the "Second Sales Information Input Screen" shown in Figure 7, it can be seen that the vehicle part name "Front Bumper AA" is shown, and examples of related vehicle parts include "Front Spoiler AA" and "Front Retainer BB."

[0039] The "alternative parts list data" is data showing the relationship between vehicle parts to be sold and alternative vehicle parts that can be substituted for the vehicle parts. This alternative parts list data is stored in association with a vehicle part ID that identifies a vehicle part, and an alternative vehicle part ID that identifies an alternative vehicle part that is similar to and can be substituted for the vehicle part identified by the vehicle part ID. Here, the term "alternative vehicle part" refers to a vehicle part that is functionally compatible with a specific vehicle part, and is also called a similar vehicle part. By referring to this data, the parts information management device 1 can output second sales information including substitute vehicle parts to the second sales server 200 (second sales site), as shown in FIG. Furthermore, when looking at the "Second Sales Information Input Screen" shown in FIG. 7, it can be seen that "Front Bumper BB" and "Front Bumper CC" are shown as examples of substitute vehicle parts.

[0040] <<Vehicle parts sales registration>> The part information registration unit 11 registers in the storage unit 10 part information relating to vehicle parts to be sold. In more detail, the parts information registration unit 11 accepts input of parts information for vehicle parts to be sold from the first user terminal 400 (parts seller) via the "first sales information input screen" shown in FIG. 6, and registers the parts information as first sales information (part of the first sales information). The "first sales information" is information based on the part information of the vehicle part, and includes, in addition to the part information of the vehicle part, attribute information of the part seller, site information required when selling on the first sales site, etc.

[0041] The first output unit 12, upon registration by the parts information registration unit 11, outputs first sales information based on the registered parts information to the first sales site, thereby enabling the vehicle parts to be sold at the first sales site. In detail, when the first output unit 12 receives input of the first sales information and registration of the first sales information from the first user terminal 400 (parts seller) via the "first sales information input screen" shown in FIG. 6, the first output unit 12 outputs (automatically outputs) the first sales information to the first sales server 100 upon said registration (triggered by said registration). The first sales server 100 (sales information receiving unit 112) receives the first sales information of the vehicle part output by the first output unit 12, and starts selling the vehicle part at the first sales site.

[0042] The part supplemental information registration unit 13 registers in the storage unit 10 supplemental part information that supplements the part information of the vehicle parts registered in the storage unit 10 . In detail, the parts supplementary information registration unit 13 accepts input of parts supplementary information for vehicle parts from the first user terminal 400 (parts seller) via the "second sales information input screen" shown in Figure 7, and registers the parts supplementary information for the vehicle parts as part of the second sales information. The "second sales information" is information based on the part information of the vehicle part, supplementary part information related to and supplementing the part information, and part-related information about the vehicle part (e.g., related vehicle parts, alternative vehicle parts, etc.). In addition to this information, it also includes attribute information of the part seller. The second sales information is sales information when selling on the second sales site.

[0043] The part-related information generating unit 14 generates part-related information on vehicle parts to be sold based on the "vehicle information" stored in the storage unit 10. In more detail, the part-related information generating unit 14 refers to the "vehicle information" to generate part-related information including related vehicle parts related to the vehicle parts to be sold and alternative vehicle parts that can be substituted for the vehicle parts. In addition to "related vehicle parts" and "alternative vehicle parts," part-related information may also include information on "non-compatible related vehicle parts" that are related to vehicle parts but are incompatible with the vehicle parts, and "non-compatible alternative vehicle parts" that can in principle be substituted for vehicle parts but are incompatible with some vehicles. "Incompatible related vehicle parts" are, for example, related parts that can be assembled to the same vehicle, but cannot be assembled together because the vehicle models, types, years, etc. are different. "Non-conforming substitute vehicle parts" are, for example, vehicle parts that, although they are generally substitutable for other vehicle parts, cannot be substituted for certain vehicle models, types, years, etc., and therefore cannot be considered fully conforming substitute vehicle parts.

[0044] The second output unit 15 outputs second sales information based on the part information, the part supplementary information registered by the part supplementary information registration unit 13, and the part-related information generated by the part-related information generation unit 14 to the second sales site, thereby enabling the vehicle parts to be sold at the second sales site. In detail, the second output unit 15 accepts input and registration of the second sales information from the first user terminal 400 via the "second sales information input screen" shown in Figure 7, and outputs the second sales information to the second sales server 200 when a sales instruction is given to the second sales site (triggered by the sales instruction from the user). The second sales server 200 (sales information receiving unit 212) receives the second sales information of the vehicle part output by the second output unit 15, and starts selling the vehicle part at the second sales site. It is preferable that the second output unit 15 outputs second sales information based on at least the part information and the part supplemental information to the second sales site.

[0045] Through the above sales registration process, the parts information management device 1 performs sales registration of the vehicle parts, the first sales server 100 starts selling the vehicle parts at the first sales site, and the second sales server 200 starts selling the same vehicle parts at the second sales site. After the sale of the vehicle parts starts, the parts information management device 1 manages the sales of the vehicle parts sold at a plurality of sales sites.

[0046] <<Sales management of vehicle parts>> The sales status management unit 16 manages the sales status of vehicle parts sold at the first sales site and the second sales site, and receives updated information regarding the sales status of vehicle parts from either the first sales server or the second sales server, and updates the sales status of the vehicle parts. The instruction unit 17 gives instructions on vehicle parts according to the sales status of the vehicle parts, i.e., according to the sales status of the vehicle parts updated by the sales status management unit 16. A detailed explanation is provided below.

[0047] (Sales completed on the first sales site) The sales status management unit 16 receives notification of updated information regarding the purchase request for the vehicle part from the first sales server 100 (first sales site), and updates the sales status of the vehicle part from a "sales status" in which the vehicle part is being sold at the first sales site to a "sales suspended status" in which the vehicle part is being temporarily suspended from sale. More specifically, first, the first sales server 100 (sales information receiving unit 112) receives a notification of a desire to purchase a vehicle part from the second user terminal 500 (parts purchaser) via the first sales site. Then, the sales status notifying unit 113 transmits the notification to the sales status management unit 16. Then, the sales status management unit 16 receives the notification of the updated information for the vehicle part and updates the sales status of the vehicle part. The first user terminal 400 (parts seller) receives a notification of a desire to purchase a vehicle part, and may receive the notification from the first sales server 100 or from the instruction unit 17.

[0048] Then, when the sales status at the first sales site is updated to "sales suspended", the instruction unit 17 instructs the second sales server 200 (second sales site) to update the sales status of the same vehicle part at the second sales site from "sales status" to "sales suspended". This is a process (exclusive control process) that is required in the sales management of vehicle parts because the vehicle parts are used vehicle parts and are essentially one-of-a-kind items that are not mass-produced (there are no identical items).If the vehicle parts are not one-of-a-kind items, the sales status at each sales site will be updated according to the inventory quantity of the vehicle parts. When the second sales server 200 receives an instruction for the vehicle part from the instruction unit 17, it updates the sales status at the second sales site from "sale status" to "sale suspended status."

[0049] Thereafter, when the sales status at the first sales site is in a "sales suspended state," the sales status management unit 16 receives from the first sales server 100 the fulfillment of the "sales completion conditions" for the vehicle part, and updates the sales status of the vehicle part from a "sales suspended state" to a "sales terminated state." Then, the instruction unit 17 instructs the second sales server 200 to update the sales status of the vehicle part at the second sales site from "sales suspended" to "sales terminated." The "conditions for successful sale" will be explained in detail below.

[0050] The "conditions for completing a sale" are conditions indicating whether the first user terminal 400 (parts seller) approves a sale to the second user terminal 500 (potential buyer). In other words, the conditions for completing a sale are met when the parts seller approves a sale to the potential buyer based on the potential buyer's attribute information, evaluation information, etc. The conditions for a transaction to be concluded may be satisfied not only when the parts seller approves the sale to the prospective buyer, but also when the prospective buyer approves the final purchase from the parts seller. Alternatively, the conditions for a transaction to be concluded may be satisfied not only when both users approve the sale to the prospective buyer, but also when the parts information management device 1 finally approves the sale. In addition, the parts seller is not limited to granting sales approval each time based on the evaluation information of the prospective purchaser. For example, the parts information management device 1 may automatically grant or reject sales approval on behalf of the parts seller in accordance with sales rejection conditions registered in advance by the parts seller.

[0051] "Evaluation information" will also be explained in detail. The evaluation information acquisition unit 18 receives inquiry information regarding the evaluation information of the would-be purchaser from the first user terminal 400, refers to the "purchaser attribute data" stored in the storage unit 10, and compares it with the identification ID of the would-be purchaser of the vehicle part. Then, when the identification ID of the purchaser registered in the "purchaser attribute data" matches with the identification ID of the would-be purchaser, the evaluation information of the would-be purchaser is acquired. Then, the evaluation information output unit 19 outputs the evaluation information of the intending purchaser acquired by the evaluation information acquisition unit 18 to the first user terminal 400. In addition, when the evaluation information acquisition unit 18 determines that it cannot match the identification ID of the prospective purchaser, that is, when the prospective purchaser is purchasing a vehicle part for the first time, the evaluation information output unit 19 will output to the first user terminal 400 that it is not possible to acquire the evaluation information of the prospective purchaser.

[0052] That is, the sales status management unit 16 accepts a sales approval designation operation by a user using the first user terminal 400, and the instruction unit 17 instructs the first sales server 100 about the sales approval information by the user. Note that the first user terminal 400 may directly instruct the first sales server 100. When the first sales server 100 receives approval for the sale of a vehicle part from the instruction unit 17 (first user terminal 400), it determines that the "sale and purchase completion conditions" for the vehicle part have been met. Then, it transmits information that the "sale and purchase completion conditions" have been met to the sales status management unit 16. Note that the sales status management unit 16 may determine that the "sale and purchase completion conditions" have been met instead of the first sales server 100. The sales status management unit 16 receives from the first sales server 100 the fulfillment of the "sales completion conditions" and updates the sales status of the vehicle part from "sales suspended" to "sales completed." Then, the instruction unit 17 instructs the second sales server 200 to update the sales status of the vehicle part at the second sales site from "sales suspended" to "sales terminated." Through the above series of processes, a sale of the vehicle part is concluded at the first sales site. Then, at sales sites other than the first sales site, exclusive control is performed to terminate the sale of the vehicle part for which a sale has been concluded.

[0053] In addition, when buying and selling on the first sales site, the second user terminal 500 (purchaser) who requests to purchase the vehicle part will obtain the right to negotiate with the first user terminal 400 (parts seller) selling the vehicle part, and during the negotiation period, the sales status of the vehicle part will be ``sales suspended'' on all sales sites. In other words, this can be explained as the first sales server 100 (first sales site) setting a "priority sales right (priority flag)" for the prospective purchaser, which is the first priority (priority condition) when purchasing vehicle parts.

[0054] (The sale on the first sales site was unsuccessful) The sales status management unit 16 receives notification of updated information regarding the purchase request for the vehicle part from the first sales server 100, and updates the sales status of the vehicle part from "sale status" to "sale suspended status." Then, the instruction unit 17 instructs the second sales server 200 to update the sales status of the same vehicle part at the second sales site from "Sales Status" to "Sales Suspended Status."

[0055] Thereafter, when the sales status at the first sales site is in a "sales suspended state," the sales status management unit 16 updates the sales status of the vehicle part from a "sales suspended state" to a "sales status" again by receiving from the first sales server 100 a notification that the "sales completion conditions" have not been met. Then, the instruction unit 17 instructs the second sales server 200 to update the sales status of the vehicle part at the second sales site from "sales suspended" to "sale status" again.

[0056] Here, failure to satisfy the "conditions for successful sale" means that the first user terminal 400 (parts seller) has refused to sell to the second user terminal 500 (potential buyer). That is, the sales status management unit 16 accepts a designation operation of refusing sales by a user using the first user terminal 400, and the instruction unit 17 instructs the first sales server 100 about information on the user's refusal to sell. When the first sales server 100 receives a refusal to sell the vehicle part from the instruction unit 17 (first user terminal 400), it determines that the "conditions for sale and purchase" have not been met. Then, it transmits the information that the "conditions for sale and purchase" have not been met to the sales status management unit 16. At this time, the instruction unit 17 or the first sales server 100 notifies the user of information regarding the failure of the sale to the second user terminal 500. When notifying the user, it is preferable to notify the user of the reason selected by the first sales server 100 or by automatic selection from the information on reasons for sale refusal pre-registered in the storage unit 10.

[0057] When the sales status management unit 16 updates the sales status of the vehicle part from "sales suspended" to "sale status" again and the sales status at the first sales site is updated to "sale status" again, it is advisable to perform a purchase selection disable process so that the prospective purchaser who was refused the sale cannot select to purchase the same vehicle part. The purchase selection disabling process is, for example, a process in which the parts information management device 1 collates the user ID of the prospective purchaser and instructs the first sales server 100 to hide the sales screen for the vehicle part on the first sales site displayed on the second user terminal 500 that has the user ID. Alternatively, the sales screen for the vehicle part may be grayed out, or the purchase button for the vehicle part may be hidden.

[0058] (Sales completed on the second sales site) When the sales status management unit 16 receives notification of updated information regarding the purchase request for a vehicle part from the second sales server 200, it updates the sales status of the vehicle part from "sale status" to "sales completed status" regardless of whether the "sales completion conditions" are met or not. Then, when the sales at the second sales site are updated to "sales ended", the instruction unit 17 instructs the first sales site to update the sales status at the first sales site from "sales state" to "sales ended". In other words, when a purchase request (purchase operation) for a vehicle part is made on the second sales site, the sale is immediately concluded. On the second sales site for general consumers, the same vehicle part is usually sold at a higher selling price (for example, a 150% markup) than on the first sales site. In other words, the same vehicle part is sold at a selling price and under selling conditions that are more favorable for the parts seller than on the first sales site. Therefore, when a purchase request is made by a prospective buyer at that selling price and under those selling conditions, the sale is concluded without any special negotiations.

[0059] The second sales site may be an auction-style sales site. In that case, the vehicle part may be sold to the highest bidder within a certain sales period. Alternatively, the vehicle part may be sold to the highest bidder when a higher sales price than that of the first sales site is reached.

[0060] (Inquiries on the second sales site) The storage unit 10 stores "vehicle information" in which vehicle parts are associated with related vehicle parts and alternative vehicle parts. The response information generation unit 20 receives inquiry information regarding vehicle parts sold at the second sales site from the second sales server 200, and generates response information to the inquiry information by referring to the ``vehicle information'' stored in the memory unit 10. Then, the response information transmitting unit 21 transmits the response information generated by the response information generating unit 20 to the second sales server 200. That is, the second user terminal 500 (parts purchaser) can receive response information to the inquiry from the part information management device 1 via the second sales server 200. The "response information to the inquiry" may be, for example, more detailed information about related vehicle parts or replacement vehicle parts, or current or past listing information for related vehicle parts or replacement vehicle parts.

[0061] <Parts information management method> Next, the processing of the parts information management program (parts information management method) executed by the parts information management system S will be described with reference to FIGS. The program according to this embodiment is a program for realizing the above-mentioned part information registration unit 11, first output unit 12, part supplementary information registration unit 13, part-related information generation unit 14, second output unit 15, sales status management unit 16, instruction unit 17, evaluation information acquisition unit 18, evaluation information output unit 19, response information generation unit 20, and response information transmission unit 21 as functional components of a part information management device 1 equipped with a memory unit 10, and the CPU of the part information management device 1 executes this part information management program. The memory unit 10 of the parts information management device 1 stores "parts inventory data," "first sales data," "second sales data," "purchaser attribute data," "related parts list data," "substitute parts list data," etc.

[0062] The flow shown in FIG. 8 shows the processing flow of the "sales registration method," and the flow shown in FIG. 9 shows the processing flow of the "sales management method."

[0063] The processing flow of the sales registration method shown in FIG. 8 begins with step S1 in which the part information registration unit 11 accepts "part information" of a new vehicle part from the first user terminal 400 and registers the part information. More specifically, the parts information registration unit 11 registers the parts information of the vehicle parts as “first sales information.” The “first sales information” includes, in addition to the parts information of the vehicle parts, attribute information of the parts seller, site information required for selling on a sales site, and the like.

[0064] Then, in step S2, the first output unit 12, upon registration by the part information registration unit 11, outputs "first sales information" based on the registered part information to the first sales site. More specifically, the first output unit 12 automatically outputs the "first sales information" to the first sales server 100 upon the above registration. The first sales server 100 receives the "first sales information" of the vehicle parts and sells the vehicle parts at the first sales site. Note that the first sales site may start selling the vehicle parts first, or the first sales site and the second sales site may start selling the vehicle parts at the same time.

[0065] Then, in step S3, the part supplemental information registration unit 13 accepts input of "part supplemental information" for the vehicle part from the first user terminal 400, and registers the part supplemental information. Then, in step S4, the part-related information generating unit 14 generates "part-related information" about the vehicle part based on the "vehicle information" stored in the storage unit 10, and registers the part-related information (step S5). More specifically, the part information management device 1 registers the part information of the vehicle part, the part supplemental information, and the part related information as "second sales information."

[0066] Then, in step S6, if the second output unit 15 receives a sales instruction from the first user terminal 400 to the second sales site (step S6: Yes), it proceeds to step S7 and outputs the "second sales information" to the second sales server 200. The second sales server 200 accepts the "second sales information" of the vehicle part and sells the vehicle part at the second sales site.

[0067] The process of FIG. 8 is completed through steps S1 to S7. That is, the parts information management device 1 performs sales registration of the vehicle parts, the first sales server 100 starts selling the vehicle parts at the first sales site, and the second sales server 200 starts selling the same vehicle parts at the second sales site. On the other hand, if the second output unit 15 does not receive a sales instruction to the second sales site (step S6: No), sales of the vehicle parts will begin at the first sales site, but sales of the vehicle parts will not take place at the second sales site.

[0068] Next, we will explain the processing flow of the sales management method shown in Fig. 9. In this processing flow, we assume that vehicle parts are sold at a first sales site and a second sales site, and the sale of the vehicle parts is concluded at the first sales site. First, the process starts in step S101, in which the sales status management unit 16 manages the sales status of vehicle parts sold at the first sales site and the second sales site, and waits for updated information on the sales status of vehicle parts from each sales server.

[0069] Then, in step S102, the sales status management unit 16 receives a notification from the first sales server 100 regarding a purchase request for the vehicle part, and updates the sales status of the vehicle part from "sale status" to "sale suspended status." At this time, the first sales server 100 also sends a notification regarding the desire to purchase the vehicle part to the first user terminal 400, and notifies the parts seller that there is a desire to purchase the vehicle part. In addition, the first sales server 100 changes the sales status of the vehicle part at the first sales site from "sale status" to "sale suspension status."

[0070] Then, in step S103, the instruction unit 17 instructs the second sales server 200 to update the sales status of the same vehicle part at the second sales site from "Sales Status" to "Sales Suspended" in response to the sales status at the first sales site being updated to "Sales Suspended." The second sales server 200 receives the instruction from the instruction unit 17 and changes the sales status of the vehicle part at the second sales site from "sale status" to "sale suspension status."

[0071] Then, in step S104, the evaluation information acquisition unit 18 receives inquiry information regarding the evaluation information of the would-be purchaser from the first user terminal 400, and compares it with the identification ID of the would-be purchaser of the vehicle part by referring to the "purchaser attribute data" stored in the storage unit 10. Then, when the identification ID of the purchaser registered in the "purchaser attribute data" matches with the identification ID of the would-be purchaser, the evaluation information of the would-be purchaser is acquired. Then, in step S105, the evaluation information output unit 19 outputs the evaluation information of the intending purchaser to the first user terminal 400.

[0072] Then, the first user terminal 400 (parts seller) accepts a user's designation operation of "sales approval of vehicle parts" based on the evaluation information of the prospective purchaser, and instructs the first sales server 100 to grant the sales approval. When the first sales server 100 receives the sales approval for the vehicle part, it determines that the "sales completion conditions" for the vehicle part have been met, and then transmits to the sales status management unit 16 information that the "sales completion conditions" have been met. In addition, the first sales server 100 changes the sales status of the vehicle part at the first sales site from "sales suspended" to "sales completed."

[0073] Then, in step S106, the sales status management unit 16 accepts that the "sales completion condition" has been met and updates the sales status of the vehicle part from "sales suspended" to "sales completed." Then, in step S107, the instruction unit 17 instructs the second sales server 200 to update the sales status of the vehicle part at the second sales site from "sales suspended" to "sales terminated." The second sales server 200 receives the instruction from the instruction unit 17 and changes the sales status of the vehicle part at the second sales site from "sales suspended" to "sales completed."

[0074] Then, in step S108, the parts information management device 1 notifies the first user terminal 400 that the sale of the vehicle part has been concluded, and stores information relating to the conclusion of the sale of the vehicle part in the storage unit 10 (step S109). The process of FIG. 9 is completed through steps S101 to S109.

[0075] The parts information management method shown in FIGS. 8 and 9 makes it possible to manage the sales of vehicle parts at a plurality of sales sites and promote the sales of vehicle parts.

[0076] <Other embodiments> In the above embodiment, the parts information management device 1 manages the sales of vehicle parts at the first sales site, the second sales site, and the third sales site, but is not particularly limited to sales management at three sales sites. For example, the parts information management device may manage the sales of vehicle parts at a first sales site for professionals and a second sales site for general consumers. Alternatively, the parts information management device may manage the sales of vehicle parts at a plurality of first sales sites and a plurality of second sales sites.

[0077] In the above embodiment, the part information registration unit 11 registers part information about vehicle parts to be sold in the storage unit (parts registration database), but registration is not limited to on a vehicle part-by-vehicle part basis. Considering that the vehicle parts are used vehicle parts, the part information registration unit 11 may register vehicles and vehicle parts while associating the vehicle parts with each other on a vehicle-by-vehicle (used vehicle) basis. This makes it easier to register the vehicle parts in association with each other. It also makes it easier to sell the vehicle parts as a set. In this case, it is preferable to be able to display a "sales information input screen" for each vehicle in addition to the "sales information input screen" for each vehicle part shown in Figures 6 and 7. It is also preferable to be able to register detailed information about the vehicle, not just the vehicle parts.

[0078] In the above embodiment, a part information management program is stored in a recording medium readable by the part information management device 1, and processing is performed by the part information management device 1 reading and executing the program. Here, the recording medium readable by the part information management device 1 refers to a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, etc. Alternatively, a dedicated web application may be started using a terminal (mobile terminal) that serves as the part information management device 1, and the part information management program may be executed on a web browser.

[0079] In the above embodiment, the parts information management device, the parts information management method, and the parts information management program according to the present invention have been mainly described. However, the above embodiment is merely an example for facilitating understanding of the present invention, and does not limit the present invention. The present invention can be modified and improved without departing from the spirit thereof, and the present invention naturally includes equivalents thereof. [Explanation of symbols]

[0080] S Parts information management system 1. Parts information management device 10 Storage section 11 Parts Information Registration Section 12 First output section 13 Parts supplementary information registration section 14 Parts-related information generation unit 15 Second output section 16 Sales Status Management Department 17 Instruction section 18 Evaluation information acquisition unit 19 Evaluation information output unit 20 Answer information generation section 21 Response information sending unit 100 First sales server 110 Storage section 111 Communications Department 112 Sales Information Reception Department 113 Sales Status Notification Department 114 Trading Determination Department 200 Second sales server 210 Storage section 211 Communications Department 212 Sales Information Reception Department 213 Sales Status Notification Department 300 Third sales server 310 Storage section 311 Communications Department 312 Sales Information Reception Department 313 Sales Status Notification Department 314 User Notification Section 315 Priority Sales Setting Department 400 First user terminal 410 Storage section 411 Communications Department 412 Display section 413 Operation Execution Unit 500 Second user terminal 510 Storage section 511 Communications Department 512 Display section 513 Operation Execution Unit

Claims

1. A parts information management device for managing part information of vehicle parts, a first sales site that sells the vehicle parts using first sales information based on the part information; a second sales site that is different from the first sales site and that sells the vehicle parts using second sales information based on the part information and supplemental part information that is related to the part information and supplements the part information, a storage unit that stores vehicle information relating to vehicles and vehicle parts; a part information registration unit that registers part information related to vehicle parts in the storage unit; a first output unit that outputs first sales information based on the registered part information to the first sales site; a part supplemental information registration unit that registers part supplemental information that supplements the part information in the storage unit; a part-related information generating unit that generates part-related information about the vehicle part based on the vehicle information; a second output unit that outputs second sales information based on the part information, the part supplemental information registered by the part supplemental information registration unit, and the part related information generated by the part related information generation unit to the second sales site; Equipped with the storage unit stores the vehicle information in which a vehicle part is associated with an associated vehicle part related to the vehicle part and / or an alternative vehicle part that can be substituted for the vehicle part; The part-related information generation unit generates the part-related information including the related vehicle parts related to the vehicle parts and / or the alternative vehicle parts that can be substituted for the vehicle parts based on the vehicle information stored in the memory unit.

2. A parts information management method executed by a computer that manages part information of vehicle parts, comprising: The computer has a storage unit that stores vehicle information related to vehicles and vehicle parts, and registers part information related to the vehicle parts in the storage unit; outputting first sales information based on the part information to a first sales site that sells the vehicle part using the first sales information based on the part information; registering, in the storage unit, supplemental part information that is related to the part information and supplements the part information; generating part-related information about the vehicle part based on the vehicle information stored in the storage unit; outputting second sales information based on the part information, the part supplementary information, and the part-related information to a second sales site different from the first sales site; The storage unit stores the vehicle information in which a vehicle part is associated with a related vehicle part related to the vehicle part and / or a substitute vehicle part that can be substituted for the vehicle part, The computer A part information management method, which, when generating the part-related information, generates the part-related information including the related vehicle parts related to the vehicle parts and / or the alternative vehicle parts that can be substituted for the vehicle parts based on the vehicle information stored in the storage unit.

3. a computer having a storage unit for storing vehicle information relating to a vehicle and a vehicle part, and managing part information of the vehicle part; A process of registering part information related to vehicle parts in the storage unit; a process of outputting first sales information based on the part information to a first sales site that sells the vehicle part using the first sales information based on the part information; a process of registering supplemental part information related to the part information and supplementing the part information in the storage unit; generating part-related information about the vehicle part based on the vehicle information stored in the storage unit; outputting second sales information based on the part information, the part supplemental information, and the part-related information to a second sales site different from the first sales site; The storage unit stores the vehicle information in which a vehicle part is associated with a related vehicle part related to the vehicle part and / or a substitute vehicle part that can be substituted for the vehicle part, The computer, A part information management program that executes a process for generating the part-related information, based on the vehicle information stored in the storage unit, to generate the part-related information including the related vehicle parts related to the vehicle parts and / or the alternative vehicle parts that can be substituted for the vehicle parts.

Images