> 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/analytics/reporting/mo-reports/mo-standard-reports/po-allocation-report.md).

# PO Allocation Report

{% hint style="info" %}
**Quick Answer:** When sales targets are missed, use Mo's PO Allocation Report to evaluate every open purchase order against current sell-through rate and weeks of supply per SKU. Mo surfaces a ranked recommendation — Proceed, Delay, or Cancel — for each open PO so you can act before cancellation windows close.
{% endhint %}

## What is the PO Allocation Report?

**The PO Allocation Report** is a post-sales-miss analysis that cross-references your open purchase orders with current sell-through rate and weeks of supply per SKU. When demand falls short of target, not every open PO should move forward — this report gives you the data to decide which ones should.

Mo pulls from your active POs, current inventory levels, and sales actuals to surface a reprioritization recommendation for each open order, ranked by urgency.

### When to Use This Report

* A monthly sales miss has been confirmed and open POs have not yet been reviewed
* You need to identify cancellation or delay candidates before vendor deadlines close
* You want to avoid compounding over-inventory into already slow-moving SKUs
* Your end-of-month PO review requires a structured, data-backed prioritization

## Before You Start

Make sure the following are in place before running this report:

| Requirement                                    | Why It Matters                                                          |
| ---------------------------------------------- | ----------------------------------------------------------------------- |
| Active POs are loaded in Moselle               | Mo needs visibility into open orders to evaluate each one               |
| Sales actuals are synced and up to date        | Required to calculate sell-through rate and identify the sales miss     |
| Current inventory levels are accurate          | Mo uses on-hand stock to calculate weeks of supply per SKU              |
| Monthly sales targets are set in your forecast | Mo compares actuals against targets to determine the extent of the miss |

## The Report Prompt

Copy and send this prompt to Mo in full. It generates the complete PO Allocation Report — sell-through and weeks-of-supply analysis, post-sales-miss reprioritization logic, and PO recommendations — in one response.

{% hint style="warning" %}
Replace `[current month or relevant period]` with your specific date range, and `[X weeks]` with your target weeks of supply threshold. If you are unsure what threshold to use, ask Mo first: `What weeks of supply threshold should I use given my current sell-through rate and lead times?`
{% endhint %}

```
Generate my PO Allocation Report using post-sales-miss logic.

I have missed my sales targets and need Mo to evaluate every open PO in light of that miss — using sell-through rate and weeks of supply per SKU to determine which orders are still justified and which should be delayed or cancelled.

Include the following in one report:

1. Sales Miss Summary
   - Which SKUs have missed their monthly sales targets, and by how many units?
   - What is the sell-through rate per SKU for [current month or relevant period]?
   - Rank SKUs from highest to lowest sales miss so I can see where reprioritization is most urgent

2. Weeks of Supply per SKU
   - For each SKU with an open PO, what is the current weeks of supply based on on-hand inventory and current sales velocity?
   - Flag any SKUs where weeks of supply exceeds [X weeks] — given the sales miss, these are the strongest candidates for PO cancellation or delay

3. Open PO Reprioritization
   - List all active POs with their associated SKUs, quantities, and expected arrival dates
   - For each open PO, apply post-sales-miss logic to provide a recommendation: Proceed, Delay, or Cancel
   - Base each recommendation on: (1) how far the SKU missed its sales target, (2) current sell-through rate, and (3) resulting weeks of supply if the PO were to land as scheduled
   - Include a clear rationale for each recommendation tied directly to the sales miss data

4. Summary
   - How many POs are recommended to proceed, delay, or cancel?
   - What is the estimated inventory and cost impact of acting on these recommendations?
   - Summarize the top 3 actions I should take before my next PO deadline
```

## How to Read the Recommendations

| Recommendation | What It Means                                                                               | Typical Signal                                                              |
| -------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| **Proceed**    | The PO is still justified — demand supports receiving this inventory                        | Sell-through on track; WOS will remain within healthy range after receipt   |
| **Delay**      | The PO should be pushed out — receiving now risks excess stock given the miss               | Moderate sales miss; WOS would extend above threshold if landed on schedule |
| **Cancel**     | The PO should be cancelled — demand has fallen far enough that this inventory is not needed | Significant sales miss; WOS is already above threshold without this order   |

{% hint style="info" %}
A typical weeks of supply threshold is **8–12 weeks**, but this varies by business. Brands with longer lead times or seasonal inventory often carry more weeks of cover. Adjust your threshold to match your operational reality.
{% endhint %}

## Recommended Check-In Cadence

Run this report whenever a sales miss occurs or as part of your end-of-month PO review.

