Trade management system, trade management program, and trade management method
The transaction management system addresses inefficiencies in trader transactions by using historical data to determine alert dates, manage inventory, and control editing rights, ensuring timely and efficient product ordering and receiving.
Patent Information
- Application Number
- JP2019240005
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2019-12-29
- Publication Date
- 2024-12-04
- Estimated Expiration
- 2039-12-29
AI Technical Summary
Existing transaction management systems do not facilitate smooth ordering and receiving of products between traders, leading to inefficiencies and difficulties in managing inventory and logistics.
A transaction management system that includes a server and terminal capable of communicating with it, featuring a product management department, alert unit, and component expansion unit, which calculates alert dates based on historical delivery or order data, manages inventory, and allows for product registration with nicknames to avoid confusion, and controls editing rights based on business partner roles.
Enables smooth transactions by ensuring timely ordering and inventory management, preventing shortages, and simplifying the ordering process through historical data analysis and controlled editing rights, thereby enhancing operational efficiency.
Smart Images

Figure 0007594266000005 
Figure 0007594266000006 
Figure 0007594266000007
Abstract
Description
[Technical field]
[0001] The present invention relates to a transaction management system, a transaction management program, and a transaction management method. [Background technology]
[0002] In recent years, various transactions have been taking place, but managing the suppliers and vendors of these transactions can be extremely difficult.
[0003] In Patent Document 1, the order receiving server includes an inventory information receiving means for receiving inventory information of products that can be ordered by a trader from the trader terminal, an inventory information recording means for recording the inventory information received by the inventory information receiving means in a recording device; a first order receiving means for receiving an order for a product by disclosing the inventory information recorded in the recording device to an orderer terminal and receiving a selection of inventory information of a product that the orderer wishes to order from the orderer terminal, which is a store terminal; The disclosed device is equipped with a second order accepting means for accepting an order for a product by receiving, from the orderer terminal, information regarding the product that the orderer wishes to order as request information, disclosing the request information to the trader terminal, and accepting from the trader terminal a selection of whether or not to comply with the orderer's request based on the request information.
[0004] In other words, "inventory information is disclosed to purchasers, who can specify the products they want and place orders, and information about the products the purchaser wishes to order is disclosed to traders, who can then choose whether or not to comply with the request. This allows traders to receive orders from purchasers specifying the stock to be allocated, and furthermore, if there is a product that the purchaser desires, they can accept the order by fulfilling that request.
[0005] Patent document 2 describes a system that simplifies invoice management for commodity transactions between multiple traders in stages, and includes a transaction setting information storage unit that stores an upstream trader ID from which an intermediate trader orders the commodity, in correspondence with an intermediate trader ID and a product ID, a price storage unit that stores a first selling price of the commodity by the upstream trader in correspondence with the product ID and upstream trader ID, and stores a second selling price of the commodity by the intermediate trader in correspondence with the product ID and intermediate trader ID, and a invoice issuance processing unit.
[0006] "When a downstream trader places an order for a product, the invoice issuance processing unit generates an order invoice from the downstream trader to the intermediate trader based on the order quantity and the second selling price, and also generates an order invoice from the intermediate trader to the upstream trader based on the order quantity and the first selling price."
[0007] In other words, "order, delivery, and logistics data are managed centrally, and delivery documents are efficiently created using the data at the time of generating order documents." [Prior art documents] [Patent documents]
[0008] [Patent Document 1] JP 2014-74975 A [Patent Document 2] JP 2018-142382 A Summary of the Invention [Problem to be solved by the invention]
[0009] However, the inventions disclosed in Patent Documents 1 and 2 do not allow traders to smoothly place and receive orders for products with each other.
[0010] An object of the present invention is to facilitate smooth ordering and placing of goods between traders. [Means for solving the problem]
[0011] A transaction management system according to a first aspect of the present invention is a transaction management system for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: The server, A product management unit that records the delivery or order history of the product; an alert unit that transmits an alert to the terminal based on a delivery or order history of the product recorded in the product management unit; The alert unit is a transaction management system that determines an alert date based on records of past deliveries or orders of the product recorded by the product management unit.
[0012] Since the alert date is determined based on the delivery or order history, the terminal user can smoothly place and receive orders for products.
[0013] A transaction management system according to a second aspect of the present invention is a transaction management system according to the first aspect, The alert unit is a transaction management system that calculates the number of days it will take to consume the delivery quantity by dividing the delivery quantity by the consumption amount, and determines the alert date.
[0014] The number of days it will take to consume the latest delivery quantity is calculated by dividing the latest delivery quantity by the consumption amount per day.
[0015] The date on which the alert will be issued is determined by adding the calculated number of days to the latest delivery date.
[0016] The alert date is calculated based on past inventory records, so the terminal user can refer to the alert to place an order for the product, which allows for smooth transactions.
[0017] A transaction management system according to a third aspect of the present invention is a transaction management system according to the first or second aspect, The alert unit is a transaction management system that determines the alert date for the maximum value, the minimum value, and the average value by calculating the number of days in which the delivery quantity will be consumed based on the maximum value, the minimum value, and the average value among the multiple calculated consumption amounts.
[0018] The maximum value means that the consumption per day is high, so the alert date will be earlier, whereas the minimum value means that the consumption per day is low, so the alert date will be later.
[0019] The terminal user can place orders for products by referring to multiple alerts such as maximum, minimum and average prices, which allows for smoother transactions.
[0020] A transaction management system according to a fourth aspect of the present invention is a transaction management system for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: The server, A product management section that manages inventory of the products; an alert unit that transmits an alert to the terminal when there is a risk of a shortage of inventory of the product; The product management department records the shipping fluctuations of the products, The alert unit is a transaction management system that determines an alert date based on the record of the shipment fluctuation of the product recorded by the product management unit.
[0021] By being alerted about product stock, the terminal user can prevent situations where stock is insufficient and delivery is delayed.
[0022] The alert date is determined taking into consideration the number of days it takes to order inventory and deliver the product (delivery date).
[0023] This allows the terminal user to carry out transactions smoothly.
[0024] A transaction management system according to a fifth aspect of the present invention is a transaction management system for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: The server, a parts expansion unit that registers parts that constitute the product as parts and associates the parts with the product; When an order for the part is placed, the transaction management system displays the part on the display unit of the terminal.
[0025] There are cases where the user of the terminal needs to order parts for the product that has been ordered, but in the present invention, the parts expansion unit links the product parts, so ordering parts is easy, which allows for smooth transactions.
[0026] A transaction management system according to a sixth aspect of the present invention is a transaction management system according to any one of the first to fifth aspects, The product management unit is a transaction management system that allows the product to be registered under a nickname.
[0027] Giving each product an easy-to-understand nickname has the advantage of preventing confusion with other companies' products and making it easier to understand the connection between the company's own products.
[0028] A transaction management system according to a seventh aspect of the present invention is a transaction management system for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: The terminal can access the server and edit information about the product; If the product is a ready-made product, the terminal capable of editing the product information is the terminal of the upstream trading partner, When the product is an order product, the terminals capable of editing the product information are the terminal of the most downstream trading partner and the trading management system which is the terminal of the trading partner one upstream.
[0029] If the product is a ready-made product, only the most upstream trading partner can edit the product information. Alternatively, the most upstream trading partner and its downstream trading partners may be allowed to edit the product information.
[0030] In addition, if the product is a custom-made product (an original product, not a ready-made product), only the most downstream trading partner and the trading partner one level upstream can edit the product information. It is also possible to make it so that only the most downstream trading partner can edit the product information.
[0031] A transaction management program according to an eighth aspect of the present invention is a transaction management program for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: A product management process for recording the delivery or ordering history of the product; an alert process for transmitting an alert to the terminal based on a delivery or order history of the product recorded by the product management process; The alert process is a transaction management program that determines an alert date based on records of past deliveries or orders of the product recorded by the product management process.
[0032] Since the alert date is determined based on the delivery or order history, the terminal user can smoothly place and receive orders for products.
[0033] A transaction management program according to a ninth aspect of the present invention is a transaction management program according to the seventh aspect, comprising: The alert process is a transaction management program that calculates the number of days it takes to consume the delivery quantity by dividing the delivery quantity by the consumption amount, and determines the alert date.
[0034] The number of days it will take to consume the latest delivery quantity is calculated by dividing the latest delivery quantity by the consumption amount per day.
[0035] The date on which the alert will be issued is determined by adding the calculated number of days to the latest delivery date.
[0036] The alert date is calculated based on past inventory records, so the terminal user can refer to the alert to place an order for the product, which allows for smooth transactions.
[0037] A transaction management program according to a tenth aspect of the present invention is a transaction management program according to the seventh or eighth aspect, The alert processing is a transaction management program that determines the alert date for the maximum value, the minimum value, and the average value by calculating the number of days in which the delivery quantity will be consumed based on the maximum value, the minimum value, and the average value of the calculated consumption amounts.
[0038] The maximum value means that the consumption per day is high, so the alert date will be earlier, whereas the minimum value means that the consumption per day is low, so the alert date will be later.
[0039] The terminal user can place orders for products by referring to multiple alerts such as maximum, minimum and average prices, which allows for smoother transactions.
[0040] A transaction management program according to an eleventh aspect of the present invention is a transaction management program for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: A product management process for managing inventory of the product; An alert process is executed to send an alert to the terminal when there is a risk of a shortage of the inventory of the product; The product management process records the shipping fluctuations of the product, The alert process is a transaction management program that determines an alert date based on the record of the fluctuation in shipment of the product recorded by the product management process.
[0041] By being alerted about product stock, the terminal user can prevent situations where stock is insufficient and delivery is delayed.
[0042] The alert date is determined taking into consideration the number of days it takes to order inventory and deliver the product (delivery date).
[0043] This allows the terminal user to carry out transactions smoothly.
[0044] A transaction management program according to a twelfth aspect of the present invention is a transaction management program for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising: A part product constituting the product is registered as a part, and a part expansion process is executed to associate the part product with the product; A transaction management program that displays the part product on the display unit of the terminal when an order for the part is placed.
[0045] There are cases where the user of the terminal needs to order parts for the product that has been ordered, but in the present invention, the parts expansion unit links the product parts, so ordering parts is easy, which allows for smooth transactions.
[0046] A transaction management program according to a thirteenth aspect of the present invention is a transaction management program according to any one of the seventh to eleventh aspects, The product management process is a transaction management program that allows the product to be registered under a nickname.
[0047] Giving each product an easy-to-understand nickname has the advantage of preventing confusion with other companies' products and making it easier to understand the connection between the company's own products.
[0048] A transaction management method according to a fourteenth aspect of the present invention is a transaction management method for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising the steps of: a product management step of recording a delivery or order history of the product; an alert step of transmitting an alert to the terminal based on a delivery or order history of the product recorded by the product management step; The alert step is a transaction management method in which an alert date is determined based on a record of past deliveries or orders of the product recorded by the product management step.
[0049] Since the alert date is determined based on the delivery or order history, the terminal user can smoothly place and receive orders for products.
[0050] A transaction management method according to a fifteenth aspect of the present invention is a transaction management method according to the thirteenth aspect, comprising: The transaction management method includes a step of: dividing the number of deliveries by the consumption amount to calculate the number of days required to consume the number of deliveries, thereby determining the alert date.
[0051] The number of days it will take to consume the latest delivery quantity is calculated by dividing the latest delivery quantity by the consumption amount per day.
[0052] The date on which the alert will be issued is determined by adding the calculated number of days to the latest delivery date.
[0053] The alert date is calculated based on past inventory records, so the terminal user can refer to the alert to place an order for the product, which allows for smooth transactions.
[0054] A transaction management method according to a sixteenth aspect of the present invention is a transaction management method according to the thirteenth or fourteenth aspect, comprising: This is a transaction management method in which the alert step calculates the number of days in which the delivery quantity will be consumed based on the maximum, minimum and average values of the consumption amounts calculated multiple times, thereby determining the alert dates for the maximum, minimum and average values.
[0055] The maximum value means that the consumption per day is high, so the alert date will be earlier, whereas the minimum value means that the consumption per day is low, so the alert date will be later.
[0056] The terminal user can place orders for products by referring to multiple alerts such as maximum, minimum and average prices, which allows for smoother transactions.
[0057] A transaction management method according to a seventeenth aspect of the present invention is a transaction management method for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising the steps of: A product management process for managing inventory of the product; an alert step of sending an alert to the terminal when there is a risk of a shortage of inventory of the product; The product management step records the shipping fluctuation of the product, The transaction management method includes determining an alert date by the alert step based on the record of the fluctuation in shipment of the product recorded by the product management step.
[0058] By being alerted about product stock, the terminal user can prevent situations where stock is insufficient and delivery is delayed.
[0059] The alert date is determined taking into consideration the number of days it takes to order inventory and deliver the product (delivery date).
[0060] This allows the terminal user to carry out transactions smoothly.
[0061] A transaction management method according to an eighteenth aspect of the present invention is a transaction management method for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising the steps of: a parts expansion step in which parts products constituting the product are registered as parts and the parts products are associated with the product; This is a transaction management method in which, when an order for the part is placed, the part is displayed on the display unit of the terminal.
[0062] There are cases where the user of the terminal needs to order parts for the product that has been ordered, but in the present invention, the parts expansion unit links the product parts, so ordering parts is easy, which allows for smooth transactions.
[0063] A transaction management method according to a nineteenth aspect of the present invention is a transaction management method according to any one of the thirteenth to seventeenth aspects, comprising: The product management step is a transaction management method in which the product can be registered with a nickname.
[0064] Giving each product an easy-to-understand nickname has the advantage of preventing confusion with other companies' products and making it easier to understand the connection between the company's own products.
[0065] A transaction management method according to a twentieth aspect of the present invention is a transaction management method for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising the steps of: The terminal can access the server and edit information about the product; a first editing right transfer step in which, when the product is a ready-made product and the supplier registered in the server is an upstream supplier, a terminal of the upstream supplier can edit information on the product, and a terminal of the downstream supplier cannot edit information on the product; When the product is an ordered product, if the trading partner registered in the server is a downstream trading partner, a second editing right transfer step is included in which the terminal of the downstream trading partner and the trading partner one upstream from the downstream trading partner can edit information about the product, and other trading partners cannot edit the information about the product.
[0066] If the product is a ready-made product, only the most upstream trading partner can edit the product information.
[0067] In addition, if the product is a custom-made item (an original product, not a ready-made product), only the most downstream trading partner and the trading partner one level upstream can edit the product information. [Brief description of the drawings]
[0068] [Figure 1] 1 is a conceptual diagram of a transaction management system according to an embodiment of the present invention. [Diagram 2] 1 is a conceptual diagram of a transaction management system according to an embodiment of the present invention. [Diagram 3] A conceptual diagram of a server memory unit of a transaction management system in one embodiment according to the present invention. [Figure 4] 4 is a flowchart for purchasing a transaction management system in one embodiment of the present invention. [Diagram 5] 4 is a flowchart relating to editing of a transaction management system in one embodiment of the present invention. [Figure 6] 4 is a flowchart relating to editing of a transaction management system in one embodiment of the present invention. [Figure 7] 4 is a flowchart relating to editing of a transaction management system in one embodiment of the present invention. [Figure 8] 4 is a flowchart relating to editing of a transaction management system in one embodiment of the present invention. [Figure 9] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 10] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 11] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 12] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 13] 4 is a flowchart relating to sales of a transaction management system in one embodiment of the present invention. [Figure 14] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 15] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 16] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 17] A display unit of a terminal of a transaction management system in one embodiment of the present invention. [Figure 18] 4 is a flowchart relating to a transaction management system sales in one embodiment of the present invention. [Figure 19] A trading partner list displayed on a terminal of a trading management system in one embodiment of the present invention. [Figure 20]A conceptual diagram of nicknames for a transaction management system in one embodiment of the present invention. [Figure 21] 4 is a flowchart relating to the part expansion section of a transaction management system in one embodiment of the present invention. [Figure 22] 4 is a flowchart relating to an alert in a transaction management system in one embodiment of the present invention. [Figure 23] 4 is a flowchart relating to an alert in a transaction management system in one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0069] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0070] The transaction management system 100 according to this embodiment includes a server 200 and A first terminal 300 capable of communicating with the server 200 and editing part of the information in the server; A second terminal 400 capable of communicating with the server 200 and editing information in the server 200; Includes.
[0071] The server 200 includes a server storage unit 210 for storing information. An alert unit 220 that transmits an alert to a first terminal 300 that is a terminal; a parts expansion unit 230 for registering parts constituting a product as separate products and linking them to the product to be sold; a product management unit (240) that manages product inventory and transmits an alert to a first terminal (300) according to the number of products in stock; and a server communication unit 250 that enables communication with the first terminal 300 and the second terminal 400.
[0072] The server 200 is a normal server, but may also be a cloud server.
[0073] The server storage unit 210 includes a purchasing unit 500 for allowing the user of the first terminal 300 to select and place an order for a product that he or she wishes to purchase, A sales section 600 for allowing a user of the first terminal 300 to select and order products to be sold; A trading partner list 700 that displays a list of trading partners; and a member registration section 800 for registering the user of the first terminal 300 and the trading partner (transactor).
[0074] The product management section 240 includes a product information section 241 for registering product information, a sales information section 242 for registering product sales information; and a purchase information section 243 for registering product purchase information.
[0075] The information stored in the product management unit 240 is stored in the server storage unit 210. The product management unit 240 may be configured to be included in the first terminal 300.
[0076] It should be noted that a trading partner (transactor) may also be a user of the first terminal 300, but for the sake of explanation, the user of the first terminal 300 and the transactor will be described separately.
[0077] The first terminal 300 includes a first display unit 310 that displays product information stored in the server storage unit 210 of the server 200; The first communication unit 320 enables communication with the server 200.
[0078] The purchasing section 500 includes a purchasing list section 510 for storing and displaying information on purchasable products as a list; a first unconfirmed list unit 520 for storing and displaying a list of information on products to be purchased that the user of the first terminal 300 has not yet confirmed; and an order list section 530 for storing and displaying, as a list, information on products that the user of the first terminal 300 has ordered from a trader.
[0079] The purchase list section 510 is a section for storing and displaying information on products that the user of the first terminal 300 wishes to purchase as a list.
[0080] (Register the product you want to purchase) Specifically, as shown in FIG. 4, first, the user of the first terminal 300 registers a product that he or she wishes to purchase, and sets the place of purchase (transactor) (step S11).
[0081] When a user of the first terminal 300 registers a product, that user can edit the product.
[0082] Next, the server 200 transmits an approval email to the trader (purchaser) (step S12). Note that, although an approval email is used in this embodiment, a notification other than an email may be used.
[0083] The trader who receives the approval mail performs the approval process for the product, and the result of the application is transmitted to the server 200 (step S13).
[0084] If the trader performs the approval process, the trader can also edit the information about the product.
[0085] If the product is a custom-made item (an original product, not a ready-made product; the same applies below), the end purchaser and the seller immediately preceding them can edit the product information (first editing rights transfer process, second editing rights transfer process). In other words, the most downstream trader and the trader one level upstream can edit the product information. Specifically, this is as follows. It is also possible to allow only the most downstream trader to edit the product.
[0086] (When the product is an order product and the user of the first terminal 300 registers the seller first) As shown in FIG. 5, in this embodiment, when a user X of the first terminal 300 registers an ordered item a, the user X is able to edit information about the item a (has editing rights).
[0087] When the user X of the first terminal 300 sets and registers the seller of the product a (selling company C, downstream business partner), the seller (selling company C) can also edit the information of the product a.
[0088] If user X of the first terminal 300 sets and registers a seller (selling company C) and then sets and registers a purchaser of product A (purchasing company A), the purchaser (purchasing company A) cannot edit the information of product A.
[0089] When a buyer (selling company C) sets and registers the next buyer of product A (selling company D, a downstream business partner of selling company C), user X of the first terminal 300 will no longer be able to edit the information of product A.
[0090] In addition, if a supplier of product A (supplying company A, an upstream business partner) also sets and registers a supplier of product A (supplying company B, an upstream business partner of purchasing company A), that supplier (supplying company B) will not be able to edit the information of product A.
[0091] It should be noted that the user of the first terminal 300 will only be unable to edit the basic product information section 241, but will be able to edit the sales information section 242 and the purchase information section 243.
[0092] (When the product is an order item and the user of the first terminal 300 registers the place of purchase first) As shown in FIG. 6, in this embodiment, when a user Y of the first terminal 300 registers an ordered product b, the user Y is able to edit information about the product b (has editing rights).
[0093] When the user Y of the first terminal 300 registers the supplier (supplier company A) of the product b, the supplier (supplier company A) can edit the information of the product b.
[0094] If user Y of the first terminal 300 sets and registers the purchaser of product b (purchasing company A) and then sets and registers the seller of product b (selling company C), the seller (selling company C) will be able to edit the information of product b, but the purchaser (purchasing company A) will no longer be able to edit the information of product b.
[0095] If a seller of product b (selling company C) further sets and registers a seller of product b (selling company D), user Y of the first terminal 300 will no longer be able to edit the information of product b.
[0096] In addition, if a supplier of product b (supplier company A) also sets and registers another supplier of product b (supplier company B), that supplier (supplier company B) cannot edit the information of product b.
[0097] In other words, in this embodiment, if there are more traders beyond the buyer who is the trader, the user of the first terminal 300 cannot edit the information.
[0098] Furthermore, if the user of the first terminal 300 adds (sets and registers) a further trading partner (selling company D) beyond the selling partner (selling company C), the user of the first terminal 300 will only be unable to edit the product basic information section 241, but will be able to edit the sales information section 242 and the purchase information section 243.
[0099] Next, if the product is a ready-made product, the only person who can edit the product information is the manufacturer of the product. In other words, only the most upstream trader can edit the product information. Specifically, this is as follows. Note that it may be possible for the most upstream trader and the trader one level downstream to both be able to edit the product information.
[0100] (When the product is a ready-made product and the user of the first terminal 300 registers the seller first) As shown in FIG. 7, in this embodiment, when a user M of the first terminal 300 registers a ready-made product c, the user M is able to edit information on the product c (has editing rights).
[0101] When the user M of the first terminal 300 sets and registers a seller (selling company C), the selling company C cannot edit the information of the product c.
[0102] If user M of the first terminal 300 sets up and registers a seller (selling company C) and then a buyer (purchasing company A), the buyer (purchasing company A) will be able to edit the information of product c, and user M of the first terminal 300 will no longer be able to edit the information of product c.
[0103] If a sales destination (sales destination company C) further sets and registers a sales destination (sales destination company D) of product c, the sales destination (sales destination company D) cannot edit the information of product c.
[0104] If a purchasing source (purchasing company A) further sets up and registers a purchasing source (purchasing company B) for product c, purchasing company B, the previous purchasing source, will be able to edit the information for product c, but purchasing company A, the selling source, will no longer be able to edit the information for product c.
[0105] In other words, places that allow you to edit ready-made products are the best places to buy.
[0106] It should be noted that the user of the first terminal 300 will only be unable to edit the basic product information section 241, but will be able to edit the sales information section 242 and the purchase information section 243.
[0107] (When the product is a ready-made product and the user of the first terminal 300 registers the place of purchase first) As shown in FIG. 8, in this embodiment, when a user N of the first terminal 300 registers a ready-made product d, the user N is able to edit information on the product d (has editing rights).
[0108] When user N of the first terminal 300 sets and registers the place of purchase of product d (purchasing company A), the place of purchase (purchasing company A) becomes able to edit the information of product d, but user N of the first terminal 300 becomes unable to edit the information of product d.
[0109] If user N of the first terminal 300 sets and registers the purchaser (purchasing company A) of product d and then sets and registers the seller (selling company C), the seller (selling company C) cannot edit the information of product d.
[0110] If a sales destination (sales destination company C) further sets and registers a sales destination (sales destination company D), the previous sales destination (sales destination company D) cannot edit the information of product d.
[0111] If a purchasing source (purchasing company A) sets up and registers another purchasing source (purchasing company B), the previous purchasing source (purchasing company B) can edit the information of product d, but purchasing company A, which is the seller of product d, cannot edit the information of product d.
[0112] In other words, places that allow you to edit ready-made products are the best places to buy.
[0113] It should be noted that the user of the first terminal 300 will only be unable to edit the basic product information section 241, but will be able to edit the sales information section 242 and the purchase information section 243.
[0114] The application result sent to the server 200 is then sent to the user of the first terminal 300 and the trader (step S14). To be precise, the application result is sent to the first terminal 300, and to the trader's registered email address.
[0115] Information on products that have been approved for inclusion on the list as a result of the application is stored in the first unconfirmed list section 520.
[0116] As shown in FIG. 9, products stored in the first unconfirmed list section 520 are displayed on the first terminal by selecting the “Unconfirmed List” icon A1 in the “Purchase” column displayed on the first display section 310 of the first terminal 300.
[0117] Products displayed in the "Unconfirmed List" in the "Purchase" section have an "Approved" icon A2 and a "Rejected" icon A3.
[0118] If the "Approve" icon A2 is selected, the item is moved to the "Buying List".
[0119] That is, the product information is moved from the first unconfirmed list section 520 to the purchase list section 510.
[0120] (Ordering products) The user of first terminal 300 selects (clicks on) the product he or she wishes to purchase from the purchase list (product list) stored in purchase list section 510.
[0121] To open the "Shopping List" page, select the "Shopping List" icon B1.
[0122] Then, the user selects the purchased product from the "purchase list" page displayed on the first display unit 310 of the first terminal 300 (step S15).
[0123] Specifically, as shown in FIG. 10, the "Order" icon B2 in the product section of the "Purchase List" column is selected.
[0124] The product information in the "purchase list" displayed on the first display unit 310 can be narrowed down by the person in charge, the trader, etc. Also, the order of the products displayed can be rearranged by the product name, update date, alert date and time, etc.
[0125] When the "Order" icon B2 of a product displayed in the "Purchase List" is selected, an order email is sent from the server 200 to the trader, and an order receipt email is sent to the user of the first terminal 300 (step S16). To be precise, the order receipt email is sent to the first terminal 300.
[0126] As shown in FIG. 11, when the "Order" icon B2 of a product displayed in the "Purchase List" is selected, a "Confirm Order" page is displayed.
[0127] The user of the first terminal 300 checks whether the information on the "Confirm Order" page is correct and enters the necessary information. If the "Place Order" icon B3 located at the bottom is selected, the order is placed. If the "Back" icon B4 is selected, the user returns to the previous screen showing details of the purchased item.
[0128] (Accepting orders) When the user of the first terminal 300 accepts the ordered product, the server 200 transmits an acceptance email to the user of the first terminal 300 and the transactor (steps S17 and S18).
[0129] To be precise, the receipt email is sent to the first terminal 300, and to the email address registered with the trader. The registered email addresses include the email address of the person in charge at the trading company who is the trader. The same applies below.
[0130] In the "order list" displayed on first display unit 310 of first terminal 300, information on products ordered by the user of first terminal 300 is displayed.
[0131] To open the "Order List" page, select the "Order List" icon C1 shown in FIG.
[0132] As shown in FIG. 12, specifically, the “Order List” page displays product information such as order status, updates to order status, product name (product name), supplier, order quantity / delivery quantity, desired delivery date, order date and time, etc.
[0133] The sales section 600 includes a sales list section 610 for storing and displaying information on products available for sale as a list; a second unconfirmed list unit 620 for storing and displaying a list of information on products for sale that have not yet been confirmed by the user of the first terminal 300; and an order list section 630 for storing and displaying, as a list, information on products that the user of the first terminal 300 has ordered from a trader.
[0134] The sales list section 610 is a section for storing and displaying information on products that the user of the first terminal 300 wishes to sell as a list.
[0135] (Registering products for sale) As shown in Fig. 13, specifically, first, the user of the first terminal 300 registers the product to be sold and sets the seller (transactor) (step S21). Multiple sellers can be set. In the case of an ordered product rather than a ready-made product, it may be possible to set only the person who placed the order as the seller (transactor).
[0136] The registered product information is stored in the second unconfirmed list 620. That is, it is displayed on the "Unconfirmed List" page in the "Sales" section.
[0137] When a user of the first terminal 300 registers a product, that user can edit the product.
[0138] When the user of the first terminal 300 selects (clicks) the “Unconfirmed List” icon E1 in the “Sales” column displayed on the first display unit 310, the unconfirmed list is displayed on the first display unit 310.
[0139] Next, the server 200 transmits an approval email to the trader (sale destination) (step S22). Note that, although an approval email is used in this embodiment, a notification other than an email may be used.
[0140] The trader who received the approval mail performs the approval process for the product, and the result of the application is transmitted to the server 200 (step S23).
[0141] The application result sent to the server 200 is then sent to the user of the first terminal 300 and the trader (step S24). To be precise, the application result is sent to the first terminal 300, and to the trader's registered email address.
[0142] Information on the product for which the trader's approval has been obtained as a result of the application is stored in the sales list section 610.
[0143] (Product orders) An order is sent from the trader to the server 200 (step S25).
[0144] The user of the first terminal 300 selects the "Sales List" icon D1, and then selects the "Place Order" icon D2 for a product displayed in the sales list.
[0145] The product information in the "Sales List" displayed on the first display unit 310 can be narrowed down by the person in charge, the trader, etc. Also, the order of the products displayed can be rearranged by the product name, update date, alert date and time, etc.
[0146] When the “Order” icon D2 for a product displayed in the sales list is selected, an “Order Confirmation” page is displayed in the first display section 310.
[0147] The user of the first terminal 300 checks whether the information on the "Order Confirmation" page is correct and enters the necessary information. If the "Place Order" icon D3 located below is selected, the order is accepted. If the "Back" icon D4 is selected, the user returns to the previous screen showing the product details.
[0148] The server 200 sends an order receipt email to the user of the first terminal 300, and an order receipt email to the trader (step S26). To be precise, the order receipt email is sent to the first terminal 300, and to the trader's registered email address.
[0149] In the "order list" displayed on the first display unit 310 of the first terminal 300, information on products ordered by the user of the first terminal 300 is displayed.
[0150] To open the "Order List" page, select the "Order List" icon F1 shown in FIG.
[0151] As shown in FIG. 17, specifically, the “Order List” page displays product information such as order status, updates to order status, product name (product name), ordering destination, number of orders / number of deliveries, delivery date response, desired delivery date, order date and time, etc.
[0152] (Accepting orders) When the user of the first terminal 300 accepts the ordered product, the user inputs that fact into the server 200, and the server 200 transmits a receipt email to the user of the first terminal 300 and the transactor (step S27).
[0153] To be precise, the receipt email is sent to the first terminal 300, and to the trader's registered email address.
[0154] (Delivery of ordered products) When the user of the first terminal 300 delivers the ordered product to the trader, a delivery process is carried out in the server 200 (step S28).
[0155] The server 200 transmits a delivery notification email to the user of the first terminal 300 and the transactor (step S29).
[0156] The trader who receives the ordered product performs acceptance processing on the server 200 (step S30).
[0157] The server 200 transmits an acceptance notification email to the user of the first terminal 300 and the transactor (step S31).
[0158] To be precise, the delivery notification email and the acceptance notification email are sent to the first terminal 300, and to the email address registered with the trader.
[0159] In addition, if a seller (seller) stops selling to a trader, this will affect the final end user, so the seller (seller) cannot change or delete a trading partner.
[0160] The supplier list section 700 is used to display the company name, type of business, address, telephone number, fax number, email address, and so on of suppliers.
[0161] When the "supplier list" icon G1 displayed on the first display unit 310 of the first terminal 300 is selected, the supplier list is displayed.
[0162] Once the user inputs the necessary information into transaction management system 100, it is automatically displayed in the supplier list, making supplier management easy.
[0163] Member registration unit 800 is where member registration is performed. Specifically, after the user of first terminal 300 accesses the website of transaction management system 100 and performs provisional member registration, a provisional registration email is sent from server 200, and when the user of first terminal 300 receives the email, the user is officially registered as a member.
[0164] When the member is officially registered, a formal registration email is sent from the server 200 to the first terminal 300.
[0165] Then, the user of the first terminal 300 accesses the website of the transaction management system 100 and registers company information and employee information.
[0166] The product management unit 240 can set nicknames for products according to the seller or purchaser.
[0167] For example, as shown in Figure 20, when a sales company C places an order with company A, the order form for sales company C prints "store carrier bag (large)," and the order form for sales company B, which receives the order, prints "company C carrier bag large." The two parties are not aware of what the products are called.
[0168] This allows the user of the first terminal 300 to avoid confusing the products of the business partners.
[0169] The alert unit 220 transmits an alert to the user of the first terminal 300. Note that the alert unit 220 may be configured to transmit alert information to the first terminal 300, and the first terminal 300 may display the alert.
[0170] Specifically, when there is a risk of a shortage in stock, the product management unit 240 sends an alert to the first terminal 300. More specific details will be described later.
[0171] Furthermore, the product management unit 240 transmits an alert to the first terminal 300 based on the records of past deliveries or orders of products recorded by the product management unit 240. This will also be described in more detail later.
[0172] The parts expansion unit 230 registers the parts that make up a product as separate products and links them to the product to be sold.
[0173] This allows the user of the first terminal 300 to immediately place an order for parts for a product being sold by a trader when the user receives an order for the product.
[0174] As shown in FIG. 21, specifically, first, the user of the first terminal 300 registers a product and sets up sales of the registered product (step S41).
[0175] Next, the user of the first terminal 300 registers the parts that make up the product as separate products (part products), and registers the respective supplier companies (step S42).
[0176] Next, the user of the first terminal 300 sets these part products in the part expansion unit 230 (step S43). This makes it possible to link the part products to the product.
[0177] When an order for a product is received, the part expansion section 230 displays the part product on the first display section 310 (step S44).
[0178] This allows the user of the first terminal 300, when an order for a product is placed, to immediately check the part products registered in the "parts expansion" and place an order.
[0179] (If you want to secure stock) The product management unit 240 manages product inventory, and the alert unit 220 transmits an alert to the first terminal 300 according to the number of products in stock.
[0180] As shown in FIGS. 22 and 23, first, the user of the first terminal 300 registers the inventory quantity of the product in the product management section 240 (step S51).
[0181] Next, the product management unit 240 records inventory changes due to product orders and deliveries from customers (step S52).
[0182] The product management unit 240 also records inventory changes due to orders and deliveries of products (including parts products) to suppliers (step S53).
[0183] Then, when it is determined from the history of past shipments to sellers that the stock quantity will be insufficient, the alert unit 220 transmits an alert email to the user of the first terminal 300 (step S54).
[0184] Furthermore, the product management unit 240 causes the alert unit 220 to transmit an alert to the first terminal 300 based on the records of past deliveries or orders of products that the product management unit 240 records.
[0185] The alert unit 220 issues an alert when, after a product has been delivered, the stock quantity is insufficient for the next product to be delivered.
[0186] Furthermore, the alert unit 220 issues an alert taking into consideration the number of days (delivery date) from ordering the product to delivery of the product.
[0187] For example, if the next order is likely to be placed earlier than the delivery date, the alert unit 220 may issue an alert before it is determined that there will be a shortage of stock.
[0188] (If not in stock) If the item is not in stock, the date for the alert is calculated based on past order history.
[0189] In other words, the system calculates when the currently ordered quantity will be sold out based on past order history, and determines the alert date from that.
[0190] Specifically, for example, as shown in Tables 1 and 2 below, the alert unit 220 calculates the number of days between intervals and the consumption amount from the delivery date and time and the number of deliveries.
[0191] In this embodiment, the alert date is determined based on the delivery date and time and the number of deliveries, but the alert date may also be determined based on the order date and time and the number of orders.
[0192] [Table 1]
[0193] [Table 2]
[0194] Specifically, there are 20 days between August 21, 2019 and September 10, 2019, and if you divide the delivery quantity of 2,000 on August 21, 2019 by 20 (days), the daily consumption becomes "100".
[0195] Similarly, the number of days between July 22, 2019 and August 21, 2019 is 30 days, and if we divide the delivery quantity of 2,100 on July 22, 2019 by 30 (days), the daily consumption becomes "70".
[0196] Similarly, the number of days between June 12, 2019 and July 22, 2019 is 40 days, and if we divide the delivery quantity of 2,300 on June 12, 2019 by 40 (days), the daily consumption becomes "57.5".
[0197] Similarly, the number of days between May 18, 2019 and June 12, 2019 is 25 days, and if you divide the delivery quantity of 2,000 on May 18, 2019 by 25 (days), the daily consumption becomes "80".
[0198] Therefore, from Table 1 the daily consumption amounts are 100, 70, 57.5, and 80.
[0199] Then, as shown in Table 3, the alert unit 220 calculates the maximum, minimum, and average values of the consumption amount per day.
[0200] In other words, of the four numbers above, the maximum value is 100 and the minimum value is 57.5. And the average value is (100+70+57.5+80)÷4=76.875.
[0201] [Table 3]
[0202] Then, the alert unit 220 calculates the alert sending date taking into consideration the number of days it will take to consume the latest delivery quantity (September 10, 2019 in this embodiment), "2500", and the lead time.
[0203] That is, if your consumption is 100, it will take you 25 days to consume 2500. Similarly, if your consumption is 76.875, it will take you 32 days to consume 2500. Similarly, if your consumption is 57.5, it will take you 43 days to consume 2500.
[0204] [Table 4]
[0205] Therefore, as shown in Table 4, the alert unit 220 determines the alert transmission dates to be September 25, 2019, October 2, 2019, and October 13, 2019.
[0206] Note that the alert unit 220 may set, for example, a cycle month (how many months between alerts) or a cycle day (how many days between alerts) in addition to the automatic calculation described above.
[0207] The alert unit 220 may also be configured to transmit alerts on multiple fixed months or fixed days (for example, the alert dates may be set to April 1, 2020, August 1, 2020, and December 1, 2020).
[0208] The server communication unit 250 is for communicating with the first terminal 300 and the second terminal 400 .
[0209] The first terminal 300 includes a first display unit 310 that displays product information stored in the server storage unit 210 of the server 200 as described above, and The first communication unit 320 enables communication with the server 200.
[0210] As shown in FIGS. 9 to 12 and 14 to 17, first display unit 310 displays a screen for operation by the user of first terminal 300.
[0211] The first communication unit 320 is capable of communicating with the server 200. Specifically, the first communication unit 320 communicates with the server communication unit 250 of the server 200.
[0212] The second terminal 400 is a management terminal for editing the contents of the server 200. The second terminal 400 includes a second display unit 410 for displaying the contents of the server 200, and a second communication unit 420 that enables communication with the server 200.
[0213] The second display unit 410 displays the contents of the server 200 and allows the contents to be edited.
[0214] The second communication unit 420 is capable of communicating with the server 200. Specifically, the second communication unit 420 communicates with the server communication unit 250 of the server 200.
[0215] It should be noted that second terminal 400 and first terminal 300 may be the same.
[0216] The present invention can be implemented in various forms with improvements, modifications, or variations without departing from the spirit of the invention. [Explanation of symbols]
[0217] 100...Transaction management system 200...Server 220…Alert section 230…Parts deployment section 240…Product Management Department 241…Product Basic Information Department 242…Sales Information Department 243…Purchase Information Department 250…Server communication section 300…First terminal (terminal) 310...Display section (screen) 400…Second terminal (terminal) 500…Purchase 600…Sales Department 700…Customer List Section 800…Member Registration Department
Claims
1. A transaction management system for placing and receiving orders for products using a server and a terminal capable of communicating with the server, The server, A product management unit that records the delivery or order history of the product; an alert unit that transmits an alert to the terminal based on a delivery or order history of the product recorded in the product management unit; the alert unit determines an alert date based on a record of past deliveries or orders of the product recorded by the product management unit, Calculating the number of days between deliveries of the product from the delivery date and time of the product and the immediately preceding delivery date and time of the product; Calculate the daily consumption by dividing the number of deliveries of the product immediately before by the number of days between deliveries; Calculate the number of days to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the maximum consumption amount calculated multiple times; The transaction management system sets the alert date to the latest delivery date of the product plus the number of days it takes for the calculated delivery quantity of the product to be consumed.
2. The alert unit calculates the number of days to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the minimum value of the consumption amount calculated multiple times, 2. A transaction management system according to claim 1, wherein the alert date is set to the latest delivery date of the product plus the number of days it takes for the calculated number of delivered products to be consumed.
3. The alert unit calculates the number of days to consume the delivery quantity of the product based on an average consumption amount calculated based on a plurality of the latest delivery quantities of the product, 2. A transaction management system according to claim 1, wherein the alert date is set to the latest delivery date of the product plus the number of days it takes for the calculated number of delivered products to be consumed.
4. A transaction management program that causes a server to place and receive orders for products using a server and a terminal that can communicate with the server, A product management process for recording a delivery or order history of the product in the server; causing the server to execute an alert process of transmitting an alert to the terminal based on a delivery or order history of the product recorded by the product management process; The alert process determines an alert date based on a record of past deliveries or orders of the product recorded in the product management process, The alert process calculates a number of days between deliveries of the product from a delivery date and time of the product and a delivery date and time of the product immediately before the delivery date and time of the product, Calculate the daily consumption by dividing the number of deliveries of the product immediately before by the number of days between deliveries; Calculate the number of days to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the maximum consumption amount calculated multiple times; A transaction management program in which the latest delivery date of the product plus the number of days it takes to consume the calculated delivery quantity of the product is set as the alert date.
5. The alert process calculates the number of days to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the minimum value of the consumption amount calculated multiple times, 5. A transaction management program according to claim 4, wherein the alert date is set to the latest delivery date of the product plus the number of days it takes for the calculated delivery quantity of the product to be consumed.
6. A transaction management method for placing and receiving orders for products using a server and a terminal capable of communicating with the server, comprising the steps of: a product management step in which the server records a delivery or order history of the product; an alert step of the server transmitting an alert to the terminal based on the delivery or order history of the product recorded in the product management step; The alert step determines an alert date based on a record of past deliveries or orders of the product recorded in the product management step, The alert step calculates a number of days between deliveries of the product from a delivery date and time of the product and a delivery date and time of the product immediately before the delivery date and time of the product, Calculate the daily consumption by dividing the number of deliveries of the product immediately before by the number of days between deliveries; Calculate the number of days to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the maximum consumption amount calculated multiple times; A transaction management method in which the latest delivery date of the product is added to the number of days it takes for the calculated delivery quantity of the product to be consumed as the alert date.
7. The alert step calculates the number of days required to consume the latest delivery quantity of the product by dividing the latest delivery quantity of the product by the minimum value of the consumption amounts calculated multiple times; The transaction management method according to claim 6, wherein the alert date is set to a date obtained by adding the number of days required for the calculated number of delivered items to be consumed to the latest delivery date of the item.
Citation Information
Patent Citations
Stock quantity display method and stock quantity adjusting method of article
JP2002087529A
Inventory prediction and management device and system as well as inventory prediction and management method
JP2002145413A
Inventory management system
JP2002236730A
Article ordering system and method
JP2009129092A
Order placement / reception system and order placement / reception acceptance server
JP2014074975A
