vtex-io-masterdata-strategy

Use Master Data v2 for custom data in VTEX IO apps when you need explicit entity boundaries, indexing plans, and a controlled schema lifecycle for use cases like reviews, wishlists, or forms.

Decide by evaluating whether your app requires owning a schema via the masterdata builder for custom lifecycle control, or if relying on a stable external schema via the Master Data client better fits your data contracts.

The best way to manage schema lifecycle is using the masterdata builder to validate or create schemas before deployment, ensuring controlled setup and schema evolution across app environments.

Yes, you can model custom entities like wishlists and reviews in Master Data v2 by defining explicit schema boundaries and indexing plans tailored to your VTEX IO app's data access requirements.

The Master Data client supports consumption of stable external schemas, while the masterdata builder handles controlled schema creation and lifecycle evolution for VTEX IO app environments.

Relying on stable external schemas limits your ability to control schema evolution and entity boundaries, making the masterdata builder necessary for custom data modeling when app-specific lifecycle changes are required.