JP2001022824A - Order cancel support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To decrease order mistakes and to reduce the burden on a network or a server by judging the presence or absence of a canceling instruction given from a user for a period covering a point of time when the user carried out an order transmitting operation through an order delay time and then canceling or deciding an order. SOLUTION: The order number, the order transmitting operation time, the URL of an ordering destination site, the order contents, etc., are stored in a transmitting operation time file 106 and an order contents store file 107. The time when the order delay time corresponding to the order URL of a delay time monitoring file 108 is added to the order transmitting operation time corresponding to the order number of the file 106 is found. If an order cancel is detected before the current time is coincident with the said time, a cancel list of order numbers, etc., is shown on a display device 104. If no order cancel is detected within the order delay time, the order registered in the file 106 is transmitted.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an order cancellation support system applied to an order system for ordering a product from a terminal device to a server via a network.

[0002]

2. Description of the Related Art Conventionally, there has been known an order system for ordering various products from a terminal device to a server via a network. An order via a network cannot be canceled once the order is placed in a system that requires high real-time properties, such as purchasing stocks. In some cases, such as Internet shopping, where an order is not highly real-time, cancellation is possible, but in that case, the cancellation process is impossible unless the customer knows the order to be canceled.

[0003]

When ordering a product via the Internet, such as online shopping or stock trading, erroneous information may be entered and transmitted as it is. In the case of missing or obvious mistakes, the server may return a request for rejection or re-entry, but incorrect information such as incorrectly filling in the ordered product with another product Is sent, the conventional technology cannot cancel the order except by the user explicitly canceling the order. Mistakes are often noticed by the user immediately after submitting, but to cancel the order after submitting, it is necessary to access the server again and cancel the ordered item. In the case of an auction or stock trading in which a transaction is made in real time, the transaction may be made before the cancellation is made, and in such a case, the transaction cannot be canceled.

The present invention has been made in view of the above-mentioned problems in the prior art, and can easily cancel an order even after a user sends an erroneous order, thereby reducing order errors and reducing network load. And an order cancellation support system capable of reducing the load on a server.

[0005]

In order to achieve the above object, the present invention provides an order system for transmitting an order from a terminal device to a server device via a network. In a support system, a storage unit storing an order delay time, which is a time from an order transmission operation by a user until the order is actually confirmed, and when there is an order transmission operation by the user,
Means for determining whether or not there is a cancellation instruction by the user between the time and the order delay time, and the cancellation instruction between the order transmission operation time and the order delay time. Means for canceling the order when there is no instruction for canceling the order.

The present invention also relates to an order cancellation system for sending an order from a terminal device to a server device via a network, the system supporting the cancellation of an order entered by a user. Means for receiving and displaying an order screen transmitted from the server device, means for receiving an order transmission operation by the user through the order screen, and time from the order transmission operation by the user to the actual confirmation of the order. An order delay time storage unit that stores an order delay time, an order transmission operation time storage unit that stores the transmission operation time of the order when an order transmission operation is received by the user, and an order transmission operation that is received by the user. Is When the order, for the order, order content storage means for storing the contents of the order, between the transmission operation time and the order delay time, determining means for determining whether or not there is a cancellation instruction by the user, When it is determined that there is a cancellation instruction between the transmission operation time and the order delay time,
Canceling means for deleting the transmission operation time relating to the order stored in the order transmission operation time storage means, and the content of the order stored in the order content storage means; and When it is determined that there is no cancellation instruction before the delay time, the transmission operation time related to the order stored in the order transmission operation time storage unit is deleted, and the transmission operation time stored in the order content storage unit is deleted. Order transmitting means for transmitting the contents of the order to the server device, the server device transmitting means for transmitting an order screen to the terminal device, and an order for receiving and processing the order content transmitted from the terminal device. And processing means.

