> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ai-store/orders-carts-and-customers.md).

# Orders, Carts & Customers

## Orders, Carts & Customers – Complete Guide

The **Orders, Carts, and Customers** sections work together to help you track the complete customer journey — from adding products to the cart, to placing an order, and managing customer information.

### 1. Manage Orders

1. Go to **Ecom Store → Orders → Orders**.
2. View all orders in the order list.
3. For each order, you can view:
   * Order Number
   * Customer Phone Number
   * Total Amount
   * Number of Items
   * Order Status
   * Source
   * Order Type
   * Order Date
4. Use the available actions to **Print Invoice, Edit, or Delete** an order.
5. Use the **Search** option to find a specific order.
6. Use filters to view orders based on their **status or cart**.
7. Sort orders by **Latest** or **Oldest**.

#### Order Status

You can filter orders based on statuses such as:

* Pending
* Processing
* Shipped
* Cancelled
* Other available statuses

### 2. Manage Carts

A **Cart** represents products that a customer has added but has not necessarily purchased yet.

1. Go to **Ecom Store → Orders → Carts**.
2. View the available carts.
3. For each cart, you can see:
   * Cart ID
   * Customer Phone Number
   * Products
   * Quantity
   * Created Date
   * Updated Date
4. Use the available actions to view or manage cart details.

#### Cart vs Order

* **Cart:** Products added by the customer before completing checkout.
* **Order:** A completed purchase record created after checkout.

### 3. Manage Customers

The **Customers** section stores customer records associated with your ecom store.

1. Go to **Ecom Store → Customers**.
2. View the customer database.
3. Customer information may include:
   * Name
   * Phone Number
   * Email Address
   * Joining Date
4. Use the **Search** option to find a specific customer.

### 4. Understanding the Customer Journey

The three sections are connected:

**Customer → Cart → Order**

For example:

1. A customer visits your store and browses products.
2. The customer adds products to the **Cart**.
3. The customer can update quantities or continue shopping.
4. Once checkout is completed, the cart activity becomes an **Order**.
5. The order appears in the **Orders** section with its amount, status, and other details.
6. The customer's information is maintained in the **Customers** section.

#### In Short

* **Carts** → Shows shopping activity.
* **Orders** → Shows completed purchases.
* **Customers** → Shows the people associated with your store.

Together, these sections provide a complete view of customer activity and purchasing behavior in your ecom store.

{% embed url="<https://youtu.be/GJ7Cwctfpfo>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ai-store/orders-carts-and-customers.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.