Complete VTEX Guide: Everything About the E-commerce Platform

VTEX is one of the most relevant e-commerce platforms in Latin America. Founded in Brazil in 2000, it now serves over 2,500 stores across 38 countries, processing billions in GMV annually. The VTEX ecosystem goes far beyond a simple shopping cart: it includes a native marketplace, OMS (Order Management System), logistics module, seller program, CMS and a complete development runtime. This guide brings together everything you need to know to make informed decisions about the platform, from technical architecture to real implementation and operational costs.

VTEX Architecture: CMS, IO and FastStore

VTEX has gone through three frontend generations. Legacy CMS (Portal/Sites) is the original version, based on HTML/CSS/JS templates with proprietary controls. It still works but is officially deprecated and receives no new features. VTEX IO (Store Framework) is the second generation: it uses declarative React blocks in JSON, theming via CSS Handles and a robust app ecosystem. It is the stable version with the largest number of available apps and the biggest developer community. FastStore is the third generation and the most modern. Built on Next.js, it delivers server-rendered pages with minimal hydration, Lighthouse scores consistently above 90 and a development experience with pure React and Tailwind CSS. For new projects in 2025, FastStore is the recommended choice when performance is a priority. Store Framework remains valid for operations that depend on the existing app ecosystem or lack the budget to rebuild the frontend.

VTEX for whom? Ideal profile

VTEX primarily serves mid-to-large operations. The ideal profile includes: revenue above $60K per month, catalog with more than 1,000 SKUs, marketplace needs (selling or being a seller), integration with ERPs like SAP, TOTVS or Oracle, and B2B operations with complex pricing rules and commercial conditions. It is also suitable for companies needing customized checkout, multiple commercial policies (pricing by region, channel or customer cluster) and advanced logistics with multiple shipping points. It is not recommended for small operations with revenue below $20K per month, unless the growth plan justifies the investment. The entry cost is high and operational complexity requires a dedicated technical team or partner agency.

Ecosystem: Apps, integrations and marketplace

The VTEX App Store has hundreds of native and third-party apps: reviews (Yotpo, Bazaarvoice), search (Algolia, SearchandISe), payments (Adyen, Stripe, PayPal), logistics (ShipStation, EasyPost), marketing (Klaviyo, Mailchimp) and analytics (Google Analytics 4, Hotjar). VTEX's native marketplace allows any store to become a marketplace receiving sellers, or a brand to connect as a seller on existing marketplaces via native integration. ERP integrations are done via REST APIs and webhooks. SAP, Oracle, NetSuite and Microsoft Dynamics have ready connectors or dedicated middleware. For systems without a connector, VTEX exposes documented APIs for catalog, orders, pricing, inventory, logistics and CRM.

Performance and Core Web Vitals on VTEX

Performance has historically been VTEX's Achilles heel. Stores on Legacy CMS or Store Framework with many installed apps frequently show Lighthouse scores between 30 and 50. The reason: excessive JavaScript bundles, poorly optimized third-party apps, fonts without font-display swap and images without defined dimensions. To achieve Lighthouse 90+, there are two paths. The first is optimizing within Store Framework: audit installed apps removing non-essential ones, implement lazy loading on images and components below the fold, use preload on the hero image, configure GraphQL cache correctly and minimize custom CSS. The second path is adopting FastStore or a headless frontend like deco.cx. In this model the VTEX backend continues processing orders, but the lightweight frontend delivers native performance without needing to optimize app by app. For new projects where performance is a priority, the second path is recommended.

How much does a VTEX store cost

VTEX costs break down into three pillars: platform fee, implementation and ongoing maintenance. The platform fee includes a fixed monthly charge plus a percentage of GMV (revenue share), which varies by contract but generally falls between 1% and 3% of gross revenue. Implementation of a VTEX store with custom theme, ERP integrations and complete go-live starts at $5,000 for simple projects and can reach $30,000 or more for complex operations with marketplace, B2B and multiple integrations. Monthly maintenance (bug fixes, new features, support) costs between $1,000 and $4,000 depending on scope and operational complexity. For a complete cost breakdown, check our dedicated article about how much a VTEX store costs.

VTEX IO vs FastStore: which to choose

The choice between VTEX IO (Store Framework) and FastStore depends on three factors: operation maturity, technical team profile and performance goals. Store Framework is the right choice when the operation depends on ecosystem apps that do not exist on FastStore, when the team consists of developers familiar with blocks and CSS Handles, or when the budget does not allow frontend rebuilding. FastStore is the right choice when performance is a competitive differentiator, when the team masters React and Next.js, when the operation is starting from scratch or when Store Framework's technical debt has become unsustainable. Both coexist in the VTEX ecosystem and VTEX will continue supporting Store Framework in the medium term. For a detailed technical analysis, check our complete comparison between Store Framework and FastStore.

VTEX implementation checklist

A successful VTEX implementation follows clear steps. First, scope definition: catalog, integrations, commercial policies, promotion rules and logistics. Second, account setup: environment configuration, access policies, development and staging workspaces. Third, ERP integration: catalog, pricing, inventory and order synchronization. Fourth, theme development: Store Framework with custom blocks or FastStore with React components. Fifth, checkout configuration: payment methods, shipping calculation, promotion rules. Sixth, SEO and analytics: sitemap, meta tags, structured data, GTM and GA4. Seventh, QA and testing: load tests, integration tests, purchase flow validation across all devices. Eighth, go-live: DNS pointing, cache warmup, intensive monitoring for the first 48 hours. Average implementation time is 2 to 4 months for standard projects and 4 to 8 months for complex projects with marketplace and B2B.