Skip to main content

Product Lifecycle

The Product Lifecycle feature lets you define the stages your products move through as they progress from raw data to published, sellable items. By configuring lifecycle stages, you give your team a clear visual indicator of where each product stands and what still needs to happen before it is ready.
Product Lifecycle is configured per project. Navigate to Settings > Product Lifecycle to set up your stages.

Why Use Lifecycle Stages?

Clear Status Visibility

See at a glance which products are drafts, under review, approved, or published. No more guessing where things stand.

Structured Process

Define a repeatable process that every product follows, ensuring nothing gets published before it is ready.

Quality Gates

Set requirements and checklists for each stage so products cannot advance until they meet your quality standards.

Workflow Integration

Lifecycle stages connect directly to Workflows, enabling guided processes that move products from one stage to the next.

Enabling the Lifecycle

1

Open Lifecycle settings

Navigate to Settings > Product Lifecycle. Make sure you have a project selected in the project switcher.
2

Toggle the feature on

Use the Enable Product Lifecycle switch at the top of the page to activate the feature for your project.
3

Configure your stages

Once enabled, you will see the stage editor where you can add, edit, reorder, and remove stages.

Default Stages

When you first enable the lifecycle, WISEPIM provides two default stages to get you started:
StageColorPurpose
Not ReviewedRedProducts that have not been reviewed yet
ReviewedGreenProducts that have been reviewed and approved
You can customize these defaults or replace them entirely with your own stages. Click Reset to Default at any time to restore the original configuration.

Configuring Stages

Adding a Stage

Click the Add Stage button (either at the top of the stage list or at the bottom of the pipeline). A new stage appears with default settings that you can customize immediately.

Editing a Stage

Each stage card lets you configure:
  • Name — A clear label for the stage (e.g., “Draft”, “Content Review”, “Ready to Publish”)
  • Color — Pick from eight color options (blue, green, yellow, purple, red, orange, cyan, pink) to visually distinguish stages
  • Icon — Choose from 28 icons organized into five categories:
    • Content & Creation (7 icons) — icons for writing, editing, and content production
    • Review & Approval (6 icons) — icons for checking, approving, and signing off
    • Product Data (4 icons) — icons for data, attributes, and specifications
    • Publishing & Sales (7 icons) — icons for launching, selling, and distributing
    • Maintenance (3 icons) — icons for archiving, updating, and lifecycle end
  • Description — An optional explanation of what happens during this stage
Choose colors that intuitively communicate progress. For example, use red for early stages that need work, yellow for in-progress stages, and green for completed or published stages.

Reordering Stages

Stages represent a pipeline, and their order matters. Use the up and down arrow buttons that appear when you hover over a stage card to change its position in the sequence.

Deleting a Stage

Hover over a stage card and click the trash icon to remove it. Products currently in that stage will need to be reassigned to a different stage.
Deleting a stage cannot be undone after you save. Make sure no critical products are assigned to a stage before removing it.

Stage Requirements

Requirements are conditions that a product must meet before it can enter or remain in a specific stage. They act as quality gates in your pipeline.

Adding Requirements

Within each stage card, you will find a requirements section where you can add conditions:
1

Add a condition

Click Add Condition in the stage’s requirements area.
2

Select a field

Choose which product attribute to evaluate. The list includes every attribute defined in your project — both built-in fields (description, price, EAN, etc.) and any custom attributes you have created under Settings > Product Attributes. This means your quality gates can reference the exact data points that matter to your business.
3

Choose an operator

Select how to evaluate the field. The full set of available operators is:
OperatorDescription
equalsExact match
not_equalsDoes not match
containsField includes the value
not_containsField does not include the value
starts_withField begins with the value
ends_withField ends with the value
greater_thanNumeric comparison
less_thanNumeric comparison
greater_than_or_equalNumeric comparison
less_than_or_equalNumeric comparison
in_listValue is one of a set
is_emptyField has no value
is_not_emptyField has a value
is_trueBoolean check
is_falseBoolean check
4

Set a value

