Order information and status flow

Pull order service: It is to pull the order generated by the front-end server to the back-end production library (generally known as the internal ERP library), which is required to be fast and can not have a backlog of orders.

Split order service: Split order is divided into two parts, pre-split order will be carried out in front order, that is, different goods are divided into piles and marked according to the rules for subsequent split order service. Unorder is carried out after the completion of payment, and it will be divided according to the attributes of the goods, the requirements of the distribution conditions or whether the goods are out of stock and other reasons. At this time, the goods are divided into piles, and then sub-orders are generated. The relevant amount information of the general order main table will be recalculated according to the goods of the sub-order. There are a lot of rules, this article will not comb deeply.

Order placement service: The WMS system is separate from the OMS system or ERP, and if a third-party warehouse system is used, the transfer of data is essential. As for the design of the document delivery and status return system, it is carried out in the way of scheduled task + message queue. Orders can be issued according to the WMS system issued by the warehouse, or they can be passed to the partner merchants through the open platform for shipment. After placing an order on Jingdong, you will clearly see a system message similar to the following: "Your order has been allocated to XXX warehouse..." To the user.

Order blocking service, after the user creates an order or pays, before the order is opened, there should also be an order blocking service. The purpose of this service is to make the judgment of malicious orders, and for the review of special orders, it depends on the relevant rule Settings. When the order is blocked, the order may be forced to cancel in order to release inventory or avoid the user to brush the order, this process is sometimes called the order rollback period, I understand it is similar to the recycle bin.

Pending shipment: Orders in this status may not have been sent to the warehouse, or they may have been sent. But at this point, orders can be canceled.

Looking at the figure above, each state of an order can theoretically be cancelled (user active or passive) before it is shipped.

After the order is cancelled, the status changes to the cancelled state, which I understand to be one of the final states of the order (cancelled, invalid, closed or signed).

If the cancellation of the order has not occurred, it may be made on the basis of payment or non-payment, that is, it does not involve the refund of the user; If an order is opened, the order is to be cancelled according to the sub-order, and whether to judge whether it can be cancelled in the cancellation process, which involves information such as promotion or giveaway or order classification, the details are not said.

Add an order status here, that is, what is the status of the parent order after the order is dismantled? Generally set to invalid order, this is also an end state of the order.

Order received: This status may be defined in WMS system as pending sorting or some other name, in the upper system is issued or pending shipment. At this time, the order begins to flow in the WMS system, but the user generally will not pay attention to your specific performance node, he is most concerned about your delivery or not sent.

Sorting/packaging/delivery: these states are the operation process of warehousing or merchants, the delivery speed is the user's concern, the general upper system only focuses on when to ship, if there is no timely operation will be reminded. Although these status changes are in the warehouse, I think they need to be synchronized to the OMS system, so as to analyze the timeliness of orders and be helpful for after-sales service.

Under normal circumstances, when the order has not started sorting, the user or the system can still cancel, depending on how the order cancellation process is designed.

Shipped: When the warehouse or merchant operates the shipment, the order will enter the next state process, that is, the logistics state. At this time, the order has been packaged and completed, and the order is not allowed to be canceled at this time, if the user does not want to, then it can only be intercepted for rejection processing.

Logistics status information: there are mainly four nodes, "received -> in transit -> Sent -> Signed", which are obtained by connecting with third-party logistics information. These status information are generally separated from the main status of the order and recorded in the logistics list in the order information. When docking with logistics companies, they will have a lot of status codes, which show users, which do not show users can be screened according to the situation. However, it is best to be consistent with the official logistics, because some users will go to the express official website to inquire, and if there is an anomaly, they will complain.