This topic provides an overview of subsystems and data model for Episerver Commerce, part of the Episerver platform.
Episerver Commerce consists of an e-commerce engine with a number of subsystems, together with Episerver CMS for creation and display of product content on the front-end website.
The e-commerce part of Episerver Commerce is built on these components and frameworks:
- Microsoft .NET Framework and ASP.NET
- Microsoft Windows Communication Foundation (Catalog System)
- Business Foundation (Customer Management)
- Meta Data Plus (legacy Order and Catalog Systems)
- Security and Permissions
See Episerver system requirements for supported versions.
These are the main subsystems of Episerver Commerce:
- Customers. Create organization structures, set roles and permissions, and extend customer or organization objects.
- Orders. Define order schemas, connect payment and shipment gateways, customize order workflows, and manage taxes
- Marketing. Create campaigns, custom discounts/promotions, and define policies used for promotions.
- Catalogs. Define catalog schemas, import existing catalogs, and define price lists.
- Markets. Define multiple markets for market-specific features.
Below is a data model of the entities in commerce and the logical relationships they have to each other. The 1 to many relationship means that for each 1 instance of an entity there are 1 or more other related instances. An example is orders and order lines, where for every order there is at least one order line.
The 1 to many (optional) relationship means that it can be related but does not have to be related. A good example is customers and organisations. Customers do not have to be associated with an organisation, so the relationship is an optional one to many between organisation and customer.