When Commerce Belongs Inside Your DXP
Key Takeaways
- Shopify is transaction-first and Xperience by Kentico is experience-first: the real question is whether the store is your business, or one step in a broader customer journey.
- For content-led organizations, keeping commerce inside the DXP removes the silos, synchronizing, and integration upkeep that come with bolting a separate store onto your content and marketing stack.
- Experience-first commerce isn't about catalog size. From membership sites to manufacturers with tens of thousands of SKUs, what matters is whether the experience around the product drives the sale.
Most organizations don't set out to choose a commerce platform. They want to sell something (e.g., courses, memberships, event registrations, publications, products) alongside the content and campaigns they already run.
That's where a deceptively simple question appears: do you bolt on a dedicated ecommerce platform, or use the native commerce of the digital experience platform (DXP), like Xperience by Kentico, that you already use to run your content and marketing?
The honest answer depends on one thing: what role commerce plays in your business.
If selling products at scale is your business, a dedicated commerce platform is the right tool. But if your content is what earns the sale (if people read, learn, and engage long before they buy, and stay long after) then using commerce as a separate system creates a problem most teams don't know about until they're dealing with it.
This article is about the second case, and why a growing number of content-led organizations are keeping commerce inside their DXP instead of running a store beside it.
Two Ways to Think About Commerce: Transaction-First vs. Experience-First
So how do you tell which case you're in? Start with what each type of platform is designed to put at the center of the experience. This choice shapes everything that follows, from your customer journeys to results.
Platforms like Shopify are transaction-first. It was purpose-built to sell: storefronts, checkout, payments, inventory, fulfillment, and a deep app ecosystem. Content and marketing are secondary and minimal.
Xperience by Kentico is experience-first. Commerce is located inside the same platform as your content, email, personalization, and customer data. The transaction is one step in a relationship. Products are modeled as reusable content: the same content you already publish across your site, campaigns, and emails.
This content-driven setup is the heart of experience-first commerce, where the experience around the product, not just the checkout, does the selling.
Neither is "better,” but they're built for different jobs. Here's how that plays out in practice:
| Transaction-first (Shopify) | Experience-first (Xperience by Kentico) | |
|---|---|---|
Built around | Selling products at scale | Customer experience and content, with commerce built in |
Best for | Businesses where the online store is the core of the business | Content-led organizations where the purchase is one step in a wider journey |
Storefront & checkout | Ready-made and hosted, live out of the box | Built once by your team on top of Xperience by Kentico's commerce services, shaped to your journey |
Orders & customers | Managed in a commerce-centered platform | Managed in the same platform as your content and marketing, for a single customer view |
Promotions | Discount codes, automatic discounts, Buy X Get Y, free shipping; more via apps | Catalog and order discounts, coupon codes, and scheduled promotions, managed by your marketers |
Products as content | Product content lives inside the store | Products are reusable content, published across web, email, and campaigns |
The stack | A separate platform connected to the rest of your tools | One platform, with no second system to license, sync, and maintain |
The trade-off is real: though transaction-first platforms are built for commerce at scale, but lack the depth of content management and digital marketing needed for businesses that rely on unified systems. Xperience by Kentico gives you one connected platform and the freedom to shape commerce around your journey, in exchange for building the storefront and checkout as part of your project.
To be fair, "building" sounds like a lot, but it's less intimidating than it sounds. Xperience by Kentico handles cart persistence, pricing, orders, customers, and promotions; your team builds the storefront, checkout, and the cart's behavior. The real contrast is that this approach is designed to be a one-time build, versus a second platform you keep running and connecting to everything else for as long as you use it.
Beside Your Experience, or Inside It
The cost of a separate store isn't only the platform itself; it's everything that platform has to connect to. Your CMS knows what a customer engaged with, your store knows what they bought, your email tool holds a third version of who they are, and none of them share the full picture on their own. As a result, marketing can't easily see how a piece of content led to a purchase, which is the exact insight a content-led business runs on.
For a pure retailer, that's a fair trade. But when commerce is one part of a bigger journey, closing those gaps with APIs and middleware becomes a cost you keep paying: every connection has to be built, governed, and maintained. That's the difference between commerce beside your experience and commerce living inside it.
Flip it around, and the payoff is concrete. Keep commerce in the DXP, and marketers can manage products as content, publishing across web, email, and campaigns without re-keying. Personalization can then act on what someone read and what they bought. Orders, customers, and promotions live in one admin. There's no integration layer between content engagement and purchase intent, because there's nothing to integrate.
That's what experience-first commerce is really selling: not a longer feature list, but a single, coherent customer relationship instead of a stitched-together one.
"Platforms like Xperience by Kentico give you the flexibility to integrate content and commerce in one place, which is essential for delivering personalized, high-converting experiences across every touchpoint."
Do You Need Transaction-First, or Experience-First Commerce?
Experience-first commerce, like in Xperience by Kentico, is the stronger fit when the purchase needs to support a broader experience rather than being the main event.
That typically describes organizations where:
Content, trust, and the experience around the product drive the sale as much as price or sheer volume,
You're selling anything from memberships, event registrations, publications, and digital resources to large B2B or manufacturer catalogs,
The quality of the overall experience matters as much as checkout efficiency,
You'd rather extend the platform you already run than stand up and integrate a separate store, and you're already running, or planning to run, a DXP for content and marketing.
The deciding factor isn't necessarily catalog size. And when a business needs a full retail engine, with warehousing, marketplaces, or complex logistics at its core, Xperience by Kentico integrates cleanly with a specialized commerce engine, Shopify included.
Organizations already doing this back it up, at very different scales. BlueSoft rebuilt Elkov, a manufacturer with a large and growing catalog, natively in Xperience by Kentico; The Physics Classroom runs subscription-based education sales on the same platform. They use the same commerce features, but for different purposes.
"At Bluesoft, we delivered on Xperience by Kentico Commerce implementation for B2C with 50,000 products and a clear plan to expand to 150,000 products for B2B. The project initially ran in a hybrid architecture using the Kentico Xperience 13 commerce bridge, and after the release of native commerce for Xperience by Kentico, it was migrated to a clean, fully native implementation in just one month. Xperience by Kentico Commerce proved highly flexible for custom commerce needs, while its similarity to the Kentico Xperience 13 approach made team onboarding and adoption smooth."
"Our site handles teacher and student subscriptions, and the ability to tie in our commerce, subscriptions, and our bookkeeping software together was a must. The customization abilities in Xperience by Kentico's commerce and their APIs made this a reality, allowing us to take orders on our site, generate invoices, and accept payments on our bookkeeping software, and then set up the subscriptions automatically; cutting our ordering processes down from 15-30 minutes per order to nothing."
The Bottom Line for Commerce
The transaction-first vs. experience-first question was never about feature lists. It's about how commerce is set up in your architecture and how the architecture is held together.
For content-led organizations, keeping commerce inside the DXP means the sale stops being a separate system to maintain and becomes part of the same experience that earns it. Content, campaigns, personalization, and the transaction share one view of the customer, with nothing to sync and nothing to reconcile.
So, the next step isn't a longer commerce feature list. It's seeing what commerce can do when it’s located right where your content is, too.
Ready to see it in practice? Book a demo of digital commerce in Xperience by Kentico, or download our commerce planning ebook to map out your own experience-first strategy.
Frequently Asked Questions
Transaction-first commerce, like Shopify, is built around the sale itself: storefront, checkout, payments, and fulfillment come first, and content and marketing support them. Experience-first commerce, like Xperience by Kentico, treats the transaction as one step in a broader relationship, so commerce lives in the same platform as your content, personalization, and customer data. The difference isn't feature count; it's what sits at the center of the experience.
Not in every case. If your business is a high-volume retail operation built on complex logistics, marketplaces, or point-of-sale, a dedicated commerce platform is likely the better fit. If content and experience are what earn the sale, running commerce inside your DXP removes the silos a standalone store creates. And when you do need a dedicated retail engine, Xperience by Kentico integrates with it cleanly, Shopify included, so it's never an either/or.
Yes. Catalog size isn't the dividing line. Implementations on Xperience by Kentico range from focused membership and education sites to a manufacturer catalog of 50,000 products scaling toward 150,000. What determines fit is whether the experience around the product drives the sale, not how many SKUs you carry.
Xperience by Kentico provides the commerce building blocks: cart persistence, price calculation, order creation, customer and order management, and promotions. Your team, or your implementation partner, builds the storefront and checkout on top, once, inside the platform you already run. It's a one-time build, in contrast to running and integrating a separate commerce platform for as long as you own it.
Get ready for your upgrade
Upgrading from Kentico Xperience 13 to Xperience by Kentico gives your marketing and development teams a unified and future-proof platform with native AI that reduces complexity, and helps you create more impactful customer experiences.
