VTEX implementation: B2B, B2C, OMS and marketplace on one platform.

Yes. VTEX sells its platform to companies across Europe, including Poland, with offices in London, Cologne, Paris, Milan, Barcelona, Lisbon and Bucharest, among others, and a store can run in Polish. Local payments and delivery such as BLIK, Przelewy24 and InPost depend on the payment provider and connector, so we check them in every project.

Public VTEX customers include OBI, which runs its online store, 349 physical stores and third-party sellers on VTEX; Whirlpool, in more than 20 countries; Mondelēz, with a B2B ordering platform for shops in Colombia and Peru; Colgate, with a store in Germany since 2025; H Mart, which moved from Adobe Magento to VTEX in seven months; and Manchester City. VTEX also lists Carrefour, Sony and Stanley Black & Decker. These are VTEX customers from VTEX publications, not LemonMind projects.

Yes. VTEX has buyer organisations with roles and cost centres, contract price lists and catalogues, quotes with approval, quick orders and punchout to Ariba and Coupa (OCI, cXML). B2B and B2C run on one platform, with separate trade policies for each channel. See also your own B2B store and your distributors.

The modules your sales model needs (storefront, B2B, OMS, marketplace), integrations with ERP, CRM, PIM, payments and delivery, the product catalogue, migration from the old platform, tests and launch. The cost of the implementation is separate from the VTEX fee and depends mainly on the number of integrations and the quality of the product data. We give the exact scope and estimate after a pre-implementation analysis, which usually takes 2 to 6 weeks. For consumer stores on other platforms, see B2C e-commerce.

In one of four ways: with Store Framework, the ready components of VTEX; with FastStore, a toolkit for fast storefronts focused on Lighthouse and Core Web Vitals scores, with an external CMS; as a fully headless frontend on the VTEX APIs, for example for a mobile app or a kiosk; and with VTEX IO apps (TypeScript, React, GraphQL, Node) for extensions of the store and the admin. We recommend the model in the pre-implementation analysis, based on your team, performance requirements and plans.

Through public APIs, or a ready connector when one fits the project. ERP sends prices, stock and B2B terms to VTEX and receives orders through order feeds or hooks; invoices and tracking go back to the VTEX OMS. Customer and B2B account data is kept in VTEX Master Data and synchronised with the CRM. Payment providers connect through the Payment Provider Protocol; local methods such as BLIK depend on the provider, for example through the Adyen connector, so we check them for every market. Carriers, warehouses and pickup points are set up in VTEX logistics.

With a large catalogue and many channels, yes. VTEX has a catalogue with categories, brands, variants, specifications and translations, which is good for presenting products, but it is not where a team collects data from ERP, suppliers and spreadsheets, fills gaps and approves content. Pimcore fits when you also need DAM, MDM or a product portal and have many integrations; Akeneo when a large product team works on content in many languages and markets; Ergonode when you want to start quickly with a PIM in the cloud.

openProd is a separate AI product (openprod.io) for importing supplier product data. It reads supplier PDFs, spreadsheets and data sheets, maps the values to the attributes, dictionaries and units of your PIM, and shows your team only the values that need a decision. Approved data goes to Pimcore, Akeneo or Ergonode and from there to the VTEX catalogue, so new supplier products reach the store without retyping.

VTEX when you combine B2C, B2B, a marketplace and physical stores on one SaaS platform without your own infrastructure; its fee has a fixed part and a part based on sales value (GMV). OroCommerce when you sell mainly B2B, have unusual processes and want full control over the code and hosting; its cost does not grow with turnover, but hosting, maintenance and upgrades come on top. We implement OroCommerce and know VTEX, so we help you choose. Both can use the same PIM.

All five serve larger companies but differ in what is standard. VTEX has B2C, B2B, OMS and a marketplace in one SaaS platform. Shopify Plus starts fast and is strongest in B2C; a multi-seller marketplace or an advanced OMS usually needs apps or separate systems. commercetools is an API-first commerce engine with a lot of freedom, but the storefront and some functions are chosen or built separately. Salesforce Commerce Cloud suits companies already on Salesforce; B2C and B2B are separate products. Adobe Commerce (Magento) gives code freedom and a large extension ecosystem, but version upgrades are usually separate projects. This is a simplification; we compare platforms on your requirements in the analysis.

We start with an audit of the data, integrations, extensions and search traffic. The catalogue is cleaned up in the PIM and published to VTEX through the API, because the VTEX spreadsheet import is limited to 10,000 rows per file. Customers and B2B accounts move separately, old URLs get 301 redirects, and integrations are switched to the VTEX APIs. A test migration comes before launch. A public example: H Mart moved from Adobe Magento to VTEX in seven months.

VTEX does not publish a price list. Its fee has a fixed part and a part based on the value of sales (GMV), and the level depends on the size of the company. Project length depends on the number of integrations, markets and the quality of the product data, so we give a timeline after the pre-implementation analysis.