> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/planning-and-execution/replenishment/core-workflow/create-a-production-plan.md).

# Create a Replenishment or Allocation Plan

{% hint style="info" %}
**Quick Answer:** Go to **Planning** in the left nav, click **Create Plan**, and follow the two-step wizard: name your plan and choose a type, then link a forecast, select locations, and set a coverage period. Once the plan is ready, click the green **Generate Purchase Orders** button — Mo will open automatically and create your POs for review.
{% endhint %}

## Watch: End-to-End Production Planning Walkthrough

Not sure where to start? This video walks through the full process — what a production plan actually is, how to navigate it, and how to generate orders at the end. The second half covers how Mo fits into the workflow once your plan is built.

**What's covered:**

* The journey from forecast to production plan (and what usually gets lost along the way)
* Replenishment vs. allocation — knowing which lens to plan through
* How safety stock, lead time, and MOQ factor into an executable plan
* Navigating the plan table and reviewing buy recommendations
* Generating purchase orders and where Mo accelerates the process

{% embed url="<https://www.youtube.com/watch?v=l7faaxHIMgA>" %}
End-to-end production planning walkthrough in Moselle
{% endembed %}

## What Is a Production Plan?

**A production plan in Moselle** is a time-series buy schedule that turns your forecast into concrete order recommendations. It shows how much to order, when to order, and what will happen to your inventory levels if you follow — or deviate from — the plan.

Every plan is linked to a forecast scenario, so demand signals flow directly into the replenishment math. When your forecast changes, you can rebuild the plan to reflect the latest projections.

**Time Required:** 5–10 minutes\
**Difficulty:** Beginner

**Before you begin, make sure you have:**

* [ ] An active Moselle account with at least one warehouse configured
* [ ] At least one forecast created and saved
* [ ] Supplier and lead time data configured (for best recommendations)

{% hint style="success" %}
Plans require an existing forecast. [Learn how to create a forecast](/getting-started/fast-tutorial/create-a-forecast.md) before proceeding.
{% endhint %}

***

## Choose Your Plan Type

From the **Planning** page, click **Create Plan**. Before filling in any details, choose the type of plan you need:

### Replenishment Plan

**A replenishment plan** determines what to reorder from suppliers and when. Moselle identifies at-risk items and recommends order quantities based on your forecast, current stock, lead times, and safety stock targets.

Use this when you need to **place new purchase orders** with suppliers.

### Allocation Plan

**An allocation plan** distributes existing inventory across multiple locations — warehouses, retail stores, or sales channels. No new orders are placed; inventory is moved or committed from existing stock.

Use this when you have **stock on hand** that needs to be assigned across locations rather than reordered.

***

## Step 1: Name Your Plan

{% stepper %}
{% step %}

### Set the Basics

Fill in the foundational details for your plan:

| Field               | Description                                                                    |
| ------------------- | ------------------------------------------------------------------------------ |
| **Plan Name**       | A memorable name for easy reference (e.g., "Q3 Replenishment — North America") |
| **Plan Type**       | Replenishment or Allocation (selected above)                                   |
| **Coverage Period** | The date range for this plan — how far out you want to plan orders             |

**Coverage Period guidance:**

* **Short-lead-time brands (< 4 weeks):** 3–4 months of coverage
* **Long-lead-time brands (ocean freight, 3–6 month lead times):** 6–12 months of coverage
* **Seasonal businesses:** Cover through the end of your peak season plus one reorder cycle

{% hint style="info" %}
**How Moselle uses your coverage period:** Moselle works backward from your coverage end date. Given your lead times, it calculates the latest date you can place each order and still be in stock by the time you need inventory. This is why a longer coverage window surfaces order trigger dates earlier — so you're never caught with too little runway to act.
{% endhint %}

Click **Next** when ready.
{% endstep %}
{% endstepper %}

***

## Step 2: Configure Your Plan

