Sales catalog

Purpose

Use a Sales Catalog to turn selected products into company offers. Product data remains on the Product; Catalog Products adds a sellable package, price, ordering rules, stock, Google Merchant preflight, and XML export.

Who uses it

Catalog Managers maintain the assortment. Company Administrators and Integration Managers manage offers, stock, and exports when their permissions and plan allow it.

When to use it

Use a Sales Catalog when products need prices and channel-ready availability. Use Showcase or Exhibition Catalogs for non-commercial presentation instead.

Prerequisites

Before creating an offer:

  1. Add the Product to the Catalog assortment.
  2. Open the Product's Product Packs tab and confirm that the automatic base Product Pack and any inherited or Product-specific orderable packs are available.
  3. Use Add or manage Product Packs when this Product needs another sellable quantity. Choose a reusable Application/Company Package and save 1, 10, and 100 pieces as separate Product Packs; the automatic one-unit base Product Pack is always available.
  4. Confirm that the selected Product Pack resolves the logistics values required by the destination. Use a Package, explicit packed values, or the Category Logistics Shape Profile instead of guessing shipping measurements.

Page controls or fields

  • Product Pack selects the exact trade or order unit, such as each, box, reel, case, or pallet.
  • Price / currency is the price of one selected Product Pack.
  • Minimum order (packs) is the smallest accepted order; Order step (packs) is the quantity interval allowed after it.
  • Availability selects From available stock or Made to order for this offer. One Sales Catalog may contain both kinds.
  • On hand is the physical exact-pack stock; Reserved is already committed stock; Available is calculated as On hand minus Reserved.
  • Ready to ship in records preparation time in days. It is required for Made to order and optional for stock.
  • Available for sale publishes or withdraws this Product Pack offer without deleting its saved terms.
  • Merchant-created multipack is an advanced Google-only option. Select it only when the merchant groups identical manufacturer units; do not select it for a manufacturer-defined box or case.
  • Run preflight reports blocking Google Merchant issues per offer before queueing.
  • Generate Google feed queues a private Google Merchant XML artifact through Data Export after preflight passes.

Step-by-step usage

  1. Open a Sales Catalog and select Products.
  2. Find the Product through the existing search and filters, then select its Edit commercial offer tag icon.
  3. Each orderable package opens as a separate row. Enable only the packages offered by this Catalog.
  4. Enter the price, select a currency from the currency directory, and enter the minimum order and order step for that pack.
  5. Choose From available stock and enter On hand/Reserved quantities, or choose Made to order and enter the preparation time.
  6. Save with the row action and confirm the offer status changes from Not saved to Active.
  7. Run Google Merchant preflight and correct every item-level blocker.
  8. Select Generate Google feed to queue XML; open Company Workspace -> Data Integration -> Exports to review and download the result.

Business rules

One Product may have several Product Packs and several offers in the same Sales Catalog. Stock belongs to Company + Product Pack and can be reused by other catalogs. It is never inherited from another pack automatically. Made-to-order offers do not create fake stock; their minimum order, order step, and preparation time remain commercial terms of that catalog offer.

Not every destination supports every supply mode. Connector preflight must report an incompatible offer before export instead of changing its meaning.

Google export requires Product title, description, landing page, primary image, price, currency, availability, one Google taxonomy code, and a GTIN. It uses the selected package's GTIN first; only a base consumer unit may fall back to the Product GTIN. Multiple taxonomy codes or multiple different GTIN/MPN values are treated as ambiguity, not resolved by choosing the first value. Marketplace logistics checks use resolved Product Pack values and the destination's channel requirements.

Common mistakes

Do not enter box stock against an each-level pack, and do not use a Product Variant to represent packaging alone. Do not expect the current one-time XML export to be a scheduled public feed; Channel Profiles, feed URLs, and direct Google delivery are later steps.