JP7370404B2 - Information processing device, information processing method, and program - Google Patents

Description

The disclosed technology relates to an information processing device, an information processing method, and a program.

In recent years, companies are increasingly using pre-order sales systems such as crowdfunding as a marketing tool for new products and services. The advance reservation sales system accepts reservations for products and services (for example, also referred to as support), and publishes the reservation status (for example, see Patent Document 1).

Patent No. 5733869

However, in conventional reservation sales systems, support targets are general users, and there has been no reservation sales system that is convenient for buyers such as wholesalers and retailers.

Therefore, the disclosed technology aims to provide a new mechanism for reservation sales systems that includes buyers as support targets.

An information processing method in one aspect of the disclosure includes: an information processing device providing a platform that accepts pre-order sales for predetermined products or services and publishes the reception status of the pre-order sales; and among projects registered on the platform. selecting at least one project from the list; obtaining an order request from a buyer who provides the product or service to another person for the product or service of the selected project; and executing processing related to the order request. Including.

According to the disclosed technology, it is possible to provide a new mechanism for reservation sales systems that includes buyers as support targets.

1 is a diagram illustrating an example of a configuration of a reservation sales system according to an embodiment. FIG. 1 is a diagram for explaining an overview of a reservation sales system according to an embodiment. FIG. 1 is a block diagram illustrating an example of a server according to an embodiment. FIG. 2 is a diagram illustrating an example of a user terminal according to an embodiment. FIG. 3 is a diagram illustrating an example of user data according to an embodiment. FIG. 3 is a diagram illustrating an example of project data according to an embodiment. FIG. 3 is a diagram illustrating an example of return data according to an embodiment. FIG. 3 is a diagram illustrating an example of transaction data according to an embodiment. FIG. 3 is a diagram illustrating an example of template data according to an embodiment. It is a figure showing an example of the template of the statement of delivery concerning one embodiment. FIG. 3 is a diagram showing an example of a registration screen according to an embodiment. It is a figure showing an example of transition from a login screen concerning one embodiment. It is a sequence diagram showing an example of processing by each device of the reservation sales system concerning one embodiment. FIG. 3 is a diagram illustrating an example of processing by a server according to an embodiment.

Preferred embodiments of the present invention will be described with reference to the accompanying drawings. In addition, in each figure, those with the same reference numerals have the same or similar configurations.

[Embodiment]
<System configuration>
FIG. 1 is a diagram showing an example of the configuration of a reservation sales system 1 according to an embodiment of the disclosure. As shown in FIG. 1, the reservation sales system 1 includes a server 10, a plurality of user terminals 20, and a plurality of user terminals 30. The server 10, one or more user terminals 20, and one or more user terminals 30 can mutually send and receive data via a network N using TCP/IP or the like as a communication protocol. The network N is constructed of, for example, the Internet, a dedicated communication line (for example, a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), a gateway, and the like. The disclosed reservation sales system is, for example, a system that accepts reservations for predetermined products or services (hereinafter also referred to as "products, etc.") in advance. The predetermined products, etc. include products, etc. approved by the management side of the reservation sales system 1. For example, in addition to unsold products that are not actually sold, there are also products that are sold overseas but are not sold in that country. Improved versions of current products, such as products that are not on sale, or products that have been sold through BtoB but are not recognized or sold to general users.
(function, color, shape, etc.), and products sold only in local areas (limited areas).

The server 10 is a server that provides a platform for executing the reservation sales system 1. The reservation sales system 1 is a mechanism for collecting funds from a large number of supporters via the Internet in order to realize a project that provides a predetermined product or service. An example of realizing this reservation sales system 1 is crowd funding. There are various types of crowdfunding, including purchase-type and investment-type.

The user terminal 20 is a terminal device used by a user (supporter or purchaser) who supports a project published in the reservation sales system 1 realized by the platform provided by the server 10. As the user terminal 20, for example, a personal computer, PDA
(Personal Digital Assistant), mobile information terminals such as smartphones, mobile phones, etc. are used.

The user terminal 30 is a terminal device used by a user (project executor) who executes a project published on a platform implemented in the reservation sales system 1 provided by the server 10. As the user terminal 30, for example, a personal computer, a PDA (
Personal Digital Assistant), mobile information terminals such as smartphones, mobile phones, etc. are used. Hereinafter, when the user terminal 20 or the user terminal 30 is not distinguished, the user terminal 20 (
Also written as 30).

