Possible enumeration values:
| Name | Value | Description |
|---|---|---|
| NoStatus |
-1 |
|
| Draft |
1 |
|
| Open |
2 |
|
| InProgress |
3 |
|
| Complete |
4 |
|
| Closed |
5 |
|
| Cancelled |
6 |
|
| Deleted |
7 |
|
| Rejected |
8 |
|
| Reopen |
9 |
for work orders which transitioned from status of Close-complete/Close-incomplete into re-open status. Under no circumstances do we allow closed/completed to go into ''open''. We should go into this new code #9 (re-open) |
| MaintenanceOrderSave |
2 |
|
| CloseCompleted |
4 |
|
| CloseIncomplete |
5 |
|
| ECommercePreShippingPreparation |
1005 |
order_status_id order_status_text order_status_text_lang_label 1005 Shipping ORDER_STATUS_PRELIMARY_TRANSIT |
| ECommerceShipped |
2005 |
order_status_id order_status_text order_status_text_lang_label 2005 Shipped ORDER_STATUS_SHIPPED |
| ECommerceDeliveredToBuyer |
3005 |
Note: This state is an impossible state. As of 2023, shipstation.com DOES NOT support an api OR even this kind of status code for example, a shipstation ship order can be: cancelled, on hold, awaiting shipment, waiting payment, etc, BUT NEVER any status that tells us that the buyer has received the shipment. shipstation.com does *OPTIONALLY* send out email to buyer or the seller-agent, but NEVER programatic status. order_status_id order_status_text order_status_text_lang_label 3005 Delivered ORDER_STATUS_DELIVERED |