# Update Warehouse

`PATCH /inventory/warehouses/{id}`

Group: Inventory › Warehouses · Operation ID: `updateWarehouse`

Updates the warehouse with the given identifier. Only the fields in the request body change.

Everything omitted from the request body is left as it was. warehouseTypeId is the one field where null means something: pass null to clear the warehouse type, which lets the warehouse allow every document type again. A warehouse that already has inventory transactions cannot be moved to another entity. The response is only the warehouse's id. Read the updated record with GET inventory/warehouses/:id when you need its state after the update.

[Open in the interactive reference](https://docs.api.lensing.ai/?op=updateWarehouse)

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | `"v1"` | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `Idempotency-Key` | header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored. |
| `id` | path | string | yes | The unique identifier for the warehouse to update. |

## Request body

Required, `application/json`: updateWarehouseInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `locationCode` | string | no | The location code of the warehouse, for example 'WH-01'. It must stay unique within the tenant. Reusing the warehouse's own current code is not a collision. |
| `name` | string | no | The site name of the warehouse. |
| `entityId` | string | no | The unique identifier for the legal entity that owns this warehouse. See id on GET base/entities. A warehouse that already has inventory transactions cannot be moved to another entity: the platform refuses it and the call fails with a validation error. |
| `inventoryLocationType` | string, one of `"WAREHOUSE"`, `"STORE"`, `"VIRTUAL_QC"`, `"VIRTUAL_RECEIVING"`, `"VIRTUAL_SHIPPING"`, `"EXTERNAL_3PL"`, `"EXTERNAL_CONSIGNMENT"` | no | The kind of location. |
| `isActive` | boolean | no | Whether the warehouse can be selected on new inventory documents. Set it to false to retire the warehouse without deleting it: its stock, transactions and bins keep pointing at it and new documents cannot select it. |
| `isPrimaryReceiving` | boolean | no | Whether this is the entity's primary receiving warehouse. At most one warehouse per entity is meant to be the primary receiving warehouse. It is not enforced. |
| `warehouseTypeId` | string or null | no | The unique identifier for the warehouse type, which limits the document types the warehouse allows. Pass null to clear it, which lets the warehouse allow every document type again. An unknown identifier fails the call with WAREHOUSE_TYPE_NOT_FOUND. There is no endpoint for it. |
| `addressLine1` | string | no | The first address line: street number and name, or PO box. |
| `addressLine2` | string | no | The second address line: apartment, suite, unit, building or floor. |
| `city` | string | no | The city or locality. |
| `stateProvince` | string | no | The state, province or region. |
| `postalCode` | string | no | The postal or ZIP code. |
| `countryCode` | string | no | The country of the address. Format ISO 3166-1 alpha-2, for example 'NL'. It is not validated against the ISO list. |
| `region` | string | no | A free-text business region grouping, independent of country and state. |

Example:

```json
{
  "locationCode": "<locationCode>",
  "name": "<name>",
  "entityId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "inventoryLocationType": "WAREHOUSE",
  "isActive": false,
  "isPrimaryReceiving": true,
  "warehouseTypeId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "addressLine1": "<addressLine1>",
  "addressLine2": "<addressLine2>",
  "city": "<city>",
  "stateProvince": "<stateProvince>",
  "postalCode": "<postalCode>",
  "countryCode": "<countryCode>",
  "region": "<region>"
}
```

## Response

`200` Success

Under `data` (updateWarehouseOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The unique identifier for the warehouse. |

## Response headers

- `Idempotency-Replayed` — Present and `true` only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as `false`.

## Errors

| Code | Status |
| --- | --- |
| `NOT_FOUND` | 400 |
| `DUPLICATE_LOCATION_CODE` | 400 |
| `ENTITY_NOT_FOUND` | 400 |
| `WAREHOUSE_TYPE_NOT_FOUND` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: NOT_FOUND, DUPLICATE_LOCATION_CODE, ENTITY_NOT_FOUND, WAREHOUSE_TYPE_NOT_FOUND
- `401` — Missing or invalid access token
- `403` — Not authorized
- `404` — Not found
- `409` — The Idempotency-Key is still being processed by another request.
- `422` — The Idempotency-Key was already used with a different request payload.
- `429` — Too many requests
- `500` — Internal server error