An application program (app) for using the platform of the reservation sales system 1 provided by the server 10 may be stored in the user terminal 20 (30). The application causes the user terminal 20 (30) to execute services such as project planning and support in the reservation sales service provided by the server 10. By executing the application, the user terminal 20 (30) accesses the server 10 and transmits and receives information used for executing the application.

Further, the user terminal 20 (30) may use a web browser to access a website provided by the server 10, and may support a project published on this website or draft a project.

<System overview>
FIG. 2 is a diagram for explaining an overview of the reservation sales system 1 according to an embodiment of the disclosure. The left side of Figure 2 shows one or more buyers, the center shows platform A that realizes the reservation sales system 1, and the right side shows the project contents that each project executor (supplier) wants to realize on the platform. Indicates that it has been published by A. The project display screen includes project details and a report reporting the status of pre-order sales. Projects to be made public may include projects for which pre-order sales are currently being accepted and projects for which pre-order sales have ended.

In the example shown in FIG. 2, in order to use platform A, the buyer performs a login operation using an app or web browser installed on the user terminal 20. The server 10 providing platform A receives login information from the user terminal 20 and executes authentication processing of the login information. Login information may be entered by the buyer or by Coo.
It may be saved in kie, etc.

The server 10 determines whether the user who requested the login is a buyer based on the login information. In this case, when the server 10 registers the user, it is preferable to associate information indicating whether the user is a buyer or not with the user identification information and register it in the database. This results in
The server 10 can determine whether the user is a buyer using the user identification information included in the login information.

When the server 10 determines that the logged-in user is a buyer, the server 10 displays, for example, a web page or application page for buyers (hereinafter also referred to as buyer page), and displays the project displayed on the buyer page. Obtain an order request from a buyer for one project selected from the list. Selectable projects may include projects for which pre-order sales are currently being accepted and projects for which pre-order sales have ended. Here, unlike the page displayed to general users, the buyer page is different from the page displayed to general users.
Indicates a page where you can place orders for products and services, negotiate purchasing, etc.

The project executor receives an order from a buyer via platform A.
For example, the user terminal 30 used by the project executor receives information regarding the order from the server 10 and displays it on the screen to allow the project executor to confirm the order details. When receiving an order, the user terminal 30 receives an order acceptance operation from a project executor, and transmits order acceptance information based on the order acceptance operation to the server 10. Further, when a negotiation is proposed for an order, the user terminal 30 receives a response operation for the negotiation content from the project executor, and transmits response information based on the response operation to the server 10.

The project executor provides the ordered products and services to the buyer and delivers them. At the time of delivery, for example, the user terminal 30 may transmit delivery note data to the user terminal 20 used by the buyer via the server 10.

According to the above reservation sales system 1, it is possible to provide a new system that includes buyers as support targets. For example, buyers can log into the system as support recipients, and, unlike general users, they can also place orders for predetermined products and services. Thereby, the platform in the reservation sales system 1 can also function as a platform that mediates between suppliers (project executors) and buyers. Each configuration of the reservation sales system 1 described above will be explained in detail below.

<Hardware configuration>
FIG. 3 is a block diagram illustrating an example of the server 10 according to an embodiment of the disclosure. server 1
0 includes one or more processing units (CPUs) 110, one or more network or other communication interfaces 120, memory 130, a user interface 150, and one or more for interconnecting these components. communication bus 170.

Server 10 may optionally include a user interface 150, which may include a display device 151 and input devices 152 (such as a keyboard and/or mouse, or some other pointing device).

Memory 130 is, for example, a high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state storage, and may also include one or more magnetic disk storage, optical disk storage, flash memory devices, or It may be a non-volatile memory such as another non-volatile solid-state storage device, or it may be a non-temporary recording medium.

Memory 130 stores data used by reservation sales system 1 . For example, the memory 130 stores user data, project data, return data, transaction data regarding orders, template data regarding orders, and the like. Note that details of each data will be described later using FIGS. 5 to 9.

Further, as another example of the memory 130, one or more storage devices installed remotely from the CPU 110 may be used. In some embodiments, memory 130 stores programs, modules and data structures executed by CPU 110, or a subset thereof.

The CPU 110 executes the program stored in the memory 130 to provide the provision unit 11
2, a determination unit 113, a processing unit 114, a selection unit 115, and an acquisition unit 116 are configured. Providing part 11
2 provides a platform A that accepts reservation sales for predetermined products or services and publishes the reception status of the reservation sales. By providing the platform A, the reservation sales system 1 is realized.

