0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by VTEX · www.vtex.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
VTEX 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
- Panel verdict
- The AI panel rates VTEX 2/5, the mean of 6 judges. VTEX presents itself as an AI-native commerce suite for CIOs and CEOs, covering D2C, B2C, B2B and marketplaces. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
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.
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Tax & German legal correctness | 1 of 5 |
| Extensibility & developer surface | 3.5 of 5 |
| Order operations & back office | 2.5 of 5 |
| Data ownership & exit | 1.5 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
The path to payment is real and rebuildable: cart, payment and profile data all flow through the Checkout API, orders place from an existing cart, and a headless checkout built purely on API requests means I could change my checkout without a platform rebuild, with multi-currency and multi-language sold as standard. But the captured pages name no payment provider at all, and I found no information on vouchers or rule-based promotions, product variants, guest checkout, or the invoice and direct debit methods German shoppers expect. 1 2 3 8
The B2B Seller
The headless cart and checkout are documented in working detail — order forms, cart attachments, saved card tokens, orders placed from an existing cart, abandoned carts retrievable by ID — and the vendor page claims multi-region, multi-language, multi-currency selling and B2B self-service portals. Payment runs through connectors configured in the environment; the captured pages name no specific provider, and I found no public information on variants, vouchers, guest checkout, or the customer-group and tiered price lists a trade buyer cannot do without. 1 2 3
The Developer
The checkout path is documented end to end for headless builds: carts as orderForm objects with customer-profile, shipping and payment attachments, order placement through two methods, saved cards behind a token vault, and abandoned carts retrievable by ID, with payments routed through connectors configured in the store's environment. We found no public information on variants, discounts or vouchers, guest checkout, or named payment providers of the kind German buyers expect, and the vendor page claims multi-region, multi-language and multi-currency management only at platform level. 1 2 3
The Operations Lead
The headless checkout is real: carts, payment data, saved cards and transactions all run through documented endpoints with payment connectors configured in the environment, plus postal-code address lookup, pickup points and carts that stay retrievable after abandonment. I stop short of more because we found no public information on variants, discounts or vouchers, guest checkout, or a single named payment provider — multi-currency and multi-language appear only as claims on the vendor page. 1 2 3
The Data Protection Officer
The checkout itself is documented in depth: a headless cart organised as an order form with items priced in cents, customer profile, shipping and payment attachments, address autofill, pickup points and saved cards behind an opt-in checkbox, with orders placed through payment connectors configured in the environment. The captured pages show no variants, vouchers or guest checkout, name no payment provider, and say nothing about invoice or direct debit, so this sits a step above a basic catalogue-plus-payment checkout. 1 2 3
The Skeptic
The checkout path is real and headless: cart, client profile, payment data and order placement all run through documented API endpoints, with cards tokenised, saved cards, address autofill and pickup points, and carts retrievable by ID. What I cannot see is the merchandising underneath: no captured page shows variants, discounts, vouchers, guest checkout, or names a single payment provider — payments run through "payment connectors configured in your VTEX environment" — and the multi-currency, multi-language claim appears only as marketing on the vendor page, not as documentation. 1 2 3
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
Tax correctness is do-it-yourself: the documentation is a protocol, GraphQL API and recipe for wiring an external tax provider into checkout, with simulate and commit routes and a reference implementation on GitHub. No shipped VAT logic appears on these pages, and I found no information on gross and net display, OSS, invoicing, or the German checkout requirements — the merchant or an integrator carries the legal correctness. 4 5
The B2B Seller
VAT is not determined on the platform: the documented route is an integration protocol wiring an external tax provider into checkout, with simulate, commit and configuration steps and a fees array for regulatory charges. We found no public information on VAT-ID validation, reverse charge, OSS, invoicing or the German checkout requirements — the first questions my EU buyers ask. 4 5
The Developer
The documented approach to tax is a protocol for integrating an external tax provider: simulate, commit and configure routes registered against the order form, a GraphQL API, per-item fees for non-tax charges, and a reference implementation on GitHub. That places the VAT determination logic in an outside system the merchant builds or connects rather than in the platform, and we found no public information on VAT rates by country, reverse charge, OSS, invoicing or the German checkout requirements in the captured pages. 4 5
The Operations Lead
What is documented is a protocol for wiring an external tax provider into checkout — a GraphQL API, simulate-and-commit routes, parsers and a reference implementation that the merchant or partner builds and maintains. We found no public information on VAT rates configured in the platform, gross or net display, invoicing, OSS, reverse charge or the German checkout requirements such as order button wording; for a German merchant the tax story is build-your-own. 4 5
The Data Protection Officer
VAT is not determined in the platform: the documentation defines a protocol and a recipe for connecting an external tax provider, with simulate and commit routes, parsers and an optional per-item fees array, implemented by the merchant or an integration partner. We found no public information on VAT rates per country, B2B reverse charge, invoicing from orders, or the German checkout requirements — order button wording, withdrawal policy, price indications — on any captured page. 4 5
The Skeptic
Tax here is a build-it-yourself affair: the platform documents a protocol and a recipe for wiring an external tax provider into checkout, complete with simulate and commit routes, parsers and a sample repository to copy — the compliance work sits with the merchant and their chosen provider. We found no public information on VAT rates per country, OSS, reverse charge, invoicing from orders, or any German checkout requirement such as order button wording, withdrawal policy or price indication rules. 4 5
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
This is a surface a team can work with: an apps marketplace, headless storefronts on REST APIs where a third-party CMS is allowed, a GraphQL storefront API extended with typed resolvers in TypeScript, a local development server, order events through Feed and Hook, and app hosting on VTEX IO. What I don't see documented are staging environments, theme versioning and rate limits, and the checkout payload may gain new fields without warning. 1 2 6 7
The B2B Seller
The strongest evidence in the set: a GraphQL storefront API extendable in TypeScript, third-party API extensions, a headless build path through REST where the storefront can even run on a third-party CMS, order events via feed and hook, an apps marketplace, and apps hosted on the vendor's IO platform. Two caveats from the pages themselves: the authentication page stays with the vendor's storefront, and checkout payloads may gain new fields without warning; we found no public information on staging environments or documented rate limits. 2 4 6 7
The Developer
This is the strongest surface in the captures: a GraphQL storefront API extended through typed resolvers in mandatory source paths, TypeScript support, a development server run with a single yarn command, order-event updates through Feed v3 and Hook, and an apps marketplace with the vendor's IO platform hosting both core microservices and developed applications. We found no public information on version control for themes, staging environments, documented rate limits or a plugin dependency model, and two developer pages note fragmentation — a feature unavailable to stores on the FastStore stack, and a checkout payload that can gain new fields without warning. 1 2 6 7
The Operations Lead
There is a genuine developer surface: an apps marketplace, a GraphQL API you extend with typed resolvers in TypeScript, a local development server, and VTEX IO hosting for custom services with their own routes, alongside full headless builds over REST where order events reach you via Feed v3 and Hook integrations. I hold it below the top because rate limits, staging environments and theme version control are undocumented, the checkout payload can gain new fields without warning, and at least one feature is gated behind a support ticket and specific storefronts. 1 2 6 7
The Data Protection Officer
A genuine developer surface: a GraphQL storefront API extended with TypeScript resolvers in mandatory schema paths, a local development server, headless builds over REST where a third-party CMS is allowed except the authentication page, an apps marketplace, and order status via feed and hooks. Documented rate limits, staging environments and theme version control are absent from the captures, and the Checkout API may gain new fields without warning — a stability risk for anyone maintaining integrations. 1 2 6 7
The Skeptic
This is a real developer surface: GraphQL API extensions with typed resolvers in TypeScript, a local development server, a documented apps marketplace, webhooks and feed integrations for order events, and headless builds on REST APIs where a third-party CMS is allowed — except the authentication page, which stays on the vendor's side even when you build your own storefront. We found no public information on documented rate limits, staging environments, or version control for themes, which keeps it a step below the top tier. 1 2 6 7
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
After checkout the system runs the order: get and list order endpoints with status checks, Feed v3 and hooks for updates, an Inventory & Shipping module configuring carriers, loading docks and inventories, and genuinely deep marketplace handling where franchise stock sells through external marketplaces with item and price changes mid-order. I found no information on returns or refunds, partial shipments, label printing with named carriers, or maintained interfaces to ERP and accounting systems such as DATEV. 2 8 9
The B2B Seller
Order management is real — status feeds and hooks, changes to items and prices flowing out to external marketplaces, multilevel inventory letting franchise and white-label sellers' stock sell through connected marketplaces — and logistics sits in a dedicated inventory and shipping module with carriers, docks and shipping policies. We found no public information on refunds or returns handled in the system, or on maintained interfaces to ERP and accounting systems such as DATEV. 2 8 9
The Developer
After checkout there is a documented order management system: order status through Get order, List orders and Feed v3 and Hook integrations, an Inventory & Shipping module where carriers, loading docks and inventories are configured, and multilevel omnichannel inventory that lets franchise and white-label sellers' stock sell through connected marketplaces, including order changes with item additions, removals, discounts and increments. We found no public information on returns or refunds, label printing, named carrier integrations, or interfaces to ERP and accounting systems in the captured pages. 2 8 9
The Operations Lead
After checkout the picture is credible: orders tracked through status endpoints and hooks, an order management system behind marketplace intake, multilevel omnichannel inventory that sells franchise and white-label stock through connected marketplaces, shipping policies with carriers, docks and inventories, and an order-change routine that adds or removes items and adjusts totals with a reason surfaced to the shopper in transactional emails. What decides my score is the December test — we found no public information on refunds of any kind, partial or whole, nor on returns processing, label printing, or maintained interfaces to ERP and accounting systems such as DATEV. 2 8 9
The Data Protection Officer
After checkout there is real machinery: an order management system with order status endpoints, feed and hooks, item and price changes including discounts, marketplace order intake through multilevel omnichannel inventory, and an inventory and shipping module with docks, carriers and shipping policies. We found no public information on refunds, returns, label printing, or maintained interfaces to named ERP and accounting systems such as DATEV. 2 8 9
The Skeptic
After checkout there is an order management system with statuses tracked via endpoints, feed and hook integrations, an Inventory & Shipping module where carriers, docks and inventories are configured, and marketplace order intake with order and price changes on external-marketplace orders. We found no public information on returns or refunds handled in the system, label printing, named carriers, or interfaces to ERP and accounting systems such as German merchants need — the documented back office story stops at the API. 2 8 9
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Products and SKUs move in and out by spreadsheet, and marketing flows export as JSON for re-import into another organisation. Beyond that the captured pages say nothing about customer or order export, data return or deletion on cancellation, or any self-hosting option, so leaving looks like spreadsheet-level catalogue portability. 10 11
The B2B Seller
Getting out is documented at the level of spreadsheets and definition files: products and SKUs import and export via spreadsheet, and automation flows export to JSON and import again, with a warning that exporting one flow from a group can break functionality. Customer profiles are reachable and deletable through documented API endpoints, but we found no public information on contractual data return on cancellation, order-history export, or any self-hosting option — storefronts and apps run on the vendor's infrastructure. 3 10 11
The Developer
Product and SKU export through a spreadsheet is documented, and automation flows can be exported as JSON and imported back — portability for catalogue data and automation configuration, not a documented exit for customers or order history. We found no public information on export of customer and order data, on data return or deletion at cancellation, or on self-hosting; the captured pages describe applications hosted on the vendor's IO platform. 10 11
The Operations Lead
Getting the catalogue out is documented — products and SKUs import and export via spreadsheet, automation flows export to JSON and re-import — with orders reachable through list and feed endpoints and customer profiles manageable by API including a delete call. We found no public information on full-fidelity export including order documents and media, on data return when a contract ends, or on any choice of hosting. 2 3 10 11
The Data Protection Officer
Products and SKUs export by spreadsheet and automation flow definitions export as JSON, and — the point I check first — there is a documented endpoint that deletes a customer's personal data from the profile system, with personal data masked by default in the order form. Beyond that we found no public information on export of customers and full order history, on data return or deletion when a contract ends, or on self-hosting, so what is documented is spreadsheet-level export at most. 2 3 10 11
The Skeptic
What you can take with you is thin: products and SKUs export via spreadsheet, and automation flows export as JSON with a warning that exporting one flow from a group may break its functionality. We found no public information on export of customers or order history, on data deletion or return on cancellation, or on any self-hosting option — the exit path evidenced is a product list and your automation blueprints. 10 11
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant not rated — no public information
We found no public information on where customer and order data are hosted, who the contracting entity is, or which subprocessors sit in the checkout path; every sovereignty dimension is unstated in the material captured. The pages read were the vendor homepage and the developer and help centre documentation. 1 2 7
The B2B Seller not rated — no public information
We found no public information on where customer and order data are hosted, on the contracting entity behind the vendor, on a data processing agreement, or on any subprocessor in the checkout path; a Trust Center is named but the captured pages establish no location or legal entity. Nothing here is proven European or non-European — it is simply unstated. 1 2
The Developer not rated — no public information
We found no public information on where customer and order data are hosted, on the jurisdiction of the contracting entity, on a data processing agreement, or on the subprocessor chain in the captured pages. The vendor page lists a Trust Center among its support channels, but the captures do not state its contents. 1
The Operations Lead not rated — no public information
We found no public information on the contracting entity's jurisdiction, where customer and order data are hosted, hosting options, or a data processing agreement; every sovereignty dimension is recorded as unknown, and the vendor page's Trust Center link proves nothing about where data sits. I cannot score this from the captured pages. 1 2
The Data Protection Officer not rated — no public information
No captured page establishes where the contracting entity sits, where customer and order data are hosted, or which subprocessors carry the payment connectors, CDN and analytics in the checkout path; the vendor page offers only a Trust Center link among support channels, with its contents not captured. I found no public information on the European dimensions of this platform, so this criterion goes unscored rather than assumed either way. 1 2
The Skeptic not rated — no public information
Every dimension came back unknown: the captured pages establish nothing about where customer and order data live, who the contracting entity is, or which subprocessors sit in the checkout path. We found no public information on European sovereignty in the pages read — the vendor page points to a Trust Center, but nothing on it was captured. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant not rated — no public information
No price appears on any page captured — no tiers, no licence figures, no transaction or revenue-share rates, no billing terms or VAT treatment. With the suite positioned to CIOs and CEOs and 3,500+ enterprise customers, we found no public information from which a merchant could compute an annual cost. 1
The B2B Seller not rated — no public information
We found no public prices of any kind on the captured pages — no tiers, no "from" price, no transaction rates. The vendor page addresses CIOs and CEOs of enterprises, which reads as a sales conversation rather than a price list a merchant can compute from. 1
The Developer not rated — no public information
We found no public information on pricing: the captured vendor page positions the suite for CIOs and CEOs with figures for enterprise customers served and GMV processed, but no tier prices, billing periods or fee rates appear in the pages we read. 1
The Operations Lead not rated — no public information
We found no public information on pricing: the vendor page carries customer counts and GMV processed but no tiers, licence fees, transaction rates or billing period. A merchant cannot compute an annual cost from the captured pages. 1
The Data Protection Officer
We found no public price of any kind: the vendor page presents an enterprise suite for CIOs and CEOs with customer counts and GMV figures but no tiers, rates or billing periods, and none of the captured documentation pages carries a price either. A merchant cannot begin to compute an annual cost from these pages; the sale is clearly a conversation. 1
The Skeptic not rated — no public information
Not one price appears anywhere I read: no tier, no licence cost, no transaction or revenue-share rate, no order or GMV limits, no hosting line item, no term or VAT treatment. We found no public information on pricing in the captured pages, so a merchant cannot begin to compute the annual cost of this platform from what is published. 1
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about VTEX
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), Saleor (3/5) and Shopware (3/5) 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 (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: VTEX alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 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. Know more? Tell us
- 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. Know more? Tell us
- 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. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.vtex.com Checked 10 Nov 2026 Details →
- 2 Catalogue & checkout — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 3 Catalogue & checkout — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 4 Tax & German legal correctness — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 5 Tax & German legal correctness — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 6 Extensibility & developer surface — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 7 Extensibility & developer surface — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 8 Order operations & back office — found from sitemap developers.vtex.com Checked 10 Nov 2026 Details →
- 9 Order operations & back office — found from sitemap help.vtex.com Checked 10 Nov 2026 Details →
- 10 Data ownership & exit — found from sitemap help.vtex.com Checked 10 Nov 2026 Details →
- 11 Data ownership & exit — found from sitemap help.vtex.com Checked 10 Nov 2026 Details →