> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/api-documentation/v2-api-reference/inventory-items/update-multiple-inventory-items.md).

# Update Multiple Inventory Items

Updates multiple inventory items in a single request. This consumes a single rate limit token rather than one token per item.

Each inventory item must include an `id` field so the correct record can be properly updated.

{% hint style="danger" %}
All fields should be passed through. Any empty fields will be set to blank on the record.
{% endhint %}

Legacy clients that cannot issue `PUT` can send `POST` with the `X-HTTP-Method-Override: PUT` header.

```json
{"openapi":"3.0.3","info":{"title":"Order Desk API","version":"2.0"},"tags":[{"name":"Inventory Items"}],"servers":[{"url":"https://app.orderdesk.me/api/v2","description":"Production"}],"security":[{"OrderDeskStoreId":[],"OrderDeskApiKey":[]}],"components":{"securitySchemes":{"OrderDeskStoreId":{"type":"apiKey","in":"header","name":"ORDERDESK-STORE-ID","description":"Your store ID, found under Store Settings on the API tab."}},"schemas":{"InventoryItemBatchWrite":{"allOf":[{"type":"object","required":["id"],"properties":{"id":{"type":"integer","description":"Each inventory item must include an `id` field so the correct record can be\nproperly updated.\n"}}},{"$ref":"#/components/schemas/InventoryItemFields"}]},"InventoryItemFields":{"type":"object","properties":{"name":{"type":"string"},"code":{"type":"string","description":"Product's unique SKU. This is how Order Desk matches an order line to an inventory\nrecord, so it must match the code that your orders arrive with.\n"},"price":{"type":"number","format":"double"},"cost":{"type":"number","format":"double","description":"Item cost in decimal format."},"weight":{"type":"number","format":"double","description":"The shipping weight of the item."},"stock":{"type":"integer","description":"The number of available units."},"variation_list":{"allOf":[{"$ref":"#/components/schemas/KeyValue"}],"description":"Collection of variations in key/value format, such as `{\"Size\": \"Large\", \"Color\":\n\"Red\"}`.\n"},"metadata":{"allOf":[{"$ref":"#/components/schemas/KeyValue"}],"description":"Collection of special information about the inventory item. Used by some\nintegrations.\n"},"manufacturer_sku":{"type":"string","description":"The SKU used by the manufacturer. This can be used as `print_sku`."},"location":{"type":"string","description":"Warehouse or fulfillment method responsible for the item."},"update_source":{"type":"string","description":"The name of the last system to update the item's details. Setting this allows those\nupdates to be excluded later using the `update_source_not` search parameter.\n"}}},"KeyValue":{"type":"object","additionalProperties":true,"description":"A collection in key/value format. Must be flat, with no nested arrays. Keys must be\nstrings, and values must be strings, numbers, booleans, or null.\n\nWhen the collection is empty, the API returns an empty array (`[]`) rather than an\nempty object. Treat both as \"no entries\" when parsing.\n"},"ResponseEnvelope":{"type":"object","required":["status"],"properties":{"status":{"type":"string","enum":["success","error"],"description":"Either `success` or `error`."},"message":{"type":"string","description":"Describes the result. Always present when an error occurs."},"execution_time":{"type":"string","description":"Time taken to process the request."}}}},"responses":{"BadRequest":{"description":"The request was rejected. `message` names the problem.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"Unauthorized":{"description":"Authentication failed. See the Authentication guide, and\nnote that an invalid store ID blocks your store rather than simply\nfailing the request.\n","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"RateLimited":{"description":"You are sending too fast. Wait `X-Retry-After` seconds. See\nthe Rate Limits guide.\n","headers":{"X-Tokens-Remaining":{"description":"Number of request tokens currently available.","schema":{"type":"integer"}},"X-Retry-After":{"description":"Seconds to wait before requests can resume.","schema":{"type":"integer"}}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"Error":{"description":"The request could not be completed.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}}}},"paths":{"/batch-inventory-items":{"put":{"tags":["Inventory Items"],"summary":"Update Multiple Inventory Items","description":"Updates multiple inventory items in a single request. This consumes a single\nrate limit token rather than one token per item.\n\nEach inventory item must include an `id` field so the correct record can be\nproperly updated.\n\n{% hint style=\"danger\" %}\nAll fields should be passed through. Any empty fields will be set to blank on\nthe record.\n{% endhint %}\n\nLegacy clients that cannot issue `PUT` can send `POST` with the\n`X-HTTP-Method-Override: PUT` header.\n","operationId":"updateMultipleInventoryItems","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"array","minItems":1,"items":{"$ref":"#/components/schemas/InventoryItemBatchWrite"}}}}},"responses":{"200":{"description":"The items were updated.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"400":{"$ref":"#/components/responses/BadRequest"},"401":{"$ref":"#/components/responses/Unauthorized"},"429":{"$ref":"#/components/responses/RateLimited"},"default":{"$ref":"#/components/responses/Error"}}}}}}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.orderdesk.com/api-documentation/v2-api-reference/inventory-items/update-multiple-inventory-items.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.