For example, the providing unit 112 performs user registration, publishes the project, accepts pre-order sales for the project, and reports the reception status of pre-order sales. As an example, the providing unit 112 provides a purchase-type crowdfunding platform.

The determination unit 113 acquires login information when the user logs in to use platform A, and executes authentication processing using the acquired login information. The login information includes user identification information (user ID) for identifying users such as project executors, buyers, and general users, passwords, and the like. The user ID is, for example, information unique to the user, such as an email address or a combination of alphanumeric characters set by the user.

Further, when the determination unit 113 acquires a user ID from another processing device used by a user such as a buyer or a general user via the network communication interface 120, the determination unit 113 determines whether the acquired user ID is the user ID of the general user. (first identification information) or buyer's user ID (
second identification information). In addition to general users and buyers, the determining unit 113 may also determine project executors and users of other categories.

For example, the determination unit 113 uses user data (membership data) stored in the memory 130 to determine the user corresponding to the user ID included in the login information. The user data stores at least a user ID (first identification information) of a user who uses platform A, and a user ID (second identification information) of a buyer who sells a predetermined product or service to another person. Further, the user ID of the project executor may also be stored in the user data.

The processing unit 114 executes processing based on the determination result of the determination unit 113. For example, when the acquired user ID indicates a general user, the processing unit 114 controls a normal web page in the reservation sales system 1 to be displayed on the user terminal 20. A typical web page is one that publishes a project for individual users, displays returns on the project, and
This page allows you to solicit support (collect working capital for the project).

Furthermore, when the acquired user ID indicates a buyer, the processing unit 114 controls so that a web page for the buyer is displayed on the user terminal 20. A web page for buyers is, for example, a web page that makes it possible to place an order for a predetermined product or service, and a UI component (UI component) for displaying a web page for buyers on a normal web page. (e.g. buttons).

Thereby, the processing unit 114 executes the subsequent process according to the determination result based on the user ID at the time of login, thereby making it possible to execute the subsequent process suitable for the logged-in user. In the disclosed pre-order sales system 1, since buyers are included as logged-in users, it is possible for buyers to place orders with reference to the pre-order sales reception information published on the platform A.

Furthermore, the processing section 114 includes a selection section 115 and a reception section 116. The selection unit 115 selects at least one project from among the projects registered on the platform A. For example, the selection unit 115 acquires information (for example, a project ID) indicating a project selected from one or more projects that are open to the public from the user terminal 20 based on a selection operation by a supporter (for example, a buyer). . The selection unit 115 selects one project based on the acquired project ID. Note that the selectable projects include projects for which pre-order sales are currently being accepted and projects for which the pre-order sales period has ended. By making it possible to select projects for which the pre-order sales acceptance period has ended, buyers can decide on the content of their orders in consideration of the final acceptance results of the pre-order sales. It is also possible to increase the number of projects that buyers can select from.

The acquisition unit 116 acquires an order request for a product or service of the selected project from a buyer who provides the product or service to another person. For example, when a predetermined item is input from the order screen on the user terminal 20 and the order button is pressed by the buyer, the acquisition unit 116 acquires an order request from the buyer from the user terminal 20 .

Furthermore, the processing unit 114 executes processing regarding the acquired order request. For example, the processing unit 114 generates transaction data based on the order request, and stores the generated transaction data in the memory 13.
Manage to 0. Specifically, the processing unit 114 assigns a transaction ID, the date on which the order request was obtained, and if order information is attached to the order request, the number of ordered items, amount, delivery date, and payment method included in the order information. etc. are stored in the memory 130 in association with the transaction ID.

This makes it possible for platform A to provide ordering services through smooth processing by obtaining purchase ordering requests from buyers for publicly available products and the like. Note that the processing unit 114 also includes the processing described below as the processing related to the order request.

The processing unit 114 displays first display information (for example, a normal web page) displayed on the user terminal 20 when the acquired user ID is an ID (first identification information) indicating a general user, and the acquired user ID. When the ID is an ID (second identification information) indicating a buyer, the second display information (for example, a web page for buyers) displayed on the user terminal 20 may be different. For example, a normal web page and a web page for buyers may have different display contents, or may have different screen operability in terms of user interface. For example, a web page for buyers can be structured so that customers can place large orders for products, negotiate prices, and ask questions about specifications.

