ReceivingInboundItem

ReceivingInboundItem Type

Represents an individual item within a receiving inbound shipment. ReceivingInboundItem specifies the products expected to be received, their quantities, and related receiving information as part of an inbound shipment process.

Fields

Field	Type	Description
id	ID!	Unique identifier of the receiving inbound item
tenantID	UUID!	Tenant identifier
dataTypeID	UUID	DataType identifier for schema validation
dataTypeSlug	String	DataType slug for easier reference
data	Map	Custom metadata stored as JSON
createdAt	Time!	Creation timestamp
createdBy	UUID!	User identifier who created the item
updatedAt	Time	Last update timestamp
updatedBy	UUID	User identifier who last updated the item
deletedAt	Time	Deletion timestamp
deletedBy	UUID	User identifier who deleted the item
sku	String!	Stock Keeping Unit identifier of the item to receive
inboundID	ID!	Reference to the parent ReceivingInbound shipment
quantity	Int!	Expected quantity of the item to be received
inbound	ReceivingInbound!	The parent receiving inbound shipment

Interfaces

• Node

Usage Example

query {
  receivingInboundItems(first: 10) {
    edges {
      node {
        id
        sku
        quantity
        inboundID
        inbound {
          id
          supplierID
          status
          expectedDate
        }
        data
        createdAt
        updatedAt
      }
    }
  }
}

Query by Inbound Shipment

query {
  receivingInboundItems(
    where: {
      inboundID: "inbound-uuid-here"
    }
  ) {
    edges {
      node {
        id
        sku
        quantity
        data
      }
    }
  }
}

Mutation Examples

Create a ReceivingInboundItem

mutation {
  createReceivingInboundItem(input: {
    sku: "PROD-001"
    inboundID: "inbound-uuid-here"
    quantity: 100
    dataTypeSlug: "inbound_item"
    data: {
      expected_condition: "new"
      lot_number: "LOT-2024-001"
      expiry_date: "2025-12-31"
      special_handling: "temperature_controlled"
    }
  }) {
    receivingInboundItem {
      id
      sku
      quantity
      inbound {
        id
        supplierID
      }
    }
    workflows {
      id
      status
    }
  }
}

Update a ReceivingInboundItem

mutation {
  updateReceivingInboundItem(
    id: "item-uuid-here"
    input: {
      quantity: 95
      data: {
        received_quantity: 95
        condition: "good"
        variance_reason: "shipping_damage"
        quality_check_passed: true
        receiver_notes: "5 units damaged in transit"
      }
    }
  ) {
    receivingInboundItem {
      id
      sku
      quantity
      data
    }
    workflows {
      id
      status
    }
  }
}

Delete a ReceivingInboundItem

mutation {
  deleteReceivingInboundItem(id: "item-uuid-here") {
    deletedID
    workflows {
      id
      status
    }
  }
}

Relations

• ReceivingInboundItem N:1 ReceivingInbound: Multiple items belong to a single inbound shipment

• ReceivingInboundItem N:1 DataType: Items can reference a DataType for schema validation

• ReceivingInboundItem references InventoryItem via SKU: Items are received and matched to inventory by SKU

Common Use Cases

• Purchase Order Receiving: Processing expected items from supplier purchase orders

• Return Processing: Handling returned merchandise from customers

• Transfer Receipts: Receiving items transferred from other warehouse locations

• Quality Control: Tracking inspection results and condition assessments

• Variance Management: Recording discrepancies between expected and received quantities

Receiving Status Tracking

Use the data field to track receiving progress and details:

{
  "status": "expected|receiving|received|inspected|put_away",
  "received_quantity": 95,
  "received_condition": "good|damaged|expired|rejected",
  "receiver_id": "user-456",
  "receive_time": "2024-01-15T14:30:00Z",
  "lot_number": "LOT-2024-001",
  "expiry_date": "2025-12-31",
  "quality_notes": "All items passed inspection",
  "variance_reason": "shipping_damage",
  "put_away_location": "A1-B2-C3"
}

Quality Control Integration

ReceivingInboundItems support quality control workflows:

• Track inspection results in the data field

• Record condition assessments (good, damaged, expired)

• Document quality control notes and decisions

• Link to quality control workflows for complex inspections

Best Practices

• Always validate supplier information and purchase orders before creating items

• Use the data field to store receiving-specific information like lot numbers and expiry dates

• Implement variance tracking to monitor supplier performance

• Consider implementing automatic inventory updates upon successful receipt

• Monitor receiving workflows to ensure timely processing

• Link items to appropriate storage locations during put-away operations