# Season membership

Source: https://docs.tightly.io/help/commitments/season-membership
Reviewed: 2026-10-29

## The question this page answers

For each season you have declared, which products does Tightly think belong in it, and what do you say to each proposal?

## What you see

Season membership is a review of proposals, opened from **Selling periods**. Tightly reads the sales of your products against the windows of the seasons you declared and proposes a season for each product. A proposal is not applied until you accept it, and it is never applied for you.

Two views sit under the title: **Suggestions** and **Fits no season**, each with a count. In **Suggestions**, a second row of views reads **Waiting on you**, **Accepted** and **Rejected**, with a search box, "Search this page".

Each row of the table is one product in one season. A product that fits two seasons is two rows. The first column names the product and its category. The others are **Season**, **Window**, **Units** and **Sold in season**, which reads the share of the product's sales inside the season, with the sentence behind it. **Window** is the member's own window: the season's window, cut to start when the product launched. **Category** and **In window** can be shown from the column menu. A season that is running or upcoming wears a tag saying so. Where there is no sales history, a row carries a word for how strong its evidence is, Strong or Weak, with a count, and the units read Never sold.

Select a row to open it. The panel shows the share of the product's sales in the season, the units in the window and the total units, and the sentence the proposal rests on.

**Fits no season** lists, with a count of products each, the reasons a product got no proposal. That is a normal outcome, and the page names it rather than leaving a blank.

The **Season steps and figures** icon opens **Season steps**, which says where each step stands: continuity, seasons, membership and what follows from it. **Refresh the proposals** reads the sales again. Both **Refresh the proposals** and the decisions need a seat that can write.

## What to do

1. Open **Selling periods**, then **More**, then **Season membership**. If no season is declared, the page says "Nothing can be proposed until a season is declared and its previous instance named." and offers **Declare a season**.
2. In **Waiting on you**, select a row to open it and read the sentence under the figures.
3. Select **Accept into {season}** to make the product a member. The panel says first what will happen: the product "becomes a member of {season}, stamped as a proposal you accepted". It also says whether a forecast follows. Where the season has no previous season named, the panel shows "Needs a linked previous season" and no forecast follows until one is named.
4. To refuse, select **Reject** and add a reason. The season is never suggested for that product again, and the product stays in the catalogue and can still be recorded in a season by hand.
5. If the engine chose the wrong season, select **Move…**, pick the season under **Move to**, give a **Reason** and select **Move to {season}**. The product is recorded in the new season as your own declaration, and the old one is not suggested again.
6. To accept several at once, tick their rows and select **Accept {n}**. Pick proposals for one season, and of one evidence tier, at a time.

Each decision answers where the button was, for example "Accepted {day}. {product} is a member of {season}." A row someone else already answered reads "Already answered; nothing changed."

## When it is empty or failed

The empty views read "Nothing waits on you; every proposal has been answered.", "No proposed members accepted." and "Nothing has been refused yet." A failed read shows "Season proposals unavailable" with a retry control. If a change could not be confirmed, the row stays blocked with "An earlier membership change could not be confirmed. Refresh and review the saved membership before trying again."