As a result, in the reservation sales system 1, by providing display information for buyers, it becomes possible to place large orders and conduct business negotiations that cannot be done with support from general users. In addition, as an example, buyers will be able to check pre-order sales information, consider which project, how much to order, and at what price, and input the results of their consideration into the system. .

Furthermore, when the acquired user ID is the user ID of the buyer, the processing unit 114 may receive order information regarding a predetermined product or service from the user terminal 20 used by the buyer along with the order request. Next, the processing unit 114 controls the received order information to be transmitted to the user terminal 20 used by the project executor who supplies the predetermined product or service. For example, the ordering information includes information related to ordering, such as quantity, delivery date, and price.

As a result, the buyer can, via platform A provided by the reservation sales system 1,
By sending order information to the project executor (supplier), it becomes possible to request negotiations for the purchase of products, etc.

Also. The processing unit 114 may perform payment processing regarding order information. For example, if the order is approved by the project executor, the processing unit 114 may perform a payment process in which the buyer pays the project executor. For example, the server 10 may allow the buyer to register payment information, and once the quantity and price to be ordered are determined, the total amount may be calculated and the payment may be made. The payment information includes, for example, at least one of a bank account number, credit card information, account information for a service that uses electronic money, and the like.

Furthermore, the processing unit 114 may transmit the template file of the delivery note to the user terminal 20 used by the project executor. Further, the processing unit 114 may transmit each template file of a document related to an order (for example, a purchase order) to the user terminal 20 on the purchaser side or the user terminal 30 on the project executor side at an appropriate time. For example, the processing unit 114
When sending order information, the company also sends a template file for the delivery note, or makes it available for download from a web page for project executors.

This makes it possible to send delivery note template files to project executors who do not have their own delivery notes, making it possible to provide more appropriate services.

The processing unit 114 may perform processing for the buyer to enroll in a predetermined insurance. for example,
A company providing platform A collaborates with an insurance company that provides insurance for retail and wholesale trade, and recommends and provides this insurance to buyers. Specifically, UI parts (for example, check buttons, radio buttons, etc.) that prompt the buyer to subscribe to insurance such as product liability insurance are displayed on the screen displaying the web page for buyers. When this UI component is operated by the buyer, a screen showing the insurance details is displayed, and the processing unit 114 executes the insurance enrollment procedure.

This makes it possible to provide appropriate insurance to buyers who sell products. Furthermore, by including the insurance enrollment operation in the ordering operation, the buyer can easily enroll in insurance. Furthermore, the processing unit 114 may perform processing for the project executor to take out insurance such as product liability insurance, for example. For example, by including an insurance subscription operation in response operations for an order for a project executor, the project executor can easily subscribe to insurance.

Furthermore, the processing unit 114 may perform management related to transactions or shipping processing for predetermined products. For example, the processing unit 114 may utilize a warehouse owned by a company that provides platform A.
manages the products delivered from the project executor to the warehouse, and also manages the shipment from the warehouse to buyers, etc.

This makes it possible for project executors who do not own a warehouse to manage products appropriately, and improves the reliability of platform A. Additionally, transaction processing, inventory management, and shipping management can be centrally managed, making processing more efficient.

Furthermore, the processing unit 114 may acquire review information regarding a trading partner of a predetermined product or service. In this case, the memory 130 stores the acquired review information in association with the user ID indicating the transaction partner. For example, after the delivery is completed, the processing unit 114 sends a review request notification from the buyer to the project executor's review information and from the project executor to the buyer to the user terminals 20 of each of the buyer and the project executor. It may be controlled so that the information is sent to In this case, each piece of review information input in response to the review request notification may be received by the server 10.

This allows project executors and buyers to refer to review information of the parties with whom they will do business from now on, which can be useful in selecting business partners.

FIG. 4 is a diagram illustrating an example of a user terminal 20 (30) according to an embodiment of the disclosure. User terminal 20 (30) includes one or more processing units (CPUs) 210, one or more network or other communication interfaces 220, memory 230, user interface 25
0, and one or more communication buses 270 for interconnecting these components.

User interface 250 includes a display device 251 and an input device 252 (such as a keyboard and/or mouse, or some other pointing device).

Memory 230 is, for example, a high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state storage, and may also include one or more magnetic disk storage, optical disk storage, flash memory devices, or It may be a non-volatile memory such as another non-volatile solid-state storage device, or it may be a non-temporary recording medium.

The memory 230 stores data and programs used by the reservation sales system 1. For example, the memory 230 stores application programs for mobile terminals in the reservation sales system 1.

