VTEX Plans: Seats, Hubs, and Qualifying Tiers
Choose your VTEX plan by mapping must-haves to qualifying tiers — seats, hubs, pools, and add-ons — not homepage “from” tiles.
Quick answer
Choose a VTEX plan by listing day-one must-haves for enterprise SaaS commerce platform, mapping them to a qualifying tier — subscription, processing, apps, GMV, or quote packaging included — then proving the loop on that package before you buy. Confirm marketing automation (Talk to sales+) and dropshipping sourcing (Talk to sales+) are on the package you will actually buy. Homepage “from” tiles are not a bill of materials. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/vtex/.
- List day-one must-haves
- Map to a researched qualifying plan
- Price processing, apps, and GMV you will actually use
- Prove the loop on the package you will buy
- Get the qualifying configuration in writing
- Never invent a spreadsheet total in this guide
VTEX packaging rules
- Tiles are the bottom layer — Researched plans: Talk to sales.
- Gates change the bill — Plan-gated in research: marketing automation (Talk to sales); dropshipping sourcing (Talk to sales).
- Prove on the package you will buy — Our snapshot records no trial length for VTEX — ask for an evaluation window in writing before you commit to a plan.
- Job cluster first — Must-haves should match stand up a storefront sandbox, import a catalog slice, and complete a test order on the quoted package. Do not pay for hubs that serve an SMB published-tile Shopify Basic launch or a POD sourcing app.
VTEX plan path
VTEX plan anatomy

What actually shapes a VTEX bill
We do not invent list prices here. Use this anatomy, then confirm live numbers on the VTEX pricing page.
- Seats61%
- Add-ons18%
- Implementation12%
- Training5%
- Other4%
Subscription / hub
The researched plan that unlocks checkout, imports, or sales channels — not the homepage starter tile.
Processing / GMV
Transaction fees, payment plans, and any GMV bands. Confirm whether the vendor’s processor is cheaper than yours.
Apps, modules, themes
Plan-gated in research: marketing automation (Talk to sales); dropshipping sourcing (Talk to sales).
Hosting / implementation
Open-source and enterprise paths add hosting or integrator hours — get fees in writing; do not invent them.
AI / extras
Research lists AI assistant, AI summaries, AI automation, and AI recommendations for VTEX. Research places AI assistance on Talk to sales.
Who VTEX packaging usually fits
- 01
Early catalog / one channel
Fits when enterprise SaaS commerce platform is the job and you can live without enterprise multi-storefront or composable programmes.
- One store or connected storefront
- Named merchandiser
- Payments you will actually use
- 02
Growing catalog / omnichannel
Fits when inventory, channels, or GMV gates matter and someone will admin the store weekly.
- Named store owner hours
- Must-haves mapped to a qualifying hub
- Stop shadow spreadsheets for stock
- 03
Quote-led / multi-store
Fits only if VTEX is still enterprise SaaS commerce platform at that scale — not if you actually needed an SMB published-tile Shopify Basic launch or a POD sourcing app.
- Written qualifying configuration
- GMV / processing rules
- Adoption review before more apps
VTEX must vs nice
- Core loop on the qualifying plan
- Payments / shipping / channels for day one
- online storefront, product catalog, checkout payments, and order management
- AI / extra apps
1. List day-one must-haves for this job cluster

Honest musts
Five jobs, all used weekly — catalog, checkout, and the channel you sell on.
Wishlist
Twelve musts including unused AI and marketplace apps — cut to five.
Wrong job
If musts describe an SMB published-tile Shopify Basic launch or a POD sourcing app, this product’s packaging will not save you.
Must-haves should match stand up a storefront sandbox, import a catalog slice, and complete a test order on the quoted package. Research-supported features include online storefront, product catalog, checkout payments, and order management. 1. Write five things the store must do in week one.
- Mark each must vs nice.
- Drop anything that is actually an SMB published-tile Shopify Basic launch or a POD sourcing app. Worked example: Northline Mid-Market (hosted enterprise commerce) drops a cheaper tile when the must-have workflow unlocks only on a higher hub.
2. Map must-haves to a researched qualifying plan

