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

# S&OP lines

> Configure the editable rows of the demand plan — the adjustment layer between the statistical Baseline and the agreed Consensus.

## What this page is for

This page configures the editable rows — the **"lines"** — of your demand plan. Each line is an **S\&OP (Sales & Operations Planning)** planning row that a planner types adjustments into, such as "Promo," "Sales input," or "Distribution gain."

Every line you set up here appears as an **editable row under each product and channel** in the demand plan. Together, these lines form the **adjustment layer** that sits between the statistical **Baseline** and the agreed **Consensus**.

## What you set up

| Field                           | What it controls                                                                                                                                                     |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                            | The line's label as it appears in the plan (for example, "Promo").                                                                                                   |
| Order                           | Drag to reorder — sets the display order of the lines in the plan.                                                                                                   |
| Include in Baseline adjustments | When **ON**, this line's values roll up into **Baseline Adj.** When **OFF**, the values are still stored but do **not** contribute — the line is informational only. |

## How it works

The core math is simple:

> **Baseline + the sum of all "included" S\&OP lines = Baseline Adj.**

* **Baseline** is the statistical starting forecast.
* Each S\&OP line adds (or subtracts) an adjustment. Only lines with **Include in Baseline adjustments** turned **ON** roll up.
* **Baseline Adj.** is the result of that roll-up. It is **derived** — you never type into it directly.

From there, a planner can push **Baseline**, **Baseline Adj.**, or a **single line** into **Consensus** — the agreed number the business plans around.

A line switched **OFF** for Baseline adjustments still stores whatever a planner enters, but those values sit to the side for reference and do not change Baseline Adj. Use OFF lines to capture context you want visible without moving the plan.

> **Note:** "Baseline Adj." and "Consensus" are default names and may be renamed for your company. Whatever the labels, **Baseline Adj. stays derived** — it is always the roll-up, never a typed-in value.

## Step by step: add and order a line

1. Choose **Add line** and give it a clear **Name** (for example, "Promo").
2. Decide whether it should roll into the plan: turn **Include in Baseline adjustments** ON to make it count, or OFF to keep it informational.
3. **Drag** the line up or down to set where it appears in the plan.
4. Repeat for each adjustment type your team uses.

## Deleting a line

**Deleting a line removes it and every adjustment stored in it, across all products and channels. This cannot be undone.** Delete only lines you are certain you no longer need.

## Example

For one product/channel:

* **Baseline** = 1,000
* **Promo** line = **+200**, with **Include in Baseline adjustments** turned **ON**
* **Baseline Adj.** = 1,000 + 200 = **1,200**

If you had left the Promo line's include toggle **OFF**, the +200 would still be recorded on the line, but **Baseline Adj.** would remain **1,000**. A planner might then push **Baseline Adj. (1,200)** into **Consensus** as the agreed number.

> **Tip:** Name lines the way your team talks about them, and turn the include toggle **ON** only for lines that should move the plan. See also [Adjustments](/guide/demand-planning/adjustments), [Building consensus](/guide/demand-planning/building-consensus), and [Demand profiles](/demand-profiles).