1688 KA Order Fulfillment Flow: From Creation to After-Sales

API Endpoint: /alibaba/ka/order/page
Status Enum: PoolOrderStatusEnum
Last Updated: May 28, 2026

📋 Order Status Overview

Status Code	Enum Name	Chinese	Description
1	`WAITING_FOR_PAYMENT`	待付款	Awaiting buyer payment
2	`PAYMENT_IN_PROGRESS`	支付中	Payment being processed
3	`WAITING_FOR_PROCURED`	待采购	Paid, awaiting procurement
7	`PROCUREMENT_FAILED`	采购失败	Procurement failed
4	`WAITING_FOR_SENT`	待发货	Awaiting shipment
5	`SENT`	已发货	Shipped by seller
10	`FINISHED`	已完成	Order completed
18	`REFUNDING`	退款/售后中	Refund/after-sales in progress
20	`REFUND_FINISHED`	售后完成	After-sales completed
-1	`CANCEL`	已取消	Order cancelled

🔄 Main Business Flows

Flow 1: Normal Fulfillment (Success)

WAITING_FOR_PAYMENT(1) ← Order placed
  ↓
WAITING_FOR_PROCURED(3) ← Payment successful
  ↓
WAITING_FOR_SENT(4) ← Procurement completed
  ↓
SENT(5) ← Seller shipped
  ↓
FINISHED(10) ← Order completed

Time Requirements: Each phase typically takes 1-7 days depending on supplier

Flow 2: Payment Exception Flow

WAITING_FOR_PAYMENT(1)
  ↓
PAYMENT_IN_PROGRESS(2) ← Start payment
  ↓ (Payment successful)
WAITING_FOR_PROCURED(3)

OR

PAYMENT_IN_PROGRESS(2)
  ↓ (Payment failed)
WAITING_FOR_PAYMENT(1) ← Retry payment

Flow 3: Procurement Failure Flow

WAITING_FOR_PROCURED(3)
  ↓
PROCUREMENT_FAILED(7) ← Supplier out of stock/cannot procure
  ↓
CANCEL(-1) ← Order cancelled and refunded

OR

PROCUREMENT_FAILED(7)
  ↓ (Re-procurement successful)
WAITING_FOR_SENT(4)

Flow 4: Order Cancellation Flow

Orders can be cancelled in the following statuses:

Cancellable Statuses:
- WAITING_FOR_PAYMENT(1)
- PAYMENT_IN_PROGRESS(2)
- WAITING_FOR_PROCURED(3)
- PROCUREMENT_FAILED(7)
- WAITING_FOR_SENT(4)

After cancellation → CANCEL(-1)

Non-Cancellable Statuses:

SENT(5) - Already shipped

FINISHED(10) - Completed

REFUNDING(18) - Refunding

REFUND_FINISHED(20) - After-sales completed

Flow 5: Refund/After-Sales Flow

Any fulfillment status
  ↓
REFUNDING(18) ← Apply for refund/after-sales
  ↓
REFUND_FINISHED(20) ← Refund/after-sales completed

OR

REFUNDING(18)
  ↓ (Refund failed/cancelled)
Revert to original status

OR

Any status
  ↓
CANCEL(-1) ← Direct order cancellation

Allowed initial statuses for refund:

WAITING_FOR_SENT(4) - Awaiting shipment

SENT(5) - Shipped

FINISHED(10) - Completed

📊 Status Transition Rules Matrix

From \ To	-1	0	1	2	3	4	5	6	7	10	18	20
1 (WAIT_PAYMENT)	✓	✓	-	✓	✓	✓	✓	✓	-	✓	-	-
2 (PAY_PROGRESS)	✓	✓	✓	-	✓	✓	✓	✓	✓	✓	-	-
3 (WAIT_PROCURE)	✓	-	✓	✓	-	✓	-	-	✓	-	-	-
4 (WAIT_SENT)	✓	-	-	-	-	-	✓	✓	-	✓	✓	-
5 (SENT)	✓	-	-	-	-	-	-	✓	-	✓	✓	-
7 (PROC_FAIL)	✓	-	-	-	-	-	-	-	-	-	-	-
10 (FINISHED)	-	-	-	-	-	-	-	-	-	-	-	-
18 (REFUNDING)	✓	-	-	-	-	-	-	-	-	-	-	✓
20 (REFUND_DONE)	✓	-	-	-	-	-	-	-	-	-	-	-

Legend: ✓ = Allowed transition | - = Not allowed

🔍 Customer-Facing Status Descriptions

Fields Visible to Customers

{
  "orderStatus": 4,
  "orderStatusDesc": "WAITING_FOR_SENT",
  "subOrderList": [
    {
      "subOrderStatus": 4,
      "subOrderStatusDesc": "WAITING_FOR_SENT"
    }
  ]
}

Status Description Mapping

orderStatus	orderStatusDesc	Customer Understanding
1	`WAITING_FOR_PAYMENT`	Awaiting your payment
2	`PAYMENT_IN_PROGRESS`	Your payment is being processed
3	`WAITING_FOR_PROCURED`	Payment successful, procuring goods
4	`WAITING_FOR_SENT`	Goods procured, awaiting shipment
5	`SENT`	Goods shipped, in transit
6	`INBOUND`	Goods arrived at warehouse
7	`PROCUREMENT_FAILED`	Procurement failed, please contact support
10	`FINISHED`	Order completed
18	`REFUNDING`	Refund/after-sales in progress
20	`REFUND_FINISHED`	Refund/after-sales completed
-1	`CANCEL`	Order cancelled

