The Official Oracle Commerce Cloud Blog

What's New in 17.2 Release of Oracle Commerce Cloud (April)

In our second release of the year for Oracle Commerce Cloud, we've added several major features, including Multisite via One Admin Console, B2B Commerce Order Approvals, initial release of Audiences, A/B Testing of Widgets, SKU bundle support (API only).

As always, you can check out our online Help center for more in depth documentation. All customers can now also access details on What's New with each Commerce Cloud release, as well as FAQs, how-tos, best practice guides, and more at Customer Connect, our online community (log-in required). Check it out!

17.2 Major New Features

Multisite via One Admin Console

Create additional B2C sites and assign catalog and price groups to each site via API. Manage multiple B2C sites using a single administration interface, enabling merchants to run multiple websites on unique URLs that require a unique shopper experience per site, including different content and product assortments. This would be particularly useful for cases where country stores are needed that have their own URLs, country-specific product catalogs, and/or prices.

The OCCS Admin UI provides a centralized location for business users to manage shared and site-specific promotions, different products, catalogs, pricing, and content for multiple sites per site. In addition to being able to assign a promotion to a single site and multiple sites, a promotion can also be set to apply to all sites. Also includes preview by site, site-specific SEO, site-aware endpoints, and Storefront, Agent, and Assisted Selling Application support for multiple site, including separate shopping carts per site.

In this first iteration of multisite, sites have the same look and feel and layouts and email templates, shared payment gateways, payment methods, and shipping methods. Shoppers have the same login and address book across sites, but order history is shown for the specific site a shopper is on.

Note that in 17.2, access control for Admin Console users cannot be restricted by site and wish lists are available on the default site only.

B2B Commerce: Order Approval: Purchase Limits

A new Approver role is now available which, when assigned to an active contact on an Account, allows order approvals to be enabled. The option to control purchasing by requiring approvals based on a configurable order total purchase limit can be configured in the Admin UI. Merchant admins can allow/disallow Account admins to control this approval feature on their own accounts. Merchants can also choose to hold prices on an order waiting for approval for a configurable length of time before an order is cancelled.

Additional email templates are now available to support this feature as well. When a buyer attempts to place an order exceeding the purchase limit, the order is sent for approval and the account approvers are notified via email. Also, when an order is either approved or rejected, the buyer is notified by email.

Once an order is approved, the rest of the order flow is dependent on the payment method chosen by the shopper. As a result, due to the nature of this feature, layout changes to the Profile Layout, Order Details Layout, Scheduled Order Layout, Checkout Layout, and Order Confirmation Layout must be made in order to add order approvals to the Storefront.

Audiences: Audience-Building and Widget Configurations

The Marketing tab of the Admin UI now contains the ability for business users to define audiences using rules built against out of the box or custom shopper profile properties of type string, such as gender.

The new Audiences feature also provides the ability to leverage a new audience membership API endpoint within custom widgets to display different content to shoppers within difference audiences, initially against these rules built against default or custom shopper profile properties of type string.

Based on audience membership, different content can be shown within a widget on the Storefront.

Experiments: A/B Testing of Widgets

Major new Experiments and Design Studio feature makes it easy to test performance and success of different website experiences, allowing A/B testing of widget variations, as well as testing of <i>different</i> widgets. Allows business users to take advantage of the flexibility of Design Studio to create complex A/B testing experiments easily.

Introduces a new library component called Experiment Slot, which can be added to a layout. Business users can use the current experience as the control and add up to five variants to test against the default. Essentially, any widget that can be added to the website can now be tested&mdash;either a variation of that widget with different settings or another separate widget altogether. As with all A/B tests run using Experiments, performance results are available while the test is in progress, as well as after the test is complete. Test results can be determined using industry-standard success metrics, including Conversion Rate, Add to Cart, Average Order Value, and Revenue per Visitor, making it easy to identify the winner (as long as there is statistical significance).

Allows testing of major system changes that would not be possible with standard client-side approach, for example, comparing the number of products per page, testing different product recommendation presentations on the product detail page or different presentations of shipping and handling charges in the shopping cart, or comparing performance of a promotional banner versus product recommendations versus marketing copy in a particular location on the homepage.

Additional New Features and Other Changes

Language and Currency Support

Languages: Serbian is now supported: Serbian-Cyrillic (sr) and Serbian-Latin (sr_latn). Thirty-five languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Chinese-Simplified (zh_CN), Chinese-Traditional (zh_TW), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en, Estonian (et), Finnish (fi), French (fr), French Canadian (fr_CA), German (de), Greek (el), Hungarian (hu), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Norwegian (no), Polish (pl), Portuguese-Brazil (pt_BR), Portuguese-Portugal (pt_PT), Romanian (ro), Russian (ru), Serbian-Cyrillic (sr), Serbian-Latin (sr_latn), Slovenian (sl), Spanish (es), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk).

