Skip to main content

​
What this page is for

Sometimes you need the plan in a spreadsheet - to share it, to work on it offline, or to load a lot of numbers at once. Spherecast has two tools: Download Demand to export, and Upload Forecast to import. Both work in the background and notify you when they finish.

​
Download Demand

Choose forecast or targets, then set the options.

​
For a forecast download

The output is an .xlsx file. If you pick multiple markets without aggregation, Spherecast asks whether to turn aggregation on so the file stays readable.

​
Upload Forecast

Choose forecast or target, then set where the numbers land.

​
File limits

  • Formats: CSV, XLS, XLSX
  • Maximum size: 50 MB

​
Errors you might see

Spherecast flags problems instead of loading bad data:
  • Inactive, missing, or duplicate SKUs
  • Missing or unknown channels
  • Invalid market–channel combinations

​
Upload actual sales

Use Actual sales to load sales history for a channel whose sales no integration delivers, such as a marketplace you only get reports from. The file has the same layout as a forecast upload: SKU, Channel and one units column per month. The forecast options (warehouse allocations, past periods, adjustments) do not apply and are hidden. Rules:
  • Every row needs a Channel, and a SKU can appear only once per channel.
  • Quantities are read in each product’s demand planning unit, the unit the demand plan shows it in. A downloaded file names it per SKU in the Demand plan unit column. A file in another unit is booked at the wrong scale, and the upload cannot tell.
  • Months up to the current one are accepted. A value in a future month is rejected; leave those columns empty.
  • A negative value or a cell that holds text is rejected. The upload names the cells and loads nothing.
  • Each month is spread evenly over its days in whole units. The current month is read as sales so far and spread over the days up to yesterday, so upload it again to keep it current.
  • Revenue is calculated from the product’s price.
  • A SKU and channel that already receive sales from an integration cannot be uploaded. The upload lists them and loads nothing.
  • Uploading a month again replaces what was uploaded before for that SKU, channel and month. An empty or zero cell clears it.
  • Actual sales are not scenario-specific, so the option is unavailable while a scenario is active.
  • Forecasts pick the new history up with the next forecast run.

​
Target upload rules

  • Target uploads are blocked if product-level (SKU) targets already exist or a scenario is active.
  • If your uploaded targets would overwrite existing goals, an override confirmation appears first.

​
Step by step: upload a Consensus forecast

  1. Open Upload Forecast and choose forecast.
  2. Set Apply to = Consensus.
  3. Decide whether to upload past periods and whether to create adjustments.
  4. Leave only apply to new items on unless you mean to overwrite existing items.
  5. Check each channel’s warehouse allocations sum to 100%.
  6. Attach your file (CSV/XLS/XLSX, under 50 MB) and submit.
  7. Fix any flagged SKU or channel errors and resubmit.
  8. Wait for the completion notification.

​
Example

A planner exports Consensus for the Midwest and West markets, monthly, in units, aggregated by channel - one clean .xlsx to share with sales. Later, they receive a revised file, open Upload Forecast, set Apply to = Consensus, confirm each channel’s warehouse splits total 100%, and submit a 6 MB XLSX. Two duplicate SKUs are flagged; they remove the duplicates and resubmit, and a notification confirms the load.
Tip: Keep only apply to new items on unless you truly intend to replace numbers for existing products - it’s the safeguard that stops a bulk upload from wiping out work already in the plan. See Targets for how target uploads interact with top-down goals.