Most ecommerce businesses do not need custom software. Shopify, WooCommerce, BigCommerce, and their app ecosystems are mature enough to handle the vast majority of online retail operations. I want to be clear about that up front because there is a lot of money wasted rebuilding things that existing platforms already do well. That said, there is a real category of ecommerce needs that platforms and their app stores cannot meet, and understanding where that line falls is the most valuable thing I can tell an ecommerce operator who is wondering whether to build something custom.

When the Platform App Store Is Not Enough

The signal that you need custom development is usually one of these situations: your product configuration or pricing logic is too complex for the platform’s variant system — custom bundles, configurable assemblies, quote-based pricing, or dynamic pricing based on customer tier or order history. You sell wholesale and retail from the same catalog with genuinely different pricing rules, minimums, and payment terms, and the platform’s B2B features do not model your specific agreements. Your inventory lives in an ERP or warehouse management system that does not have a native integration with your storefront platform, and the third-party connectors all have critical gaps in how they handle edge cases. You need post-purchase logic that the platform does not support: custom subscription billing cycles, loyalty redemption rules, or order modification workflows that your fulfillment team needs after checkout is complete.

Custom Product Configurators

One of the most common ecommerce custom builds is a product configurator — a tool that lets a customer specify a custom product, see a price that updates in real time as they make selections, and place an order that carries the full specification through to fulfillment without requiring a sales rep to interpret a vague order note. Shopify’s native variant system caps at one hundred variants. For a product with five attributes and ten options each, that cap is hit immediately. A custom configurator, built as a Shopify or WooCommerce extension, handles arbitrary complexity, validates incompatible combinations, generates a SKU or specification document for fulfillment, and integrates with the platform’s cart and checkout without requiring the operator to replatform their entire store.

Manufacturers and companies selling configured products — custom signage, promotional merchandise, made-to-order furniture, configurable software bundles — are the most common clients for this type of build. The configurator becomes a direct revenue driver by enabling online sales of products that previously required a quote-to-order process with a sales rep involved.

ERP and Inventory Integration

The most complex and expensive ecommerce custom builds I do are ERP integrations. When a business runs its inventory in NetSuite, SAP, a legacy system, or a custom warehouse management platform, and sells on Shopify or WooCommerce, the integration is never as simple as the middleware vendors suggest in their marketing. Stock level synchronization, SKU and variant mapping, order routing and split fulfillment, return processing, and invoice reconciliation all have edge cases that generic connectors handle poorly — often silently, without flagging the error until there is a customer complaint or an audit discrepancy.

A custom integration built for your specific ERP version, your specific data model, and your specific business rules is more reliable and easier to maintain than a generic connector. It also handles the edge cases explicitly rather than ignoring them. The initial build cost is higher, but the ongoing cost of connector failures, manual corrections, and customer service time from oversell errors often makes the custom build less expensive over three years.

Subscription and Recurring Order Logic

Subscription ecommerce is well-served by platforms like ReCharge and Skio for standard use cases — fixed-quantity subscriptions, standard billing intervals, basic pause and cancel flows. The custom layer is needed when your subscription logic does not fit the standard model: variable quantity subscriptions where the amount shipped changes based on usage data or customer input, subscription boxes with rotating contents that need to be planned and assigned before they ship, subscriptions that bundle digital access with physical product fulfillment, or multi-tier subscription programs with different fulfillment rules and pricing at each level.

B2B Wholesale Portals

Selling wholesale through an ecommerce platform requires a customer experience that is fundamentally different from retail: account-specific pricing that may differ from the public price list, minimum order quantities by product category, net payment terms with invoice generation rather than immediate charge, purchase order number capture, and sometimes a multi-step approval workflow before an order is released to fulfillment. Shopify Plus and WooCommerce have B2B features, but they are general-purpose. A custom wholesale portal — built on top of the existing platform or as a separate authenticated application — models the exact rules your wholesale accounts expect and integrates with your accounting system for invoice tracking and payment reconciliation.

Scoping a Custom Ecommerce Build

The workflow mapping session I do before any ecommerce build focuses on two things: where orders fail or require manual intervention after they are placed, and where the platform configuration is forcing the business to operate around a rule that does not fit. Those two questions almost always surface the right build. Custom ecommerce development starts around $9,500 for a focused extension; full ERP integrations or custom configurator builds are larger depending on complexity. The honest answer sometimes is that a different platform or a different app, configured correctly, would solve the problem without a custom build. I will tell you that if it is true, because a bad custom build is worse than a well-configured off-the-shelf solution.

The software development work I do for ecommerce clients is almost always additive — extending an existing platform rather than replacing it. That approach keeps scope and cost contained while solving the specific problem that is limiting revenue or creating operational overhead that scales with order volume.