Skip to main content

Lifecycle

Lifecycle management is how you move SKUs through their statuses in bulk, keep a reversible record of each change, and find slow-moving stock worth pruning. This page covers the bulk change from a Collection and the batch record it writes.

Bulk lifecycle change from a Collection

To retire everything still active in a Collection before a new drop lands, run Bulk Lifecycle Change on the Collection Card.

  1. Choose a target SKU Status (defaults to a list filtered to Discontinued or Blocked lifecycle stages).
  2. Every currently Active SKU under the Collection's tagged Styles is gathered (respecting per-Colour tag scoping).
  3. On the Select SKUs for Bulk Lifecycle Change picker, every candidate is pre-ticked; use Select All or Clear Selection to adjust, or untick individual rows.
  4. Confirm to apply the change.

Result: "Bulk lifecycle change recorded. N SKU(s) moved to [status]; M had open Sales/Purchase Orders." Open Sales or Purchase Orders never block the transition: they are only flagged for visibility on the batch. Standard Business Central posting rules, driven by the new status's blocking flags, are what actually stop anyone posting against a discontinued SKU afterward.

Lifecycle batches and reversal

Every bulk lifecycle change writes a permanent record. Open Lifecycle Batches to see the history: Source Type and Source Code, Target Status Code, Created At/By, Line Count, Open Doc Warning Count, and Reverse Until, the cutoff after which reversal is no longer possible.

Run Reverse on a batch, within its window, to restore the prior status on every line. A batch can only be reversed once, and reversal is blocked outright once the window has expired. Changing the global Bulk Lifecycle Reversal Days setting afterward never retroactively changes a deadline already stamped on a past batch; each batch keeps the window it was given when it ran.

If a SKU in a reversed batch had reached a status flagged Is Retired, its code stays permanently retired even after the batch is reversed; the SKU itself becomes sellable again, but that specific code reservation is never undone. See Retired codes.

Run Lines on a batch to see the per-SKU detail: Prior Status Code, New Status Code, Open Doc Warning, Open Doc Detail (a readable list like "Sales Order SO-0001; Purchase Order PO-0042"), and whether that individual line has been Reversed.

More