Sales knows a customer project is coming. Purchasing gets a spreadsheet saying "add 20% to these items next quarter." Someone then has to look up every forecast, do the math, and format an upload file. This guide hands that work to Cue. You upload the spreadsheet and get back a file ready to load through forecast overrides.
⏰ Time: about 10 minutes.
Before you start
Start a new chat on the Cue module.
Save your file as a CSV. Excel files aren't supported for upload yet. In Excel, use File > Save As and pick CSV.
Files can be up to 10 MB.
Your file needs to identify the item and location, the time period, and the change. The change can be a percentage, a quantity to add, or a new forecast number.
Step 1: Prepare your file
There are two ways to build the file. Use whichever fits.
Option A: Use your own spreadsheet
Best when the change varies by item, location, or month, such as a list from Sales. Column names don’t have to match Recurrency’s. You’ll describe them in the prompt. A simple file looks like this:
Item code | Location | Month | Change |
100245 | Main | 2026-12 | +20% |
100245 | North | 2026-12 | +20% |
208811 | Main | 2027-01 | +15% |
Option B: Export a list from Planning
Best when the same change applies to a group of items, such as everything from one supplier or one product line.
In Planning, filter to the items you want to change.
Download the table. It downloads as an Excel file.
Open it in Excel, then use File > Save As and pick CSV.
The export has more columns than Cue needs. That’s fine. Cue only uses item code and location. If the file is close to 10 MB, delete the extra columns before saving.
Step 2: Upload the file and ask
Attach the CSV in the chat, then copy the prompt that matches your file.
If you used Option A (your own spreadsheet):
I've uploaded a CSV of expected demand changes. Each row has an item code, a location, a month, and a percentage change.
For each row, look up the current Recurrency forecast for that item-location and month, apply the change, and return a CSV in the forecast override upload format.
Before the file, summarize how many rows you applied and list any item-locations from my file that don't exist in the Recurrency forecast.
If your file is set up differently, change the first paragraph:
Quantities instead of percentages: "Each row has an item code, a location, a month, and a quantity to add to the forecast."
New forecast numbers: "Each row has an item code, a location, a month, and the new forecast quantity."
Customer or project level: "Each row is a customer, item code, location, month, and expected quantity. Add up the quantities by item-location and month before applying them."
If you used Option B (Planning export):
I've uploaded a CSV of item-locations exported from Planning. Use the item code and location columns.
For [month 1] and [month 2], increase the current Recurrency forecast by X% for every item-location in the file, and return a CSV in the forecast override upload format.
Before the file, summarize how many rows you applied and list any item-locations from my file that don't exist in the Recurrency forecast.
Replace the months and percentage with your own. To add a fixed quantity instead, change the second paragraph to: “For [month 1] and [month 2], add [quantity] units to the current Recurrency forecast for every item-location in the file.”
Step 3: Review the file
Read the summary before you download.
Check that the number of rows applied matches your file.
Look at any item-locations Cue couldn't find in the Recurrency forecast. Fix or remove those rows in your source file and run it again.
Spot-check a few rows. If one looks off, ask: "How did you calculate the override for [item code] at [location] for [month]?"
Step 4: Upload the overrides
Download the CSV and upload it through forecast overrides in the Forecasting page. No reformatting needed.
Tips
Keep one change per file. A clean file for one project is easier to review than a mix of everything.
Very large files take longer. If a request times out, split the file and run it in parts.
What happens next
Cue never changes your forecast on its own. The override takes effect only when you upload the file.