Effective June 2026 — Master Data usage-based pricing begins. Your May invoice includes a preview with no charges applied.
Product Update · Master Data
Starting June 2026, VTEX is introducing usage-based pricing for Master Data when used for non-native data structures. Native commerce entities remain free. Here's everything you need to know — and what to do next.
Why this is happening
Master Data was designed to store and organize essential commerce data with powerful capabilities for search, triggers, and integrations. That foundation is unchanged.
Over time, however, some customers began using Master Data to build highly customized applications — storing large datasets and creating multiple non-native data structures. These implementations introduce complexity, degrade performance, and drive infrastructure costs to unsustainable levels.
To ensure the platform continues to scale with performance and reliability, VTEX is introducing a usage-based model for non-native data structures. This aligns us with industry best practices and creates the right incentives for sustainable, efficient architectures.
"The incorrect use of Master Data results in an overly customized architecture — expensive and hard to maintain. Clear commercial boundaries help keep architectures simpler and more sustainable over time."Mariano Gomide de Faria — Founder & Co-CEO, VTEX
What changes
The distinction is simple: native commerce data structures continue at no cost. Only custom, non-native entities are subject to the new usage-based fee.
Pricing model
Charges apply only to non-native entities. Each stored document counts as 100 KB. Usage is measured via a snapshot on the 25th of each month.
Fixed monthly fee. Predictable cost for lower-volume non-native usage.
Fixed monthly fee. No variable component — full cost certainty up to 1M documents.
$125 base + $0.10 per additional block of 1,000 documents beyond the 1M threshold.
You earn a billing credit equal to 2% of your net VTEX payment (excluding VAT). Credits accumulate throughout your contract term and are automatically applied to Master Data charges — in many cases, offsetting them entirely.
Your action plan
The first consumption snapshot is taken on June 25th. That's your window to understand your current usage and, if needed, optimize before billing begins.
Ask your Commerce Engineer or VTEX account team to pull your current document volume in non-native entities. In the initial rollout, usage data is available on request. A self-service monitoring dashboard will be available by end of June. Your May invoice also includes an estimated charge for visibility — review it when it arrives on June 1st.
Action required · Before June 25If your non-native document volume is significant, you have two options. You can reduce your stored document count before June 25th to lower your billing baseline — your Commerce Engineer can guide you on best practices. Or, if these custom use cases are important to your operations, you can continue using Master Data as-is: the new model simply means usage will be billed to reflect the infrastructure it requires.
Review with your teamIf your projected Master Data charge exceeds 10% of your monthly VTEX invoice, your Commerce Engineer will reach out proactively. You don't need to wait — contact them directly to review your architecture, explore optimization opportunities, or discuss transition options. In select cases, temporary waivers of up to three months may be granted at the discretion of the Global Head of Commerce Engineers.
High-impact accounts · Contact CETimeline
All new VTEX Order Forms include the Master Data charge clause.
All customers receive the official announcement with details of the new model and estimated impact based on current usage.
Your May invoice shows estimated Master Data charges for transparency only. No amount is due this month. Use it to understand your exposure before billing begins.
This is the measurement date that sets your June billing baseline. Reduce document volume before this date if you wish to optimize your first invoice.
A dashboard to monitor your Master Data usage in real time becomes available. Until then, usage data is available on request from your Commerce Engineer.
The July invoice (for June consumption) is the first where Master Data charges are applied. Accumulated loyalty credits are automatically deducted.
FAQ
If your team created custom data entities in Master Data outside of VTEX's native commerce structures — to support custom applications or store large datasets — those are non-native entities. Your Commerce Engineer can confirm this and provide document counts.
Yes — and that's the right window to do it. The June 25th snapshot sets your billing baseline for the July invoice. If you'd like to reduce your non-native document volume, work with your engineering team or Commerce Engineer before that date. Your CE can advise on the most efficient approach.
Each stored record in a non-native entity is counted as one document, equivalent to 100 KB of storage. Total document count is assessed via a snapshot on the 25th of each month.
Your Commerce Engineer will proactively reach out to accounts with projected Master Data charges exceeding 10% of their monthly VTEX invoice. Temporary waivers of up to three months may be considered on a case-by-case basis by the Global Head of Commerce Engineers.
Yes. Every VTEX payment generates a credit equal to 2% of the net amount paid. These credits accumulate over your contract term and are automatically applied to Master Data charges. For many accounts, accumulated credits will partially or fully offset the monthly charge.
Yes. Master Data usage fees will be included on the same invoice as your Commerce Platform Fees, with a clear breakdown showing total usage charges, credits applied, and the final net amount due.
Whether you want to review your current usage, understand your exposure, or optimize your architecture before June 25th — reach out. We're committed to making this transition smooth.