The CPU 210 configures the client application 211 by executing a program stored in the memory 230. The client application 211 includes, for example, a web browser, a mail application, and the like. The web browser allows viewing of platform A web pages. Furthermore, by executing the application for the mobile terminal in the installed pre-order sales system 1, the web page of the platform A can be viewed.

The CPU 210 of the user terminal 20 on the support target side logs into platform A,
It is possible to view projects that pre-sell products, etc. Furthermore, the CPU 210 of the user terminal 30 on the side of the project executor can log into the platform A and check the pre-order sales status and answer questions from the support target.

<Example of each data>
Next, each data stored in the memory 130 of the server 10 will be explained using FIGS. 5 to 9. FIG. 5 is a diagram illustrating an example of user data according to an embodiment. The user data in the example shown in FIG. 5 includes a user name, email address, password,
This includes information indicating whether the item is a buyer or not.

"User ID" indicates information for identifying a user, for example. "Username" indicates data used when displaying a user on platform A, such as a full name and a nickname. "Email address" indicates, for example, an e-mail address that is a user's contact information. “Trader” indicates data indicating whether the buyer is a retailer or wholesaler, “〇” indicates a buyer, and “-” indicates a general user. Further, the user data may include an address, payment information such as a bank account number and credit card number, information indicating whether the user is a project executor, and the like.

FIG. 6 is a diagram illustrating an example of project data according to an embodiment. The project data in the example shown in FIG. 6 includes name, user ID, start date,
It includes the end date, target amount, web page, etc.

"Project ID" indicates information that identifies a project that aims to realize a product or service, for example. “Name” indicates, for example, the name of the project. "User ID" is
For example, it shows the user ID of the project executor who planned this project. The "start date" indicates, for example, the date on which this project starts. “End date” indicates the date and time when this project ends. The "target amount" indicates, for example, the lower limit sales amount set for the execution of this project. "Web page" indicates, for example, the URL of a web page for viewing the contents of this project or supporting this project.

FIG. 7 is a diagram illustrating an example of return data according to an embodiment. The return data in the example shown in FIG. 7 includes a name, price, maximum number of sales, remaining number of sales, return details, etc. in association with the project ID and return ID.

“Project ID” indicates, for example, an ID for identifying a project. The "return ID" indicates, for example, an ID for identifying a return obtained when a user provides support. "Name" indicates, for example, the name of this return. "Price" indicates, for example, the selling price of this return. The "maximum sales number" indicates, for example, the maximum sales number of this return.
The "remaining sales number" indicates, for example, the remaining sales number of this return. "Return details"
For example, it shows text data explaining the details of this return. In addition, the return is
Multiple settings may be set for one project.

FIG. 8 is a diagram illustrating an example of transaction data according to an embodiment. The transaction data in the example shown in FIG. 8 includes a user ID, number of orders, wholesale price, order date, transaction type, status, scheduled delivery date, etc. in association with the project ID, transaction ID, product ID, and the like. At least part of the transaction data can be the above-mentioned order information.

“Project ID” indicates, for example, an ID for identifying a project. "Transaction ID" indicates an ID for identifying a transaction such as an order, for example. The "product ID" is, for example, an ID for identifying a product of a project. "User ID" indicates, for example, the buyer's user ID. “Number of orders” indicates, for example, the number of orders for products of this project. The "wholesale price" indicates, for example, the price of a product, etc. that is under negotiation or that has been negotiated. The "order date" indicates, for example, the date on which an order was requested by a buyer. Further, the "order date" may indicate the date on which the transaction was completed. The "transaction type" indicates, for example, the type of transaction, and includes consignment sales, purchase sales, and the like. "Status" indicates, for example, the status of a transaction between a buyer and a project executor. The "scheduled delivery date" indicates, for example, the scheduled date on which the product or the like will be delivered. Note that the transaction data may further include a payment method indicating a payment method, insurance coverage, and the like.

Additionally, sales history data of general users is stored in the memory 110 of the server 10, but is not shown. Sales history data includes, for example, project ID, purchaser ID, return ID,
Includes sales date and time, payment method, etc.

FIG. 9 is a diagram illustrating an example of template data according to an embodiment. The template data in the example shown in FIG. 9 includes a template name, data, etc. in association with the file ID.

"File ID" indicates, for example, an ID for identifying a template. The "template name" indicates, for example, the name of the document used for the transaction. "Data" indicates, for example, the storage location of the template.

