> 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/pickingorder.md).

# PickingOrder

PickingOrder Type

Represents a picking order in the system, which is used to collect items from inventory for fulfillment.

## Fields

| Field          | Type                  | Description                                        |
| -------------- | --------------------- | -------------------------------------------------- |
| `id`           | `ID!`                 | Unique identifier of the picking order             |
| `tenantID`     | `UUID!`               | Tenant identifier                                  |
| `createdAt`    | `Time!`               | Creation timestamp                                 |
| `createdBy`    | `UUID`                | User identifier who created the picking order      |
| `updatedAt`    | `Time`                | Last update timestamp                              |
| `updatedBy`    | `UUID`                | User identifier who last updated the picking order |
| `deletedAt`    | `Time`                | Deletion timestamp                                 |
| `deletedBy`    | `UUID`                | User identifier who deleted the picking order      |
| `dataTypeID`   | `UUID`                | Data type identifier                               |
| `dataTypeSlug` | `String`              | Data type slug                                     |
| `data`         | `Map`                 | Custom data associated with the picking order      |
| `customerID`   | `UUID!`               | ID of the customer this order is for               |
| `orderitems`   | `[PickingOrderItem!]` | Items included in this picking order               |
| `attachments`  | `[Attachment]`        | Attachments associated with this picking order     |

## Interfaces

* `NodePicking`

## Usage Example

```graphql
query {
  pickingOrders(
    first: 10,
    orderBy: { direction: DESC, field: CREATED_AT }
  ) {
    edges {
      node {
        id
        customerID
        data
        orderitems {
          sku
          quantity
          item {
            data
          }
        }
        createdAt
      }
    }
  }
}
```

```graphql
mutation {
  createPickingOrder(
    input: {
      customerID: "550e8400-e29b-41d4-a716-446655440000",
      data: {
        "order_number": "PO-12345",
        "priority": "high",
        "delivery_address": {
          "street": "123 Main St",
          "city": "Springfield",
          "postalCode": "12345",
          "country": "US"
        },
        "notes": "Handle with care"
      },
      orderItems: [
        {
          sku: "ITEM-123",
          quantity: 5,
          data: {
            "notes": "Gift wrapped"
          }
        },
        {
          sku: "ITEM-456",
          quantity: 2
        }
      ]
    }
  ) {
    pickingOrder {
      id
      data
      orderitems {
        id
        sku
        quantity
      }
    }
  }
}
```


---

# 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/pickingorder.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.