B2B Integration Is Broken with Tom Flierl and Ethan Koehler

Watch on YouTube

About This Episode

Tom Flierl and Ethan Koehler, leaders at Znode (the B2B ecommerce platform acquired by Amla Commerce), address the persistent integration challenge in B2B ecommerce: integrations remain the highest-risk, most-expensive component of commerce implementations, consuming 30-40% of mid-market project budgets and even higher percentages for enterprises managing multiple ERPs. The fundamental problem stems from commerce platform architecture decisions made in the B2C era—traditional ecommerce platforms were never designed to deeply integrate with back-office systems. As companies increasingly depend on real-time inventory, pricing, and order status from ERPs, custom API integrations become scattered throughout platform code, making migrations (especially during ERP consolidation initiatives) brittle and expensive to rip-and-replace.

Znode's response is the Commerce Connector, a native integration framework baked into the platform itself—not middleware bolted on externally, but a native capability that provides a unified administrative interface for managing all data exchanges. The Commerce Connector abstracts data integration across ERPs, CRMs, WMS systems, and PIMs through configurable "data exchanges" that define source-to-target mapping, frequency (real-time, on-demand, scheduled), and authentication. Rather than eliminating custom code entirely, the framework creates configurability-first workflows with optional custom code injection where needed, allowing organizations to reduce custom development while maintaining flexibility for complex workflows and contractual relationships. For distributors, the connector unifies connections to Salesforce CRM (to sync account data and create opportunities for field activity), PIMs (to pull authoritative product content), and ERPs (to expose real-time inventory and pricing).

Znode's recent cloud-native replatforming represents an architectural choice distinct from traditional SaaS: distributed SaaS where each customer maintains their own segregated Azure SQL database (eliminating noisy-neighbor problems that plague shared-database SaaS) while still receiving continuous platform updates tested in lower environments before production deployment. This hybrid approach solves the enterprise pain point of monolithic upgrade cycles (which historically required six months of disruption and hundreds of thousands in cost) while maintaining the security and data isolation that manufacturers and distributors demand. Ethan notes that their 2026 roadmap emphasizes execution and customer enablement, with particular focus on agentic AI applications and improvements to the Commerce Connector for handling increasingly complex orchestration scenarios.

Key Themes

Notable Quotes

More Episodes

All episodes