> ## 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.

# Import & export

> Download the demand plan to a spreadsheet and upload forecasts or targets in bulk

## What this page is for

Sometimes you need the plan in a spreadsheet — to share it, to work on it offline, or to load a lot of numbers at once. Spherecast has two tools: **Download Demand** to export, and **Upload Forecast** to import. Both work in the background and notify you when they finish.

## Download Demand

Choose **forecast** or **targets**, then set the options.

### For a forecast download

| Option            | Choices                                                                             |
| ----------------- | ----------------------------------------------------------------------------------- |
| **Forecast type** | Baseline, Baseline Adj., or Consensus (default **Consensus**), plus any custom line |
| **Lag**           | Optionally pull from a snapshot at a chosen lag                                     |
| **Filters**       | Channels, markets, groups, categories (with exclude), sales rep                     |
| **Granularity**   | Weekly or Monthly                                                                   |
| **Date range**    | The period to export                                                                |
| **Include**       | Revenue and/or units                                                                |
| **Aggregate by**  | Market, channel, or group                                                           |
| **Other**         | Exclude zero demand, merge supersessions                                            |

The output is an **.xlsx** file. If you pick **multiple markets without aggregation**, Spherecast asks whether to turn aggregation on so the file stays readable.

## Upload Forecast

Choose **forecast** or **target**, then set where the numbers land.

| Option                      | Choices / notes                                                     |
| --------------------------- | ------------------------------------------------------------------- |
| **Apply to**                | Target, a custom line, or Consensus                                 |
| **Upload past periods**     | Include months that have already closed                             |
| **Create adjustments**      | Turn the upload into reviewable adjustments, with a description     |
| **Only apply to new items** | Defaults **on** — protects established products                     |
| **Warehouse allocations**   | Per channel → warehouse; each channel's splits must sum to **100%** |

### File limits

* Formats: **CSV, XLS, XLSX**
* Maximum size: **50 MB**

### Errors you might see

Spherecast flags problems instead of loading bad data:

* Inactive, missing, or duplicate SKUs
* Missing or unknown channels
* Invalid market–channel combinations

### Target upload rules

* Target uploads are **blocked** if product-level (SKU) targets already exist or a **scenario is active**.
* If your uploaded targets would overwrite existing goals, an **override confirmation** appears first.

## Step by step: upload a Consensus forecast

1. Open **Upload Forecast** and choose **forecast**.
2. Set **Apply to** = **Consensus**.
3. Decide whether to **upload past periods** and whether to **create adjustments**.
4. Leave **only apply to new items** on unless you mean to overwrite existing items.
5. Check each channel's warehouse allocations sum to **100%**.
6. Attach your file (CSV/XLS/XLSX, under 50 MB) and submit.
7. Fix any flagged SKU or channel errors and resubmit.
8. Wait for the completion notification.

## Example

A planner exports Consensus for the Midwest and West markets, monthly, in units, aggregated by channel — one clean .xlsx to share with sales. Later, they receive a revised file, open **Upload Forecast**, set **Apply to = Consensus**, confirm each channel's warehouse splits total 100%, and submit a 6 MB XLSX. Two duplicate SKUs are flagged; they remove the duplicates and resubmit, and a notification confirms the load.

> **Tip:** Keep **only apply to new items** on unless you truly intend to replace numbers for existing products — it's the safeguard that stops a bulk upload from wiping out work already in the plan. See **[Targets](/guide/demand-planning/targets)** for how target uploads interact with top-down goals.