> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/suppliers/managing-suppliers/supplier-purchases-tab.md).

# Supplier Purchases Tab

Using the Purchases tab makes it easy to track and manage all purchasing activity with a supplier in one place, helping keep orders organised and purchasing records up to date.

A supplier’s **Purchases** page provides a central place to view and manage all purchasing activity with that supplier. From here, you can review current and previous purchase orders, view order details and statuses, track outstanding purchases, and access your purchasing history. This makes it easy to monitor orders and refer back to previous purchase information when needed.

This document provides a brief overview of the **Purchases** tab on a supplier’s page in Supply’d.

***

## The Supplier's Purchases Tab

Selecting a supplier from the **Suppliers** list will open their **Supplier Page**, where you can view and manage their information across the available tabs.

The **Purchases** tab on a supplier's page provides a central place to view and manage purchases made from the supplier, allowing you to review purchase orders, track their progress, and access details of your purchasing activity with that supplier.

<figure><img src="https://2965503026-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDaPYJDB89ny0x7wcMedb%2Fuploads%2FpK8eGSyfXfhjAzsFHOSw%2FSupplier%20-%20Purchases%20Tab.png?alt=media&amp;token=f9bbfd8b-8dd9-4e0d-b94c-8cbcd6799d05" alt=""><figcaption></figcaption></figure>

Selecting a purchase will open the **Purchase Details** page, where you can view and manage the information associated with that purchase.

<figure><img src="https://2965503026-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDaPYJDB89ny0x7wcMedb%2Fuploads%2F5R5egG9bIWZGJXzgZSMS%2FSuppliers%20-%20PO%20Details.png?alt=media&amp;token=3a113d60-b9c1-4502-8c8c-81c2cd6875df" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
👉 Orders can be managed following the guidelines in the [Managing Purchase Orders](https://help.supplyd.co/supplyd-erp/purchases/managing-purchase-orders.md) document.

👉 You can place new orders from this page by clicking **Add +** in the top right and following the instructions in the [Placing Purchase Orders](https://help.supplyd.co/supplyd-erp/purchases/placing-purchase-orders.md#creating-a-purchase-order-from-a-supplier) section of the [Placing Purchase Orders](https://help.supplyd.co/supplyd-erp/purchases/placing-purchase-orders.md) document.
{% endhint %}


---

# 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://help.supplyd.co/supplyd-erp/suppliers/managing-suppliers/supplier-purchases-tab.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.
