Import and Export Forecast
Learn how to export your forecast data, make bulk modifications externally, and re-upload to update your projections in Moselle.
Moselle allows you to export your forecast data, make modifications externally, and re-upload it to update your projections. This is useful for bulk editing forecasts outside of the application or integrating data from external planning tools.
Exporting a Forecast
To export your forecast:
Navigate to the Forecasting tab and select your scenario plan
Click on the Gear Icon next to the Done Planning button
Select Export and Download
A CSV file will be sent to your email
The exported file contains all items across your channels with projection data for each month in your forecast timeframe.

Understanding the Export Template
The exported CSV file contains the following columns:
channelId
The unique identifier for the sales channel
itemId
The unique identifier for the product/item
scenarioPlanId
The unique identifier for the forecast scenario
Date columns
Monthly projection values (e.g., 2024-01, 2024-02)
Importing a Forecast
To upload your modified forecast:
Navigate to the Forecasting tab and select your scenario plan
Click on the Gear Icon next to the Done Planning button
Select Upload & Replace
Drag and drop your file or click to browse
Click Upload to process the file

You will receive a notification once your forecast upload has been processed, confirming whether it was successful or if there were any errors.
File Format Requirements
Supported File Types
CSV (.csv)
Excel (.xlsx)
Required Columns
The following columns are required and must not be removed from the file:
channelId
Yes
Must match an existing channel in your account
itemId
Yes
Must match an existing item in your catalog
scenarioPlanId
Yes
Must match the scenario plan you are uploading to
Removing any of the required columns (channelId, itemId, or scenarioPlanId) will cause the import to fail.
Date Column Formats
Date columns represent the monthly projection periods. The following date formats are supported:
YYYY-MM
2024-01
YYYY-M
2024-1
MM-YYYY
01-2024
MM/D/YYYY
01/1/2024
M/D/YYYY
1/1/2024
YYYY-MM-DD
2024-01-01
All dates are processed as the beginning of the month regardless of the day specified. For example, 2024-01-15 will be treated as 2024-01-01.
Adding or Removing Date Columns
You can modify the date columns in your template:
Add new months by adding columns with properly formatted date headers
Remove months by deleting the corresponding date columns
Dates must use one of the supported formats listed above
Modifying Rows
Removing Rows
You can delete any number of rows from the template to limit your upload to specific item and channel combinations. This is useful when you only want to update projections for a subset of your catalog.
Rows that are removed from the upload file will retain their existing projections in Moselle. Only rows included in the upload will be updated.
Empty Rows
Empty rows (where all values are blank) are automatically ignored during processing.
Skipping Specific Items
If a row is missing both itemId and channelId and scenarioPlanId, that row will be skipped during processing.
Projection Values
Numeric Format
Projection values should be numeric
Commas in numbers are automatically removed (e.g.,
1,000becomes1000)Values are stored with decimal precision
Empty Values
If a date column cell is left blank for a row, no projection will be created or updated for that item/channel/month combination.
Validation Rules
The import process validates the following:
Channel exists
Rows with invalid channelId values are skipped
Item exists
Items must exist in your catalog
Scenario plan exists
Must be an active (non-archived) scenario plan
Scenario plan ownership
Must belong to your company
When exporting and uploading a forecast, you must use the template from the same scenario plan you intend to upload to. Each exported forecast contains specific scenario IDs tied to that forecast.
Best Practices
Always start with an export - Use the exported file as your template to ensure all IDs are correct
Keep required columns intact - Never remove
channelId,itemId, orscenarioPlanIdUse consistent date formats - Stick to one date format throughout your file
Validate before uploading - Check that your file opens correctly and data appears as expected
Upload to the correct scenario - Ensure you're uploading to the same scenario plan you exported from
Troubleshooting
Import fails immediately
Verify all required columns are present
Some rows not imported
Check that channelId and itemId match existing records
Date columns not recognized
Ensure date format matches one of the supported formats
Notification shows error
Review the file format and try re-exporting a fresh template
Exporting with Financials (Amount Mode)
For advanced financial planning, you can export a detailed financial breakdown of your forecast. This report is generated when you export while viewing your forecast in Amount mode.
How to Generate
Navigate to your Scenario Plan.
Locate the toggle in the header and switch from Quantity to Amount.
Click the Gear Icon and select Export and Download.
Report Structure
The CSV file is organized into three distinct sections, repeating the date columns for each financial metric:
ASP (Average Selling Price)
Projected revenue based on historical average selling price.
Calculated from your historical sales data (Analytics::AverageMonthlyItemPrice).
MSRP (Retail Value)
Projected revenue based on the item's current list price.
Pulls directly from the Unit Price field in your item catalog.
COGS (Cost of Goods Sold)
Projected inventory cost.
Pulls directly from the Unit Cost field in your item catalog.
Column Layout
The export follows this sequence:
Item Details: Channel, SKU, Name
ASP Section: Monthly columns showing
Forecast Units * ASPSeparator: Blank column
MSRP Section: Monthly columns showing
Forecast Units * Unit PriceSeparator: Blank column
COGS Section: Monthly columns showing
Forecast Units * Unit Cost
Currency Note: ASP values are automatically converted to your company's operating currency if the sales channel uses a different currency.
Last updated