The Catalog V3 APIs allow you to manage Wix Stores product catalogs. For an overview of all available services, see Introduction to Catalog V3.
This article contains a comprehensive list of the various terms and concepts used in Catalog V3 and its APIs.
The current selling price of a variant. This is the price customers pay at checkout.
A manufacturer or brand identity associated with a product. Brands are managed through the Brands API and can be assigned to products for organization and filtering.
A hierarchical grouping for organizing products. Categories can be nested up to 5 levels deep and are managed through the Categories API.
A specific value in an option or modifier. For example, "Red" and "Blue" are choices in a "Color" option, and "Small", "Medium", and "Large" are choices in a "Size" option.
The original price of a variant before a discount, displayed with a strikethrough in the storefront.
A reusable entity that defines customer selections for a product. Customizations can be either options or modifiers. Customizations are stored independently and can be assigned to multiple products.
The automatically created location used for inventory items that don't have a specific location assigned. Every store has 1 default location.
For products without options, the single variant with an empty choices array. This default variant holds the product's price, SKU, and other variant-level data.
A 3rd-party app that provides fulfillment services, such as dropshipping or print-on-demand. Fulfillers can define editing restrictions on products they create through the Product Restrictions Service Plugin.
A user-defined unique identifier for a product, useful for cross-platform consistency. Unlike a slug, the handle doesn't change when the product name changes.
A content block displayed on product pages containing detailed information such as shipping details, return policies, or care instructions. Info sections are managed through the Info Sections API.
A record tracking stock for a specific variant at a specific location. The combination of variant ID and location ID is unique. Inventory items are managed through the Inventory Items API.
A physical place configured for inventory management, such as a warehouse, retail store, or fulfillment center.
A customization that collects additional information from customers without creating variants or affecting inventory. For example, a "Gift Message" modifier allows customers to enter custom text. Modifiers can have a price add-on but don't have their own SKU or inventory.
A customization that creates variants. Each combination of option choices creates a separate variant with its own price, SKU, and inventory. For example, a "Size" option with choices "Small", "Medium", and "Large" creates 3 variants.
A status indicating that an inventory item can be ordered before it's in stock, with shipments occurring once inventory becomes available.
An item in a store, which can be physical or digital. Every product has at least 1 variant. Products are managed through the Products API.
How a customization is displayed to customers. Available render types include:
A badge that highlights specific product features or promotions, such as "Sale", "New", or "Bestseller". Ribbons are managed through the Ribbons API.
An auto-generated URL-friendly identifier for a product, derived from the product name. The slug is used in the product's URL path. Unlike a handle, the slug updates when the product name changes.
Specifies how an inventory item tracks availability. The item can either track the current quantity left in inventory or simply indicate availability status (IN_STOCK or OUT_OF_STOCK) without quantity tracking.
A specific purchasable version of a product. Every product has at least 1 variant. Products with options have 1 variant for each combination of option choices. Each variant can have its own price, SKU, barcode, weight, and inventory status.