> ## Documentation Index
> Fetch the complete documentation index at: https://help.mathership.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Order List

> View, search, and manage orders in the vendor order list

# Order List

The order list shows vendors the orders received from their connected customers.

Use it to review incoming orders, open details, check customer information, and follow up on orders that still need processing.

## What it is

The order list is the main overview for vendor orders.

It helps vendors see:

* Which orders have been received
* Which customer placed the order
* When the order was placed
* Which delivery location belongs to the order
* Whether an order is still open
* Whether more details are available

## Who can access it?

The list is available to vendor users.

A vendor can only view orders that belong to their own vendor company.

<Warning>
  Vendors cannot view orders for other vendor companies.
</Warning>

## Data shown in the list

The overview can include information such as:

| Field             | Meaning                                 |
| ----------------- | --------------------------------------- |
| Order ID          | Internal Mathership order identifier    |
| Customer          | Customer company that placed the order  |
| Delivery location | Location selected for the order         |
| Placed at         | Date and time when the order was placed |
| Status            | Current order status                    |
| Message           | Optional message from the customer      |
| Items             | Products included in the order          |

The exact fields shown can depend on the user interface and serializer configuration.

## Opening the overview

To open the order list:

1. Go to **Vendors**
2. Open your vendor company
3. Go to **Orders**
4. Review the list of received orders

From there, you can open an individual order to view the full details.

## Sorting

Orders are normally shown with the newest orders first.

This helps vendors see the most recent incoming orders at the top of the list.

## Pagination

The list can use pagination.

Pagination helps load larger order histories in smaller parts instead of loading all orders at once.

Typical pagination values include:

| Parameter | Meaning                                 |
| --------- | --------------------------------------- |
| limit     | Number of orders to load                |
| offset    | Starting point for the list             |
| has\_more | Shows whether more orders are available |
| total     | Total number of matching orders         |

Example:

```txt theme={null}
limit = 20
offset = 0
```

This means Mathership loads the first 20 orders.

## Filtering by customer

Vendors can view all orders for their company or filter by a specific customer.

This is useful when a vendor wants to check the order history for one restaurant or customer company.

Example use cases:

* Review all orders from one customer
* Check whether a customer has placed a recent order
* Find orders related to a specific customer relationship
* Support customer service questions

## Draft and scheduled orders

Vendor order lists normally exclude orders that are not sent yet.

Orders with the following email statuses may be hidden from the standard vendor view:

| Email status | Meaning                                  |
| ------------ | ---------------------------------------- |
| draft        | The order was saved as a draft           |
| scheduled    | The order is scheduled for later sending |

This prevents vendors from seeing orders that the customer has not actually sent yet.

<Note>
  Draft and scheduled orders are not treated like fully sent orders in the standard vendor order list.
</Note>

## Open orders

Mathership can also show a short list of recent open orders.

The dashboard-style open order view can include:

* The last 10 open orders
* The total count of open orders

This helps vendors quickly identify orders that may still need attention.

## Status

Orders can have a status that helps vendors track processing.

The available statuses depend on the order model configuration.

A typical workflow may include values such as:

| Status      | Meaning                                  |
| ----------- | ---------------------------------------- |
| Open        | Order still needs processing             |
| In progress | Order is being handled                   |
| Completed   | Order has been processed                 |
| Archived    | Order is hidden from normal active views |

<Note>
  Archived orders may be excluded from some customer-facing order history views.
</Note>

## Updating status

Vendors can update the status of an order if the order belongs to their vendor company.

When updating a status, Mathership checks that:

* The user is a vendor
* The order belongs to the vendor company
* The new status is valid
* The order exists

If the status is invalid, Mathership rejects the update.

<Warning>
  Only vendors can update order statuses.
</Warning>

## Search

Order lists can support search fields depending on the view.

Search may include values such as:

* Order number
* Delivery location
* Vendor contact
* Customer-related information

Use search when the list becomes too long to scan manually.

