vtex-io-masterdata

Assess MasterData v2 schema design and CRUD operations in VTEX IO applications.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Willjeanne/faststore-soliverdemo --skill vtex-io-masterdata-willjeanne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-masterdata
Source: https://github.com/Willjeanne/faststore-soliverdemo/tree/main/.agents/skills/vtex-io-masterdata
Command: npx skills add https://github.com/Willjeanne/faststore-soliverdemo --skill vtex-io-masterdata-willjeanne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and architects avoid common pitfalls when working with MasterData v2 in VTEX IO apps, ensuring efficient and effective data management.

Core Features & Use Cases

  • Justification for MasterData Usage: Provides guidelines for determining when MasterData v2 is the right choice for storing and managing data.
  • CRUD Operations: Offers instructions for performing Create, Read, Update, and Delete operations using MasterDataClient.
  • Schema Management: Explains schema lifecycle and the importance of managing the 60-schema limit.
  • Data Placement Decisions: Assists in deciding whether data should be stored in MasterData, Catalog, OMS, or an external database.
  • Use Case: When developing a VTEX IO app that requires storing and querying custom data, this Skill helps ensure the right data storage strategy is chosen.

Quick Start

Use the vtex-io-masterdata skill to review your data storage strategy for the 'Order Management' feature in your VTEX IO app.

Frequently Asked Questions about vtex-io-masterdata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform CRUD operations on MasterData v2 in a VTEX IO app?

To perform CRUD operations on MasterData v2, you use the MasterDataClient API within your VTEX IO app. This approach ensures your data management operations align with platform best practices for creating, reading, updating, and deleting data.

When should I use MasterData v2 instead of the Catalog or OMS for custom data?

You should use MasterData v2 for storing and querying custom data when it fits your specific schema design needs. Evaluating data placement decisions helps determine if MasterData, Catalog, OMS, or an external database is the right choice.

What is the 60-schema limit in MasterData v2 and how do I manage it?

The 60-schema limit in MasterData v2 restricts the number of schemas you can create. Managing this schema lifecycle is crucial for optimizing MasterData usage and ensuring efficient data placement without hitting platform constraints.

Does MasterData v2 require understanding VTEX IO architecture to use effectively?

Yes, optimizing MasterData v2 requires an understanding of VTEX IO architecture and the MasterDataClient API. This knowledge is necessary to justify MasterData usage and ensure your data storage strategy complies with platform best practices.

What is the best way to optimize schema design for MasterData in VTEX IO?

The best way to optimize schema design for MasterData in VTEX IO is to follow platform best practices for data placement and schema lifecycle management. This ensures efficient CRUD operations and effective data management.