Oracle CX Commerce 20A New Feature Summary

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Search Admin

Dynamic Content

Dynamic Content allows merchants to display relevant content based on shopper behavior – specifically, via navigation location and search – allowing merchants to capture and focus the shopper’s attention, convey a message specific to shopper intent, and direct the shopper to a desired location.

Capability highlights:

Display an image from the Media Library along with the product listing when the shopper enters specific search terms or navigates to a specific collection page.
Display promotional images targeted to specific searches or collections.
Make the image a clickable link taking the shopper to a relevant landing page.
Preview the results of your rule.

To use the feature, two key steps must be completed. One is to create a Dynamic Content rule. The other is to create a custom widget to display the content and place the widget on the Search Results and/or Collection layouts – including the Agent layout.

Site-Specific Rules

New in Search Administration is the ability to create site-specific rules. A Dynamic Curation, Facet Ordering, or Dynamic Content rule can be defined for one or more specific sites. This feature allows the merchant to tailor the results for a given search term or collection to meet different requirements on different sites.

A merchant can define a rule for all destinations on a specific site. This rule is essentially a default rule for the site. The default is for a rule to apply globally (on all sites). When you upgrade, all existing rules will continue to be global, unless and until you change them.

The key benefit of this feature is that it allows merchants to refine their product listings to support the business goals of specific sites. The feature addresses situations where, for example, different sites have different sales goals, marketing approaches, or target audiences.

Catalog

Price Group Inheritance

Merchants can now define specific prices for particular products and SKUs, while the rest of the prices are inherited from its parent price list group. This allows them to define the relationship between price list groups and customer-specific prices at the child price list level, as well as define price list groups that are applicable for a specific purpose (e.g. pricing for select promotional products, special pricing for a particular customer or multiple accounts). Not only does this provide increased flexibility and targeting, but it helps improve maintenance and management of price list groups.

With release of the Price Group Inheritance feature, changes can be done directly in the new price group, resulting in faster pricing calls, faster publishing and search, and improved performance.

This feature is applicable for both consumer-based (B2C) and account-based environments (B2B).

Update 20A Week 11

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
30 APR 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Loyalty

Pay an Order with Points and Currency (API Only)

With the latest release, merchants using our generic loyalty framework may now offer product redemption in loyalty points (points as a pricelist group) with payment for the full order in points or a mix of points and monetary currency. This allows shoppers to pay in a mix of loyalty points and currency or monetary currency by itself, so that they do not have to limit what they buy based solely on their available points. Loyalty shopper cards can also now be used.

Merchants may launch a separate site to offer products to be sold in points only, with taxes and shipping payment separated by points or currency. The feature enables integration with payment gateways and loyalty engines in parallel.

NOTE: Products cannot be offered in a mix of points and currency. The price list is still in one currency. Integration with a loyalty engine is required. This is an API only feature with no out-of-the-box widgets included.

Integrations

Cancel In-Flight Order

With this release, CX Commerce provides functionality that allows the shoppers to initiate cancellations, returns, or exchanges on orders placed through their account. This feature builds on the previously introduced concept of cancel in-flight, the process of cancelling an order after it has been submitted to fulfilment.

Capability Highlights:

Cancels orders when items have passed the ‘point of no return’ in fulfillment.
Automatically generates return requests and service terminations.
Executes cancel/return/terminate as required for each element of a configured item.

In the Admin settings, merchants can enable Extended Remorse Period specifying the number of days from the date of submission during which orders can be cancelled. Unlike the Remorse Period implementation there will be no delay in the order process and orders will be sent to fulfillment immediately on submission

NOTE: To implement this feature merchants will be required to download and install a few new and updated Server-Side Extensions; and also required to build a new Order Details Cancel widget or, if using the current cancel in-flight feature, update their Order Details Cancel widget.

Shipping Group Assignment

With this release, when a shopper purchases a non-shippable item such as a download or warranty, the item will now automatically be assigned to a virtual shipping group thereby ensuring no shipping charges are applied to the purchase at checkout time.

This new feature provides for a flexible structure for selling services, allowing merchants to decide how and when shoppers pay for shipping for physical items.

