Integrating CPQ

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read
  • Learn how CPQ connects with downstream systems and UI frameworks—visualization engines (CDS, kBridge, Threekit), eCommerce storefronts (Shopify, headless), and Salesforce (CPQ, B2B Commerce, Base Package)—to deliver real-time, guided configuration, pricing, and ordering at scale.

    With integrations, you can:

    • Visualize configurations in real time using 2D/3D viewers (CDS, kBridge, Threekit).
    • Transact in your commerce stack via Shopify or headless storefronts with draft orders or add-to-cart flows.
    • Sell through Salesforce with CPQ/B2B Commerce, launch the CPQ Configurator from Product2, and persist configuration data to Salesforce objects for quoting and amendments.

    Integration categories at a glance

    Table 1. Integration categories
    Category Primary purpose Where it’s configured Typical data flow
    Visualization (CDS, kBridge, Threekit) Show 2D/3D product visuals that react to user selections Blueprint → Layout (CSV/Editor) CPQ fields/sets → viewer (1-way); optional viewer → CPQ (2-way)
    eCommerce (Shopify, Headless) Embed configurator on product/content pages; create carts or draft orders Shopify app + CPQ runtime client Storefront → CPQ → cart/draft order
    Salesforce (Base, CPQ, B2B Commerce) Launch/configure from Product2, write BOM/field data, amendments Salesforce package + CPQ Settings Quote/Cart ↔ CPQ runtime; optional persistence to CLI/CFD
    Limits and behaviors (visualization):
    • Sets and product pickers: up to 25 indices/options sent to the viewer
    • Active set index: can be published to the viewer when using set repeaters
    • Two-way sync: supported for CDS and kBridge (fields; sets require a listener field + parsing rule)
    • Threekit supports one-way from CPQ; pair with set repeater guidance where applicable