> 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

Manage and perform customer transactions.

<figure><img src="https://2226476425-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNKURzayaXpmKiC6tCrOP%2Fuploads%2FDjPVJ3kikt3TRqVKllSq%2Fnavigator-order-tab.webp?alt=media&amp;token=9783cd65-f5be-4111-b5cf-575789a3e8ca" alt=""><figcaption><p>Orders are shown in the Orders tab of the Navigator Window.</p></figcaption></figure>

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](https://docs.tuplo.com/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 by asking a question.

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

```
GET https://docs.tuplo.com/using-tuplo-studio/orders.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.
