# VTEX — E-Commerce Platforms & Shop Systems

VTEX by VTEX holds a panel rating of 2/5 from 6 AI judges (category median 2.5/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: VTEX (https://www.vtex.com)
- Category: [E-Commerce Platforms & Shop Systems](https://whats-best.ai/software/e-commerce.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/e-commerce/vtex
- Alternatives: https://whats-best.ai/software/e-commerce/vtex/alternatives ([markdown](https://whats-best.ai/software/e-commerce/vtex/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-11 · oldest source captured 2026-11-10

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: VTEX
- Headquarters: Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## The panel's verdict

VTEX presents itself as an AI-native commerce suite for CIOs and CEOs, covering D2C, B2C, B2B and marketplaces. Its strongest surface is extensibility, scored 7 with no spread: a GraphQL storefront API extended with TypeScript resolvers, a local development server, headless builds over REST, an apps marketplace, and order events through Feed v3 and hooks. Weakest is tax and legal, a flat 2 — VAT is not determined in the platform; the documentation is a protocol for wiring an external tax provider, with the compliance work on the merchant or an integration partner. Catalog and checkout sits at 4 to 5 on a documented headless cart; the captured pages name no payment provider and show no variants, vouchers or guest checkout. The judges split on operations, 4 to 6, and data control and exit, 3 to 5: the higher scores credit order management, marketplace inventory and API-managed customer profiles; the lower see spreadsheet-level export and no documented returns or refunds. Sovereignty scored 0, with jurisdiction, data residency and hosting options unknown; no public price appears on the captured pages.

**Speaks for it:**
- Headless cart and checkout documented end to end through API requests, with saved cards behind an opt-in checkbox, address autofill and pickup points.
- Extensibility scored 7 with no spread, resting on a GraphQL storefront API with TypeScript resolvers, a local development server, an apps marketplace and headless REST builds.
- Order status is available through the get-order and list-orders endpoints plus Feed v3 and Hook integrations.
- Multilevel omnichannel inventory lets franchise or white-label sellers' stock sell through connected marketplaces, with item and price changes mid-order.
- Personal data is masked by default in the order form, and a documented endpoint deletes a customer's personal data from the profile system.

**Held against it:**
- VAT is not determined in the platform — the documentation defines a protocol and recipe for connecting an external tax provider, implemented by the merchant or an integration partner.
- We found no public information on refunds, returns processing, label printing, or maintained interfaces to ERP and accounting systems such as DATEV.
- Documented export reaches spreadsheet level — products and SKUs via spreadsheet, automation flows as JSON — with no public information on customer or order-history export.
- The Checkout API payload may gain new fields without warning, a stated stability risk for maintained integrations.
- Sovereignty attributes such as legal entity jurisdiction, data residency and hosting options are recorded as unknown; we found no public information on them.

**Best for:**
- You have an engineering team and want a headless storefront built on documented APIs — extensibility scored 7 with no spread and the headless checkout path is documented end to end.
- You run marketplace or omnichannel operations with franchise or white-label sellers — multilevel omnichannel inventory and mid-order item and price changes are documented.
- You already work with an external tax provider or an integration partner who can implement the documented tax protocol.

**Avoid if:**
- You need VAT determination and German checkout compliance handled inside the platform — the documented route places tax in an external provider that you or a partner build and maintain.
- You maintain integrations that cannot tolerate payload drift — the Checkout API may gain new fields without warning.
- Your exit plan must go beyond catalogue spreadsheets and automation flow definitions — that is the level of export the documentation shows.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Merchant | The B2B Seller | The Developer | The Operations Lead | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Catalogue & checkout | 2/5 | 2/5 | 2/5 | 2.5/5 | 2/5 | 2/5 |
| Tax & German legal correctness | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 |
| Extensibility & developer surface | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Order operations & back office | 2.5/5 | 2.5/5 | 2.5/5 | 3/5 | 2/5 | 2/5 |
| Data ownership & exit | 1.5/5 | 2/5 | 1.5/5 | 2.5/5 | 1.5/5 | 1.5/5 |
| European sovereignty | n/r | n/r | n/r | n/r | n/r | n/r |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2/5** | **2.5/5** | **2.5/5** | **1.5/5** | **2/5** |

### The judges

- **The Merchant** (v1.0): Sells to consumers and lives on conversion. Wants a checkout that can be changed without a rebuild, the payment methods German shoppers expect including invoice, and promotions with rules. Judges price against contribution, not against a competitor's tier.
- **The B2B Seller** (v1.0): Sells to businesses across the EU: net prices, VAT-ID validation, reverse charge, customer-specific price lists and payment on account. Reads a shop that shows gross prices to a trade customer as one that has not met a trade customer.
- **The Developer** (v1.0): Will maintain this for five years. Wants local development, version control for themes, a plugin architecture with a dependency model, and upgrades that do not orphan the customisations. Reads a closed template editor as a future migration.
- **The Operations Lead** (v1.0): Ships the orders and handles the returns. Wants stock that is true across channels, partial shipments, carrier integrations with labels, and an ERP link the vendor maintains. A shop that cannot do a partial refund is a shop that has never had December.
- **The Data Protection Officer** (v1.0): The shop holds customers, addresses and buying histories, and the checkout is full of third parties. Wants the subprocessor list, consent handling that survives a complaint, deletion that executes against order history, and an answer on where the CDN and analytics sit.
- **The Skeptic** (v1.0): Knows the headline price is never the invoice here. Reads for the transaction fee, the apps that turn out to be mandatory, the hosting nobody mentioned, and what the platform charges to let a merchant leave with their own order history.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Payment connector warning: Order processing uses payment connectors configured in VTEX environment [S2]
- Pii masking: yes [S2]

**Integrations**
- Add client profile data: POST /api/checkout/pub/orderForm/{orderFormId}/attachments/clientProfileData [S3]
- Add items to cart: POST /api/checkout/pub/orderForm/{orderFormId}/items [S3]
- Add payment data: POST /api/checkout/pub/orderForm/{orderFormId}/attachments/paymentData [S3]
- Address autofill: yes [S2]
- Apps: VTEX Apps marketplace [S1]
- Change item fields: integer, cents · integer · SKU ID string · integer · string [S8]
- Change notification endpoint: /pvt/orders/{orderGroup}/changes [S8]
- Change payload fields: string · array of objects · integer, cents [S8]
- Change payload same as register change API: Register change on order API [S8]
- Change response error: 500 · no [S8]
- Change response success: orderId · receipt · 200 [S8]
- Create profile: POST /api/profile-system/pvt/profiles [S3]
- Delete profile: DELETE /api/profile-system/pvt/profiles/{profileId}/personalData [S3]
- Flow export: Flows can be exported via the flow editor options menu using the "Export Definition" button [S10]
- Flow export json: Flow export generates a .json file [S10]
- Flow import: Flows can be imported via the "Import" button in the organization's general settings [S10]
- Get card: GET /api/pvt/accounts/{accountId} [S3]
- Get profile cards: GET /api/profile-system/pvt/profiles/{profileId}/vcs-checkout [S3]
- Get transaction details: GET /api/pvt/transactions/{transactionId} [S3]
- Implementers: integration partner · external marketplace [S8]
- List payments: GET /api/pvt/transactions/{transactionId}/payments [S3]
- Marketplace services endpoint field: Order placement API · marketplaceServicesEndpoint [S8]
- Pickup points: yes [S2]
- Place order: POST /api/checkout/pub/orderForm/{orderFormId}/transaction [S3]
- Save card token: POST /api/card-token-vault/tokens [S3]
- Shipping policies API: Shipping Policies APIs documented in Developer Portal [S9]
- Start client login: POST /api/vtexid/pub/authentication/startlogin [S3]
- Validate client login: POST /api/vtexid/pub/authentication/classic/validate [S3]

**Product**
- Ads AI campaigns: AI-optimized sponsored campaigns on storefront [S1]
- Ads platform: VTEX Ads Platform: sponsored products advertising [S1]
- Agentic customer experience: Autonomous AI agents for support and purchases [S1]
- Agentic whatsapp store: Conversational commerce within WhatsApp [S1]
- AI search recommendations: AI search and personalized recommendations [S1]
- API payload changes: Checkout API payload may gain new fields without warning [S2]
- API purpose: credit card tokenization flows: profile management, card token vault, checkout, payment gateway, authentication [S3]
- API schema extension: FastStore API can be extended to access and modify data from VTEX and third-party APIs [S6]
- Availability restriction: yes [S3]
- B2b commerce: B2B Commerce with self-service portals [S1]
- B2c commerce: B2C Commerce solution [S1]
- Cart attachments: Attachments cover customer profile, shipping, marketing, payment, merchant context data [S2]
- Cart endpoints: Get current or create a new cart endpoint returns orderFormId; abandoned carts retrievable via Get cart information by ID [S2]
- Change order item price change: franchise account products sold via external marketplaces · change order items · change order prices [S8]
- Checkout API headless: Headless cart and checkout implemented via Checkout API using API requests only [S2]
- Cms genai: CMS with generative AI content creation [S1]
- Commerce platform: VTEX Commerce Platform: commerce platform for D2C, B2C, B2B, and Marketplaces [S1]
- Conversational commerce: Conversational commerce via WhatsApp and chat channels [S1]
- Countries served: 43 [S1]
- Custom search sort version: Custom search sort values require FastStore 4.9.0 or later [S6]
- Custom sort builtin control limitation: Custom sort keys do not appear in the built-in Product Gallery sort control; a custom control must be rendered [S6]
- Custom sort key locations: A custom sort key must be defined in StoreSort extension, api.customSortMap in discovery.config.js, and registerCustomSortKeys in the storefront [S6]
- Custom sort map priority: customSortMap entries override built-in sort value mappings [S6]
- Customer count: 3500 [S1]
- Cx platform: VTEX CX Platform: AI-native customer service and conversational commerce [S1]
- Dashboard rename: Dashboard tab renamed to Shipping strategy from May 12, 2020 [S9]
- Data insights agent: AI-powered analytics data insights agent [S1]
- Dev server command: Development server is run with yarn dev [S6]
- Extension folder structure: Extension typeDefs and resolvers live in mandatory paths src/graphql/vtex/typeDefs and src/graphql/vtex/resolvers [S6]
- Flow export grouping: Export page displays flows and campaigns grouped by usage; exporting only one flow from a group may cause functionality issues [S10]
- Global commerce: Multi-region, multi-language, multi-currency management [S1]
- Gmv processed: 15000000000 [S1]
- Graphql based: FastStore API is GraphQL-based; extensions require type definitions and resolvers [S6]
- Headless app keys: Application keys can be used where shopper authentication is not necessary, such as product search [S7]
- Headless core via rest: Headless stores use VTEX core commerce features via REST APIs [S7]
- Headless experience parts: Viewing catalog information · Placing orders · Viewing account information [S7]
- Headless login cookie: user token for authenticating API requests · VtexIdclientAutCookie [S7]
- Headless third party cms: yes [S7]
- Headless vtex io hosting: VTEX IO can host core commerce microservices and developed applications to extend functionality [S7]
- Logistics module: Inventory & Shipping module manages logistics; Dashboard tab configures carriers, loading docks and inventories [S9]
- Marketplace: Marketplace solution [S1]
- Moi definition: Allows franchise accounts or white label sellers' inventory to be sold in marketplaces connected to the main account [S8]
- No config change: no [S9]
- Omnichannel operations: Omnichannel operations unifying online and offline [S1]
- Oms payment requirement: Order Management System (OMS) · yes [S8]
- Order completion window: 5 · order canceled and tagged incomplete [S2]
- Order ownership cookie: CheckoutOrderFormOwnership cookie controls access to unmasked personal data [S2]
- Order placing methods: 2 · place new order · place order from existing cart [S2]
- Order verification: Order status via Get order / List orders endpoints, Feed v3 and Hook integrations [S2]
- Orderform structure: Cart data organized in orderForm object with products, shipping, payment info [S2]
- Positioning: AI-Native Commerce Suite for CIOs and CEOs [S1]
- Process order endpoint: Process order endpoint requires approved payment, else 500 [S2]
- Recaptcha limitation: reCAPTCHA only works with Checkout v6 stores · no [S2]
- Recommended method: place order from existing cart [S2]
- Save card optin: yes [S2]
- Saved credit cards: Saved cards retrievable via Get client profile by email; only last four digits shown [S2]
- Search capability: yes [S9]
- Tax protocol definition: Protocol that defines how to build an integration of an external tax provider to VTEX. [S5]
- Tax protocol graphql API: yes [S5]
- Tax protocol sections: Overview · Specification · Recipe · Reference Implementations [S5]
- Tax service client checkout: Checkout client configures the tax service in Checkout [S4]
- Tax service client logistics: Logistics client fetches dock information by ID via a single method [S4]
- Tax service client taxprovider: TaxProvider client connects to the external tax provider API [S4]
- Tax service client vtexcommerce: VtexCommerce is a base client other clients inherit to connect to the VTEX API [S4]
- Tax service example repo: A Tax Protocol Example on GitHub serves as a reference implementation [S4]
- Tax service item fees: Provider-to-VTEX payload supports an optional per-item fees array for non-tax charges like regulatory or commercial fees [S4]
- Tax service parsers: Parsers format payloads between the external provider API and the Checkout API [S4]
- Tax service purpose: Tax service apps connect VTEX Checkout to an external tax provider via clients, routes, and parsers [S4]
- Tax service route dependency: Simulate and commit routes only work after configuring the tax service with the configuration route [S4]
- Tax service routes commit: Route to commit order taxes based on order status changes, same as the hooks object route in the provider's response [S4]
- Tax service routes configure: Private route to activate or deactivate the tax service via orderForm configuration [S4]
- Tax service routes setup: Routes are defined in service.json with handlers used in node/index.ts [S4]
- Tax service routes simulate: Route to simulate taxes for a cart and return them to Checkout in a specific format; registered in Order Form Configuration [S4]
- Terminology change: Carrier renamed to Shipping policy in VTEX Admin [S9]
- Third party extension structure: Third-party API extensions use a src/graphql/thirdParty folder with resolvers and typeDefs, distinguishing VTEX-origin data from third-party data [S6]
- Third party query mutation: Third-party extensions require a Query or Mutation schema to generate new query entry points [S6]
- Typedefs format: typeDefs files use .graphql extension; index.ts required only for resolvers [S6]
- Typescript support: Resolvers can be written in TypeScript, with typed root params like StoreProductRoot from @faststore/api [S6]
- Unified commerce claim: One suite for operations, CX and retail media for D2C, B2C, B2B [S1]
- Unmapped sort behavior: Unmapped StoreSort values return a bad request 'Unknown sort value'; Object.prototype keys like constructor are also rejected [S6]

**Support**
- Academy: VTEX Academy [S1]
- Feature enablement: no · yes [S2]
- Help center: Help Center · Documentation · Trust Center [S1]

## Questions

### Is VTEX European?

Not determined: the vendor’s pages as captured do not say where VTEX is based.

### Where does VTEX store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

### Does VTEX have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

### What are the best alternatives to VTEX?

As of 18 Nov 2026, the panel rates [JTL-Shop (3.5/5)](https://whats-best.ai/software/e-commerce/jtl-shop), [Saleor (3/5)](https://whats-best.ai/software/e-commerce/saleor) and [Shopware (3/5)](https://whats-best.ai/software/e-commerce/shopware) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [JTL-Shop](https://whats-best.ai/software/e-commerce/jtl-shop) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [VTEX alternatives](https://whats-best.ai/software/e-commerce/vtex/alternatives).

## What this page leaves out

- We found no public information on pricing on the pages we read (vtex.com, developers.vtex.com/docs/guides/headless-cart-and-checkout, developers.vtex.com/docs/api-reference/checkout-custom-card-payment-api, developers.vtex.com/docs/guides/tax-services-recipe, developers.vtex.com/docs/guides/tax-service-integration-guide, developers.vtex.com/docs/guides/faststore/api-extensions-extending-api-schema and 5 more). If the vendor publishes it somewhere else, send us the page.
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.

## Sources

- [S1] Vendor page: https://www.vtex.com (checked 2026-11-10)
- [S2] Catalogue & checkout — found from sitemap: https://developers.vtex.com/docs/guides/headless-cart-and-checkout (checked 2026-11-10)
- [S3] Catalogue & checkout — found from sitemap: https://developers.vtex.com/docs/api-reference/checkout-custom-card-payment-api (checked 2026-11-10)
- [S4] Tax & German legal correctness — found from sitemap: https://developers.vtex.com/docs/guides/tax-services-recipe (checked 2026-11-10)
- [S5] Tax & German legal correctness — found from sitemap: https://developers.vtex.com/docs/guides/tax-service-integration-guide (checked 2026-11-10)
- [S6] Extensibility & developer surface — found from sitemap: https://developers.vtex.com/docs/guides/faststore/api-extensions-extending-api-schema (checked 2026-11-10)
- [S7] Extensibility & developer surface — found from sitemap: https://developers.vtex.com/docs/guides/headless-commerce (checked 2026-11-10)
- [S8] Order operations & back office — found from sitemap: https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces (checked 2026-11-10)
- [S9] Order operations & back office — found from sitemap: https://help.vtex.com/en/announcements/2020-05-05-inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab (checked 2026-11-10)
- [S10] Data ownership & exit — found from sitemap: https://help.vtex.com/en/docs/tutorials/import-and-export-flows (checked 2026-11-10)
- [S11] Data ownership & exit — found from sitemap: https://help.vtex.com/en/docs/tutorials/importing-and-exporting-products-and-skus-using-a-spreadsheet (checked 2026-11-10)

---

Cite as: whats-best.ai, "VTEX — E-Commerce Platforms & Shop Systems", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/e-commerce/vtex

Corrections: https://whats-best.ai/correct/1751?target=page
