> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/advance-shipment-dashboard.md).

# Advance Shipment Dashboard

The Advance Shipment Dashboard lists all advance shipment orders of your organization in one table. Use the search bar and the filter panel to narrow down the list, open a row to see the order in detail, and use the row actions to download the shipment document as PDF or share the order through a magic link.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-56b1f6e5574ef3f4f72aa47a826ed4196fabcfa8%2Fadvance-shipment-dashboard-overview-en-20261012.png?alt=media" alt="Advance Shipment Dashboard in the English Sandbox showing the search bar, the refresh button, the columns Customer Name, Customer Number, Order Date, Requested Delivery Date, Estimated Delivery Date, PO Number, Order Number, Order Status and Actions, three example orders and the pagination bar"><figcaption><p>The dashboard with example orders from the synthetic Sandbox organization. The figures will differ in your organization.</p></figcaption></figure>

{% hint style="info" %}
The dashboard is only available when the **Advance Shipment Dashboard** module is switched on. An administrator enables it under **Settings → Module** in the **Dashboards** section — see [Module](https://docs.docbits.com/administration-and-setup/settings/document-processing/module.md#dashboards). Without the switch, the page shows an "action not allowed" message instead of the table.
{% endhint %}

## Columns

| Column                      | Description                                                                                                                                                                                         |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Customer Name**           | Name of the customer the order belongs to.                                                                                                                                                          |
| **Customer Number**         | Customer number assigned in your system.                                                                                                                                                            |
| **Order Date**              | Date the order was created, shown in your personal date format.                                                                                                                                     |
| **Requested Delivery Date** | Delivery date the customer asked for.                                                                                                                                                               |
| **Estimated Delivery Date** | Delivery date currently expected.                                                                                                                                                                   |
| **PO Number**               | Purchase order number linked to the order.                                                                                                                                                          |
| **Order Number**            | Sales order number. Click the row to open the order detail page.                                                                                                                                    |
| **Order Status**            | A three-step progress indicator: the first steps are covered while the order is reserved, allocated or the picking list is printed, the second once it is delivered, the third once it is invoiced. |
| **Actions**                 | Row menu with **Export** and **Share** — see [Row actions](#row-actions).                                                                                                                           |

## Searching and filtering

Type in the search bar to filter the list by the entered text; the list updates as you type. The **tune** icon at the end of the search bar opens the filter panel:

| Filter                       | Description                                       |
| ---------------------------- | ------------------------------------------------- |
| **PO Number**                | Show only orders with this purchase order number. |
| **Order Number**             | Show only orders with this order number.          |
| **Order date**               | Show only orders from one specific order date.    |
| **After Date / Before Date** | Show only orders in a date range.                 |
| **Shipments Per Page**       | Number of rows shown per page (10, 25 or 50).     |
| **Clear filters**            | Remove all filters and the search text.           |

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-21c0f50cd99cf0ee65f66161cac9d68544b3967e%2Fadvance-shipment-dashboard-filterpanel-en-20261012.png?alt=media" alt="Filter panel of the Advance Shipment Dashboard with the fields PO Number, Order Number, Order date, After Date, Before Date, Shipments Per Page and the Clear filters button"><figcaption><p>The filter panel of the search bar.</p></figcaption></figure>

The **refresh** button next to the search bar reloads the list, for example after new shipments were imported.

## Row actions

Open the **more\_vert** (three dots) menu at the end of a row:

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-1e2ce5cb887ad8f2885bf452073e501030b63c8b%2Fadvance-shipment-dashboard-rowmenu-en-20261012.png?alt=media" alt="Row action menu of an advance shipment order with the entries Export and Share"><figcaption><p>The row menu with the entries <strong>Export</strong> and <strong>Share</strong>.</p></figcaption></figure>

* **Export** downloads the shipment document of the order as a PDF file.
* **Share** copies a magic link to your clipboard. Anyone who opens the link sees the order detail page of this shipment without logging in (the link uses the `/share/sales-orders/...` address — see [Web Address Changes](https://docs.docbits.com/end-user-and-partner-section/end-user-section/web-address-changes.md#shared-links)). Only share the link with people you trust — the link opens the order directly.

## Your view settings are saved

* **Column order:** Drag a column header to a new position. DocBits saves the order per user, so the table looks the same the next time you open the dashboard.
* **Page size:** The number of rows per page is saved per user as well and is restored on your next visit.


---

# 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.docbits.com/end-user-and-partner-section/end-user-section/advance-shipment-dashboard.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.
