Timoty Weis Field Manager Digital Commerce Technology

The current spectrum of payment gateways available, especially from an e-commerce point of view, is too limited having only Adyen at disposal. The fees charged are extremely high and suboptimal for a lot of merchants. All major e-commerce platforms are providing standard capabilities to integrate with way more than only one payment gateway, a key requirement from many brands in the selection of a platform.

Looking at the payment gateways market, Stripe is one of the most interesting (as well as reasonably priced) players. It would be beneficial for Dynamics 365 Commerce to add this provider to the portfolio and integrate it in a standardized way.

Successive options to be considered would be Authorize.net, Braintree or Square.

After a SEO assessment, we identified several optimizations that should be considered for Dynamics 365 Commerce as an e-commerce platform. The top three that we deem should be taken into consideration for further implementation are:

1. Categories (PLP) and product (PDP) page URLs should not be generated using the rackID but leveraging a dedicated attribute to enable friendlier and optimized URLs
2. Apart from the URL slug attribute of the previous point, there should be at least other two, namely page title and meta description (should be possible to override an autogenerated rule)
3. Inclusion of the content-language attribute and hreflang attribute in case of multi-language storefronts

In order to have a constant monitoring and overview of the status of the various services, as well as receiving a direct communication in case of incident (with clear statuses like "investigating", "resolved", ...) it would be extremely helpful to have a monitoring service in place. Other platforms are relying on something similar like the functionalities provided by Atlassian Statuspage. This feature gives a higher level of confidence to the merchants that have a direct and proactive communication regarding the status of the application.

In order to simplify the content management and authoring operations in Sitebuilder, it would be optimal to have an option to export/import contents to allow bulk operations to take place. For example it could help in ensuring the proper SEO information are added to all pages.

In order to provide more appealing checkout options to our consumers, and leveraging the Amazon.com presence and penetration, we would like to propose the standard integration of Amazon Pay within Microsoft Commerce. Key motivators:

1. activation of Amazon customers (100 million prime customers transacting in +170 countries)
2. fast and easy checkout, minimizing cart abandonment (cart abandonment rates average 67.57%, with 34% of customers citing forced account creation as a key reason for site abandonment)
3. Minimize costs for payment providers
4. Help improve sales due to Amazon name recognition