> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/types/supplier.md).

# Supplier

Supplier Type

Represents a supplier entity in the system that provides goods or services to the warehouse.

## Fields

| Field          | Type     | Description                                   |
| -------------- | -------- | --------------------------------------------- |
| `id`           | `ID!`    | Unique identifier of the supplier             |
| `tenantID`     | `UUID!`  | Tenant identifier                             |
| `dataTypeID`   | `UUID`   | Data type identifier                          |
| `dataTypeSlug` | `String` | Data type slug                                |
| `data`         | `Map`    | Custom data associated with the supplier      |
| `createdAt`    | `Time!`  | Creation timestamp                            |
| `createdBy`    | `UUID!`  | User identifier who created the supplier      |
| `updatedAt`    | `Time`   | Last update timestamp                         |
| `updatedBy`    | `UUID`   | User identifier who last updated the supplier |
| `deletedAt`    | `Time`   | Deletion timestamp                            |
| `deletedBy`    | `UUID`   | User identifier who deleted the supplier      |

## Interfaces

* `Node`

## Usage Example

```graphql
query {
  suppliers(
    first: 10
    orderBy: { field: CREATED_AT, direction: DESC }
  ) {
    edges {
      node {
        id
        data
        dataTypeSlug
        createdAt
      }
    }
    totalCount
  }
}
```

## Custom Data Examples

The `data` field typically contains supplier-specific information:

```json
{
  "name": "ACME Supply Co.",
  "code": "SUP-001",
  "email": "orders@acmesupply.com",
  "phone": "+1-555-0123",
  "address": {
    "street": "123 Industrial Way",
    "city": "Manufacturing City",
    "state": "CA",
    "zip": "90210",
    "country": "USA"
  },
  "contactPerson": "John Doe",
  "paymentTerms": "NET30",
  "preferredDeliveryDays": ["Monday", "Wednesday", "Friday"],
  "minimumOrderValue": 500.00,
  "leadTimeDays": 7
}
```

## Notes

* Suppliers are master data entities used throughout the system
* Custom fields are stored in the `data` JSON field
* Use `dataTypeSlug` to categorize suppliers (e.g., "domestic\_supplier", "international\_supplier")
* Virtual repositories can be named after suppliers for receiving operations
* Suppliers can be referenced in receiving inbounds and purchase orders


---

# 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.pyck.cloud/graphql-api/types/supplier.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.