> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/products/stock-locations.md).

# Stock Locations

## Stock Locations

## Introduction

Stock locations represent physical storage locations from which stock is shipped. If you sell different products such as clothes and merchandise you can set up multiple Stock Locations.

## Architecture

The OMS can manage your store's inventory. This allows you to keep track of your current stock, backordered stock, as well as sold and shipped inventory. Because inventory touches orders, shipments, and the contents of your physical warehouse, there are many essential moving parts.

On-hand inventory is tracked using your **Stock Item**. Each\*\* Variant\*\* in your store has a corresponding **Stock Item** with a c**ount\_on\_hand** value that represents the number of items you have in stock.

If you have two stock locations, there are two Stock Items for each variant in your store: one for each **Stock Location**. Each stock item count represents the number of stock items at a specific location.

When creating a Stock Location ensure to provide all **general** and **address** information:

**Name** is required: This is the name of your Stock location, i.e., HQ or Shipstation or the name of your warehouse.

**Code** is not required and can be used as a unique text identifier. This can be helpful when trying to determine stock locations in integrations.

**Internal Name:** This field is only used internally

**Channels** If a Channel is specified, this stock location will only fulfill orders mapped to that channel. If this field is left empty, the OMS will use the stock location to fulfill all orders regardless of their channel

{% hint style="info" %}
**Channels** are a way to define/organize orders within the OMS. Effectively a channel says “how” and which avenue an order came through. If an order is created manually via the OMS admin, the channel defaults to “admin.” Suppose the order was a subscription, the channel defaults to “subscription,” etc.
{% endhint %}

**Fulfillment Service:** Select your 3PL. See the **Fulfillment Services** section below.

**Address:** Address of your stock location

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-437d4d746c7ebb773757f0fe2c68e73f65d0aa2c%2Fstock-locations-1.jpg?alt=media)

**Settings section**

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-e58d4b5ee8076002310afaf8d64d88ca160a949e%2Fstock-locations-2.jpg?alt=media)

**Active:** If unchecked, your stock will not be available at this location. Check to activate.

**Default:** Check if this Stock Location is your default location.

**Backorderable Default:** When checked, stock items in this location will default to allowing backorders.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-d1ebd5c6ce85439c69b965749429357b69ddccc3%2Fstock-locations-3.jpg?alt=media)

**Propagate All Variants:** When checked, this will create a stock item for each variant at this location.

**Restock Inventory:** Returned inventory can be added back to this stock location when this option is checked. When you perform an RMA and select that stock location, it will not restock if the checkbox is not selected.

**Fulfillable:** When unchecked, this indicates that items in this location don't require actual fulfillment. The system will not send an email confirmation, and there will be no stock verification when shipping.

**Check Stock on Transfer:** The inventory level will be checked when performing stock transfers.

After creating your Stock Location, navigate to your Product Store Stock. Products --> product --> Product Stock

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-e42a9173e4fb4f6cb43ff7b76bc861b6348aabb2%2Fstock-locations-4.jpg?alt=media)

{% hint style="info" %}
For more information about Products and Inventory please refer to this document
{% endhint %}

###


---

# 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.chord.co/chord-oms/products/stock-locations.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.