[0007] The present invention also relates to an order cancellation support system for sending an order from a terminal device to a server device via a network. The order cancellation support system assists in canceling an order entered by a user. Storage means for storing an order delay time, which is the time from when the order is received by the server device to when the order is actually determined, and when the order transmitted from the terminal device is received by the server device, Means for determining whether or not there is a cancellation instruction from the user during the period from the time to the order delay time, and when the cancellation instruction is received from the order reception time to the order delay time. Canceled the order and did not receive the cancellation instruction Can is characterized by comprising a means for determining the order.

[0008] When an order is placed by the user, it is preferable to further comprise means for displaying the past purchase history of the user on the terminal device.

The user's cancel instruction within the order delay time displays a cancel icon on the display screen of the terminal device within the order delay time, and displays a list of orders that can be canceled when the cancel icon is selected by the user. May be displayed on the display screen of the terminal device, and the order selected by the user from the list may be canceled.

The order delay time is, for each customer,
If it is determined according to the use situation of the customer (for example, a beginner who has not been using the system for a long time, or an expert who frequently uses the system) Good.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Two embodiments according to the present invention will be described below with reference to the drawings. These embodiments are:
For orders sent via the network, by displaying purchase history, setting a time difference between user order operation and actual order processing, and displaying a cancelable list display when canceling within that time , To assist in order cancellation. In the first embodiment, the terminal has a file for recording the transmission time, a file for storing the contents of the order, and a file for monitoring the delay time, and performs time monitoring and management of the order history on the terminal side. It is an example. The second embodiment is an example in which a server has a file for recording the time at which an order is received and a file for storing the contents of an order, and performs time monitoring and management of order history on the server side.

First, a first embodiment will be described.

FIG. 1 shows an example of a system configuration of an order system according to the first embodiment. Reference numeral 101 denotes a terminal device such as a personal computer handled by a user. 102 is the terminal (10
This is the processing device of 1). 103 is an input device of the terminal (101) such as a keyboard. 104 is a display device of the terminal (101) such as a display. Reference numeral 105 denotes a storage device of the terminal (101) such as a hard disk, which includes a transmission operation time file (106), an order content storage file (107), and a delay time monitoring file.
(108). 111 is a server that provides virtual shopping and the like. 112 is a processing device of the server (111). Reference numeral 113 denotes a storage device of the server (111), which has an order page file (114) and an order page delay file (115) used in virtual shopping. 121 is a terminal (101) such as the Internet and a server
It is a network connecting (111).

FIG. 3 shows a terminal (1) according to the first embodiment.
It is a specific data configuration example of the transmission operation time file (106) on the 01) side. Column 301 is the order number. This No
When there is an order from the user, the terminal (101) may give a serial number, or the order number received from the server 111 may be stored. Column 302 is the time when the user performed the order transmission operation. Column 303 is the URL of the order destination site (server (111)) (Un
iform Resource Locator). The use of the transmission operation time file (106) will be described later with reference to FIGS. 8 and 9, but when a user performs an order transmission operation, a record is added to the transmission operation time file (106), and the order The record is deleted when is confirmed or canceled. In other words, a record about the order in the waiting state is stored in the transmission operation time file (106).

FIG. 4 shows a terminal (1) according to the first embodiment.
It is a specific data configuration example of the order content storage file (107) on the 01) side. Column 401 is the order number (301) in FIG.
And the order number of the same data. Column 402 is the date when the order was placed, and column 403 is the URL of the site to which the order was placed.
The 404 column is the content actually ordered. The use of the order content storage file (107) will be described later with reference to FIGS. 8 and 9, but when a user performs an order transmission operation, a record is added to the order content storage file (107), and the order is saved. Is canceled when is canceled. Therefore, the record for the confirmed order is stored in the order details file
(107).

FIG. 5 shows a terminal (1) according to the first embodiment.
It is a specific data configuration example of the delay time monitoring file (108) on the 01) side. Column 501 is the URL of the ordered site, and column 502 is the order delay time sent from the server (111).