Currencies: No new currencies have been added in 17.2. Sixty-one currencies are currently supported. Full list here: AED (UAE Dirham), ARS (Argentine Peso), AUD (Australian Dollar), BGN (Bulgarian Lev), BOB (Boliviano), BRL (Brazilian Real), CAD (Canadian Dollar), CHF (Swiss Franc), CLP (Chilean Peso), CNY (Chinese Yuan Renminbi), COP (Colombian Peso), CRC (Costa Rican Colon), CZK (Czech Koruna), DKK (Danish Krone), DOP (Dominican Peso), DZD (Algerian Dinar), EGP (Egyptian Pound), EUR (Euro), GBP (British Pound Sterling), GTQ (Guatamelan Quetzal), HKD (Hong Kong Dollar), HNL (Lempira), HRK (Croatian Kuna), HUF (Hungarian Forint), IDR (Indonesian Rupiah), INR (Indian Rupee), JPY (Japanese Yen), KES (Kenyan Shilling), KRW (South Korean Won), KZT (Tenge), LBP (Lebanese Pound), MAD (Moroccan Dirham), MXN (Mexico Peso), MYR (Malaysian Ringgit), NGN (Naira), NIO (Cordoba Oro), NOK (Norwegian Krone), NZD (New Zealand Dollar), PAB (Panamanian Balboa), PEN (Peruvian Nuevo Sol), PHP (Philippine Peso), PKR (Pakistani Rupee), PLN (Polish Zloty), PYG (Paraguayan Guarani), QAR (Qatari Riyal), RON (Romanian Leu), RSD (Serbian Dinar), RUB (Russian Ruble), SAR (Saudi Riyal), SEK (Swedish Krona), SGD (Singapore Dollar), THB (Thai Baht), TJS (Somoni), TRY (Turkish Lira), TWD (New Taiwan Dollar), UAH (Ukrainian Hryvnia), USD (US Dollar), UYU (Uruguayan Peso), VND (Vietnamese Dong), XAF (CFA Franc BEAC), ZAR (South African Rand.

Webhooks: Bulk Re-Queue for Failed Webhooks

This feature is available as part of the Admin API which now provides a way to retry the failed messages in bulk by providing a query parameter. Improves ability to resolve webhook failures saved in the WebhookRespository more efficiently by allowing querying of the failure list and requeuing of the failures in bulk using a single API call (instead of separate ones).

The failed webhook list can now be queried by message ID, webhook message type, server type, or saved time.

Publishing: Selective Publishing Enhancements

Enhanced publishing selection capabilities include allowing merchants to Select/Deselect All per page, view how many assets were selected, ability to Clear All sections, and see information on multiple authors and which assets they modified.

Catalog and Promotions: SKU Bundles Support (API Only) 

Allows merchants to combine multiple SKUs to create a new product/SKU bundle by using an existing hidden property & bundleLinks. Merchants can even add more than one quantity of the same SKU to a bundle.

Merchants can now easily create pre-combined products that are appealing to shoppers (e.g. special gift basket) and respond to shopping trends and behaviors quickly (e.g. bundling products that shoppers are already naturally buying together).

This new catalog type is available in the Storefront and Agent APIs as well. Note that the bundle can only be created by the merchant and does not cover cases where the shopper is configuring a bundle on his/her own.

Catalog and Promotions: Promotions Folders

This enhancement makes it easier for business users to manage their promotions, allowing them to create, edit, and delete folders, assign promotions to folders, sort and view sub-sets of promotions, and generally have more granular control over promotions organization.

Can be used to organize like promotions together and/or group together promotions that are managed by different teams.

Assisted Selling Application: Cart and Order Enhancements

Provides updated shopping cart to allow merchants to edit quantities and view items in a more user-friendly way. Allows store associates to see the cost breakdown and applied discounts in the cart more easily.

Note: Does not handle split shipping.

Recommendations: Recommendations by Email

Allows product recommendations to be included in two email types already available out of the box—Abandoned Order and New Account—to improve merchandising and upsell/crossell opportunities through key shopper emails.

Merchants can define the recommendations strategy and restrictions, as well as the number of recommendations shown. In order to enable this feature, merchants just need to add the recommendations section to the existing out of the box email templates available in OCCS.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.