CN111127157A - Order processing method, device, storage medium and equipment - Google Patents

Order processing method, device, storage medium and equipment Download PDF

Info

Publication number
CN111127157A
CN111127157A CN201911349172.9A CN201911349172A CN111127157A CN 111127157 A CN111127157 A CN 111127157A CN 201911349172 A CN201911349172 A CN 201911349172A CN 111127157 A CN111127157 A CN 111127157A
Authority
CN
China
Prior art keywords
order
link
cancelled
service node
feedback message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201911349172.9A
Other languages
Chinese (zh)
Inventor
李建伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Missfresh Ecommerce Co Ltd
Original Assignee
Beijing Missfresh Ecommerce Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Missfresh Ecommerce Co Ltd filed Critical Beijing Missfresh Ecommerce Co Ltd
Priority to CN201911349172.9A priority Critical patent/CN111127157A/en
Publication of CN111127157A publication Critical patent/CN111127157A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Landscapes

  • Business, Economics & Management (AREA)
  • Economics (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses an order processing method, an order processing device, a storage medium and equipment, and belongs to the technical field of the Internet. The method comprises the following steps: receiving an order canceling request sent by a user terminal, and broadcasting the order canceling request; obtaining feedback information returned by at least one service node after receiving the order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods delivery link, and the feedback information of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and issuing a response message aiming at the order canceling request to the user terminal based on the feedback message of the at least one service node. The method and the system adopt a broadcasting mode to inquire whether each service node can cancel the order, can timely and quickly respond to the order canceling service, and remarkably improve the processing timeliness of the order canceling service.

Description

Order processing method, device, storage medium and equipment
Technical Field
The present application relates to the field of internet technologies, and in particular, to an order processing method, an order processing apparatus, a storage medium, and a device.
Background
With the rapid development of internet technology, electronic commerce has stepped into a vigorous development era, for example, numerous e-commerce platforms are emerged at present, and the rise of the e-commerce platforms makes online shopping more and more popular among people, and the e-commerce platform has gradually developed into a very important shopping mode.
One common scenario in the online shopping process is as follows: the user usually performs order cancellation operation on the ordered goods for the reasons of wrong information filling, out of stock, and no desire to continue purchasing. After the user performs the order cancel operation, the point of great concern is whether the order is successfully cancelled. Since the user is waiting all the time, timely and quick feedback on canceling the order service is necessary. That is, from the perspective of the e-commerce platform, how to quickly perform order processing after receiving an order canceling request to improve processing timeliness and further ensure user experience becomes a problem to be solved urgently at present.
Disclosure of Invention
The order processing method, the order processing device, the storage medium and the order processing equipment can timely and quickly respond to order canceling business, remarkably improve processing timeliness of the order canceling business and further ensure user experience. The technical scheme is as follows:
in one aspect, an order processing method is provided, and is applied to a cancellation server, where the method includes:
receiving an order canceling request sent by a user terminal, and broadcasting the order canceling request;
obtaining feedback information returned by at least one service node after receiving the order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods delivery link, and the feedback information of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link;
and issuing a response message aiming at the order canceling request to the user terminal based on the feedback message of the at least one service node.
In a possible implementation manner, for any service node, the obtaining a feedback message returned by at least one service node after receiving the order cancel request includes:
if the current order state of the order to be cancelled is not matched with a first order flow transfer link corresponding to the service node, and the first order flow transfer link is positioned behind a second order flow transfer link in the processing flow, receiving a first feedback message returned by the service node;
the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node executes cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transfer link, and forbidding the order to be cancelled to enter the next order flow transfer link;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, receiving a second feedback message returned by the service node, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, for any service node, the obtaining a feedback message returned by at least one service node after receiving the order cancel request includes:
if the current order state of the order to be cancelled is matched with a first order flow transfer link corresponding to the service node and the order state indicates that a target sub-link in the first order flow transfer link is entered, receiving a third feedback message returned by the service node, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow transferring link and the order state indicates that the target link is not entered, receiving a fourth feedback message returned by the service node; the fourth feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node performs cancellation processing on the order to be cancelled and forbids the order to be cancelled to enter a next order streaming link.
In another aspect, an order processing method is provided, which is applied to a service node, and the method includes:
receiving an order canceling request broadcasted by a canceling server, wherein the order canceling request is sent to the canceling server by a user terminal;
generating a feedback message aiming at the order canceling request, wherein the feedback message gives a processing result of a first order streaming link corresponding to the service node on the order canceling request;
returning the feedback message to the cancellation server, where the feedback message is used to instruct the cancellation server to issue a response message for the order cancellation request to the user terminal based on the received feedback message;
wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
In a possible implementation manner, the generating a feedback message for the cancel order request includes:
if the current order state of the order to be cancelled is not matched with the first order flow conversion link and the first order flow conversion link is positioned behind a second order flow conversion link in the processing flow, executing cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow conversion link, forbidding the order to be cancelled to enter the next order flow conversion link, and generating a first feedback message, wherein the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, generating a second feedback message, where the second feedback message is used to indicate that the order cannot be cancelled.
In one possible implementation manner, the generating the feedback message for the cancel order request includes:
if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that a target sub-link in the first order flow conversion link is entered, generating a third feedback message, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that the order to be cancelled does not enter the target sub-link, executing cancellation processing on the order to be cancelled, prohibiting the order to be cancelled from entering the next order flow conversion link, and generating a fourth feedback message, wherein the fourth feedback message is used for indicating that the order can be cancelled.
In another aspect, an order processing apparatus applied to a cancellation server is provided, the apparatus including:
the first receiving module is configured to receive an order canceling request sent by a user terminal;
a broadcast module configured to broadcast the cancel order request;
a second receiving module, configured to obtain a feedback message returned by at least one service node after receiving the order cancellation request, where one service node serves an order flow link, the order flow link at least includes an uncommitted link, a warehouse goods distribution link and a goods distribution link, and the feedback message of each service node gives a processing result of the order cancellation request in the corresponding order flow link;
and the sending module is used for sending a response message aiming at the order canceling request to the user terminal based on the feedback message of the at least one service node.
In a possible implementation manner, for any service node, the second receiving module is further configured to receive a first feedback message returned by the service node if the current order state of the order to be cancelled is not matched with the first order flow transfer link corresponding to the service node, and the first order flow transfer link is located after the second order flow transfer link in the processing flow;
the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node executes cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transfer link, and forbidding the order to be cancelled to enter the next order flow transfer link;
the second receiving module is further configured to receive a second feedback message returned by the service node if the current order state of the order to be cancelled does not match the first order flow transfer link and the first order flow transfer link is located before the second order flow transfer link in the processing flow, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, for any service node, the second receiving module is further configured to receive a third feedback message returned by the service node if a current order state of an order to be cancelled matches a first order flow transfer link corresponding to the service node and the order state indicates that a target sub-link in the first order flow transfer link has been entered, where the third feedback message is used to indicate that the order cannot be cancelled;
the second receiving module is further configured to receive a fourth feedback message returned by the service node if the current order state of the order to be cancelled matches the first order streaming link and the order state indicates that the target sub-link is not entered; the fourth feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node performs cancellation processing on the order to be cancelled and forbids the order to be cancelled to enter a next order streaming link.
In another aspect, an order processing apparatus is provided, which is applied to a service node, and the apparatus includes:
the receiving module is configured to receive a cancellation order request broadcasted by a cancellation server, wherein the cancellation order request is sent to the cancellation server by a user terminal;
a generating module configured to generate a feedback message for the order cancellation request, where the feedback message gives a processing result of the first order streaming link corresponding to the service node on the order cancellation request;
a sending module configured to return the feedback message to the cancellation server, where the feedback message is used to instruct the cancellation server to issue a response message for the order cancellation request to the user terminal based on the received feedback message;
wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
In a possible implementation manner, the generating module is further configured to, if a current order state of an order to be cancelled is not matched with the first order flow transferring link and the first order flow transferring link is located after the second order flow transferring link in a processing flow, perform cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transferring link, prohibit the order to be cancelled from entering the next order flow transferring link, and generate a first feedback message, where the second order flow transferring link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled;
the generating module is further configured to generate a second feedback message if the current order state of the order to be cancelled does not match the first order flow transfer link and the first order flow transfer link is located before the second order flow transfer link in the processing flow, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, the generating module is further configured to generate a third feedback message if a current order state of an order to be cancelled matches the first order flow transfer link and the order state indicates that a target sub-link in the first order flow transfer link has been entered, where the third feedback message is used to indicate that the order cannot be cancelled;
the generating module is further configured to, if the current order state of the order to be cancelled is matched with the first order flow forwarding link and the order state indicates that the order does not enter the target sub-link, perform cancellation processing on the order to be cancelled, prohibit the order to be cancelled from entering the next order flow forwarding link, and generate a fourth feedback message, where the fourth feedback message is used to indicate that the order can be cancelled.
In another aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, and the at least one instruction is loaded and executed by a processor to implement the order processing method described above.
In another aspect, an order processing apparatus is provided, which includes a processor and a memory, where the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the order processing method described above.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
after receiving an order canceling request sent by a user terminal, a canceling server broadcasts the order canceling request; each service node returns a feedback message aiming at the order canceling request to a canceling server after receiving the broadcasted order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods distribution link, and the feedback message of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and finally, the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
Based on the above description, the cancellation server uses a broadcast mode to inquire whether each service node can cancel an order, that is, the cancellation server uses a parallel mode to complete the inquiry of each service node, so that the inherent dependency relationship existing between upstream and downstream service nodes is decoupled, the cancellation server can respond to the order canceling service in time and quickly after receiving the order canceling request, the processing timeliness of the order canceling service is remarkably improved, the system response time is shortened, the system performance is ensured, and the user experience is further ensured.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of an order flow provided by an embodiment of the present application;
fig. 2 is a schematic diagram of an implementation environment related to an order processing method provided in an embodiment of the present application;
fig. 3 is a flowchart of an order processing method according to an embodiment of the present application;
fig. 4 is a flowchart of an order processing method according to an embodiment of the present application;
fig. 5 is a flowchart of an order processing method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an order processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an order processing apparatus according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an order processing apparatus according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Before explaining embodiments of the present application in detail, some noun terms or abbreviations referred to in the embodiments of the present application are introduced.
Order form: in the embodiment of the application, the order refers to a shopping voucher generated by the e-commerce platform after the user shops on the e-commerce platform.
Illustratively, the order generated by the e-commerce platform is typically an electronic order. In the warehouse distribution stage, electronic orders are usually printed out to form paper orders. The information recorded in the order includes, but is not limited to: the order number, the delivery address, the name of the goods, the quantity or weight of the goods, the total price of the goods, the freight rate, the preferential price, the total price of the order, the real payment, the placing time and the like, which are not particularly limited in the embodiment of the present application.
The order flow link may be divided into an unpaid link ①, a warehouse matching link ②, and a goods delivery link ③, as an example, referring to fig. 1, that is, the order fulfillment process includes three stages.
Wherein, the non-distribution link defines the flow from the order placing of the user to the warehouse distribution; the warehouse goods distribution link limits the warehousing process from the stage of entering the order into the warehouse to the stage of leaving the goods from the warehouse; the goods distribution link limits the logistics flow from the goods delivery to the goods delivery stage.
As shown in fig. 1, each order flow segment is typically made up of multiple sub-flow segments. Illustratively, the non-distribution links include, but are not limited to: creating sub-flow links such as orders, payment orders, order pause and the like; warehouse distribution links include, but are not limited to: the sub-circulation links of printing, picking, packing, rechecking, delivering from the warehouse and the like of the bill are carried out; the goods delivery links include, but are not limited to: sorting, site, distribution, proper delivery and other sub-transferring links.
In addition, the embodiment of the application also comprises a plurality of service nodes. Illustratively, a service node may serve an order flow link. Since the order is in continuous circulation according to the flow shown in fig. 1 after the user places the order, the service node through which the order passes in the circulation process is also continuous. In addition, since the order processing sequence follows the direction of the arrow shown in fig. 1, there is a dependency relationship between the service nodes, that is, there is an inherent dependency relationship between the upstream and downstream service nodes.
Order status: in the embodiment of the present application, the order status includes, but is not limited to: the method includes, but is not limited to, not preparing a good, dispensing a good, canceling a good, and refunding a good.
The following describes an implementation environment related to the order processing method provided by the embodiment of the present application.
Referring to fig. 2, the implementation environment includes: a user terminal 201, a cancellation server 202 and at least one service node 203. Wherein the cancellation server 202 is also referred to herein as an order cancellation server.
In one possible implementation, the types of the user terminal 201 include, but are not limited to: mobile terminals and fixed terminals. As an example, mobile terminals include, but are not limited to: smart phones, tablet computers, notebook computers, electronic readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts compress standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts compress standard Audio Layer 4), etc.; the fixed terminal includes, but is not limited to, a desktop computer, which is not particularly limited in the embodiments of the present application.
Exemplarily, fig. 2 is only illustrated by taking the user terminal 201 as a smart phone.
And the cancellation server 202 is used to provide the order cancellation service for the user terminal 201. The cancellation server 202 may be an independent server, or may be a server cluster composed of a plurality of servers, which is not specifically limited in this embodiment of the present application. In addition, the user terminal 201 is usually installed with an application adapted to the e-commerce platform, so that the user can browse products, place orders, cancel orders and the like through the adapted application conveniently.
The service node 203 may also be referred to herein as a service server. Fig. 2 is only an example of three service nodes, and in an actual service processing process, the number of the service nodes 203 may include a greater number or a smaller number than that shown in fig. 2, which is not specifically limited in this embodiment of the present application.
Assuming that the three service nodes shown in fig. 2 are referred to as a first service node, a second service node, and a third service node, respectively, as an example, the three service nodes may correspond to the three order streaming links shown in fig. 1, respectively. The first business node corresponds to an uncommitted link, namely the first business node serves the uncommitted link; the second service node corresponds to a warehouse goods distribution link, namely the second service node serves the warehouse goods distribution link; the third service node corresponds to the goods delivery link, i.e. the third service node serves the goods delivery link. In addition, a dependency relationship exists among the first service node, the second service node and the third service node.
For example, the order processing method provided by the embodiment of the application can be applied to a fresh food electronic commerce platform to process order cancelling business of a user for fresh food products. For the fresh food e-commerce platform, a two-stage distributed storage system environment of a main city cabin and a front cabin is usually adopted at present, so that after a user places an order through a user terminal 201, a related order can be distributed to a micro cabin near the user, for example, a related fresh food product purchased by the user may come from a micro cabin arranged in a community near the user, and further, the product purchased by the user in a short time after placing the order can be distributed to a door.
Based on the implementation environment, the embodiment of the application mainly relates to a processing method for canceling an order request in an order circulation process. For this processing method, each service node is unchanged but the dependency between upstream and downstream service nodes is decoupled. That is, after receiving the order cancel request sent by the user terminal 201, the cancel server 202 notifies the order cancel request to each service node 203 in a broadcast manner; after receiving the broadcasted order canceling request, each service node 203 performs check judgment and generates a feedback message for the order canceling request; wherein, the feedback message of each service node gives the processing result of the order canceling request in the corresponding order flow transferring link; then, after receiving the feedback message of each service node, the cancellation server 202 determines, according to the received feedback message, whether the order cancellation request is valid, and informs the user of the final result through the user terminal 201.
Based on the above description, the cancellation server 202 queries whether each service node can cancel a corresponding order in a broadcast manner, that is, queries to each service node are completed in a parallel mode, so that an inherent dependency relationship existing between upstream and downstream service nodes is decoupled, and not only can the cancellation server 202 respond to the cancellation of the order service in time and quickly after receiving a request for canceling the order, the processing timeliness of the cancellation of the order service is remarkably improved, the system response time is shortened, the system performance is ensured, and further the user experience is ensured, but also the situation that the whole link flow is stopped in the order circulation process due to the fact that one service node is abnormal is effectively avoided.
In addition, the embodiment of the application is also provided with a monitoring system, and can respond and process abnormal conditions possibly occurring in the order canceling business execution process in time. In addition, under the condition that the order can be cancelled, each service node can automatically stop the order to continue flowing, and unnecessary fulfillment cost caused by warehouse logistics is avoided.
The order processing method provided in the embodiments of the present application is explained in detail below by the following embodiments.
Fig. 3 is a flowchart of an order processing method according to an embodiment of the present application. The method is applied to cancel a server, and referring to fig. 3, a method flow provided by the embodiment of the present application includes:
301. and receiving an order canceling request sent by the user terminal, and broadcasting the order canceling request.
302. And obtaining feedback information returned by at least one service node after receiving the order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods delivery link, and the feedback information of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link.
303. And issuing a response message aiming at the order canceling request to the user terminal based on the feedback message of at least one service node.
According to the method provided by the embodiment of the application, after the order canceling request sent by the user terminal is received, the canceling server broadcasts the order canceling request; each service node returns a feedback message aiming at the order canceling request to a canceling server after receiving the broadcasted order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods distribution link, and the feedback message of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and finally, the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
Based on the above description, the cancellation server uses a broadcast mode to inquire whether each service node can cancel an order, that is, the cancellation server uses a parallel mode to complete the inquiry of each service node, so that the inherent dependency relationship existing between upstream and downstream service nodes is decoupled, the cancellation server can respond to the order canceling service in time and quickly after receiving the order canceling request, the processing timeliness of the order canceling service is remarkably improved, the system response time is shortened, the system performance is ensured, and the user experience is further ensured.
In a possible implementation manner, for any service node, the obtaining a feedback message returned by at least one service node after receiving the order cancel request includes:
if the current order state of the order to be cancelled is not matched with a first order flow transfer link corresponding to the service node, and the first order flow transfer link is positioned behind a second order flow transfer link in the processing flow, receiving a first feedback message returned by the service node;
the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node executes cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transfer link, and forbidding the order to be cancelled to enter the next order flow transfer link;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, receiving a second feedback message returned by the service node, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, for any service node, the obtaining a feedback message returned by at least one service node after receiving the order cancel request includes:
if the current order state of the order to be cancelled is matched with a first order flow transfer link corresponding to the service node and the order state indicates that a target sub-link in the first order flow transfer link is entered, receiving a third feedback message returned by the service node, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow transferring link and the order state indicates that the target link is not entered, receiving a fourth feedback message returned by the service node; the fourth feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node performs cancellation processing on the order to be cancelled and forbids the order to be cancelled to enter a next order streaming link.
All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.
Fig. 4 is a flowchart of an order processing method according to an embodiment of the present application. The method is applied to a service node, and referring to fig. 4, a method flow provided by the embodiment of the present application includes:
401. and receiving a cancellation order request broadcast by the cancellation server, wherein the cancellation order request is sent to the cancellation server by the user terminal.
402. And generating a feedback message aiming at the order canceling request, wherein the feedback message gives a processing result of the first order streaming link corresponding to the service node on the order canceling request.
403. And returning the feedback message to the cancellation server, wherein the feedback message is used for indicating the cancellation server to issue a response message aiming at the order cancellation request to the user terminal based on the received feedback message.
Wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
According to the method provided by the embodiment of the application, after the order canceling request sent by the user terminal is received, the canceling server broadcasts the order canceling request; each service node returns a feedback message aiming at the order canceling request to a canceling server after receiving the broadcasted order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods distribution link, and the feedback message of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and finally, the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
Based on the above description, the cancellation server uses a broadcast mode to inquire whether each service node can cancel an order, that is, the cancellation server uses a parallel mode to complete the inquiry of each service node, so that the inherent dependency relationship existing between upstream and downstream service nodes is decoupled, the cancellation server can respond to the order canceling service in time and quickly after receiving the order canceling request, the processing timeliness of the order canceling service is remarkably improved, the system response time is shortened, the system performance is ensured, and the user experience is further ensured.
In one possible implementation, generating a feedback message for the cancel order request includes:
if the current order state of the order to be cancelled is not matched with the first order flow conversion link and the first order flow conversion link is positioned behind a second order flow conversion link in the processing flow, executing cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow conversion link, forbidding the order to be cancelled to enter the next order flow conversion link, and generating a first feedback message, wherein the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, generating a second feedback message, where the second feedback message is used to indicate that the order cannot be cancelled.
In one possible implementation, generating the feedback message for the cancel order request includes:
if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that a target sub-link in the first order flow conversion link is entered, generating a third feedback message, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that the order to be cancelled does not enter the target sub-link, executing cancellation processing on the order to be cancelled, prohibiting the order to be cancelled from entering the next order flow conversion link, and generating a fourth feedback message, wherein the fourth feedback message is used for indicating that the order can be cancelled.
All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.
It should be noted that descriptions such as first, second, third, and fourth appearing in the following embodiments are only for distinguishing different objects, and do not constitute any other limitation.
Fig. 5 is a flowchart of an order processing method according to an embodiment of the present application. The interaction subject of the method is the user terminal, the cancel server and the service node. Taking the three order flow links shown in fig. 1 as an example, referring to fig. 5, the method provided by the embodiment of the present application includes:
501. the user terminal sends an order canceling request to the canceling server.
In the embodiment of the application, the user can execute order cancellation operation on an application installed on the user terminal, so as to trigger the user terminal to send an order cancellation request to the cancellation server through the application. For example, a cancel button for each order may be displayed on the application to facilitate the user in canceling the order. Wherein, the application program mentioned here refers to a software client of the e-commerce platform.
That is, after receiving an order cancel operation performed by a user, the user terminal sends an order cancel request to the cancel server in response to the order cancel operation. Illustratively, the cancel order request includes, but is not limited to: the order number of the order to be cancelled, the reason for canceling the order, the request initiation time, the user identifier of the request initiator, and the like, which are not specifically limited in the embodiment of the present application.
In one possible implementation, the user may cancel the order either before or after payment. Among the reasons for canceling an order prior to payment are, but not limited to: unwanted purchases, errors in information filling, stock out of the seller, and other reasons. Reasons for canceling an order after payment include, but are not limited to: x days unpruned refunds, discrepancy in size/color/pattern/style/material to item description, defects, quality problems, breakage/stain/distortion/damage upon receipt of the item, counterfeit brands, unscheduled deliveries, misdeliveries, and the like.
502. And after receiving the order canceling request sent by the user terminal, the canceling server broadcasts the order canceling request.
As an example, after receiving the order cancel request, the cancel server may place the received order cancel request in a cancel message queue, and sequentially process each order cancel request in the cancel message queue according to a first-in first-out order. In addition, the cancellation server can also store the received order cancellation request to a background database for data storage.
In the embodiment of the application, the cancellation server inquires whether each service node can cancel an order or not in a broadcasting mode, namely, the inquiry of each service node is completed in a parallel mode, so that the inherent dependency relationship existing between upstream and downstream service nodes is decoupled, the cancellation server can respond to the order canceling service timely and quickly when receiving the order canceling request, the processing efficiency of a system can be effectively improved, the response time of the system to the order canceling service is shortened, and the user experience is further ensured.
In addition, because the data formats adopted between the cancellation server and each service node may be different, before the cancellation server broadcasts the order cancellation request, the cancellation server may further process the order cancellation request to convert the order cancellation request into the data format suitable for each service node.
In addition, the cancel server needs to periodically perform a cleaning process on the stored cancel order request. The data cleaning is a procedure for finding and correcting recognizable errors in the data, and the step of cleaning is performed by selecting a proper method aiming at obvious error values, missing values, abnormal values and suspicious data found in the data examination process, so that dirty data are changed into clean data, and subsequent statistical analysis is facilitated to obtain a reliable conclusion. Of course, the data cleaning may further include deleting the duplicate records, checking data consistency, and the like, which is not specifically limited in this embodiment of the application.
503. And the at least one service node receiving the broadcast returns a feedback message for the order cancellation request to the cancellation server.
In the circulation process of the order to be cancelled, after each service node receives the order cancellation request broadcast by the cancellation server, the service node performs checking judgment according to internal logic and returns a feedback message to the cancellation server. Wherein, the feedback message of each service node gives the processing result of the order canceling request in the corresponding order streaming link.
Illustratively, each service node needs to be checked and judged by three types: firstly, the order to be cancelled has not been forwarded to the service node, namely the order to be cancelled has not entered the order forwarding link corresponding to the service node; secondly, the order to be cancelled has been streamed to the service node, namely the order to be cancelled enters an order streaming link corresponding to the service node; and thirdly, the order to be cancelled passes through the service node, namely the order to be cancelled passes through an order streaming link corresponding to the service node.
Taking the order flow conversion link corresponding to the service node as the first order flow conversion link, and matching the current order state of the order to be cancelled with the second order flow state as an example,
then, the order to be cancelled is not forwarded to the service node, that is, the first order forwarding link is inconsistent with the second order forwarding link, and the first order forwarding link is located after the second order forwarding link in the processing flow. For example, in this case, the first order flow link may be a goods distribution link, and the second order flow link may be an uncommitted link, and accordingly, the current order status of the to-be-cancelled order is uncommitted. That is, the present embodiment further includes step 5031 described below.
5031. After the order to be cancelled enters the first order flow transferring link, the service node executes cancellation processing on the order to be cancelled, prohibits the order to be cancelled from entering the next order flow transferring link, and generates a first feedback message, wherein the first feedback message is used for indicating that the order can be cancelled.
For this step, since the order to be cancelled has not yet been forwarded to the service node, the service node will feed back to the cancellation server that the order can be intercepted after receiving the order cancellation request broadcast by the cancellation server. In another expression, when the order to be cancelled is transferred to the service node, the service node performs cancellation processing on the order to be cancelled, and automatically stops subsequent transfer of the order to be cancelled, that is, stops the order to be cancelled from being continuously transferred, so as to avoid unnecessary fulfillment cost caused by warehouse logistics.
Then, the order to be cancelled has passed through the service node, that is, the first order flow transfer link is inconsistent with the second order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow. For example, for such a situation, the first order flow link may be an uncommitted link, the second order flow link may be a warehouse distribution link, and accordingly, the current order status of the order to be cancelled is in distribution. That is, the embodiment of the present application further includes the following step 5032.
5032. The service node generates a second feedback message, wherein the second feedback message is used for indicating that the order is not cancelable.
For this step, since the order to be cancelled has already passed through the service node, the service node will feed back to the cancellation server that the order cannot be intercepted after receiving the order cancellation request broadcast by the cancellation server, and does not perform any operation.
Then, the order to be cancelled is forwarded to the service node, that is, the first order forwarding link is consistent with the second order forwarding link. For the situation, because the order to be cancelled is streamed to the service node, the service node performs internal check judgment after receiving the order cancellation request broadcast by the cancellation server, and determines whether the order can be intercepted; if the order cannot be intercepted, then step 5033 is performed; if the order can be intercepted, step 5034 is performed as follows.
5033. And if the current order state indicates that the target sub-link in the first order flow conversion link is entered, the service node generates a third feedback message, wherein the third feedback message is used for indicating that the order cannot be cancelled.
For this step, if the order to be cancelled has entered the target sub-link, after receiving the order cancellation request broadcast by the cancellation server, the service node will feed back to the cancellation server that the order cannot be intercepted, and does not perform any operation. Taking the first order flow link as a warehouse goods distribution link as an example, the target sub-link may be warehouse-out, that is, the order arrives at the warehouse-out node, which does not support the user to cancel the order.
5034. And if the current order state indicates that the order does not enter the target sub-link, the service node executes cancellation processing on the order to be cancelled, prohibits the order to be cancelled from entering the next order streaming link, and generates a fourth feedback message, wherein the fourth feedback message is used for indicating that the order can be cancelled.
For this step, after receiving the order cancellation request broadcast by the cancellation server, the service node feeds back to the cancellation server that the order can be intercepted. Namely, the service node executes cancellation processing on the order to be cancelled and automatically stops subsequent circulation of the order to be cancelled, namely, the service node stops the order to be cancelled and continues circulation of the order to be cancelled, so that unnecessary performance cost caused by warehouse logistics is avoided.
In addition, because the data formats adopted between the cancellation server and each service node may be different, each service node may further process the feedback message before returning the feedback message, so as to convert the feedback message into the data format adapted to the cancellation server.
Through the steps, the check logic and the feedback mechanism of each service node for the order cancel request can be clarified. For example, in the embodiment of the present application, an order number is used as a unique identification code of an order to be cancelled between a cancellation server and each service node, which is not specifically limited in the embodiment of the present application.
504. And the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
And the cancellation server performs comprehensive judgment aiming at the feedback messages returned by each service node so as to finally determine whether the order cancellation request is valid or not and inform a user of a final result through the user terminal. Exemplarily, if at least one of the received feedback messages indicates that the order can be cancelled, the cancellation server determines that the order cancellation request is valid, and issues a response message of order cancellation to the user terminal; otherwise, the cancellation server issues a response message that the order cannot be cancelled to the user terminal.
In addition, for the case that the order cannot be cancelled, the cancellation server may also feed back the reason why the order cannot be cancelled to the user terminal, which is not specifically limited in this embodiment of the present application.
505. And the user terminal displays the response message issued by the cancellation server.
In this embodiment, the user terminal may display the response message through a software client of the e-commerce platform. For example, if the software client is in a foreground operating state, the response message is displayed through the software client; or, if the software client is in the background running state, the push message is partially displayed through a system message notification bar, and after a triggering operation of a user on a response message in a system notification form is received, the response message is displayed in detail through the software client. Illustratively, push messages include, but are not limited to, teletext messages, plain text messages, and the like.
In another possible implementation manner, in addition to the cancellation server and the service node, the implementation environment shown in fig. 2 may also be configured with a monitoring system to deal with an abnormal situation that may occur during the execution of the cancellation order service. Illustratively, in the process of canceling data transmission between the server and each service node, the monitoring system is responsible for monitoring abnormal data receiving and transmitting conditions; when the monitoring system monitors that an abnormal data transceiving condition occurs, for example, a certain service node does not perform message feedback on the broadcasted order canceling request due to the existence of an abnormality, the monitoring system can perform an alarm and perform response processing on the abnormal data transceiving condition.
The method provided by the embodiment of the application has at least the following beneficial effects:
in the embodiment of the application, the cancellation server inquires whether each service node can cancel a corresponding order in a broadcasting mode, namely, the inquiry of each service node is completed in a parallel mode, so that the inherent dependency relationship existing between upstream and downstream service nodes is decoupled, the cancellation server can respond to the order canceling service in time and quickly after receiving the order canceling request, the processing timeliness of the order canceling service is obviously improved, the system response time is shortened, the system performance is ensured, the user experience is further ensured, and the condition that the whole link flow is stopped in the order circulation process due to the fact that one service node is abnormal is effectively avoided.
In addition, the embodiment of the application is also provided with a monitoring system, and can respond and process abnormal conditions possibly occurring in the order canceling business execution process in time. In addition, under the condition that the order can be cancelled, each service node can automatically stop the order to continue flowing, and unnecessary fulfillment cost caused by warehouse logistics is avoided.
Fig. 6 is a schematic structural diagram of an order processing apparatus according to an embodiment of the present application. The apparatus is applied to cancel a server, and referring to fig. 6, the apparatus includes:
a first receiving module 601 configured to receive an order cancel request sent by a user terminal;
a broadcasting module 602 configured to broadcast the cancel order request;
a second receiving module 603, configured to obtain a feedback message returned by at least one service node after receiving the order cancellation request, where one service node serves an order flow transfer link, the order flow transfer link at least includes an uncommitted link, a warehouse goods transfer link, and a goods delivery link, and the feedback message of each service node gives a processing result of the order cancellation request in the corresponding order flow transfer link;
a sending module 604, configured to issue a response message for the order cancel request to the user terminal based on the feedback message of the at least one service node.
The device provided by the embodiment of the application broadcasts the order canceling request after receiving the order canceling request sent by the user terminal; each service node returns a feedback message aiming at the order canceling request to a canceling server after receiving the broadcasted order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods distribution link, and the feedback message of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and finally, the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
Based on the above description, it can be seen that in the embodiments of the present application, a broadcast manner is adopted to inquire whether each service node can cancel an order, that is, the inquiry on each service node is completed in a parallel mode, so that an inherent dependency relationship existing between upstream and downstream service nodes is decoupled, and a cancellation server can respond to an order cancellation service in time and quickly after receiving an order cancellation request, thereby significantly improving the processing timeliness of the order cancellation service, shortening the system response time, ensuring the system performance, and further ensuring the user experience.
In a possible implementation manner, for any service node, the second receiving module 603 is further configured to receive a first feedback message returned by the service node if the current order state of the order to be cancelled is not matched with the first order flow transfer link corresponding to the service node, and the first order flow transfer link is located after the second order flow transfer link in the processing flow;
the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node executes cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transfer link, and forbidding the order to be cancelled to enter the next order flow transfer link;
the second receiving module 603 is further configured to receive a second feedback message returned by the service node if the current order state of the order to be cancelled does not match the first order flow transfer link and the first order flow transfer link is located before the second order flow transfer link in the processing flow, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, for any service node, the second receiving module 603 is further configured to receive a third feedback message returned by the service node if a current order state of an order to be cancelled matches a first order flow transfer link corresponding to the service node, and the order state indicates that a target sub-link in the first order flow transfer link has been entered, where the third feedback message is used to indicate that the order cannot be cancelled;
the second receiving module 603 is further configured to receive a fourth feedback message returned by the service node if the current order state of the order to be cancelled matches the first order streaming link and the order state indicates that the target sub-link is not entered; the fourth feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node performs cancellation processing on the order to be cancelled and forbids the order to be cancelled to enter a next order streaming link.
All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.
Fig. 7 is a schematic structural diagram of an order processing apparatus according to an embodiment of the present application. Referring to fig. 7, the present application is applied to a service node, referring to fig. 7, the apparatus includes:
a receiving module 701 configured to receive a cancellation order request broadcasted by a cancellation server, where the cancellation order request is sent to the cancellation server by a user terminal;
a generating module 702, configured to generate a feedback message for the order cancel request, where the feedback message gives a processing result of the first order forwarding segment corresponding to the service node on the order cancel request;
a sending module 703 configured to return the feedback message to the cancellation server, where the feedback message is used to instruct the cancellation server to issue a response message for the order cancellation request to the user terminal based on the received feedback message;
wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
The device provided by the embodiment of the application broadcasts the order canceling request after receiving the order canceling request sent by the user terminal; each service node returns a feedback message aiming at the order canceling request to a canceling server after receiving the broadcasted order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods distribution link, and the feedback message of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link; and finally, the cancellation server issues a response message aiming at the order cancellation request to the user terminal based on the feedback message of at least one service node.
Based on the above description, it can be seen that in the embodiments of the present application, a broadcast manner is adopted to inquire whether each service node can cancel an order, that is, the inquiry on each service node is completed in a parallel mode, so that an inherent dependency relationship existing between upstream and downstream service nodes is decoupled, and a cancellation server can respond to an order cancellation service in time and quickly after receiving an order cancellation request, thereby significantly improving the processing timeliness of the order cancellation service, shortening the system response time, ensuring the system performance, and further ensuring the user experience.
In a possible implementation manner, the generating module 702 is further configured to, if the current order state of the order to be cancelled is not matched with the first order flow transferring link and the first order flow transferring link is located after the second order flow transferring link in the processing flow, perform cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transferring link, prohibit the order to be cancelled from entering the next order flow transferring link, and generate a first feedback message, where the second order flow transferring link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled;
the generating module 702 is further configured to generate a second feedback message if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, where the second feedback message is used to indicate that the order cannot be cancelled.
In a possible implementation manner, the generating module 702 is further configured to generate a third feedback message if a current order state of the order to be cancelled matches the first order flow transfer link and the order state indicates that a target sub-link in the first order flow transfer link has been entered, where the third feedback message is used to indicate that the order cannot be cancelled;
the generating module 702 is further configured to, if the current order state of the order to be cancelled matches the first order flow forwarding link and the order state indicates that the order does not enter the target sub-link, execute cancellation processing on the order to be cancelled, prohibit the order to be cancelled from entering the next order flow forwarding link, and generate a fourth feedback message, where the fourth feedback message is used to indicate that the order may be cancelled.
All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.
It should be noted that: in the order processing apparatus provided in the above embodiment, only the division of the functional modules is illustrated when processing an order, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to complete all or part of the functions described above. In addition, the order processing apparatus and the order processing method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.
Fig. 8 is a schematic structural diagram of an order processing apparatus provided in this embodiment of the present application, where the apparatus 800 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 801 and one or more memories 802, where the memory 802 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 801 to implement the order processing method provided in each method embodiment described above. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.
In an exemplary embodiment, a computer-readable storage medium, such as a memory, is also provided that includes instructions executable by a processor in a terminal to perform the order processing method in the above-described embodiments. For example, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (10)

