How to Organize Products and Categories Before Building Your Store

Start with product truth, not page layout

Before you build, decide what each product is, what it costs, where it belongs, which facts buyers need, and which images show it accurately.

Your catalog is the source of truth; the storefront is its presentation. Keep them separate so a layout change cannot alter a price, and polished copy cannot disguise a missing measurement.

A practical way to enforce the boundary is to keep two columns in your working document:

If a fact is missing, mark it as missing. Do not write around it. If the presentation is weak, improve the page without changing the factual record.

Define the required fields for every launch product

Create one row per sellable product and use the same fields throughout. Consistent structure makes gaps easier to see.

At minimum, record:

• Internal identifier: a stable team reference that need not appear to shoppers.
• 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 approved facts from which copy can be developed.
• Category assignment: one primary shopping category and any additional placement that serves a genuine customer path.
• Availability status: a controlled value such as ready, paused, or awaiting stock confirmation.
• Fulfilment facts: weight, packed dimensions, handling constraints, or other details 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: the person who checked the record and any unresolved issue.

These are preparation fields, not a claim that every storefront exposes a rich standardized attribute system. Store category-specific details as verified source facts; decide later where they should appear.

Avoid adding fields merely because another store uses them. Start with the questions a buyer must answer and the facts your operations team must know.

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.

Do not rely on invented labels such as “best seller,” “limited,” or “premium.” Use those words only when they describe a real, supportable state.

Treat price as controlled commerce data

Record price as a number and currency separately. Do not 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 storefront can emphasize a price but should not infer one. For catalog readiness, ask whether the price is 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:

1. What it is: the product type and intended use.
2. What distinguishes it: a verified material, format, function, scent, finish, or other meaningful difference.
3. What the customer receives: quantity and package contents.
4. What they need to know: dimensions, care, ingredients, compatibility, warnings, or limitations where relevant.

Keep placeholders such as “TBC” visible in the source until resolved, but never in finished customer copy. A blank creates a clear task; an invention hides one.

Setka can generate and refine storefront copy from the merchant’s catalog and brief, preserve merchant-supplied wording, or combine both. The merchant still owns product truth and approves the final copy. The same rule applies whether a person or AI writes it: expression may change; facts may not drift.

Design categories around shopping decisions

Categories should reflect how shoppers look for products, not your internal folders.

Begin 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.

Assign one primary category to each product. Add a secondary category only for another real shopping path, such as “Gifts Under €30.” Placing everything everywhere weakens category meaning.

The structure should also support later category page design: each category needs a reason to exist, a clear label, and products that make sense together. Detailed merchandising choices—featured products, seasonal edits, and ordering—belong 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. Every detail is illustrative, not a real product claim.

Sample catalog

A production sheet should add separate currency, full facts, fulfilment 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 exposes useful questions. Is a two-product category worthwhile? Does “Writing Tools” match customer language? Is the gift collection helpful, or merely repetitive? The merchant decides based on the offer and intended shopping paths.

It also shows why category assignment and display ordering are different. NP-101 can belong to Notebooks without automatically becoming the first card. Card content and hierarchy deserve 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 uses the catalog media supplied or authorized by the merchant when generating product pages.

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 fulfilment 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.

Let the clean catalog inform the whole storefront

Once ten records pass the checklist, they become more than product-page inputs. Names and images shape product cards. Category logic shapes navigation and collection pages. Price range and catalog size influence hierarchy. Descriptions and media inform how the products are presented across the store. The complete sequence continues in how to build an online store.

This is where Setka becomes useful: the catalog and brief inform the generated storefront as a whole, including homepage, category pages, product-page templates, shared surfaces, and cart. Setka can populate product-page templates with actual product data, descriptions, and media; generate or refine copy; and let the merchant preview and direct changes. The merchant remains responsible for product truth, price approval, image rights, and category decisions.

That division of responsibility is productive. Setka can change how the catalog is expressed without turning presentation into a second, competing source of facts. You can refine a page, edit exact wording, and review the result while the approved product record stays authoritative.

Prepare ten complete products now. Choose a representative set, fill every required field, map each product to a useful category, attach the approved images, run the checklist, and hold back any record that still depends on a guess.