Exporting the forecast

The Export button sits in the bar underneath the Forecast table, next to the page controls. It downloads what the table shows — your visible columns, in your column order, with the numbers formatted the way you see them on screen. You can export the view you’re looking at, or combine it with other saved views in one file.

Exporting the current view

Click Export. A dialog opens with two choices:

Rows to export — Current page (the rows in front of you) or All pages (everything the view’s filters match). Some places that open this dialog also offer Selected rows.
Format — Excel Spreadsheet (.xlsx) or CSV File (.csv).

Confirm with Export XLSX / Export CSV. The file downloads when it’s ready; large views take a moment while the remaining pages are fetched.

Which columns come out

The export follows the view, not a fixed template: whatever columns are visible, in the order you arranged them, is what the file contains. Three things never export:

The selection checkbox and the row-actions column.
The inventory burndown chart.
The Manufacturing (Assemblified) planning columns — those are calculated for the rows on screen only, so there’s nothing to write for rows the export walks past.

Supply and Sales Performance views export their period columns with the same headings the table shows.

Combining several views

If you have more than one saved view, the dialog also shows Combine with other views. Your current view sits at the top, ticked and locked (it’s always included, and is marked “(current)” — or “(current, edited)” if you have unsaved changes to it). Underneath, every other saved view is listed, starred ones first. Tick as many as you want.

Separate sheets vs. combined rows

With more than one view selected, a Layout choice appears:

Separate sheets — one per view. Each view keeps its own table, exactly as it would export on its own.

In XLSX you get one workbook with one worksheet per view, named after the view. Long or duplicate view names are shortened and numbered so every tab stays unique.
In CSV you get one file, with each view as its own section: a title row with the view name, that view’s header row, its data rows, then a blank line before the next view.

Combined rows, sorted by SKU. One flat table for all the selected views, with an extra View column in front telling you which view each row came from.

A SKU that appears in three of the selected views produces three consecutive rows, in the order you picked the views.
The columns are the union of the selected views’ visible columns — the current view’s columns first, then any column a later view adds.
A cell is left blank when that row’s own view doesn’t show that column. Blank means “not part of this view”, not “zero”.
Rows are grouped by SKU and sorted naturally ascending; rows without a SKU follow at the end, sorted by product and variant title.

File names and progress

A single-view export is named after the view and its location scope, with a timestamp — for example bestsellers-all-locations-2026-09-14-08-30-00.xlsx. A combined export is named for how many views went into it: forecast-multi-3-views-2026-09-14-08-30-00.xlsx.

While a combined export runs, the dialog shows which view it’s on — Fetching “Bestsellers” (2/4)… — and stays open until it finishes. Views are fetched one at a time, so a four-view export takes roughly four times as long as one view.

If any view fails to load, the whole export stops and the dialog tells you which view it was; nothing is downloaded. That’s deliberate — a half-complete file is worse than no file. Try again, or untick the view that failed. A view that simply matches no rows is not a failure: it contributes its headers and no data rows.