Skip to main content

Seasonality and the active season

How seasons work in Resourced: the active season selector in the top header, how seasons scope products, BOMs and exports, how a new season copies forward, and where seasons are set up.

Resourced is built around seasons. A products articles belongs to one or more seasons, and some of its detail — its BOM, its prices, tags, custom fields and suppliers — is held per season, so the same product can carry different specs from one season to the next without overwriting its history.

The active season selector

The Active season control sits in the top header, on every page. Open it and you get a list of your brand's seasons; tick one to make it active. The selection is a filter on what you're working in and shows the values for the active season.

With a season active, you only see that season's values. If a product or article has nothing recorded on that season, its fields show empty — which catches people out: you know you entered the information, but it lives on a different season while this one is active. To see everything again, open Active season in the header and click your selected season to deselect it.

In the table, when no active season is selected, the values shown are from the latest season.

The active season selector in the top header, showing where it sits

The active season selector open in the top header, with the season list and the active season

How seasons run through the system

A few things are held per season rather than once per product:

  • The BOM — each product has one BOM per season. Editing the BOM in one season doesn't touch the others. In article row the principal material comes from the BOM of the season selected.

  • Pricing — article prices can be set per season, so a colorway can be priced differently from one season to the next.

  • Suppliers — an article's supplier can be set per season, so the same colorway can be sourced from a different supplier across seasons.

  • Tags — article tags are per season (product tags are not), so the same article can be tagged differently from one season to the next.

  • Custom fields — a custom field that's set up as seasonal in Admin is held per season, so its value can change from one season to the next.

When you add a season to a product or article, the system copies forward from the article's latest existing season rather than starting blank — the BOM's slot connections and colors come across as a best-effort starting point, which you then adjust.

Import and export

Both export and import follow the active season.

  • Export — if an active season is selected and you export, you export that season. If no season is chosen you export the latest season — so it's worth checking the selector before pulling an export.

  • Import — an active season must be set to bring data into a specific season; otherwise the imported data lands on the latest season.

Where seasons are set up

Seasons themselves — their names, colors, the channels they belong to, and the active date ranges — are configured in Admin. This is also where you add a new season or channel.

Deleting a season

Deleting a season asks you to confirm first. If the season is still in use, the system additionally warns you when the deletion would clear seasonal data — for example when you'd be removing the last season from a product or article. Season names also have to be unique within your brand, so you can't create or rename two seasons to the same name.

⚠️ Deleting a season that's in use can clear the seasonal data attached to it. Read the warning before confirming.

Did this answer your question?