In 19AMP, our latest release for Oracle Commerce Cloud, we've added support for editing prices directly in the storefront, publishing a filtered list of changes, personalization based on geolocation, ability to manage failed webhook messages and retry functional web hook failures, preview capability by audience, and more.
Visit our online Help center for more in-depth documentation on 19AMP.
All customers can now also access details on What's New with each Commerce Cloud release, as well as videos, FAQs, how-tos, best practice guides, and more in our online community, Customer Connect (log-in required).
The major new features released in the Oracle Commerce Cloud 19AMP update include:
Edit Prices on Storefront
For merchants who make high-frequency price changes, OCC now allows for editing prices directly in the storefront, bypassing the publishing process. Merchants can edit product and SKU prices in the OCC Admin UI or use CSV file import.
Search is automatically adjusted to use an automated frequent indexing schedule to update, so that the updated price is presented to shoppers.
This feature is not turned on by default and must be configured using the updateDirectPriceEdit endpoint.
NOTE: Cannot be used simultaneously with price edits that must be published. Merchants should select the price editing model that best fits their business needs.
Publish Filtered List
OCC Admin users can now filter the change list and publish items without explicitly selecting checkboxes (selecting items one by one or page by page).
AUDIENCES AND PERSONALIZATION
Merchants now have the ability to build audiences of registered or anonymous shoppers based on their location as reported by the CDN. Audiences can be built based on Place (country, region, city), Latitude and Longitude, and Time Zone, allowing merchants to present personalized content, products, and offers to shoppers in different areas of the country, for example, to present cold weather products to people living in the Northeast, show special promotions to people living in a city where the merchant has a physical store, or display targeted content to people in a specific location and time zone timed to coincide with a time-dependent on-air television spot, radio ad, and/or social media campaign.
Geolocation-based audience rules can also be combine with other existing rules, making personalization capabilities even more powerful.
ADDITIONAL NEW FEATURES AND OTHER CHANGES
There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud 19AMP. 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).
STOREFRONT AND AGENT
Customize Emails for Saved Carts
If your store supports saved carts, you can now include the cart name of the saved cart in emails, such as the Abandoned Order email which reminds customers of items left unpurchased in their shopping cart.
The saved cart name can also be included in any email template that has order details, including Items Shipped, Quote Failed, Order Approved, Order Rejected, Order Payment Initiated, Order Placed, Order Quoted, Quote Requested, Scheduled Order Placed Failed, Store Cancel Inflight Order, Store Cancel Order, and Store Return Order.
Changing the Status of Contact Registration Requests
In the Agent Console, agents acting as delegated administrators can now change the status of a contact request (Accept, Reject, More Info Needed, Review, New) improving workflow efficiencies.
Customizing Countries and Regions in Addresses
New Admin API endpoints at /ccadmin/v1/countries now let merchants add, delete, and update countries and regions available to their store, making it possible to manage a list of countries and regions that have assigned abbreviations for region and display names.
NOTE: Each country and region added must match a valid ISO 3166 code.
Manage Failed Event Webhook Messages
Merchant administrators can now view and resend failed messages using the Admin UI. (Previously, this capability was available via API only.) Includes ability to:
Retry Functional Webhook Failures
Allows for the ability to retry functional web hook failures where a failure is defined as any response other than 2xx (e.g. 200 OK), as well as the ability to configure the number of retries for each web hook or disable retry altogether. This is useful in instances where there are intermittent connection failures and a retry is necessary.
Retry is currently supported for the following functional web hooks: Shipping Calculator, External Tax Calculation, Catalog and Price Group Assignment, Order Approvals, Return Request Validation
NOTE: There is a one minute time limit to complete retry attempts.
Add Card to Shopper Profile
Shoppers can now add a saved credit card to their profile without having to place an order. Once saved, this card can be used as the payment method for future orders.
Customers that are using specific layouts or targeting content to specific Audiences can now preview the shopper experience for a specific audience or combination of audiences without having to test on a test site and set up Shopper profiles that correlate to a specific audience rule.
For instances where multiple Audiences are applied, Preview applies the same log as the storefront would, to ensure that the correct content is being previewed and the experience matches what a shopper would see in production.
Also now includes the ability to preview by viewport. When a viewport is applied, the preview window is resized to give a better indication as to how the storefront would look.
Dynamic Curation Preview
It is now possible to preview a rule that has a read-only, complex "destination,” allowing merchants to preview the effects of rules created via API for “destinations” other than a product collection or search terms.
NOTE: If you preview a rule with multiple “OR” clauses, you are taken to the destination described in the first clause.
Two other smaller enhancements have been made: