How to Turn B2B Commerce Into a Revenue Engine with Account Intelligence
May 14, 2026 • 5 Minute Read • Chris Boulanger, Managing Director, Data & Analytics
By Chris Boulanger, Managing Director, Data & Analytics, and Carrie Souza, Sr. Account Director, Commerce
A joint perspective from Verndale's Commerce and Data & Analytics practices. The first in a series on connecting commerce data to revenue.
There’s a common story in B2B ecommerce: invest in the platform, modernize the experience, and revenue will follow.
The catalog gets broader, search gets faster, checkout gets cleaner. The storefront starts to look like something that should behave like its B2C counterparts, with personalized and predictive benefits.
But there's a disconnect beneath that progress: commerce and data are still treated as separate conversations. And in B2B, that separation is expensive. Because the experience only performs as well as the intelligence behind it.
So when teams go looking for revenue impact, it’s often not there. Conversion is flat, average order value hasn’t moved, and the digitally sourced pipeline still needs to be hand-qualified before sales will act on it.
This is usually interpreted as a platform gap. It isn’t. It’s an account intelligence gap.
The platform is still essential. It's where the purchasing happens. But on its own, it can only do what it was built to do—serve distributors and customers, not know their habits, preferences, or history. The work that turns sessions and carts into revenue sits upstream of the ecommerce experience, in a layer most B2B organizations haven't yet built.
In B2B ecommerce, the unit of value is the customer account, not the single transaction. A standard order typically involves three to six people from the same purchasing organization, with multiple touches across the website, sales rep, and partner channel.
The digital commerce platform sees one slice of that account: anonymous and known web sessions, products viewed, items added, orders placed through self-service, based on product data managed in a PIM and fed into the platform. Everything else lives somewhere else:
On their own, each system is coherent. Together, they're often disconnected, making it difficult to see the full picture of a customer transaction.
When those four systems don’t speak to each other, the storefront can’t recognize the account behind the activity. Instead of driving efficiency, your tech stack creates manual work, data gaps, and lost revenue.
A returning $2M-per-year customer stops purchasing entirely because their primary contact left, and no one flagged the change.
Meanwhile, a purchaser who is three meetings deep with sales lands on a generic homepage instead of being guided toward the products, pricing, or next step tied to their active deal.
Another customer is looking for speed and wants to reorder from a previous purchase list, but the list isn't saved or isn't accessible. Instead, they go to a competitor that makes it easier to buy.
Your platform isn't broken, but the context that defines the account and that should let it remember is living in multiple systems it can't see.
Personalization can improve the B2B customer experience, especially for top accounts and product recommendations that drive cross-sell.
But it only works when it's grounded in customer identity. And that identity has to be resolved at the account level across CRM, ERP, commerce, and web. Without that foundation, personalization is limited to in-session behavior rather than the full context of the account.
Treating it as a feature within the ccommerce experience is how organizations end up two years post-launch with a more dynamic experience but no meaningful revenue lift.
Most B2B ecommerce reviews still anchor on platform telemetry like sessions, conversion rates, and checkout performance. Those numbers tell you the ecommerce experience is functioning; they don't tell you whether the right accounts are purchasing more, where margin is lost, or, when customers are shifting spend to a competitor.
Once you treat buying as account-shaped, a different set of questions comes into focus:
None of these questions can be answered solely from the commerce platform.
All of them are answerable when CRM, ERP, commerce, and website are on a common foundation, and an intelligence layer is built on top of it.
Most B2B organizations aren’t equipped to answer these questions today. And until they are, revenue will continue to stall no matter how much the platform improves.
Fixing that requires a different approach to how commerce, data, and revenue are connected.
In the next piece, we'll break down what it takes to close that gap and design for account-aware, revenue-driving commerce.