# 訂單狀態字典與流程

由已部署的程式碼（OrdersStatusInput / OrdersService）於 https://api.superlabel.ca/api/documentation/order-status-flow?lang=cht 即時產生 — 可隨時重新下載以取得最新版本。

## 狀態字典（`orders_status_id`）

| id | key |
|---|---|
| 1 | need_update_address |
| 2 | new_order |
| 3 | waiting_to_plan |
| 4 | planning |
| 5 | already_planned |
| 6 | plan_failed |
| 7 | already_pickup |
| 8 | successful |
| 9 | redelivered_later |
| 10 | need_rescheduled |
| 11 | rescheduled |
| 12 | cancelled |
| 14 | already_pickup |
| 16 | need_to_pick_up |
| 17 | waiting_for_self_pickup |
| 18 | self_pickup_completed |
| 19 | return_to_customer |
| 20 | out_for_delivery |
| 21 | out_for_pickup |
| 22 | partial_received |
| 23 | partial_delivered |
| 24 | partial_pickuped |
| 25 | hand_off |
| 26 | review |
| 27 | destroyed |
| 28 | need_convert_to_3rd_party_label |
| 29 | in_transit |
| 30 | package_lost |
| 31 | package_damaged |
| 32 | waiting_customer_options |
| 33 | handed_over_to_the_third_party_carrier |
| 34 | waiting_batch_pickup |
| 35 | payment_required |
| 36 | bulk_transshipment_pending |
| 37 | bulk_transshipment_in_transit |
| 38 | bulk_transshipment_pending_inbound |
| 39 | inbound_scan_required |
| 40 | rejected_by_recipient |
| 41 | package_outbound |
| 42 | waiting_for_quote |
| 43 | waiting_third_party_handover |
| 44 | waiting_for_assignment |
| 45 | start_pickup |
| 46 | start_delivery |

語意錨點：out_for_delivery=20、successful=8、配送失敗=10（need_rescheduled）/ 9（redelivered_later）、rejected_by_recipient=40、cancelled=12、redelivery=11（rescheduled）。

最終狀態：cancelled(12), waiting_for_self_pickup(17), waiting_customer_options(32)。

## 追蹤事件字典（`status_code` / `tracking_event_key`）

由 TrackingEvent::EVENT_KEY_MAPPING 產生 — 與執行時期寫入每筆追蹤資料與 Webhook 的常數完全相同。鍵值是穩定的：只會新增，絕不會重新命名或重複使用。

| status_code | key |
|---|---|
| 100 | information_submitted |
| 110 | booking_confirmed |
| 120 | awaiting_pickup |
| 200 | pushed_successful |
| 201 | pushed_failed |
| 300 | received |
| 301 | arrival_scan |
| 400 | planned |
| 401 | removed_from_route |
| 402 | route_cancelled |
| 403 | cancelled |
| 410 | rider_assigned |
| 411 | rider_reassigned |
| 412 | rider_assignment_cancelled |
| 430 | in_transit |
| 431 | on_hold |
| 434 | collection_on_hold |
| 432 | customs_clearance |
| 433 | loaded |
| 435 | facility_received |
| 436 | arrived_at_facility |
| 450 | start_delivery |
| 500 | deliver_success |
| 501 | need_rescheduled |
| 502 | redelivered_later |
| 503 | not_delivered |
| 504 | partial_deliver_success |
| 460 | start_pickup |
| 470 | at_device |
| 471 | device_picked_up |
| 472 | device_expired |
| 473 | device_removed |
| 510 | pickuped |
| 512 | repickup_later |
| 513 | not_pickuped |
| 600 | return_to_sender |
| 700 | rejected_by_recipient |
| 800 | package_outbound |

## 主要配送流程

```mermaid
stateDiagram-v2
    [*] --> new_order: 訂單已建立
    new_order --> waiting_to_plan
    waiting_to_plan --> planning
    planning --> already_planned
    planning --> plan_failed
    plan_failed --> waiting_to_plan: 重新規劃
    already_planned --> out_for_delivery: 司機開始路線
    out_for_delivery --> successful: 已送達（POD）
    out_for_delivery --> need_rescheduled: 配送失敗
    out_for_delivery --> redelivered_later: 同一路線重試
    out_for_delivery --> rejected_by_recipient: 被拒收
    redelivered_later --> successful
    redelivered_later --> need_rescheduled
    need_rescheduled --> rescheduled: 重新排入佇列
    rescheduled --> waiting_to_plan
    successful --> [*]
```

## 收回修正（由 ALLOWED_RECEIVE_STATUS_MAP 產生）

在包裹再次被實際收回時套用。`successful --> rescheduled` 這條邊即為「已送達狀態可能被撤銷」的情況，整合方必須加以處理：以最新事件（id 最大者）為準。啟用資料封套（webhook_payload_envelope=1）時，此類事件亦會帶有 `is_correction: true`。

```mermaid
stateDiagram-v2
    in_transit --> new_order: 已收回
    package_outbound --> new_order: 已收回
    need_to_pick_up --> new_order: 已收回
    waiting_batch_pickup --> new_order: 已收回
    already_pickup --> new_order: 已收回
    out_for_pickup --> new_order: 已收回
    partial_received --> new_order: 已收回
    partial_pickuped --> new_order: 已收回
    already_pickup --> already_pickup: 已收回
    waiting_customer_options --> waiting_customer_options: 已收回
    out_for_delivery --> rescheduled: 已收回
    hand_off --> rescheduled: 已收回
    redelivered_later --> rescheduled: 已收回
    need_rescheduled --> rescheduled: 已收回
    rescheduled --> rescheduled: 已收回
    successful --> rescheduled: 已收回
    handed_over_to_the_third_party_carrier --> successful: 已收回
    bulk_transshipment_in_transit --> new_order: 已收回
    bulk_transshipment_pending_inbound --> new_order: 已收回
    inbound_scan_required --> new_order: 已收回
    package_damaged --> review: 已收回
    package_lost --> review: 已收回
```

## 取消規則

- 可透過 API 取消的狀態：need_update_address(1), new_order(2), already_planned(5), redelivered_later(9), need_rescheduled(10), rescheduled(11), cancelled(12), plan_failed(6), status_15(15), already_pickup(7), already_pickup(14), need_to_pick_up(16), waiting_for_self_pickup(17), self_pickup_completed(18), return_to_customer(19), out_for_delivery(20), out_for_pickup(21), partial_received(22), partial_delivered(23), partial_pickuped(24), hand_off(25), review(26), destroyed(27), need_convert_to_3rd_party_label(28), in_transit(29), inbound_scan_required(39), payment_required(35)。
- 僅限客戶/員工帳號可額外取消的狀態：successful(8)。
- 已取消的訂單會從追蹤查詢中排除，且絕不會自動復原。

## 失敗 / 拒收原因字典

1. 標準化事件代碼（穩定、僅會新增）：追蹤事件上的 `incident_reason` — 分為 carrier_* / retailer_* / consignee_* / customs_* / weather / other 等類別。
2. 商家可自訂的退回原因（自由文字，可能變動）：在追蹤資料中以 `reason` 呈現。

整合方應以（1）作為程式分支依據，（2）僅用於顯示。