A practical guide to getting work done in your product catalog.

Start with the product categories your team uses to browse and organize its assortment. Define the attributes that describe each product and group related fields so they are easier to work with.

When product types need different data, assign the relevant attribute definitions to attribute families. This gives product editors a consistent schema without forcing every item into an identical set of fields.

Open the product import workflow and select a supported file. Review the previewed columns, choose or create a mapping, and check that a source column maps to the product identifier your workspace expects.

Save a mapping profile if the same source format will be used again. Resolve unmapped fields and validation notices before starting the import. Track batch progress, created or updated records, and failures in the job or import status view.

Search the catalog, open a product, and update the fields your team maintains: titles, descriptions, attributes, images, categories, or language-specific content. For work across several records, use the supported bulk actions.

AI-assisted bulk editing provides a change preview. Review affected products, sample before-and-after values, warnings, and the selected language before confirming. The edit is queued for background processing; wait for its job status rather than assuming it finished immediately.

Use the product completeness details to find which configured criteria are fulfilled and which data is missing. A displayed estimate is marked as estimated; open the detail view for criterion-level context and configuration messages.

Publication readiness is a separate check. Review the current status and blocking reasons instead of treating a completeness percentage as a guarantee that a product will be published. Readiness depends on the data and rules configured for that product.

Imports, bulk edits, and other long-running operations may be processed as jobs. Use the workspace job and integration status screens to review progress and investigate failures; do not assume that a queued task has already finished.

For external feeds, confirm which integrations and destinations are configured for your workspace, then review the listing or feed history available in the product. Platform support and publication behavior depend on the installed connector and its configuration.