Add and Organize a Research Product

Create a research record, capture useful validation evidence, and prepare it for the next product decision.

Before you begin

Confirm the active organization, Research access, and the organization’s SKU convention. Search for the SKU before adding a record so you do not split research evidence across duplicates. Gather the product name, priority, category, competitor or sourcing references, and validation notes available to your team.

How it works

Research is the first structured stage of the product workflow. Each row represents organization-scoped product research linked through its SKU. Configurable columns hold evidence and evaluation fields, while status and priority help the team organize what should be reviewed next. A product can be entered in the grid or loaded through the supported Imports workflow.

Step-by-step

Open Research in the correct organization and search for the intended SKU.
If no suitable record exists, add a row through the available grid action or use Imports for a prepared workbook.
Enter a stable SKU and recognizable product name.
Set the appropriate research status, priority, and category where those fields are configured.
Add validation notes and supported competitor, advertising, sourcing, creative, or market references.
Fill only evidence you can support; leave unavailable information blank rather than inventing a value.
Review the row across the visible columns and save any editable changes.
Use filters or a saved grid arrangement to keep the product in the correct review queue.

Check your result

The product appears once under the intended SKU, its key evidence is readable, and its status and priority place it in the expected research workflow. Reopening or refreshing the grid preserves the saved data. A teammate with Research access can locate the same organization record.

Common problems

The SKU already exists: open the existing product and add evidence there unless the new item is a true variation.

A field is not visible: use the column chooser and check whether the organization has configured that research column.

The row will not save: review required identity fields, invalid links, and your edit permission.

Workbook data is rejected: use Imports to inspect sheet readiness, headers, and duplicate or missing SKU issues.

Permissions and data notes

Research access is organization-specific. Column availability and editable fields can depend on shared settings and role permissions. Avoid customer information or credentials in notes and references. Moving a product forward is a separate workflow action and can require Quotation access.