Product catalog setup

A maintainable catalog is the difference between a store that scales and one that collapses under its own variants. This guide covers products and variants, collections, media, and imports on Build Me Web Commerce.

Products & variants

Model the shopper-facing product as the parent. Variants carry SKU, price, barcode, and inventory. Keep option names consistent — Size, Color, Material — across the catalog so filters and analytics stay coherent.

Avoid exploding matrices you cannot stock. If most combinations are impossible, use fewer options or separate products. Each purchasable SKU should have a clear fulfillment story.

1. Create the parent with title, description, and default media.
2. Define option axes before adding dozens of rows.
3. Assign unique SKUs; never reuse SKUs across active products.
4. Set price and compare-at carefully — misleading compare-at pricing erodes trust and can violate regional rules.

Parent: Trail Runner Shoe
├── Size: 8 / 9 / 10
├── Color: Slate / Clay
└── SKUs: TR-8-SLT, TR-8-CLY, …

Collections

Manual collections suit campaigns and editorial merchandising. Automated collections suit rules such as tag equals sale or product type equals clearance. Avoid overlapping rules that fight for the same product and churn membership daily.

Collection pages need unique copy and metadata — thin tag pages rarely deserve indexation. Curate navigation collections separately from SEO landing collections when intent differs.

• Sort order: manual for campaigns, best-selling or newest for evergreen.
• Seasonal collections: schedule publish/unpublish with inventory plans.
• B2B catalogs: hide wholesale-only collections from the public storefront.

Media

Upload high-quality images; Build Me Web generates responsive derivatives. Put the primary image first — it feeds LCP on product detail pages and cart thumbnails.

Use consistent framing and backgrounds within a collection so grids look intentional. Provide alt text that describes the product, including color or variant when the image is variant-specific. Video and 3D, when used, should not block first paint; lazy-load below the fold.

• Primary image optimized and dimensioned
• Variant images mapped to the correct SKU
• Alt text written for accessibility and clarity
• No watermarked vendor comps in production

Imports

CSV and API imports support bulk create and update. Always dry-run on a preview store before touching production inventory. Validate encodings, decimal separators, and boolean fields.

Map columns deliberately: price vs compare-at, tracked inventory vs unlimited, and option columns for variants. After import, spot-check a sample of PDPs, collection membership, and search.

# Dry-run mindset
1. Export a small slice from source
2. Import to preview store
3. Diff counts: products, variants, media
4. Only then run production import in a maintenance window

Troubleshooting

Variant missing at checkout: confirm the SKU is active, in stock, and not filtered by a market rule.

Duplicate products after import: check handle/SKU match keys — updates need stable identifiers.

Images broken: ensure import URLs are publicly reachable during ingest or upload files directly.

Best practices

Govern taxonomy with a short vocabulary document. Review top sellers monthly for content quality. Archive discontinued SKUs with redirects instead of deleting URLs that still receive traffic. Keep merchandising and engineering aligned on option naming before peak season.

Prerequisites & preparation

Before changing production settings for catalog management, align the people who own content, DNS, analytics, and approvals. A fifteen-minute kickoff that names owners prevents multi-day Slack archaeology later. Capture decisions in the workspace notes so the next teammate inherits context instead of guesswork.

Gather credentials and access: workspace admin or editor role, DNS control when hostnames are involved, payment or API sandbox accounts when money paths are involved, and a shared checklist link. Confirm which environment you will rehearse in — preview first, production only after a green run.

Define option vocabulary, SKU schemes, and who may import to production. Prepare a preview store for dry runs.

Detailed walkthrough

Work the happy path slowly the first time. Narrate what you expect to see after each click: a status badge, a DNS record, a webhook delivery, a Lighthouse metric. When reality diverges, stop and resolve the mismatch instead of clicking ahead — most outages begin as ignored yellow states.

1. Model a parent product with realistic variant axes you can stock.
2. Create manual and automated collections with non-overlapping purposes.
3. Standardize imagery framing and alt text conventions.
4. Dry-run CSV/API import on preview; diff counts before production.
5. Spot-check PDPs, collections, and search after import.

Edge cases & failure modes

Plan for partial failure. Networks drop, registrars delay, providers rate-limit, and humans approve the wrong revision. Your runbook should say what “abort” looks like: leave preview up, roll back the release, or freeze campaigns until metrics recover.

• Sandbox and live keys crossed between environments.
• Tax inclusive labels disagreeing with checkout math.
• Webhooks delivered twice without idempotent handlers.

QA checklist before you announce

• Happy path verified on mobile and desktop
• Failure path messaging reviewed
• Owners named for the first hour after launch
• Rollback or freeze path documented

Operating the change

After launch, watch the metrics that prove the change worked — not vanity charts. Pair quantitative signals with one qualitative check (support ticket themes, sales feedback). Schedule a follow-up within a week to remove temporary flags, raise DNS TTLs, or archive the experiment.

Review top sellers monthly for content quality; archive discontinued SKUs with redirects.

Stable handles matter for SEO and ads; change titles freely, change handles only with redirects.

Avoid impossible variant matrices you cannot fulfill — separate products when combinations are rare.

Primary image order drives LCP and social cards; treat gallery order as a merchandising decision.

Automated collections that churn membership daily create noisy merchandising and flaky campaigns.

Govern taxonomy with a one-page vocabulary doc that imports must follow.

B2B-only collections should never leak onto public navigation or sitemaps.