As a pioneer in the ERP-native commerce space with over twenty-five years of experience, Michael Kulik has witnessed the evolution of Microsoft Dynamics 365 Business Central from its early NAV days into a powerhouse for global trade. His perspective focuses on a critical yet often overlooked reality: as businesses grow, the very tools they add to drive expansion can inadvertently create a web of complexity that slows them down. By examining the intersection of architectural logic and real-world operational flow, he provides a roadmap for leaders who want to scale their eCommerce presence without sacrificing the structural integrity of their primary business engine. This conversation explores how to identify the subtle signs of system sprawl and the strategic necessity of maintaining a governed, single-process environment to ensure long-term agility.
Organizations often add individual tools or channels to extend functionality, but the cumulative impact eventually shifts the operating model. How do these incremental changes specifically alter daily team coordination, and what are the early signs that a governed environment is becoming unmanageable?
The shift usually starts with a single, innocent addition—perhaps a third-party tool for a specific sales channel or a custom workflow to handle a unique shipping requirement. In isolation, these choices seem like smart, agile wins, but they gradually move the “source of truth” away from Business Central and into a fragmented landscape of connected systems. Daily coordination transforms from a streamlined process into a constant game of “catch-up” where teams spend more time verifying data across different screens than actually processing orders. You know you’re reaching a breaking point when your operational experts are no longer looking for ways to improve the customer experience because they are too busy manually reconciling inventory levels between platforms. It’s a sensory overload for the staff; they feel the weight of these extra steps, and the predictability that makes an ERP valuable begins to dissolve into a chaotic mix of exceptions and workarounds.
When growth metrics like revenue remain positive, operational strain often stays hidden behind manual workarounds and frequent reconciliation tasks. What specific indicators should leadership monitor to uncover this “invisible” friction, and how can they distinguish between healthy growth and unsustainable complexity?
Leadership often falls into the trap of celebrating rising revenue while ignoring the “operational tax” being paid behind the scenes. Healthy growth should feel like a well-oiled machine accelerating, where increased volume doesn’t exponentially increase the hours required to manage it. To find the invisible friction, you have to look past the top-line numbers and monitor the frequency of manual interventions—if your team is constantly “fixing” orders before they can ship, that’s a red flag. You might see dashboards that look green and stable, yet the internal culture is one of high stress and constant firefighting. Unsustainable complexity reveals itself when you realize that doubling your order volume would require doubling your headcount just to handle the validation steps; that isn’t scaling, it’s just bloating.
As eCommerce systems expand, orders frequently pass through multiple platforms, increasing validation steps and exception handling. How does this fragmented flow affect fulfillment timelines for manufacturers and distributors, and what steps can be taken to restore a predictable, single-process workflow?
For manufacturers and distributors, predictability is the lifeblood of the business, and fragmentation is the poison that kills it. When an order has to hop through three different platforms before hitting the warehouse floor, each jump introduces a delay and a potential point of failure that erodes customer confidence. This lack of flow creates a palpable anxiety in the warehouse as fulfillment timelines become “best guesses” rather than guarantees. To restore order, you must aggressively consolidate your architecture back toward the ERP core, ensuring that validation happens at the point of entry rather than hours later. By collapsing these external silos, you remove the “hop” and return to a single-process workflow where the logic of Business Central governs the transaction from the moment the customer clicks “buy.”
Reducing complexity is often misinterpreted as removing essential capabilities or features. In a high-scale Business Central environment, how do you simplify the architecture without losing functionality, and what is the step-by-step process for ensuring operational data remains reliable during this transition?
Simplification is about refining the path, not cutting the destination; it is an architectural discipline that improves how capability flows through the entire business. To simplify without losing power, you start by auditing every external tool and asking if that function can be handled natively or through deep integration within the Business Central logic. The transition begins with mapping the current “sprawl” and identifying where data is being duplicated or manually moved, then systematically migrating those functions back into the governed ERP environment. Throughout this process, you must prioritize data integrity by ensuring that the ERP remains the undisputed master of pricing and inventory. When you remove the noise of secondary systems, your operational data actually becomes more reliable because there are fewer places for it to be corrupted or delayed.
Scaling successfully requires shifting the focus from adding new features to ensuring consistent execution across pricing and inventory. Why does operational simplicity act as a competitive advantage during rapid expansion, and what is the long-term impact on a company’s ability to respond to market changes?
In a hyper-competitive market, the ability to execute cleanly and consistently is a much more durable advantage than having a long list of niche website features. Operational simplicity allows a company to move with a level of agility that complex organizations simply cannot match; when your foundation is lean, you can pivot your strategy in days rather than months. During rapid expansion, the companies that thrive are those that can trust their automated systems to handle the load without constant human supervision. Long-term, this structural clarity means you aren’t fighting your own technology when the market shifts. Instead of spending your budget on maintaining a fragile web of integrations, you can reinvest that capital into actual growth initiatives that move the needle.
What is your forecast for Business Central eCommerce?
I believe we are entering an era where the “integrated” model will be replaced by the “unified” model, where the distinction between the ERP and the eCommerce platform virtually disappears. Businesses are tired of the friction caused by system sprawl, and I forecast a massive consolidation where the most successful companies will run 100% of their commerce logic directly inside Business Central. We will see a shift away from flashy, superficial front-end features in favor of deep, data-driven operational efficiency that allows for true global scaling. This movement will empower manufacturers and distributors to act with the speed of a startup but the structural reliability of a twenty-five-year-old enterprise. Ultimately, the future of Business Central eCommerce isn’t about more tools; it’s about better execution through architectural elegance.