¶ About
Litium Commerce Cloud (LCC or just Litium) is an e-commerce platform complete with integrated PIM. It is built with the latest .NET technologies and fully customizable by you as a developer.
This page will give you an overview of LCC, read it and then continue to the Litium development page and finally complete the tutorials to prepare for the developer certification (linked in the main menu) that will make you a Litium certified developer!
Let's get started!
¶ Areas
The Litium platform has of six main areas:
- Media: Manage uploads of files and media (pdf, images, videos etc.)
- Customers: Personalization and user management, manage all users from administrators to external customers
- Sales - Order and campaign management
- Products - The product information management system (PIM)
- Website - The content management system (CMS)
- Globalization - For content publishing, common (and part of) the other areas
¶ Media
The Media area handles files in a folder structure. It contains file uploads for all areas, such as products images and website content.
Read about media data modeling on Litium docs
¶ Customers
The Customer area handles users and permissions.
-
A Person is the user account for a user in Litium
-
A Person may be added to one or more Groups:
- Permissions are always set on Groups (they cannot be given directly to a Person)
- A Group in Litium can be smart or simple:
- In simple groups you manually add or remove members when needed.
- Smart groups instead define a set of search criteria and all Persons with attributes that match the criteria are automatically added (or removed) based on this, as an example a group called Litium staff could be configured to automatically include all Persons with an email that contain "@litium.com"
-
Target groups are behavior controlled groups used for personalization.
- The difference between Smart groups and Target groups is that Smart groups identify logged in Persons based on data stored on that Person, but Target groups only identify Sessions (for both logged in and anonymous visitors) based on behavior.
- Examples of behavior that can be identified in Target groups are "Has a specific product in cart" or "Has visited a specific page".
- Behavior information is stored in cookie and not in database.
- Read more about Target groups on Litium docs.
-
A Person may also be connected to one or more Organizations. An Organization is (usually) the customer entity in B2B scenarios and customer information (like delivery address, billing address, customer number etc.) added to the order is fetched from the Organization of the current Person. In B2C the Person is usually also the customer, and customer information is then fetched from the Person-object to the order.
-
As an attribute on the link between a Person and an Organization it is possible to set one or more Roles. A Person can for example be connected to an Organization with the role "Manager". Roles are also used in Litium Accelerator to handle the order approval flow.
-
To comply with GDPR, Litium supports exporting and removing user information. Extra audit information is also stored when a user with access to customers or orders logs in. Read more about GDPR on Litium docs.
Read about customers data modeling on Litium docs
¶ Sales
The sales-area contains all orders that has been placed on all websites and channels in the Litium installation.
This is also where you manage campaigns and discounts.
¶ Products
Products can be created in Litium PIM but more often there is an integration to an ERP where products are first created and then sent to Litium to be enriched and published. By using workflows in Litium PIM it is possible to set rules for who should be doing what and provide useful instructions on what needs to be done at all times.
A product in Litium PIM always has a single baseproduct and one or many variants.
The variant:
- Is the physical SKU
- Has price and inventory information
- Is the sellable item, variants are added to the shoppingcart
- Cannot exist without a baseproduct
The baseproduct:
- Is a container for variants
- Not a physical or sellable item
- Should hold all information that is common to all its variants, like Brand and Description
The product page in Litium will likely display information from both the baseproduct and the variant. In the image below the Brand and Description are fields on the baseproduct. Images, Color, Size, Price and Quantity in stock are set on the variant. By selecting values for Color and Size a unique variant can be identified and will be added to cart when the add-button is clicked.
Read about product data modeling on Litium docs
¶ Related products and categories
Products and categories can be connected using relations. Common use cases are to present lists of accessories, similar products or others also bought on the product page.
-
A relation can be between any combination of category, baseproduct or variant.
-
Relations can be:
- Directional - a one way relationship where an item points to another item
- Bi-directional - a two way relationship where two items both point to each other
¶ Workflows
Workflows are tasks that need to be completed in Litium PIM. You can create workflows to find products that need to be updated with translations, images, price, categry or any other missing information.
¶ Workflow tasks
A workflow is made up of tasks, a task is basically a stored product search to identify products that need be processed, a task to "Add product images" is just a search to "Find all products that does not have a connected image":
The task can also have an instruction with more deails on what needs to be done and it can be assigned to individual users or groups.
¶ Website
The website area in Litium is a CMS built specifically for e-commerce.
- Create pages and publish them though globalization channels into one or more markets
- Blocks are page sections that can be individually published and permission managed for simple personalization of a website
- Blocks allow editors to easily change the page structure without developer involvement
- A Block can be Global making it reusable in multiple places on the website while still managed in a single location
- Blocks are rendered on site as view components
- Both Pages and Blocks support drafts allowing a pending edit to be reviewed before making it public
- Both Pages and Blocks have the full field framework
Read more:
¶ Globalization
Globalization is a general area that manage access to Litium data through channels. When visitors looks at a Litium website they always view it through a channel that acts as an information filter, the visitors only see the data configured for that specific channel:
- Only pages enabled on the channel are visible
- Only products enabled on the channel are visible
- Only payment methods enabled on the channel are visible
- Only shipment methods enabled on the channel are visible
- Only currencies methods enabled on the channel are visible
- etc...
The same website in Litium CMS can be exposed through multiple different channel, all different content depending on configuration. Setting up a new channel is simple and does not require additions to the Litium license.
Entities of the globalization-area are:
- Domain name
- Has settings for
robots.txtandhttps
- Has settings for
- TaxClass
- A tax class is only a name, the tax class gets its value when linked to a country, the link will hold the percentage for the tax class in that specific country
- Language
- Currency
- Country
- Has setting for currency, price lists and inventory that will be used for the country when connected to a channel
- Channel (has the field framework)
- May belong to a market (but only one)
- May be connected to a website (but does not have to be)
- May have one or many countries connected (normally a channel will only have a single country)
- Defines among other things: language, domain name and payment methods
- Market (has the field framework)
- A market is a group of channels
- Products are sold in a market through channels
- A market can contain multiple channels but a channel can only belong to a single market
Read more about globalization configuration scenarios for markets and channels
¶ Litium Accelerator
Most e-commerce websites share the same base structure, layout and functionality. By providing this core in every new Litium installation, new projects can focus on adding customer value from day one.
Litium Accelerator is provided as source code making it fully customizable, everything that comes included can be removed or modified. The codebase is maintained as part of the platform and comes with its own release notes.
Benefits include:
-
Instant MVP, get a clean e-commerce website instantly and start work by adding value instead of boilerplate code.
-
Lower risk when you start projects on a tested, maintained and supported codebase.
-
Having all projects start with the same codebase also makes it easier for developers to move between different projects and work with multiple Litium customers.
Read more about Litium Accelerator on Litium Docs
¶ Accelerator content
Litium Accelerator is a fully functional e-commerce website, some of the things included are:
-
A website in the CMS containing created instances of required pages (checkout, order confirmation, navigation, cart, search, filtering, my page, order confirmations)
-
A product assortment in PIM with some sample categories and products
-
Templates and fields to create objects in all areas
-
Globalization artifacts:
- Channel
- Country
- Currency
- Domain name
- Market
- Tax class
-
Business rules such as validations and state transitions
-
The search engine Litium search
¶ Backoffice
Litium backoffice (administration UI) is accessed by adding /litium to your website url (the Litium db-tool can be used to create a new administrator account after installation).
Litium backoffice is a SPA built with Angular. Extensions added by developers are built as Angular components. There are several extension points available in backoffice where developers can add custom UI and functionality:
¶ Add-Ons
Add-Ons are packaged functionality that can be added to Litium installations, some commonly used ones are:
- Product Media Mapper: Automatically connects uploaded images to products
- Payment providers: Many supported such as Klarna, Svea, Briqpay and Adyen
- Integration kit: A codebase used to develop file based integrations towards Litium
See the full list of available Add-Ons on Litium docs
¶ Distribution
Add-Ons are distributed either as:
-
Compiled Add-Ons (e.g. Product Media Mapper)
- Installed as NuGet packages
- Run as part of the Litium application
-
As source code Add-Ons (e.g. Integration kit)
- Source code is downloaded from Litium docs
- Run as part of the Litium application
Be aware that when a new version of Litium version is released most Add-Ons will not be available for that version. Verify before project start that required Add-Ons are available.