1. An order processing method is applied to a cancellation server, and comprises the following steps:
receiving an order canceling request sent by a user terminal, and broadcasting the order canceling request;
obtaining feedback information returned by at least one service node after receiving the order canceling request, wherein one service node serves an order flow transfer link, the order flow transfer link at least comprises an uncommitted link, a warehouse goods transfer link and a goods delivery link, and the feedback information of each service node gives a processing result of the order canceling request in the corresponding order flow transfer link;
and issuing a response message aiming at the order canceling request to the user terminal based on the feedback message of the at least one service node.
2. The method according to claim 1, wherein for any service node, said obtaining a feedback message returned by at least one service node after receiving the order cancel request comprises:
if the current order state of the order to be cancelled is not matched with a first order flow transfer link corresponding to the service node, and the first order flow transfer link is positioned behind a second order flow transfer link in the processing flow, receiving a first feedback message returned by the service node;
the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node executes cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow transfer link, and forbidding the order to be cancelled to enter the next order flow transfer link;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, receiving a second feedback message returned by the service node, where the second feedback message is used to indicate that the order cannot be cancelled.
3. The method according to claim 1, wherein for any service node, said obtaining a feedback message returned by at least one service node after receiving the order cancel request comprises:
if the current order state of the order to be cancelled is matched with a first order flow transfer link corresponding to the service node and the order state indicates that a target sub-link in the first order flow transfer link is entered, receiving a third feedback message returned by the service node, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow transferring link and the order state indicates that the target link is not entered, receiving a fourth feedback message returned by the service node; the fourth feedback message is used for indicating that the order can be cancelled, and the order cancellation request is used for indicating that the service node performs cancellation processing on the order to be cancelled and forbids the order to be cancelled to enter a next order streaming link.
4. An order processing method applied to a service node, the method comprising:
receiving an order canceling request broadcasted by a canceling server, wherein the order canceling request is sent to the canceling server by a user terminal;
generating a feedback message aiming at the order canceling request, wherein the feedback message gives a processing result of a first order streaming link corresponding to the service node on the order canceling request;
returning the feedback message to the cancellation server, where the feedback message is used to instruct the cancellation server to issue a response message for the order cancellation request to the user terminal based on the received feedback message;
wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
5. The method of claim 4, wherein generating the feedback message for the cancel order request comprises:
if the current order state of the order to be cancelled is not matched with the first order flow conversion link and the first order flow conversion link is positioned behind a second order flow conversion link in the processing flow, executing cancellation processing on the order to be cancelled after the order to be cancelled enters the first order flow conversion link, forbidding the order to be cancelled to enter the next order flow conversion link, and generating a first feedback message, wherein the second order flow conversion link is matched with the order state; the first feedback message is used for indicating that the order can be cancelled;
or, if the current order state of the order to be cancelled does not match the first order flow transfer link, and the first order flow transfer link is located before the second order flow transfer link in the processing flow, generating a second feedback message, where the second feedback message is used to indicate that the order cannot be cancelled.
6. The method of claim 4, wherein generating the feedback message for the cancel order request comprises:
if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that a target sub-link in the first order flow conversion link is entered, generating a third feedback message, wherein the third feedback message is used for indicating that the order cannot be cancelled;
or, if the current order state of the order to be cancelled is matched with the first order flow conversion link and the order state indicates that the order to be cancelled does not enter the target sub-link, executing cancellation processing on the order to be cancelled, prohibiting the order to be cancelled from entering the next order flow conversion link, and generating a fourth feedback message, wherein the fourth feedback message is used for indicating that the order can be cancelled.
7. An order processing apparatus applied to a cancellation server, the apparatus comprising:
the first receiving module is configured to receive an order canceling request sent by a user terminal;
a broadcast module configured to broadcast the cancel order request;
a second receiving module, configured to obtain a feedback message returned by at least one service node after receiving the order cancellation request, where one service node serves an order flow link, the order flow link at least includes an uncommitted link, a warehouse goods distribution link and a goods distribution link, and the feedback message of each service node gives a processing result of the order cancellation request in the corresponding order flow link;
and the sending module is used for sending a response message aiming at the order canceling request to the user terminal based on the feedback message of the at least one service node.
8. An order processing apparatus, applied to a service node, the apparatus comprising:
the receiving module is configured to receive a cancellation order request broadcasted by a cancellation server, wherein the cancellation order request is sent to the cancellation server by a user terminal;
a generating module configured to generate a feedback message for the order cancellation request, where the feedback message gives a processing result of the first order streaming link corresponding to the service node on the order cancellation request;
a sending module configured to return the feedback message to the cancellation server, where the feedback message is used to instruct the cancellation server to issue a response message for the order cancellation request to the user terminal based on the received feedback message;
wherein, a business node serves an order flow transfer link, and the order flow transfer link at least comprises an uncommitted link, a warehouse goods distribution link and a goods distribution link.
9. A computer-readable storage medium having stored therein at least one instruction, which is loaded and executed by a processor to implement the order processing method of any one of claims 1 to 3; or, the order processing method of any of claims 4 to 6.
10. An order processing apparatus, characterized in that the apparatus comprises a processor and a memory, the memory having stored therein at least one instruction, the at least one instruction being loaded and executed by the processor to implement the order processing method according to any one of claims 1 to 3; or, the order processing method of any of claims 4 to 6.
CN201911349172.9A 2019-12-24 2019-12-24 Order processing method, device, storage medium and equipment Pending CN111127157A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911349172.9A CN111127157A (en) 2019-12-24 2019-12-24 Order processing method, device, storage medium and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911349172.9A CN111127157A (en) 2019-12-24 2019-12-24 Order processing method, device, storage medium and equipment

