Vendure Limitations: What Vendure Cannot Do in 2026

For merchants evaluating open-source commerce frameworks, Vendure presents an appealing proposition: a TypeScript-based, GraphQL-first platform with full code control. Alongside the developer-friendly surface sit operational considerations that growing businesses can evaluate. Vendure Core's self-managed deployment model, its subscription approach, and GPLv3 licensing create work that API-first platforms address through managed infrastructure. When you factor in cloud hosting, DevOps, and developer time, implementation costs extend beyond the initial assessment.

The space between open-source promise and production reality becomes clearer as businesses scale. Vendure Core assumes a team comfortable with modern TypeScript codebases and capable of managing infrastructure, security patching, and performance optimization when self-hosting. These capabilities use engineering resources that could focus on differentiation. Understanding these considerations helps merchants choose platforms aligned with their operational capacity and growth trajectory.

Key Takeaways

• Vendure Core is commonly self-hosted and, when self-managed, involves ongoing hosting, security, scaling, and maintenance work; Vendure also now offers Vendure Cloud as a managed runtime, currently available for design partners with general availability planned for Q4 2026
• Vendure Core does not appear to include native subscription billing; recurring models typically use custom implementation or a community/third-party plugin such as the documented Stripe Subscription or Accept Blue plugins
• Vendure v3 is GPLv3 with commercial licensing available; running a modified Vendure app internally or for a client without conveying it generally does not require public source disclosure
• Vendure Core draws on TypeScript/NestJS expertise, so teams without strong TypeScript skills can face learning curves and specialized hiring needs
• Total cost of ownership can run higher than managed alternatives once infrastructure, security compliance, and specialized developer time are included
• Vendure Core is designed for engineering teams working in TypeScript, NestJS, GraphQL, and SQL databases, so nontechnical teams may need developer support for deeper customization

Considering Core eCommerce Platform Needs: Why Vendure Might Involve Additional Development for Scalability and Feature Depth

Vendure positions itself as a modern commerce framework, and "framework" describes what Vendure Core delivers compared to a fully managed platform. The distinction matters when evaluating what your team builds versus what comes ready to use.

Unlimited Product Options and Attributes

Vendure supports flexible product modeling, and realizing that flexibility involves development work. The platform provides primitives, and assembling them into production-ready features draws on TypeScript expertise and ongoing maintenance.

Swell approaches product modeling differently. Unlimited variants and options work immediately through both dashboard and API. A merchant can create products with any combination of characteristics without developer involvement. The model editor extends this flexibility to custom data structures for business-specific requirements.

Beyond Basic: When Native Subscriptions Become Critical for Growth

Subscription commerce is one area where Vendure Core involves more assembly. Vendure Core does not appear to include native subscription billing, and recurring models typically use custom implementation or a community/third-party plugin such as the documented Stripe Subscription or Accept Blue plugins. Requirements like these are worth scoping:

• Turnkey subscriptions with flexible billing intervals
• Mixed carts combining one-time and recurring products
• Dunning management and payment retry logic
• Customer self-service portals

For businesses where recurring revenue drives growth, this involves implementation work. Building subscription logic (billing schedules, payment retry, proration, plan changes) uses engineering capacity.

Swell's native subscription engine handles flexible billing intervals, separate invoicing and fulfillment schedules, automatic payment retry with configurable dunning rules, and customer-initiated subscription management. The capability works with any connected payment gateway through an encrypted card vault, without third-party app dependencies.

The Transaction Fee Consideration: How Vendure's Payment Model Compares to Managed Alternatives

Vendure itself charges no transaction fees, a characteristic of open-source licensing. This involves context about larger cost factors that impact total payment processing economics.

The Infrastructure Responsibility

The transaction cost story involves what you manage to process payments through self-hosted Vendure:

• Payment gateway fees remain identical regardless of commerce platform
• Infrastructure costs to host payment processing workflows
• PCI scope that varies by payment integration and checkout implementation
• Security patching for payment-related updates

Managed platforms handle these responsibilities within their service structure. PCI scope and compliance responsibilities vary by payment integration and checkout implementation, so self-hosted Vendure teams evaluate PCI scope based on their gateway, tokenization, and card-data handling approach.

Payment Structures on Managed Platforms

Swell's payment abstraction layer integrates with Stripe, PayPal, Braintree, Authorize.Net, and Amazon Pay. The platform handles PCI compliance, payment security, and gateway abstraction, reducing the operational overhead merchants manage with self-hosted solutions.

For growing businesses, focusing engineering resources on revenue-generating features rather than payment infrastructure maintenance is a meaningful advantage.

Headless Architecture: Where Vendure's Headless Implementation Differs from True API-First Flexibility

Vendure offers genuine headless architecture through GraphQL APIs. The question isn't whether headless capabilities exist (they do) but whether the implementation delivers practical flexibility for diverse development teams.

The Promise and Reality of Headless: True API-First Design

Vendure's GraphQL-first architecture serves TypeScript/NestJS teams well. Type-safe queries and mutations align with modern frontend development practices. Teams preferring REST APIs or working in different technology stacks plan for additional adaptation work.

