This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 17 DEC 2018 | 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.
| Action Required to Enable Feature |
||||
|---|---|---|---|---|
| Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
 |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Manage independent catalogs for brand sites or other sites that have unique catalog hierarchies. Includes support for truly unassigned products and collections, linking collections across multiple catalogs, and allowing a collection to exist multiple times in the same catalog hierarchy. With support for multiple catalogs, merchants can now perform a catalog-specific export, as well as manage each separate catalog within the Admin UI.
Merchants can manage each catalog independently, create completely inherited catalogs or have a mix of shared catalog items and independent ones (blended). The business user can also now edit any catalog directly, including adding unique collections and products to those catalogs.
The enhanced multicatalog model is useful when a merchant has unique catalog structures that need to be merchandised independently. It is also beneficial for B2C or B2B customers that have smaller catalogs, but that need uniqueness in the catalog contents.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
If you think the new multicatalog model is right for your business and you are interested in migrating from the existing legacy model, please contact your CSM for additional guidance in using this new feature.
Saved Orders and Multi-Cart (API Only)
Allows both B2B and B2C shoppers to save their current cart, view a previously saved cart, and check out with a saved cart. This is supported via API only.
With Saved Orders and Multi-Cart, buyers have an additional way to save an order for later if they are unable to complete the purchase in that session. They can then access and complete the purchase anytime in the future when they have the time and availability to check out. This feature gives sellers an additional way to decrease conversion abandonment. Saved Cart or Saved Order reminders can also be used as a marketing opportunity to remind buyers to complete the purchase at a later time.
This feature also allows merchants with multiple sites to enable a saved cart across multiple sites in a multisite instance.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
The saved carts for a B2B buyer are contained within the account-site context they were created in.
Allows purchase lists to be shared with individuals, as well as the entire account, for B2B, and individuals by email address for B2C. Recipients can be given read and edit rights, as well as create their own copy of a purchase list shared with them. Allows Agents to access these shared purchase lists via on-behalf of shopper flow (but not within the Agent App console itself).
Especially useful for creating and sharing commonly used purchased lists with others, for example, grocery lists for B2C shoppers, or purchasing lists for B2B account users.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Only registered users can access a shared purchase list.
Additional New Features and Other Changes
Browser Support, Language, and Currency Support
Browser support is up-to-date. High Sierra now supported.
Steps to Enable
No steps are required to enable this feature.
Languages: Four new languages added--all Storefront only: Catalan - ca, Vietnamese - vi, Malay - ms, and Indonesian - id
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 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).
Steps to Enable
No steps are required to enable this feature.
Allows an anonymous shopper or existing B2B contact to request to be added to an existing B2B account. This account can be approved or rejected by a merchant or delegated administrator. Agent supports on-behalf-of flow for delegated admin and shoppers.
Extends the account registration feature to allow new or existing users to join an account with approval of a delegated admin or merchant admin (instead of requiring admins to create the contact and fill in detail about the buyer manually).
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Storefront widget available out of the box supports Account ID-based registration. API supports both Account ID and Account Name-based requests. Agent can search via API.
Buyers can now upload a structured CSV file with items and quantities to the Quick Order form, so they can be added quickly and easily to cart. System validates file format, file size, and product.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
The default CSV row count supported is 999. This can be changed in the widget code. Also, hierarchical line items (e.g. configured or add-on items) cannot be added to a Quick Order form via import in 18D.
Order deletion is now supported via API, providing merchants with the flexibility to choose to delete order data when required, such as GDPR compliance. This action is limited to the “super admin” role (special administrators) and not available to regular call center agents.
Deleting an order deletes all of its constituent parts, including the order, commerce items, shipping groups, payment groups, and returns. When an order is deleted, any returns against the order are also deleted (if a return has an exchange order, the exchange order is *not* deleted).
Includes support for deleting quoted orders.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Where possible, we recommend making sure operations against an active order are complete before deleting an order to avoid subsequent complications (i.e. deleting an order that a shopper could still return items against).
URL Patterns: Simplified URL Slugs
A uniqueness check is now triggered for products or collections when building URL slugs, helping to prevent unpredictable page resolutions. The relevant Build URL Slugs button must be clicked to run the check. This check alerts merchants to any duplicate URL slug values. Also allows all URL override values to be removed.
This feature allows merchants to proactively prevent the following possible outcomes due to duplicate URLs when using the Simplified URL pattern feature:
- The wrong collection or product is displayed.
- A 404 is returned because the wrong collection is found, but that collection/product doesn't exist in the current site category.
Also, the generate endpoint response now includes an indicator to state whether or not duplicates exist, and if so, for each locale for which duplicates exist (there may be more than one), a list of all of the duplicates, including:
- Item Descriptor
- displayName
- seoUISlugDerived
- id
The unique check is run across the entire product catalog and is done for each site and language combination that is supported for that store.
Lastly, the Admin API has been provided to destroy all previously created URL Override values: /ccadminui/v1/urlPatterns/destroy. This API removes all URL Override values for both Products and Collections, but note that no response is returned.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
The system only checks for uniqueness and reports duplicates, if they exist. Merchants must manually make any updates to prevent duplication.
We recommend merchants add/modify/remove products and collections via the catalog UI or catalog import feature. If using simplified URLs, make sure to rebuild URL slugs after those updates.
Number of Visits has been added as an automatically updated Shopper Profile property for audience-building purposes. Merchants can now build audiences that target shoppers based on the number of visits to the site — useful for personalizing the site experience for shoppers visiting for the first time vs. shoppers who have visited multiple times, for example. This can be used in conjunction with Visitor Type to target anonymous and/or registered shoppers.
Merchants can now provide an appropriate experiece for shoppers based on the number of times they have visited the site and can, for example, display special content and promotions to encourage first-time visitors to convert, while displaying loyalty offers to registered shoppers and incentives to register to shoppers who have visited several times, but not yet registered.
Steps to Enable
No steps are required to enable this feature.
The Search DataStore API now allows merchants to upload any structured data as JSON and it is indexed automatically, making it accessible via all of the advanced search and navigation capabilities of OCC Search--uploaded data can be keyword-searched, navigated, and faceted. Allows for non-catalog data to be indexed and presented in search results, so that shoppers can find and navigate content, such as buying guides, store locations, and customer service and marketing content.
Allows merchants to configure the schema via the Attributes API and control what should be returned via a custom Service. The existing /v1/assembler endpoint can be used to query standard search parameters.
Data can be returned in a separate call, so search results can contain standard product results and spotlight matching information in the Search DataStore.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
This is a headless feature -- any front-end code needs to be created separately. Data indexed in the Search Datastore is not returned alongside product catalog information in the existing search endpoints, so merchants will need to make a second call to search and specify the DataStore.
Allows store associates to scan barcodes on receipts, enhancing order lookup for returns and Buy Online, Pick-Up in Store, as well as expediting order search.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Requires setup of barcodes in OCC.
Supports partial payments via the Assisted Selling Application. Allows store associates to assist with adding payments to a partially paid order.
Merchants can now enable or disable partial payments for the site and orders may be submitted with a remaining balance. Now possible to view or manage orders that are in a partially paid state, as well as add payments to a partially paid order in ASA, allowing for more comprehensive payment management.
Steps to Enable
No steps are required to enable this feature.
Supports order cancellations via the Assisted Selling Application. Allows store associates to cancel partially and fully paid orders if they are within the remorse period. Order History now reflects any cancelled orders and payments returned.
This feature helps assist with line busting as store associates can assist shoppers with order cancellations without requiring them to go to the register. Also allows store associates to view any store credit returned to the shopper's balance.
Steps to Enable
No steps are required to enable this feature.
---
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
