An Introduction to Episerver for B2B Commerce

Episerver provides a .NET B2C and B2B commerce platform. B2B Commerce Solutions require more specific features such as order pads, organizational based pricing, quick order, impersonation, quoting and more.

Consumers expect a B2C experience on B2B sites so a B2B solution still needs all the features and value that a B2C site gives you. Episerver provides one platform on Microsoft .Net to create a B2B solution with B2C features to create the optimal B2B portal focused on frictionless transactions and a leading experience.

The B2B demo site available on github for download. This site is designed to showcase how Episerver easily supports complex B2B capabilities. Its built on our framework QuickSilver and has its own catalog; the catalog is also more B2B/Industrial, containing items like Lifting Equipment, Power Tools, and Generators. If you are not familiar with Quicksilver it is our Commerce Reference Site build on MVC .NET using things like Bootstrap, JQuery and Less CSS. It is fully ready and enabled for Azure Web Apps and the cloud. 

Here are some of the capabilities it demonstrates:

  • Organizing customers into companies (Organizations) and company divisions (SubOrganizations)

Customers can be associated with Organizations, representing the company. In addition, an organization can have sub-organizations, representing subdivisions.

  • Customer Self Service, as a Company/Organization

Users for a company can log in and see/manage their company's users, orders, order pads (e.g. wishlists), divisions, addresses, and other information.

  • User Impersonation

This empowers customer users to impersonate other user's within the company.

  • User Roles within a Company

The site demonstrates how you can use Episerver to create admins, purch

asers, and approvers with different permissions. Admins can manage the company's users, budgets, orders, e

tc as well as impersonate purchasers and approvers. Purchasers can't manage or see their company's information, but they can place orders. Approvers can see organization information and approve purchaser orders, allowing them to be submitted to the backend. To be clear, this is an example role setup - each B2B implementation user role setup will be unique.

  • Customer Credit Accounts/Budgets

Users can manage their organization's budgets. These budgets can be assigned to a Purchaser. These budgets can then be used as a payment method during checkout.

  • Order Workflow

Cart can be submitted by Purchasers. Orders placed by Purchaser's must be approved by Approvers to be submitted for fulfillment.

  • Requesting a Quote

Carts and Order Pads can be submitted to the backend for a quote. The quote can then be processed in the Order Management system, updating the pricing, and marking the quote as complete.

  • Organization-based Pricing

This demonstrates how Episerver supports pricing based on asssociation to an Organization. Organizations have a property, Customer Group, which maps to the pricing field Customer Price Group. Using this, you can group one or more Organizations in a Customer Group and assign a price to that Customer Group. Any users associated with that organization will get that price. To learn more about that, read here: http://world.episerver.com/documentation/developer-guides/commerce/pricing/.

  • Organization-based Discounts

This highlights how you can create a visitor group that maps to a customer's Organization Customer Group (see previous). You can then target promotions to only apply to members of that visitor group/Organization using a setting on the Campaign settings.

You can find the source for this B2B demo here : http://github.com/episerver/quicksilverb2b

You can find more information about the B2B Demo here from a technical perspective. http://world.episerver.com/blogs/Shannon-Gray/Dates/2017/4/episerver-releases-b2b-demo-site/