FIG. 6 shows a specific data configuration example of the order delay files (115, 215) on the server (111, 211) side used in the first embodiment and a second embodiment to be described later. In the column 601, a customer ID is set, and in the column 602, an order delay time for setting a delay time from an order request to actual processing (order transmission) is set. The order delay time (602) is set in advance by a system administrator for each customer. Further, the delay time may be changed according to the access status of the customer. For example, its URL
Set a longer delay time for beginners who have just started purchasing products on the server (111,211), and shorter for customers who have more than a predetermined number of purchases and who seem to be skilled in operation. May be set.

FIG. 7 shows an example of a cancel list (701) displayed on the terminals (101, 201) in the first embodiment and a second embodiment to be described later. The display contents of the cancel list (701) include an order number (711) and order contents (712) as an example.

Next, the operation of the system according to the first embodiment will be described with reference to the flowcharts of FIGS. FIG.
Is a flow showing the operation of the terminal (101). Figure 9 is the server
It is a flow showing the operation of (111).

First, FIG. 8 will be described. When the user browses from a terminal (101), using a browser or the like, to a shopping site or a stock exchange site having his / her user ID and accesses the order page (step
801), the terminal (101) is the site server (111)
At the same time as receiving the order screen from the server, the order delay time (time difference from order operation to actual order transmission) assigned to the user
1) (Step 802).

Subsequently, if the transmission operation time file (106), the order content storage file (107), or the delay time monitoring file (108) does not exist in the storage device (105), these files are created and the delay time monitoring file (108) is created. The URL of the ordering site and the order delay time received from the server (111) are stored in the time monitoring file (108) (step 803). If the transmission operation time file (106), the order content storage file (107), and the delay time monitoring file (108) already exist, they are used.

Next, the order screen received from the server (111) is displayed (step 804), and the user is prompted to select whether or not to display the past purchase history (step 80).
Five). If the user selects to display the purchase history, the past purchase history is listed and displayed on the display device (104) of the terminal (101) with reference to the order content storage file (107) (step 806). If it is selected in step 805 not to display the past purchase history, step 806 is skipped. Next, an operation of inputting and transmitting order information by the user is received (step 807). Here, it is assumed that the terminal (101) assigns the order numbers in a serial number.
Here, only the transmission operation is accepted, and the actual transmission of the order is step 816 described later.

The obtained order number, order transmission operation time, and URL of the site to which the order was placed are entered in the order number column (301 column) of the transmission operation time file (106), respectively.
Save the order transmission operation time column (302 column) and the order URL column (303 column), and store the order No., the date on which the order operation was performed, the URL of the ordered site, and the contents of the order, respectively, in the order contents storage file ( 107) Order No. column (401 column), date column (402 column), order URL
Column (403 column) and order contents column (404 column) (step 808). Next, when the past purchase history is displayed (Yes in step 809), the past purchase history is relisted based on the information of the updated order content storage file (107), and the terminal (101) ) Display device (104),
It is displayed together with the order cancel icon (steps 810, 811). If the past purchase history is not displayed (No in Step 809), the order cancel icon is displayed on the display device (104) of the terminal (101) without going through Step 810 (Step 811). The order cancel icon is an icon displayed to cancel an order by clicking the icon, as described later. FIG. 15 shows a display example of the order cancel icon. FIG. 16 shows a display example of a past purchase history.

Next, at the order transmission operation time (column 302) corresponding to the order No. in the transmission operation time file (106), the order delay time (column 502) corresponding to the order URL in the delay time monitoring file (108). Is obtained, and it is determined whether or not the order cancel icon is clicked before the current time reaches the time (step 812). If the click is made, the order in the transmission operation time file (106) is determined. Search the order contents storage file (107) using No. (301 column) as a key, and delete the matched order No. and order contents from the cancel list (70).
1) is displayed on the display device (104) of the terminal (101) (step
813), the user is prompted to select an order number to cancel (step 814). A display example of the cancel list (701) is shown in FIG. Order canceled by user
When No is selected (step 814), the record of the selected order No is deleted in the order content storage file (107) when cancelled (step 815), and the cancel list is hidden. Next, the record of the canceled order number is deleted from the transmission operation time file (106) (step 817). If there is still a registration record in the transmission operation time file (106) (step 8
18), it is determined that there is an order within the cancelable time, and the process returns to step 812.

