Products & product cards

A product card is a pre-launch planning record. You build it in setlist — variants, SKUs, costs, tests, pricing, forecast — and only push it to Shopify once it's ready to list.

Where: setlist → Products The detail page is documented separately: The Product Workspace

What a product card is

setlist's intro line says it best:

"Plan products, generate SKUs, prescribe tests, set pricing, and review them before they're created in Shopify."

A product card is everything about a product before it becomes a real Shopify listing. It starts with a temporary working name and an auto-generated SKU, then moves through the stages — Plan → Design → Review → Ready for launch — as you flesh it out. When it reaches "Ready for launch," you push it to Shopify and finish the listing there.

setlist owns the prep (variants, SKUs, bill of materials, costs, testing, forecast). Shopify owns the listing (final name, photos, description, SEO, collections). The two don't overlap.

setlist

the prep room

Variants
SKUs
Bill of materials
Costs
Testing
Forecast
Readiness pipeline

Shopify

the listing

Official name
Photos
Description
SEO
Collections
Live storefront

Fulfil

source of truth for materials

Stock on hand
Unit costs
Labor

Who owns what — setlist · Shopify · Fulfil

Creating a product card

Click New product card (on the Products list, the dashboard, or from inside a campaign). The form has four sections.

1. Product details

Field	Required	Notes
Working name	✅	A temporary name to start ("e.g. gold ring with a blue stone"). The SKU auto-derives from the product type + this name. You set the official name later, in Review.
Description	—	A short internal working description. The final listing description still lives in Shopify.
Link to brief	—	A Monday doc or any other URL for the product brief. A URL without `https://` is normalized so it still opens directly.

2. Classification

Field	Required	Notes
Product type	✅	Drives the SKU and the available subcategories. Sourced from Settings → Product types. (If you haven't added any types yet, this becomes a free-text field with a hint to add them in Settings.)
Subcategory	—	A dependent dropdown — appears once you pick a type that has subcategories.
Product line	—	From Settings → Product lines. Its behavior may add a conditional field below (see "Launch & availability").
Behavior	(read-only)	Mirrors the chosen line's behavior — None / Limited date / Limited quantity. Set on the line in Settings.
Owner	—	A person from Settings → Team. Defaults to "Unassigned."
Plan-stage classifications	—	Any classifications you've set to show at the Plan stage appear here.

3. Launch & availability

Field	Required	Notes
Campaign	—	Only shown if you have campaigns. Adds the new product to that campaign on save. Pre-filled when you start from a campaign.
Launch group	—	A launch to assign to. Assigning one seeds and locks the launch date to the launch's start.
Launch date	—	Editable when no launch is assigned (no past dates). Locked to the launch's start when a launch is assigned.
End date	conditional	Appears when the product line's behavior is Limited date. Defaults to the launch's end date.
Quantity	conditional	Appears when the behavior is Limited quantity — the units cap.

4. Testing

Field	Default	Notes
Tests required for this product	ON	Turn off for products that don't need physical testing — the test UI is then hidden.

Click Create product. setlist generates the SKU, creates a single default variant, files the card at stage Plan, and opens its detail page.

What's created automatically: the SKU (you never type it), one default variant carrying that SKU, and — if the product type has a forecast target — a starting forecast. You add option types/variants later on the detail page.

Required fields

Only two things are required to create a card:

A working name — "Give the product a working name before creating it."
A product type — "Pick a product type so setlist can generate the SKU."

New product card

Product details

Working name

e.g. gold ring with a blue stone

Description

What is this product, who is it for, any notes for the team…

Classification

Product type

Ring (R)⌄

Subcategory

Band⌄

Product line

Core⌄

Behavior

None

Owner

Priya L. — Design⌄

Launch & availability

Launch group

Fall 2026⌄

Launch date

Sep 1, 2026

Set by Fall 2026

Testing

Tests required for this product

Turn off for products that don’t need physical testing.

Create productCancel

Creating a product card — the four sections

The Products list

Columns: Product · Stage · Owner · Ready · Margin · Channels

Column	Shows
Product	Title (links to the detail page) + SKU beneath
Stage	The pipeline-stage badge
Owner	Assigned person + team, or "Unassigned"
Ready	Readiness % — a fixed 6-point checklist (named, SKU, final price, supplies, channels, tests). Brand-new cards read low; that's expected.
Margin	Product margin %, or "—" when there's no final price yet
Channels	Selected sales channels, or "—"

Filtering

The Filter popover lets you filter by Launch and by one or more Stages (each stage shows its live count). The button reads "Filtered (N)" when active. There's no free-text search or column sorting — use the filter.

Editing forecasts and assignments

Click Edit to reveal row checkboxes and an editable Forecast total column.

Enter forecast totals and click Save — setlist splits each changed total evenly across that product's variants. Unchanged rows are ignored.
Select one or more visible rows and click Add to… to attach them to a campaign or move them to a launch. Choosing No launch (unassign) clears the launch assignment.
Filters compose with selection: bulk assignment only acts on checked products that are still visible.

Importing products from CSV

Already have products in a spreadsheet? Click Import CSV — on the Products list toolbar, or from the Setup actions menu on the empty state — to bulk-create (or update) product cards.

The flow: drop a .csv file (with a header row) on the upload zone, then click Import. There's no preview or column-mapping step — setlist reads the headers and imports straight away, then shows a summary such as "Imported 12 new · 3 updated," with any skipped rows called out.

Recognized columns

Only two things are required for a new row: title (the working name) and productType. Everything else is optional.

Column	Notes
title (required)	The working name. Also accepts `name`, `product`, `style`, …
productType (required for new rows)	Must match a type in Settings → Product types by name or SKU code. Also `type`, `category`.
sku	Leave blank to auto-generate. A SKU that matches an existing product updates that product instead of creating a new one.
description · briefUrl · subcategory · owner · launch · launchDate · productLine · endDate · limitedQuantity · campaign · testsRequired · forecastTotal	All optional. `owner`, `launch`, `productLine`, and `campaign` resolve against your Settings catalogs by name (or id) — an unrecognized value is quietly dropped.

Headers are matched loosely (case, spaces, and punctuation are ignored, and common aliases are accepted), so Product Type, product_type, and PRODUCT-TYPE all land on the same column.

How rows are matched

setlist matches each row to an existing product by SKU (case-insensitive):

No match → a new product card is created at stage Plan with one default variant. testsRequired defaults on unless the column says otherwise.
Match → that product is updated (title, type, description, dates, owner, classifications…). Its stage, production quantity, due date, and assignee are preserved.

Gotchas. There's no undo — a matched SKU overwrites. If two rows resolve to the same SKU, the first wins and the rest are skipped. And if your file has no recognizable header row, columns are read positionally in the order above, so always keep a header row.

Tips & gotchas

You don't type SKUs. They're generated from the product type's template + your global prefix. You can override a variant's SKU on the detail page if needed. See Product types & SKUs.
The working name isn't the final name. The official (Shopify-ready) name is set in the Review stage and is what syncs to Shopify.
Two "readiness" numbers exist. The list's Ready column (and the dashboard's Avg readiness) use a fixed 6-point checklist; the pipeline board's progress bar tracks the current stage's gate. They can differ for the same product. See Stages & progress gates.
Set up Settings first. Product types, team, launches, product lines, and classifications all feed the creation form. An empty catalog shows an "Add … in Settings" hint. See Settings.