VUE STOREFRONT / VSF 1 + VSF 2

Your storefront.
Built for
your customers.

Build, support and improve your Vue Storefront. We connect the shopping experience to Magento and your business systems, with hands-on experience across VSF 1, VSF API and VSF 2.

Discuss your storefront

A new storefront.
Your Magento behind it.

What is Vue Storefront?

It is the part of your online store customers see and use: product pages, search, the cart and checkout. It replaces the customer-facing Magento theme with a separate web application, giving you more freedom over design, mobile experience and frontend releases. Your team keeps managing products and orders in Magento.

How does it connect to Magento?

The storefront exchanges data with Magento through APIs. VSF 1 typically uses VSF API, with catalog data indexed in Elasticsearch for fast browsing. VSF 2 uses a Magento integration and middleware. Cart, account and checkout requests reach the commerce backend, where prices, stock and orders are validated.

When does it make sense?

When Magento works for your business but its storefront limits the experience you want to offer. A separate frontend can help with a distinctive buying journey, PWA features or targeted performance improvements, without replacing the whole commerce platform.

What is the trade-off?

A separate frontend needs its own deployment and maintenance, and extensions with customer-facing features may need integration work. If your current theme meets your needs, improving it may be simpler. We assess the business benefit, existing customizations and operating costs before recommending VSF.

What we can build.

From a focused improvement to a connected commerce application. Explore the areas we can take on with Vue Storefront.

Vue Storefront 1 & VSF API

Develop and maintain VSF 1 storefronts and VSF API integrations with Magento. Improve catalog, cart and checkout journeys while preserving the customizations your business relies on.

Vue Storefront 2 development

Adapt carts, checkout and customer account journeys to the business. Verify the full path against the connected commerce platform instead of treating the UI as a separate source of order state.

Commerce API & middleware integration

Review the connection between the storefront and backend. Normalize contracts in the integration layer and handle authentication, failures and request lifetimes without duplicating rules in components.

Custom storefront development

Implement agreed promotions, product options or buying flows. Assess whether the existing integration supports the requirement before adding custom frontend and backend behavior.

Architecture & modernization

Review the installed version, dependency support and integration contracts. Keep working parts where they serve the business; plan upgrades around a concrete benefit, with regression checks and a staged rollout.

Maintenance & support

Investigate rendering and integration issues, protect existing purchase flows and assess dependency risks. Agree a realistic maintenance or migration path for the specific installation.

Get the first release into use.

Keep delivery focused.

Reuse the store’s working components and integration contracts, then deliver one customer journey at a time. Check the installed versions and customizations first so a seemingly small interface change does not introduce an unexpected platform migration.

Make the next release easier.

Agree acceptance criteria and ownership before development. Hand over working code, relevant tests and release instructions so the team can continue with a clear view of the decisions made.

Explore MVP development

Stable under load.

Follow the whole request.

VSF API backed by Elasticsearch can handle 1,000+ requests per second for catalog reads. Serving product listings, filters and product data from the search index keeps that traffic away from Magento’s transactional database. We tune indexing, queries and caching, then verify throughput on your catalog and infrastructure. Cart, checkout and payments are assessed separately against their own backend dependencies.

Check the expected demand.

Agree the critical journeys, traffic model and response-time targets. Use test results to prioritize changes and verify the affected flows again. Framework choice alone is not evidence of capacity.

Explore load testing

Before we start.

Do you still work with Vue Storefront 1?

Yes. We support and develop VSF 1 as well as VSF 2, including Magento and VSF API integrations. We assess the installation and its dependencies individually; a version number alone is not a reason to replace a working store.

Can we move to modern Nuxt without replacing the backend?

That may be possible when the commerce APIs cover the required journeys. We assess middleware, sessions and integrations and plan a staged transition rather than assume a drop-in upgrade.