If the order cancel icon is not clicked within the order delay time in step 812, the order registered in the transmission operation time file (106) is replaced with the order (the order contents are The process of actually transmitting the content storage file (obtained from the content storage file (107)) is performed (step 81).
6), the record of the transmission operation time file (106) is deleted (step 817). In addition, deletion of step 817
If the process proceeds from step 815 to step 817, it means that the canceled order is deleted.
If the process proceeds to step 817, it means that the actually transmitted order is deleted.

Next, if there is a registration record in the transmission operation time file (106), the process returns to step 812.
If there is no registered record, the cancel icon is hidden (steps 818 and 819). Next, it is determined whether or not the access to the order page has been completed (step 820). If the access has not been completed, it is determined whether or not the user has input and transmitted the order information again (step 821). Step 8 if entered
Return to 08. If there is no input, the process returns to step 820. If it is determined in step 820 that the access to the order page has been completed, the display device (10
The purchase history displayed in 4) is hidden (when the purchase history is displayed), and the corresponding U in the delay time monitoring file (108) is
Delete the RL record and end the operation (step 82
2).

Since the transmission operation time file (106) may include a plurality of orders (not actually transmitted), the processing in steps 812 to 818 is actually performed on those orders. They are executed in parallel.

Referring now to FIG. FIG. 9 is a flowchart of the operation on the server (111) side. When there is an access request for the order page (114) from the terminal (101) (step 9
01), customer ID column (601 column) of order delay file (115)
From the presence or absence of the customer's ID in (1), it is determined whether the customer has accessed the site for the first time (step 902).
If D does not exist, it is determined that no access has been made in the past, a new record is created, and a default value or the like is stored in the order delay time (602) corresponding to the customer ID (601) (step 903). . If it is determined in step 902 that the customer is an existing customer, the process skips step 903 and proceeds to step 904.

