Product Limits

ObjectLimit B2B and D2C Except Where IndicatedStore or OrgNotes
Products3 millionStoreApplies to B2B and D2C stores. Products in Commerce rely on standard core entities shared across Sales, Service, and other clouds. Contact your account representative when you need more than a million SKUs to be uploaded to your store. If you work with a third-party search provider, for example, Coveo, Algolia, or Bloomreach, the 3 million limit doesn’t apply
Variation Parent Products500,000StoreThis is specific to parent products. It does not include the child products.
Variation Products3 millionStoreIncludes the variation parent and child products
Variants per Parent200Store
Attributes per Variation5N/AApplies to Product variations and sets
Products per entitlement policy3 millionN/AD2C: Only one entitlement policy is supported
Products per Product Category100,000N/AD2C: This can be increased based on the holistic use of data limits.
Products per Catalog3 millionStore
Images per Product9N/AYou can also add up to 5 file attachments per product.
Total Custom Attributes700 per productN/A
Product Categories per Store15,000N/AThe total number of top-level and subcategories in a product catalog.
Product Subcategories per Category200N/AThe number of subcategories for each top-level category.
Top-Level Categories200N/AThe number of top-level categories.
Category Depth (Levels)5N/AThe number of levels in a category hierarchy.

Best Practice

Salesforce recommends you keep product data within the scope of the established limits. If you have requirements that exceed the limits, consider how the increase impacts other data limits across your stores and org. For example, you’re adding new product lines to your store and want to increase the total number of products to 3.5 million. Before requesting the increase from Support, assess the impact the increase has on related data limits. For each additional product, consider the additional data the product generates.

Configure product categories to enhance customer navigation and hierarchy optimization.

  • Keep the category hierarchy as simple as possible while still meeting your business needs.
  • Avoid overly deep or complex hierarchies that can impact performance and make maintenance challenging.
  • Focus on critical fields and attributes that impact product categorization and customer navigation.

If you have requirements that exceed the limits, consider the impact on performance and data limits.

  • Does the additional data push the related data objects beyond their limits?
  • Can you offset a data increase in data volume by decreasing data requirements in other store functions?

After you assess the impact of a data increase, if you still want to request an increase, contact Support.