| Timing                               | What to Focus On                                                                               |
| ------------------------------------ | ---------------------------------------------------------------------------------------------- |
| **After a sales miss is identified** | Run immediately to assess which open POs are still justified before cancellation windows close |
| **End-of-month PO review**           | Use as a standard checkpoint to validate all active orders against current sell-through        |
| **Before placing new POs**           | Cross-reference to avoid compounding over-inventory into already slow-moving SKUs              |

## Save and Re-Run This Report

Once Mo has generated your report, consolidate it into a saved prompt so you can re-run it without retyping.

**Time Required:** 2 minutes **Difficulty:** Beginner

{% stepper %}
{% step %}

### Ask Mo to Consolidate the Report

At the end of your report session, send this to Mo:

> "Can you take everything you just ran — the sales miss summary, weeks-of-supply analysis, open PO review, and recommendations — and consolidate it into a single reusable prompt I can save and run whenever I need it?"

Mo will return one clean prompt that captures the full report logic.
{% endstep %}

{% step %}

### Save It as a Favourite Prompt

Once Mo returns the consolidated prompt:

1. Hover over Mo's response to reveal the action icons
2. Click the **star icon (☆)**
3. A confirmation toast will appear: **"Prompt saved to favourites"**

Give it a clear name — for example: **PO Allocation Report** — so it is easy to find.
{% endstep %}

{% step %}

### Re-Run It Anytime

To run your report each time you need it:

1. Navigate to the **Mo page** from the left sidebar
2. Scroll to **Favourite Prompts** at the bottom of the page
3. Click **PO Allocation Report**
4. Update `[current month or relevant period]` and your weeks of supply threshold as needed
5. Send — Mo will generate the full report instantly

{% hint style="success" %}
You only need to set this up once. After that, re-running a full PO allocation analysis takes under a minute.
{% endhint %}
{% endstep %}
{% endstepper %}

## Frequently Asked Questions

<details>

<summary>How often should I run the PO Allocation Report?</summary>

Run it whenever a sales miss is confirmed — typically at the end of a month or after a major sales period. Using it as a standard end-of-month checkpoint ensures you catch over-inventory risks before cancellation windows close.

</details>

<details>

<summary>What weeks of supply threshold should I use?</summary>

A common starting range is 8–12 weeks. Brands with longer overseas lead times often carry more cover; brands with shorter domestic lead times can operate leaner. If you are unsure, ask Mo: "What weeks of supply threshold makes sense given my current sell-through rate and lead times?"

</details>

<details>

<summary>Can I run this report for a specific product category or vendor?</summary>

Yes. Add scope to your prompt — for example, "limit this to our outerwear category" or "evaluate only POs from Supplier A" — and Mo will filter the analysis accordingly.

</details>

<details>

<summary>What if I disagree with Mo's recommendation for a specific PO?</summary>

Mo's recommendations are based on the data in Moselle. You may have context Mo does not — an upcoming promotion, a retailer commitment, or a supply constraint. Use the recommendations as a starting point and override where your business judgment differs. You can ask Mo to re-evaluate a specific PO with updated assumptions.

</details>

<details>

<summary>Does Mo factor in open-to-buy budgets when making recommendations?</summary>

The base prompt focuses on sell-through rate and weeks of supply. To layer in budget constraints, add a line to the prompt such as "my remaining open-to-buy for the quarter is \[amount]" and Mo will factor that into the prioritization.

</details>

## Related Guides

{% content-ref url="/pages/ZiMAO4xUpdTQI2yoZWu5" %}
[Weeks of Supply (WOS) Report](/analytics/reporting/mo-reports/mo-standard-reports/wos-report.md)
{% endcontent-ref %}

{% content-ref url="/pages/aYMGZMjVZa0NMZNaCeKo" %}
[Forecast vs Actuals](/analytics/reporting/mo-reports/mo-standard-reports/forecast-vs-actuals.md)
{% endcontent-ref %}

{% content-ref url="/pages/UJBeJZb1fZD3mCfSbojq" %}
[Review your Order](/planning-and-execution/orders/review-your-order.md)
{% endcontent-ref %}

{% content-ref url="/pages/DAsnRIRTbbjM6bgR0RLM" %}
[Save Your Favourite Prompts](/mo/tips/save-favourite-prompts.md)
{% endcontent-ref %}

{% content-ref url="/pages/8QlNv4eTnXy8INtmWeyS" %}
[Create a Replenishment or Allocation Plan](/planning-and-execution/replenishment/core-workflow/create-a-production-plan.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:

```
GET https://learn.moselle.io/analytics/reporting/mo-reports/mo-standard-reports/po-allocation-report.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.