{% stepper %}
{% step %}

### Link a Forecast Scenario

Select the forecast that will drive your buy recommendations. This is the demand signal your plan uses to calculate how much inventory you'll need across the coverage period.

{% hint style="info" %}
Each plan is a snapshot of the forecast at the time it was generated. If your forecast has been updated since you created the plan, click **Rebuild** to refresh the recommendations.
{% endhint %}
{% endstep %}

{% step %}

### Select Locations

Choose which warehouse or location this plan is for. Moselle calculates inventory projections and buy quantities relative to the stock at the selected location.
{% endstep %}

{% step %}

### Filter Products

Decide which products to include:

| Option                       | What It Includes                                  |
| ---------------------------- | ------------------------------------------------- |
| **SKUs (including bundles)** | All product variations, including bundle SKUs     |
| **Core SKUs**                | Roll up bundles and cases to their component SKUs |
| **Components**               | Break down to the component/ingredient level      |

**Optional settings:**

* **All Products Toggle** — Include products with no current planning recommendations (useful for reviewing the full catalog)
* **Transit Lead Times** — Default lead time in days per month, used as a fallback for items without a specific Transit Lead Time attribute
* **Safety Stock** — Default safety stock buffer in days, used as a fallback for items without a specific Safety Stock attribute
  {% endstep %}

{% step %}

### Set Order Frequency

Choose how the plan groups time periods:

| Frequency   | Best For                                     |
| ----------- | -------------------------------------------- |
| **Monthly** | Most brands; standard planning cadence       |
| **Weekly**  | High-velocity SKUs or short lead times       |
| **Daily**   | Advanced use cases with daily reorder points |

{% hint style="warning" %}
**Important:** The frequency setting cannot be changed after a plan is created. If you need a different cadence, create a new plan.
{% endhint %}

