Start with product truth, not page layout
Before you build, settle five things for every product: what it is, what it costs, where it belongs, which facts a buyer needs, and which images show it accurately. Keep those answers in one catalog sheet, group the products by how shoppers look for them, and check the sheet before any page exists. Ten complete products are enough to start.
The catalog is the source of truth; the store is how that truth is presented. Keep them separate, so a layout change can’t alter a price and polished copy can’t hide a missing measurement. Setka is our product, and it is built around that separation: it builds the store from your catalog and brief, and it can rewrite how a product is presented without touching the facts you approved.
The simplest way to hold the line is two columns in your working document:
| Product data truth | Presentation decision |
|---|---|
| Name, price, currency, dimensions, material, contents, availability, category assignment | Headline style, description structure, image order, section hierarchy, featured placement |
| Approved by the merchant or product owner | Generated, edited, tested, and changed without rewriting the underlying facts |
If a fact is missing, mark it as missing instead of writing around it. If the presentation is weak, improve the page and leave the factual record alone.
Define the required fields for every launch product
Create one row per sellable product and use the same fields throughout, so gaps are easy to see.
At minimum, record:
- Internal identifier: a stable team reference that shoppers don’t need to see.
- Product name: the customer-facing name, written consistently across the catalog.
- Selling price and currency: the exact current amount before any defined discount.
- Factual summary: what the product is, its main use, and the approved facts that copy can be built from.
- Category assignment: one primary shopping category, plus other placements only where they serve a real customer path.
- Availability status: a value from a fixed list, such as ready, paused, or awaiting stock confirmation.
- Fulfillment facts: weight, packed dimensions, handling constraints, or anything else needed to deliver the item.
- Product-specific facts: material, ingredients, dimensions, care, compatibility, or package contents when relevant.
- Image references: filenames for the approved main image and supporting views.
- Review status: who checked the record and any unresolved issue.
These are preparation fields. Not every store shows each one as a structured attribute, so record category-specific details as verified facts and decide later where they appear.
If a product comes in options such as size and color, record each combination you sell with its own price and availability, and note which product it belongs to. Setka supports variants, including combinations of two options, each with its own price.
Add a field only when it answers a buyer’s question or something your fulfillment depends on, not because another store has it. Fields that enrich presentation without changing a decision, such as a longer product story or extra lifestyle shots, can wait for a named owner and date. If a buyer can’t safely purchase without a field, or you can’t ship correctly without it, it belongs in the launch set.
Agree what each field means
Add a short field dictionary above the sheet or on a separate tab. For each field, give the format, allowed values, an example, and who approves it. That keeps “dimensions” from meaning the product to one person and the parcel to another. The examples come from the fictional Northline Paper catalog later in this guide.
| Field | Format and rule | Example | Approved by |
|---|---|---|---|
product_id | unique, permanent text; no spaces | NP-101 | catalog owner |
name | customer-facing name | Harbor A5 Notebook — Plain Pages | product owner |
fact_summary | 2–4 sentences, confirmed facts only | A5 notebook with a cloth cover... | product owner and editor |
price | number, no currency symbol | 18.00 | whoever owns pricing |
currency | three-letter code | EUR | finance or owner |
availability_status | one value from a shared list: ready, paused, awaiting stock | ready | catalog owner |
primary_category | exact name of an approved category | Notebooks | offer owner |
packed_weight_g | weight of the packed parcel in grams | 410 | whoever packs orders |
package_mm | length × width × height | 240 × 180 × 30 | whoever packs orders |
main_image | full name of the approved file | np-101-main.jpg | brand or photographer |
open_issue | a specific gap, or — | Verify care text | owner named in the note |
approved_by | name and role of the person who checked the facts | Anna, brand owner | catalog owner |
For a first pass, these columns are enough (semicolons separate columns; pick one rule for fields that hold several values):
product_id;name;fact_summary;price;currency;availability_status;primary_category;additional_categories;product_facts;packed_weight_g;package_mm;main_image;additional_images;open_issue;approved_by
Name one sheet as the master copy and give a small number of people the right to change it. The photographer’s shot list, an export, and the copy brief are views of that catalog, not competing versions: when a price or name changes, fix the master and refresh the views.
Write product names for recognition and comparison
A product name should help a shopper identify the item in a list and distinguish it from nearby options. Choose a pattern and apply it throughout the launch range.
A useful pattern for a small catalog is:
Distinctive name + product type + meaningful differentiator
For example, “Harbor A5 Notebook — Plain Pages” distinguishes the item without stuffing the title with every specification. The paper weight, binding, and page count can live in the details.
Check names side by side. Look for inconsistent capitalization, unexplained abbreviations, near-duplicates, and distinctions buried at the end of long titles. If “Stone Mug” and “Stoneware Mug” are different, the names must explain how; otherwise you may have found a duplicate.
Don’t use labels such as “best seller,” “limited,” or “premium” unless they describe a real state you can support.
Treat price as controlled commerce data
Record price as a number and currency separately. Don’t mix “38”, “€38,” and “38.00 EUR” in one price column.
Then check every amount against the source that owns pricing. Flag:
- zero or blank prices;
- currencies that differ unexpectedly;
- decimal or separator mistakes;
- sale prices without a valid original price and real sale state;
- identical products with conflicting amounts;
- product descriptions that mention an old price.
The store can emphasize a price but must never infer one. Before launch, each price should be current, approved, and attached to the correct product.
Build descriptions from facts in two layers
Keep a factual source description separate from customer-facing copy. The source should answer the buying questions with plain statements. The presentation layer can decide order, emphasis, rhythm, and tone.
For each product, capture:
- What it is: the product type and intended use.
- What distinguishes it: a verified material, format, function, scent, finish, or other meaningful difference.
- What the customer receives: quantity and package contents.
- What they need to know: dimensions, care, ingredients, compatibility, warnings, or limitations where relevant.
Keep placeholders such as “TBC” visible in the source until they are resolved, and never let one reach customer copy. A blank creates a clear task; an invention hides one.
Setka can write and refine the store’s copy from your catalog and brief, keep your own wording, or combine both. Whether a person or AI writes it, the rule is the same: expression may change; facts may not drift.
Design categories around shopping decisions
Categories should follow how shoppers look for products, not how your files are organized. Start with three questions:
- What does the shopper believe they are looking for?
- Which product difference changes their decision?
- Does this group deserve a page with a clear purpose?
Use concrete labels such as “Notebooks,” “Desk Accessories,” or “Writing Tools.” Avoid “Other,” “Everything Else,” and clever labels that require interpretation. Keep the structure shallow enough to scan. Ten products rarely need five levels of hierarchy.
Give each product one primary category. Add a second placement only for another real shopping path, such as “Gifts Under €20.” Put everything everywhere and categories stop meaning anything. In Setka, a product can sit in several categories, and menus can range from a few top-level links to multi-level mega-menus, so the store can follow whatever structure you settle on here.
Write one or two plain sentences describing each category, too: who it is for and what sets its products apart. Setka uses the category list and these descriptions when it builds the store.
Each category needs a reason to exist, a clear label, and products that belong together; category page design builds on exactly that. Featured products, seasonal edits, and ordering are merchandising choices, covered in the guide to merchandising a small catalog.
A fictional ten-product worked example
The catalog below is entirely fictional. It assumes a desk-goods brand called Northline Paper, euro prices, one sellable record per product, and no configurable options.
Sample catalog
| ID | Customer-facing name | Price | Primary category | Key verified source facts | Main image | Record status |
|---|---|---|---|---|---|---|
| NP-101 | Harbor A5 Notebook — Plain Pages | €18 | Notebooks | A5; 160 plain pages; cloth cover | np-101-main.jpg | Ready |
| NP-102 | Harbor A5 Notebook — Ruled Pages | €18 | Notebooks | A5; 160 ruled pages; cloth cover | np-102-main.jpg | Ready |
| NP-103 | Field Pocket Notebook — Grid Pages | €9 | Notebooks | A6; 96 grid pages; card cover | np-103-main.jpg | Ready |
| NP-104 | Weekly Desk Planner | €24 | Planners | Undated; 60 weekly sheets; A4 | np-104-main.jpg | Ready |
| NP-105 | Daily Focus Pad | €14 | Planners | 50 tear-off sheets; A5 | np-105-main.jpg | Ready |
| NP-106 | Oak Pen Rest | €16 | Desk Accessories | Solid oak; holds one pen; 18 cm | np-106-main.jpg | Needs scale image |
| NP-107 | Brass Page Clips — Set of 6 | €12 | Desk Accessories | Six clips; brass finish; storage sleeve | np-107-main.jpg | Ready |
| NP-108 | Canvas Pencil Case | €22 | Desk Accessories | Cotton canvas; zip closure; 20 × 7 cm | np-108-main.jpg | Verify care text |
| NP-109 | Fine Liner Pen — Black | €4 | Writing Tools | Black ink; 0.5 mm tip; one pen | np-109-main.jpg | Ready |
| NP-110 | Mechanical Pencil — 0.5 mm | €11 | Writing Tools | 0.5 mm lead; metal body; one pencil | — | Missing main image |
A production sheet should add separate currency, full facts, fulfillment information, supporting images, availability, and an owner for unresolved issues.
Category tree
Shop
├── Notebooks
│ ├── NP-101 Harbor A5 — Plain
│ ├── NP-102 Harbor A5 — Ruled
│ └── NP-103 Field Pocket — Grid
├── Planners
│ ├── NP-104 Weekly Desk Planner
│ └── NP-105 Daily Focus Pad
├── Desk Accessories
│ ├── NP-106 Oak Pen Rest
│ ├── NP-107 Brass Page Clips
│ └── NP-108 Canvas Pencil Case
└── Writing Tools
├── NP-109 Fine Liner Pen
└── NP-110 Mechanical Pencil
Optional secondary collection: Gifts Under €20
NP-101, NP-102, NP-103, NP-106, NP-107, NP-109, NP-110
The tree raises useful questions. Is a two-product category worthwhile? Does “Writing Tools” match how customers talk? Does the gift collection help, or just repeat the other categories? You decide, based on the offer and the shopping paths you intend.
It also shows that category assignment and display order are separate decisions. NP-101 can belong to Notebooks without becoming the first card. Card content and hierarchy need their own review; see what shoppers need on a product card.
Prepare images as product evidence
Every launch product needs an approved main image. Supporting images should answer relevant questions about scale, texture, finish, contents, or use.
For each record, log:
- main and supporting filenames;
- what each view proves;
- orientation and crop readiness;
- minimum useful resolution for your intended layouts;
- color or retouching issues;
- rights or ownership status;
- missing views and the person responsible for them.
Use filenames tied to the product ID. NP-106-scale-desk.jpg is more useful than final-new-3.jpg. Check that files open, match the item, and show current packaging.
A detail crop cannot replace a full-product view, and a lifestyle image cannot prove package contents. The product image and brand asset guide covers shot planning and file organization. Setka places your catalog images across the store, on product pages, product cards, and merchandising sections, so a missing or wrong image shows up everywhere the product does.
Run missing-data and duplicate checks
Review the catalog in passes so repeated errors stand out.
Completeness pass: filter required fields for blanks. Resolve missing names, prices, categories, main images, and essential facts.
Consistency pass: compare capitalization, units, currency, category labels, availability terms, and filename patterns. Normalize the format without changing the meaning.
Duplicate pass: find repeated IDs, identical or similar names, reused main images, and copied descriptions. Similar names may be valid, but their differentiator must be explicit.
Contradiction pass: compare the structured facts, description, packaging text, and images. A record that says “set of six” while the image shows four needs investigation, not creative rewriting.
Category pass: confirm every product has one primary home, every label is used consistently, and every category represents a meaningful shopping path.
Approval pass: have the person responsible for the products approve the facts and record unresolved issues. Products with launch-critical gaps should remain out of the ready set.
Catalog readiness checklist
Use this gate before handing the catalog to a store builder:
- Every product has one unique internal identifier.
- Names follow one pattern and clearly distinguish similar products.
- Every price and currency is current, approved, and correctly formatted.
- Source descriptions contain facts rather than unsupported marketing claims.
- Package contents, dimensions, materials, care, and warnings are present where relevant.
- Every product has one primary category with a clear customer-facing label.
- Secondary category placement serves a real shopping path.
- Category labels and assignments contain no accidental duplicates or spelling variations.
- Every product has an approved main image tied to the correct record.
- Supporting images answer relevant buying questions.
- Image filenames, crops, and rights status have been checked.
- Blank required fields, duplicate IDs, near-duplicate names, and conflicting facts have been reviewed.
- Availability and fulfillment information are confirmed for launch.
- One accountable person has approved each ready record.
- Unresolved products are excluded from the ready set rather than completed with guesses.
What a clean catalog does for the whole store
Once ten records pass the checklist, they feed far more than product pages. Names and images shape product cards. Category logic shapes navigation and category pages. Price range and catalog size shape the hierarchy. Descriptions and media shape how products are presented across the store. The full sequence continues in how to build an online store.
In Setka, that happens directly. The catalog and brief are what Setka builds the store from: homepage, category pages, product-page templates filled with your actual product data, descriptions, and photos, plus header, footer, navigation, and cart. When you later open a page and ask for a different emphasis, or edit a headline yourself, the presentation changes and the approved product record stays the authority. A clean catalog is the best input you can give it.
Pick your ten representative products, run them through the checklist, and hold back any record that still depends on a guess. Then start your store in Setka and add those ten first.