The ability to assign items to the virtual shipping group and assign each item in a configuration hierarchy to a shipping group enables CX Commerce to implement the new ‘Cancel In-flight Order’ feature.

Adjustments to tax calculation and shipping charge calculations work out-of-the-box.

To implement the assignment of shipping groups at the sub item level, customers will be required to build their own ‘Shipping Options Sub-Item Widget.’

Update 20A Week 10

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
20 APR 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Integrations

Calculate Tax Refunds Based on Date of Original Order

Tax refund amounts can now be calculated more accurately based on the actual tax rate charged for an item. The date of the original order can be used to calculate tax refunds for returns and exchanges. This ensures that the tax refund amount corresponds to the actual tax amount charged instead of a potentially different current rate.

A new merchant setting – useOrderSubmittedDateForTax – has been introduced to control this behavior.

The setting is enabled for new customer implementations and disabled by default for existing customers.
The setting applies to all sites.
The setting can be updated using the Admin merchantSettings endpoint.
The setting affects tax calculation for out-of-the-box Avalara and Vertex integrations, as well as custom tax integrations implemented using the External Tax Webhook.

Update 20A Week 9

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
10 APR 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Audiences

Behavorial Audiences: Current Session Page Views

With this release, powerful new Behavioral Audience rules can now be used to drive improved personalized experiences for shoppers. Merchants can build audience rules based on a shopper’s current session page views to collection or product pages and combine those with other criteria. This is useful for providing a more contextual experience for shoppers in terms of the content, promotions, and tests they see, as well as contributing to driving increased conversions and sales.

We currently support product and collection page views from a shopper’s current session and specifically the following behavioral audience types:

