



Shopify Integration
Manage your product data easily and transparent in PIM.RED.
PIM.RED is synchronised with Shopify in real time.
Shopify v2 is an upgrade in terms of reliability and scalability. It reduces API traffic, ensures synchronisation quality even when approaching Shopify’s rate limits, and offers better operational control for production use.
In v1, synchronising a product with multiple variants often triggered repeated product/variant cycles. A practical example from current workflows: a product with 6 variants could end up generating more than 12 Shopify API requests.<zIn v2, the same core synchronisation of product and variants is consolidated and typically involves around 2 requests:
=> Result: In this scenario, typically around 80% fewer requests.
Bulk and multi-data updates are noticeably faster in practice, as each product change requires far fewer Shopify calls. Synchronisation is queue-based and deduplicated, so rapid repeated edits do not cause unnecessary duplication of effort.
=> Result: improved responsiveness for teams that edit many products throughout the day.
The Excel import starts immediately in the background, allowing users to continue working without having to wait for the full run to complete. Import processing is batch-oriented and handles delayed variant synchronisation with repeat rounds. Combined with a lower Shopify request volume and rate limit management, imports are more stable for larger files.
v2 tracks the remaining Shopify API capacity and slows down the process before the limit is reached.
This prevents the ‘half-synchronised’ situations that occur when limits are reached during busy synchronisation windows. v2 retries in the event of temporary API errors and has a protective fail-safe behaviour in the event of repeated failures.
The v2 queue is deduplicated for pending jobs, ensuring that rapid, repeated save operations do not flood Shopify with redundant calls.
It features clear retry behaviour and dead-letter handling for failed jobs. The synchronisation status is consistently updated (in queue, synchronising, synchronised, failed), enabling clearer monitoring.
Settings can be reloaded at runtime (no need to restart the process after changes to tokens/shops).
A dedicated endpoint for schema synchronisation ensures that fields and language environments match Shopify’s definitions.
Webhooks are validated and processed via the queue flow, which improves stability under load.
The synchronisation status is visible in the user interface with clear status labels and filter options, making operational tracking easier.
Teams can immediately see whether an item is queued, currently being synchronised, completed or has failed.
This enables faster daily checks during campaigns, bulk edits and imports.
Failed items are easier to identify and prioritise, allowing for quicker follow-up.
v2 uses new module IDs (shopify_v2_products, shopify_v2_variants, shopify_v2_categories).
Existing v1 data should be migrated before going live.
The v2 webhook endpoint is /api/rest/custom/shopify-v2/webhooks.
Shopify webhook subscriptions must be updated to this endpoint during migration.
v2 is designed for queue-based processing (near real-time), not for inline blocking of synchronisation.
For customers, this means more stable synchronisation behaviour during high data volumes, although minor delays may occur in the queue.
Shopify v2 provides a more secure and scalable foundation: fewer API calls, faster workflows with multiple data sources, more stable Excel imports, clear visibility of synchronisation status, better behaviour when approaching limits, and more predictable synchronisation results. For teams migrating from v1, the migration is straightforward and should include data/module migration as well as updating the webhook endpoint.
