Navigate the Product Catalog and Lifecycle

Create and manage the organization’s master product catalog, then reuse its SKUs across workflows.

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 and the source of truth for product identity, descriptive fields, product images, size-chart content, and default COG. 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.

Creating a product here creates only a draft, main product in the SKU registry. It does not create a Research or Quotation row. Those workflows can select the existing master SKU later.

Step-by-step

Open Products and confirm the active organization.
Select + Product to create a main product.
Enter a product name. Add your own SKU, or leave SKU blank to generate one from the first three alphanumeric characters of the normalized product name plus the next number for that prefix in your organization, such as EVE-001. Short prefixes are padded with X, and names without letters or digits use PRD.
Optionally add category, gender, description, default COG, up to eight ordered product images, and a separate size-chart image or size-chart text.
Select Create product. The new product is saved as a draft parent SKU.
If some media cannot upload or attach, stay on Products and use Retry remaining media in the + Product dialog. You may close and reopen the dialog while the Products page remains mounted; the saved product is reused and successful uploads are not repeated.
Choose the list view for precise searching or Kanban for lifecycle review.
Search by exact SKU first, then by product name if needed.
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.

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, media, 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 Products, Imports, or a connected source.

A manual SKU is rejected: that SKU already exists in the organization. Choose another identifier or leave the field blank to generate the next available number.

The product saved but media is incomplete: stay on the Products page and retry from the + Product dialog. The product detail link lets you inspect the saved product, but it cannot resume pending files from your device. Navigating away may clear that in-memory recovery state, so retry before leaving when possible.

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. Files uploaded through the CapitalOS Products media picker use the private organization-and-SKU products path, with signed, module-checked access. Supported durable external HTTPS or CDN references follow that external host’s access policy and are not stored in CapitalOS object storage. 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.