> For the complete documentation index, see [llms.txt](https://docs.shopeasy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shopeasy.ai/sales-management.md).
# Sales Management
Welcome to Shopeasy's Sales Management section! This area allows you to oversee and manage orders, returns, and abandoned carts. Follow these steps to efficiently handle your sales processes:
#### Step 1: Order Management
1. **Navigate to Sales > Orders** to begin managing customer orders.
2. **Order Status:**
* Payment Pending
* Payment Failed
* Canceled
* Denied
* Order Placed
* Completed
* Shipped
* Ready to Ship
#### Managing Orders
In this section, you can:
* **View Detailed Order Information**
* **Update Order Status**
* **Manage Payment Details**
* **Track Order Shipments**
#### Step 2: Return Order Processing
1. **Navigate to Sales > Returns** to handle return requests.
2. Review customer return requests and take appropriate actions based on the reason for the return.
#### Step 3: Abandoned Cart Monitoring
1. **Navigate to Sales > Abandoned Cart** to track customer cart activities.
2. View a list of customers who have added products to their carts. Identify abandoned carts that have been inactive for 24 hours or more.
#### Note:
* Efficiently managing sales processes ensures a seamless experience for your customers.
---
# 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.shopeasy.ai/sales-management.md?ask=&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.
