marketplace-order-hook

Process VTEX marketplace order status updates from Hook or Feed v3 events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or insecure VTEX marketplace order integrations by ensuring webhook/feed-driven order status events are validated, deduplicated, and handled across the full lifecycle.

Core Features & Use Cases

  • Order status integration via Hook or Feed v3: Choose push-based Hook for real-time middleware or pull-based Feed v3 for controlled throughput, with Feed as a fallback during downtime.
  • Secure, authenticated event handling: Validate VTEX webhook authentication (expected Origin.Account and Origin.Key plus configured headers) before processing any order event.
  • Idempotent state processing across retries: Deduplicate events using the combination of OrderId + State + LastChange to avoid double fulfillment or duplicate downstream actions.
  • Complete lifecycle coverage with safe fallback: Handle all possible order statuses (including Status Null) with a default logger path for unknown values so processing never crashes or stalls.
  • Integration pattern for external systems: Use Hook notifications to trigger ERP/WMS/fulfillment updates by fetching full order details with GET /api/oms/pvt/orders/{orderId}.

Quick Start

Configure a VTEX marketplace order Hook with a FromWorkflow filter for the states you care about, then build an endpoint that validates Origin and headers, deduplicates by OrderId+State+LastChange, fetches the full order by ID, and responds with HTTP 200 within 5000ms.

Frequently Asked Questions about marketplace-order-hook

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

FAQPage Schema
How do I process VTEX order webhooks safely for ERP integration?

Ensure idempotent VTEX order processing by deduplicating incoming events using the unique combination of OrderId, State, and LastChange. This combination prevents duplicate fulfillment actions or double processing when webhook or Feed v3 retries occur.

What is the difference between VTEX Hook and Feed v3 for order status lifecycle events?

VTEX Hook provides push-based real-time order status lifecycle event notifications, while Feed v3 offers pull-based controlled throughput. Feed v3 is commonly used as a fallback during downtime to ensure no order updates are lost.

How do I handle unknown VTEX order statuses during webhook ingestion?

Handle unknown VTEX order statuses, including Status Null, by routing them to a default safe fallback logger path. This ensures end-to-end order processing never crashes or stalls when encountering unexpected lifecycle states.

Does VTEX webhook processing require fetching full order details for fulfillment updates?

VTEX webhook processing requires fetching full order details using GET /api/oms/pvt/orders/{orderId} after validating the event. This retrieves the complete data needed to trigger accurate downstream ERP, WMS, and fulfillment updates.

Why does my VTEX marketplace order hook fail with timeout errors?

VTEX marketplace order hooks fail with timeout errors if the endpoint does not respond with HTTP 200 within 5000ms. Fast acknowledgements are required after validating authentication and queueing the order for asynchronous processing.