Trade Management System
The transaction management system addresses inefficiencies in managing building exterior product transactions by using dual management servers and a database to automate quote creation and tracking, enhancing user experience and transaction efficiency.
Patent Information
- Application Number
- JP2024117584
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-04-16
AI Technical Summary
Existing systems for managing transactions between sellers and customers for building exterior products are inefficient, as they rely on verbal communication, emails, and faxes, leading to delays in sharing transaction details, and electronic commerce systems are inconvenient due to varying product prices based on customer-specific conditions.
A transaction management system that includes a first management server for sellers and a second management server for customers, utilizing a database to associate customer identification with transaction information, allowing for automated creation and display of customer-specific quotes, including profit margins, and enabling easy management of product transactions through a user-friendly interface.
Facilitates efficient and user-friendly management of product transactions by automating the creation of customer-specific quotes, reducing the need for manual meetings and document preparation, and ensuring accurate tracking of transaction details for both sellers and customers.
Smart Images

Figure 0007593700000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a transaction management system. [Background technology]
[0002] Generally, transactions between a seller such as a trading company and a customer such as a construction company regarding products related to the exterior of a building are conducted as follows. First, when the seller receives an offer from the customer, a meeting is held to discuss the planned contents of the transaction (product to be purchased, quantity to be purchased, etc.). The seller then prepares documents (a confirmation of the meeting contents and an estimate) based on the items agreed upon in the meeting, and presents these documents to the customer. If the seller is satisfied with the transaction contents written in the documents, the seller officially orders the product. The transaction is then completed when the product is delivered to the location specified by the customer (the construction site or construction company).
[0003] In recent years, electronic commerce sites have come into practical use (for example, Patent Document 1). On the electronic commerce site, products selected by sellers are displayed together with their prices. A purchaser selects the product he or she wants from among the products on the electronic commerce site and purchases it. The product thus purchased is delivered to the location (usually the purchaser's home) selected on the electronic commerce site. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2019-21300 A Summary of the Invention [Problem to be solved by the invention]
[0005] In exterior construction work, customers such as construction companies set the schedule for construction work using the product based on the delivery schedule of the product. Therefore, customers want to understand the actual transaction details of the product they are purchasing as soon as possible. In this regard, in the general product transactions described above, information is communicated verbally during meetings, or by e-mail or facsimile, which creates the problem that it takes time for the transaction details to be communicated between the seller and the customer.
[0006] Here, it is conceivable that all transactions related to exterior products can be carried out using an e-commerce site. Since the e-commerce site stores the history of transaction details, customers can check the transaction details through the history section of the e-commerce site. However, in product transactions between businesses (so-called BtoB), various conditions such as the product delivery quantity, delivery time, and past transaction records are taken into consideration, so the product sales price varies depending on the customer. Therefore, simply using an e-commerce system would not allow for such sales price setting, making the system extremely difficult to use for both sellers and customers. [Means for solving the problem]
[0007] An embodiment of an apparatus for solving the above problems will be described. [Aspect 1] A transaction management system for managing transaction details of products related to exteriors, comprising: a storage unit for storing a database in which transaction information data, which associates identification information set for each customer with transaction information of the customer corresponding to the identification information, and product data related to information on the products, are stored; a first management server for managing the transaction information data and the product data as data related to transaction details of the product by the seller of the product; and a second management server for managing the transaction information data and the product data as data related to transaction details of the product by the customer, the transaction information data including profit data indicating a profit share of the customer for the product, the second management server having a usage permission unit for permitting the external terminal to use the database when the identification information is input through the operation of an external terminal connected via a communication network, and a usage permission unit for permitting use of the database by the external terminal when the identification information is input. a page display unit that displays on the external terminal the transaction information page, when the identification information is input, the transaction information page displaying the transaction information page in which a quotation request unit that is operated when requesting a quotation for the product is set, a quotation request storage unit that creates quotation request data for requesting a quotation for the product and stores the quotation request data in the database when the quotation request unit is operated, and a quotation output unit that creates a quotation for the product in an amount including a profit for the customer based on the quotation data and the profit data and outputs the quotation when quotation data corresponding to the quotation for the product indicated by the quotation request data is created by the first management server through operation of an operation terminal connected to the first management server and the quotation data is stored in the database and when the quotation request unit is operated.
[0008] According to the above configuration, a quotation for a product can be created using the price of the product included in the quotation data, i.e., the product purchase price for the customer, and the customer's profit for the same product indicated by the profit data, i.e., the amount added by the customer to the product purchase price. Therefore, an estimate including the customer's profit can be easily created without the need for cumbersome tasks such as holding a meeting between the seller and the customer and creating documents based on the items agreed upon in the meeting. This estimate can then be presented to a third party other than the seller (e.g., the client). Thus, according to the above configuration, the transaction management system can be made easy to use for both the seller and the customer. Effect of the Invention
[0009] According to the present invention, the transaction management system can be made easy to use for both sellers and customers. [Brief description of the drawings]
[0010] [Figure 1] 1 is a schematic diagram of an embodiment of a transaction management system. [Diagram 2] 1 is a schematic diagram conceptually showing the structure of data stored in a database. [Diagram 3] FIG. 13 is a diagram showing the display contents of a login screen on the home screen. [Figure 4] FIG. 13 illustrates the steps for performing a task of obtaining a customer-form quote. [Diagram 5] FIG. 13 is a diagram showing the display contents of a customer list page. [Figure 6] FIG. 13 is a diagram showing the display contents of a quote request page. [Figure 7] FIG. 13 is a diagram showing the display contents of a quote inquiry page. [Figure 8] FIG. 13 is a diagram showing the display contents of a quote input page. [Figure 9] FIG. 13 is a diagram showing the display contents of a new order page. [Figure 10] 13 is a flowchart showing an execution procedure of a calculation and display process. [Figure 11] FIG. 13 is a diagram showing the display contents of a process chart page. [Figure 12] FIG. 13 is a diagram showing the display contents of a specification selection page. [Figure 13] FIG. 13 is a diagram showing the display contents of a specification confirmation page. [Figure 14] FIG. 13 is a diagram conceptually illustrating an example of the display content of a product display section. [Figure 15] FIG. 13 is a diagram showing the display contents of a catalog page. [Figure 16] FIG. 13 is a diagram showing the display contents of a delivery date notification page. [Figure 17] FIG. 13 is a diagram showing the display contents of a delivery instruction page. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] An embodiment of the transaction management system will be described below. The transaction management system of this embodiment is introduced by a sales trading company that sells products related to building exteriors, and is a system for managing various information related to product transactions between the sales trading company and its customers (e.g., construction companies).
[0012] <Outline of the transaction management system> As shown in FIG. 1, a transaction management system 10 of this embodiment includes a first management server 11, a second management server 12, and a database server 13.
[0013] <First Management Server 11> The first management server 11 is for managing various data stored in the database server 13 as data related to the transaction details of merchandise by sellers.
[0014] The first management server 11 includes a central processing unit (so-called CPU) and a storage device. The storage device is configured with storage such as a hard disk drive (HDD) or a solid state drive (SSD). The storage device stores applications and various software used to manage the transaction details of products. The first management server 11 executes various processes related to the management of the transaction details of products by sellers based on the applications and various software stored in the storage device. The first management server 11 has a function of a web server and a function of an application server.
[0015] The first management server 11 has, as functional units, a shipping request data creation unit 111 and a shipping request data transmission unit 112. The functions of the shipping request data creation unit 111 and the shipping request data transmission unit 112 will be described later.
[0016] The first management server 11 can be connected to external devices such as a facsimile of a product manufacturer (a so-called manufacturer) or a customer's smartphone via a communication network 16 such as the Internet network or a mobile phone network. The first management server 11 can transmit and receive information to and from the external devices. In detail, the first management server 11 can communicate with the external devices of the manufacturer and the customer by facsimile, e-mail, social networking service (SNS), etc. Various data is transmitted and received between the first management server 11 and the external devices in accordance with a known communication protocol.
[0017] <Operation terminal 14> An operation terminal 14 is connected to the first management server 11. The operation terminal 14 is configured by a computer having an input device 15 (e.g., a mouse, a keyboard, or a touch panel) for performing input operations. The operation terminal 14 is intended for use by an administrator of the transaction management system 10 (e.g., an employee of a sales trading company). By operating the operation terminal 14, mainly data related to the content of product transactions by sellers, among various data stored in the database 20, is updated.
[0018] <Second management server 12> The second management server 12 is for managing various data stored in the database server 13 as data relating to the contents of transactions of products by customers.
[0019] The second management server 12 includes a central processing unit and a storage device. The storage device is configured with storage such as a hard disk drive or a solid state drive. The storage device stores applications and various software used to manage the details of product transactions. The second management server 12 executes various processes related to the management of the details of product transactions by customers based on the applications and various software stored in the storage device. The second management server 12 has a function of a web server and a function of an application server.
[0020] The second management server 12 has, as its functional parts, a usage permission part 121, a page display part 122, a quotation request storage part 123, a quotation output part 124, a nameplate order request transmission part 125, a nameplate order completion display part 126, and an earliest delivery date display part 127. The second management server 12 also has, as its functional parts, an order request transmission part 128, an order completion display part 129, a schedule display part 12A, a schedule postponement part 12B, a construction-included cost display part 12C, and a delivery instruction part 12D. The functions of these functional parts will be described later.
[0021] <External Terminal 17> The second management server 12 is connectable to an external terminal 17 via a communication network 16 such as a mobile phone network or the Internet. For example, the external terminal 17 is configured by a user terminal such as a personal computer, a tablet terminal, or a smartphone. The second management server 12 is capable of transmitting and receiving information to and from the external terminal 17. Various data is transmitted and received between the external terminal 17 and the second management server 12 in accordance with a known communication protocol.
[0022] <Database Server 13> The database server 13 stores a database 20. The database 20 stores various data related to the content of product transactions between sellers and customers. The various data include transaction information data 21, product data 22, seller data 23, and manufacturer data 24. In this embodiment, the database server 13 corresponds to a storage unit.
[0023] <Transaction information data 21> The transaction information data 21 is data that associates identification information (customer ID) set for each customer with the transaction information of the customer corresponding to the identification information.
[0024] As conceptually shown in FIG. 2, the transaction information data 21 includes the following data: [Customer Data 25] The customer data 25 (A1, A2, etc.) is data on identification information (customer code, login ID, and login password) determined for each customer, and data on customer information (including contact information such as address, telephone number, and email address). Note that the identification information is set by the sales trading company for customers with whom the company trades products.
[0025] [Purchased Product Data 26] The purchased product data 26 (B1, B2, . . . ) is data relating to products purchased by the customer (model number, manufacturer, name, color, price, etc.). "Delivery destination data 27" Delivery destination data 27 (C1, C2,...) is data on the delivery destination of the product purchased by the customer, more specifically, on the delivery location and delivery method. Data on the delivery location includes "your company", "land yard", "site", "- (other)", etc. "Your company" indicates that the product will be delivered directly to the customer (for example, a construction company). "Land yard" indicates that the delivery location will be the customer's material storage site. "Site" indicates that the delivery location will be the site where the customer will install the product. "-" indicates that the delivery location will be another location. Data on the delivery method includes "normal", "manufacturer pick-up", "store delivery", "manufacturer direct delivery", "other", etc. "Normal" indicates that the seller delivers the product. "Manufacturer pick-up" indicates that the customer picks up the product directly from the manufacturer of the product. "Store delivery" indicates that the product will be delivered at the sales trading company to which the sales representative belongs (more specifically, the office, warehouse, or logistics center of the sales trading company). "Direct from manufacturer" means that the product is shipped directly from the manufacturer to the customer.
[0026] [Quotation Request Data 28] The quotation request data 28 (D1, D2, . . . ) is data created by the second management server 12 when a customer requests a quotation for a product by operating the external terminal 17.
[0027] [Estimate Data 29] The estimate data 29 (E1, E2, . . . ) is data created by the first management server 11 based on the estimate request data 28 through the operation of the operation terminal 14 connected to the first management server 11.
[0028] [Sales Price Rate Data 30] The sales price rate data 30 (F1, F2,...) is the sales price rate of the product by the customer, more specifically, the value obtained by dividing the sales price PA of the product by the purchase price PB of the product by the customer, and multiplying the result by "100" (PA / PB x 100). As the sales price rate data 30, values determined by the customer for each product are stored in advance in the database 20. In this embodiment, the sales price rate data 30 corresponds to profit data indicating the customer's profit share for the product.
[0029] [Buying rate data 31] Buying rate data 31 (G1, G2,...) is the buying rate of a product by a seller, more specifically, the value obtained by dividing the selling price PC of the product by the purchasing price PD of the product by the same seller and multiplying the result by "100" (PC / PD x 100). As buying rate data 31, values determined by the seller for each product are stored in advance in database 20.
[0030] [Order request data 32] The order request data 32 (H1, H2,...) is data created by the second management server 12 when a customer requests an order for a product registered in the quotation input page 60 described below through the operation of the external terminal 17. The order request data 32 is created by the second management server 12, for example, when a customer requests an order for a product based on the quotation data 29 through the operation of the external terminal 17.
[0031] [First data 33] The first data 33 (I1, I2,...) is data that defines the relationship between the product, the manufacturer of the product, the delivery destination of the product, and the delivery route of the product. The first data 33 is preset by the seller and updated at appropriate times.
[0032] [Second Data 34] The second data 34 (J1, J2,...) is data that defines the relationship between the manufacturer of the product and the shortest date and time required from ordering the product to shipping the product to the warehouse. The second data 34 is preset by the seller based on information on product shipment transmitted by the manufacturer of the product, and is updated at appropriate times.
[0033] [Third Data 35] The third data 35 (K1, K2,...) is data that defines the relationship between the warehouse and the operation date and time of the warehouse. The third data 35 is preset by the seller based on the warehouse operation calendar defined by the seller, and is updated at appropriate times.
[0034] [Fourth data 36] The fourth data 36 (L1, L2,...) is data that defines the relationship between the delivery destination of the product and the date and time required for the product to be delivered from the warehouse to the delivery destination. The fourth data 36 is preset by the seller based on the delivery date calendar of the delivery destination obtained from the customer, and is updated at appropriate times.
[0035] [Fifth data 37] The fifth data 37 (M1, M2,...) is data that defines the relationship between the product, the layout including the length dimension of the product, multiple components that realize the layout, the prices of the components, the work content that realizes the layout, and the cost of the work content. Note that the fifth data 37 is preset by the sales trading company based on information about the product transmitted by the product manufacturer, and is updated at appropriate times.
[0036] [Property Data 38] The property data 38 (N1, N2,...) is data related to the property where the product is installed. The property data 38 includes the property name (e.g., Mr. A's house in Ginan Town), address, and deliverable vehicle model corresponding to the product purchased by the customer.
[0037] [Nameplate Ordering Request Data 39] Nameplate ordering request data 39 is data created by the second management server 12 when a customer requests an order for a nameplate through the operation of the external terminal 17.
[0038] [Shipping request data 40] The shipping request data 40 is data to be sent to a product manufacturer to request the shipping of a catalog (for example, document data to be sent by facsimile or e-mail). The shipping request data 40 is created by the first management server 11 when a customer requests the ordering of a catalog by operating the external terminal 17.
[0039] [Delivery possible data 41] The delivery possible data 41 is data indicating that the product purchased by the customer is in a state where it can be delivered to the customer. The delivery possible data 41 is created through the operation of the operation terminal 14 by the sales trading company's staff when the target product is delivered to the warehouse, and is stored in the database 20.
[0040] [Delivery Instruction Data 42] The delivery instruction data 42 is data created by the second management server 12 when a customer issues an instruction for delivery of a product that is ready for delivery through the operation of the external terminal 17.
[0041] [Layout information 43] Layout information 43 is information about the layout of products. The layout information defines the length of the products, the structure of the corners, etc. The layout information 43 is information input by the customer through the operation of the external terminal 17.
[0042] <Product data 22> Product data 22 is data related to information on products handled by the seller. Product information includes the manufacturer, name, model, purchase price, details of work required for installing the product, costs of the work, etc. Product data 22 is preset by the seller based on product information provided by the product manufacturer, and is updated at appropriate times.
[0043] <Seller Data 23> The seller data 23 is data regarding information about the seller (including contact information such as address, telephone number, and email address).
[0044] <Manufacturer Data 24> The manufacturer data 24 is data regarding information about the manufacturer (including contact information such as address, telephone number, facsimile number, and email address).
[0045] <Operation of the transaction management system 10> In this embodiment, through the seller's operation of the operation terminal 14 and the customer's operation of the external terminal 17, the seller and the customer can each use the data in the database 20 in a manner suitable for their own product management to manage the details of the product transaction.
[0046] The following describes the operations of sellers and customers managing product transaction details using the transaction management system 10 of this embodiment. <Work to authorize use of the transaction management system 10> First, the process of permitting a customer to use the transaction management system 10 will be described with reference to FIG.
[0047] When a customer operates the external terminal 17 to access the transaction management system 10 (more specifically, the second management server 12), a home screen 200 shown in FIG.
[0048] As shown in FIG. 3, if the customer has not logged in to the transaction management system 10, a login screen is displayed on the home screen 200. When the customer starts using the transaction management system 10, the customer inputs a "customer ID" on the home screen 200. Specifically, a login ID is input in an ID input field 201 on the home screen 200, and a login password is input in a password field 202, and then a login button 203 is operated. When this customer ID is authenticated by the usage permission unit 121 of the second management server 12, the external terminal 17 is permitted to use the database 20. As a result, various information related to the product transaction linked to the customer ID input at this time (specifically, a transaction information page including the information) is permitted to be displayed on the external terminal 17 thereafter. In this way, the second management server 12 includes a page display unit 122 as a functional unit. The page display unit 122 has a function of displaying a transaction information page on the external terminal 17.
[0049] In the transaction management system 10 of this embodiment, a menu field 210 is set in the transaction information page (including the home screen 200) displayed on the external terminal 17. In the menu field 210, various operation buttons are displayed, such as a home button 211, a customer ledger button 212, an allocation table button 213, a request / history button 214, a property management button 215, a schedule button 216, an inventory button 217, and a guide button 218. In addition, the menu field 210 also displays a catalog button 219, an inquiry button 220, and the like. By logging in to the transaction management system 10, the customer can operate these operation buttons 211 to 220. When the home button 211 in the menu field 210 is operated, the above-mentioned home screen 200 is displayed on the external terminal 17.
[0050] <Printing out customer-formatted estimates> Next, the operation of obtaining a customer-specific estimate will be described with reference to FIGS. The transaction management system 10 of the present embodiment allows a customer to obtain a custom-made quotation.
[0051] As shown in Fig. 4, when obtaining a customer-specific quotation, first, quotation request data 28 for requesting a product quotation is created through operation of external terminal 17 (S101), and the quotation request data 28 is stored in database 20 (S102). This operation is specifically executed as follows.
[0052] 5, the transaction information page displayed on the external terminal 17 includes a customer list page 50. The customer list page 50 is one of the transaction information pages that displays transaction information of a customer corresponding to the input identification information when use of the database 20 is permitted by the usage permission unit 121, which is one of the functional units of the second management server 12.
[0053] The customer list page 50 is configured with a customer search section 51 for inputting information for customer search, and a customer display section 52 for displaying the results of the customer search. By inputting a keyword (construction site or customer name) into the customer search section 51 and operating a search button 53 of the customer search section 51, the results of the customer search are displayed in the customer display section 52. In the example shown in FIG. 5, six customer columns 54 are displayed in a list in the customer display section 52 of the customer list page 50. In this embodiment, the customer who operates the external terminal 17 corresponds to a primary customer (e.g., a construction company), and the customer displayed in the customer display section 52 corresponds to a secondary customer (e.g., a client) who orders the product.
[0054] Each customer field 54 is provided with an expand / close button 55. By operating the expand / close button 55, the customer field 54 can be expanded to display details or closed to display only the property name. In the example shown in Fig. 5, one of the six customer fields 54 is in the expanded state.
[0055] Further, a quote request button 56 is set in each customer column 54. The quote request button 56 is an operation section that is operated when creating data for requesting a quote (the quote request data 28).
[0056] When a customer obtains a customer-formatted quotation, first, the quotation request button 56 on the customer list page 50 is operated. As a result, a quotation request page 65, which is one of the transaction information pages, is displayed on the external terminal 17, as shown in Fig. 6. Then, when the customer operates this quotation request page 65, the quotation request storage unit 123, which is one of the functional units of the second management server 12, creates quotation request data 28 for requesting a quotation for the product, and stores the quotation request data 28 in the database 20.
[0057] <Request for quotation page 65> The quotation request page 65 includes a summary input section 66 for inputting the details of the quotation to be requested, and a registration button 67 .
[0058] The overview input section 66 includes a project name input field 661 for entering the project name, a desired date input field 662 for entering the desired date for submitting an estimate, a request content input field 663 for writing the request content in text, and an attachments field 664 for attaching documents such as construction drawings.
[0059] <Customer Request for Quote page 65 operation> The customer operates the external terminal 17 to input information into the work name input field 661, the desired date input field 662, the request content input field 663, and the attachment field 664 on the quotation request page 65, and also operates the register button 67. As a result, quotation request data 28 requesting a quotation for the product is created, and the quotation request data 28 is stored in the database 20. The quotation request data 28 includes data on the outline of the quotation (more specifically, the data entered in each field 661 to 664). In this embodiment, the quotation request page 65 including the register button 67 corresponds to the quotation request section.
[0060] <Creation of quotation data 29 by seller> 4, when the quotation request data 28 is stored in the database 20 (S102), a signal SG is output from the second management server 12 to the first management server 11 to notify that a quotation request has been received from the customer (S103). When the first management server 11 receives this signal SG (S104), the seller becomes aware that a quotation request has been received.
[0061] Then, the seller creates quotation data 29, which is data corresponding to the quotation for the product indicated in the quotation request data 28, through operation of the operation terminal 14 connected to the first management server 11 (S105), and stores the quotation data 29 in the database 20 (S106).
[0062] <Confirmation of quotation data 29 by customer> Once the quotation data 29 has been stored in the database 20 (S106), the first management server 11 notifies the customer's external device by email or SNS that the seller has completed creating the quotation (S107). When the customer receives the email or SNS on the customer's external device, the customer is made aware that the seller has completed creating the quotation. The customer then operates the external terminal 17 connected to the second management server 12 (S108) to confirm the quotation data 29 created by the seller (S109). This operation is specifically executed as follows.
[0063] 7, the transaction information page displayed on the external terminal 17 includes a quote inquiry page 80. The quote inquiry page 80 has a quote inquiry section 81 for inputting a quote inquiry, and a quote list display section 82 for displaying the results of the quote inquiry.
[0064] By inputting a keyword (e.g., quotation or quotation request, quotation request date, quotation request status, customer name, etc.) in this quotation inquiry section 81 and operating a search button 83 in the quotation inquiry section 81, the search results for quotation or quotation request are displayed in the quotation list display section 82. In the example shown in Fig. 8, three quotations are displayed in a list in the quotation list display section 82 of the quotation inquiry page 80.
[0065] An edit button 84 is set in the quotation list display section 82 to be operated when editing a quotation. When obtaining a quotation in a customer format, the edit button 84 corresponding to the quotation to be obtained is operated. As a result, the quotation input page 60 (FIG. 8) is displayed on the external terminal 17.
[0066] As shown in FIG. 8, the quotation input page 60 has a product selection field 63. When obtaining a customer-format quotation, a "Reflect quotation request details" button 793 in the product selection field 63 is operated. This causes the contents of the quotation data 29 created by the seller to be reflected in the product selection field 63. In more detail, the displayed contents of the product selection field 63 are updated to the contents defined in the quotation data 29. Note that FIG. 8 shows an example of the state in which the contents of the quotation data 29 are reflected in the product selection field 63.
[0067] The customer checks the contents of the quotation prepared by the seller based on the contents displayed in the product selection field 63. If the customer wishes to obtain a quotation in a customer format, the customer selects "Customer" in the quotation layout selection area 62. If the customer wishes to include major items in the quotation, the customer checks the check box 621. After performing these operations, the customer operates the registration button 72 to register the quotation contents.
[0068] The quote input page 60 will be described in detail below. The quotation input page 60 includes a summary input section 61 for inputting the details of the quotation to be requested, a quotation layout selection section 62 for selecting the output format of the quotation, and a product selection section 63 for selecting the product.
[0069] The overview input section 61 includes a project name input field 611 for inputting the project name, a desired date input field 612 for inputting the desired date for submitting an estimate, and an attachment field 613 for attaching documents such as construction drawings.
[0070] The quotation layout selection section 62 is an input section in a pull-down format. Selection items in the quotation layout selection section 62 include "Customer" for selecting a customer style, "Dealer" for selecting a dealer style, "House manufacturer" for selecting a house manufacturer style, and "Other" for selecting other styles. Near the quotation layout selection section 62, a check box 621 is set together with the character string "Print major items." When entering major items, which will be described later, in the quotation, a check mark is placed in this check box 621. In this embodiment, the quotation layout selection section 62 corresponds to an output style selection section.
[0071] <Product selection column 63> The product selection field 63 includes a main item field 70, a medium item field 71, a sub-item field (not shown), a register button 72, and a back button 73. In this embodiment, the product selection field 63 corresponds to a product selection unit operated to select a product.
[0072] <Major item column 70> The major item field 70 displays major item display fields 74 that display major items related to the content selected in the product selection field 63. In the example shown in Fig. 8, three major item display fields 74 are displayed. When the quotation data 29 is reflected, the major item display fields 74 display major items related to the content of the quotation data 29 (information on the product to be quoted).
[0073] In the major item display field 74, a major item selection section 75, a total amount field 76, a details button 77, etc. are set as display items. The major item selection section 75 is an input section for inputting major items (text information) regarding the content selected in the product selection field 63. The total amount field 76 is a display field that displays the cost (amount) for the major item selected in the major item selection section 75. The details button 77 is an operation section that is operated when displaying details (more specifically, the medium item field 71 and the minor item field) of the major item selected in the major item selection section 75 in the product selection field 63.
[0074] An add line button 78 is set in the main item column 70. The add line button 78 is an operation section that is operated when adding a main item display column 74. <Medium item column 71> The medium item column 71 displays a medium item display column 79 that displays medium items for the product selected in the product selection column 63. In the example shown in FIG. 8, three medium item display columns 79 are displayed. When the quotation data 29 is reflected, the medium item display column 79 displays medium items for the contents of the quotation data 29 (information on the product to be quoted). The medium item display column 79 has various display items set therein, such as a selection check section 790, as described below.
[0075] The selection check section 790 is an operation section that is operated when the product displayed in the medium item display column 79 is to be ordered. The selection check section 790 is operated by putting a check mark in a check box.
[0076] The medium item section 791 is a display section that displays a medium item selected through operation of the medium item display column 79 . The product selection button 792 is an operation unit that is operated when selecting a product. When the product selection button 792 is operated, a product selection page for product selection is displayed. It is possible to select a product by operating this product selection page.
[0077] The estimate request content reflect button 793 is an operation section that is operated when the estimate data 29 created by the seller based on the estimate request data 28 is reflected in the product selection field 63 . The quantity display section 794 is a display section that displays the quantity of the product displayed in the medium item section 791.
[0078] The unit input section 795 is an input section for inputting the unit of the quantity inputted to the quantity display section 794 (text information such as formula, piece, kg, etc.). The list price display section 796 is a display section that displays the selling price of the product offered by the customer.
[0079] The selling price rate display section 797 is a display section that displays the selling price rate of the product by the customer. The unit price display section 798 is a display section that displays the sales price (unit price) of the product by the customer. The price display section 799 is a display section that displays the total selling price (unit price x quantity) of the product by the customer.
[0080] The purchase rate display section 800 is a display section that displays the purchase rate of the product by the seller. The purchase price display section 801 is a display section that displays the purchase price (unit price) of the product by the seller.
[0081] The purchase price display section 802 is a display section that displays the total purchase price (unit price x quantity) of the product by the seller. In this embodiment, it is possible to select a product using the medium item display field 79 as follows.
[0082] First, when the product selection button 792 is operated, a product selection page for product selection is displayed on the external terminal 17. Then, when a product is selected and the quantity is input through the operation of the product selection page, the name of the selected product is displayed in the medium item section 791. At this time, the price (unit price) of the selected product is automatically displayed in the list price display section 796, unit price display section 798, and purchase unit price display section 801. At this time, the selling price rate of the selected product is automatically displayed in the selling price rate display section 797, and the purchase rate of the selected product is automatically displayed in the purchase rate display section 800.
[0083] Furthermore, the amount (price) according to the quantity input through the operation of the product selection page is automatically calculated, and the calculated amount is displayed in the amount display area 799 and the purchase amount display area 802. In this embodiment, by selecting a product and inputting the quantity in the product selection field 63 (more specifically, the product selection page), a list of information on the selected product is automatically created in the medium item display field 79 based on the product data 22 stored in the database 20.
[0084] For products that are not registered in product data 22, the product cannot be selected on the product selection page, so text information (product name and model) is directly entered into medium item section 791. In this case, list price display section 796, selling price rate display section 797, unit price display section 798, amount display section 799, purchase rate display section 800, unit purchase price display section 801, and purchase amount display section 802 are left blank.
[0085] <Small item column> The sub-item column is a display column that is created when a product is selected through the operation of the product selection page and the selected product has "sub-items" in addition to "medium items." In the sub-item column, a plurality of sub-item display columns that display sub-items for the product selected in the product selection column 63 are displayed. When the quotation data 29 is reflected, the sub-item column displays sub-items for the contents of the quotation data 29 (information on the product to be quoted). In each sub-item display column, various display items such as a selection check section 790 are set, similar to the above-mentioned medium item display column 79. In the sub-item display column, information on the product is displayed in the same display format as the above-mentioned medium item display column 79.
[0086] <Register button 72> The registration button 72 is an operation section that is operated when registering a product selected in the product selection field 63 or a product displayed in the product selection field 63 .
[0087] <Back button 73> The back button 73 is an operation unit that is operated when returning to the previous page (for example, the customer list page 50).
[0088] In this embodiment, the product selection field 63 on the quotation input page 60 has a function of displaying the contents of the quotation data 29 (more specifically, information on the product to be quoted), as well as a function of selecting and displaying a product through an operation by the customer. Even if a product is selected in the product selection field 63 by the customer before the quotation data 29 is reflected in the product selection field 63, the quotation data 29 can be reflected in the product selection field 63 by operating the quotation request content reflect button 793. The customer then checks the contents of the quotation created by the seller based on the product information reflected in this way.
[0089] <Customer prints out customer-formatted quote> 4, when the quotation (specifically, quotation data 29) created by the seller is confirmed by the customer (S109), the confirmed quotation is output to the external terminal 17 (S111) through operation of the external terminal 17 connected to the second management server 12 (S110). The customer then obtains this quotation by receiving it on the external terminal 17 (S112). This operation is specifically executed as follows.
[0090] That is, the quotation button 85 on the quotation inquiry page 80 is operated as shown in Fig. 7. This causes a confirmation page (not shown) for confirming the display contents of the quotation to be output to be displayed. Then, by operating this confirmation page, a quotation in a predetermined file format (e.g., PDF file format) is output to the external terminal 17 as a customer-style quotation. Note that in this embodiment, the quotation button 85 and the confirmation page on the quotation inquiry page 80 correspond to an output operation section that is operated when outputting a quotation.
[0091] In this embodiment, the quotation output unit 124, which is one of the functional units of the second management server 12, has the function of creating a quotation in a customer format based on the quotation data 29 and outputting the quotation when the following (conditions) are met:
[0092] (Condition) The output operation section is operated in a state where a customer format corresponding to the customer is selected through operation of the estimate layout selection section 62. <Actions and effects of obtaining customer-specific quotations> In this embodiment, a first management server 11 for managing the product transaction details of a seller who sells a product and a second management server 12 for managing the product transaction details of a customer who purchases a product are set up. Therefore, the same data stored in the database 20 can be used in the first management server 11 as data related to the seller's transaction details (e.g., sales), while in the second management server 12 as data related to the customer's transaction details (e.g., purchases). Therefore, each of the seller and the customer can manage the product transaction details by using the data in the database 20 in a form suitable for their own product management.
[0093] According to this embodiment, the customer can use the database 20 and the second management server 12, specifically, by operating the external terminal 17, to request an estimate for a product from a seller.
[0094] Furthermore, upon receiving a request from a customer, the seller can use the database 20 and the first management server 11, specifically through the operation of the operation terminal 14, to create a quotation for a product (more specifically, quotation data 29) and store it in the database 20. Then, when the quotation data 29 is stored in the database 20, the customer can use the quotation data 29 and the second management server 12, specifically through the operation of the external terminal 17, to obtain a quotation in a customer format that is created and output.
[0095] Therefore, a product estimate can be easily created without the need for tedious tasks such as holding a meeting between the seller and the customer, creating documents based on the items agreed upon in the meeting, etc. Moreover, the customer can easily create a customer-formatted estimate without the need for tedious tasks such as receiving an estimate from the seller by facsimile or e-mail, and then transcribing the estimate. Then, the customer can present such a customer-formatted estimate to a third party other than the seller (e.g., the client) as his or her own estimate.
[0096] As described above, according to this embodiment, the transaction management system 10 can be made to be a system that is easy to use for both sellers and customers. <Work related to ordering nameplates> Next, the process for ordering a nameplate will be described with reference to FIG.
[0097] As shown in Figure 5, in this embodiment, in order to perform all tasks related to ordering nameplates without any omissions, a nameplate order button 90 and an ordered / not ordered display column 91 are set in the customer column 54 in the customer display section 52 of the customer list page 50.
[0098] The nameplate order button 90 is an operation unit that is operated when ordering a nameplate. The ordered / not ordered display field 91 is a display field that selectively displays either order completion information that indicates that the ordering of the nameplate has been completed, or order incomplete information that indicates that the ordering of the nameplate has not been completed. For example, the text information "ordered" is used as the above-mentioned order completion information, and the text information "not ordered" is used as the above-mentioned order incomplete information.
[0099] In this embodiment, the nameplate order button 90 and the ordered / unordered display field 91 are set for each customer field 54. Therefore, when multiple customer fields 54 are displayed on the customer list page 50, the nameplate order button 90 and the ordered / unordered display field 91 are displayed for each customer field 54.
[0100] The following describes the process of ordering a nameplate using the nameplate order button 90 and the ordered / not ordered display field 91. When ordering a nameplate, the customer display section 52 of the customer list page 50, more specifically, the customer column 54 corresponding to the nameplate to be ordered, is displayed on the external terminal 17. For example, by performing a customer search using the customer search section 51 of the customer list page 50, it is possible to display the customer column 54 corresponding to the nameplate to be ordered in the customer display section 52 of the customer list page 50. Note that in this embodiment, the customer search section 51 of the customer list page 50 corresponds to a collective display operation section that is operated when displaying transaction information of customers for the same property all at once. Also, in this embodiment, the customer column 54 of the customer list page 50 corresponds to a collective display section that displays transaction information of customers for the same property all at once.
[0101] When ordering a nameplate, the nameplate order button 90 in the customer column 54 corresponding to the nameplate to be ordered is operated. As a result, a nameplate order page (not shown), which is one of the transaction information pages, is displayed on the external terminal 17. Then, through operation of this nameplate order page, information on the nameplate to be ordered (e.g., text data, drawings) is input, and an order request for the nameplate is made based on the information. Specifically, the nameplate order request sending unit 125, which is one of the functional units of the second management server 12, creates nameplate order request data 39 requesting the order of the nameplate, and sends the nameplate order request data 39 to the first management server 11. The nameplate order request data 39 includes information on the nameplate to be ordered. In this embodiment, the nameplate order button 90 and the nameplate order page correspond to the nameplate order operation unit.
[0102] The seller performs the process of ordering the nameplate, such as creating an order form based on the nameplate order request data 39 received by the first management server 11 and sending it by facsimile to the manufacturer of the nameplate. In this embodiment, when a request to order a nameplate is made through operation of the nameplate order button 90 and the nameplate order page, the order completion information is displayed in the ordered / not ordered display field 91. In detail, before a request to order a nameplate is made, the incomplete order information (e.g., text information of "not ordered") is displayed in the ordered / not ordered display field 91. Then, when a request to order a nameplate is made through operation of the nameplate order button 90 and the nameplate order page, the display content of the ordered / not ordered display field 91 is switched from the incomplete order information to the complete order information (e.g., text information of "ordered").
[0103] In this embodiment, a process is executed by the nameplate ordered display unit 126, which is one of the functional units of the second management server 12, to display order completion information in the ordered / not ordered display field 91. In this embodiment, the ordered / not ordered display field 91 corresponds to the nameplate ordered completion display field that displays the order completion information.
[0104] <Actions and effects of carrying out work related to ordering nameplates> In this embodiment, a nameplate order button 90, which is an operation unit dedicated to ordering nameplates, and an ordered / unordered display field 91, which is a display field dedicated to ordering nameplates, are set in the customer field 54 of the customer list page 50. As a result, the ordered / unordered display field 91 displayed in the customer field 54 is visible every time the customer field 54 of the customer list page 50 is viewed. By viewing the ordered / unordered display field 91, it is possible to know whether the order of the nameplate has been completed for the property corresponding to the customer field 54. Moreover, if it is understood based on the ordered / unordered display field 91 that the order of the nameplate is incomplete, the nameplate can be ordered by operating the nameplate order button 90 displayed in the customer field 54 together with the ordered / unordered display field 91. Therefore, according to this embodiment, the work related to ordering nameplates, which is a work that is often forgotten in exterior construction work, can be performed without omission.
[0105] <Displaying the earliest delivery date for a product> Next, the operation of displaying the earliest delivery date of a product will be described with reference to FIG. 9 and FIG.
[0106] 9, a new order page 100, which is one of the transaction information pages, has an expected earliest delivery date field 106. In the expected earliest delivery date field 106, the earliest delivery date of the product is displayed.
[0107] The new order page 100 is displayed on the external terminal 17, for example, in the following procedure. First, in order to specify the product to be ordered, the selection check section 790 is operated on the quotation input page 60 (see FIG. 8). Then, in this state, the quote order button 803 on the quotation input page 60 is operated. This causes the new order page 100 for ordering the product to be ordered to be displayed.
[0108] The new order page 100 includes an "input page" and a "content confirmation page." The "input page" is a page for inputting information related to ordering a product, and the "content confirmation page" is a page for confirming the information input on the "input page."
[0109] The earliest expected delivery date field 106 is not set on the input page, but is set on the content confirmation page. The setting items other than the earliest expected delivery date field 106 are the same on the input page and the content confirmation page. Therefore, the input page and the content confirmation page of the new order page 100 will be described in detail below with reference to FIG. 9 showing the content confirmation page of the new order page 100.
[0110] As shown in FIG. 9, the input page of a new order page 100 has a manufacturer selection section 101, a delivery destination selection section 102, a desired delivery date input section 103, and a product display section 104 set up. The manufacturer selection section 101 is an operation section operated to select the manufacturer of the product to be ordered, more specifically, the product for which the selection check section 790 has been operated on the quotation input page 60. When the new order page 100 is displayed through the operation of the quotation order button 803 on the quotation input page 60, the manufacturer of the product is automatically input and displayed in the manufacturer selection section 101.
[0111] The delivery destination selection section 102 is an operation section operated to specify the delivery destination of the product to be ordered, more specifically, the product for which the selection check section 790 has been operated on the estimate input page 60. Through the operation of the manufacturer selection section 101, the delivery destination of the product, such as the above-mentioned "normal", "manufacturer pick-up", "store pick-up", "direct from manufacturer" and "other", and the address of the place where the product will be delivered are input.
[0112] The desired delivery date input section 103 is an input section for inputting the desired delivery date of the product to be ordered, more specifically, the product for which the selection check section 790 on the quotation input page 60 has been operated. A check box 105 is set near the desired delivery date input section 103 along with the text information "shortest". In this embodiment, when the check box 105 is checked, the shortest delivery date of the product is displayed in the shortest expected delivery date field 106 set on the content confirmation page. In this embodiment, the shortest expected delivery date field 106 corresponds to the shortest delivery date display field that displays the shortest delivery date for the product to be ordered.
[0113] The product display section 104 displays information about the product to be ordered, more specifically, the product for which the selection check section 790 on the estimate input page 60 has been operated. A confirmation button (not shown) is set on the input page of the new order page 100. The confirmation button is operated when moving to the content confirmation page of the new order page 100 after inputting information in the manufacturer selection section 101, delivery destination selection section 102, and desired delivery date input section 103 on the input page.
[0114] The content confirmation page of new order page 100 has an expected earliest delivery date field 106 that displays the earliest delivery date of the product. The content confirmation page of new order page 100 has a confirm button 107. Confirm button 107 is an operation unit that is operated when confirming the content displayed on the content confirmation page and placing an order for the product.
[0115] The following describes how to order a product using the new order page 100. When ordering a product, first, the new order page 100 is displayed on the external terminal 17. For example, the new order page 100 can be displayed by checking the selection check section 790 on the quotation input page 60 and operating the quotation order button 803.
[0116] Then, the manufacturer of the product to be ordered and the delivery destination of the product are input through operation of the new order page 100, more specifically, the input page. If the customer wishes to know the earliest delivery date of the product to be ordered, the customer checks the check box 105 through operation of the external terminal 17. After such operation, the confirmation button on the input page of the new order page 100 is operated.
[0117] This displays the content confirmation page of new order page 100. In addition to the product manufacturer, product delivery destination, desired delivery date, and product information, the content confirmation page displays an earliest expected delivery date field 106. If a check mark is placed in check box 105, the earliest expected delivery date field 106 automatically calculates and displays the earliest delivery date for the product.
[0118] Specifically, the earliest delivery date display unit 127, which is one of the functional units of the second management server 12, calculates the earliest delivery date for the product based on the input information in the product display field 104, the manufacturer selection unit 101, and the delivery destination selection unit 102, and the first to fourth data 33 to 36. Then, the earliest delivery date display unit 127 displays the calculated earliest delivery date in the earliest scheduled delivery date field 106.
[0119] <Calculation display process> Hereinafter, the process of calculating the earliest delivery date and displaying it in the earliest scheduled delivery date field 106 (calculation and display process) will be described with reference to FIG.
[0120] Fig. 10 shows the procedure for executing the calculation and display process, more specifically, the procedure for executing the calculation and display process when the product to be ordered is shipped from the manufacturer and then delivered to the delivery destination specified by the customer via the seller's warehouse. The series of processes shown in Fig. 10 is executed by the second management server 12 as a process at a predetermined interval. The calculation and display process is executed on the condition that the product to be ordered, the manufacturer of the product, and the delivery destination of the product are selected through the operation of the new order page 100, and a check mark is placed in the check box 105.
[0121] 10, in this process, first, a delivery route for the product is calculated from the first data 33 based on the product, manufacturer, and delivery destination selected through the operation of the new order page 100 (S201). This identifies the delivery route for the product to be ordered, such as "manufacturer → seller's warehouse → delivery destination."
[0122] Thereafter, the shortest arrival date (hereinafter, the first shortest arrival date a1) for the product shipped from the manufacturer and received at the warehouse is calculated based on the product, manufacturer, and the second data 34 selected through the operation of the new order page 100 (S202). In the process of S202, the first shortest arrival date a1 is calculated based on the following considerations.
[0123] The manufacturer may publish the shortest number of days required from ordering a product to shipping it (hereinafter, the first shortest shipping period a2). In the second data 34, the relationship between the product and the first shortest shipping period a2 for the same product is predefined. In this process, first, the first shortest shipping date a3 (e.g., xx year xx month [xx+N] days), which is the shortest date and time when the product is shipped from the manufacturer, is calculated based on the first shortest shipping period a2 (e.g., N days) for the product to be ordered and the current date and time (e.g., xx year xx month xx day). Note that the calculation of the first shortest shipping date a3 takes into account the manufacturer's holidays. In addition, when multiple products are selected through the operation of the new order page 100, the latest date and time of the first shortest shipping dates a3 for each product is adopted as the first shortest shipping date a3.
[0124] The seller also knows the shortest date and time required from when the product is shipped by the manufacturer until the product is received at the seller's warehouse (hereinafter referred to as the first shortest number of days for arrival a4). In the second data 34, the relationship between the product and the first shortest number of days for arrival a4 for the product is predefined. In this process, the shortest date and time when the product shipped from the manufacturer is received at the seller's warehouse, that is, the first shortest date for arrival a1, is calculated based on the first shortest number of days for arrival a4 and the first shortest shipping date a3. In this manner, the first shortest date for arrival a1 is calculated.
[0125] Thereafter, based on the warehouse specified in the process of S201 and the above-mentioned first shortest arrival date a1, the shortest date and time when the product once stored in the warehouse will be shipped from the warehouse (hereinafter, the second shortest shipping date b1) is calculated from the third data 35 (S203). In the process of S203, the second shortest shipping date b1 is calculated based on the following considerations.
[0126] The seller knows, for each warehouse, the day on which the goods will not arrive at the warehouse (hereinafter, the arrival unavailable day) and the day on which the goods will arrive at the warehouse (hereinafter, the arrival available day). The relationship between the warehouse and the arrival unavailable day for the warehouse is predefined in the third data 35.
[0127] In this process, the shortest date and time when the product will be received at the warehouse (hereinafter, the second shortest arrival date b2) is calculated. Specifically, if the first shortest arrival date a1 is the date on which the product cannot be received at the warehouse specified in the process of S201, the second shortest arrival date b2 is set to the next available date at the warehouse. In this case, the first shortest arrival date a1 is set to the date and time when the product cannot be received at the warehouse, and the second shortest arrival date b2 is set to the date and time when the first shortest arrival date a1 is shifted to the next available date at the warehouse, that is, the shortest date and time when the product can be received at the warehouse. On the other hand, if the first shortest arrival date a1 is set to the date and time when the product can be received at the warehouse specified in the process of S201, the first shortest arrival date a1 is set to the second shortest arrival date b2 as it is, and the first shortest arrival date a1 is set to the date and time when the product can be received at the warehouse.
[0128] The seller also knows the shortest date and time required from when the product arrives at the warehouse until it is shipped from the warehouse (hereinafter, the second shortest shipping date b3). In the third data 35, the relationship between the product and the second shortest shipping date b3 of the same product is predefined. In this process, based on the second shortest shipping date b3 and the second shortest arrival date b2, the shortest date and time when the product once stored in the warehouse is shipped from the warehouse (the second shortest shipping date b1) is calculated. If the second shortest shipping date b1 is a shipping unavailable date of the warehouse, the second shortest shipping date b1 is shifted to the next shipping available date of the warehouse. Note that the shipping unavailable date of the warehouse is a date on which the product is not shipped, and the shipping available date of the warehouse is a date on which the product is shipped. On the other hand, if the second shortest shipping date b1 is a shipping available date of the warehouse, the second shortest shipping date b1 is not shifted. In this manner, the second shortest shipping date b1 is calculated.
[0129] Thereafter, the shortest date and time when the product shipped from the warehouse will be delivered to the delivery destination (hereinafter, shortest delivery date c1) is calculated based on the delivery destination specified in the process of S201, the second shortest shipping date b1, and the fourth data 36 (S204). In the process of S204, the shortest delivery date c1 is calculated based on the following considerations.
[0130] The seller knows the days when the product is not delivered (hereinafter, delivery unavailable days) and the days when the product is delivered (hereinafter, delivery available days) for each warehouse. The fourth data 36 predetermines the relationship between the warehouses and the delivery unavailable days for each warehouse.
[0131] In this process, the shortest date and time when the product is shipped from the warehouse (hereinafter, the third shortest shipping date C2) is calculated. Specifically, if the second shortest shipping date b1 is a date on which the warehouse specified in the process of S201 cannot deliver the product, the third shortest shipping date C2 is set to the next date on which the warehouse can deliver the product. In this case, the second shortest shipping date b1 is set to a date and time when the product cannot be delivered, and the third shortest shipping date C2 is set to a date and time that is later than the second shortest shipping date b1 until the next date on which the warehouse can deliver the product, that is, the shortest date and time when the product can be delivered. On the other hand, if the second shortest shipping date b1 is a date on which the warehouse specified in the process of S201 can deliver the product, the second shortest shipping date b1 is set to the third shortest shipping date C2 as it is, and the second shortest shipping date b1 is set to the third shortest shipping date C2 as it is.
[0132] In addition, the seller knows, for each delivery destination, the date on which the product cannot be delivered to the delivery destination (hereinafter, the delivery unavailable date) and the date on which the product can be delivered to the delivery destination (hereinafter, the delivery possible date). In the fourth data 36, the relationship between the delivery destination and the delivery unavailable date for the same delivery destination is predefined. In this process, if the third shortest shipping date C2 is the delivery unavailable date for the delivery destination identified in the process of S201, the shortest delivery date c1 is set to the next possible delivery date for the delivery destination. In this case, the third shortest shipping date C2 is regarded as the date and time on which the product cannot be delivered to the delivery destination, and the shortest delivery date c1 is set to a date and time that is later than the third shortest shipping date C2 until the next possible delivery date for the delivery destination, that is, the shortest date and time on which the product can be delivered. On the other hand, if the third shortest shipping date C2 is the delivery possible date of the delivery destination specified in the process of S201, the third shortest shipping date C2 is regarded as the date and time when the product can be delivered, and the third shortest shipping date C2 is set as the shortest delivery date c1 as it is. In this way, the shortest delivery date c1 is calculated.
[0133] Thereafter, the earliest delivery date c1 calculated in the process of S204 is displayed in the earliest scheduled delivery date field 106 (S205). In the calculation and display process of this embodiment, when the "manufacturer pick-up" is selected as the delivery destination, the first shortest shipping date a3 is calculated as the shortest delivery date c1 and displayed in the shortest expected delivery date field 106. When the "store pick-up" is selected as the delivery destination, the second shortest shipping date b1 is calculated as the shortest delivery date c1 and displayed in the shortest expected delivery date field 106.
[0134] <Actions and effects of displaying the shortest delivery date c1> In the exterior industry, sellers are often asked by customers about the earliest delivery date for their products. Calculating the earliest delivery date is complicated because it requires consideration of various parameters, such as the time required from ordering the product to shipping the product, the route the product will be delivered on, the operating dates and times of the warehouses the product will pass through during delivery, and the status of the delivery destination.
[0135] In this embodiment, the shortest delivery date c1 of the product is automatically calculated by a simple operation of selecting the product, the product's manufacturer, and the product's delivery destination through the operation of the external terminal 17, taking into consideration the above parameters. The automatically calculated shortest delivery date c1 is then displayed in the shortest expected delivery date field 106 on the content confirmation page of the new order page 100. In this way, according to this embodiment, the work of calculating the shortest delivery date c1 and the work of presenting the shortest delivery date c1 to the customer can be performed automatically. This saves the seller the trouble of presenting the shortest delivery date of the product to the customer.
[0136] As shown in FIG. 9, when placing an order for a product, the user confirms the order contents based on the displayed contents on the content confirmation page of new order page 100, and if the order contents are satisfactory, operates confirmation button 107 on the content confirmation page to register the order contents.
[0137] At this time, the order request transmission unit 128, which is one of the functional units of the second management server 12, creates order data 44 requesting the ordering of the product, and transmits the order data 44 to the first management server 11. In this manner, the product is ordered. In this embodiment, the new order page 100 and the confirmation button 107 correspond to a product ordering operation unit.
[0138] Furthermore, the ordered display unit 129, which is one of the functional units of the second management server 12, displays ordered information in the selection check unit 790 of the quotation input page 60 when a product order is placed through the operation of the new order page 100. Specifically, the selection check unit 790 is displayed in a light gray color, i.e., is grayed out, and is in an inoperable state with a check mark always placed in the check box. In this embodiment, the selection check unit 790 corresponds to an ordered display field that displays ordered information indicating that an order based on the quotation data 29 has been completed.
[0139] <Actions and Effects of Displaying Ordered Information in the Selection Check Unit 790> In this embodiment, a series of systems including a first management server 11 and a second management server 12 enables centralized management of data regarding product quotations created by the second management server 12 and data regarding product orders created by the first management server 11.
[0140] Therefore, when an order request is made to the first management server 11 based on the product information registered on the quotation input page 60, the ordered information can be automatically displayed in the selection check section 790 of the quotation input page 60 without any special operation. Note that when an order request is made to the first management server 11 based on the product information registered on the quotation input page 60, this includes when an order request is made to the first management server 11 based on the quotation data 29 created by the second management server 12.
[0141] This prevents the display content of the selection check section 790 of the quotation input page 60 from being in a state where the ordered information is not displayed even though the product has already been ordered, i.e., the product cannot be ordered. Furthermore, it also prevents the display content of the selection check section 790 of the quotation input page 60 from being in a state where the ordered information is displayed even though the product has not yet been ordered, i.e., the product cannot be ordered. Therefore, by looking at the selection check section 790 of the quotation input page 60, the customer can accurately recognize whether or not a product has been ordered based on the created quotation.
[0142] <Displaying a schedule for construction by a customer> Next, the operation of displaying a schedule for construction work by a customer will be described with reference to FIG.
[0143] As shown in Fig. 11, the transaction information page includes a schedule page 130. The schedule page 130 is displayed, for example, by operating a schedule tab 501 on the customer list page 50 (see Fig. 5). The schedule page 130 has a first schedule display field 131, a second schedule display field 132, a new input button 133, a correction button 134, and a rain crevice button 135 set thereon.
[0144] The first schedule display field 131 is a display field that displays a schedule for construction work by the seller. The first schedule display field 131 displays a schedule that is created based on construction information (construction date, construction content) input by the seller.
[0145] The second schedule display field 132 is a display field that displays a schedule for construction work by a customer. The second schedule display field 132 is configured to display a schedule that is created based on construction information (construction date, construction content) input by the customer. In the example shown in FIG. 11, one second schedule display field 132 is displayed.
[0146] The new input button 133 is an operation section operated when creating a new second schedule display field 132. When the new input button 133 is operated, a new input page (not shown) is displayed. By inputting and registering construction information through the operation of the new input page, a second schedule display field 132 that displays a schedule including the construction information is newly created on the schedule page 130.
[0147] The edit button 134 is an operation section that is operated when modifying an already created second process chart display field 132. When a plurality of second process chart display fields 132 are formed, a edit button 134 is set for each second process chart display field 132. When the edit button 134 is operated to modify the second process chart display field 132, a edit page (not shown) is displayed. By inputting and registering the content of the modifications through the operation of the edit page, the content of the modifications is reflected in the second process chart display field 132.
[0148] In this embodiment, the new input button 133, the new input page, the correction button 134, and the correction page correspond to the construction information input section. In this embodiment, the process schedule display section 12A, which is one of the functional sections of the second management server 12, has a function of displaying a process schedule including the construction information inputted through the operation of the construction information input section in the second process schedule display field 132.
[0149] <Actions and Effects of Setting the Second Process Chart Display Column 132> According to this embodiment, the customer himself / herself can operate the external terminal 17 to display a schedule for the construction work to be performed by the customer on the schedule page 130, which is one of the transaction information pages displayed on the external terminal 17. Therefore, the customer can conveniently use the transaction information page displayed on the external terminal 17.
[0150] <Rain-stained button 135> The rain shift button 135 is an operation unit operated by the customer when postponing multiple construction plans displayed in the second schedule display field 132 all at once. When the rain shift button 135 is operated, all of the multiple construction plans displayed in the second schedule display field 132 (in the example shown in FIG. 11, 2 / 1 (Thu), 2 / 2 (Fri), 2 / 3 (Sat)) are shifted to plans postponed by one day (2 / 2 (Fri), 2 / 3 (Sat), 2 / 4 (Sun)).
[0151] In this embodiment, the schedule postponement unit 12B, which is one of the functional units of the second management server 12, has the function of postponing all of the multiple construction schedules displayed in the second schedule display area 132 by one day when the rain slippage button 135, which serves as a bulk postponement operation unit, is operated.
[0152] <Actions and effects of setting the rain shear button 135> Construction work related to the exterior may be postponed due to rainfall or snowfall. In this case, the construction work is postponed by one day. According to this embodiment, when construction work is postponed due to rainfall or snowfall, by operating the rain slippage button 135, multiple construction work plans displayed in the second schedule display field 132 can be postponed by one day at once in accordance with the actual situation of the above-mentioned exterior construction work.
[0153] Therefore, when construction work is postponed due to rain or snowfall, instead of individually changing the multiple construction plans displayed in the second schedule display area 132, all of the multiple construction plans can be appropriately changed without hassle by operating the rain shift button 135.
[0154] <Estimation work for products that will be installed with length dimensions set by the customer> Next, the process of estimating a product to be installed with a length dimension set by a customer will be described with reference to FIGS.
[0155] For products such as fences and handrails that are installed according to the length specified by the customer (hereinafter referred to as "specific products"), the overall length is adjusted by adding or cutting the components that make up the product during installation. Therefore, when estimating or ordering specific products, the task of calculating the number and cost of components required for installation is complicated.
[0156] In this embodiment, the transaction information page includes a specification selection page 140 shown in Fig. 12 and a specification confirmation page 150 shown in Fig. 13. When the product for which a quotation is requested, i.e., the product selected by the customer in the product selection field 63, is the specific product, the above-mentioned work can be easily performed by operating the specification selection page 140 and the specification confirmation page 150.
[0157] The procedure for executing the above tasks through the operations on the specification selection page 140 and the specification confirmation page 150 will be described below. As shown in Fig. 12, when a specific product is selected, the specification selection page 140 automatically displays a layout input section 142 for inputting information regarding the layout of the product in addition to displaying a first selection section 141 for selecting the product. The specification selection page 140 is a page that is displayed on the external terminal 17 in the process of selecting a product through operation of the product selection section 63 on the estimate input page 60 (see Fig. 8), for example. The specification selection page 140 is also displayed on the external terminal 17 when the product selection button 108, fence pick-up button 109, or handrail pick-up button 110 on the new order page 100 (see Fig. 9) is operated.
[0158] Fig. 12 shows an example of the display of specification selection page 140 when a fence made by company A, which is a specific product, is arranged in an L-shape. In the example shown in Fig. 12, the length dimension of one fence section (4.3 meters), the length dimension of the other fence section (2.8 meters), and a component part (hiding corner joint A...) to be used at the corner where the two fence sections form an angle are input into layout input section 142. Then, when specification confirmation button 143 is operated in this state, specification confirmation page 150 shown in Fig. 13 is displayed.
[0159] As shown in FIG. 13, a specification confirmation page 150 includes a construction cost display field 151, a selection check section 152, and a product confirmation button 153. The construction-inclusive cost display field 151 is a display field that displays a plurality of components for implementing the layout inputted in the layout input section 142, the prices of the plurality of components, the construction content for implementing the layout inputted in the layout input section 142, and the cost for the construction content. In this embodiment, each display item displayed in the construction-inclusive cost display field 151 is automatically calculated by the construction-inclusive cost display unit 12C, which is one of the functional units of the second management server 12, and displayed in the construction-inclusive cost display field 151. Specifically, the construction-inclusive cost display unit 12C calculates each display item by calculation based on information on the product selected in the first selection field 141, information on the layout inputted in the layout input section 142, and the fifth data 37. Then, the construction-inclusive cost display unit 12C displays each calculated display item in the construction-inclusive cost display field 151.
[0160] The selection check section 152 is an operation section operated by the customer when requesting the seller to carry out the work according to the work content displayed in the work-inclusive cost display field 151. The selection check section 152 is an operation section consisting of a check box and the character string "Request work", and is operated by checking the check box.
[0161] The product confirmation button 153 is an operation section that is operated when confirming the selection of a product in the display content of the installation-included cost display field 151 . In this embodiment, by operating product confirmation button 153 while operating selection check section 152 on specification confirmation page 150, the display contents displayed on the specification confirmation page 150 are reflected in product selection column 63. Fig. 14 conceptually shows an example of the display contents of product selection column 63. As shown in Fig. 14, the multiple components that realize the above layout, the prices of the multiple components, the work content that realizes the above layout, and the cost of the work content are automatically calculated and reflected in product selection column 63.
[0162] <Actions and effects of setting pages 140 and 150> In this embodiment, by selecting a specific product through the operation of the external terminal 17 and inputting information regarding the layout of the product, the number and cost of components required to install the specific product in the specified layout can be automatically calculated and displayed in the product selection field 63. This allows the customer to easily understand the number and cost of components required to install the specific product. Moreover, since it is possible to eliminate the effort required to calculate the number and cost of components required to install the specific product, the work required to request a quote and the work required to place an order can be easily performed while saving time and effort.
[0163] <Task of requesting to send catalogues to customers> Next, the operation of requesting delivery of a catalog to a customer will be described with reference to FIG. As shown in Fig. 15, the transaction information page includes a catalog page 160. The catalog page 160 is a page operated by a customer to request a catalog to be sent to the customer. The catalog page 160 is displayed, for example, by operating the catalog button 219 in the menu column 210 (see Fig. 3).
[0164] The catalog page 160 includes a subject selection section 161, a manufacturer selection section 162, a delivery destination input section 163, a catalog input section 164, and a request button 165. The subject selection section 161 is an operation section operated to select a subject. When requesting the shipment of a catalog, "catalog" is selected in the subject selection section 161. The manufacturer selection section 162 is an operation section operated to select a manufacturer to be requested to ship a catalog. In this embodiment, the destination of the shipment request data 40 requesting the shipment of the catalog is specified based on the manufacturer selected in the manufacturer selection section 162 and the manufacturer data 24.
[0165] The delivery destination input section 163 is an input section for inputting the delivery destination of the catalog. The delivery destination input section 163 allows input by selecting the above-mentioned "your company", "lumber yard", "work site", "others", etc. Furthermore, when the above-mentioned "others" is selected, it allows direct input of character information (postal code, address, telephone number, etc.) regarding the delivery destination in the delivery destination input section 163.
[0166] The catalog input section 164 is an input section through which an input operation is performed to select a catalog for which shipping is requested. When a manufacturer is selected in manufacturer selection section 162, catalog input section 164 displays a list of catalogs corresponding to that manufacturer together with quantity input section 166. In the example shown in Fig. 15, four types of catalogs are displayed together with quantity input section 166. By inputting a quantity in quantity input section 166, the catalog to be requested for shipping is selected and the quantity is input.
[0167] The request button 165 is an operation section that is operated when requesting the delivery of a catalog with the contents selected through the operation of the catalog page 160. <Operation on Catalog Page 160> When requesting that a catalog be sent to the customer, the customer operates catalog page 160 as follows. The customer selects "catalog" by operating subject selection section 161. The customer also selects the manufacturer to whom the catalog is to be sent by operating manufacturer selection section 162, and selects the destination of the catalog by operating destination input section 163. The customer further operates catalog input section 164 to select the catalog to be sent and input the quantity of the catalog. In detail, the customer selects the catalog to be sent from the list of catalogs displayed in catalog input section 164 by selecting a manufacturer in manufacturer selection section 162, and inputs the quantity in quantity input section 166 corresponding to the selected catalog. After this series of operations, the customer operates request button 165.
[0168] This displays a confirmation page (not shown) for confirming the request details for requesting the shipment of the catalog. Then, by operating the confirm button on this confirmation page, the request details for requesting the shipment of the catalog are confirmed. In detail, at this time, creation request data 45 for requesting the creation of the shipment request data 40 is created, and the creation request data 45 is stored in the database 20. The creation request data 45 includes data on the manufacturer requesting the shipment of the catalog, data on the delivery destination of the catalog, and data on the catalog to be requested to be shipped. The second management server 12 has a function of creating the creation request data 45 in this way, and storing the creation request data 45 in the database 20. In this embodiment, the request button 165 and the confirmation page correspond to the catalog delivery request section.
[0169] The first management server 11 has, as a functional unit, the shipping request data creation unit 111. On the condition that the creation request data 45 is created by the second management server 12 and stored in the database 20, the shipping request data creation unit 111 creates shipping request data 40 to be transmitted to the product manufacturer to request the shipment of a catalog.
[0170] The shipping request data 40 is data for requesting the shipping of a catalog, with the seller as the sender of the shipping request data 40 and the customer as the recipient of the catalog. The shipping request data 40 is created based on the production request data 45, the customer data 25, and the manufacturer data 24 stored in the database 20. As the shipping request data 40, for example, document data that can be sent by facsimile or e-mail is created.
[0171] The first management server 11 has, as a functional unit, the shipping request data transmission unit 112. The shipping request data transmission unit 112 has a function of transmitting the shipping request data 40 created by the shipping request data creation unit 111 to an external device of the manufacturer via the communication network 16. The shipping request data transmission unit 112 automatically transmits the shipping request data 40 to the manufacturer, for example, by facsimile or email.
[0172] <Actions and effects of setting catalog page 160> A seller may be requested by a customer to order a product catalog. In this case, the seller creates document data for ordering the catalog in a format that lists the seller as the sender of the document for ordering the catalog and the customer as the recipient of the catalog, and transmits the document data to the product manufacturer by facsimile or e-mail. The tasks involved in creating such documents and transmitting the document data are simple, but tedious.
[0173] According to this embodiment, when a customer requests to order a catalog, the task of creating shipping request data 40 can be performed automatically by using seller data 23, customer data 25, and manufacturer data 24 stored in database 20. In addition, the task of transmitting shipping request data 40 to the manufacturer can also be performed automatically by using manufacturer data 24. This saves the seller time and effort when ordering a catalog from a manufacturer at the customer's request.
[0174] <The task of instructing the delivery of products for which delivery instructions can be given> Next, the task of issuing a delivery instruction for a commodity for which a delivery instruction can be issued will be described with reference to FIGS.
[0175] As shown in Fig. 16, the transaction information page includes a delivery date notification page 170. The delivery date notification page 170 is displayed, for example, by operating the delivery date notification tab 502 on the customer list page 50 (see Fig. 5). The delivery date notification page 170 is a page that a customer refers to when checking the delivery date of an ordered item.
[0176] The delivery date notification page 170 has a product display field 171 and a delivery instruction waiting display field 172. The product display field 171 is a display field that displays various information about the product ordered by the customer. The delivery instruction waiting display field 172 is a display field that displays delivery instruction waiting information (for example, text information such as "waiting for instructions") for the product that is waiting for delivery instructions.
[0177] Here, at the exterior construction site, it may be desirable for the seller to temporarily store the product purchased by the customer and deliver the product to the customer when the storage space for the product becomes available or when construction work using the product is being carried out. In this embodiment, in such a case, the delivery instruction waiting information is displayed in the delivery instruction waiting display field 172. More specifically, in this embodiment, if the product is one for which a delivery instruction can be issued based on the product data 22, the delivery instruction waiting information is displayed in the delivery instruction waiting display field 172.
[0178] A delivery instruction button 173 is set on the delivery date notification page 170. The delivery instruction button 173 is an operation section operated by a customer when requesting delivery of a product. When the delivery instruction button 173 is operated, a delivery instruction page 180 shown in Fig. 17 is displayed on the external terminal 17. The delivery instruction page 180 is one of the transaction information pages.
[0179] As shown in FIG. 17, a delivery instruction page 180 includes a product display section 181, a selection check section 182, a delivery waiting display section 183, a desired delivery date input section 184, a delivery destination selection section 187, a request button 185, and a back button 186.
[0180] The product display field 181 is a display field that displays the same content as the product display field 171 on the delivery date notification page 170. The selection check section 182 is an operation section that is operated when a product displayed in the product display field 181 is designated as a product to be delivered. The selection check section 182 is an operation section that is composed of check boxes, and is operated by putting a check mark in the check box. The delivery waiting display field 183 is a display field that displays the same content as the delivery instruction waiting display field 172 on the delivery date notification page 170. The desired delivery date input field 184 is an operation section for inputting the date and time for which the product is desired to be delivered.
[0181] The delivery destination selection section 187 is a pull-down input section for selecting a delivery destination of the product. The delivery destination selection section 187 has options such as "your company", "land yard", and "work site".
[0182] The request button 185 is an operation unit operated when requesting delivery of the product according to the contents displayed on the delivery instruction page 180. The back button 186 is an operation unit operated when returning to the previous page (for example, the delivery date notification page 170) without requesting delivery of the product.
[0183] <Delivery Instruction Page 180 Operation> When requesting delivery of a product for which delivery instruction waiting information is displayed in the delivery instruction waiting display field 172, that is, a product for which a delivery instruction can be issued, the delivery instruction page 180 is operated as follows.
[0184] The selection check section 182 corresponding to the product for which delivery is requested is operated. The desired date and time for delivery of the product is entered by operating the desired delivery date input field 184. The delivery destination of the product is selected by operating the delivery destination selection section 187. Then, in this state, the request button 185 is operated. As a result, delivery of the product is requested with the details displayed on the delivery instruction page 180. In this embodiment, the delivery instruction button 173 and the delivery instruction page 180 correspond to the delivery instruction operation section.
[0185] Specifically, a delivery instruction unit 12D, which is one of the functional units of the second management server 12, outputs delivery instruction data 42 instructing the delivery of a product to the first management server 11 when the delivery instruction operation unit is operated through the operation of the external terminal 17. Based on the delivery instruction data 42 received by the first management server 11, the seller arranges for the delivery of the product included in the delivery instruction data 42 to the delivery destination.
[0186] <Actions and effects of setting the delivery instruction operation section> According to this embodiment, the customer can set the delivery timing of the product that the customer has purchased and for which a delivery instruction can be given to the seller, by the simple task of operating the external terminal 17.
[0187] <Effects of this embodiment> The effects of this embodiment will be described. (1) Each of the seller and the customer can use the data in the database 20 in a form suitable for their own product management to manage the details of the product transaction. Also, a product quotation can be easily prepared without the need for tedious tasks such as holding a meeting between the seller and the customer and preparing documents based on the items agreed upon in the meeting. Moreover, the customer can easily prepare a quotation in the customer's format without the need for tedious tasks such as receiving a quotation from the seller by facsimile or e-mail and transcribing the quotation. Thus, according to this embodiment, the transaction management system 10 can be made a system that is easy to use for both the seller and the customer.
[0188] (2) A customer-formatted quotation can be created using the product price included in the quotation data 29, i.e., the purchase price for the customer, and the customer's profit for the same product indicated by the selling price rate data 30, i.e., the amount added by the customer to the purchase price. This allows the customer to automatically create a customer-formatted quotation that lists the product purchase price plus the customer's profit.
[0189] (3) In the customer column 54 of the customer list page 50, an ordered / not ordered display column 91, which is a display column dedicated to ordering nameplates, and a nameplate order button 90, which is an operation unit dedicated to ordering nameplates, are set. Therefore, the work related to ordering nameplates, which is a task that is often forgotten in exterior construction work, can be performed without omission.
[0190] (4) The shortest delivery date c1 of the product is automatically calculated by a simple operation of selecting the product, the product's manufacturer, and the product's delivery destination through the operation of the external terminal 17, taking into consideration the above parameters. The automatically calculated shortest delivery date c1 is then displayed in the shortest planned delivery date field 106 on the transaction information page. In this way, according to this embodiment, the work of calculating the shortest delivery date c1 and the work of presenting the shortest delivery date c1 to the customer can be performed automatically. This saves the seller the trouble of presenting the shortest delivery date of the product to the customer.
[0191] (5) When an order request is made to the first management server 11 based on the quotation data 29 created by the second management server 12, the ordered information can be automatically displayed in the selection check section 790 of the quotation input page 60 without any special operation. Therefore, by looking at the selection check section 790 of the quotation input page 60, the customer can accurately recognize whether or not an order for a product has been placed based on the created quotation.
[0192] (6) The customer can operate the external terminal 17 to display a schedule for the construction work to be performed by the customer on the schedule page 130, which is one of the transaction information pages displayed on the external terminal 17. Therefore, the customer can conveniently use the transaction information page displayed on the external terminal 17.
[0193] (7) When construction work is postponed due to rain or snowfall, instead of individually changing the multiple construction plans displayed in the second schedule display area 132, all of the multiple construction plans can be appropriately changed without hassle by operating the rain shift button 135.
[0194] (8) By selecting a specific product through the operation of the external terminal 17 and inputting information regarding the layout of the specific product, the number and cost of components required to install the specific product in the specified layout can be automatically calculated and displayed in the product selection field 63. This allows the customer to easily perform tasks related to requesting a quote and placing an order while saving time and effort.
[0195] (9) When a customer requests a catalog, the task of creating shipping request data 40 can be performed automatically by using the seller data 23, customer data 25, and manufacturer data 24 stored in database 20. In addition, the task of sending shipping request data 40 to the manufacturer can also be performed automatically by using manufacturer data 24. This saves the seller time and effort when ordering a catalog from a manufacturer at the customer's request.
[0196] (10) When a seller temporarily stores a product that is ready for delivery, the customer can set the delivery timing of the product by a simple operation of the external terminal 17.
[0197] <Example of change> The above embodiment can be modified as follows: The above embodiment and the following modifications can be combined with each other to the extent that no technical contradiction occurs.
[0198] It is possible to directly import the quotation data 29 and create a customer-format quotation based on the quotation data 29 without performing a process to reflect the contents of the quotation data 29 in the product selection field 63. This configuration can be realized by setting up a dedicated page for creating customer-format quotation.
[0199] The quotation request data 28, quotation data 29, and customer-format quotation may be created without using the selling price rate data 30 as profit data. -The selling price rate can be set for each product, or it can be set to the same value for all products of the same customer.
[0200] When requesting a quotation for a product, instead of using the selling price rate data 30 stored in advance in the database 20, a value (selling price rate) input each time through the operation of the external terminal 17 may be used.
[0201] - Purchase rates can be set for each product, or the same value can be set for all products of the same manufacturer. The confirmation page displayed by operating the quotation button 85 on the quotation inquiry page 80 may be omitted. In this case, the quotation in the customer format may be output to the external terminal 17 by operating the quotation button 85.
[0202] When calculating the shortest delivery date, in addition to considering "dates" such as the date on which arrival or shipment is not possible, "times" such as the cut-off time for product delivery or the cut-off time for product collection may also be considered.
[0203] The ordered information displayed in the selection check section 790 of the quotation input page 60 is not limited to a check mark that is always in the check box, a grayed-out state, an inoperable state, or the like, and any other information can be used. For example, the ordered information can be two or only one of a check mark that is always in the check box, a grayed-out state, or an inoperable state. In addition, the ordered information can be a symbol "○" or the text information "ordered" in place of a check mark in the check box.
[0204] Any information can be used as the order completion information to be displayed in the ordered / not ordered display field 91, such as the character information of "order completed" or the symbol "○". Also, any information can be used as the order incomplete information to be displayed in the ordered / not ordered display field 91, such as the character information of "not yet" or the symbol "×".
[0205] The confirmation page that is displayed by operating the confirmation button (not shown) on the new order page 100 may be omitted. In this case, the details of the product order may be registered by operating the confirmation button.
[0206] Days on which construction is not performed (hereinafter, construction unavailable days) may be set in the second schedule display field 132 of the schedule page 130. In order to realize this configuration, construction unavailable days may be registered through the operation of the schedule page 130. With the above configuration, construction plans can be prevented from being displayed on construction unavailable days in the second schedule display field 132 of the schedule page 130. Moreover, when the rain slippage button 135 is operated, all of the multiple construction plans displayed in the second schedule display field 132 can be postponed by one day, excluding construction unavailable days.
[0207] The rain shear button 135 may be omitted. The specific product for which the layout input section 142 and the installation cost display section 151 are automatically displayed is not limited to either a fence or a handrail. Alternatively, the specific product for which the layout input section 142 and the installation cost display section 151 are automatically displayed may be any product that is installed with the length dimensions set by the customer.
[0208] The shipping request data transmission unit 112, which is one of the functional units of the first management server 11, may be omitted. With this configuration, it is possible to automatically create shipping request data 40 with the seller as the sender of the shipping request data 40 and the customer as the recipient of the catalog. In this case, the shipping request data 40 may be sent to an external device of the manufacturer through the operation of the operation terminal 14, or a printed version of the shipping request data 40 may be sent to the manufacturer by facsimile.
[0209] The process for displaying the delivery instruction waiting information in the delivery instruction waiting display field 172 can be changed as desired. The above process can be executed based on the following idea. The customer specifies a product for which a "delivery instruction" is to be issued by operating the external terminal 17. The second management server 12 displays the delivery instruction waiting information in the delivery instruction waiting display field 172 corresponding to the specified product.
[0210] The date and time to be entered in the desired delivery date input field 184 on the delivery instruction page 180 can be the "date" on which the product is desired to be delivered, or the "date" and "time" on which the product is desired to be delivered, or the "period" on which the product is desired to be delivered.
[0211] The deliverable status information displayed in the delivery instruction waiting display field 172 is not limited to the text information "waiting for instructions" and can be changed as desired, such as by using text information other than "waiting for instructions" or by using a check mark to be placed in a check box.
[0212] The transaction management system 10 is not limited to performing all of the following (Task 1) to (Task 8), but may perform only a portion of (Task 1) to (Task 8) (specifically, one, two, three, four, five, six, or seven).
[0213] (Task 1) Printing out a quote in customer format. (Task 2) Work related to ordering nameplates. (Task 3) Displaying the earliest delivery date for the product.
[0214] (Task 4) Displaying the ordered information in the ordered information display field. (Task 5) Displaying a schedule for the construction work done by the customer. (Task 6) Estimating products to be installed according to the length dimensions set by the customer.
[0215] (Task 7) Requesting that catalogs be sent to customers. (Task 8) Requesting delivery of products that are in a deliverable state. The transaction management system 10 can be constructed not only as a self-developed system, but also by using an external service such as an ASP (Application Service Provider) service. [Explanation of symbols]
[0216] 10. Trade management system 11…First management server 111…Shipping Request Data Creation Department 112…Shipping request data transmission unit 12…Second management server 121…Usage Permission Department 122...Page display section 123...Quote request storage section 124... Estimate output section 125…Nameplate order request transmission section 126…Nameplate order confirmation section 127…Shortest delivery date display section 128...Order request transmission section 129…Order completed display section 12A…Process chart display section 12B…Schedule postponement section 12C…Including installation cost display section 12D…Delivery Instructions 13...Database server 14...Operation terminal 16…Communications Network 17…External terminal 20…Database 50…Customer list page 60...Quote input page 65…Quote Request Page 80…Quote inquiry page 90…Nameplate order button 91...Ordered / Not ordered display column 100…New order page 130...Schedule page 135…rain-stained buttons 140...Specification selection page 142...Layout input section 150…Specification confirmation page 151...Construction cost display column 160…Catalog page 170…Delivery date contact page 173...Delivery instruction button 180…Delivery Instruction Page
Claims
[Claim 1] A transaction management system for managing transaction details of products related to exteriors, a storage unit that stores a database in which transaction information data, which associates identification information set for each customer with transaction information of the customer corresponding to the identification information, and product data relating to information on the products are stored; a first management server that manages the transaction information data and the product data as data related to transaction details of the product by a seller of the product; a second management server that manages the transaction information data and the product data as data related to the transaction details of the product by the customer; the transaction information data includes profit data indicating a profit share of the customer for the product; The second management server a usage permission unit that permits the external terminal to use the database by inputting the identification information through an operation of the external terminal connected via a communication network; a page display unit that displays, when the use of the database is permitted by the usage permission unit, a transaction information page that displays transaction information of the customer corresponding to the input identification information, and that has a quotation request unit that is operated when requesting a quotation for the product and an output operation unit that is operated when outputting the quotation, on the external terminal; a quotation request storage unit which, when the quotation request unit is operated, creates quotation request data for requesting a quotation for the product and stores the quotation request data in the database; a quotation output unit which, through an operation of an operation terminal connected to the first management server, creates quotation data which is data corresponding to the quotation of the product indicated by the quotation request data and stores the quotation data in the database, notifies the external terminal from the first management server of completion of creation of the quotation data as the quotation data is stored, and creates a quotation for the product in an amount including a profit portion of the customer based on the quotation data and the profit data and outputs the quotation to the external terminal when the output operation unit is operated through the operation of the external terminal in response to the notification, Transaction management system.
Citation Information
Patent Citations
Interior and exterior construction order reception and execution system
JP2001209740A
Sales managing system for housing material
JP2002222234A
Market system and its method
JP2007179321A
Electronic commerce transaction integrated management system
JP2019021300A
Information processing system, information processing method, and program
JP2024031943A
