provider-strategy

To add an e-commerce provider for order sync, extend the appropriate SyncRequestStrategyBase class with provider-specific logic, implement the build method with error handling, update provider enums, and wire queue services and processors to dispatch sync requests.

The strategy pattern for ERP and e-commerce integrations isolates provider-specific API logic within standardized strategy classes that extend a base sync request strategy, ensuring consistent data mapping, error handling, and queue processing across multiple connectors like Shopify or VTEX.

Handle order synchronization failures by creating dataNotSynced records that report per-id failures, using an unprocessable flag to distinguish permanent errors from transient ones, and configuring queue retries and deduplication to manage transient failures automatically.

Yes, the integration pattern supports abandoned cart and customer data sync by extending the appropriate SyncRequestStrategyBase for each domain, allowing you to implement provider-specific logic for fetching and mapping data across orders, carts, and customers.

The best way to wire a queue processor for a new provider connector is to update queue constants, create a QueueService, implement a QueueProcessor that instantiates the strategy, and register dispatching through the OrderSyncBuilder with correct priority and deduplication.

A provider integration needs both a queue service and a strategy class because the strategy class isolates provider-specific API calls and data mapping, while the queue service manages job dispatching, processing priority, retries, and deduplication across the synchronization workflow.