> 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/guides/purchasing/purchase_order_tracking.md).

# Purchase Order Tracking

Track purchase orders, expected receipts, and supplier performance.

The **Purchase Order List** provides functionality that will help purchasing departments to better track and manage open purchase transactions, mainly Purchase Orders. As well as multiple dates to tell everyone when to expect goods to be shipped and delivered, you can assign a haulier (Shipping Agent), logistics status, and information.

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

Ability to create purchase documents.
{% endhint %}

### Shipping Agents

**Shipping Agents** and **Shipping Agent Services** represent the companies and their services used to transport your purchased goods. You can use these codes against purchase documents. The Shipping Agents ‘Name’ is also printed on the Purchase Order report as the **Haulier**.

To set up Shipping Agents:

{% stepper %}
{% step %}

### Step 1

Choose the ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2FLuKEmx9nOWvNYJ04heYpojcYTl8OMgD_UA.png?alt=media) icon, enter **Shipping Agents**, and then choose the related link.
{% endstep %}

{% step %}

### Step 2

Fill in the fields as necessary. Hover over a field to read a short description.
{% endstep %}

{% step %}

### Step 3

Choose the **Shipping Agent Services** action.
{% endstep %}

{% step %}

### Step 4

In the **Shipping Agent Services**, fill in the fields as necessary.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Shipping Agents are shared across sales and purchasing activities.
{% endhint %}

{% hint style="info" %}
Purchase document date fields are not impacted by Shipping Agents Services **Shipping Time** or **Calendar** functionality.
{% endhint %}

### Logistics Status

**Logistics Status** is a field that helps identify where each purchase document is in the process from initial order to receipt. The codes are user-defined and can be created to match your individual process.

For example:

* 01- Planning
* 02 - Sent
* 03 - Confirmed
* 04 - In Production
* 05 - Collection
* 06 - In Transit
* 07 - Booked In
* 08 - Landed
* 09 - Receipted

or can be used to differentiate different types of orders:

* GSTK- General Stock
* ENP - En Primeur
* EXC - ExCellar
* PROD - Raw materials for Production

To create Logistics Status codes, this is what you need to do:

{% stepper %}
{% step %}

### Open Logistics Status / Logistics Codes

Choose the ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2FoCsEaJZFNwMqqdVgLcgqs3tmkpMReW_MhA.png?alt=media) icon, enter **Logistics Status** or **Bevica Setup**, and then choose either link. To access **Logistics Codes** in Bevica Setup, you will need to click on **Navigate > Operations > Logistics Codes**.
{% endstep %}

{% step %}

### Create the code

The codes are user-defined and can be created to match your individual process. To be able to create them, click on **New**. You will need a **unique code** and a **name**. As per list above (Planning; Waiting Approval; PO Sent; Confirmation Received)
{% endstep %}
{% endstepper %}

The **No. of Purchase documents** field is a field that shows the total number of purchase documents against each status code. If you drill down on the number it will give you a list of all purchase documents with that logistic status.

{% hint style="success" %}
If you decide to access the drilldown page, you can further filter by using ‘Filter total by’ on Purchaser Code Expected Receipt Date and Pay-to Vendor No. and Document Type (Quote, Order, Invoice, Credit Memo, Blanket Order, Return Order).
{% endhint %}

### Logistics Information

**Logistics Information** is a large text field that can be used to hold misc. information, i.e. vessel name and sailing dates, customs/legal documentation references, etc.

All three fields, **Shipping Agent Code**, **Logistics Status**, and **Logistics Information** are available on all open and posted purchase document card and list pages, they may be hidden by default.

#### Examples:

* *“Shipped on MV Bordeaux Star – ETD Le Havre 12/03/2026, ETA Felixstowe 18/03/2026.”*
* *“Sailing delayed due to port congestion; revised ETA 24/04/2026.”*
* *“Transhipment via Rotterdam—final leg on Hapag-Lloyd vessel HL Accra.”*
* *“UK VI-1 certificate reference: FR‑2026‑38910; organic certification attached.”*
* *“Vintage substitution agreed: 2022 → 2023 due to producer shortage.”*
* *“Inspection required upon arrival due to previous haze issue in last shipment.”*
* *“Seal #998877 verified intact on arrival.”*


---

# 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/guides/purchasing/purchase_order_tracking.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.