Order Status Codes

The numeric codes returned in an order's status field, and what each one means
View as Markdown

An order’s status — whether you filter on it or read it back from the API — is a numeric code describing the order’s current condition.

CodeEnumDescription
1UNSENTA future order that will be processed when its place date arrives.
3REJECTEDThe order was rejected after the retry limit was reached.
4CANCELLEDThe order was cancelled before it was successfully processed.
5SUCCESSThe order was processed successfully.
6SEND_NOWA future order already exists for this subscription before the placement process runs.
9PENDING_BATCH_RESPONSEOrdergroove has sent the order and is awaiting a response file. Applies only to merchants on legacy file-based batch placement, not to API-based placement.
10PENDING_VERIFICATIONAwaiting confirmation from the merchant or ecommerce platform that the order was processed.
11PENDING_PLACEMENTThe order is queued and will be processed shortly.
12EXCEPTION_DURING_PLACEMENT_PREPARATIONSomething failed before the order could be attempted.
13CONNECTION_ERROR_DURING_PLACEMENTThe connection failed mid-placement, so the outcome is unconfirmed. Depending on your configuration the order may be retried on the next placement, with no retry limit.
14RESPONSE_PROCESSING_ERRORThe merchant’s batch or HTTP response wasn’t understood. This order isn’t retried.
15GENERIC_ERROR_RESPONSEA generic error was returned or defaulted. You control how many times these are retried.
17MERGEDThe order was merged into another. The target order ID is in the order’s extra data, under merged_order_id.
18CREDIT_CARD_RETRYThe order failed with a 140 error code and is in the credit card retry process.
19AWAITING_RETRY_INSTRUCTIONSThe rejection has been classified and rejected_error_code now holds the three-character Ordergroove code. This state resolves quickly.
20AWAITING_RESPONSE_CLASSIFICATIONThe order was rejected and is awaiting classification. While in this state rejected_error_code may hold a raw platform code such as PAYMENT_METHOD_DECLINED rather than an Ordergroove code — treat it as null until classification completes, typically within a minute.