Mapped
Every must-have has a researched plan name.
Tile shopping
You compared “from” prices across vendors — restart from must-haves.
Quote-only
If there is no public matrix, get the configuration in writing before you call it cheap.
Researched plans: Talk to sales. 1. For each must-have, write the lowest researched VTEX plan that includes it. Plan-gated in research: marketing automation (Talk to sales); dropshipping sourcing (Talk to sales).
- The highest plan on that list is the qualifying tier — not the homepage starter tile.
- Check processing, GMV bands, and extra storefronts separately. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/vtex/. Worked example: Northline Mid-Market (hosted enterprise commerce) discovers checkout, imports, or a sales channel force a higher hub than the tile they screenshotted, so they re-qualify before a trial.
3. Prove the loop on the package you will buy

Honest trial
Loop works on the hub you will pay for.
Inflated trial
Ask the vendor which package the tenant is on, in writing.
Free-plan trap
Free is a proving ground only if must-haves actually live there.
Our snapshot records no trial length for VTEX — ask for an evaluation window in writing before you commit to a plan. 1. Run a merchandiser can update a SKU and a test buyer can check out in sandbox on the qualifying hub — not a demo enterprise workspace.
- Confirm processing and app behaviour if they change the bill.
- Write the configuration: plan, processing, apps, billing term. Worked example: Northline Mid-Market (hosted enterprise commerce) fails the gate when the trial ran Plus features they will not purchase. They restart the trial on the written package.
4. Get the qualifying configuration in writing

Written
Plan, processing, apps, term — attached to the decision.
Verbal extra
If a feature was “included in the demo,” it is not included until it is written.
Walk
If packaging stays vague, keep looking via how to choose ecommerce software.
- Plan / hub (weekly operators only).
- Processing and GMV rules.
- Apps and add-ons the trial proved.
- Implementation, hosting, or onboarding fees if any — do not invent them.
- Annual vs monthly only after the configuration is frozen. Worked example: Northline Mid-Market (hosted enterprise commerce) will not sign until the qualifying hub and processing rules are in an email they can attach to the buy decision. If packaging stays vague, they also keep Shopify, BigCommerce, and Salesforce Commerce Cloud on the same must-have sheet.
Compare qualifying configurations inside the same cluster
Do not rank VTEX (enterprise SaaS commerce platform) against an SMB published-tile Shopify Basic launch or a POD sourcing app on a single price tile.
- View CRM profile
ShopifyHosted SaaS ecommerce platform with themes, checkout, channels, and POS — Basic from $39/mo ($29 annual), Grow $105 ($79 annual), Advanced $399 ($299 annual), Plus from $2,300/mo.
- View CRM profile
BigCommerceOpen-SaaS ecommerce platform — Core $39/mo ($29 annual), Growth $105 ($79), Scale $399 ($299); GMV thresholds and open payment provider fees apply on 2026 plans.
- View CRM profile
Salesforce Commerce CloudSalesforce B2C Commerce (ex-Demandware) — Growth/Plus/Premium are GMV-percent quote only; enterprise SaaS landscape, not an SMB Shopify substitute.
Shortlist is cluster-matched from the catalogue — not an affiliate-ordered ranking and not a score.
VTEX checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1List day-one must-havesFeatures that must ship without an unused enterprise tier.
- 2Map to a qualifying planUse researched plan names — not marketing starting tiles.
- 3Prove the loop on that packageTrial the hub you will buy, before you buy.
- 4Get the qualifying quote in writingPlans, processing, apps, and implementation fees.
Frequently asked questions
Does a free VTEX plan count?
Our snapshot records no trial length for VTEX — ask for an evaluation window in writing before you commit to a plan.
Should we pay annually?
Only after the qualifying configuration is written. Annual discounts do not fix the wrong hub.
How do we treat processing and GMV?
Model the constraint you will hit first — subscription, transaction fees, or a GMV band. Confirm both on the pricing page; do not invent a blended rate here.
Can we compare “from” prices across tools?
Not usefully. Compare qualifying configurations for the same must-haves. Tiles omit gates.
Where are the actual numbers?
Never invent list prices here — confirm plans, processing, and quote terms on /pricing/vtex/.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.