The question this page answers
What will this event do to my forecast, how much, on which variants and channels, from when, and does it go live now or wait?
What you see
- 1Events, at the top, returns to the list.
- 2Adjustment, Custom values, Percentage or Launch.
One page, one scroll: the fields and, beside them, the variants free for the window they set. Events, at the top, returns to the list. The head is the event's name as you type it, New event until you do, with the badge Suggested by Tightly where a suggestion opened the page.
The fields: Name, Description, Runs as a date range bounded two years ahead and open behind today, Baseline carrying the mark Do not learn from this window (its hover reads The baseline treats these days as unrepresentative.), the channels it runs on, and Adjustment as Custom values, Percentage or Launch. Percentage carries a stepper from one percent and Increase | Decrease. A zero percent event is not offered, because it would move nothing.
Launch plans a partnership drop apart from seasonal demand, in units. No percentage, no mark; Baseline states the fact. Its grid, Launch units, opens under the picker: one row for each product you picked, the window's Mondays across. Type any cell, or type one Total units and press Spread, which splits it across the products and front loads each share, so the grid totals what you typed. A cleared cell is blank; a typed zero is a zero. A product's weekly total can also be allocated across its variants and channels; the allocations must equal the total before you save.
The baseline never learns from a launch. A launch week starts on a Monday, and no Monday falls in these days. Pick the styles this launch sells first.
The picker fills once dates and channels are set: Product, Variant, SKU and Supplier, more columns from the Columns menu, filter pills, and a search for Product, variant or SKU. Its count line says how many variants are free for these dates on these channels, and only those are listed. Pick by row, or Pick all {n} that match.
A suggestion fills the name, dates, percentage and relevant variants. Its explanation distinguishes measured history from an industry range. A known one-off opened from the forecast grid fills the dates, channels and products, with the baseline exclusion ticked; give the event a name before saving.
What to do
- Name the event, set Runs as a date range, and choose its sales channels.
- Choose Adjustment: Custom values, Percentage or Launch, and set its values.
- For a past promotion, tick Do not learn from this window; without the mark a past window is refused.
- Pick variants from the picker, or press Pick all {n} that match.
- On a launch, type each product's units per week in the grid, or type one Total units and press Spread.
- Or press Import SKUs to select products from a CSV instead (one SKU column, up to 1,000 rows, under 256 KB); fix any unknown, repeated or ambiguous SKU before applying.
- Press Publish now to move the forecast from the start date, or Save as unpublished to save without moving it.
- Press Cancel to return to Events with nothing written.
Each button says what it does beside it: Publish now · The forecast moves from {date}., or Save as unpublished · Nothing moves until you publish. Pressing either before the form is complete shows the reason in ink: Name is required, Time period is required, Sales channel is required, An adjustment is required, or At least one variant is required. Ticking Do not learn from this window records an exclusion for later baseline training; it does not rewrite or recalculate recorded historical forecasts. Import SKUs replaces the current product selection without saving the event, and imports neither sales history nor several events at once. An event already covering the same products, channels and dates is refused rather than duplicated; if saving cannot be confirmed, check Events before trying again.
The result renders where the form was: Runs, the channels, Launch units on a launch, Baseline on a marked window, Created, what it still asks of you, and the door Open the event. A refused save shows its reason beside the buttons; correct the dates, product selection or launch quantities and try again.
When it is empty or failed
Set the dates and channels first. Every variant is already in an event over these dates. The variants could not be read. Your sales channels could not be read. No sales channels on file. Your filters could not be read. Tightly's suggestion could not be read. The event was created; its record could not be read.
A suggestion that is not found, dismissed or expired opens an empty form with no error.