Next, the order delay time column (602) corresponding to the customer ID (601 column) in the order delay file (115)
Column) (step 904). (At this time, against the order delay file (115), according to the customer's use frequency of this site, the history of the number of order cancellations, etc.,
The order delay time (502) may be reset. Next, the order page and the order delay time are sent to the terminal (101) (step 905). The order is received from the terminal (101), processing such as order placement is performed, and the operation is terminated (step 906).

Next, a second embodiment will be described.

FIG. 2 shows an example of the system configuration of the order system according to the second embodiment. Figure 1 shows the basic configuration
1 is different from FIG. 1 in the form of file ownership. 201 is a terminal device such as a personal computer handled by the user. 202 is a processing device of the terminal (201). 203 is an input device of the terminal (201) such as a keyboard. 204 is a display device of the terminal (201) such as a display. 205 is a storage device of the terminal (201) such as a hard disk, and has a delay time monitoring file 2 (206).

Reference numeral 211 denotes a server that provides virtual shopping and the like. 212 is a processing device of the server (211). 213 is a storage device of the server (211), which is an order page file (214), an order page delay file (215), a reception time file (216), and an order content storage file 2 used in virtual shopping.
(217). A network 221 connects the terminal (201) and the server (211) such as the Internet.

FIG. 10 shows a specific data configuration example of the reception time file (216) on the server (211) side in the second embodiment. Column 1001 is the order number. This number may be given as a serial number at the terminal (201) or the server (211)
May be set. Column 1002 is the ID of the customer who placed the order. This customer ID is assigned in advance when the customer accesses the shopping mall or site,
Prompt for input each time a customer accesses the mall or site, or obtain it through a function such as a cookie. 1003
The column is the time when the order information was received from the user.
The use of the reception time file (216) will be described later with reference to FIG. 14, but when an order is received by a user, a record is added to the reception time file (216), and when the order is confirmed or canceled, the record is added. The record is deleted. In other words, a record of the order in the waiting state is stored in the reception time file (216).

FIG. 11 shows an example of a specific data configuration of the order content storage file 2 (217) on the server (211) side in the second embodiment. Column 1101 is the same order number as the order number (column 1001) in FIG. Column 1102 is the date the order was received, and column 1103 is the customer ID (100
The same data as in column 2), column 1104 is the contents of the order. 11
The 05 column is a cancellation status indicating whether the order status is waiting for cancellation or confirmed. In the example of the data of the cancellation status (column 1105), “no waiting” and “waiting” are entered for convenience in this example, but “0” and “1” flags may be set. Order details storage file 2 (217)
How to use will be described later with reference to FIG. 14. However, when an order by a user is received, a record is added to the order content storage file 2 (217), and when the order is canceled, the record is deleted. The record related to the order in the waiting state is "waitin
g ", and the record for the confirmed order is stored as" no waiting ".

FIG. 12 shows a terminal according to the second embodiment.
It is a specific data configuration example of the delay time monitoring file 2 (206) on the (201) side. In the 1201 column, set on the terminal (201),
Alternatively, the order number sent from the server (211) is stored. The column 1202 stores the order reception time, which is the time when the server (211) receives the order. The 1203 field stores an order delay time that sets a time that can be canceled from receipt of an order (reception at the server). How to use the delay time monitoring file 2 (206) will be described later with reference to FIG. 13, but when a user performs an order transmission operation, a record is added to the delay time monitoring file 2 (206), and The record is deleted when confirmed or canceled. In other words, a record for the order in the waiting state is stored in the delay time monitoring file 2 (206).

FIG. 6 described in the first embodiment,
7, 15, and 16 are used in the second embodiment in the same manner.

Next, the operation of the system according to the second embodiment will be described with reference to the flowcharts of FIGS.
FIG. 13 is a flowchart showing the operation of the terminal (201). FIG.
Is a flow showing the operation of the server (211).

First, FIG. 13 will be described. When the user accesses the order page from the terminal (201) using a browser or the like (step 1301), the server (211)
Receives the order page access end function that informs the server (211) of the order screen and the end of access to the order page in the form of an applet or the like (step 13).
02). Next, the order screen is displayed on the display device (204) of the terminal (201) (step 1303), and the user is prompted to select whether to display the past purchase history (step 1304). If the user chooses to view purchase history, the server
A request is made to (211) to send a list of past purchase histories, the list is received, and displayed on a part of the display device (204) (step 1305). FIG. 16 shows a display example of the purchase history. If the user selects not to display the purchase history in step 1304, the process proceeds to step 1306 without going through step 1305.
Proceed to.

Next, in step 1306, it is determined whether or not the order information has been input by the user at the terminal (201) and the order information has been transmitted to the server (211). When the order information is transmitted, the display device (20
An order cancel icon (a display example is shown in FIG. 15) is displayed as a part of 4) (step 1307). Step 13
If it is determined in step 06 that there is no input and transmission of order information, it is determined whether a cancel icon is displayed on the display device (204) of the terminal (201) (step 1311). The process proceeds to step 1312 described below. If it is determined in step 1311 that the cancel icon is not displayed, the process proceeds to step 1317.

In step 1306, there is input of order information and transmission to the server (211). After displaying the cancel icon in step 1307, the order number and the time when the server receives the order from the server (211) (ie, The data of the order reception time) and the order delay time are received and stored in the delay time monitoring file 2 (206) of the storage device (205) (step 1308). Next, it is determined whether or not the past purchase history is displayed on the display device (204) of the terminal (201) (step 1309). If so, the purchase history list including the information of the current order is stored on the server.
It is received from (211) and redisplayed on the display device (204) (step 1310). If it is determined in step 1309 that the past purchase history list is not displayed, the process proceeds to step 1312 without passing through step 1310.