## Customer history

Customers can also view order history for a specific vendor relationship.

Customer order history is different from the vendor order list.

| View                   | Used by  | Purpose                            |
| ---------------------- | -------- | ---------------------------------- |
| Vendor order list      | Vendor   | Review incoming orders             |
| Customer order history | Customer | Review orders placed with a vendor |

## Overview or details?

The order list is an overview.

Order details show the full order.

| Page          | Purpose                                          |
| ------------- | ------------------------------------------------ |
| Order List    | Shows many orders in a compact list              |
| Order Details | Shows one order with all order items and details |

Use the order list to find an order, then open the details to review the full order.

## Typical workflow

A typical vendor workflow looks like this:

1. Customer sends an order
2. Mathership creates the order
3. Mathership sends the order email to the vendor
4. The order appears in the vendor order list
5. Vendor opens the details
6. Vendor checks the items and delivery location
7. Vendor updates the status when needed

## Example: Review new orders

A vendor wants to check recently received orders.

| Step | Action                                            |
| ---- | ------------------------------------------------- |
| 1    | Open the vendor company                           |
| 2    | Go to **Orders**                                  |
| 3    | Review newest orders first                        |
| 4    | Open an order                                     |
| 5    | Check products, quantities, and delivery location |

## Example: Find orders for one customer

A vendor wants to review orders from one restaurant.

| Step | Action                     |
| ---- | -------------------------- |
| 1    | Open the vendor order list |
| 2    | Filter by customer         |
| 3    | Review the matching orders |
| 4    | Open the relevant details  |

## Example: Check open orders

A vendor wants to see orders that still need processing.

| Step | Action                                      |
| ---- | ------------------------------------------- |
| 1    | Open the vendor dashboard or order overview |
| 2    | Review recent open orders                   |
| 3    | Open each order                             |
| 4    | Process the order                           |
| 5    | Update the status                           |

## Best practices

### Review new orders regularly

Check the order list regularly so incoming customer orders are not missed.

### Use customer filters

Use customer filters when you need to investigate orders for a specific restaurant or company.

### Keep statuses updated

Order statuses help your team understand which orders still need work.

### Open details before processing

The list is only an overview. Always open the details before processing an order.

### Check delivery locations

Make sure the delivery location is correct before preparing or dispatching the order.

## Common problems

### Order is not visible

Check that:

* The order was actually sent
* The order is not only a draft
* The order is not scheduled for later
* You are logged in as the correct vendor
* You opened the correct vendor company

### Vendor cannot access the list

Check that:

* The user is logged in
* The user has the vendor role
* The vendor company belongs to the user

### Order belongs to another vendor

Vendors can only access orders for their own company.

If an order belongs to another vendor company, access is denied.

### Status cannot be updated

Check that:

* The user is a vendor
* The order belongs to the vendor company
* The submitted status is valid
* The order has not been deleted or hidden

### Too many orders are shown

Use pagination, customer filters, or search to narrow the list.

## Related pages

<CardGroup cols={2}>
  <Card title="Order Details" icon="clipboard-list" href="/en/vendors/orders/order-details">
    View the full details of a single order.
  </Card>

  <Card title="Open Orders" icon="list-check" href="/en/vendors/orders/open-orders">
    Review recent open orders.
  </Card>

  <Card title="Email Notifications" icon="envelope" href="/en/vendors/orders/email-notifications">
    Learn how order emails are sent to vendors.
  </Card>

  <Card title="CSV and PDF Attachments" icon="file-lines" href="/en/vendors/orders/csv-pdf-attachments">
    Understand order email attachments.
  </Card>

  <Card title="Order Exports" icon="file-export" href="/en/vendors/orders/order-exports">
    Learn how order data can be exported.
  </Card>

  <Card title="Customer Details" icon="address-card" href="/en/vendors/customers/customer-details">
    View customer information and delivery locations.
  </Card>
</CardGroup>