FIG. 10 is a diagram illustrating an example of an invoice template according to an embodiment. The template shown in FIG. 10 is a template for a delivery note to be sent to or downloaded to a project executor. A template as shown in FIG. 10 is sent from the server 10 to the user terminal 20 (30) in a timely manner, and a notification including the storage location of the template data is sent to the server 10.
0 to the user terminal 20 (30) in a timely manner.

<Display screen example>
FIG. 11 is a diagram illustrating an example of a registration screen according to an embodiment. In the example shown in Figure 11, the screen for registering as a member of Platform A displays input fields for email address, user name, password, etc. in the right column, and a check field to indicate whether the buyer is a retailer, wholesaler, etc. Ru. Further, the left column is provided with a display column for registering as a member using a social networking service (SNS) or the like.

For example, if the user checks a check box indicating whether the user is a buyer of a retailer, wholesaler, etc., a registration screen for buyers is further displayed, allowing the buyer to register store information, payment method, etc. This makes it possible for the system to determine whether the user is a buyer or a general user by setting it at the time of registration. Note that the registration screen shown in FIG. 11 is an example, and at the beginning of membership registration, the user may be allowed to select whether to be a trader or a general user, and the corresponding registration screen may be displayed.

FIG. 12 is a diagram showing an example of transition from the login screen according to one embodiment. In the example shown in FIG. 12, the login screen is a screen common to any user, and an email address (an example of user identification information) and a password are input by the user.

When the login is completed, for example, if the user is a general user, the processing unit 114 controls the center left screen to be displayed on the user terminal 20, and if the user is a buyer, the processing unit 114 controls the center right screen to be displayed on the user terminal 20. 20. Note that the home screen of platform A may be displayed before transitioning from the login screen to the central screen.

Here, the display screen for a general user and the display screen for a buyer are different.
For example, in the case of a buyer, a "vendor" button is displayed that allows the user to transition to a screen where he or she can negotiate for purchasing with the project executor.

When the buyer presses the "Trader" button, the processing unit 114 controls the user terminal 20 to display the ordering screen at the bottom right. This ordering screen displays an input field for order quantity, an input field for desired price, a check box for insurance participation, and the like. In addition, the ordering screen may also display an input field for a payment method, an input field for a delivery date, and the like.

As a result, for example, on platform A of the reservation sales system 1, it is determined that you are a buyer when you log in, and a display screen for buyers is displayed, making it possible to provide a platform that allows buyers to place orders. become. Further, as shown in FIG. 12, even buyers may be allowed to provide normal support. Note that the display screen shown in FIG. 12 is an example, and completely different display screens may be displayed for general users and buyers after login. In addition, on Platform A, instead of determining whether you are a buyer or not when you log in, the screen shown on the center left in Figure 12 is displayed after logging in, and the message "
It may be determined whether the user is a trader or not when the "If you are a trader" button is pressed.

<Operation explanation>
Next, each operation of the reservation sales system 1 will be explained. FIG. 13 is a sequence diagram showing an example of processing by each device of the reservation sales system 1 according to an embodiment. In the example shown in FIG. 13, the user terminal 20A is a terminal used by buyer A, and the user terminal 30A is a terminal used by a project executor who plans to sell the product that buyer A wants to order.

In step S102, the client application 211 of the user terminal 20A makes a login request to the server 10 based on the buyer A's operation. For example, the login request is
It will be sent along with your user ID and password.

In step S104, upon receiving the login request, the determination unit 113 of the server 10 executes authentication processing using the user ID and password. At this time, the determination unit 113 determines that the user I
D may be used to refer to the user data stored in the memory 130 to determine whether the person to be logged in is a general user or a buyer. In addition, in this determination, the user terminal 20A
A verification process is performed to determine which user ID registered in the user data matches the user ID acquired from the user ID. Here, it is assumed that the determination unit 113 determines that the login target person is a buyer.

In step S106, the processing unit 114 of the server 10 converts the screen information after login authentication into
It is transmitted to the user terminal 20A. For example, the home screen of platform A is displayed.

In step S108, the client application 211 of the user terminal 20A controls the display of the project based on the buyer's operation, and for example, when the "Supplier" button on the project screen shown in FIG. Then, move the order screen to server 1.
Control to request 0.

In step S110, the processing unit 114 of the server 10 transmits ordering screen information to the user terminal 20A in response to the ordering screen request from the user terminal 20A (for example, see the lower right screen shown in FIG. 12).

