# Build your forecast with Mo

{% hint style="info" %}
**Quick Answer:** Mo can help you create forecasts from scratch, apply business rules across your catalog, and make targeted adjustments—all through natural conversation. Start by asking Mo to generate a forecast, then refine it with your business knowledge.
{% endhint %}

## What Mo Can Do for Forecasting

Mo transforms forecast creation from a manual, spreadsheet-heavy process into an interactive conversation. Instead of configuring settings and running reports, you describe what you need and Mo handles the execution.

**Mo helps you:**

* Generate initial forecasts based on your data
* Apply business rules across product categories
* Make targeted adjustments to specific SKUs
* Explore "what-if" scenarios
* Explain the reasoning behind forecast values

{% embed url="<https://www.youtube.com/watch?v=wfz7BUq7nMU>" %}
Vibe Demand Planning with Mo | Edit Your Forecast
{% endembed %}

***

## Getting Started with Mo Forecasting

### Generate a Forecast

Ask Mo to create a forecast using natural language:

**Example prompts:**

* "Create a bottom-up forecast for Q2 2026"
* "Generate a top-down forecast based on $5M revenue target for next quarter"
* "Build a forecast for my summer collection using last year's seasonal patterns"

Mo will select appropriate models and parameters based on your request and available data.

### Review and Understand

Once Mo generates a forecast, ask questions to understand the output:

* "Why is SKU-12345 forecasted so high for June?"
* "What data are you using for the new product projections?"
* "How does this compare to last year's actual performance?"

Mo provides transparent reasoning so you can validate the forecast against your business knowledge.

***

## Refining Your Forecast with Mo

After generating an initial forecast, refine it using Mo's two primary approaches:

### Mass Updates with Forecast Guidelines

When you need to apply consistent business rules across many products, share your guidelines with Mo:

"Apply these rules to my forecast:

* Summer products increase 40% from May through August
* New launches ramp to full demand over 6 weeks
* Discontinued items decrease 20% monthly"

Mo will process your guidelines and apply adjustments across the relevant SKUs.

### Surgical Edits for Specific SKUs

For targeted changes to individual products, describe the specific adjustment:

* "Increase SKU-ABC by 30% for the promotional period in March"
* "Match the new protein bar forecast to our chocolate bar launch last year"
* "Zero out the forecast for discontinued winter items after February"

{% content-ref url="/pages/0j4ySH8ZiAtDK6eRiQ77" %}
[Refine Your Forecast](/planning-and-execution/forecasting/refine-your-forecast.md)
{% endcontent-ref %}

***

## Scenario Planning with Mo

Mo excels at exploring different forecast scenarios:

**Test assumptions:**

* "What if BFCM sales increase 50% this year?"
* "Show me the forecast if we launch in Amazon in Q3"
* "What happens to inventory needs if lead times increase by 2 weeks?"

**Compare approaches:**

* "Compare a conservative vs. aggressive forecast for summer"
* "What's the difference between top-down and bottom-up for this category?"

Mo can create multiple scenarios and help you understand the tradeoffs between them.

***

## How Do I Review Mo's Bulk Changes Before They're Applied?

**Time Required:** 2–3 minutes per review

When Mo proposes bulk forecast changes — such as a seasonal uplift, a growth target, or a channel-wide adjustment — a **mass edit preview table** opens automatically so you can review every line before anything is applied.

**Key benefits:**

* **Full visibility:** See every proposed change before it lands in your forecast
* **Inline control:** Edit any value Mo proposed without rejecting the whole batch
* **Flexible review:** Organize and view changes the way your team thinks about the plan

### What's in the Mass Edit Table?

| Feature                  | What it does                                                                                         |
| ------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Row expansion**        | Drill into product line, channel, and time period groupings to see exactly what's changing and where |
| **Group-by**             | Organize changes by SKU, channel, or another dimension to review at the right level of detail        |
| **Channel-only view**    | Toggle off SKU grouping to see aggregated totals per channel across all items (read-only view)       |
| **Dollar / Unit toggle** | Switch between viewing proposed changes in units or revenue                                          |
| **Inline editing**       | Adjust any value Mo has proposed directly in the table before committing                             |

### Step-by-Step: Reviewing and Committing Mass Edits

{% stepper %}
{% step %}

#### Ask Mo to Make Bulk Changes

Prompt Mo with a bulk forecast request — for example, applying a seasonal uplift, a revenue target, or a category-wide adjustment across channels.

