> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/selling/order-states.md).
# Order states
**An order can have various states throughout its life cycle.**
When you create an order, it will enter the state Open. When an order is in state Open, you have the possibility of setting it to Parked to be able to open it up again later, or you can set it as Confirmed, or, lastly, you can just finalize it by adding payments to it and complete it, whereas it will be set to Complete.
{% hint style="warning" %}
In all of these states, the quantity of the product(s) on the order gets status *reserved*.
{% endhint %}
{% hint style="info" %}
**Order *****states*** and **Order *****types*** are distinct. The order types include Order and Offer .\
The key difference is that *offers* do not reserve stock for the products, like *orders* do.\
This order state documentation focuses on orders with the Order type.
{% endhint %}
### Open state
The open state makes sure no one else can open the order at the same time. So if you open up an order on one device and then try to open it up again on another device, your second device will get a warning that the first device already have it open. You then have the possibility of enforcing to open it on the other device, but be careful when doing this so you don't end up updating the order in multiple places, which might give unforeseen consequences.
### Parked state
The "parked state" allows you to temporarily save a sales transaction. For example, a customer might discuss products with a seller in one department, adding some items to their order. They can then proceed through the store, adding more items at the checkout.
You can manage parked orders by opening them anytime and either confirming or settling them. Basic orders, which are immediately paid by the customer, will bypass the parked state entirely, transitioning directly from open to done.
### Confirmed state
**The confirmed state is something you normally set manually,** typically when you for instance are very sure the customer will actually buy the product later.
The confirmed state does not change anything specifically on the order itself, other than that it is being moved from the Parked order overview to the Confirmed order overview.
{% hint style="info" %}
If you have enabled the "Cancel Parked Order" functionality, orders in Confirmed state will never be automatically cancelled.
{% endhint %}
{% hint style="warning" %}
If you are using the prepayment functionality, the system will *automatically* set orders with one or more prepayment settlements to Confirmed.
{% endhint %}
### Complete state
Orders in the complete state are fully paid for and can not be changed.
### Canceled state
Orders with state Cancelled are marked as cancelled/deleted, and are neither visible or available in the system in any way.
If you delete an order, it will be given the state cancelled.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.flowretail.com/docs/day-to-day-operations/selling/order-states.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.