This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 06 APR 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Shipping Method Update - External ID Property (API only)
With this new enhancement, you can now store an ID generated from a third-party shipping system allowing you to map shipping methods easily across systems.
Capability highlights
- Allows users to store the ID from an external shipping system on a Commerce shipping method.
- External ID is included in the shipping method information in the external shipping webhook and added to docShippingAdminEndpoints swagger.
Shipping Method Update - Internal Name Property (API only)
The internal ID enhancement allows merchants to have multiple shipping methods with the same display name for shoppers and identify them internally when managing promotions.
Capability highlights
- Users can create multiple shipping methods with the same display name on the storefront to be used in different contexts.
- When creating shipping promotions, a user can easily differentiate shipping methods even though they have the same external display name.
- Internal names are automatically displayed in the Shipping Method editor in Shipping Discount promotions editor.
Wish List Support in Open Storefront Framework
With this release, Commerce customers using Open Storefront Framework (OSF) can more easily implement wish list functionality similar to what is available in Storefront Classic. They now have access to out-of-the-box wish list widgets to create and manage multiple wish lists, add, edit, and delete wish list items, move products from one wish list to another, and add to cart from any wish list. You can invite friends to be a part of a wish list, make comments on items in a wish list, and share products and gift ideas.
The OSF wish list widgets make use of the Commerce wish list service and interface with the corresponding Social Wish List APIs.
Capability highlights
Wish list features in OSF include the ability to:
- Create, edit, and delete wish lists with different privacy settings (Private, Shared, or Group).
- Add items from the product detail page to a new or existing wish list.
- Move items from a wish list to the cart or from the cart to a wish list.
- Move items from one wish list to another.
- Edit or delete wish list items.
- Add comments to wish list items.
- Share wish lists with your family and friends and invite friends to a wish list.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 24 MAR 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Improved Server-Side Extension Logger Access & Terminology Updates
With this Commerce revision, we’ve introduced an enhancement to server-side extension (SSE) logger access, in addition to a terminology change in the SSE “package.json” file.
The logger access update provides easier access to the framework-supplied logger. When writing new code or updating an existing SSE, use the new variable “global.occ.logger”.
Capability Highlights
- The built-in logger integrates properly with the SSE log retrieval APIs.
- No change has been made to the logging APIs. The change is in how to access the logger.
Terminology Change
In an effort to modernize and clarify terms used in Oracle products and services, “whitelistUrls” in the SSE “package.json” file, has been replaced by “allowedUrls”. This name is clear and directly relates to the URLs allowed to be called by server-side extensions.
Headless Personalization APIs (API only)
This Commerce update introduces new APIs that allow headless applications to establish a visit context for each shopper when evaluating audience membership. These APIs allow merchants to use the full range of personalization audiences when building, for example, native OS or custom web applications, voice assistants, social commerce plug-ins, and chatbots.
Capability Highlights
- Your headless application can now use audiences based on visit characteristics, such as entry page, UTM parameters, and geolocation.
- Developers now have easy-to-use tools to assist in instrumenting a headless integration to support Audiences.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 17 MAR 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
This Commerce update provides enhancements that allow you to control a business user’s access to specific catalogs and price groups. This can help you prevent unauthorized updates of products and prices.
With this release, we’re providing API support for creating security criteria for catalogs and price groups, and for adding privileges and security criteria to roles.
Capability highlights:
- Create security criteria for catalogs and price groups (via API).
- Add privileges and security criteria to roles (via API).
- View the contents of roles in a new User Management UI.
- UI is accessed from the left-hand navigation panel.
- Replaces the Settings > Access Control UI.
- Requires the Administrator privilege.
- Catalogs and price groups display as read-only for users lacking permission to update.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 11 MAR 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Enhancement to Robust Order Capture
This CX Commerce update provides an enhancement to the Robust Order Capture feature released in 20D Revision 4. Robust Order Capture reduces rare occurrences of orders where the payment has been authorized, but not successfully submitted.
This new enhancement addresses the specific incident that may happen when the “Full Payment Required” setting is configured, and a shopper attempts to remove the last item from the cart.
Capability highlights
- An order is no longer deleted if a shopper tries to remove the last item from the cart and the order is now saved in ‘failed’ state.
- Merchant has access to details of the failed order.
- The order can be viewed in Order History and in the Agent Console to aid investigation.
- Shopper also has a record of the order.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 11 MAR 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Large Webhook Payload Reduction
This Commerce update allows developers to better integrate with systems that have payload size limits and provides a defined fallback mechanism when there are large quantities of data objects.
There are situations that result in webhook payloads having a very large number of items, thus very large payloads. This can present a problem for downstream systems and middleware platforms. With this update, customers and integrators have options for handling the large payloads by either reducing or limiting them. This prevents unexpected problems and errors later when operational.
Capability highlights
- Allows the configuration of a maximum number of items to be sent in the payload (for certain webhooks) and truncates after that amount. Payload indicates that data was truncated.
- For example, Shopper Profile update can be limited to 100 shipping addresses sent via webhook
Profile and account update webhooks can send deltas (changes) only for certain properties. This information will be included in product documentation in the Extending Oracle CX Commerce for 21B guide
California Consumer Privacy Act (CCPA) Support (API Only)
This Commerce feature is designed to address the California Consumer Privacy Act of 2018 (CCPA), giving consumers more control over the personal information that businesses collect about them. This landmark law secures new privacy rights for California consumers.
The update enables a merchant to request an extract of all clickstream data for an individual shopper to package in an encrypted format that can be provided to the consumer.
CCPA rights apply only to consumers/shoppers who are residents of California.
Capability highlights
- Provides an Agent API that can initiate a request to generate a snapshot of all clickstream data for a specific shopper.
- This will generate an encrypted file on file storage that can then be sent to the shopper.
- Categories of data extracted, include pages visited, products viewed, search terms entered, and products added to cart or purchased.
- Note existing APIs can already be used to extract profile and order information.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 22 FEB 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
AI Recommendation Strategies and Global Exclusions
With this release, CX Commerce allows merchandisers to create complex recommendation rules or strategies that can be managed efficiently across widgets on different page layouts and harness the power of the Commerce Recommendations engine right in the Administration UI without the need for custom rule set up and testing by a development team.
Product recommendations are generated by an AI-powered learning engine. Strategies and Global Exclusions work in harmony with this engine to provide granular control over the merchandising experience.
Capability highlights
- Extend existing recommendation strategies with additional logic, including tailoring recommendations to prioritize additional factors (for example: brand affinity).
- Combine multiple strategies and limit the number of products returned by each to create a broad variety of recommendations to connect with the customer.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 29 JAN 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Integration with Oracle Product Hub
The CX Commerce integration with Oracle Product Hub, an enterprise-class product master data management software delivered via cloud, allows customers to import centrally managed products, SKUs, images and price lists into the Commerce application. For CX Commerce customers with large catalogs, a substantial number of products and complex operations, integration with a master data application such as Product Hub is key to effectively and efficiently manage their business.
Capability highlights
-
- Ability to import products identified in Product Hub to be published in Commerce.
- Ability to associate collections created in Commerce to the products.
- Ability to synch products created / updated in Product Hub with Commerce.
- Ability to upload images from Product Hub to Commerce and associate them with products.
Integration with Customer Data Management
The CX Commerce integration with Oracle Customer Data Management (CDM) a cloud-based application for managing organizations and contacts, enables customers to import centrally managed records for accounts, customers and profiles into Commerce, providing a single source of data for all customer data. Using Oracle Integration Cloud (OIC), the integration is flexible and extensible to meet custom flows between CDM and Commerce.
Capability highlights
- Synchronize in bulk or individually contacts and profiles that have been created or updated in Commerce to CDM in real time. Additionally, associate contacts to an account during the synchronization process.
- Synchronize in bulk or individually accounts that have been created or updated in Commerce to CDM in real time.
- Maintain and synchronize account hierarchy across the systems.
- Dynamic attributes created on either system can be mapped using the OIC integration.
- Customer records can be displayed in the storefront from CDM.
Catalogs with Optional Collections
This new CX Commerce feature extends the current independent catalog model to support products that are directly linked to the catalog and not in collections. A business user can directly link a product to a catalog via the Administration UI, API, .csv import/export, or bulk import/export API and add those products to a collection in the catalog after importing into CX Commerce.
Capability highlights
- Search for products that are directly linked to a catalog via the custom search product modal.
- Ability to see/edit which catalogs the product is directly linked to from within the membership tab of the product editor.
- Ability to filter the list exported to excel by products that are directly linked to the selected catalog via the export dialog.
- Extends the current independent catalog model to that it can support products that are directly linked to the catalog and *not* in collections.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 29 JAN 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
This new CX Commerce update allows merchants to build different shopper experiences based on the type of device (mobile vs non-mobile), as well as the operating system being used (iOS, Android, or Other). Targeting based on device information applies to creating new audiences and extending existing audiences.
Capability highlights
- Create content variation slots that are specific to the type of visitor.
- Target a promotion based on the type of device being used.
- Extends the existing Audience Rule Builder to add additional criteria.
Anonymous Shopper Personalization
Many visitors to a site do not register as members, although they may be repeat visitors or buyers. This new feature of CX Commerce extends engagement and revenue conditions to these unregistered shoppers. This update expands the current Audiences capability of supporting shoppers that are registered but not logged in.
Capability highlights
Previously, first visit and last visit date were available. This new release extends the conditions to include:
- Engagement: First Purchase Date, Last Purchase Date, Number of Orders
- Revenue: Lifetime Average Order Value, Lifetime Spend, Lifetime Currency Code, Last Purchase Amount
Audiences using these metrics can now target shoppers across the journey, regardless of login status.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 15 JAN 2021 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
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.
Enhanced Boost and Bury in the Dynamic Curation UI
With this CX Commerce revision, we’ve introduced an enhancement to the UI for boosting and burying products in a dynamic curation rule. As a reminder, dynamic curation allows you to influence the ordering of search results when the shopper navigates to a category (collection) or enters a search term. You can also create dynamic curation rules. Each rule has a destination (a collection or search terms), a set of criteria for ordering the search results, and an importance level for each criterion. Search uses your prioritization and blends the criteria to generate a sort order.
This new enhancement provides an easier and more efficient way to choose and sequence the products you want to boost or bury. You can view and sequence your boosted or buried products in a light table that is always visible in the rule. For example, if you have a rule that prioritizes products that are newest and most viewed, you can boost specific products to the top of the product listing, and easily sequence them for the most appealing visual experience.
NOTE: Dynamic curation rules apply to search-driven collection pages, not collection pages driven from the catalog.
With this update, all Commerce orders are now placed in a pending payment state prior to initiating payment. This ensures that orders are captured, and problems resolved, if there is an error during the payment or order submit process.
This update allows the merchant to respond when payment has been authorized on an order but not successfully submitted and provides an historical record of the transaction causing the authorization.
Capability highlights
- When configured to allow partial payments, Commerce places orders in a pending payment state at the start of checkout.
- If payments fail in a way that Commerce does not receive an error, the order will remain in the pending payment state.
- Allows shopper to change or retry payment.
- Prevents further order changes or deletion by purchaser.
- Pending payment orders will be canceled after the defined time period set in the Admin. A record of the order will be visible in our Agent UI.
Oracle CX Commerce is excited to launch its latest innovation, our next generation Open Storefront Framework (OSF) exclusively running on Oracle Cloud Infrastructure (OCI). OSF is an evolution of our Storefront that is focused on minimizing coding required, maintaining business level control, leveraging the latest technology frameworks, and providing robust tooling for the modern developer.
Capability highlights:
- Front-end developers can deliver faster, more responsive and richer user experiences.
- OSF is built with React so developers get to work with technology they know and love, but you also have flexibility and can develop in any front-end library of choice (e.g. React, Angular, Vue) without fear of lock-in.
- Headless without compromise – develop in your preferred front-end technology and still leverage business tooling.
- OSF leverages a fully-featured platform with drag-and-drop experience tools, context-aware preview, personalization, content, merchandising, search, catalog, inventory, A/B testing, reporting, and more.
- The UI layer provides a clean separation between the presentation layer and the state model to support local development and testing.
- Micro (not macro) updates simplify how experiences are assembled and delivered with reusable, granular components (widgets) to create, swap, and go without writing code.
- Experiment in a low-risk, low-effort way. Easily insert commerce into new buying experiences, plug in new technologies, and test new sites and regions.
- Streamline collaboration by incorporating command line tools in bespoke processes.
- Monitor performance and optimization across development & release cycles.
- Accelerated development through local rendering & testing and CLI tools, providing support for customer/partner CI/CD processes.
With this CX Commerce release, merchants can scale to a larger number of catalogs and centrally manage collections and catalog taxonomies across a large range of accounts.
This is advantageous for those that share catalog taxonomies across catalogs but have unique product membership per account.
Capability highlights:
- Offers fine-grained control of account level availability of products.
- No longer the need to recreate hierarchy for each catalog.
- Provides ability to create a filtered view of an existing independent catalog:
- The filtered view will inherit the same taxonomy and products as the independent catalog.
- Ability to show/hide selected product(s) from within the filtered view.
- Ability to associate a filtered view with a site or a contract.
Longtext Dynamic Property Support for Products/SKUs
This CX Commerce revision provides merchants the ability to create product and sku dynamic properties with type long text which can be used to store a large amount of plain unformatted text, such as content in CSV, JSON, or new line separated list format.
Dynamic properties of long text can be created to add promotional content and media or to apply product-specific styling to product detail pages. Merchants can now enter data used by custom presentations/widgets, without being interpreted as HTML.
Capability highlights:
- A business user can create a long text dynamic property via Administration UI or API.
- The new long text property will be a plain text rather than rich text editor.
- The business user can view and update the values of these dynamic properties on the general or custom product tabs of the product/SKU editor in the catalog Administration UI.
With this CX Commerce update, Agents can now respond to shopper issues with a goodwill credit applied to an order where a shopper has experienced difficulties. Appeasements may be required in multiple circumstances – for example, when a shopper is dissatisfied with merchandise purchased, displeased with a delay in delivery, or upon receiving damaged product.
The appeasement may be issued against the cost of the items in the order or against the cost of shipping associated with the order.
Capability highlights:
- Appeasement can be issued against a submitted or fulfilled order.
- Capture appeasement details such as type, reason, amount, or specific notes.
- Validate appeasements data against external rules engine (via webhook).
- Issue appeasement on the payment method available on the order or to an external payment method.
- On submission, webhook will be triggered to pass the appeasement related data Admin API to return update on status and transactions.
Incomplete Order Payload Update
A new property, itemDiscountInfos, provides detailed promotion information on each line item in the incomplete order payload. This property can be used in custom widgets to display promotional information on line items in the cart and at checkout; and sent to downstream systems such as external promotions.
This property was added to the shopping cart object and is available in any of the Store APIs or Webhooks that contain the incomplete order payload.
Capability highlights:
- itemDiscountInfos property has been added to the incomplete order payload.
- For each line item, this property provides a list of the item promotions and their corresponding discount values.
- Information is in an easily consumable format.
- Contains the same information that is in order payload.