> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/production/smart-production-plan.md).
# Smart Production Plan
**Smart Plan Production** in Supply’d is a powerful tool that helps you streamline your production planning based on real-time demand and product availability. By using Smart Plan, you can automatically generate production and supply plans that reflect customer orders, stock levels, and delivery schedules. It reduces manual entry, improves accuracy, and ensures you produce just the right amount - helping minimise waste and overproduction. This feature is especially useful for businesses managing multiple suppliers and recurring orders, giving you full visibility and control over your production needs with minimal effort.
* [#setting-up-smart-plan-production](#setting-up-smart-plan-production "mention")
* [#importing-smart-plan-data-into-production-runs](#importing-smart-plan-data-into-production-runs "mention")
***
## Setting Up Smart Plan Production
{% stepper %}
{% step %}
#### Go to the Production Page
Select **Production** from the main menu.
The **Production** page will open, showing a list of all scheduled and in-progress **Production Batches**.
***
{% endstep %}
{% step %}
#### Select Smart Plan
Click on the 3 dots in the top right corner and select **Smart Plan**.
The **Smart Plan Production** form will open.
{% hint style="success" %}
To open or close the sections on this form, click the little arrows to the right of the titles (as circled in red above).
{% endhint %}
Complete the sections as per the guidelines below:
***
{% endstep %}
{% step %}
#### Plan Details
**Production Date Range**
Select the date range you want to export using the calendar that appears when you click the field.
Click to confirm and save the selected date range.
{% hint style="warning" %}
Ensure that **Smart Planning Date Range Interpretation** is configured in the [Production Settings](/supplyd-erp/settings/production-settings.md#production-defaults) section of [Production Settings](/supplyd-erp/settings/production-settings.md) so the selected dates represent the intended timeframe (ie. **Required Date** or **Scheduled Date**).
{% endhint %}
**Location**
Choose the applicable location.
**Method**
Select the method you would like to use for the smart plan.
* **Made to Order:** Create production runs for each of your current Sales Orders, including Standing Sales Orders, during the date range.
* **Net Requirements:** Deduct your current Sales Orders and expiry from inventory throughout the date range, ensuring that stock stays above Min Hold.
* **Suggested:** Utilise your forecast rate of sale, stock expiry, and Min Stock Hold to keep you always in stock.
* **Default For Products:** Use the default set in **Smart Planning Date Range Interpretation** in the [Production Settings](/supplyd-erp/settings/production-settings.md#production-defaults) section of your [Production Settings](/supplyd-erp/settings/production-settings.md).
When **Made to Order** is selected, an additional field - **Ignore Sub-Recipe Stock Levels** - will show.
**Ignore Sub-Recipe Stock Levels**
Choose whether or not to ignore the current stock levels of sub-recipes and schedule production runs for those, or to only schedule runs for sub-recipes that have insufficient stock.
{% hint style="info" %}
This field will only show when "**Made to Order**" is selected in the **Method** field.
{% endhint %}
{% hint style="warning" %}
For **Net Requirements** and **Suggested**, it is best to set minimum stock levels under [Product Settings](/supplyd-erp/settings/product-settings.md) (global level), but they can also be overridden at the individual product inventory level ( [Managing Inventory](/supplyd-erp/inventory/managing-inventory.md#minimum-stock-hold)) if needed.
{% endhint %}
{% hint style="warning" %}
**Made To Order** and **Net Requirements** planning methods are based on delivery dates, as this determines when the stock is actually required. In contrast, the **Suggested** method works from forecasted sales rather than existing sales orders. Because of this, maintaining accurate delivery dates on orders is important to ensure **Smart Plan** can correctly calculate demand timing and generate more accurate production and purchasing recommendations.
{% endhint %}
{% hint style="success" %}
For forecasting to work accurately, orders need to be consistently coming through Supply’d for a period of time - ideally at least two weeks.
{% endhint %}
***
{% endstep %}
{% step %}
#### Filtering
**Categories**
Select the products you would like to generate production runs for. Leave it blank to include all categories.
***
{% endstep %}
{% step %}
#### Advanced
**Include Reasoning Data?**
Select whether or not to include reasoning data in the smart plan export to help you understand the generated production runs.
{% hint style="info" %}
**Reasoning Data** explains how each recommended production run was calculated, giving you insight into the factors Supply’d considered when generating the plan. This can include things like current stock levels, customer demand, and delivery schedules. Having this detail makes the plan more transparent, helps you understand why certain runs are suggested, and allows for easier troubleshooting or adjustments if needed.
{% endhint %}
***
{% endstep %}
{% step %}
#### Create
Click to set up your plan.
{% endstep %}
{% endstepper %}
***
### Smart Plan Data
The **Smart Plan** data will be downloaded to your computer in a CSV file giving you a detailed breakdown of everything needed for upcoming production runs. It includes things like:
* Products to be made
* Quantities needed
* Planned production dates
It’s a handy way to get a clear, organised view of what needs to happen, so you can plan ahead, order supplies, and keep production running smoothly.
If you selected "**Yes**" in the **Include Reasoning Data** field, you'll see an extra column, showing the reasoning behind the production data.
Review all the data and make any changes necessary, making sure any changed versions are saved as .csv files.
{% hint style="warning" %}
Be careful when changing numbers, as **Yield** and **Batch Quantity** are interconnected and must remain aligned to ensure the production calculations remain valid.
{% endhint %}
***
## **Importing Smart Plan Data into Production Runs**
This feature helps eliminate manual entry and ensures your production runs are aligned with your demand forecast.
{% stepper %}
{% step %}
#### Go to the Production Page
Select **Production** from the main menu.
***
{% endstep %}
{% step %}
#### Select Import
Click on the 3 dots in the top right corner and select **Import**.
***
{% endstep %}
{% step %}
#### Choose the File
Select the relevant **Smart Plan** .csv file that you previously downloaded and reviewed.
***
{% endstep %}
{% step %}
#### Populate Production Run
The system will populate your production run with the products, quantities, and other details from your **Smart Plan**.
***
{% endstep %}
{% step %}
#### Review Data
Review the auto-filled data and make any adjustments if required.
{% endstep %}
{% endstepper %}
---
# 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://help.supplyd.co/supplyd-erp/production/smart-production-plan.md?ask=&goal=
```
`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.