This feature provides a mechanism to capture BOPIS-specific data, including pickup location, inventory location, contact details of the person picking up the order, available pickup dates and time, and shopper preferred pickup dates and times. Admin API and webhooks have been updated to support all BOPIS data.
New widgets and widget versions have been created to accommodate BOPIS as well, including new versions of the Product Details widget with a new "in-store pickup" element, Shopping Cart widget that includes support for a mixed cart model, meaning a cart can have items delivered to a home address and also in-store pickup, Checkout Order Summary widget that displays a list of shipping groups (e.g. home delivery, pickup in-store), Payments widget with ability to pay for in-store pickups in-store or online, Order Confirmation and Order Details widgets that display all BOPIS-related details, as well as a brand new Shipping Options widget which supports split shipping, new BOPIS-related emails (i.e. Goods ready for pickup, Goods have been picked up confirmation), and out-of-the-box staged checkout layout specially designed for this feature. A new "pay in store" payment group type has also been added to support the "in-store pickup" option.
NOTE: For externally configurable SKUs (CPQ), shoppers will not be able to check store availability until they add the configured item to the cart.
Stored Credit Cards
We now support the ability for registered shoppers to save cards and pay for orders (including scheduled orders) using their saved cards, enabling faster and easier checkout to increase conversion. Shoppers can indicate that they wish to save a credit card during checkout and that card will be saved following a successful authorization. At that time, a reusable card token will be returned and saved in Oracle Commerce Cloud. In addition to being able to save cards to pay for future orders, registered shoppers can also set a default card, add or change the nickname for a saved card, and delete a card. It's also possible to associate a billing address with a saved cart, so the shopper does not have to enter it.
When stored cards are being used to pay for scheduled orders, a configuration option allows these orders to be processed without a CVV (since CVV cannot be stored and the shopper is not present to enter CVV for scheduled orders). In case of a payment failure, the order will be placed in a pending payment state and the shopper can return and correct errors to complete the payment. Stored cards can also be used to pay for orders that require approval.
Cards are stored on a per gateway basis, particularly important for merchants running multiple sites, since different sites may use different gateways.
NOTE: This feature is available via API for card payments processed using the Generic Payment Framework in Oracle Commerce Cloud and is not available for out-of-the-box payment gateways. Does not currently support ability to store a card without first placing an order.
Boost and Bury
This is a new enhancement to Dynamic Curation which allows a merchandiser to select and rate criteria to influence the ordering of a product listing that appears when a shopper enters specific search terms or navigates to a search-driven collection page.
In addition to (or instead of) specifying criteria to influence the ordering, merchandisers can now manually curate product listings to promote or "boost" specific products to the top of search results and/or "bury" products at the bottom. Merchandisers can also use this feature to better control which products appear "above the fold" -- useful, for example, to boost products to the top of relevant pages when running an advertising campaign. This rule can be applied to specific search terms or to a search-driven collection page. The results can be previewed in the Oracle Commerce Cloud Admin to verify the results before putting into production.
Allows merchandisers to select and order facets that appear in Guided Navigation when a shopper enters specific search terms or navigates to a collection page, so that facets can be displayed in an order that reflects common shopping behaviors. Facet ordering can be done based on what will be most useful for shoppers and allows merchandisers to control the simplicity and granularity of the navigation menu for different collections. Merchants with a large number of facets may want to use this feature to limit and curate which facets appear in specific situations, both for performance reasons and to present a cleaner, simpler, more effective experience for shoppers.
Merchandisers can define a default rule that applies where a specific rule hasn't already been defined. This rule can be applied to specific terms or to a collection page. Results can be previewed in the OCC Admin before publishing.
Content and Experience Cloud: New "Channel" to Site Mapping
Customers using Oracle Commerce Cloud (OCC) and Oracle Content and Experience Cloud (CEC) can now map different publishing channels from Oracle CEC to sites in OCC allowing the ability to target unique content for each site. Merchants can set up a channel for each OCC site in Oracle Content and Experience Cloud and map each channel ID and token to sites in the OCC integration settings.
Content and Experience Cloud: New Content Listing Widget
Supports creation of individual listings for each "type" of content in Oracle Content and Experience Cloud (CEC), allowing merchants to create a blog site or index a group of supporting or guidance content and easily manage that noncatalog content through Oracle CEC and present it in the Oracle Commerce Cloud site and shopping experience.
NOTE: When using the content item widget with the content item layout, you don’t need to select a content item as the page is dynamically created for each relevant content item.
Content and Experience Cloud: New Content Item Layout
Similar to the concept of a product details layout, but for content, this feature allows a page for a content item in a configured channel to be created when there is an integration in place between Oracle Commerce Cloud and Oracle Content and Experience Cloud. Each content item is added to the sitemap and linked where a merchant has set up content lists for that content type.
Allows merchants to create a site with multiple types of content and add a page for each content item to a page map. Also allows for mapping "channels" to different sites in the Admin settings. Creates a unique page for each content item and links from the sitemap and relevant content listings. When using a content item widget with a content item layout, you don't need to select a content item, as the page is dynamically created for each relevant content item.
NOTE: This type of layout does not yet support multiple viewports.
Content and Experience Cloud: API for CMS Integrations
Primarily built to connect Oracle Content and Experience Cloud to Oracle Commerce Cloud. New Content Map Methods and Channel Map Methods are endpoints for operations that are now available. These APIs can be used to create a site with multiple types of content and add a page for each content item to a page map. Merchants can also now map "channels" to different sites in the Admin settings.
NOTE: These APIs can also be used to connect OCC with another CMS. Out of the box, we've provided support for notifications from Oracle Content and Experience Cloud to OCC, but if integrating with another CMS, merchants will need to build a notification extension or poll for new content.
ADDITIONAL NEW FEATURES AND OTHER CHANGES
There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud 18D. By functional area, these include:
Browser Support, Language, and Currency Support
Browser support is up-to-date.
Language and Currency Support
Languages: No new languages supported.
Forty languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Catalan - ca (Storefront only), 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), Indonesian - id (Storefront only), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Malay - ms (Storefront only), 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), and Vietnamese - vi (Storefront only).
Currencies: No new currencies 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).
Agent Console Customization
The Agent Console in Oracle Commerce Cloud can now be customized and extended by a merchant using the existing Design Studio framework (layouts and widgets), allowing customization of the user interface, so merchants can build their own user experience and screens for agents. All of these customizable pages or layouts for agents will contain either agent-specific widgets or even certain shareable storefront widgets, meaning that certain Storefront widgets are reusable on agent pages as well.
Includes drag and drop capability to build custom agent application. This includes all flows and pages, such as search pages, order, refund, and exchanges, and more--all now customizable.
Merchants can also now further extend the capabilities of the Agent Console and integrate with third party systems to provide a fuller customer experience.
B2C TO B2B Profile Conversion
Merchants can now perform a one-time bulk conversion of registered shoppers to account-based shoppers. B2C users can now be converted to B2B users--typically seen when an organization becomes a B2B account in a merchant's store and users should be able to act as buyers on the account. This is now achievable via API.
NOTE: Only the administrator can access the export and import APIs. Also, this supports a one-way B2C to B2B conversion only.
Publishing of Individual Design Assets
Users can now select only the individual design assets they want to publish, as well as filter design assets by author, status, area, and publishing event name or find individual design items via search query. (Previously, all design assets had to be published together as a group.)
Design assets, such as widgets and layouts, stacks, slots, text snippets, themes are all supported and appear as individual items in the publishing change list.
Dependencies are automatically determined and Oracle Commerce Cloud ensures appropriate items are published together. For example, if you delete a stack from a layout, the changes will be published together -- the stack is deleted and the layout is updated. Merchants have a chance to review dependencies before publishing.
EXPERIENCE AND DESIGN
DCU - Stack and Element Support
The Design Code Utility (DCU) tool now fully supports stacks, as well as global and widget-level elements. It now provides support for creation and transfer of all types of Design components used in Oracle Commerce Cloud.
DCU: CCProxy Substitution
HTML Snapshots: Mobile Support
We've now added support for mobile snapshot when using the adaptive design approach by adding a new endpoint that merchants can configure to determine which user agents will receive the mobile snapshot. When leveraging layouts with XS viewports and a mobile crawler is recognized, the mobile version will be returned. This means mobile crawlers will now receive the appropriate mobile HTML snapshot. Vary: User-Agent header is now in the snapshot response. Includes known Google mobile crawlers out of the box.
We've added a new framework for providing alternative type-ahead experiences, presenting type-ahead results using keywords instead of presenting matching products in a list. This framework allows merchants to:
Use: POST /gsdata/v1/cloud/data/keywords to upload keywords that you want to have appear in your type-ahead results, along with a rank.
Use: GET /ccstoreui/v1/assembler/pages/Default/keywords/typeahead?Ntk=typeahead&Ntt=characters to generate the new type-ahead response.
This can be integrated with a search analytics solution to populate type-ahead suggestions using most popular searches, for example. Can also be extended to include additional metadata, for example, presenting recommended products for each suggestion.
NOTE: This is a headless feature, so front-end code needs to be created separately.
AUDIENCES AND PERSONALIZATION
UTM Query Parameters
Merchants can now build audience rules using UTM query parameters which are commonly used to pass context from referring sites, pay per performance or social advertisements, and other campaigns. So for example, it is now possible to present appropriate content, promotions,, products, and/or experiments to shoppers based on an ad campaign or referrer.
Allows merchants to keep a consistent look and feel from external campaigns through to the website experience. Also enables merchants to automatically apply promotions for shoppers visiting from a referring source or with a specific external search term.
NOTE: Audience rule size estimates are not available for audience rules built against UTM parameters. And it is only possible to build details against the UTM query parameters from a shopper's current visit.
This feature allows merchants to specify that a recommendation set should always show products from a specified collection(s), in the case where there is no product context (e.g. marketing landing page). Also allows merchants to specify the collection of products that should be shown in a content variation slot associated with a particular audience.
NOTE: To enable, merchandisers will need to enter the ID of a collection (found within the catalog) in the widget configuration, rather than selecting from a dropdown.
Custom Goals for Widget Experiments
Allows merchants to track Pageview custom goals for widget-based experiments. These were previously limited to tracking of out-of-the-box commerce metrics only.
The custom goals may be added and managed via either the new Goal Tab on the Experiment slot within Design Studio or the existing Goal Tab within the Experiments configuration screen. May also select Primary Goal from within the Experiment slot.
Results are displayed in the same manner as custom goals for Layout and URL-based Experiments.
New Goal Type: Commerce Events
A new custom goal type called "Commerce Events" is now available for all types of experiments. Allows merchants to track events as custom goals. These include out of the box commerce events (a refined list of approximately 50 pubsub events), as well as custom events (any event defined by the merchant). These events are tracked in the same way as commerce metrics and removes limitations on what can be tracked as a goal for an experiment.
The list of Custom Events is maintained, so that users do not have to repeatedly key it in. These events are also included in type-ahead search. Similar to other goal types, Commerce Events may be added and managed within either the Experiments Slot or Experiments application itself. May be selected as an Experiment's Primary Goal. Results are displayed in the same manner as per custom goals for Layout and URL-based experiments.