Implement or migrate your storefront to VTEX's headless technology with a team specializing in architecture, integrations, shopping experience, technical SEO, and continuous evolution.
e-Plus has been a VTEX partner for over 10 years, serving projects ranging from accelerated B2C projects using Fast Layout to B2B and omnichannel operations with advanced integrations and business rules.
FastStore
VTEX FastStore is VTEX's headless storefront framework, developed with React, Next.js, GraphQL, and Jamstack architecture. It separates the shopping experience from the platform's commerce services, allowing you to create fast, customizable stores integrated with VTEX's catalog, search, checkout, and other capabilities.
Architecture developed with a focus on speed and stability, with automated Lighthouse testing and quality control before deployments. The final result also depends on content, integrations, scripts, and implementation decisions.
The storefront is decoupled from VTEX commerce services. This allows you to customize the experience and evolve the front-end without rebuilding the entire operation.
FastStore combines static generation, server-side rendering, and dynamic content as needed for each page, reducing latency and improving stability during periods of high traffic.
Support for titles, descriptions, metadata templates, canonical tags, and search engine-accessible HTML content. The implementation should complement this foundation with information architecture, content, and structured data.
Content, pages, and sections can be managed by the VTEX CMS, with an integrated workflow for editing, previewing, and publishing within the project.
Integration with VTEX services and APIs, including catalog, checkout, search, session, pricing, and promotions, as well as the ability to connect ERPs, PIMs, CRMs, and third-party services.
Speed isn't a technical vanity feature—it's one of the metrics most correlated with e-commerce conversion. That's why performance is at the heart of the FastStore architecture, not an extra feature.
The increased conversion rate observed in a Google and Deloitte study, after a 0,1s improvement in mobile speed for retail websites — is not a guarantee of results for individual projects.
According to data from Think with Google, a significant percentage of mobile visitors abandon a website that takes more than 3 seconds to load.
This is the benchmark performance target for VTEX FastStore projects in Google PageSpeed Insights — the final result depends on the content, integrations, and scope of each implementation.
Sources: "Milliseconds Make Millions" study (Google/Deloitte) · Think with Google · VTEX FastStore official documentation
VTEX annually recognizes the best implementation partners through the VTEX Quadrant. e-Plus has been part of the Quadrant since its first edition and has been a certified VTEX partner since 2015 — more than 10 years of continuous partnership, bringing the credibility and trust of a company that has implemented everything on this platform: from rapid deployment in FastStore to complex architectures for highly complex B2B and omnichannel operations.
I want a certified VTEX partner.
Over 10 years of continuous partnership with VTEX (since 2015)
The same FastStore technology can support both a B2C project with accelerated delivery and a B2B or omnichannel operation with advanced integrations, journeys, and business rules.
e-Plus proprietary product built on VTEX FastStore technology. Delivers a B2C store structure ready to be adapted to the brand identity, with defined scope, essential integrations, and an accelerated timeline.
Customized implementation for B2C, B2B, and omnichannel operations that require specific journeys, deep integrations, and greater freedom in experience architecture.
Two delivery methods, one single technology behind it: the headless architecture of VTEX FastStore.
Fast Layout is e-Plus's accelerated deployment product — a ready-made FastStore structure, tested and tailored to your brand identity. Created for brands that already have operations and need to digitize quickly, without sacrificing a true architecture.
The best architecture depends on the store's current situation, existing integrations, desired front-end freedom, and performance and evolution goals.
| What to evaluate | CMS Portal legacy | Store Framework VTEX IO | VTEX FastStore |
|---|---|---|---|
| Architectural model | Templates and pages managed within the VTEX admin panel. | Native blocks configured via Site Editor, with VTEX IO apps. | Headless storefront, with decoupled front-end in React/Next.js |
| Main focus | Quickly publish pages within the standard VTEX template. | Balance between editing agility and native components. | Performance, deep customization, and modern architecture. |
| Customization method | Limited to the templates and options available in the CMS. | Configurable blocks, with VTEX IO apps for specific rules. | Open source React/Next.js code, with front-end freedom. |
| content management | VTEX legacy CMS, with direct page editing. | Site Editor, with blocks editable by the content team. | VTEX CMS integrated into the project, with preview and publishing workflow. |
| Development and deployment workflow | Changes made directly in the production environment | Publishing via isolated workspaces before production. | Proprietary deployment pipeline, with testing before each release. |
| Integration with VTEX IO applications | Limited | Native — built on top of VTEX IO itself. | Through VTEX APIs and services, without relying on the same app base. |
| Performance potential | It depends on the configuration and templates used. | Well, with native platform optimizations. | Tall, with architecture designed from the outset for Core Web Vitals. |
| Front-end flexibility | Low — restricted to existing templates | Medium — native blocks plus custom apps | Alta — decoupled and fully customizable front-end |
| Most suitable scenario | Stores still operating under the legacy model, currently under evaluation. | Operations that prioritize editing agility with custom-built apps. | Projects that prioritize performance, front-end freedom, and evolution. |
From diagnosis to continuous improvement, each step has a clear objective — so you know exactly what to expect at each stage of the project.
Mapping the current operation, project objectives, existing integrations, and technical and business requirements.
Choosing the implementation model — Fast Layout or custom design — and defining the storefront architecture, integrations, and infrastructure.
Defining the browsing and shopping experience, visual identity, and content structure for each page.
Building the storefront in FastStore, with the necessary integrations for catalog, checkout, search, payment, and other services.
Configuration of metadata, structured data, URLs, redirects, and measurement tools.
Functional testing, performance validation with Lighthouse, and homologation in a controlled environment before publication.
Publication of the store in production, with technical support for the launch.
Support, performance, new features, and continuous operational evolution after go-live.
It's VTEX's official headless architecture for building storefronts — built in React and Next.js, with static generation, server-side rendering, and dynamic content as needed for each page, integration via GraphQL, and a focus on Core Web Vitals.
No. Fast Layout is e-Plus's accelerated deployment product, built on VTEX's own FastStore technology. It delivers a ready-to-use FastStore structure tailored to your brand, with essential parameter settings — for brands that need to go live quickly without sacrificing a true architecture.
A Fast Layout project typically goes live within a few weeks, with layout, essential integrations, and go-live included in the scope. Custom FastStore projects, with deep integrations to ERP, PIM, and marketplaces, have a timeline defined on a case-by-case basis, always with a contractual deadline and dedicated teams.
Yes. The same headless architecture that supports a fast B2C store also supports B2B operations with price lists, minimum order quantities, and ERP integration — the difference lies in the implementation path: Fast Layout for the most straightforward scenario, and a custom FastStore project for advanced integrations and business rules.
Speed can influence the shopping experience and conversion, especially on mobile devices. A study conducted by Google and Deloitte observed that a 0,1-second improvement in mobile speed metrics was associated with an average 8,4% increase in conversion rates for participating retail websites. This does not guarantee results: conversion also depends on the offer, experience, media, checkout process, and operation.
The implementation (Fast Layout or a customized FastStore project) is the foundation — the continuous evolution of the operation (performance, CRO, traffic, strategic CS) is done through CS Flex, e-Plus's continuous management model. Many clients naturally migrate from implementation to this recurring support.
VTEX IO is VTEX's development platform. Store Framework is a storefront solution built on this platform, with native components and integration with Site Editor. VTEX FastStore, on the other hand, uses a headless architecture based on Next.js and Jamstack, with the front-end decoupled from VTEX's commerce services.
Companies that are on a legacy CMS Portal, facing recurring performance issues, needing more freedom on the front-end, planning a complete store redesign, growing in B2B or omnichannel operations, or seeking a more controlled and scalable architecture.
It provides a technical foundation prepared for SEO — metadata, structured data, URLs, and rendering suitable for search engines. Ranking also depends on content, information architecture, indexable pages, authority, links, and continuous execution.
Currently, VTEX recommends FastStore v4 for new projects. This version brought changes to architecture, dependencies, performance, and localization—therefore, it's important that your implementation follows the latest version and best practices.
The content is managed by VTEX's CMS, with an integrated editing, preview, and publishing workflow—allowing the editorial team to update pages and sections planned in the scope without needing to develop content for each change.
The investment depends on the scope of the layout, the necessary integrations, the volume of business rules, the B2C, B2B or omnichannel model, any data migration, the timeline and the implementation model — Fast Layout or custom project.
Fill out the form below and speak with an e-Plus specialist about your situation.
Tell us a little about your operation. An e-Plus specialist will analyze your situation and indicate the most suitable path between Fast Layout, custom design, or evolution of the current architecture.
Receive contact from one of our specialists by filling out the form below or via WhatsApp Tel: +55 11 98863-7077