The platform assumes specific technical expertise. Organizations maintain TypeScript and NestJS proficiency to extend core functionality, customize business logic, or troubleshoot production issues. Teams without this expertise plan for learning curves or external contractor support.

Building Unique Experiences with Unrestricted API Access

Swell's unified backend API (the same API powering Swell's own dashboard and checkout) means developers can replicate or customize any native functionality. Both REST and GraphQL access points accommodate different team preferences and existing technology investments.

The developer console enables testing API calls, viewing request logs, and troubleshooting integrations without leaving the browser. The Frontend API with public key authentication handles customer-facing operations while the Backend API provides full data access for server-side implementations.

Enterprise Requirements: Vendure's Approach to B2B and Multi-Vendor Complexity

Enterprise commerce requirements (multi-vendor marketplaces, B2B customer segmentation, complex pricing structures) extend platform capabilities.

Marketplace Management: Beyond Basic Integrations

Vendure Core provides extensible commerce primitives and multi-channel capabilities, and teams building marketplace workflows on Core may use custom development. Vendure Platform adds enterprise plugins and supported capabilities for more complex B2B/DTC use cases. Features that often involve implementation on Core include:

• Split payments per vendor
• Seller onboarding workflows
• Marketplace-specific fulfillment logic

Swell includes multi-vendor marketplace capabilities with split payment functionality built into the core platform. Merchants can launch marketplaces connecting multiple vendors to customers without assembling marketplace logic from framework primitives.

Tailoring B2B Experiences: Customization at Scale

B2B commerce involves customer-specific pricing, account hierarchies, approval workflows, and custom payment terms. Vendure Platform adds enterprise B2B capabilities, while the core open-source version involves building some of these.

Swell's native B2B and wholesale features include customer group-based pricing, custom fields across all data models, and integration with B2B payment solutions like Resolve for net terms. These capabilities work immediately without custom development investment.

The Integration Ecosystem: Addressing Vendure's Third-Party Dependencies

Open-source platforms reduce vendor lock-in. In practice, that flexibility often shifts dependency from platform vendors to extension developers and integration partners.

Beyond Plugins: The Value of Ready-Made Integrations

Vendure's ecosystem includes a growing set of integrations, and the younger ecosystem can mean some connections involve custom development work. This can affect implementation timelines and maintenance responsibilities for connections to essential services.

Swell provides 40+ service integrations including:

• Email marketing: Klaviyo, Omnisend, Mailchimp
• Fulfillment: ShipStation
• Tax automation: Avalara AvaTax, TaxJar
• CMS: Contentful
• Search: Algolia

Simplifying Subscriptions: A Core Platform Advantage

The subscription path shows how building certain features can add complexity. Third-party subscription solutions introduce integration seams between checkout and subscription management, and customization scopes to their APIs rather than full platform access.

Swell's subscription management works directly with the payment gateway through an encrypted card vault. Mixed carts, flexible billing intervals, automatic dunning, and customer self-service come standard without third-party dependencies.

International Expansion Considerations: Vendure's Approach to Global Commerce Capabilities

Global commerce involves more than currency conversion. Tax compliance, content localization, and regional payment methods shape international success.

Global Commerce: More Than Just Currency Conversion

Vendure supports multi-currency and multi-language capabilities at the framework level. Implementing production-ready international commerce involves development work to handle edge cases, regional tax rules, and localization workflows.

Swell processes payments across 230 currencies and supports content localization in 170 languages. Multi-currency functionality includes explicit pricing rules per currency (for psychological pricing) or automatic exchange rate conversion, both configurable through dashboard or API.

International Tax and Localization Requirements

Tax compliance across jurisdictions involves specialized knowledge and ongoing maintenance. Self-hosted solutions place this responsibility on merchant teams, using either in-house tax expertise or integration with tax calculation services.

Swell integrates natively with Avalara AvaTax and TaxJar for automated tax calculation and compliance. Custom tax rule groups by location and product type handle edge cases through the tax settings without custom development.

Architectural Considerations: Why Vendure's Self-Hosted Model Differs from Managed Scalability

Architecture decisions made early in platform selection compound over time. The technical considerations of self-hosted infrastructure grow as businesses scale.

The Evolution of Ecommerce Architectures

Vendure represents modern open-source architecture: TypeScript, GraphQL, NestJS. A modern framework and a fully managed operational model are different things. For self-hosted deployments, Vendure involves traditional infrastructure management:

• Server provisioning
• Database administration
• Caching configuration
• CDN setup
• Security patching
• Scaling decisions

Vendure Cloud, currently available for design partners with GA planned for Q4 2026, is positioned as managed infrastructure with auto-scaling, backups, rollbacks, and monitoring, which reduces this work for teams that adopt it.

Investing in Future-Ready Technology

Swell's architecture starts from API-first principles where the same Backend API powering internal tools serves external developers. This design supports feature parity, so anything possible in the dashboard is possible through code.

The platform handles infrastructure scaling, with an uptime SLA on higher tiers. Auto-scaling, global CDN, and security updates happen without merchant involvement, freeing teams to focus on customer experience rather than server maintenance.

