Real-Time Product Synchronization
Keep FactFinder NG current with real-time product updates.
Last updated
Was this helpful?
Keep FactFinder NG current with real-time product updates.
Use real-time synchronization for immediate product changes. Configure a scheduled export for routine full catalog refreshes.
Real-time synchronization is currently available for FactFinder NG only. Enable it for each channel mapping in Main Settings.
When disabled, the app ignores Shopify webhooks. No real-time data is synchronized for that mapping.
When enabled, Shopify webhooks queue these events for asynchronous processing:
product/create inserts products and variants.
product/update updates products and adds missing variants.
product/delete removes products and variants.
Run a manual export after large catalog changes. It generates a complete product feed.
FactFinder NG runs only one import at a time. While the manual export is importing, you cannot apply Suggest, ranking, or real-time delta updates.
Shopify does not send product webhooks for some market, catalog, regional availability, or regional price changes. These changes do not update the product timestamp.
Shopify does not send an instant update when you change a price only in a regional market. This applies when the base product price and variant data remain unchanged.
After changing markets, regional availability, or B2B catalogs, run a manual export. It sends a complete product feed and refreshes every affected regional FactFinder channel.
Configure a daily or weekly Scheduled Export to refresh these changes routinely.
The app includes safeguards that prevent unwanted synchronization and reduce unnecessary API calls.
The app synchronizes only products that are active and published to the selected sales channel. It ignores draft and unpublished products.
Mass operations, such as product imports and bulk edits, can trigger hundreds of webhooks.
When the app detects bulk webhook activity, it temporarily pauses Real-Time Sync. It acknowledges the webhooks without processing them.
Temporary failures, such as timeouts, network errors, and HTTP 5xx responses, are retried automatically.
Permanent failures, such as invalid credentials or configuration errors, are logged and stored in a dedicated error table. After the retry limit is reached, failed products move to the sync error queue.
When notifications are configured, permanent failures send an email to the notification address.
The email includes:
Error description
Failure reason
A suggestion to check the configuration
Last updated
Was this helpful?
Was this helpful?

