Per Site Consent Configuration
Allows merchants to configure cookie and profile personalization consent by site via API. This is useful in differentiating between sites that sell to European shoppers and those that don’t. Both settings are independent of one another.
NOTE: Profile personalization consent determines whether data can be stored on a particular shopper for personalization purposes. This is not consent to capture data in the profile which many merchants will have a legitimate business need to support. As always, we recommend working closely with legal counsel on GDPR-related requirements and implementation.
With GDPR, there needs to be explicit opt-in by the shopper to create cookies containing personal data on the shopper’s machine. OCC provides sample code for the Civic UK Cookie control component that can be adapted by merchants for their needs. Alternatively, merchants can review this sample code and make equivalent changes to their existing cookie components. Whichever cookie consent component is used, two specifically named cookies need to be created:
- GDPRCookieP13nConsentGranted: If shopper has provided consent
- GDPRCookieP13nConsentNotRequired: If shopper is in a non-EU country
Commerce Cloud personalization features, such as Recommendations and Audiences, will check for the existence of these cookies.
Out-of-the-Box Widget Changes
OCC now includes two new out-of-the-box profile properties to record whether profile personalization has been granted, as well as record the date when that consent, as well as email opt-in, has been granted:
- GDPRP13nConsentGranted to track p13n consent status
- GDPRP13nConsentDate to track consent date
The option to capture consent is available upon login, checkout registration, within the shopper profile section, and My Details area for B2B. The existing Receive Email Updates checkbox will now also have a receive email consent date associated with it.
If a merchant has mandated that profile personalization consent is required, an additional checkbox will be added to out-of-the-box widgets where a shopper can register or edit his/her profile. B2B contacts created by an admin will be shown consent fields on their first session, so they can review and provide consent.
For merchants that have set profile personalization consent as a requirement for a site, shoppers that have not provided consent will not be considered a member of any audience that references profile data. This means that any personalized content, experiments (A/B testing), and promotions will not be available to shoppers who haven’t provided this consent.
By default, OCC allows a registered shopper’s visit to be personalized based on his or her profile data prior to login. For merchants that set cookie consent as a requirement for a site, shoppers that have not provided that consent will not have their site experiences personalized until after login. If additional profile personalization consent is set to be required for a site, shoppers that have not provided that consent will not have their site experiences personalized even after login.
For merchants that have set cookie consent as a requirement for a site, shoppers that have not given that consent will not see personalized recommendations based on their site behavior and their data will not be persisted across sessions. Additionally, the Most Recently Viewed product recommendations feature will also not be shown. (This means shoppers will see default recommendations based on other shoppers’ behavior if enabled.)
Deleting and Redacting Data for B2B Account Profiles
The endpoint that was provided in the 18A release for deleting shopper profiles can now be used to delete account-based shopper profiles as well. Also, the endpoint for redacting orders has been updated to apply to account-based data, such as approver IDs residing on orders. This allows merchants to remove the profiles of account-based shoppers upon request.
Scheduled Selective Publishing
Merchants can now select items from the change list and schedule them to be published at a future date and time. This allows users to set up a schedule in advance and only publish certain assets when they want them to be published, and not have to manually publish every change. Merchants can also review any dependencies before creating the scheduled event.
NOTE: Running a full publish will always publish everything in the change list, even if it was scheduled to run as part of a scheduled selection.
Additional New Features and Other Changes
There are also a number of additional new features, changes, and improvements included in the Oracle Commerce Cloud 18B Update. By functional area, these include:
Browser support is up-to-date. Note: iOS 11.0 is now supported.
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.
Custom Properties of Addresses
A new endpoint is available for creating custom address properties of type Short Text, Rich Text, Date, Checkbox, and Number. This can be used for both B2C and B2B. Any custom address property created will be available for profile addresses, account addresses, self-registration addresses, and order addresses. These custom fields display in both Admin and Agent, and are included in the Storefront view model.
Use of these custom address properties is especially useful for supporting multiple sites in different countries that have different address formats.
New Email: Account Activated/New Contract
A new email is now available for use when an account has been activated or a contract for a new site has been added. This is sent to all buyers as a bcc. Ensures a B2B buyer has access to the sites on which his/her accounts have a contract.
NOTE: The email uses the Admin content locale for emails and there is no current ability to send bulk emails with individualized content.
B2B Account Reporting
An additional sales report has been added to support B2B account hierarchies. Merchants can easily filter the report to view performance of each account as a whole, including its children, and see how each of the primary accounts are performing in relation to one another. Merchants can also now view a breakdown of each of the child accounts for a specific account and how they are contributing to the overall sales for the Primary account.
Import/Export Support for Add-On Products
Allows merchants to import/export add-on products and their SKUs linked to the main product via the Admin Products Import/Export csv file. This allows customers to more easily handle bulk assignments and removals of add-on products and SKUs.
Externally Priced Shipping Methods
Provides merchants with the ability to create shipping methods that have price and availability determined during checkout by an external system via the Shipping Calculator functional API. Externally priced shipping methods are defined the same way as existing internally priced shipping methods, so promotions and taxes are applied to externally priced shipping methods as they are to internally priced ones.
The shipping calculator request will include all externally priced shipping methods that are determined to be eligible based on the current site, price group, and cart contents. The shipping calculator response can then include the available shipping methods passed in the request and their prices. Prices returned by the webhook override internal prices.
NOTE: If “Use shipping method as a fallback” has been selected, the shopper will receive the shipping method at the internal price if the Shipping Calculator call fails and the shipping method is determined to be available based on internal criteria.
Experience and Design
Layout Manager: New Role Layout
New role-based layout is now available in Design Studio that allows merchants to render pages on the Storefront exclusively for selected Admin roles. Settings include a role picker to select one or more roles. This can be used to create agent-specific pages based on Agent roles.
Layout Manager: Stack Nesting
Support for nested stacks has been added – this allows for the ability to have a stack within a slot and a stack within a stack. These stacks provide greater flexibility, allowing merchants to have pop-up stacks within other stacks and slots. They can also be used within Experiment and Content Variation Slots, useful for testing variations or staged flows, such as checkout.
NOTE: There is a fixed maximum number of nested stack levels—current support is for only one stack-within-stack subregion.
Components Tool: JS Code Layering
With JS Code Layering, merchants can enable an additional user interface that allows layering of custom JS on top of the provided widget which has the benefit of staying on the provided widget, making it easier to upgrade to new versions of out-of-the-box widgets. Clear separation of custom code from OOTB code helps streamline the upgrade process and reduce errors in custom widgets.
Code View Redesign: New Developer Tab
The code view tab has been renamed “Developer” and is a central location where developers can update global text snippets, access developer tabs, and manage the Storefront framework. Code view functions are now accessed via the Components Tool for widgets, stacks, and slots and Theme Manager for theme code.
Product Listing Enhancements
A number of enhancements have been made to the out-of-the-box product listing widget, including grid view with 2, 3, or 4 products across, option to turn on/off list view, ability to change the number of products displayed per page, addition of minListPrice and maxListPrice to the view model to support price ranges, and redesign of the widget configuration UI.
Collection/Search Results pagination enhancements now display the current page in the center of the list of pages in the pagination element, improving user experience.
New Facet Order: Statistical Significance
Now support a new method of ordering the list of facet values via the Attributes API. This can be used to promote the facet values that are most relevant for the current search results and can be used in combination with other sort orders (e.g. “sort”: “sig,desc;alpha,asc” to sort by significance, then order alphabetically).
Presenting the most relevant facet values first is particularly useful for facets that have a large list of values. For example, using this new feature, the Brand facet for a search of “DSLR camera” could promote brands that specialize in DSLR cameras higher in the list. Similarly, when used with a Features facet, a search of “compact camera” could highlight features specific to compacts first, such as auto-focus or built-in flash.
Buy X, Get Shipping Discount template
A new promotion template has been added to allow merchants to set up shipping promotions based on the purchase of specific item(s) or per order, for example, Buy a particular table, get free standard shipping. This new promotion template can be used to be as specific as requiring shoppers to purchase specific SKUs in order to receive a particular shipping promotion, or as general as including a shipping discount on any order.
Assisted Selling Application
Deferred (Cash) Payments
Allows store associates to take cash payment types during checkout by marking the order as a cash payment, completing the order in OCC, and managing the tender outside of ASA. This feature is particularly useful for merchants that want to be able to take cash payments easily when completing checkout with ASA, but don’t have a full cash drawer integration.
Store Credit via an External System
Allows store associates to view shoppers’ store credit balance, complete checkout using store credit, and/or handle returns when the order was placed using store credit.
NOTE: Store credit purchases must be returned as store credit. Other payment methods will be returned to their original methods when processed in ASA.