Partner Commerce for Advantage Platform Oct '26 Release Notes
In these release notes, you can find new features and fixed and known issues for the Partner Commerce Oct '26 release. For documentation updates, see What's New in Partner Commerce Documentation.
This documentation may describe optional features for which you have not purchased a license; therefore your solution or implementation may differ from what is described here. Contact your customer success manager (CSM) or account executive (AE) to discuss your specific features and licensing.
For training resources and feature overviews, visit the Conga Learning Center on Conga Community.
New Features
The following features are new to Partner Commerce in this release.
Standardized Bill-To and Ship-To Address Management for External User
This update standardizes the handling of Bill-To and Ship-To addresses for external users across the storefront, quotes, and orders. Only accounts linked to the user's contact are available for selection in the Bill-To and Ship-To dropdowns. These fields are read-only on quote and order detail pages, and the Primary Contact field remains read-only, always reflecting the logged-in user. Guest users and internal users continue to use the storefront's default account mapping for Bill-To and Ship-To selections.
Administrators can create new accounts and locations directly from the Bill-To and Ship-To selection flow. Newly created locations are saved to the account for reuse in future quotes and orders. The Shipping Location field is now available and editable in quotes and orders, allowing selection and viewing of the location address, while Bill-To and Ship-To remain read-only.
The Cart API V1 now accepts additional fields, such as the Location field, in the quote creation request payload using the POST /api/cart/v1/carts/{cartId}/quote endpoint. All fields included in the request payload are stored in the quote object, and the QuoteOverrideAllowedFields setting can be configured to specify which fields can be overridden during quote creation.
These changes do not impact guest user account mappings.
For more information, see Cart APIs in Conga Developer Portal.
Line-Level Tax Data Model Extension and Storefront Display for Quotes and Orders
The platform now extends the data model to persist line-level tax details, including Tax Amount, Tax Rate, Tax Code, Taxable Amount, and Tax Inclusive Flag, on Quote Line Item and Order Line Item entities. Cart-to-Quote and Cart-to-Order conversions populate these fields, which are also available through Quote and Order GET API responses. Quote and Order headers provide a Total Tax Amount field that represents the sum of all line-level tax amounts, supporting downstream processes such as document generation, integrations, and reporting.
Partner Commerce storefronts now display the Tax Amount for each line item on Quote and Order detail pages for both buyers and partners. The application displays the tax field below the Extended Price for each line item and includes a Tax row in the Price Summary section for the total tax. An information icon beside the price field provides access to a detailed tax breakdown at the line level. These features support both logged-in and guest users, with all tax values reflecting storefront currency and locale settings. A $0.00 value appears when tax is zero or not applicable for consistent display.
Edit Order and Edit Quote modes support tax recalculation after product, quantity, or pricing changes. The Calculate Tax button updates tax values after modifications. Existing tax values remain unchanged during editing until an explicit recalculation occurs. Warning messages appear when item changes may affect taxes, while recalculation remains optional during editing.
Quotes and Orders created without tax data continue to function as before, with tax fields defaulting to zero or null. Existing Cart, Quote, and Order flows remain unaffected by these changes.
For more information in Partner Commerce, see Recalculating Tax for Order and Recalculating Tax for Quote.
Extensibility Configuration for Display Columns and Actions in Digital Commerce
- Storefront Display Column and Action Configuration in Digital 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 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, 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.
- Configure Field and Action Layouts via JSON Editor in Storefront Settings: Administrators can now configure field and action visibility for Digital Commerce storefront pages using the Set up Field Layouts and Actions entry in Storefront Settings. The built-in JSON editor provides syntax highlighting, formatting, real-time validation, and error messages, and allows administrators to load a default template or existing storefront configuration.For more information, see Editing Storefront Setting.
Admin UI and CPQ API Integration Configuration for Payment and Tax
The Integration > Others tab in the Admin Console enables administrators to configure and manage Payment and Tax integrations using CPQ APIs. Administrators can view, edit, and test integration configurations with JSON-based editing, connection validation, and standardized error handling. Sensitive credentials are securely managed through secret management and field masking, ensuring credentials remain protected and are not exposed in the UI.
CPQ APIs now support integration with the platform's generic integration configuration and secret-management solution. Administrators can securely create, update, retrieve, and validate integration configurations for Payment and Tax use cases. These APIs abstract provider-specific details, restrict access to administrators, and prevent exposure of secrets in responses, supporting Digital Commerce UI consumption.
For Partner Commerce, see Configuring Avalara Tax Integration Using the Endpoint Configuration API and Viewing and Managing Avalara in the Admin UI.
DOC ID: PCRLPOCT26.20261005