Next, based on the order reception time (column 1202) and the order delay time (column 1203) of the delay time monitoring file 2 (206), within the set time (the current time is changed to the order reception time (1202)) The time obtained by adding the order delay time (1203)
It is determined whether or not the cancel icon has been clicked (until it passes) (step 1312). If the cancel icon is clicked within the set time, the server (21
1) Requests and receives a cancelable list, displays it as a cancel list (701) on the display device (204) of the terminal (201), prompts the user to select an order to cancel, and displays the order number designated to be canceled. The server
A reply is made to (211) (step 1313). FIG. 7 shows a display example of the cancel list (701). Next, the record (the record of the order to be canceled) is deleted from the delay time monitoring file 2 (206) (step 1314).

If the cancel icon is not clicked within the set time in step 1312, step 1313
Proceed to step 1314 without passing through
(206) to the relevant record (record where the order is confirmed)
Is deleted (step 1314).

Next, it is checked whether or not there is any record in the delay time monitoring file 2 in order to determine whether or not there is any order within the cancelable time (step 1315). If there is, the process returns to step 1306. If the record has not been saved, the cancel icon displayed on the display device (204) is hidden (step 1316). Subsequently, it is determined whether or not the access to the order page has been completed based on the display other than the order page by the user, the termination of the browser, and the like (step 1317). If not completed, the process returns to step 1306. If it is determined that the order page has been completed, information indicating that access to the order page has been completed is transmitted to the server (step 1318), and the terminal (201)
The past purchase history displayed on the display device (204) is hidden, the order page access end function is deleted, and the operation is ended.

Next, FIG. 14 will be described. FIG.
It is a flow of the operation on the server (211) side. When there is an access request to the order page from the terminal (201) (step 14
01), the order delay time column (602) in the order delay file (215) based on the customer ID that issued the access request.
Column) (step 1402). At this time, if the customer ID is not registered in the order delay file (115), a new record is created, the customer ID that issued the access request is set in the customer ID column (601 column), and A value set in advance as a default in the order delay time column (column 602) is set. As in the first embodiment, the order delay time may be changed according to the access frequency of the customer. Subsequently, the order screen and the order access page end function are sent to the terminal (201) which has issued the access request (step 1).
403). The order end function is the server (211) when the order page is finished browsing on the terminal (201).
This function sends an order end message to

Next, it is determined whether there is a request from the terminal (201) to display a past purchase history (step 1404).
If there is a request, order contents storage file 2 (217)
, The past order of the customer is searched by using the customer ID as a key, the order date and order details of the search result are listed, and sent to the terminal (201) as a purchase history list (step 1405). If there is no request to display the purchase history from the terminal (201) in step 1404, step 1405 is skipped and the process proceeds to step 1406.

Subsequently, it is determined whether or not an order from the terminal (201) has been received (step 1406). If not, it is determined whether or not a record exists in the reception time file (216) (step 1406). 1411). If there is a record in the reception time file (216), the process proceeds to step 1412. If not, the process proceeds to step 1420.

If it is determined in step 1406 that the order from the terminal (201) has been received, the order N
o., the customer ID, and the time at which the order was received are respectively entered in the order number column (1001 column),
Customer ID column (1002 column) and order reception time column (1003
Column, and store the order number, date, customer ID, and order details in the order details save file 2 (2
17) In the order number column (1101 column), date column (1102 column), customer ID column (1103 column), and order content column (1104 column). Furthermore, in the cancellation status column (column 1105), "wa
Iting ”is entered (step 1407).

Next, the order number, order reception time, and order delay time of the accepted order are transmitted to the terminal (201) (step 1408). Also, the terminal (201)
It is determined whether or not the purchase history list (701) has been sent to the terminal (step 1409). If so, the list is updated by adding the contents of the order to the purchase history, and the terminal (20
It is sent to 1) (step 1410). If you have not sent the purchase history list, skip step 1410
Continue to 1412.

In step 1412, the order reception time (1003) within the set time (ie, the reception time file (216))
Column) and the order delay time (column 602) of the order delay file (215), and it is determined whether or not there is a cancel list request from the terminal (201) before the current time has reached (at the time before the current time has arrived) (step 1412) If there is, a list of cancelable order numbers and order contents is sent to the terminal (201) (701) and sent (step 141).
3). The list that can be canceled is displayed as “wai” in the cancellation status column (1105 column) of the order content storage file 2 (217).
"ting" is created by searching for a stored record. When the cancellation order number is returned from the terminal (201) (step 1414), the corresponding record (order to be canceled) of the order content storage file 2 (217)
Is deleted (step 1418).