Advanced Commerce Features: Vendure's Approach to Subscription and Complex Fulfillment Management

Recurring revenue and complex fulfillment represent growth vectors where platform capabilities become most apparent.

Mastering Recurring Revenue: The Nuances of Subscription Management

Subscription commerce involves more than recurring charges. Successful subscription businesses use:

• Flexible billing intervals (weekly, monthly, quarterly, annual, custom)
• Separate invoicing and fulfillment schedules (bill monthly, ship quarterly)
• Mixed carts combining subscription and one-time products
• Automatic payment retry with dunning sequences
• Customer self-service for pause/resume and plan changes
• Proration calculations for mid-cycle upgrades and downgrades

On Vendure Core these typically use custom development or a community/third-party plugin, a consideration shared with other open-source alternatives like Medusa and Saleor.

Swell includes built-in subscriptions on all plans, allowing merchants to sell physical or virtual products as subscriptions and manage them from the dashboard. Official docs support flexible intervals, separate billing and fulfillment schedules, one-time items added to subscriptions, pause/resume controls, subscription notifications, card-expiration notices, and dunning actions.

Optimizing Fulfillment: From Multiple Locations to Split Shipments

Advanced fulfillment scenarios (multiple store locations, split shipments, product-specific shipping rules) use robust order management. Framework approaches involve building these workflows rather than configuring them.

Swell supports multiple store locations for shipping configuration, split fulfillment shipping order items separately, and product-specific shipping rules that override zone defaults. Swell's help documentation notes multiple store locations are not automatically considered for shipping-rate or fulfillment-logistics calculations unless handled through integrations or other workflows. Line-item shipment tracking and order print templates for packing slips come standard.

Ecosystem and Support: Comparing Vendure's Community-Driven Model to Commercial Offerings

Support models differ between open-source frameworks and commercial platforms. Understanding these differences helps set realistic expectations.

The Role of Support in Commercial Success

Vendure's open-source core relies on community support: GitHub issues, Discord discussions, and Stack Overflow questions. Commercial support through Vendure Platform involves investment, with enterprise support tiers available.

Swell provides email and chat support across all plans, with priority support on higher tiers and dedicated developer support for enterprise customers. An uptime SLA backs higher-tier plans, providing contractual assurances.

Building with Confidence: Developer Resources and Partner Ecosystems

Vendure's documentation serves TypeScript developers well. Teams outside that technical profile, or without dedicated engineering resources, plan for steeper adoption considerations.

Swell's expert partner network connects merchants with agencies experienced in headless implementations. The help center provides product guides alongside developer documentation, serving both technical and business audiences. Role-based permissions on the Unlimited plan enable team collaboration with appropriate access controls.

For businesses evaluating platform options, the choice often comes down to build versus buy. Vendure offers full control with full responsibility. Swell delivers managed infrastructure with the flexibility of headless architecture: control where it matters, automation where it helps.

Explore Swell's platform features to see how managed headless commerce addresses the considerations that self-hosted frameworks present.

Frequently Asked Questions

What technical skills does my team need to run Vendure successfully?

Vendure Core uses proficiency in TypeScript, NestJS, GraphQL, Node.js, and a SQL database such as PostgreSQL. For self-hosted deployments, your team handles server deployment, database management, caching configuration, and security patching. Organizations without existing TypeScript/NestJS expertise plan for learning curves or work with specialized contractors. Vendure Core targets engineering teams comfortable with modern JavaScript ecosystems rather than business users or generalist developers.

How does the GPLv3 license affect agencies building Vendure solutions?

Vendure v3 is GPLv3, with commercial licensing available. Vendure states that running a modified Vendure web app internally or for a client without conveying the software generally does not require public source disclosure. GPL obligations become relevant when distributing modified core Vendure packages, such as on-premise delivery, and Vendure provides a plugin exception allowing plugins under other licenses. Agencies can use commercial licensing through the Vendure Platform where proprietary core customizations matter.

Can Vendure scale to handle enterprise traffic volumes?

Vendure can scale, and for self-hosted deployments scaling responsibility rests with your team: configuring auto-scaling infrastructure, optimizing database queries, implementing caching, and managing CDN distribution. Vendure Cloud, available for design partners with GA planned for Q4 2026, is positioned as managed infrastructure with auto-scaling that reduces this work. Managed platforms generally handle scaling within the service, with uptime assurances.

What happens when Vendure releases security patches?

For self-hosted deployments, security patches involve action from your team: monitoring release announcements, evaluating patch urgency, testing updates against your customizations, and deploying to production. Organizations without dedicated security monitoring plan for exposure windows between patch release and deployment. The security maintenance responsibility is an ongoing operational consideration beyond initial implementation, and managed runtimes shift more of this to the provider.

How do Vendure's B2B capabilities compare to its DTC features?

Vendure Core focuses on fundamental commerce primitives. Advanced B2B features like organizational hierarchies, approval workflows, and role-based pricing rules are associated with Vendure Platform and its enterprise plugins. Vendure Core supports multi-channel selling, and building sophisticated B2B workflow automation on Core typically involves custom development work.