In our fourth update for 2018 of Oracle Commerce Cloud, we've added a much requested B2B feature -- Punchout -- as well as support for external promotions and new promotion templates, Back in Stock Notifications (API only), ability to schedule recurring full publishing events, ability to run A/B tests in checkout, and more.
This out-of-the-box promotions template allows merchants to specify a required spend amount for certain products, collections, and/or SKUs in order to receive an order-level discount, such as Spend $100 in Women’s Shoes, Get 10% Off Your Order.
This easy to use template allows promotions of this type to be created quickly and efficiently in the Admin UI.
This out-of-the-box promotions template allows merchants to specify a required spend amount for certain products, collections, and/or SKUs in order to receive a shipping discount, such as Spend $100 in Women’s Shoes, Get Free Standard Shipping.
This easy to use template allows promotions of this type to be created quickly and efficiently in the Admin UI.
Enables ability to handle promotions defined via an external system using a new promotions webhook, including ability for shoppers to redeem external coupons and promotions. Includes real-time check of external coupons, such as profile-based coupons, from external systems, as well as ability to update promotions determined by Commerce Cloud and override where necessary. Works with order cancellations and returns as well.
NOTE: May require customization to display external promotions or related presentation in the cart.
This feature allows merchants to create a contact (including name, email, and role) outside Commerce Cloud in an external system and associate it to an existing B2B account. Supports Single Sign-On into OCC. While the feature is available natively, this does require setting up keys between OCC and the SSO provider and customizing the shopper login page to display the SSO option to buyers.
Allows for supporting common use cases, such as instances when contact information exists in both OCC and ID provider and when the contact information does not exist in OCC, but does exist in ID provider.
NOTE: Ability to auto-create the B2B Account when passing in the SSO credentials for the contact requires the Account already have been created. Also, no out-of-the-box widget is currently available. Will require custom widget.
Punchout is a new B2B feature that allows merchants to integrate between a buyers’ e-procurement system and Oracle Commerce Cloud allowing for cost savings and adding controls on the buying side (e.g. budget, approvals). Enables merchants that sell to large organizations with e-procurement systems to be set up as a supplier within that e-procurement system.
Instead of going through regular site checkout, a common scenario typically required (and now supported) is that the buyer adds items from the merchant site and then clicks “punchout” to be taken back to the e-procurement system and from that point, going through an approval process and eventually purchasing via sending a purchase order to the merchant.
Supports “direct punchout” model, punchout, re-punchout, and submit purchase order flows. Supports the most common cXML standard. Built using Server Side Extensions, so is highly extensible.
Additional New Features and Other Changes
There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud 18C.
Browser Support, Language, and Currency Support
Browser support is up-to-date.
Language and Currency Support
Languages: No new languages added.
Thirty-six 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), English-GB (en-GB), 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 are supported.
Sixty-one currencies are currently supported: 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 (Guatemalan 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).
Two new webhooks are now available to improve notifications for key shopping-related events. The Remorse Period Start Webhook can be configured to fire when an order is placed and remorse period begins, allowing for a notification of a new order to be generated. The Order Cancel Webhook can be configured to fire when an order is cancelled by a shopper or agent during the remorse period or by an agent or automatic service when an order is in a pending payment state, allowing for an order cancel notification to be generated. These webhooks can be used to trigger appropriate emails or messages by an external system to notify or confirm certain actions for shoppers.
The standard Order Submit webhook should still be used if the remorse period has not been configured, since there is no delay between placing the order and submitting it.
NOTE: Both webhooks can be enabled via Admin UI or via API.
Merchants now have the ability to update any property in the return request via the OCC Admin API, including Return Status, Refund Amounts, Tracking Number, and/or Return Label URL, allowing for processing returns in an external system, such as an external OMS, and displaying those changes to the shopper.
The new Update Return Request API allows the integration to update the OCC return request ro reflect the refunds issued in an external OMS. This API bypasses the refund calculation and refund action in OCC so duplicate refunds aren’t issued. The shopper will see the appropriate refund status and amounts as issued by the OMS.
This new API builds on existing OCC functionality allowing OCC to receive permission to create a return request and notify an external OMS when a return request is created. As a result, merchants can now implement an end to end process where an external system, such as an OMS, is the master system for returns.
Allows merchants to use an API to build a custom widget on the Product Detail page that includes a “Notify Me” link when a SKU is out of stock. Capturing the email address of shoppers interested in an item that is out of stock helps ensure merchants don’t lose a sale if an item is out of stock, and are able to capture and forecast interest on an item not currently shippable. Once set up, OCC will send shoppers who have asked to be notified, an email notification when the SKU is back in stock.
Built-in fulfillment of GDPR requirements, including automatic deletion of a request if the product is not back in stock within 3 months, as well as API support to facilitate deletion of the out of stock notification request following shopper requisition.
Currently available via REST API and Storefront JS API support only. Includes sample UI.
This feature improves storefront performance by loading a page top down based on the page layout, displaying the visible content first. This can be enabled/disabled through the cc-store-configuration-1.0.js or by uploading an extension.
Main advantages to this feature:
• The shopper or end user perceives a faster page load by having the content at the top of the page load first, so they can view relevant content earlier
• Google and other site speed measures will score the page more positively due to improvements to key points, such as meaningful “content paint” and speed index which may improve SEO search ranking.
This prioritized page loading works on all OCC pages, including cached pages.
NOTE: This feature is set to “off” by default for existing customers and will require manual activation and review of customized widgets.
Merchants can now schedule full publishing events to recur hourly, daily, weekly, monthly, or yearly, rather than having to manually set up every full publishing event. This recurrence is available for full publishing events only, not partial events.
Experience and Design
Merchants can now create Shopper Profile layouts that can be used by the storefront based on certain conditions. This is useful for scenarios where it makes sense to have separate instances of the shopper profile layout with a different set of widgets (e.g. Addresses, Invoices, Order or Account Details).
Merchants can enter a subdirectory in the URL to accommodate this (e.g. allow a URL such as “*/myinvoices”).
OCC now has enhanced content variation slot capabilities to allow merchants to vary content by Audience, Date, and Audience and Date together, thereby improving content targeting for shoppers and flexibility for merchants in being able to vary content on the Storefront.
The default sub-region will represent the starting content. This is the content that will be shown before the first date-based content activates or if there is no match on Audience. For each sub-region added, users can enter sub-region name and select one or more audiences, as well as start and end date. If the same date/time is assigned to more than one sub-region with the same Audience, OCC will use the content in the highest priority sub-region (leftmost).
The Storefront will display the highest priority content that matches Audience, Date, or Audience + Date.
The Developer Code Utility now supports the ability to transfer page layouts between instances, just like other OCC Design Studio assets. Includes the ability to list and delete layouts, as well as grab individual directories for large stores with a new “incremental grab” option – refresh –which lets partners specific what they wish to download (e.g. one widget, one theme, all widgets, all themes, all assets).
Previously, the “grab” feature brought down the source code for every widget which was time consuming. This new grab-refresh feature allows partners to more easily pick and choose, increasing efficiency and flexibility for partners managing page layouts using DCU.
Provides the ability to define an audience that will include: Registered Shoppers, Anonymous Shoppers, both Registered and Anonymous Shoppers.
Merchants can now target content or promotions to these predefined audiences, useful for campaigns, such as showing specific offers or messaging prompting anonymous shoppers to register, prompting registered shoppers to create a wish list or sign up for a loyalty program, or displaying promotions, products, or content that appeal specifically to shoppers of a particular visitor type (e.g. registered or anonymous or both).
Allows the shopper experience to be crafted for just anonymous or registered shoppers, improving relevancy and engagement.
NOTE: Size estimates only available for Registered Shoppers Audience. No size estimates will be provided for Anonymous Shoppers.
Date of Birth is now supported as a shopper profile property, allowing merchants to limit content or promotions to shoppers above or below a certain age. Recommended to use relative date operators when utilizing this attribute (e.g. date of birth is more than x years ago).
A/B tests powered by OCC Experiments may now be run on payment and checkout pages, allowing merchants to optimize conversion of shoppers in the checkout flow. This allows for testing of specific presentation options in the shopping cart (e.g. presentation and placement of tax and/or shipping charges), as well as during checkout (e.g. field names and ordering).
Merchants can now run A/B tests on all layouts.
Merchants can now create up to 20 custom goals when creating an A/B test with OCC Experiments, allowing the ability to track a larger quantity and more diverse range of elements on a page (previously limited to anchor tags, buttons, input elements and links).
Assisted Selling Application
Supporting existing loyalty points functionality, Shoppers can now pay for their orders in a combination of points and currency, allowing more flexibility for both shoppers and store associates. This is useful in instances when a shopper may not have enough loyalty points to cover the order total.
NOTE: Items in the cart can only be priced in a single monetary currency or points. Merchants must first configure their loyalty points systems and which currencies and point systems will work together. After this, it will be automatically available in ASA.
ASA has been updated with advanced order search capabilities for store associates, including product name, SKU ID, and the date an order was placed. This allows store associates to more quickly locate customer orders.
Product categories in the megamenu and filtering options in ASA now match what is configured in the Storefront and Admin, improving the browsing experience for shoppers and store associates.
NOTE: Product listings will still be displayed based on Guided Search endpoints.