# Orders

The **Orders** page gives a complete overview of all purchases made through your store—both one-time orders and subscription-based transactions.\
Admins can review order details, verify payment status, and view related subscriptions.

Access it from:\
**Store → Orders**

### **Orders List Overview**

The Orders table displays all customer orders with key information for quick review.

#### **Columns available**

* **Order** – Order ID (click to open full details)
* **Customer Name** – Name of the buyer
* **Order date** – Date the order was created
* **Transaction ID** – Stripe Payment Intent or Invoice ID
* **Price** – Order amount
* **Price (recurring)** – If the product is subscription-based (e.g., $1.00/day)
* **Status** – Active, Failed, Expired, etc.
* **Action** – View order details

This table helps you monitor daily activity, troubleshoot failed orders, and assist customers.

***

### **Order Statuses**

Each order displays one of the following statuses:

* **Active** – Payment successful, access granted
* **Failed** – Payment attempt failed
* **Expired** – Linked subscription has expired
* **Pending** – Payment still processing (Stripe pending)
* **Cancelled** – Manually or automatically cancelled

Statuses are automatically synced from Stripe based on the payment result.

***

### **Viewing Order Details**

Click any order to open its full details.

#### **Order Summary (Displayed Fields)**

* **Order ID**
* **Order date & exact time**
* **Transaction ID** (e.g., `pi_xxx` or `in_xxx`)
* **Status**
* **Total amount**

#### **Customer Information**

* Customer name
* Billing email

#### **Purchased Products**

For each item purchased, the following appears:

* Product Name
* Original price
* Charged price
* Qty (if applicable)

#### **Price Breakdown**

* **Subtotal**
* **Total**

No taxes appear unless taxes are enabled in shop settings.

***

### **Subscription Relationship**

If the order is related to a subscription:

A **Related Subscription** section appears showing:

* **Subscription ID** (clickable)
* **Relationship type** (e.g., “Subscription”)
* **Date created**
* **Status** – Active, Expired, Cancelled
* **Recurring price** (e.g., $1/day)

This helps you track recurring billing issues and customer subscription history.

***

### **Refunds & Payment Management**

**Refunds are&#x20;*****not*****&#x20;supported inside the plugin.**

If an order requires a refund:

#### **Refunds must be processed directly from Stripe Dashboard.**

After initiating a refund in Stripe:

* The order status will update automatically to reflect the change (if Stripe webhook is correctly configured).
* The customer's access will adjust according to the payment provider’s response.

This keeps your plugin lightweight while ensuring Stripe handles sensitive financial transactions.

***

### **Failed Orders**

If an order shows **Failed**, it typically means:

* Card was declined
* Authentication (3DS) failed
* Insufficient funds
* Subscription renewal attempt failed

Admins can suggest the customer:

* Update their card details
* Retry payment via Stripe’s payment link (if subscription-related)
* Purchase again

***

### **When to Contact Support**

Admins should reach out for support if:

* Order status does not match Stripe
* Webhooks are not updating orders
* Subscriptions are not syncing correctly

Correct Stripe webhook setup is required for accurate order updates


---

# Agent Instructions: 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:

```
GET https://remui-docs.edwiser.org/edwiser-store/getting-started/post-installation/course-sync-as-product/payment-and-coupon/order-and-subscription/orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
