Every quarter, I meet at least two or three distributors who tell me the same story. They went to their ERP vendor — Tally, SAP Business One, Oracle NetSuite, sometimes even a custom-built system — and asked for an ecommerce module. The vendor said yes, quoted a number, and six months later the distributor has a "portal" that nobody wants to use.
This is not a technology failure. It is an architectural mistake. And it starts with a fundamental misunderstanding of what an ERP is designed to do.
ERPs Solve Back-Office Problems. Commerce Solves Front-Office Problems.
Your ERP exists to manage inventory, process accounting entries, handle compliance, generate invoices, and track purchase orders. It is an internal tool built for internal users. The interface reflects this — dense tables, complex navigation, workflows designed for trained operators who use the system eight hours a day.
Now think about what your dealers want when they place an order online. They want to see real-time stock. They want pricing that reflects their specific tier, region, and negotiated discounts. They want to search by product name, filter by category, compare options, and check out in under two minutes. They want this on their phone, at 11 PM, without calling anyone.
These are fundamentally different design problems. An ERP interface optimised for a warehouse manager is not going to satisfy a dealer who is used to ordering from Amazon or Flipkart in their personal life. The UX gap between what ERP modules deliver and what modern B2B buyers expect is enormous — and it is growing every year.
ERP Vendors Sell Modules, Not Commerce Capability
When your ERP vendor offers you an ecommerce add-on, they are selling you a module — a piece of software that extends their existing system. They are not selling you a commerce capability.
What is the difference? A module is a feature set. A commerce capability is a business outcome. It includes the technology, yes, but also the pricing logic, the credit rules, the catalogue structure, the search experience, the mobile responsiveness, the payment gateway integration, the dealer onboarding flow, and the ongoing optimisation that turns a portal into a revenue channel.
ERP vendors do not have commerce expertise. Their core competence is back-office operations. When they build an ecommerce module, they build it the way they build everything else — as a data management interface with a web front-end bolted on. The result looks like an ERP screen with a different skin. Your dealers take one look at it and go back to WhatsApp.
I have seen this pattern at companies doing ₹50 Crore in revenue and companies doing ₹5,000 Crore. The scale is different. The mistake is the same.
The Correct Architecture: A Separate Commerce Layer
The right approach is to treat your ecommerce platform as a separate application that integrates with your ERP via APIs. Your ERP remains the system of record for inventory, pricing master data, and financial transactions. Your commerce platform handles the customer-facing experience — catalogue, search, cart, checkout, order tracking, and communication.
This separation gives you three critical advantages.
First, you can choose the best technology for each job. Your ERP can be SAP or Tally or a custom system — it does not matter. Your commerce layer can be Shopify, Bagisto, Medusa.js, or any platform that fits your specific use case. They talk to each other through well-defined APIs, and each system does what it is best at.
Second, you can evolve the commerce experience independently. When you need to add a new payment method, launch a mobile app, create a flash sale mechanism, or redesign the catalogue — you do it on the commerce platform without touching your ERP. This is critical because ERP changes are slow, expensive, and risky. Commerce changes need to be fast, iterative, and frequent.
Third, you protect your ERP investment. Your ERP is stable, tested, and your finance team depends on it. The last thing you want is an ecommerce module introducing bugs, performance issues, or data integrity problems into your core financial system. A separate commerce layer with API integration keeps the blast radius contained.
How to Get This Right Before Writing a Single Line of Code
The architecture decision is not the first decision you should make. The first decision is whether digital commerce makes financial sense for your business at all. Before you evaluate any platform — ERP module or standalone — you need a financial model that answers three questions: What will this cost over three years? What revenue will it generate? What is the break-even timeline?
This is exactly what a Digital Commerce Blueprint engagement covers. It is a structured process that starts with your business model, your dealer base, your current operations, and your financial reality — and produces a detailed roadmap that includes architecture recommendations, platform evaluation, cost projections, and an implementation timeline.
The Blueprint does not start with technology. It starts with your P&L. Because the most expensive technology mistake is not choosing the wrong platform — it is choosing any platform before you understand the economics.
The Bottom Line
If your ERP vendor is pitching you an ecommerce module, ask them three questions. First, show me a B2B distributor in India who is running a successful digital commerce operation on this module. Second, what is the total cost of ownership over three years including customisation, integration, and maintenance? Third, who will design the pricing logic, credit rules, and dealer onboarding experience?
If they cannot answer all three convincingly, you do not have a commerce solution. You have a module looking for a problem.
Your ERP should do what it does best — run your back office. Your commerce platform should do what it does best — sell to your customers. Keep them separate, integrate them properly, and build the business case before you build the technology.
That is the approach that works. I have built it at a ₹10,000 Crore company. The same principles apply at ₹50 Crore.
Farscape helps distributors and manufacturers build profitable digital commerce operations. If you are evaluating technology options for B2B ecommerce, start with a free 30-minute diagnostic call.