In step S112, the client application 211 of the user terminal 20A controls the order information to be transmitted to the server 10 when the order information is input based on the buyer's operation and a send button or the like is pressed. The ordering information includes a project ID, the number of orders, a desired price, a buyer's user ID, and the like.

In step S114, the processing unit 114 of the server 10 assigns a transaction ID related to the order based on the order information acquired from the user terminal 20A, manages the transaction information of this order, and then updates the order information. It is transmitted to the user terminal 30A. The processing unit 114 can specify the destination of the order information based on the user ID of the project executor identified from the project ID included in the order information.

In step S116, the client application 211 of the user terminal 30A sends response information including a response to the order information to the server 10 based on the operation of the project executor.
control to send to. The response information includes information such as the desired price and delivery date desired by the project executor in response to the order information.

In step S118, the processing unit 114 of the server 10 updates the transaction information using the response information received from the user terminal 30A, and transmits the response information to the user terminal 20A.

In step S<b>120 , the client application 211 of the user terminal 20</b>A controls the display of the response information, acquires modified information regarding the order based on the buyer's operation, and transmits the modified information to the server 10 .

In step S122, the processing unit 114 of the server 10 updates the transaction information using the modification information received from the user terminal 20A, and transmits the modification information to the user terminal 30A.

Thereby, the buyer can negotiate with the project executor regarding the order via platform A, and the negotiation procedure can be carried out smoothly. Note that steps S116 to S122 may be repeated until the transaction is completed, or steps S116 to S122 may be repeated until the transaction is completed.
If the project executor accepts the order based on the order details in 114, it may be omitted.

In step S124, when the client application 211 of the user terminal 30A recognizes that an order will be received by pressing an OK button or the like based on the operation of the project executor, it transmits order information indicating the order to the server 10.

In step S126, the processing unit 114 of the server 10 updates the status of the transaction information to a completed transaction using the order information received from the user terminal 30A, and updates the order information to the user terminal 20A.
Send to.

In step S128, the processing unit 114 of the server 10 transmits the delivery template to the user terminal 30A, for example. The process in step S128 may be performed at other timings; for example, the delivery template may be transmitted together with the ordering information in step S114.

In step S130, the processing unit 114 of the server 10 executes payment processing for this transaction. For example, a decision process is performed so that the costs incurred in the transaction are paid from the buyer to the project executor using the payment method set by the buyer.

In step S132, after the delivery is successfully performed, the client application 211 of the user terminal 20A controls to transmit review information including reviews for the project executor to the server 10 based on the buyer's operation.

In step S134, after the products etc. are shipped, the client application 211 of the user terminal 30A controls to send review information including reviews for buyers to the server 10 based on the operation of the project executor. . When the server 10 receives both review information, it is preferable to register the review information in association with each user ID of the user data.

According to the above process, it is possible to provide the reservation sales system 1 with a new mechanism that includes buyers as support targets. In addition, buyers can place orders for specific products, check the published pre-sale status, predict the growth potential of a specific product, etc., and decide whether to place an order or not. can be judged.

FIG. 14 is a flowchart illustrating an example of processing by the server 10 according to an embodiment. In the example shown in FIG. 14, the process from login to sending order information is shown, and the process after receiving the order is omitted.

In step S202, the determination unit 113 of the server 10 receives login information from the user terminal 20.

In step S204, the determination unit 113 of the server 10 performs authentication processing using the acquired login information, and determines whether the authentication is successful. If the authentication is successful (step S20
4-YES), the process proceeds to step S208, and if the authentication fails (step S204-
NO), the process proceeds to step S206.

In step S206, the determination unit 113 of the server 10 notifies the user terminal 20 of the authentication failure. This prompts the user to retry logging in.

In step S208, the determination unit 113 of the server 10 determines whether the logged-in user is a trader. If the logged-in user is a trader (step S208-YES), the process proceeds to step S210, and if the logged-in user is a trader (step S208-NO), the process proceeds to step S220. Note that this process may be performed at another timing. For example, this process may be performed after step S212.

In step S210, the processing unit 114 of the server 10 controls to transmit screen information for buyers (for traders) to the user terminal 20A.

In step S212, the processing unit 114 of the server 10 determines whether a request to display an ordering screen has been received from the user terminal 20. If a request to display the ordering screen is received (step S
212-YES), the process proceeds to step S214, and if the order screen display request is not received (step S212-NO), the process ends or proceeds to step S222.

In step S214, the processing unit 114 of the server 10 transmits order screen information to the user terminal 20.

