The question this page answers

Which windows has this tenant declared, when does each open and close, and what is each measured against?

What you see

Selling periods with six declared windows, marked 1 to 3.

1. 1The figure row, Declared, Running, Upcoming and Finished.
2. 2Measured against, the declared predecessor a period is compared to.
3. 3Set up selling periods, which offers history analysis or declaring dates.

Selling periods is where you declare a window, a season or a drop, from its first to its last selling day inclusive. Forecasts, and on Tightly Pro commitments, stand on these windows. It opens on every plan. The head's figure row counts what is declared and how many are running, upcoming and finished.

The toolbar's More carries Season membership, the engine's review of what belongs in each declared window, opened in place, and Set up selling periods, which offers two routes: analyse imported sales, or declare dates yourself.

The table lists periods newest first, with dates, selling days, predecessor, product count and state: Running, Upcoming or Finished. Measured against identifies the predecessor you selected. A dash means no value has been recorded; hover or focus it for the reason.

Choosing Declare dates, or pressing an existing row, opens a drawer titled Declare a Drop or Declare a Season, seeded from the row where there is one. Its fields are Name, Called a (Drop or Season), Opens and closes, and Measured against, whose options are the earlier periods of that kind and This is our first Drop (or Season). Hints under the fields give the selling days, whether demand is shaped by day or by week, and what the predecessor is compared against; unanswered, the comparison falls back to the calendar. A window that has already finished carries What was in it, listing what sold inside it so a person can take a product back out before it is recorded.

Set dates for one product or SKU

No commitment is needed. Open a product from Products → Catalogue, then Product information and edit its Selling window opens and Selling window closes dates. For an individual SKU, open its variant and Edit attributes to set the same fields. Historical dates are supported; leave the closing date blank for a product still selling. These direct dates do not create a named selling period.

For a named historical season, declare its dates here or analyse imported sales below; nothing is assigned until you approve it.

Analyse imported sales

Choose Analyse imported sales to look for groups of products that sold together. Choose a history window and optionally search for a product group. Results cover at most 500 products per batch; continue through the additional batches when shown. Each proposal names its leading product. Review the proposed products, remove any that do not belong, then name the period, choose Drop or Season under Called a (it starts on the kind your calendar mostly uses), and pick its first and last selling day. A last observed sale is evidence, not a closing date; you supply the last selling day. Approval saves that period and its chosen products together. Existing declared periods keep their dates.

If analysis takes too long, shorten the window or search a smaller group. Analysis needs access to the whole company history; approval also needs Read & write access.

What to do

1. Press More, then Set up selling periods, then Declare dates, or press an existing row to open the same drawer seeded from it. This needs Read & write access; a seat without it reads the calendar only, and the menu and drawer name the reason.
2. Name it under Name, and choose Drop or Season under Called a.
3. Set the first and last selling day under Opens and closes.
4. Answer Measured against: an earlier period, This is our first Drop (or Season), or Leave unanswered.
5. For a window that has already finished, use What was in it to take a product out of what gets recorded against it.
6. Press Declare the Drop (or Season) to write it.

Above the button, the drawer says what is still needed until every requirement is met, and a refusal holds the write back with its own reason; nothing is written until it clears.

Edit or archive a period

A row's menu offers Edit for the name, kind, dates and Measured against; only changes are saved, and moving the dates leaves recorded products as they are. Admins also see Archive, which removes the period from every list and cannot be undone; a period a commitment or line plan still uses is refused.

When it is empty or failed

A first run states the consequence of an empty calendar:

Every forecast sits on a standing twelve-week span that starts today.

While the calendar is read:

Reading the calendar this organization has declared.

A calendar that could not be read is a failed read, and declaring is held back until it can be read, so that a new period is never given a predecessor that already exists. Membership has its own states:

We could not read what sold inside this window, so no products can be recorded against it. The period itself can still be declared.

How many products sold in this window is not known yet.

Nothing matches. All stay recorded.

A window in which nothing in the catalogue sold is recorded with no products in it only on purpose, and the form asks you to check the dates first. A write the calendar did not confirm says the period may not have been recorded; a refused write says it was not recorded and nothing has changed.