Publications (1)

Publication Number Publication Date
CN111127157A true CN111127157A (en) 2020-05-08

Family

ID=70500786

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911349172.9A Pending CN111127157A (en) 2019-12-24 2019-12-24 Order processing method, device, storage medium and equipment

Country Status (1)

Country Link
CN (1) CN111127157A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112258266A (en) * 2020-10-10 2021-01-22 同程网络科技股份有限公司 Distributed order processing method, device, equipment and storage medium
CN111724106B (en) * 2020-05-22 2021-03-30 上海寻梦信息技术有限公司 Order canceling processing method, order system, electronic equipment and storage medium
CN112837013A (en) * 2021-02-02 2021-05-25 拉扎斯网络科技（上海）有限公司 Service processing method, device and equipment
CN112990847A (en) * 2021-02-01 2021-06-18 五八到家有限公司 Aging data monitoring method, device, equipment and medium
CN113762822A (en) * 2020-06-30 2021-12-07 北京京东振世信息技术有限公司 Order processing method and device
CN113780926A (en) * 2021-02-19 2021-12-10 北京京东振世信息技术有限公司 Article order processing method, device and system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003242382A (en) * 2001-12-10 2003-08-29 Tomimaro Kitaura Material procurement and transaction system
CN106296352A (en) * 2016-08-04 2017-01-04 多点生活(中国)网络科技有限公司 Order data treating method and apparatus
US20170132628A1 (en) * 2015-11-11 2017-05-11 Leauto Intelligent Technology (Beijing) Co. Ltd Order cancellation processing system, processing method and business support system
CN108428074A (en) * 2017-02-13 2018-08-21 北京京东尚科信息技术有限公司 A kind of processing method and processing device cancelled an order in order honours an agreement flow
CN109615361A (en) * 2018-11-16 2019-04-12 北京每日优鲜电子商务有限公司 Payment control method, device, equipment and the storage medium of automatically vending system
CN110503512A (en) * 2019-07-19 2019-11-26 北京三快在线科技有限公司 Order processing method, apparatus, electronic equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003242382A (en) * 2001-12-10 2003-08-29 Tomimaro Kitaura Material procurement and transaction system
US20170132628A1 (en) * 2015-11-11 2017-05-11 Leauto Intelligent Technology (Beijing) Co. Ltd Order cancellation processing system, processing method and business support system
CN106296352A (en) * 2016-08-04 2017-01-04 多点生活(中国)网络科技有限公司 Order data treating method and apparatus
CN108428074A (en) * 2017-02-13 2018-08-21 北京京东尚科信息技术有限公司 A kind of processing method and processing device cancelled an order in order honours an agreement flow
CN109615361A (en) * 2018-11-16 2019-04-12 北京每日优鲜电子商务有限公司 Payment control method, device, equipment and the storage medium of automatically vending system
CN110503512A (en) * 2019-07-19 2019-11-26 北京三快在线科技有限公司 Order processing method, apparatus, electronic equipment and storage medium

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111724106B (en) * 2020-05-22 2021-03-30 上海寻梦信息技术有限公司 Order canceling processing method, order system, electronic equipment and storage medium
CN113762822A (en) * 2020-06-30 2021-12-07 北京京东振世信息技术有限公司 Order processing method and device
CN113762822B (en) * 2020-06-30 2023-09-26 北京京东振世信息技术有限公司 Method and device for processing order
CN112258266A (en) * 2020-10-10 2021-01-22 同程网络科技股份有限公司 Distributed order processing method, device, equipment and storage medium
CN112258266B (en) * 2020-10-10 2023-09-26 同程网络科技股份有限公司 Distributed order processing method, device, equipment and storage medium
CN112990847A (en) * 2021-02-01 2021-06-18 五八到家有限公司 Aging data monitoring method, device, equipment and medium
CN112837013A (en) * 2021-02-02 2021-05-25 拉扎斯网络科技（上海）有限公司 Service processing method, device and equipment
CN112837013B (en) * 2021-02-02 2023-08-11 拉扎斯网络科技（上海）有限公司 Service processing method, device and equipment
CN113780926A (en) * 2021-02-19 2021-12-10 北京京东振世信息技术有限公司 Article order processing method, device and system