In step 1412, the terminal (201)
If there is no request for a cancel list from, the cancellation status column (1105) of the order content storage file 2 (217)
Column) is changed from "waiting" to "no waiting", and the order is confirmed (step 1416). Then, a normal order process such as order placement is performed (step # 1417), and step 1 is executed.
418 (delete the record in the reception time file). Subsequently, in order to confirm whether there is an order within the cancelable time, it is determined whether or not a record exists in the reception time file (216) (step 141).
9) If there is, return to step 1406. If not, it is determined whether the access end information of the order page has been received from the terminal (201) (step 1420). If not, the process returns to step 1406. If it has been received, the process related to order cancellation ends.

In the first and second embodiments, the power of the terminal may be turned off while there is an order waiting for cancellation. In this case, the order waiting for cancellation is stored in the transmission operation time file (106) in the first embodiment, and is stored in the delay time monitoring file 2 (206) in the second embodiment. If there is a record in these files when the power is turned on again after the power is turned off, the process may be continued from the process of checking whether or not the cancel icon has been clicked. In particular, if the order delay time is long, it is preferable that the power of the terminal can be turned off in this way.

[0052]

As described above, according to the present invention, transmission of the order to the server is suspended for a predetermined order delay time from when the user performs the order transmission operation, or the order is not sent. The processing of the order is suspended for a predetermined order delay time from when it is received by the server, and it is checked whether or not there is a cancellation instruction by the user during the order delay time. Is canceled, and if there is no cancellation instruction, the order is determined, so that the order can be easily canceled. In particular, the user is often aware of an order mistake immediately after performing the order transmission operation, which is useful in such a case. In addition, since the past purchase history is displayed, the user can perform an order transmission operation while referring to the history, thereby reducing order mistakes. Further, by displaying a cancelable list at the time of cancellation, order errors are reduced. As described above, the reduction in order errors reduces the load on the network and the load on the server.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating an example of a system configuration according to a first embodiment.

FIG. 2 is a diagram illustrating an example of a system configuration according to a second embodiment.

FIG. 3 is a diagram illustrating a data configuration example of a transmission operation time file on the terminal side according to the first embodiment;

FIG. 4 is a diagram showing a data configuration example of an order content storage file on the terminal side according to the first embodiment.

FIG. 5 is a diagram illustrating a data configuration example of a delay time monitoring file according to the first embodiment.

FIG. 6 is a diagram showing a data configuration example of an order delay file on the server side.

FIG. 7 is a view showing a display example of a cancel list.

FIG. 8 is a flowchart showing the operation of the terminal according to the first embodiment.

FIG. 9 is a flowchart showing the operation of the server according to the first embodiment.

FIG. 10 is a diagram illustrating a data configuration example of a reception time file on the server side according to the second embodiment.

FIG. 11 is a diagram showing a data configuration example of an order content storage file 2 on a server side according to the second embodiment.

FIG. 12 is a diagram illustrating a data configuration example of a delay time monitoring file 2 according to the second embodiment.

FIG. 13 is a flowchart showing the operation of the terminal according to the second embodiment.

FIG. 14 is a flowchart illustrating an operation of a server according to the second embodiment.

FIG. 15 is a view showing a display example of an order cancel icon.

