Skip to main content

Create Catalog

POST 

/api/admin/portal/catalogs

Create a catalog.

Required scope: customers:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

order_discount_tiers_json (array, nullable, optional): this catalog's own order-value ladder, e.g. [{"min_subtotal": 5000, "percent": 16.67}]. Same rules as an account ladder (at most 10 tiers, distinct thresholds, rising percentages, else 422). Stored sorted by threshold; null or [] = none. An account can override it per catalog — see Update Account Settings.

Per-catalog order-value discounts. A catalog's ladder counts ONLY the cart lines attributed to that catalog and its percentage comes off those lines only; net-priced products (portal_exclude_from_order_discount) count toward the threshold but are not discounted. Each cart line is attributed to ONE of the account's catalogs: a catalog that names the product in an include_product rule beats one that reaches it by brand/category (or includes everything), then the lowest catalog id wins. The account-level ladder (order_discount_tiers_json) still measures the WHOLE cart, but only discounts lines no catalog ladder governs — a line never takes two order-value discounts.

Pre-order pricing (2026-10-13). preorder_discount_tiers_json (array, nullable): the catalog's PRE-ORDER ladder, same shape and rules as order_discount_tiers_json; null or [] = no pre-order pricing. Used instead of the in-stock ladder when a buyer's cart is in pre-order mode (laid over it, so below the pre-order step the in-stock step still applies). preorder_lead_time_days / preorder_lead_time_max_days (integer 0–3650, nullable): the ship window buyers are promised (90 + 180 reads "~3–6 months"; max below min → 422). preorder_note (string ≤500, nullable): a short buyer-facing line. The response adds preorder_lead_time_label.

Request​

Responses​

Created

Response Headers
    Content-Type