Similar Documents

Publication Publication Date Title
CN111127157A (en) Order processing method, device, storage medium and equipment
CN107230120B (en) Order information processing method, device and system
CN108876497B (en) Resource transfer method and device and third-party server
CN105096015B (en) Commodity object information processing method and system
WO2017032226A1 (en) Returns information processing method and apparatus
CN108269042B (en) Logistics supply chain management system and method
US20140200980A1 (en) System and method for mediating transactions among a plurality of social commerce businesses
CN104143157A (en) Order matching method and device
CN101295391A (en) On-line transaction method and on-line transaction system
CN111277625A (en) E-commerce platform order pushing method and system
WO2018153277A1 (en) Method for obtaining logistics document information, and related device
WO2021073477A1 (en) Method and apparatus for supporting modification of consignee information
CN106600193A (en) TPS system
CN113379258A (en) Inventory management method and device
CN112308475B (en) Customs clearance system, customs clearance method, customs clearance device and electronic equipment
CN115357766B (en) Data matching method and related device
CN104240038A (en) Management system and management method of sales quality guarantee
CN112418748A (en) Offline reconciliation method and system for e-commerce inventory under distributed architecture
CN110163402B (en) Method and device for determining stock quantity units in order
CN105719174A (en) Website platform docking system and method
CN114841769A (en) Parcel information updating method and device
US20180357585A1 (en) System and method for supply chain management
CN111507808A (en) Commodity pre-selling system based on mobile internet
CN110866721A (en) Cross-border service processing method, system, electronic equipment and readable storage medium
CN110852682A (en) Package processing method and device, electronic equipment and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20200508

WD01 Invention patent application deemed withdrawn after publication