In previous versions of Sitecore Commerce the SQL Database Schema included 2 tables:

CommerceEntities: Stored all Commerce Entities (Catalog Items, Orders, Promotions…) as JSON.-CommerceLists: Maps Entities to Lists (SellableItems To Category for example).

Those tables quickly reached a huge amount of Data and caused significant performance issues in some cases.

To solve that, Sitecore Commerce 9 introduced a simple SQL Sharding technique driven by an Environment JSON Policy-Set: PlugIn.SQL.Sharding.PolicySet-1.0.0.json

Using the Salesforce connector we can interact with Salesforce Sales cloud and create/manage "Contacts" but what about creating "Leads".


There are many articles talking about creating custom facets and is a good one I suggest. Here i will describe steps involved in actually viewing these facet values from inside Sitecore Experience Profile.

As a website evolves and its audience grows making your content available in multiple languages becomes a top priority. The most common way to achieve this goal is to use Sitecore's out of the box language versioning functionality where the tree is shared and the same item in can have translated versions. But what if it's not only your content that differs between various country sites but also presentation? What if your sites intended for various countries are independent from each other and possibly share some components but not all? What you can do is set up a site in such a way that tree is split between countries meaning each site has its own site definition with its own hierarchy.

The goal of establishing customer loyalty is to transform a company's one-time customers into regular customers. Customers should always return to their preferred company and a strong sense of company loyalty prevents them from changing to another brand or supplier. This can be achieved by enabling customer loyalty programs, which can be set up in Sitecore Experience Commerce 9.