Discussing APIs and development related to customers, discounts, and order management.
PriceRules - Syncing of large number of records
Does anyone have any experience syncing large number of PriceRules to Shopify?
We are wishing to sync pricing records from an ERP solution to Shopify where the PriceRules are effectively the customer pricing records in the ERP - one PriceRule in Shopify to every customer/item in the ERP.
There are about 500k records.
Any ideas of how we keep these in Sync? I.e. Particularly handling deletions (i understand we can keep an intermediate change/diff table, but this is a pfaff and can get out of date).
Hi James,
Syncing large of data from an ERP to Shopify can indeed be a complex process. Here are some ideas on how to handle this:
Batching: Shopify's APIs have rate limits, so you'll want to batch your API calls. You can make use of Shopify's Bulk Operations API which is designed to handle large volumes of data.
Webhooks: To keep the data in sync, you can use webhooks to notify your system of any changes made to variant prices. This way, you can update the data in your ERP system in real time as changes occur in Shopify.
Scheduled Sync: Depending on how frequently your data changes, you could also consider scheduling regular syncs between your ERP system and Shopify. This could be done daily, hourly, or even more frequently depending on needs.
Deletions: Handling deletions can be tricky. One approach is to mark deleted records in your ERP system and then reflect these deletions in Shopify during your next sync.
Third-Party Integration Tools: There are some third-party apps available that can help you integrate your ERP system with Shopify. These apps can handle the syncing process for you, and many of them are designed to handle large volumes of data.
Hope these suggestions help!
Liam | Developer Advocate @ Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog
Liam, thanks.