Navigate the Product Catalog and Lifecycle

Search the organization SKU registry and use list or Kanban views to understand product state.

Before you begin

Select the correct organization and confirm that Products is enabled for your role. Know the SKU, name, lifecycle state, or variation group you want to inspect. Products combines records from several workflows, so missing module-specific information can reflect incomplete source data rather than a missing catalog item.

How it works

Products is the shared organization catalog. The list view supports SKU and name search, sorting, paging, and record-level navigation. The Kanban view groups supported products by lifecycle state and provides a visual operating queue. Parent and child identifiers preserve product variation structure across both views.

Step-by-step

Open Products and confirm the active organization.
Choose the list view for precise searching or Kanban for lifecycle review.
Search by exact SKU first, then by product name if needed.
Review status, variation, and available performance or returns summaries.
Use sorting or paging to move through a larger registry.
In Kanban, search the board and identify the current lifecycle column.
Open the product rather than inferring its full history from a card or row.
Use Imports only when an authorized batch update has been validated.
Recheck the catalog after workflow transitions or synchronization completes.

Check your result

The intended SKU appears once in the expected lifecycle position, with child variations grouped appropriately. Opening the record shows the same identity and organization context. List and Kanban views describe the same catalog even though they emphasize different information.

Common problems

A product is missing: clear search, check pagination and organization, then verify whether the SKU exists in Research, Imports, or a connected source.

A product appears twice: compare exact SKU formatting and parent-child identity before changing records.

Kanban and list counts differ: filters, lifecycle grouping, and variation presentation can change the visible count.

A metric is blank: the linked module, date window, integration, or identity match may not supply that evidence yet.

Permissions and data notes

Catalog viewing, importing, editing, and lifecycle actions can require different permissions. Product analytics are operational summaries derived from linked data. Do not treat a blank field as zero or reorganize established identities without checking downstream relationships.