Collection name (e.g. Collection name contains “Men's”)
Product name (e.g. Product Name starts with “Running”)
Collection page (e.g. Collection is “Accessories”)
Product page (e.g. Product is “Trail Men's Running Shorts”)
Product criteria (e.g. x products in “[camera brand name]”, “Cameras” collection, and “Camera” product type)

Update 20A Week 8

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
03 APR 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Wish Lists

Support for /ccstore Context Root

Previously, wish lists only supported /ccstoreui API. We now support /ccstore context root, particularly useful for implementing CX Commerce wish lists using a headless approach where our out-of-the-box Storefront is not the client. When a JWT token created by the /ccstore REST API is sent to the wish list (SWM) server, verification will be successful.

Update 20A Week 4

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
11 MAR 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Extensibility

Item Back in Stock Event Webhook

Back in stock notifications were previously available, but now, merchants can leverage our new Item Back in Stock event webhook to customize their website when notifying shoppers that an item they are interested in has come back into stock. This webhook allows the back in stock notification to be sent by an external system.

To implement this feature, merchants can notify shoppers when items are back in stock by:

Customizing the storefront to allow shoppers to choose “notify me when this item comes back into stock”.
Tracking the list of subscriptions externally.
Listening for the Item Back in Stock event webhook.
Implementing a service to notify subscribed shoppers when their item of interest is back in stock.

The new webhook can be enabled in the Oracle CX Commerce Admin and the end to end process developed as a customization.

NOTE: This feature provides the webhook only, so that a back in stock notification can be sent by an external system. Does not include the user experience for shoppers to opt in to notifications, ability to track the list of shopper subscriptions, or the ability to send the email itself.

Update 20A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Feature	Notes
11 FEB 2020		Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update.

DISCLAIMER

Payments

Additional Properties for Payment Webhook Requests

Additional properties are now included in payment webhook requests. This helps with improved robustness of integrated payment fraud solutions and enhanced capability in support of the Payment Service Directive 2 (PSD 2).

The Credit Card Payment and Generic Payment webhook requests have been extended to include:

Full order, including item numbers, item descriptions, quantities, prices, currency, custom properties
Shopper information, including shopper profile properties, such as custom profile properties, shopper authentication method, registration date, modification date, password change date

This feature is enabled using a new payment gateway extension property. The ability to include the full order is enabled by setting the flag on the payment extension. Upload the modified payment extension for the change to take effect.

NOTE: Enable this option only if you need the additional information, as it increases the size of the payload and could affect performance.

Reporting

Near Real-Time Dashboard

The reporting homepage is now based upon data updated in near real time, enabling merchants to:

Review key sales and traffic figures from the last twenty four hours, broken down by hour
Review product and promotion sales performance from the last twenty four hours
Refresh the data for the homepage report from a settings menu option

Integrations

Telco/Services: Direct Configuration (Bypass Iframe) API Only

Shoppers can now configure complex customizable products seamlessly in Oracle CX Commerce without being redirected to an Oracle CPQ hosted iframe.

For Oracle CX Commerce customers using Oracle CPQ and selling configurable products, this new feature allows merchants to implement a direct API configuration using new Storefront and Agent endpoints and removes the need to include an iframe in the shopper flow, thereby improving the overall user experience.

Telco/Services: Upgrade Assets

For Oracle CX Commerce customers using Oracle CPQ (or another asset master system), merchants can now define and display all of the available upgrade options for any existing service.

Shoppers can take advantage of the upgrade and check out, as well as be alerted to and prompted about upgrades as soon as they are available. Upgrades can be pushed out to customers right away and the upgraded asset is ready to be added to the cart with a single click.

Telco/Services: Direct Configuration (Bypass iFrame) Asset Operations (API Only)

For Oracle CX Commerce customers using Oracle CPQ and selling configurable products, we’ve made available new Storefront and Agent endpoints that enable asset modifications and upgrades — modification or upgrades to a shopper’s current service — via direct calls to Oracle CPQ, removing the need to include an iFrame in the shopper experience. This feature is limited to API support and customers need to build their own UI elements to invoke the new endpoints.

We previously released the ability to create ‘Configure’ and ‘Reconfigure’ UI elements and bypass using iFrame. This feature takes the next step by allowing the ability to create ‘Modify’ and ‘Upgrade’ UI elements as well, so merchants can deliver seamless and consistent user experience even when allowing shoppers to modify or upgrade complex products or services. The Configuration UI experience is derived from existing themes and styles. And merchants can customize the UI experience by adding their own UI controls.

Catalog

Catalog Export – Improved Filtering

The filter on the catalog export dialog has been replaced with a new and improved rule builder enabling users to export a specific set of products quickly using custom rules. This allows merchants to work on a more targeted set of catalog items in export. It provides a number of new capabilities, including:

Ability to filter products and SKUs being exported by all base properties, including any dynamic properties of the base type
Ability to create single/multiple rules which are grouped together with ("AND"/ "OR" ) also known as ("ALL"/ "ANY")
Ability to find and return products based on additional properties, including parent collections (parentCategories), ancestory collections (ancestorCategories) and creation date (creationDate)
Ability to find and export recently added items, as well as export based on specific or missing values, such as being able to find products with no product images.

Dynamic Properties on Collections (API Only)

Merchants can now define collection-specific data by extending collection attributes to include dynamic properties. They can create the following dynamic property types via API:

Checkbox (boolean)
Date
Number
Rich Text
Short Text
Long Text

Merchants can view and update these dynamic property values in the collection editor in the Catalog section of the Admin UI once they have been populated via API. API supports ability to create and update dynamic properties on collections. Dynamic properties can be used individually or in combination and enable the ability to drive a number of merchandising enhancements.

Inventory

Search for a SKU Within Inventory

Merchants can now search for SKUs within catalog Inventory based on product name and/or SKU ID. Searching enables merchandisers to find a specific SKU quickly, so that they can view the current state of a SKU and check its accuracy, as well as modify the inventory level if necessary. (Just double-click on the inventory count or stock threshold fields to update inventory values.)

Storefront

Shopper Profile Registration Completion with Secure Email Link

We’re now including an optional new shopper registration flow that makes the account registration process even more secure and helps avoid malicious profile registrations. It applies to both individual Storefront shopper profile registrations and creation of new B2B users and organizations as well. In this new flow, rather than the shopper creating a password during registration, the shopper fills in his/her name and email and submits a registration request which triggers a secure tokenized reset password link. The shopper than needs to click on that link, enter a password, and complete account registration.

When this flow is enabled, shoppers will no longer automatically be logged in after registration, as the shopper must complete the registration via email and then actively log in.

NOTE: To comply with security requirements, this feature is enabled by default for new customers. To ensure backwards compatibility, feature is *not* enabled for existing customers. Merchants have the option to enable/disable as desired.