Master Data: Temporary restriction on public fields
Starting October 26, 2026, Master Data v1 and v2 will temporarily restrict public fields. You won't be able to create new public fields or change existing private fields to public.
Starting October 26, 2026, Master Data will temporarily block the creation of public fields and the conversion of existing private fields to public. This change applies to both native and custom fields in Master Data v1 and v2.
What is changing?
- New fields can only be created as private.
- Existing private fields can no longer be changed to public.
- Attempts to create public fields or change private fields to public will return an error, and the changes won't be applied.
Why did we make this change?
We are strengthening data security in Master Data. Because all new fields are private, access to store and customer information always requires authentication, in line with data protection best practices.
What needs to be done?
If your store or integration uses public fields, update your implementation to use private fields and retrieve their data through authenticated API requests.
If you have a legitimate use case that requires public fields, open a support ticket explaining why unauthenticated access is necessary. The VTEX product team will review each request on a case-by-case basis.