Many mid-market businesses invest in digital commerce without seeing the value they expected. That does not necessarily mean the platform is poor or the IT team lacks skill.
More often, the initiative is competing with other priorities, depends on data and processes across the organization, or lacks the ongoing ownership needed after launch.
Consider an industrial distributor with an aging ecommerce experience and sophisticated internal systems. A planned ERP change may make a commerce replatform feel like the logical next step. But if the organization does not also address product data, customer workflows, internal ownership, and ongoing improvement, the new platform may reproduce many of the same limitations.
Technology matters, but it is only one part of the digital commerce operating model.
Here are seven conditions that commonly limit the value of B2B digital commerce—and what organizations can do about them.
1. Limited Capacity and Unclear Ownership
Digital commerce competes with ERP programs, acquisitions, cybersecurity work, infrastructure needs, integrations, and other business priorities. Even a capable IT team may not have enough dedicated capacity—or the specific ecommerce, UX, product-data, and analytics expertise—to support the work continuously.
The challenge is not simply hiring more people. The organization needs to understand which skills the initiative requires, how much time those responsibilities will take, and who will own the experience after launch.
That ownership often extends beyond IT. Depending on the business, it may include:
- Ecommerce strategy and prioritization
- Product information and merchandising
- Customer research and analytics
- Platform administration
- Integration and architecture
- Content and campaign support
- Sales and service enablement
- Testing and ongoing optimization
A practical response
Define the responsibilities required to operate digital commerce, not only to implement it. Identify what the internal team can reasonably own, where dedicated capacity is needed, and where outside support may help fill a specific gap.
2. Treating Launch as the Finish Line
A digital commerce implementation should have a defined scope, budget, and completion date. But ownership of the digital experience should not end when the project closes.
Customer expectations, products, pricing, systems, and business priorities continue to change. Search terms shift. Product data needs maintenance. Buyers encounter new sources of friction. Teams discover opportunities that were not visible before launch.
Without an operating model for what happens next, even a successful implementation can lose momentum.
A practical response
Plan the transition from project delivery to ongoing operations before launch. That plan should identify:
- Who reviews performance
- How customer and employee feedback is collected
- Who owns product and account data
- How issues are prioritized
- How enhancements are evaluated
- Which teams make decisions
- What budget and capacity are available
The implementation project should end. The work of understanding and improving the experience should continue.
3. Underestimating Product Data and Integration Work
A strong storefront depends on the information and systems behind it. Search, filtering, product comparisons, availability, customer-specific pricing, account access, and ordering workflows all rely on data that is accurate, structured, and available when it is needed.
For many B2B organizations, that information is spread across an ERP, CRM, PIM, ecommerce platform, supplier files, spreadsheets, and institutional knowledge. Product photography, attribute definitions, taxonomy, technical documents, and data governance may involve several departments.
This work is rarely owned by IT alone. It requires clear responsibility for defining, creating, approving, maintaining, and distributing information across the business.
A practical response
Identify which data is essential to the first phase and where it currently lives. Then clarify:
- Who owns each type of information
- Which system should be the source of truth
- How frequently the data must be updated
- Which gaps can be addressed manually at first
- Which inconsistencies would undermine the customer experience
- How data quality will be maintained after launch
The goal is not to perfect every record before moving forward. It is to understand which data issues could prevent customers from completing important tasks.
4. Planning Without Enough Customer Evidence
Digital commerce priorities are often shaped by internal requests, competitor features, and assumptions about what customers want. Those inputs can be useful, but they do not provide the full picture.
Customer knowledge is usually distributed across sales, service, marketing, product teams, analytics, operations, and IT. Digital commerce performs better when those perspectives are brought together and supported by direct evidence.
Useful sources may include:
- Customer interviews
- Search and navigation behavior
- Support and sales inquiries
- Order-entry errors
- Checkout abandonment
- Digital adoption by customer segment
- Feedback from account managers
- Usability testing
- Quote, reorder, and approval workflows
A practical response
Combine customer feedback with behavioral and operational data. Look for recurring friction rather than isolated feature requests.
For example, customers may not ask for a new reorder tool by name. They may repeatedly email spreadsheets to customer service, call representatives to confirm previous purchases, or abandon online orders because they cannot find account-specific products. Those behaviors reveal the underlying need.
5. Choosing Technology Without the Full Operating Context
Modern commerce platforms may reduce the need for custom development and provide capabilities that were once difficult to build. But newer technology is not automatically a better fit.
A platform decision should reflect the business model, customer needs, integrations, internal skills, operating costs, data requirements, and degree of flexibility the organization needs.
A solution that appears simple during a demonstration may become more complicated when it must support:
- Customer-specific catalogs and pricing
- Multiple account roles
- Complex product configuration
- ERP-driven availability
- Sales-assisted ordering
- Quotes and approvals
- Multiple business units or regions
- Specialized fulfillment rules
A practical response
Evaluate the full operating model—not only the feature list or implementation cost.
Consider the cost and effort required to configure, integrate, maintain, support, and improve the platform over time. Be clear about where standard functionality is sufficient, where the business can adapt its processes, and where differentiation justifies additional complexity.
6. Working in Departmental Silos
Digital commerce crosses organizational boundaries. Product data may come from one team, pricing from another, customer relationships from sales, service insights from support, fulfillment rules from operations, and technical delivery from IT.
Without shared ownership and decision-making, priorities conflict and important dependencies surface too late. One team may optimize for speed while another prioritizes control. Sales may want flexibility that operations cannot support. Marketing may plan an experience without access to the product data needed to deliver it.
These are not signs that one department is failing. They are signs that the initiative needs a clearer way to make cross-functional decisions.
A practical response
Create a cross-functional group with:
- A shared objective
- Named owners
- Clear decision rights
- A prioritized backlog
- Regular performance reviews
- A process for resolving conflicts
- Visibility into technical and operational dependencies
Not every stakeholder needs to participate in every decision. The goal is to make ownership clear and ensure the right perspectives are included before decisions become expensive to change.
7. Pursuing Conflicting or Unclear Outcomes
Organizations may begin a digital commerce initiative with several valid goals: increasing online revenue, supporting sales, improving customer service, reducing order-entry work, entering new markets, modernizing technology, or strengthening the brand experience.
The challenge comes when those objectives compete or remain too broad to guide decisions.
For example, a team may want to launch quickly while also replacing several systems, improving every product record, and creating a highly customized experience. Another organization may want customers to use self-service while continuing to reward sales teams primarily for assisted orders.
When teams have different definitions of success, platform and feature decisions become harder to evaluate.
A practical response
Agree on a small number of outcomes for each phase. Those might include:
- Increasing digital reorder adoption among existing customers
- Reducing manual order-entry time
- Improving product findability
- Increasing quote-to-order conversion
- Reducing product-related support requests
- Improving account registration and onboarding
- Shortening the time required to launch new products
- Giving sales teams better visibility into customer activity
The outcomes should be specific enough to guide priorities and measurable enough to show whether the initiative is helping.
A Practical Way to Identify the Biggest Constraint
These seven conditions are connected. Limited capacity can contribute to weak data governance. Siloed planning can create conflicting objectives. A poor understanding of customer needs can lead to technology choices that solve the wrong problem.
The goal is not to address every issue at once. Start by identifying the one or two constraints most likely to limit the next phase.
|
Common constraint |
A practical response |
|
Limited capacity |
Define ownership, required skills, and realistic availability |
|
Project-based thinking |
Create a post-launch operating model |
|
Product-data complexity |
Establish ownership, governance, and phased priorities |
|
Limited customer evidence |
Combine research, analytics, and frontline feedback |
|
Poor technology fit |
Evaluate the platform within the full operating context |
|
Siloed planning |
Create cross-functional governance and decision rights |
|
Conflicting objectives |
Agree on a few measurable outcomes for the next phase |
A focused assessment can help the organization determine whether the next investment should go toward technology, data, research, team capacity, governance, or process improvement.
Digital Commerce Is an Ongoing Business Capability
Digital commerce creates value when the organization treats it as more than a technology implementation.
That means assigning ownership, focusing on a small number of customer and business outcomes, supporting the experience with reliable data, and giving cross-functional teams a practical way to make decisions together.
A new platform may be part of the answer. But the strongest results come when the technology is supported by the people, processes, information, and operating discipline needed to use it well.
A Practical Next Step
Review your digital commerce initiative against these seven areas and identify the one or two constraints most likely to limit progress.
Then define a focused response. That might mean clarifying ownership, improving data for a priority product category, researching a high-friction customer workflow, or aligning teams around a measurable outcome for the next phase.
The goal is not to transform everything at once. It is to understand what is getting in the way and focus resources where they can make the most meaningful difference.
Not Seeing the Value You Expected From Digital Commerce?
We can help you identify what is getting in the way and determine where to focus next.
Contact us to talk through your goals, systems, and current constraints.
[i] Gartner, The Key Drivers of High Regret Technology Purchase Decisions, Christopher Marshall, Hank Barnes, et al.., 26 July 2022.
