Method and apparatus for acquiring order information
By establishing shared orders on the online shopping platform's server, the problem of inefficiency when users share order information with others is solved, information synchronization and sharing are achieved, and acquisition efficiency is improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- ADVANCED NEW TECHNOLOGIES CO LTD
- Filing Date
- 2015-04-21
- Publication Date
- 2026-08-04
AI Technical Summary
In existing technologies, users need to communicate or perform multiple operations when sharing order information with others, resulting in low efficiency.
On the online shopping platform's server, a shared order is created in the shared user's account and associated with the original order, allowing the shared user to perform operations to achieve information synchronization and sharing.
It improves the efficiency of users and sharing users in obtaining order information, saving time and effort.
Smart Images
Figure CN115471150B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese invention patent application No. 201510191261.0, filed on April 21, 2015, entitled "Method and Apparatus for Obtaining Order Information". Technical Field
[0002] This specification relates to the field of Internet information technology, and in particular to a method and apparatus for obtaining order information. Background Technology
[0003] With the development and popularization of internet technology, online shopping has become an indispensable part of people's lives. After confirming an order on an online shopping platform, users can generally track the order's processing stage and logistics status through their own accounts, allowing them to conveniently and efficiently obtain logistics information.
[0004] In some situations, goods ordered by users need to be received by someone else. For example, a user may order goods for a friend or relative, or the user may be unable to receive the package themselves and need a friend to receive it on their behalf. To keep the recipient informed of the order's processing status, such as its logistics status, one method is for the user to inform the recipient of the logistics status of their order from their account. This often requires multiple communications between the user and the recipient regarding the logistics status. Another method is for the user to provide the recipient with the logistics company and tracking number, allowing the recipient to check the order's logistics status through the logistics company's website or other logistics service platforms. However, the recipient not only needs to record the tracking number but also needs to perform multiple queries to obtain timely logistics information. Clearly, both methods are time-consuming, labor-intensive, and inefficient. Summary of the Invention
[0005] In view of this, this specification provides a method for obtaining order information, applied to the server of an online shopping platform, including:
[0006] Receive shared users submitted by users; the shared users are other users of the online shopping platform;
[0007] A shared order corresponding to the original order is created in the shared user's account, wherein the original order and the shared order are associated with the same shared information, and the original order is the order created in the user's account;
[0008] Receive operations performed by the sharing user on the shared order based on the shared information.
[0009] This specification also provides a device for obtaining order information, used on the server of an online shopping platform, including:
[0010] A shared user receiving unit is used to receive shared users submitted by users; the shared users are other users of the online shopping platform.
[0011] A shared order creation unit is used to create a shared order corresponding to the original order in the shared user's account, wherein the original order and the shared order are associated with the same shared information, and the original order is the order created in the user's account;
[0012] The shared order operation unit is used to receive operations performed by the shared user on the shared order based on the shared information.
[0013] This specification provides a computer device comprising: a memory and a processor; the memory storing a computer program executable by the processor; and the processor executing the computer program to perform the method described above for obtaining order information.
[0014] This specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is run by a processor, it executes the method described above for implementing web access on a CDN node.
[0015] As can be seen from the above technical solutions, the embodiments of this specification establish a shared order for the original order in the shared user account and associate the original order and the shared order with the same shared information. This allows both the user and the shared user to conveniently obtain the order status through their own accounts, and the shared user can operate on the shared order, thereby improving the efficiency of obtaining order information and processing order matters. Attached Figure Description
[0016] Figure 1 This is a flowchart of a method for obtaining order information according to Embodiment 1 of this specification;
[0017] Figure 2 This is a flowchart of a method for obtaining order information according to Embodiment 2 of this specification;
[0018] Figure 3 This is a flowchart illustrating the interaction between the server and the user / proxy recipient in the application examples of this manual.
[0019] Figure 4 This is the interface displayed when a user terminal confirms an order, as shown in an example in this manual;
[0020] Figure 5 This is the interface displayed when the proxy recipient's terminal receives a proxy mail receiving request, as shown in one example in this manual;
[0021] Figure 6 This is the interface displayed on the user terminal when it receives a message agreeing to accept mail via proxy, as shown in an example in this manual.
[0022] Figure 7This is an example of an interface displayed when a user terminal views the original order in this manual;
[0023] Figure 8 This is the interface displayed when the agent recipient's terminal views a temporary order, as shown in one example in this manual;
[0024] Figure 9 This is another interface displayed when a user terminal views the original order, as shown in one example in this manual;
[0025] Figure 10 It is a hardware structure diagram of a server;
[0026] Figure 11 This is a logical structure diagram of a device for obtaining order information according to an embodiment of this specification. Detailed Implementation
[0027] This specification provides an embodiment of a method for obtaining order information. A user designates another user as a shared user for a specific order on an online shopping platform. The platform creates a shared order in the shared user's account, allowing the shared user to obtain relevant information about the shared order from their own account and perform operations on it. This addresses problems existing in the prior art. The method described in this specification is applied to the server of the online shopping platform. The process of Embodiment 1 is as follows: Figure 1 As shown.
[0028] Step 110: Receive the shared user submitted by the user.
[0029] Users can submit shared users for a single order, for two or more orders, or for all orders. For clarity, in this embodiment, orders created by a user account are referred to as original orders, while orders created in a shared user account to obtain order information are referred to as shared orders.
[0030] Users can submit shared users for an order during the order creation process, or they can submit shared users for an already created order. The online shopping platform's server can create a shared order corresponding to the original order in the shared user's account during the creation of the original order; alternatively, it can create a shared order corresponding to the original order in the shared user's account after the original order has been created, based on the shared users submitted by the user.
[0031] Step 120: Create a shared order in the shared user's account that corresponds to the original order, wherein the original order and the shared order are associated with the same shared information.
[0032] Various information related to the original order can be used as shared information, such as order processing stage information (whether payment has been made, whether the goods have been shipped, etc.), logistics information (logistics company, tracking number, logistics status, etc.), and information about the items or services purchased in the order (links to the details page, item specifications, quantity, etc.). Furthermore, which information is shared can be specified by default by the online shopping platform, specified by the user, or several options can be provided for the user to choose from; this embodiment does not impose any limitations.
[0033] Based on the associated shared information, the sharing user can perform various operations on the shared order. For example, when a user shares information about the purchased items or services in the order, the sharing user can pay for the shared order, collect payments on behalf of the user, and even confirm the completion of the shared order and the original order. This embodiment does not impose any limitations on these actions.
[0034] As can be seen, in this embodiment, by creating a shared order of the original order in the shared user account and associating the original order and the shared order with the same shared information, both the user and the sharing user can conveniently know the status of the order through their own account, which improves the efficiency of obtaining order information and saves time for both the user and the sharing user.
[0035] In Embodiment Two of this specification, the shared user submitted by the user is an agent recipient who collects the ordered goods on behalf of the user. The shared order created in the agent recipient's account is a collection order. In this embodiment, the user can share logistics information with their designated agent recipient. Specifically, this can be done by creating a collection order for the agent recipient. In this way, the agent recipient can track the logistics status information of the user's order through their own account based on the collection order, so as to perform the collection operation in a timely manner. Specifically, the process of Embodiment Two is as follows: Figure 2 As shown.
[0036] Step 210: Receive the proxy recipient submitted by the user.
[0037] In this embodiment, the orders created in the recipient's account for receiving packages are referred to as collection orders.
[0038] After selecting items for an order on an online shopping platform, a user can designate another user as a proxy recipient for that order and submit the order to the platform. The proxy recipient and the user each have their own account on the same online shopping platform. The user can designate the proxy recipient using any method that uniquely identifies the proxy recipient's account on that platform, such as the proxy recipient's registered email address, username, or mobile phone number; this is not limited in this embodiment. A user can designate one or more proxy recipients for a single order.
[0039] Step 220: Create a collection order for the original order in the recipient's account; the original order and the collection order are associated with the same shared information.
[0040] Typically, when an online shopping platform's server receives an order from a user specifying a proxy recipient, it generates an original order for the user and creates a collection order for that original order in the proxy recipient's account. The collection order corresponds to the original order. In this case, the server can create the corresponding collection order before, simultaneously with, or after creating the original order. Alternatively, the user can specify a proxy recipient after generating the order. In this case, the server creates a collection order for the original order after receiving the user's specified proxy recipient. In both scenarios, the server can replace the recipient's contact information in the original order in the user's account with the proxy recipient's contact information.
[0041] Orders received on behalf of another party can be displayed in a way that distinguishes them from other orders in the recipient's account. For example, the recipient's own orders and orders received on behalf of another party can be displayed under different categories, or orders received on behalf of another party can be tagged, etc. Similarly, original orders can also be displayed in a way that distinguishes them from orders received by the user.
[0042] The server can either directly generate a collection order in the designated proxy recipient's account upon receiving an order from a specified proxy recipient, or send a proxy collection request message to the user-designated proxy recipient, informing them that they have been designated by another user as the proxy recipient for a certain order. The proxy recipient can respond to the proxy collection request message by agreeing or refusing to accept the order. If the server receives a response from the proxy recipient agreeing to accept the order, the original order is generated in the user's account and a collection order is generated in the proxy recipient's account. If the server receives a response from the proxy recipient refusing to accept the order, the server returns a message to the user that the order could not be generated due to the proxy recipient's refusal. The user can designate other proxy recipients, delete a proxy recipient if multiple proxy recipients have been designated, or choose to accept the order themselves.
[0043] After the server creates the original order in the user account and the collection order for that original order in the agent recipient account, it associates the original order in the user account and the collection order in the agent recipient account with the same shared information.
[0044] In the implementation of shared information, including logistics information, the specific way in which original orders and collection orders are associated with logistics information can vary depending on the specific implementation of order logistics information provided by the online shopping platform. For example, if the online shopping platform stores the logistics company and waybill number of an order in the user's account, and the server queries the logistics status of the corresponding waybill for that logistics company when the user requests logistics information for a certain order, then the same logistics company and waybill number can be stored for both the original order and the collection order. If the online shopping platform stores logistics information locally on the server for each order, and updates the locally stored logistics information of the order corresponding to that waybill when the logistics company refreshes the logistics information of a waybill, then the server must update the local logistics information of both the original order and the collection order when it receives a refresh message for the waybill corresponding to the original order or the collection order. This embodiment does not limit this.
[0045] As can be seen, in this embodiment, by creating a collection order for the original order in the recipient's account and associating the original order and the collection order with the same shared information, both the user and the recipient can conveniently know the status of the order through their own accounts, which improves the efficiency of obtaining order information and saves time for both the user and the recipient.
[0046] In this embodiment, the level of understanding the recipient of the package on delivery and the operations that the recipient can perform on the package can be determined according to the needs of the actual application scenario.
[0047] In one example, the agent recipient can confirm receipt of a package, but cannot confirm the completion of the package (or the original order). The user can only confirm the completion of the original order after the agent recipient has confirmed receipt. In one implementation, after the merchant on the online shopping platform ships the goods, the server allows the agent recipient to confirm receipt (e.g., enabling the confirmation button for the package); the agent recipient receives the package and confirms receipt (e.g., clicking the confirmation button); after receiving the confirmation message for the package from the agent recipient, the server allows the user to confirm the completion of the original order (e.g., enabling the completion confirmation button for the original order); after verifying that the received package matches the original order, the user confirms the completion of the original order (e.g., clicking the completion confirmation button); after receiving the completion confirmation message for the original order from the user, the original order and the package are completed. The server can either delete the package from the agent recipient's account or retain it. This example is more suitable for situations where a proxy recipient is needed to collect the package, but the user confirms the contents of the order. In this case, to protect the user's privacy, the contents of the order can include the ordering user, order number, and logistics information, but not sensitive information such as the contents and price of the order.
[0048] In another example, the agent recipient performs a confirmation operation on both the package delivery order and the original order. In one implementation, after the merchant on the online shopping platform ships the goods, the server allows the agent recipient to perform a confirmation operation (e.g., enabling the confirmation button for the package delivery order); the agent recipient receives the package, checks that the goods match the package delivery order, and performs a confirmation operation (e.g., clicking the confirmation button); after receiving the confirmation message from the agent recipient, the server notifies the user that the original order is complete; the user is informed that the package delivery order has been confirmed by the agent recipient, and both the original order and the package delivery order are complete. This example is more applicable to scenarios where a user purchases goods and sends them to an agent recipient, in which case the package delivery order may include the ordering user, order number, logistics information, and the goods in the order.
[0049] In addition, when a user designates a proxy recipient, the system can provide the user with the means to set the proxy recipient's level of understanding of the specific contents of the package and / or the actions they can perform on the package; and based on the user's settings, it can execute the subsequent processing flow of the original order and the package.
[0050] In one application example of this specification, the shared information is logistics information. After the online shopping platform agrees to accept the package on behalf of the recipient, it creates a temporary order (i.e., a package collection order for the user's original order) in the recipient's account. Only after the recipient confirms receipt of the temporary order can the user confirm receipt of the original order (i.e., complete the confirmation process). In this application example, the interaction flow between the online shopping platform server using the order information acquisition method described in this specification, the user, and the recipient on behalf of the recipient is as follows: Figure 3 As shown.
[0051] When a user confirms an order on a terminal device (including personal computers, tablets, mobile phones, etc.), they can designate one or more proxy recipients. Figure 4 Taking the user terminal display interface shown as an example, user Chuan Chuan can specify xiaoli123 as the proxy recipient for this order by selecting the username xiaoli123 as the proxy recipient.
[0052] The user's terminal sends the order details, including the user-designated agent recipient, to the online shopping platform's server.
[0053] The server sends a proxy mail collection request message to the proxy recipient's account, informing the proxy recipient of the user account that it wishes to collect mail on their behalf.
[0054] The recipient's terminal can display something like this. Figure 5 The interface shown is as follows. After the recipient clicks "Agree," the terminal sends a response message to the server agreeing to the proxy receiving of mail.
[0055] The server sends a notification message to the user's terminal, informing the user that their designated proxy recipient has agreed to receive mail on their behalf. The interface displayed to the user on the user's terminal can be as follows: Figure 6 As shown.
[0056] The server creates the original order in the user's account, replacing the recipient information in the original order with the contact information of the agent recipient. When the user views their original order, the interface will appear as follows: Figure 7 As shown, the original order information includes its designated agent recipient, and users can view the order's logistics information; at this time, the "Confirm Receipt" button for the original order is disabled.
[0057] The server creates a temporary order corresponding to the original order in the recipient's account. When the recipient views the temporary order in their account, the interface will appear as follows: Figure 8 As shown, the information for a temporary order includes the username "Chuanchuan" and the mobile phone number of the user who placed the order. The agent recipient can view the order's logistics information and can also confirm receipt by clicking the "Received Package" button.
[0058] The server links the user's original order and the agent recipient's temporary order to the same logistics information. In this way, the user and the agent recipient can share the same logistics status through their own accounts.
[0059] After the recipient receives the package, the agent confirms receipt of the temporary order, for example, xiaoli123 in Figure 8 Click the "Receive Package" button on the interface shown.
[0060] The recipient's terminal sends a confirmation message of receipt for the temporary order to the server.
[0061] After receiving the receipt confirmation message for the temporary order, the server allows the user to confirm the completion of the original order. On user Chuan Chuan's terminal, the interface for the original order looks like this: Figure 9 As shown, the "Confirm Receipt" button is now in the "Normal" state.
[0062] After the user confirms the completion of the original order, if... Figure 9 In the interface shown, after user Chuan Chuan clicks the "Confirm Receipt" button, the user's terminal sends a confirmation message for the completion of the original order to the server.
[0063] The server receives the completion confirmation message for the original order, updates the status of the original order, and deletes the temporary order from the agent recipient's account.
[0064] The above-described embodiment two, which uses logistics information as shared information for proxy package collection, illustrates the technical solution of the embodiments in this specification. In practical applications, payment information can also be used as shared information for proxy payments. For example, a proxy payment order created by a user-designated user can be used as the aforementioned shared order, allowing the designated user to make payment based on the proxy payment order to complete the order. And so on.
[0065] Corresponding to the above process, the embodiments of this specification also provide a device for obtaining order information on a server of an online shopping platform. This device can be implemented through software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by the server's CPU reading the corresponding computer program instructions into memory and running them. From a hardware perspective, besides... Figure 10 In addition to the CPU, memory, and non-volatile storage shown, servers typically include other hardware such as boards for implementing network communication functions.
[0066] Figure 11 The illustration shows a device for obtaining order information provided in this embodiment, applied to the server of an online shopping platform. Functionally, it includes a shared user receiving unit, a shared order creation unit, and a shared order operation unit. The shared user receiving unit receives shared users submitted by other users on the online shopping platform. The shared order creation unit creates a shared order in the shared user's account corresponding to the original order. The original order and the shared order are associated with the same shared information, and the original order is the order created in the user's account. The shared order operation unit receives operations performed by the shared user on the shared order based on the shared information.
[0067] Optionally, the shared order creation unit is specifically used to: create a shared order corresponding to the original order in the shared user's account during the creation of the original order; or, after the original order is created, create a shared order corresponding to the original order in the shared user's account based on the shared user submitted by the user.
[0068] Optionally, the shared information includes logistics information; the sharing user is an agent recipient; and the shared order is a collection order.
[0069] In one implementation, the shared order operation unit is specifically used to: receive a receipt confirmation message for the collection order submitted by the agent recipient; the device further includes a completion confirmation enable unit, used to allow the user to complete the confirmation of the original order.
[0070] In another implementation, the shared order operation unit is specifically used to: receive a completion confirmation message for the collection order submitted by the agent recipient; the device further includes an order completion notification unit, used to notify the user that the original order is completed.
[0071] Optionally, the shared information includes: information about the items or services purchased in the original order; the operations performed by the sharing user on the shared order include: paying for the shared order.
[0072] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor; when the processor runs the stored computer program, it executes the various steps of the method for obtaining order information described in this specification. For a detailed description of each step of the method for obtaining order information, please refer to the previous content, which will not be repeated here.
[0073] Embodiments of this specification provide a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the method for obtaining order information as described in these embodiments. Detailed descriptions of the various steps of the method for obtaining order information are provided previously and will not be repeated here.
[0074] The above description is only a preferred embodiment of this specification and is not intended to limit other embodiments for which protection is sought. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection sought.
[0075] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0076] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0077] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0078] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0079] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
Claims
1. A method for obtaining order information, applied on the server of an online shopping platform, comprising: Receive shared users submitted by users; The shared users are other users of the online shopping platform; A shared order corresponding to the original order is created in the shared user's account, wherein the original order and the shared order are associated with the same shared information, and the original order is the order created in the user's account; The system receives operations performed by the sharing user on the shared order based on the shared information. These operations include making payments for the shared order, collecting payments on behalf of the user, or confirming the completion of the shared order and the original order.
2. The method according to claim 1, wherein creating a shared order corresponding to the original order in the shared user's account comprises: During the creation of the original order, a shared order corresponding to the original order is created in the shared user's account; Alternatively, after the original order is created, a shared order corresponding to the original order is created in the account of the shared user based on the shared user submitted by the user.
3. The method according to claim 1, wherein the shared information includes logistics information; the sharing user is an agent recipient; and the shared order is a collection order.
4. The method according to claim 3, wherein receiving the operation performed by the sharing user on the shared order based on the sharing information includes: Receive a receipt confirmation message for the collection order submitted by the agent recipient; The method further includes allowing the user to confirm the completion of the original order.
5. The method according to claim 3, wherein receiving the operation performed by the sharing user on the shared order based on the sharing information includes: Receive a completion confirmation message for the collection order submitted by the agent recipient; The method further includes: notifying the user that the original order is complete.
6. The method according to claim 1, wherein the shared information includes: Information about the items or services purchased in the original order.
7. An apparatus for obtaining order information, used on a server of an online shopping platform, comprising: The shared user receiving unit is used to receive shared users submitted by users; The shared users are other users of the online shopping platform; A shared order creation unit is used to create a shared order corresponding to the original order in the shared user's account, wherein the original order and the shared order are associated with the same shared information, and the original order is the order created in the user's account; The shared order operation unit is used to receive operations performed by the sharing user on the shared order based on the shared information; the operations performed by the sharing user on the shared order include paying for the shared order, collecting the shared order on behalf of the user, or confirming the completion of the shared order and the original order.
8. The apparatus according to claim 7, wherein the shared order establishment unit is specifically used for: During the creation of the original order, a shared order corresponding to the original order is created in the shared user's account; or, after the original order is created, a shared order corresponding to the original order is created in the shared user's account based on the shared user submitted by the user.
9. The apparatus according to claim 7, wherein the shared information includes logistics information; the sharing user is an agent recipient; and the shared order is a collection order.
10. The apparatus according to claim 9, wherein the shared order operation unit is specifically configured to: receive a receipt confirmation message for the collection order submitted by the agent recipient; The device further includes: The completion confirmation enable unit is used to allow the user to confirm the completion of the original order.
11. The apparatus according to claim 9, wherein the shared order operation unit is specifically configured to: receive a completion confirmation message for the collection order submitted by the agent recipient; The device further includes: The order completion notification unit is used to notify the user that the original order has been completed.
12. The apparatus of claim 7, wherein the shared information includes: Information about the items or services purchased in the original order.
13. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the method as described in any one of claims 1 to 6.
14. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the method as described in any one of claims 1 to 6.