In step S216, the processing unit 114 of the server 10 receives ordering information from the user terminal 20 based on the information set within the ordering screen.

In step S218, the processing unit 114 of the server 10 controls the acquired order information to be transmitted to the user terminal 30 of the project executor.

In step S220, the providing unit 112 of the server 10 transmits screen information for general users to the user terminal 20.

In step S222, the providing unit 112 of the server 10 determines whether there is support from the user. If there is support (step S222-YES), the process proceeds to step S224, and if there is no support (step S222-NO), the process ends.

In step S224, the providing unit 112 of the server 10 executes support processing including specifying which return is supported. Through the support process, it is possible to specify which user has supported which return of which project.

Through the above processing, by using an existing platform and adding a user interface for buyers, it becomes possible to provide buyers with a mechanism that allows them to place orders for desired products.

Although the embodiments have been described in detail above, they are not limited to the above embodiments, and various modifications and changes other than the above embodiments can be made within the scope of the claims, as shown below. is possible.

[Modified example]
The pre-order sales system 1 described in the embodiment does not determine whether the logged-in user is a buyer at the time of login, but rather uses the "Trader" button on the screen that is commonly displayed to any user on platform A. The determination may be made when the button is pressed. In this case, the home screen and project viewing screen of Platform A are common to any user, and when a general user presses the "For Traders" button, it is preferable that an error screen is notified. Further, the merchant may process the delivered products and sell them.

The embodiments and modifications described above are examples for explaining the present invention, and the present invention is not intended to be limited only to the embodiments and modifications. Deformation is possible.

1... Reservation sales system, 10... Server, 20, 30... User terminal, 110... CPU, 13
0...Memory, 112...Providing section, 113... Judgment section, 114... Processing section, 210... CPU, 21
1...Client application, 230...Memory

Claims (5)

The information processing device
Providing a platform that accepts pre-order sales for a project that sells pre-order products or services and publishes the status of reception of the pre-order sales;
obtaining login information including identification information from another processing device;
The first identification information and the second identification information stored in a storage unit that stores first identification information of a user who uses the platform and second identification information of a buyer who provides the product or service to another person. using the method to determine whether the identification information included in the login information is the first identification information or the second identification information;
When the identification information is the first identification information, first screen information that enables the user to perform a purchase operation for one or more projects registered on the platform and accepting the pre-sales; When the identification information is the second identification information, second screen information that enables the buyer to place an order for one or more projects registered on the platform and accepting the pre-sales; transmitting to said other processing device;
An information processing method that performs. The information processing device
Obtaining a purchase request for a product or service of the project selected from among the one or more projects for which reservation sales are accepted, based on a purchase operation from the user on the first screen information;
Obtaining an order request for a product or service of the project selected from among the one or more projects for which reservation sales are accepted, based on an order operation from the buyer on the second screen information;
The information processing method according to claim 1, further comprising: 3. The information processing method according to claim 1, wherein the upper limit of the number of items that the buyer can order using the second screen information is greater than the number that the user can purchase using the first screen information. An information processing device including a processor,
The processor includes:
Providing a platform that accepts pre-order sales for a project that sells pre-order products or services and publishes the status of reception of the pre-order sales;
obtaining login information including identification information from another processing device;
The first identification information and the second identification information stored in a storage unit that stores first identification information of a user who uses the platform and second identification information of a buyer who provides the product or service to another person. using the method to determine whether the identification information included in the login information is the first identification information or the second identification information;
When the identification information is the first identification information, first screen information that enables the user to perform a purchase operation for one or more projects registered on the platform and accepting the pre-sales; When the identification information is the second identification information, second screen information that enables the buyer to place an order for one or more projects registered on the platform and accepting the pre-sales; transmitting to said other processing device;
An information processing device that executes. In the information processing device,
Providing a platform that accepts pre-order sales for a project that sells pre-order products or services and publishes the status of reception of the pre-order sales;
obtaining login information including identification information from another processing device;
The first identification information and the second identification information stored in a storage unit that stores first identification information of a user who uses the platform and second identification information of a buyer who provides the product or service to another person. using the method to determine whether the identification information included in the login information is the first identification information or the second identification information;
When the identification information is the first identification information, first screen information that enables the user to perform a purchase operation for one or more projects registered on the platform and accepting the pre-sales; When the identification information is the second identification information, second screen information that enables the buyer to place an order for one or more projects registered on the platform and accepting the pre-sales; transmitting to said other processing device;
A program to run.

Images