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

# Delete Receiving Inbound Item

deleteReceivingInboundItem Mutation

Deletes a ReceivingInboundItem object from the system.

## Arguments

| Name | Type  | Description                                                   |
| ---- | ----- | ------------------------------------------------------------- |
| `id` | `ID!` | The unique identifier of the receiving inbound item to delete |

## Return Type

`ReceivingInboundItemDeletePayload!` - Contains information about the deleted receiving inbound item and any triggered workflows.

## Return Fields

`ReceivingInboundItemDeletePayload`:

| Field       | Type                 | Description                                            |
| ----------- | -------------------- | ------------------------------------------------------ |
| `deletedID` | `ID`                 | The ID of the deleted receiving inbound item           |
| `workflows` | `[TemporalWorkflow]` | Workflow instances that were triggered by the deletion |

## Usage Example

```graphql
mutation {
  deleteReceivingInboundItem(id: "inbound_item_456") {
    deletedID
    workflows {
      id
      runID
      status
      type
      startedAt
      completedAt
      result
      failure
    }
  }
}
```

## JavaScript Example

```javascript
const DELETE_RECEIVING_INBOUND_ITEM = gql`
  mutation DeleteReceivingInboundItem($id: ID!) {
    deleteReceivingInboundItem(id: $id) {
      deletedID
      workflows {
        id
        runID
        status
        type
        startedAt
        completedAt
        result
        failure
      }
    }
  }
`;

const { data } = await client.mutate({
  mutation: DELETE_RECEIVING_INBOUND_ITEM,
  variables: {
    id: "inbound_item_456"
  }
});

console.log(`Deleted receiving inbound item: ${data.deleteReceivingInboundItem.deletedID}`);
```

## Important Notes

* Deleting a receiving inbound item removes it from the associated receiving inbound
* This operation may trigger workflows to adjust inventory expectations
* The deletion is permanent and cannot be undone
* Ensure proper authorization before performing this operation
* If this is the last item in a receiving inbound, consider whether the inbound itself should be deleted
* Related stock calculations may need to be updated after the deletion


---

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