Enter the value to compare against, if applicable. Some operators like “is empty” do not require a value.
5

Configure logic

When you have multiple conditions, choose whether all conditions must be met (AND) or any condition is sufficient (OR).
Example requirements:
  • “Ready to Publish” stage requires: description is not empty AND quality score is greater than 75 AND main image exists
  • “Content Review” stage requires: description is not empty OR short description is not empty

Stage Checklists

In addition to automated requirements, each stage can have a manual checklist of items that team members need to verify. Checklists are helpful for tasks that cannot be validated automatically, such as “Verify product photos are high resolution” or “Confirm pricing with supplier.”
1

Add checklist items

Click Add Item in the stage’s checklist section.
2

Enter the task description

Type a clear, actionable description of what needs to be checked (e.g., “Verify all product images are at least 1000x1000px”).
3

Add more items as needed

Repeat for each manual check that should be completed at this stage.
Combine automated requirements with manual checklists for a thorough quality gate. Requirements catch data issues automatically, while checklists ensure human judgment is applied where needed.

Auto-Transition

When a stage has requirements or checklist items, you can enable auto-advance. When this is turned on, products that meet all the stage’s requirements are automatically moved to the next stage in the pipeline without manual intervention. To enable auto-transition:
  1. Make sure the stage has at least one requirement or checklist item configured
  2. Toggle the Auto-advance when complete switch at the bottom of the stage card
Auto-transition only appears as an option when a stage has requirements or checklist items defined. This prevents accidental auto-advancement in stages without quality gates.

Example Lifecycle Configurations

Simple Two-Stage Review

Ideal for small teams that just need a basic review process:
  1. Not Reviewed (Red) — Products awaiting initial review
  2. Reviewed (Green) — Products that have been checked and approved

E-Commerce Publishing Pipeline

A more detailed pipeline for teams preparing products for online stores:
  1. Draft (Blue) — Raw product data, just imported or created
  2. Content Enrichment (Yellow) — Descriptions and attributes being written or AI-enriched
  3. SEO Review (Orange) — Meta titles, descriptions, and keywords being optimized
  4. Quality Check (Purple) — Final review of all product data against quality standards
  5. Ready to Publish (Green) — Approved and ready for export to your webshop
  6. Published (Cyan) — Live on your sales channels

Multi-Market Launch

For teams managing product launches across multiple markets:
  1. Data Collection (Blue) — Gathering product specs and images
  2. Content Creation (Yellow) — Writing descriptions in primary language
  3. Translation (Purple) — Translating to all target languages
  4. Legal Review (Orange) — Compliance and regulatory checks
  5. Approved (Green) — Ready for all markets
  6. Archived (Red) — Discontinued or seasonal products

Saving Your Changes

WISEPIM tracks every change you make to the lifecycle configuration — adding stages, editing names, reordering, deleting, and toggling the feature on or off. A save bar appears at the bottom of the page whenever you have unsaved modifications:
  • Click Save to persist your entire stage configuration in one operation
  • Click Undo to revert all changes since your last save, restoring the exact state from the server
  • A loading indicator shows while the save is in progress
The undo action reverts everything at once — there is no partial undo. If you want to keep some changes and discard others, save first, then make additional edits.
Changes to lifecycle stages affect all products in the project. Coordinate with your team before making significant changes to the stage pipeline.

Using Lifecycle Stages on Products

Once you have configured your lifecycle stages, they become available directly in the Products table. Each product row displays a Lifecycle Stage selector that shows the product’s current stage with its assigned icon and color. To change a product’s stage:
  1. Find the product in the products table
  2. Click the lifecycle stage indicator on the product row
  3. Select the new stage from the dropdown — each option displays the stage name, icon, and color so you can quickly identify the right one
  4. The stage updates immediately
The lifecycle stage column in the products table adapts its width based on your configured stages, so stage names remain readable without taking up unnecessary space.
You can also filter products by lifecycle stage using the Advanced Filters in the products table. If your project has lifecycle stages defined, a dedicated review filter appears that lets you narrow down products by their current stage.