> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/orders/statuses-and-order-flow.md).

# Statuses and Order flow

### Introduction

The Order provides a central place to collect information about a customer order. It contains line items, adjustments, payments, addresses, return authorizations, and shipments.

Whenever information about the order is updated, the order states get updated automatically.

In the OMS, each order is associated with Statuses and States- Below is an overview of them.

### Shipment States

Each shipment is assigned a state attribute. Depending on its state, different actions can be performed on shipments. There are four possible states:

**Pending:** The shipment has backorder inventory units, and the order has not been paid for.

**Ready**: The shipment has no backorder inventory units, and the order is paid for.

**Partial**: Suppose an order has multiple shipments, which could be caused by a lack of inventory or numerous stock locations. If only one of the various shipments has shipped, the order will be in a\*\* partial\*\* state until the remaining shipments are shipped.

\*\*Shipped:\*\*The shipment has left the stock location.

**Canceled**: All of its shipments will be canceled when an order is canceled. When this happens, all items in the shipment will be restocked. If an order is "resumed," the shipment will also be resumed.

**Backorder:** Inventory must be updated for the product(s) for the order to be shipped.

### Order States

{% hint style="info" %}
A perfect order will have the statuses of **Paid - Ready - Complete**
{% endhint %}

Before an order is marked as Complete, orders go through a number of other states. By default, the following states are available:

**Cart**: A customer has placed product(s) in the cart but has not proceed with the checkout

**Address**: The customer has begun checkout and has not yet provided their billing and/or shipping addresses. OR there is an issue with the address provided

**Delivery**: The customer needs to choose from available shipping options.

**Payment**: The customer needs to provide payment information.

**Confirm**: The customer needs to confirm that the input checkout information is correct.

**Complete**: The customer has submitted their order.

### Payment States

Typically, an order has one or multiple payments associated with it. Because of this, the order object has a payment\_state attribute that tracks against all payments associated with the order.

For example, if your customer has $20 on store credit, but their order comes to $40, they need to use two payment methods to pay for the order: Store Credit payment method and one of the other available payment methods.

**Balance\_due:** This state indicates that a payment on the order is required. The order's payment\_total value is less than its total value.

**Credit\_owed:** This state indicates that the order has been paid for in excess The order's payment\_total value is greater than its total value.

**Failed:** The payment service provider rejected the payment.

**Checkout**: The order still needs to be completed.

**Processing**: The payment is being processed by the payment service provider. This is a temporary state intended to prevent the double-submission of a payment.

**Pending**: The payment service provider has processed the payment, but still needs to be captured.

**Paid**: This state indicates that the order has been paid for in full, and no credit is owed.

**Invalid**: The payment is invalid and needs to be reattempted.

**Void**: This state indicates that the order has been canceled. No credit is owed, no balance is due, and the order has not been paid for.

**Completed**: The payment is completed.

{% hint style="success" %}
If you have any questions or need help, please get in touch with us at <help@chord.co>.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/chord-oms/chord-oms-overview/orders/statuses-and-order-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.