Settings
Settings is where you configure the catalogs and connections that power the rest of setlist. Each section is its own page; set them up once and they feed the dropdowns and behaviors everywhere else.
Where: setlist → Settings
"Configure the catalogs and connections that power your product pipeline. Pick a section to manage it."
A note on saving
setlist uses a consistent save model across Settings:
- Editing an existing row autosaves. No save button — inline Saving… → Saved status text next to the row confirms it. If a save fails, the row reads "Couldn't save — changes kept" (or "Conflict — changes kept" if the record changed in another session) and your typed values stay put.
- Adding and removing are explicit. "Add …" buttons and trash icons are deliberate clicks, and an add shows a brief confirmation toast ("Category added", "Launch created"…). Removing takes effect immediately (no confirmation dialog).
A few spots use an explicit Save button by design — the global SKU prefix (Save prefix), the Materials add/edit form, the CSV import, and the Fulfil connect/sync actions. Those are called out on their own pages.
A new shop starts empty
setlist doesn't ship with pre-loaded catalogs — a new shop starts empty, and you build these lists yourself. (Demo stores can be loaded with sample jewelry data, which is where examples like "Rings" and "Sterling Silver" in these docs come from.) Wherever a catalog is empty, the related field on a product shows an "Add … in Settings" hint.
Suggested setup order:
- Categories & SKUs — set the global SKU prefix, add your categories, build their SKU templates and default options
- Team — teams + people (product owners)
- Launches and Product lines
- Classifications — your custom product fields
- Testing presets and Questionnaires
- Materials — sync them from Fulfil, or add them by hand / by CSV if you don't use Fulfil
- Campaign types and Preferences as needed
The sections
| Section | What it configures |
|---|---|
| Categories | The Category dropdown + how SKUs are generated (global prefix, per-category templates, auto-derived codes), default variant options, target margin/forecast, and sub-categories |
| Team | Teams (groups) and People (the product owners); one team can be marked default for compatibility |
| Launches | The launches you assign products to — name + date range + internal images |
| Campaign types | Labels for the campaign Type dropdown (Seasonal, Drop, Collab…) |
| Product lines | The product-line dropdown; each line's behavior drives a limited-quantity or limited-date field |
| Classifications | Define-your-own product fields — a Yes/No picker, a managed list, or a free-form text field |
| Testing presets | Standard QA tests used as the test-name dropdown |
| Questionnaires | Reusable question sets for user testing |
| Materials | Raw materials — synced from Fulfil (read-only) and/or added by hand (manual entry + CSV import) |
| Integrations | The Fulfil connection |
| Preferences | App-behavior toggles (progressive product view, design lead time) |
| Billing | The single Shopify-managed plan and its status |
How it all connects
Categories ──▶ SKU generation, the Category dropdown, default variant options,
target margin (→ suggested prices), target forecast (→ starting forecast),
sub-categories
Global SKU prefix ──▶ prepended to SKUs (when a category's template includes the prefix token)
People ──▶ the product Owner dropdown; Team appears as each person's group
Launches ──▶ product assignment; launch window scales weekly/monthly forecast targets;
launch end date defaults a limited-date product's end date
Product lines ──▶ the line dropdown; behavior → limited-quantity / limited-date field
Classifications ──▶ custom fields on the chosen product stage card
Testing presets ──▶ the QA test-name dropdown (prefills prescription + team responsibility label)
Materials ──▶ the bill-of-materials picker (unit cost + stock); pending materials block launch
Fulfil connection ──▶ populates Materials (optional — materials can also be added by hand / CSV)
Preferences ──▶ progressive product view; the design lead time that derives due dates