All Collections
Integrations
Cloud Integration Guide
Cloud Integration Guide

This article outlines how our Cloud Orchestrated Integration work.

Kyran O'Neill avatar
Written by Kyran O'Neill
Updated over a week ago

This guide covers how our Cloud integration works and how you can check the current status of your imports. Connection to ERPs including Unleashed, Cin7 Omni, Cin7 Core, QuickBooks Commerce, Xero and Katana all run on our Cloud Orchestrated Integration.

Cloud Orchestrated imports run continuously, but to limit API call usage and keep the syncs running efficiently, subsequent syncs after the initial import will only queue data updated since the last import.

This means rather than having to re-sync 30,000 Product records including all their Stock records and any Special Pricing which could take a long time. We check the 'last modified' field to get any Product records that have been modified since the last run has finished. This applies to most imported records.

A new sync will start 15 minutes after the previous sync has ended. So for example, if a sync starts at 15:00, and takes 12 minutes to sync all data across, it will finish at 15:12. The subsequent sync will then start at 15:27, and only update any data that has been modified since 15:12. This allows our syncs to run efficiently, keeping data as up to date as possible, and limit the calls made to the APIs so we avoid triggering any API call limitations.

Admin users can see your current sync status in the CRM by going to the System Settings > Integration > Operating Companies and then opening the company they wish to check. Alternatively you can follow this link and click on the company; https://crm.prospect365.com/configure/HomeCurrency

On the bottom right group you can see your ERP integration information, including current sync status (if a sync is running) as well as the end time of your previous sync.


Please note that if you make bulk changes in your ERP, it will take longer for the next sync to complete, as there will be more data to process.

Our integration relies on the modifications made in the ERP updating the ModifiedSince timestamp on the relevant record, if this is not updated the data will not be queued for the sync. Users cannot manually queue data to be synced or force full data syncs, only data that has been updated in the ERP and changed the ModifiedSince timestamp will be queued.


Looking for how to manage your On-Premise Integration? Check out this article here!

Did this answer your question?