> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kibocommerce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Items

> Deletes inventory for multiple products in a single request. Accepts an array of up to 1,000 product identifiers per request (each specified by `partNumber`, `upc`, or `sku`); the recommended batch size is 500 items. The operation is asynchronous — the endpoint returns immediately with one job ID per affected location for progress tracking. Use `dryRun: true` to preview deletion scope before executing. For batch sizing, self-throttling patterns, step-by-step execution workflow, and job monitoring guidance, see the <a href="/pages/bulk-inventory-deletion">Bulk Inventory Deletion guide</a>.



## OpenAPI

````yaml /openapi/openapi_inventory.json post /commerce/inventory/v5/inventory/deleteItems
openapi: 3.0.0
info:
  description: |-
    <div id="overview_INVENTORY">
                <h2>INVENTORY</h2>
                <p>Use the Inventory API to retrieve the inventory levels of requested products, refresh and adjust current
                    stock levels at fulfillment locations, and tag segmented inventory for different channels. When using tags for inventory segmentation, inventory records are separated into categories to identify
                    which portions of its
                    total quantity are intended for different channels, customer groups, fulfillment methods, or other
                    needs.
                    This allows for setting a percentage of the quantity that would be available for each category and
                    setting discrete units at the location level as available for each category. For example, tags could
                    define how much of each
                    inventory record is set aside for a certain sales channel: the Kibo storefront, Walmart, or Amazon. The
                    percentages of the
                    inventory allotted for each channel would add up to 100% - the Kibo storefront could have 80% of the
                    inventory, Amazon 10%, and Walmart 10%. For more information, see the <a href="/developer-guides/inventory">Inventory guides</a>.</p>
                <p>Use the <strong>Inventory</strong>, <strong>Inventory Allocation</strong>, and <strong>Modify Inventory</strong> resources to retrieve and update inventory levels.</p>  
                <p>Use the <strong>Inventory Job</strong> resource to retrieve information about your pending inventory update processing jobs.</p> 
                <p>Use the <strong>Inventory Tag</strong> and <strong>Tag Category</strong> resources to segment your inventory records.</p> 
            </div>
  title: Inventory
  version: 0.0.1
servers:
  - description: Kibo Base URL
    url: '{baseUrl}/api'
    variables:
      baseUrl:
        default: https://t1000000.sb.usc1.gcp.kibocommerce.com
        description: Base URL
security:
  - bearerAuth: []
paths:
  /commerce/inventory/v5/inventory/deleteItems:
    post:
      tags:
        - ModifyInventory
      summary: Delete Items
      description: >-
        Deletes inventory for multiple products in a single request. Accepts an
        array of up to 1,000 product identifiers per request (each specified by
        `partNumber`, `upc`, or `sku`); the recommended batch size is 500 items.
        The operation is asynchronous — the endpoint returns immediately with
        one job ID per affected location for progress tracking. Use `dryRun:
        true` to preview deletion scope before executing. For batch sizing,
        self-throttling patterns, step-by-step execution workflow, and job
        monitoring guidance, see the <a
        href="/pages/bulk-inventory-deletion">Bulk Inventory Deletion guide</a>.
      parameters:
        - description: Site ID
          in: query
          name: x-vol-site
          required: false
          schema:
            type: integer
      requestBody:
        $ref: '#/components/requestBodies/DeleteItemsRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteItemResponse'
          description: Success
        '400':
          description: Bad Request
components:
  requestBodies:
    DeleteItemsRequest:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/DeleteItemsRequest'
      description: Request to batch delete items
      required: true
  schemas:
    DeleteItemResponse:
      description: Delete Item Response
      properties:
        dryRun:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        itemsDeleted:
          description: Items deleted due to the request
          items:
            $ref: '#/components/schemas/M_DeleteItem'
          type: array
        jobIDs:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        totalAuditsDeleted:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        totalInventoryEntriesDeleted:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        totalLocationsAffected:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        totalPickWavesDeleted:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        totalProductsDeleted:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
      title: Delete Item Response
      type: object
    DeleteItemsRequest:
      description: Request needed for deleting inventory
      properties:
        allLocations:
          description: >-
            Flag used to request deletion of inventory across all locations
            (overrides locationCodes).
          type: boolean
        dryRun:
          description: Flag used to differentiate between a test and a non-test run.
          type: boolean
        explicit:
          description: >-
            Flag used to request explicit inventory, location, pick wave, and
            audit information for each request item.
          type: boolean
        items:
          description: 'List of items to delete. Supports basic regex operators: .*+?^$[]'
          items:
            $ref: '#/components/schemas/InventoryItem'
          type: array
        locationCodes:
          description: >-
            An array of locationCodes to be considered for item-deletion
            purposes. Optional.
                All locationCodes associated with the requesting tenant will be considered if no locationCodes are provided.
          items:
            type: string
          type: array
        tags:
          $ref: '#/components/schemas/tags'
      title: Delete Item Request
      type: object
    M_DeleteItem:
      description: Delete Item Model
      properties:
        auditIDs:
          description: List of audit identifiers associated with the deleted item
          items:
            type: integer
          type: array
        inventoryIDs:
          description: List of inventory identifiers associated with the deleted item
          items:
            type: integer
          type: array
        itemIdentifier:
          $ref: '#/components/schemas/ProductIdentifier'
        locationCodes:
          description: List of location codes associated with the deleted item
          items:
            type: string
          type: array
        locationIDs:
          description: List of location identifiers associated with the deleted item
          items:
            type: integer
          type: array
        productID:
          description: Product Identifier
          type: integer
      title: M_DeleteItem
      type: object
    InventoryItem:
      description: Item
      properties:
        condition:
          type: string
        date:
          format: date-time
          type: string
        lotCode:
          type: string
        partNumber:
          description: Part/Product Number
          type: string
        serialNumber:
          type: string
        sku:
          description: Stock Keeping Unit
          type: string
        tags:
          $ref: '#/components/schemas/tags'
        upc:
          description: Universal Product Code
          type: string
      title: Item
      type: object
    tags:
      additionalProperties:
        type: string
      description: Associative Map of <String, String> for tagCategoryName => tagName
      type: object
    ProductIdentifier:
      description: Product Identifier Model
      properties:
        partNumber:
          description: Part/Product Number
          type: string
        sku:
          description: Stock Keeping Unit
          type: string
        upc:
          description: Universal Product Code
          type: string
      title: ProductIdentifier
      type: object
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: JWT Authorization header using the Bearer scheme.
      scheme: bearer
      type: http

````