41 Results for Category Commerce
The landscape of business and shopping is changing!. With the help of unique Artificial Intelligence (AI) capabilities, e-commerce platforms are able to leverage the latest advancements in technology to learn about their customers and create personalized shopping experiences. One of the recent improvements in this market is voice-activated shopping using intelligent personal assistants. One of them being Amazon's Alexa, which stands out to be the most powerful and accurate voice system on the market.
In this article, I will go over my experience of integrating Sitecore Commerce application with Alexa. The integration of Alexa with Sitecore Commerce will delight the end users with a completely new way to interact with commerce applications.
When talking with potential clients, they tell me the mere thought of the time and cost involved to platform, or re-platform, eCommerce can be enough to leave things ‘status- quo’. Might that be you?
Not so long ago, it was a huge Enterprise undertaking to get an eCommerce system up and running. The good news is, Software as a Service (SaaS) options and the right implementation partner significantly reduce time, cost and stress in getting your platform up and making money.
Insite has a built-in EmailService that allows a developer to easily send emails to a customer whenever they perform an action on the system. This EmailService utilizes the RazorEngine in order to parse HTML and generate rich content emails for delivery. On a recent project, I had many scenarios where an email was being sent to the customer. All of the emails contained a common look and feel, including a fully rendered header and footer. In this blog, I will go over the process I followed in order to allow for the use of the standard Layout property in the Razor template for emails.
Sitecore Commerce currently allows object extension through the use of weakly and strongly typed properties. Although the recommended development practices point to the strongly-typed approach as being preferred our experience shows that the weakly-typed should be used in the majority of the use cases. In this blog we look at the cons and pros of each approach and the reason behind the recommendation.
Combining existing InsiteCommerce solutions allows the sharing of ecommerce capabilities across several different websites. This article outlines the steps involved and explains some of the challenged we faced in the areas of managing Content, Settings, and Code when merging Insite solutions. We hope this article enables you to quickly and easily merge your Insite solutions.