> For the complete documentation index, see [llms.txt](https://docs.eventnook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventnook.com/online-registration-report/view-orders.md).

# View Orders

The **View Orders** section allows you to manage and monitor all registrations and transactions for your event. It provides detailed order-level data, filtering options, and export capabilities.

***

### 🧭 How to Access

1. Log in to your **EventNook account**
2. Select your event
3. Go to:\
   **Report → View Orders**

***

### 📊 What You Can Do

In View Orders, you can:

* View all registration orders
* Filter and search for specific orders
* Access detailed order information
* Export order data for reporting

***

### 🔍 Filtering & Search Options

#### 1️⃣ Order Status Filter

Filter orders by status:

* **Approved (Confirmed)**
* **Pending**
* **Cancelled**
* **Incomplete**

💡 *Useful for tracking registration progress and follow-ups.*

***

#### 2️⃣ Order Type

* **All Orders**
* **Free Orders**
* **Paid Orders**

***

#### 3️⃣ Payment Type Filter

Filter by payment methods such as:

* Stripe / PayPal
* Bank Transfer / Invoice / Cheque
* Onsite / Cash / PayNow
* Others

💡 *Helpful for reconciliation and payment tracking.*

***

#### 4️⃣ Search Function

Search using different fields:

* Email / Secondary Email
* First Name / Last Name / Full Name
* Order Number
* Invoice Number
* Discount / Invitation / Referral Code

***

### 🧾 Display Columns

Customize what information you see by clicking **“Display Columns”**.

Available fields include:

* Order No.
* Order Status
* Order Date
* Invoice No.
* Payment Type
* Amount (Subtotal / Total)
* Customer Name
* Email / Secondary Email
* Discount / Referral Codes
* Payment details and timestamps

💡 *Select only relevant fields for a cleaner view.*

***

### 📋 Order List Overview

Each row represents an order and shows:

* Order number
* Status (Approved, Pending, etc.)
* Quantity of tickets
* Order date
* Payment type
* Total amount
* Buyer details

***

### 👁️ View Order Details

Click **“View”** to access full order details, including:

* Attendee information
* Payment details
* Ticket information
* Invoice / receipt links

***

### 📤 Export Data

* Click **“Export”** to download order data (Excel format)
* You may need to confirm a **data privacy acknowledgment** before exporting

💡 *Use export for reporting, reconciliation, or CRM integration.*

***

### ⚠️ Important Notes

* Exported data must be handled securely and comply with data protection policies
* Pending orders include:
  * Manual approval
  * Manual payment
  * Waiting list (if applicable)
* Incomplete orders refer to abandoned or unfinished registrations

***

### ✅ Best Practices

* Regularly monitor **pending orders** for follow-up
* Use filters to quickly locate specific transactions
* Customize columns for operational efficiency
* Export data for post-event reporting and analysis

***

The **View Orders** page gives you full control over your event transactions, helping you track registrations, manage payments, and access attendee information efficiently.


---

# 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.eventnook.com/online-registration-report/view-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.