⚠️ Important Rules

1. Terminal Status Rules

The following are terminal statuses and cannot transition to other statuses (except CANCEL):

FINISHED(10) - Completed

CANCEL(-1) - Cancelled

2. Refund Rules

Refunds can only be applied for after shipment status

After refund completion, can transition to CANCEL or remain as REFUND_FINISHED

3. Cancellation Rules

Before shipment (status < 5): Can be freely cancelled

After shipment (status >= 5): Must go through refund process

4. Idempotency

Transitions to the same status are allowed (idempotent operations)

Example: SENT → SENT is valid

🎯 Typical Business Scenarios

Scenario 1: Normal Purchase

User pays → WAITING_FOR_PROCURED(3)
Supplier ships → WAITING_FOR_SENT(4) → SENT(5)
Arrives at warehouse → INBOUND(6)
Completion → FINISHED(10)

Scenario 2: Procurement Failure

User places order  → WAITING_FOR_PROCURED(3)
Procurement fails → PROCUREMENT_FAILED(7)
Cancel order → CANCEL(-1)
Refund → Auto-completed

Scenario 3: After-Sales Refund

Order completed → FINISHED(10)
Apply for refund → REFUNDING(18)
Refund completed → REFUND_FINISHED(20)

Scenario 4: Cancel During Payment

Place order → INIT(0) → WAITING_FOR_PAYMENT(1)
Start payment → PAYMENT_IN_PROGRESS(2)
Cancel payment → WAITING_FOR_PAYMENT(1)
Cancel order → CANCEL(-1)

📝 API Response Example

{
  "code": "200",
  "message": "success",
  "data": {
    "total": 1,
    "data": [
      {
        "tradeNo": "PT20250528001",
        "deliveryAddress": {
          "name": "John Doe",
          "phone": "13800138000",
          "province": "Guangdong",
          "city": "Shenzhen",
          "district": "Nanshan",
          "detailAddress": "Tech Park Road XX"
        },
        "orderVOList": [
          {
            "orderId": "1688-12345678",
            "orderStatus": 4,
            "orderStatusDesc": "WAITING_FOR_SENT",
            "orderTotalAmount": 15800,
            "orderHandlingPrice": 50,
            "subOrderList": [
              {
                "id": "1001",
                "subOrderId": "sub-001",
                "subOrderStatus": 4,
                "subOrderStatusDesc": "WAITING_FOR_SENT",
                "productName": "Product A",
                "quantity": 2,
                "subTotalPrice": 15800,
                "refundId": null
              },
              {
                "id": "1002",
                "subOrderId": "sub-002",
                "subOrderStatus": 5,
                "subOrderStatusDesc": "SENT",
                "productName": "Product B",
                "quantity": 1,
                "refundId": null
              }
            ]
          }
        ]
      }
    ]
  }
}

📌 Status Flow Diagram

Create Order
WAITING_FOR_PAYMENT(1)──────→ CANCEL(-1)
   ↓                        ↑
PAYMENT_IN_PROGRESS(2) ─────┤
   ↓                        ↑
WAITING_FOR_PROCURED(3) ────┤
   ↓         ↓              ↑
WAITING_FOR_SENT(4) ────────┤
   ↓                        ↑
SENT(5) ────────────────────┤
   ↓                        
FINISHED(10)
   ↓
REFUNDING(18)
   ↓
REFUND_FINISHED(20)

1688-KA-Order-EN.md

1688 KA Order Fulfillment Flow: From Creation to After-Sales#

📋 Order Status Overview#

🔄 Main Business Flows#

Flow 1: Normal Fulfillment (Success)#

Flow 2: Payment Exception Flow#

Flow 3: Procurement Failure Flow#

Flow 4: Order Cancellation Flow#

Flow 5: Refund/After-Sales Flow#

📊 Status Transition Rules Matrix#

🔍 Customer-Facing Status Descriptions#

Fields Visible to Customers#

Status Description Mapping#

⚠️ Important Rules#

1. Terminal Status Rules#

2. Refund Rules#

3. Cancellation Rules#

4. Idempotency#

🎯 Typical Business Scenarios#

Scenario 1: Normal Purchase#

Scenario 2: Procurement Failure#

Scenario 3: After-Sales Refund#

Scenario 4: Cancel During Payment#

📝 API Response Example#

📌 Status Flow Diagram#

1688 KA Order Fulfillment Flow: From Creation to After-Sales

📋 Order Status Overview

🔄 Main Business Flows

Flow 1: Normal Fulfillment (Success)

Flow 2: Payment Exception Flow

Flow 3: Procurement Failure Flow

Flow 4: Order Cancellation Flow

Flow 5: Refund/After-Sales Flow

📊 Status Transition Rules Matrix

🔍 Customer-Facing Status Descriptions

Fields Visible to Customers

Status Description Mapping

⚠️ Important Rules

1. Terminal Status Rules

2. Refund Rules

3. Cancellation Rules

4. Idempotency

🎯 Typical Business Scenarios

Scenario 1: Normal Purchase

Scenario 2: Procurement Failure

Scenario 3: After-Sales Refund

Scenario 4: Cancel During Payment

📝 API Response Example

📌 Status Flow Diagram