> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/shipping_agent_planning_worksheet_-sales.md).

# Shipping Agent Planning Worksheet (Sales)

Plan dispatches by shipping agent and warehouse status.

**Shipping Agent Planning** lets you manage where in its lifecycle a sales order is. Filters by Shipping Agent, with additional user-defined filters you can apply as necessary.

{% hint style="warning" %}
**Prerequisites**

Sales processing using Shipping Agents.

Bevica Warehouse Integration extension installed.
{% endhint %}

## Shipping Agent Planning Worksheet (Sales)

Navigate to Shipping Agents, select Related Information, **Shipping Agent Planning Worksheet** on the ribbon. Alternatively, search for the page.

The page has a number of filter fields at the top. These filter the order count by each Shipping Agent Code.

| Filter Field                           | Note                                                                                                                                                                    |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Location Filter                        | Select a Location Code to filter the fields below.                                                                                                                      |
| Shipment Date Filter (up to date)      | Enter a Date to filter the order count. Bevica automatically sets the date you enter to ..DATE, i.e. all dates up to and including the entered date.                    |
| Req. Delivery Date Filter (up to date) | Enter a Date to filter the order count. Bevica automatically sets the date you enter to ..DATE, i.e. all dates up to and including the entered date. Hidden by default. |
| Duty Status Filter                     | Select a Location Code to filter the fields below. Hidden by default                                                                                                    |

{% hint style="info" %}
Note

If you personalise the page, the two hidden fields above must be added to the top section, not the lines.
{% endhint %}

**Shipping Agents line fields**

Each field is filtered on Sales Orders and its respective Shipping Agent Code, plus...

| Field                        | Note                                                                          |
| ---------------------------- | ----------------------------------------------------------------------------- |
| Open Sales Orders            | where Status = Open.                                                          |
| Pending Sales Orders         | where Status = Pending Prepayment.                                            |
| Release Sales Orders         | where Status = Released & Credit Status = Released.                           |
| Credit Held Sales Orders     | where Status = Released & Credit Status = Credit Held.                        |
| Whse. Pending Sales Order    | where Whse. Integration Request Status = Pending                              |
| Whse. Generated Sales Orders | where Whse. Integration Request Status = Generated                            |
| Whse. Sent Sales Orders      | where Whse. Integration Request Status = Sent                                 |
| Whse. Error Sales Orders     | where Whse. Integration Request Status = Error on Generating Error on Sending |

The page has an additional filter at the bottom, **No. Sales order with blank Shipping Agent Code.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/shipping_agent_planning_worksheet_-sales.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.