A Director of eCommerce explains the CEO wanted AI in the buyer experience by end of year. The CMO had budget for AI tooling. The CIO had concerns about data security and integration. The Chief Data Officer was protective of the customer data layer. The Director of eCommerce, technically responsible for the buyer experience, had no real authority over any of the upstream systems the AI would depend on.
Six months later, four pilots had launched. None had scaled. The post-mortem identified the technical reasons. Stale data. Latency between systems. Integration gaps. None of those were the actual reason.
The actual reason was that nobody owned the AI initiative end to end. The work was distributed across four functions, none of which controlled all the inputs they needed, and the accountability for outcomes was diffuse enough that nobody could be the person whose performance review was on the line.
This is the org-chart problem nobody is solving. And it is the single most common cause of stalled AI investment we see in enterprise B2B.
Why ownership is so unclear
AI-ready commerce sits at the intersection of four traditional functions, each of which has legitimate claims and equally legitimate gaps.
eCommerce owns the buyer experience and the commercial outcome, which makes them the natural home for AI features that touch the storefront. They typically do not own the ERP, the PIM, the CRM, or the integration layer that AI features depend on. Their authority ends where the storefront ends, and AI features almost never end at the storefront.
IT owns the systems and the integration plumbing. They have the architectural authority to make AI-ready commerce work. They do not typically own the customer experience or the commercial outcome, which means AI features built primarily by IT risk being technically excellent and commercially uninteresting.
Data and Analytics owns the customer data layer, the data warehouse, and increasingly the governance frameworks AI requires. They have the substrate. They are rarely staffed for commerce-specific governance, and their priorities span every function in the enterprise, not just commerce.
Marketing often holds the budget. AI tooling, MarTech, personalization, and content engines frequently sit under a CMO. Marketing leadership has the funding authority. They typically do not have the operational authority over the systems where the AI actually runs.
The result, in most enterprises, is that AI initiatives have funding but no clear ownership. Or ownership but no funding. Or both, but split across four leaders whose incentives are not perfectly aligned.
Why this is harder than it looks
The instinct most enterprises have is to solve this by appointing a Chief AI Officer or by creating an AI Center of Excellence. Both can work. Both also tend to create new accountability gaps without fully closing the old ones.
A Chief AI Officer at the C-level can drive strategy and prioritization. They rarely have direct control over the four functions that have to coordinate. They become a fifth voice in the room rather than a clear decision-maker.
An AI Center of Excellence can build technical capability and provide reusable infrastructure. They are typically a service organization, not a decision-making one. They support AI work across the enterprise without owning any specific business outcome.
Neither solves the underlying problem, which is structural rather than personnel. The work of AI-ready commerce spans the org chart, but the accountability has to land somewhere singular.
What works
Across the enterprise B2B commerce organizations we have worked with most recently, three patterns are producing real results.
Pattern one is naming a single accountable executive for the commerce AI outcome, with explicit cross-functional authority. This is typically a VP of Digital Commerce, a VP of Customer Experience, or in some cases a newly created Chief Commerce Officer role. The role is given a P&L, a defined set of AI-related outcomes, and the authority to convene IT, Data, and Marketing leadership to deliver against those outcomes. Critical detail: the role has to have a P&L, not just a project. Cost centers cannot drive AI commerce. Profit centers can.
Pattern two is establishing a commerce-specific data and integration governance group, separate from the enterprise-wide data team. This group owns the substrate that AI features depend on. PIM, ERP-to-commerce integration, customer data hygiene specific to commerce, and the integration patterns that keep all of this current. We have written about the architecture this group has to operate. Without dedicated ownership of that substrate, every AI feature inherits the same upstream gaps over and over.
Pattern three is making the accountability explicit at the metric level. Every AI initiative should have a single owner whose performance is measured against its outcomes. Distributed accountability is functionally no accountability. The Director or VP whose name is next to the AI line item in the operating plan is the person who has to make it work. Everyone else is supporting.
How to get this conversation started
For Directors of eCommerce inheriting an AI mandate without the org-chart authority to deliver on it, the most useful framing in leadership conversations is to make the accountability problem visible.
A specific question worth raising in the next leadership meeting: "If our AI commerce initiative slips by a quarter or fails to hit its outcome targets, whose performance review reflects that?" If the answer is unclear, the ownership is unclear. If the ownership is unclear, the project is structurally underwritten to fail.
A second question worth raising: "Who has the authority to make trade-off decisions across the four systems this depends on?" If the answer is "we will work it out across teams," that is an organizational risk, not a coordination success.
A third question worth raising, particularly for organizations new to this conversation: "What is the difference between funding an AI initiative and owning an AI initiative?" Most enterprises are currently funding without owning. The gap is exactly what causes pilots to stall in month six.
What good ownership looks like in practice
A well-structured commerce AI initiative has one accountable executive with cross-functional authority, a defined operating model that specifies who decides what, a dedicated governance group for the data and integration substrate, and explicit performance metrics tied to individual owners. The technical pieces matter, but they sit on top of an accountability structure that has to be sound before the technology has a chance to work. This is also why an outside eCommerce technology assessment often reframes the AI conversation in ways internal teams struggle to do on their own. The diagnostic is part technical and part organizational. The two are inseparable.
AI in B2B commerce is not, in the end, a technology problem. It is a coordination problem dressed in technology vocabulary. The enterprises that solve the coordination first deliver AI value that compounds. The ones that solve the technology first end up funding the coordination work later, at higher cost, with more political damage along the way.
The org chart is where AI commerce is won or lost. The technology comes second.
FAQs
Q: Who should own AI in an enterprise commerce organization?
A: A single accountable executive with cross-functional authority and a P&L. In most enterprises this lands with a VP of Digital Commerce, VP of Customer Experience, or a newly created Chief Commerce Officer. The role has to have explicit authority to convene IT, Data, and Marketing leadership, plus performance metrics tied to commerce AI outcomes. Distributed ownership across four functions is the most common pattern, and it is the most common reason AI initiatives stall.
Q: Does a Chief AI Officer or AI Center of Excellence solve the ownership problem?
A: Partially, and not on their own. A Chief AI Officer adds strategic clarity at the C-level but typically does not have direct control over the four functions that have to coordinate. An AI Center of Excellence provides reusable capability but is a service organization, not a decision-maker. Both work better as supporting structures around a clearly accountable commerce executive, not as replacements for one.
Q: How do you structure governance for AI-ready commerce data?
A: A commerce-specific data and integration governance group, separate from the enterprise-wide data function. This group owns PIM, ERP-to-commerce integration, customer data hygiene specific to commerce, and the integration patterns that keep all of it current. They report into or coordinate closely with the commerce-accountable executive. Without dedicated commerce data governance, every AI feature inherits the same upstream gaps repeatedly, which is the most common reason pilots fail to scale.