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

# Products — Stocking

> Choose which warehouses stock each product and which warehouse-products are included in planning.

## What this page is for

This page controls **which warehouses stock each product**, and whether each warehouse-product is **Visible** — that is, included in planning. Expand a product row to see every warehouse, along with the available stock at each one, and switch planning on or off per warehouse.

Think of Visible as "planned here." When a warehouse-product is visible, Spherecast forecasts it, watches its coverage, and can recommend orders for it. When it is not visible, that warehouse is left out of the plan for that product.

## What you can set

| Column                  | What it means                                                                                                                                                              |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Product / Warehouse** | The product, and each warehouse it can be stocked in when expanded.                                                                                                        |
| **SKU**                 | The stock-keeping identifier, shown with the available stock at each warehouse.                                                                                            |
| **Visible**             | A per-warehouse on/off switch for whether the product is planned at that warehouse. The product row summarizes how many warehouses are visible, for example "3/5 visible." |

You can add a warehouse to a product, and bulk-update visibility across several selected products at once. Turning a warehouse off warns you about the planning impact first, so you don't accidentally drop a location that is actually being planned.

## How it affects planning

Visibility decides where a product appears in your plan. Making a warehouse visible brings it into forecasting and replenishment for that product; hiding it takes that warehouse-product out of the plan entirely — no forecast, no coverage signals, no recommended orders there.

**Important:** this page does **not** hold reorder point, minimum, maximum, or review period. The reorder cadence lives on [General](/general) (the **Order cycle**), and the buffer lives on [Safety](/safety) (**safety stock**). Stocking only answers "does this product plan at this warehouse, yes or no."

## Step by step: start planning a product at a new warehouse

1. Find the product and expand it to see its warehouses.
2. Add the warehouse to the product if it isn't listed yet.
3. Turn **Visible** on for that warehouse.
4. Confirm the product row now counts the extra location (for example "3/5 visible" becomes "4/5").
5. Set the buffer for the new warehouse on [Safety](/safety), since safety stock is per warehouse.

## Example

A product is stocked in five warehouses but only actively sold from three. You set the two non-selling warehouses' **Visible** switch to off, and the product row reads **3/5 visible**. Spherecast now plans the product at the three selling locations and ignores the other two — no forecasts or orders are generated for them.

> **Note:** Visibility is per warehouse-product. After you make a warehouse visible, set its buffer on [Safety](/safety). Warehouse setup itself lives under [Locations & warehouses](/guide/network/locations-warehouses).