Click **Create Replenishment Plan** (or **Create Allocation Plan**) to generate your plan. It will appear in the Plans list, nested under the forecast scenario you selected.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Optional — Optimization Method (Beta):** Replenishment plans support an opt-in **Optimized** build that consolidates buys across the full coverage horizon instead of placing one order per deficit period. Useful when MOQs are large relative to monthly demand. The default **Standard** method is unchanged. See [Choose an Optimization Method (Beta)](/planning-and-execution/replenishment/advanced-planning/advanced-production-plans.md#how-do-i-use-the-optimized-build-method-beta) in the Advanced guide.
{% endhint %}

***

## Reviewing Your Plan

Your plan opens to the **Order Schedule** tab — a time-series grid showing:

* **Buy quantities** — Mo's recommended order amounts per period
* **Ending inventory projections** — Starting Balance + Buys − Projected Sales, period by period. Periods showing zero indicate stockouts where sales exceed available inventory.
* **Coverage metrics** — Days on hand for each SKU across the coverage window
* **Constraint data** — MOQ, min/max levels, and lead time impacts reflected in recommendations

Above the table you'll see two tabs:

| Tab                 | What It Shows                                                            |
| ------------------- | ------------------------------------------------------------------------ |
| **Order Schedule**  | The time-series grid with buy quantities and inventory projections       |
| **Purchase Orders** | All purchase orders Mo has created from this plan, linked directly to it |

From the Order Schedule view, review Mo's suggestions and edit order quantities as needed before generating purchase orders.

***

## Generating Purchase Orders with Mo

Once your order quantities look right, you're ready to turn the plan into purchase orders. There are two ways to do this:

{% tabs %}
{% tab title="Option 1: Ask Mo directly" %}
Open the Mo chat panel and ask Mo to generate orders from your plan. This gives you the most control — you can scope the request before Mo builds anything.

**Example prompts:**

* "Create purchase orders from this plan"
* "Generate POs for all at-risk items in this plan"
* "Create a PO for Supplier X from this plan"

Mo will show you a summary of the orders it plans to create, ask you to confirm, then generate the POs.
{% endtab %}

{% tab title="Option 2: Click the Generate button" %}
Click the green **Generate Purchase Orders** button at the top of your plan. Mo opens automatically and starts generating purchase orders right away — no prompt needed.

Mo will:

* Create **one PO per supplier** based on the items in your plan
* Pull unit costs and lead times from your catalog automatically
* Ask you to choose a supplier for any items that have multiple options

{% hint style="info" %}
This is the fastest path when you want Mo to handle everything and you're ready to generate orders for the full plan.
{% endhint %}
{% endtab %}
{% endtabs %}

### Reviewing Mo's Orders

Once Mo finishes generating, review the purchase orders it created:

* Verify supplier groupings and quantities
* Check expected delivery dates against your lead times
* Confirm unit costs match your current supplier agreements

If anything needs adjusting, ask Mo to make changes directly in the chat — for example: "Change the delivery date on this PO to June 15th" or "Reduce the quantity on SKU-123 by 20%."

***

## Viewing All Purchase Orders for This Plan

After Mo generates your orders, click the **Purchase Orders** tab above the table (beside the Order Schedule tab) to see every purchase order linked to this plan.

From the Purchase Orders tab you can:

* See all POs Mo created, organized by supplier
* Check the status of each order (draft, active, received)
* Navigate directly to any PO for further review or edits
* Confirm that all plan quantities have been converted to orders

{% hint style="success" %}
Purchase orders generated from a plan are automatically linked to it. The Purchase Orders tab always reflects the current state of those orders — so you can track your plan through to fulfillment in one place.
{% endhint %}

***

## Frequently Asked Questions

### Can I change the plan type after creating it?

No. Plan type (Replenishment vs. Allocation) is set at creation. If you need a different type, create a new plan — your existing plan remains accessible for reference.

### Can I have multiple plans at the same time?

Yes. You can maintain as many plans as needed. Your most recent active plan appears at the top of the Planning page; previous plans are listed below for reference and comparison.

### What happens when I rebuild a plan?

Rebuilding regenerates the plan's recommendations using the latest data from the linked forecast, current inventory levels, and any updated constraints. Your manually edited order quantities are not preserved after a rebuild.

### Can I link a plan to a different forecast?

No. The forecast link is set at creation. To use a different forecast, create a new plan. This allows you to run parallel scenario plans — for example, an internal demand plan and a factory-facing plan — side by side.

### What if Mo doesn't create a PO for some SKUs?

Moselle will not generate a PO line item for SKUs without a configured supplier. Assign suppliers to affected SKUs in **Operations > Suppliers** before generating orders. You can also ask Mo: "Are there any SKUs in this plan without a supplier assigned?"

### Can I edit a purchase order after Mo creates it?

Yes. All generated POs start as drafts. You can ask Mo to adjust them in the chat, or go to the **Orders** section to edit quantities, delivery dates, or supplier details before activating.

***

## Related Guides

{% content-ref url="/pages/XujjS3140dWgq4aagxaz" %}
[Manage Your Production Plan](/planning-and-execution/replenishment/core-workflow/production-planning.md)
{% endcontent-ref %}

{% content-ref url="/pages/rWrUXYFkPuQYJLDgxBg2" %}
[Add Your Constraints](/planning-and-execution/replenishment/core-workflow/add-your-constraints.md)
{% endcontent-ref %}

{% content-ref url="/pages/c3H9nIfH0qdJQffJKIWc" %}
[Generate Orders](/planning-and-execution/replenishment/core-workflow/generate-orders.md)
{% endcontent-ref %}

{% content-ref url="/pages/rt03PNU9zAGxsqubrFMs" %}
[Planning with Mo](/planning-and-execution/replenishment/advanced-planning/production-planning-with-mo.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

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

```
GET https://learn.moselle.io/planning-and-execution/replenishment/core-workflow/create-a-production-plan.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.