> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/using-tuplo-studio/orders.md).
# Orders
Orders are shown in the Orders tab of the Navigator Window.
The **Orders tab** showcases your orders and offers the standard navigator options to filter the items shown. You can create your orders here and access the Order Details Window to explore your orders and their details.
Orders are **created** in one of three ways.
* **Online:** Customers place orders and require little interaction aside from handling payments and shipping the products.
* **In-Store Orders:** POS Orders, or Point-of-Sale Orders, involve a physical storefront. Customers bring the products to a register, where the transaction is performed, and walk out with their purchase.
* **Back-office:** This occurs when a customer orders over the phone. You would enter the order just like in the store, with some extra steps for processing payments.
{% hint style="info" %}
**Quick Tips!**
Please check the [Point-of-Sale Mode](/using-tuplo-studio/kiosk-mode.md) section for more details on how POS Orders differ from your other orders.
{% 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 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.tuplo.com/using-tuplo-studio/orders.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.