Clone Cart API Performance Optimization

Digital Commerce and DSR now optimize Clone Cart API calls by passing price=false to avoid redundant pricing calculations during cart cloning. This reduces backend processing and improves API response times. Pricing is still applied when the cloned cart is opened or activated, and cloned carts retain all line items and display correct totals after activation.

For more information, see Clone Cart API in Conga Developer Portal.

External Digital Sales Room User Authentication and Access

External buyers accessing a shared Digital Sales Room (DSR) link are routed to a dedicated login page instead of the internal application login. After authentication, access is limited to the Digital Sales Rooms and features shared with them. Invalid or expired links display a clear message and deny access.

For more information, see Initiating Quote Collaboration – Sales Representative.

Digital Sales Room as a Default Storefront

A Digital Sales Room (DSR) storefront provides a separate storefront for managing DSR branding and settings independently from other application storefronts.

When a quote is shared with an authenticated buyer, the DSR storefront is identified in the shared link. For anonymous access, the application name is used in the link.

For more information, see Sharing a Quote with a Buyer in CPQ and Digital Sales Room and its child pages in Digital Commerce.

Storefront Display Column and Action Configuration For E-Commerce and DSR

Administrators can now configure display columns and action buttons for E-Commerce and Digital Sales Room (DSR) storefronts through Storefront Settings. Display column controls the fields shown in list pages, summary cards, line-item grids, and price rows. Administrators can configure field selection, including lookup paths for list and summary sections, custom headings, column order, formatting, sorting, record links, quick views, alternate display values, inline editing, and guest visibility. Display Action controls the action buttons on Quote and Cart detail pages, including action labels, order, placement, styling, and visibility based on user type, record stage, and, for DSR, collaboration state.

Changes take effect on the next page load without requiring a deployment. For guest users, configure the /api/revenue-admin/v1/flows/{flowname}/settings/{settingname}/{childsettingname} endpoint with the GET method in the allowed routes to enable this feature.

For more information, see Editing Storefront Setting in CPQ for Administrators and Retrieve custom settings associated with a flow API.