Catalog
Product model and detail tabs
Understand products, variants, attributes, assets, relations, and the product detail workspace.
For workspace users and administrators · Updated October 1, 2026
What this module is for
Understand products, variants, attributes, assets, relations, and the product detail workspace.
Use this page when you need to complete the task yourself and understand what each action changes. The steps name the relevant screen, explain why the action belongs in the workflow, and state what to verify before moving on.
Before you start
- Sign in with a role that can view or change the records in this guide.
- Have the product, file, channel, or workspace information ready before starting an action that saves data.
- Use a small test record or file first when an action affects multiple products or a connected channel.
1. Choose the structure
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 1.1
Do this: Use categories for navigation, product families for a shared schema, and attributes for individual fields.
Why this matters: This keeps the choose the structure work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 1.2
Do this: Create a product for the shared record, then add sellable variants where SKU-level data differs.
Why this matters: This keeps the choose the structure work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 1.3
Do this: Attach assets, prices, and related records before publishing to a channel.
Why this matters: This keeps the choose the structure work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
2. Details, attributes, and media
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 2.1
Do this: Use Details for the core record. Save or discard edits before switching tabs when the unsaved-changes prompt appears.
Why this matters: This keeps the details, attributes, and media work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 2.2
Do this: Use Attributes to edit typed field values; if no attribute set is selected, assign a suitable family or attribute set first.
Why this matters: This keeps the details, attributes, and media work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 2.3
Do this: Use Media to add from the library or browse files, then confirm the selected image appears on the product.
Why this matters: This keeps the details, attributes, and media work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
3. Variants, bundles, and relations
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 3.1
Do this: Use Variants for a configurable product; the tab only renders the variant editor for that product type.
Why this matters: This keeps the variants, bundles, and relations work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 3.2
Do this: Use Bundles for a bundle product and check its component records.
Why this matters: This keeps the variants, bundles, and relations work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 3.3
Do this: Use Relations to search for another product and create a link between the records.
Why this matters: This keeps the variants, bundles, and relations work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
4. Publishing, quality, SEO, and DPP
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 4.1
Do this: Use Channels & Publishing to inspect the product’s channel readiness, publication state, and schedule.
Why this matters: This keeps the publishing, quality, seo, and dpp work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 4.2
Do this: Use Quality for its score and recent issues, then fix the underlying fields before refreshing.
Why this matters: This keeps the publishing, quality, seo, and dpp work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 4.3
Do this: Use SEO for metadata, hreflang, link intelligence, experiments, and audit actions; use Digital Product Passport to inspect versions, public access, and the QR download.
Why this matters: This keeps the publishing, quality, seo, and dpp work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
5. Workflow and history
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 5.1
Do this: Use Workflow & Tasks to review current status, assigned tasks, and available approval or rejection actions.
Why this matters: This keeps the workflow and history work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 5.2
Do this: Use Versions to inspect previous snapshots, and AI history to audit enrichment activity.
Why this matters: This keeps the workflow and history work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 5.3
Do this: Check Relations again after a linked product changes.
Why this matters: This keeps the workflow and history work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
6. Check the result
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 6.1
Do this: Resolve validation issues before export or publication.
Why this matters: This keeps the check the result work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 6.2
Do this: Use Export Product Sheet on the detail page when you need a single-product handoff.
Why this matters: This keeps the check the result work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
Events and statuses to watch
Actions such as saving, importing, exporting, connecting, publishing, and approving can either update a record immediately or create background work. Wait for the on-screen confirmation and then check the relevant list, detail view, or job status before repeating an action.
- Saved or created: confirm the record appears with the intended values.
- Queued, running, or processing: wait for completion and open the job or event detail if progress stops.
- Failed, partial, rejected, or blocked: read the specific message, correct the source data or permissions, then retry only the affected work.