FIG. 16 is a diagram showing a display example of a purchase history.

[Explanation of symbols]

101: terminal device, 102: processing device, 103: input device, 104: display device, 105: storage device, 106: transmission operation time file, 107: order content storage file, 108: delay time monitoring file, 111: server, 112: processing device, 113: storage device, 114: order page file, 115: order delay file, 121: network, 201: terminal device, 202
... Processing device, 203 ... Input device, 204 ... Display device, 2
05: storage device, 206: delay time monitoring file 2, 2
11 server, 212 processing unit, 213 storage device, 214 order file, 215 order delay file, 216 reception time file, 217 order content storage file 2, 221 network.

 ────────────────────────────────────────────────── ─── Continued on the front page (72) Inventor Takashi Yagi 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa Prefecture F-term in the System Development Division, Hitachi, Ltd. 5B049 AA01 BB11 CC05 DD01 FF03 FF07 GG02 GG04

Claims (6)

[Claims] In an order system for transmitting an order from a terminal device to a server device via a network, an order cancellation support system for supporting cancellation of an order input by a user, wherein the order is transmitted from an order transmission operation by the user. Storage means for storing an order delay time, which is the time until the actual confirmation, and whether or not there is a cancellation instruction by the user from the time when the order transmission operation is performed by the user to the order delay time. Means for determining whether or not the order is canceled and the order is delayed when the order is canceled and the order is canceled, and the order is canceled when the order is not canceled. Characterized by having means for performing Yanseru support system. 2. An order cancellation support system for assisting cancellation of an order input by a user in an order system for transmitting an order from a terminal device to a server device via a network, wherein the terminal device includes: Means for receiving and displaying the transmitted order screen, means for receiving an order transmission operation by the user by the order screen, and an order delay time, which is the time from the order transmission operation by the user to the actual confirmation of the order. When an order transmission operation by a user is received, an order transmission operation time storage unit that stores the transmission operation time of the order, and when an order transmission operation by the user is received , Order content storage means for storing the contents of the order with respect to the orderer; determining means for determining whether or not a user has issued a cancel instruction between the transmission operation time and the order delay time; and the transmission operation When it is determined that there is a cancellation instruction between the time and the order delay time, the transmission operation time related to the order stored in the order transmission operation time storage means and the order operation time stored in the order content storage means are stored. Cancel means for deleting the contents of the order, and when it is determined that there is no cancellation instruction between the transmission operation time and the order delay time, the order transmission operation time is stored in the order transmission operation time storage means. The transmission operation time related to the order is deleted and stored in the order content storage means. Order transmitting means for transmitting the contents of the order to the server device, the server device transmitting means for transmitting an order screen to the terminal device, and receiving the order contents transmitted from the terminal device. An order cancellation support system comprising an order processing means for processing. 3. An order cancellation support system for assisting cancellation of an order entered by a user in an order system for sending an order from a terminal device to a server device via a network, the order cancellation support system comprising: Storage means for storing an order delay time, which is the time from when the order is actually received by the server device until the order is actually confirmed, and when the order transmitted from the terminal device is received by the server device, Means for determining whether or not there is a cancellation instruction by the user before the order delay time; and, when the cancellation instruction is received from the order reception time to the order delay time, the order Is canceled, and if there is no cancellation instruction, the Order cancellation support system comprising the means for determining the over. 4. The order cancellation support system according to claim 1, further comprising means for displaying a past purchase history of the user on a terminal device when the user places an order. 5. The user's cancel instruction within the order delay time includes displaying a cancel icon on a display screen of the terminal device within the order delay time, and canceling the order when the cancel icon is selected by the user. The order cancellation support system according to any one of claims 1 to 3, wherein the order list is displayed on a display screen of the terminal device, and the order selected by the user from the list is canceled. 6. The order delay time is, for each customer,
4. The method according to claim 1, wherein the method is determined according to the usage of the customer.
An order cancellation support system according to any one of the above.