Glossary

Catalog, taxonomy, import and publishing terms as this documentation uses them.

Terms as this documentation uses them.

Catalog

• SKU — your identifier for a stocked item. The join key for everything: imports, price and stock updates and marketplace sync all match on it.
• Platform Product — one record per SKU for your account, holding stock and the marketplace ids that SKU already has. See Platform Product vs Product.
• Product — one record per SKU per marketplace and country: that channel's content, category and sync state.
• Variant — a child of a parent product, expressed in a feed via parent-sku and parentage.

Taxonomy

• Product type — a node in a marketplace's taxonomy. Decides which fields a listing must carry.
• Product type version — that product type's field list as at one taxonomy import. See Product types and taxonomy versions.
• Category folder — one of your own categories. Organisational; never sent to a marketplace.

Import

• Feed — a file or endpoint MarketplaceHub reads products from. CSV or JSON. See Feeds and formats.
• Base file — in a multi-file import, the file with one row per product. Others link to it. See Linking several files.
• Journey — one configured import: its source, mapping, filters and schedule. Re-running a journey re-fetches rather than re-uploads.
• Skip rule — a condition that drops a row before it becomes a product. See Filtering rows.

Publishing

• Connection — an authorised link to one marketplace account. Can be a source, a publishing target, or both. See Marketplace integrations.
• Publish — sending reviewed products to a marketplace. Creates a listing, or revises the existing one when the SKU already carries an id for that marketplace.
• Master store — a connected store treated as the source of truth for price and stock, propagated outward to your other channels.