Mo will process your request and prepare a set of proposed changes.
{% endstep %}

{% step %}

#### Review the Preview Table

The mass edit table opens automatically, showing every line Mo intends to modify.

* Use **row expansion** to drill into specific product lines, channels, or time periods
* Use **group-by** to reorganize the view by SKU, channel, or another dimension
* Use the **Dollar / Unit toggle** to switch between revenue and units view

{% hint style="warning" %}
Nothing is applied to your forecast at this stage. You are in review mode only.
{% endhint %}
{% endstep %}

{% step %}

#### Adjust Any Values Inline

If a specific value looks off, click directly into that cell and edit it. You can keep Mo's changes everywhere else and only override what needs to change.

This is faster than rejecting the full batch and re-prompting Mo.
{% endstep %}

{% step %}

#### Commit When You're Ready

Once you're satisfied with the changes — including any manual overrides — click **Commit** to apply the edits to your forecast.

{% hint style="success" %}
Your forecast is updated only at this point. All changes reflect both Mo's proposals and any inline edits you made.
{% endhint %}
{% endstep %}
{% endstepper %}

### Mass Edit Tips

**Use the dollar/unit toggle to sense-check Mo's numbers.** If your team plans in revenue, switch to dollar view before committing — it's easier to spot outliers that way.

**Toggle to channel-only view for high-level validation.** Uncheck "SKU" in the grouping options to see aggregated totals per channel. This is useful when you want to validate overall channel impact without drilling into individual items.

**Expand rows before approving top-line numbers.** A channel or time-period breakdown can reveal a concentration of changes that looks fine in aggregate but is off at the detail level.

**Edit inline instead of rejecting the batch.** If one value is wrong, adjust it directly in the table. There's no need to redo Mo's work across all the other lines that are correct.

***

## Understanding Mo's Forecast Calculations

After creating your forecast and reviewing any adjustments, you can dig deeper into how Mo arrived at each number — directly within the platform.

### Clicking Into a Cell

When you click on any white (editable) cell in your forecast, Mo surfaces two quick-action options:

* **Explain This** — Mo breaks down how it calculated the forecasted number for that specific SKU and channel, giving you full visibility into the logic behind the figure.
* **Sales History** — Mo displays the historical sales data for that SKU by channel, so you can contextualize the forecast against past performance.

### Using the ? Icon

On the left-hand side of the screen, you'll see a **?** icon. Clicking this opens the Mo chat box, where you can ask any question related to your forecast — whether it's about a specific SKU, a channel trend, or the methodology behind a number. This opens a full conversation with Mo, allowing you to explore further without leaving the forecasting view.

{% hint style="info" %}
**Build this into your workflow:** After creating your forecast and reviewing adjustments, take a moment to click into Mo and validate the numbers. Understanding the *why* behind a forecast leads to more confident decisions.
{% endhint %}

***

## Locking Your Forecast

When you've finalized your forecast and want to prevent further changes:

{% hint style="warning" %}
You can lock your forecast to prevent adjustments, including changes by Mo. This is useful when you've completed planning and want to preserve the forecast for execution.
{% endhint %}

To lock a forecast, navigate to your forecast scenario and select the lock option. Locked forecasts can be unlocked later if you need to make additional changes.

***

## Tips for Working with Mo

**Be specific:** "Increase outdoor furniture 50% from April through September" works better than "increase summer products"

**Provide context:** "We're running a major promotion" or "this product is being discontinued" helps Mo make better adjustments

**Iterate:** Start with broad guidelines, review the results, then make surgical edits for fine-tuning

**Ask questions:** If a forecast value seems wrong, ask Mo to explain its reasoning before making changes

***

## Related Guides

{% content-ref url="/pages/0j4ySH8ZiAtDK6eRiQ77" %}
[Refine Your Forecast](/planning-and-execution/forecasting/refine-your-forecast.md)
{% endcontent-ref %}

{% content-ref url="/pages/XFbBg0MSQpAiqVkBJo75" %}
[How to Create a Forecast](/planning-and-execution/forecasting/how-to-create-a-forecast.md)
{% endcontent-ref %}

{% content-ref url="/pages/sb2SV5PNVIJy5jUlhar2" %}
[Meet Mo](/mo/meet-mo.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.moselle.io/planning-and-execution/forecasting/build-your-forecast-with-mo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.