What problem does it solve?
It prevents teams from misusing VTEX Master Data v2 as a default storage layer by forcing a rigorous check of whether Master Data is the right system of record for the problem at hand.
Core Features & Use Cases
- Master Data decision guidance: Critically evaluate whether data belongs in Catalog, OMS/checkout surfaces, a BFF with caching, or an external database rather than defaulting to Master Data.
- Correct MasterData v2 implementation: Define entities and JSON Schemas, use MasterDataClient/ctx.clients.masterdata for CRUD, and ensure query performance through indexed
where fields.
- Operational safety for scale: Avoid placing synchronous Master Data in purchase-critical paths, respect pagination/scroll behavior, manage trigger usage, and plan around the 60-schema limit.
Quick Start
Use the vtex-io-masterdata skill to review your VTEX IO Master Data design and validate that your entities, schemas, indexing, and access patterns are correct and safe for production.