Downloading, Editing, and Uploading a Demand Plan

This article will describe the steps to edit a demand plan as a spreadsheet (as opposed to editing directly in DemandCaster) and re-uploading to DemandCaster as a user defined forecast.

Please note that pricing changes can only be made at the item level. This is because pricing in most companies tends to be customer specific. If DemandCaster exploded pricing down to the item level in the same manner as demand plan edits at upper levels, slight shifts from one item to another will skew results.

Select Level to View and Edit

  1. Use drop down to select level to view.
  2. In this example, we will be reviewing and editing at the item level.

Select the Report to Download

  1. Click Excel to open the report pop-up
  2. Select Rolling 12 Month Context Demand Plan report to show the demand plan by context (i.e. customer). A description of each of the other reports is described in the What reports do the different excel icons in demand and supply planning generate.
  3. The report will run and will download when ready. The time required to generate depends on the number of customers and items being planned.

Please note, the the report may also be generated in the Custom Reports section as long as it includes the level related data that the upload will be performed at. At minimum you will need the context level where the demand plan is being edited as well as the level above the level. In addition, you will require the demand plan values in months. Price is optional.


  1. Open the excel document.
  2. The demand plan start on column G. Proceed to edit the demand plan by item - context. You may also edit the selling price following the unit columns.
  3. Removing values (making blank) from a given unit or price cell will maintain the previously edited or statistical demand plan or price.
  4. Removing a row will not upload and update the demand plan. Please remove all rows that you wish to keep as a statistical forecast otherwise if they are uploaded the item will become a user defined forecast and will no longer change unless the user edits the forecast or makes the forecast statistical again.
  5. Changing a cell to 0 will zero out the demand plan or price.
  6. The download defaults to a 12 month or 52 week rolling demand plan. Add additional columns at the end following the same format to include additional demand plan periods beyond the rolling 12 month plan.

Prepare the report for upload (item level demand plan)

  1. Delete columns B and C and then once removed, proceed to delete what are now columns C and D leaving the customer code, item code, and demand plan units by month (and price if also uploading)
  2. Only upload the context item demand plans that you would like to change.
  3. If you wish to not change a period, leave the period blank in the file. Making the value 0 in a period will change the demand plan or price to 0.
  4. Cell A2 can be named whatever "customer" name is assigned in the field.
  5. Cell A1 will determine the level the forecast will be uploaded which in the example below is the item.
  6. The customer code and item code followed by the unit plan by weeks or months and then unit price by weeks or months will follow.
    1. The unit upload date header must be the date period followed by "-unit" i.e. 01/28/2018-unit. The date format will follow your companies date format (U.S. or European)
    2. The price upload date header must be the date period followed by "-price" i.e. 01/28/2018-price. The date format will follow your companies date format (U.S. or European)
  7. Pricing may be uploaded above the item level as an average price.
  8. Whatever your planning bucket is set at is the bucket you upload. Upload months, if your demand planning process is in months, weeks if your demand planning process is weeks. If in weeks make sure it follows your week start day i.e. Sunday or Monday.
  9. Make sure there are no empty columns being saved in your excel. At times excel may add invisible columns and rows that are saved in the text file. These will cause errors in the upload. If you run into this issue, we recommend moving the data to a clean spreadsheet prior to saving as a text file particularly when using a downloaded files as the basis of your data.
  10. You may also enter new customer/item demand plans that do not currently exist. These will be automatically created as part of the upload.

The upload file at the item level should look like the image below.

Save the file as a tab delimited text file with the same name as the file - userdefinedsopforecast.txt

Zip the converted file

Upload the zipped file

Follow the upload steps as described in the Manually Uploading Data article and then check for any errors per the article Reviewing Upload Files for Errors

Uploading to Customer Level

When uploading to the customer level, there is a minor change.

When uploading to customer level, cell A-1 will have to be filled with “customer” (regardless if the customer level is renamed).

The the first column is the customer code, and the other columns contain the forecast of the customer. There is no lower level in this case.

Levels above the customer are named the level name in both cell A-1 and A-2.

When uploading to levels above the item level, the pricing should be removed from the upload file since pricing is only applied at the item level.

Follow steps above to save and upload.

Please remember that the uploaded file must be a zipped tab delimited text file named userdefinedsopforecast.txt

Uploading to a Level Between Customers and Items

As stated in the Upload Planning Hierarchy article, the hierarchy is a top down build. As a result, the upload above the item level follows a top down approach as well.

In the example above, we are loading a demand plan to a level named "style" to a customer. In this case, the style is in column A and Customer is in column B.. Cell A-1 will call out the level in which the forecast is being applied - which, in this example, is Style.

Please remember that the uploaded file must be a zipped tab delimited text file named userdefinedsopforecast.txt

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request