AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    Administration interface basicsDevelopers and adminsBusiness usersChangelogGlossary
  • Guides
    Welcome to Xperience by KenticoAdministration interface basicsCustomer journeysDigital marketingConfigurationDevelopmentArchitectureUpgrade to Xperience by Kentico
  • Training
    For AdminsFor Business usersFor DevelopersFor Solution architects
  • API Examples
    ConfigurationContent managementDevelopmentDigital marketing
  • Changelog
    Documentation updatesSecurity advisories
  1. Home
  2. Developers and admins
  3. Digital commerce

Digital commerce


Was this page helpful?

Send us feedback Go back to top
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

Advanced license required

Features described on this page require the Xperience by Kentico Advanced license tier.

Xperience by Kentico digital commerce is an extensible framework for building content-driven online stores. Rather than providing a turnkey storefront, it gives your development team a set of composable services, data structures, and extension points that you assemble into a custom commerce solution.

This page provides a technical overview of the commerce architecture for solution architects and developers evaluating or planning an Xperience commerce implementation.

Key points

  • Digital commerce in Xperience is a framework, not a ready-made store – you build the storefront, checkout flow, and business-specific logic.
  • Products are modeled as content types, not a fixed SKU table – your catalog structure is fully customizable.
  • A pipeline architecture handles price calculation with replaceable steps for taxes, shipping, promotions, and custom logic.
  • The system integrates with Xperience membership, email channels, and content modeling features.
  • At a minimum, a custom implementation is required for tax calculation, payment processing, and storefront UI.

Framework philosophy

The commerce module follows a "provide the building blocks, not the building" approach. Xperience handles data persistence, service orchestration, and extensibility infrastructure. Your team builds the business-specific logic and user-facing experience on top.

This separation is deliberate – commerce requirements (payment providers, tax regulations, product structures, checkout flows) vary greatly between projects. Rather than imposing opinionated defaults that most teams would need to override, the framework provides a set of well-defined interfaces and services that you implement and compose to match your business needs.

What Xperience provides vs. what you build

Xperience providesYour team builds
Shopping cart persistence and session managementCart data model and serialization (the cart content is a free-form string)
Price calculation pipeline with 10 replaceable stepsProduct data retrieval and tax calculation (both mandatory)
Order creation orchestrator (customer management, price calculation, persistence, notifications)Payment gateway integration (no built-in abstraction)
Promotion engine (catalog discounts, order discounts, free shipping, coupon codes)Custom promotion rules and discount logic
Order status management with email and internal notificationsStorefront UI, product pages, checkout flow
Shipping and payment method configuration (admin UI)Multi-currency support, advanced inventory, subscriptions

Customer journey through the framework

The following diagram maps the customer journey to the Xperience services that handle each stage:

Browse products

  1. Products are retrieved from the content hub or website channel using the content retriever API.
  2. IPriceCalculationService computes display prices with catalog discounts.
  3. The customer adds items to the cart. Your code serializes the cart data into ShoppingCartInfo.ShoppingCartData.

Checkout

  1. IPriceCalculationService computes line totals, order discounts, and taxes.
  2. The customer enters addresses, selects shipping and payment methods, and optionally applies coupon codes.
  3. IPriceCalculationService produces the final total including shipping.

Confirm and pay

  1. IOrderCreationService creates the order with all associated data (customer, items, addresses, promotions).
  2. Your payment integration redirects the customer to the payment provider.
  3. The payment callback updates the order status via IInfoProvider<OrderInfo>.
  4. IOrderNotificationService sends customer and internal notifications.

Reference implementation

The sample Dancing Goat project provides a production-ready implementation of the digital commerce solution that demonstrates how to integrate all commerce features into a working online store. The sample site includes complete implementations of:

  • Product catalog modeling and display
  • Price calculation with tax logic
  • Shipping and payment method handling
  • Shopping cart functionality
  • Checkout process with multiple steps
  • Order management and status tracking
  • Promotions and discounts implementation
  • Customer account integration with membership

Documentation pages in this section often reference specific parts of the Dancing Goat implementation when describing features and providing code examples. We recommend examining the sample site's source code alongside this documentation to see how individual commerce components work together in a complete solution.

The Dancing Goat implementation serves as a practical reference for:

  • Architecture patterns – See how to structure your commerce-related services, controllers, and view models.
  • Best practices – Learn recommended approaches for error handling, validation, and data flow.
  • Integration examples – Understand how commerce features integrate with Xperience's content management, membership, and other capabilities.
  • Customization techniques – Explore examples of extending default behaviors to meet specific business requirements.

You can use the Dancing Goat implementation as a starting point for your own commerce solution, adapting its patterns and code to your specific needs.

Next steps

  • Commerce architecture – read about the commerce solution architecture.
  • Commerce setup – enable the feature.
  • Product catalog – design your product content model.
  • Price calculation – understand the price calculation pipeline.
  • Checkout process – implement shopping cart and order creation.
  • Promotions – set up catalog discounts, order discounts, and free shipping.
  • Manage commerce stores – business user guide for day-to-day operations.

On this page

  • Framework philosophy
    • What Xperience provides vs. what you build
  • Customer journey through the framework
    • Browse products
    • Checkout
    • Confirm and pay
  • Reference implementation
  • Next steps