one. Introduction to the split-order and delivery business

For the business introduction of the split-order project, you can refer to the gang post:

http://bbs.taobao.com/catalog/thread/567766-261212808.htm?spm=0.0.0.0.LJ4sdF

##two. Process introduction

##3. Focus

#1. Impact of order management##(1) Orders that are split and shipped are more than ordinary ones The order has a

partial delivery

status SELLER_CONSIGNED_PART and whether it is multiple orders is marked is_part_consign

Developers need to pay attention to:

##a.

In order to prevent developers from missing orders, search for

"Unshipped orders" will "partial delivery"# The orders of ## are also searched, and the developer needs to make a judgment on the is_part_consign of the returned order

b. In the message service, sub-orders will also send separate messages. We hope developers will pay attention to

c. Associated sub-order numbers (bind_oid), these associated sub-orders must be shipped together with the current sub-order to be shipped successfully. For example: you bought a computer on the page and got a 3-year warranty as a gift. Warranty service is the associated sub-order of this computer. Warranty service requires the computer to be shipped together

(2) Sub-orders are independent The Logistics and related information, including bind_oid (associated sub-order number), consign_time (shipping time), shipping_type (shipping type), logistics_company (logistics company), invoice_no (sub-order waybill number), Need to be processed separately in ERP

2. Impact on delivery management

(1) Logistics delivery must pass in the parent-child order and the split order mark

(2) Logistics order query and logistics flow information query must pass in the parent and child order number

(3) taobao.logistics. dummy.send (no need for logistics (virtual) delivery processing) does not support split orders for delivery

3. Impact of reconciliation

Reconciliation is calculated based on the final status of the order and has no impact for the time being.

FAQ

• There is no FAQ about this document