provider-strategy

What problem does it solve?

Integrating a new e-commerce or ERP provider requires implementing provider-specific API calls, consistent error handling, and wiring job queuing and processing across multiple layers; this Skill documents a repeatable pattern and checklist to avoid missed steps and fragile integrations.

Core Features & Use Cases

• Standardized strategy classes: Shows how to extend the appropriate SyncRequestStrategyBase for orders, abandoned carts, customers, and similar domains so provider-specific logic stays isolated.
• End-to-end wiring checklist: Explains enum updates, queue and job constants, QueueService creation, OrderSyncBuilder dispatching, and QueueProcessor implementation that instantiates the strategy.
• Error handling guidance: Describes how to build dataNotSynced records, use the unprocessable flag for permanent vs transient failures, and ensure retries/deduplication.
• Use case: Add a Shopify or Yampi connector that fetches provider orders, maps them to sync requests, reports per-id failures, and enqueues processing with the correct priority and deduplication.

Quick Start

Create a new provider strategy for your-provider by extending the correct SyncRequestStrategyBase, implement build(management, ids?) with try/catch and unprocessable handling, add the provider to the enum, create queue service and processor, and register all entries following the checklist.