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

# Create Receiving Inbound

createReceivingInbound Mutation

Creates a new ReceivingInbound with associated inbound items.

## Arguments

| Name    | Type                                    | Description                                                |
| ------- | --------------------------------------- | ---------------------------------------------------------- |
| `input` | `CreateReceivingInboundWithItemsInput!` | Input data for creating the inbound shipment and its items |

## Return Type

`ReceivingInboundOutput` - Contains the created inbound shipment and any associated workflows.

## Input Fields

`CreateReceivingInboundWithItemsInput`:

| Field          | Type                                 | Description                                                |
| -------------- | ------------------------------------ | ---------------------------------------------------------- |
| `dataTypeID`   | `UUID`                               | Optional data type ID                                      |
| `dataTypeSlug` | `String`                             | Optional data type slug                                    |
| `data`         | `Map`                                | Custom data associated with the inbound shipment           |
| `supplierID`   | `UUID`                               | ID of the supplier this inbound is from                    |
| `orderID`      | `String`                             | Optional order or reference ID for the inbound shipment    |
| `inboundItems` | `[CreateReceivingInboundItemsInput]` | List of inbound items to create with this inbound shipment |

`CreateReceivingInboundItemsInput`:

| Field          | Type      | Description                                   |
| -------------- | --------- | --------------------------------------------- |
| `dataTypeID`   | `UUID`    | Optional data type ID                         |
| `dataTypeSlug` | `String`  | Optional data type slug                       |
| `data`         | `Map`     | Custom data associated with the inbound item  |
| `sku`          | `String!` | Required stock keeping unit (SKU) of the item |
| `quantity`     | `Int!`    | Required quantity of the item                 |

## Usage Example

```graphql
mutation {
  createReceivingInbound(
    input: {
      supplierID: "550e8400-e29b-41d4-a716-446655440000",
      orderID: "PO-98765",
      data: {
        "expected_arrival_date": "2023-06-15",
        "carrier": "Express Logistics",
        "tracking_number": "TRK123456789",
        "notes": "Requires inspection upon arrival"
      },
      inboundItems: [
        {
          sku: "ITEM-123",
          quantity: 50,
          data: {
            "batch_number": "BN-001",
            "expiry_date": "2025-12-31"
          }
        },
        {
          sku: "ITEM-456",
          quantity: 25
        }
      ]
    }
  ) {
    receivingInbound {
      id
      orderID
      supplierID
      data
      inbounditems {
        id
        sku
        quantity
        data
      }
    }
    workflows {
      id
      type
      id
      runID
      status
    }
  }
}
```


---

# 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/mutations/createreceivinginbound.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.