marketplace-catalog-sync

Synchronize VTEX marketplace catalog, SKU suggestions, price, and inventory via SKU Integration API.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/exilonX/ap2 --skill marketplace-catalog-sync-exilonx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marketplace-catalog-sync
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/marketplace-catalog-sync
Command: npx skills add https://github.com/exilonX/ap2 --skill marketplace-catalog-sync-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the recurring integration failures and data drift that happen when a seller connector updates VTEX marketplace SKUs, prices, and inventory without following the required changenotification, suggestions, and simulation flow.

Core Features & Use Cases

  • Change Notification + SKU Suggestion Workflow: Correctly determine whether a SKU already exists (200) or must be suggested (404), then push new SKUs through the pending approval lifecycle.
  • Seller-Scoped Price & Inventory Updates: Send price and inventory notifications to the proper VTEX notificator endpoints using the seller SKU identifier.
  • Fulfillment Simulation Readiness: Implement a fast seller-side fulfillment simulation so the marketplace can fetch updated availability within the required timeout window.
  • Rate-Limited Batch Sync with 429 Backoff: Throttle bulk notifications and implement exponential backoff to avoid blocking the integration during heavy updates.

Quick Start

Use the marketplace-catalog-sync skill to design your seller connector so it posts seller-scoped changenotifications, sends SKU suggestions to the api.vtex.com suggestions endpoint when needed, and serves a fulfillment simulation response fast enough for the marketplace to reflect updated price and stock.

Frequently Asked Questions about marketplace-catalog-sync

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

FAQPage Schema
How do I sync VTEX marketplace catalog SKUs using changenotification and sellerSkuId?

Avoid direct catalog writes for VTEX marketplace integration and instead use dedicated SKU Integration API endpoints to route changenotifications, SKU suggestions, price, and inventory updates with correct identifier routing and verifiable workflows.

How do I handle VTEX API rate limiting and 429 errors during bulk catalog sync?

Handle VTEX API 429 rate limiting during bulk catalog sync by throttling notification batches and implementing exponential backoff to prevent integration blocking and data drift during heavy inventory or price updates.

How does fulfillment simulation work for VTEX marketplace seller connectors after inventory updates?

Send separate price and inventory notifications to the proper VTEX notificator endpoints using the seller SKU identifier, rather than combining them, to ensure correct seller-scoped updates and fulfillment simulation readiness.

What is the correct lifecycle for pending SKU suggestions in a VTEX marketplace integration?

The VTEX pending SKU suggestion lifecycle requires sending new SKUs to the api.vtex.com suggestions endpoint after a 404 changenotification response, then updating those pending suggestions through the approval workflow without direct catalog writes.