Sync schedule
| Path | When it is refreshed |
|---|---|
| Data API | The moment you send it. Vectors are generated in the background |
| Inbound webhook | The moment your site says “an order changed” (WooCommerce or the signed generic webhook) |
| Data feed | On the schedule you choose (below) |
| Store connection (WooCommerce, Shopify) | First in the setup wizard’s Catalog sync step; after that incrementally by the platform’s scheduled sync. The sync fetches pages one after another with pauses so your site isn’t overloaded; after an error it resumes where it stopped |
| During a call | If the stored order is older than 10 minutes and not in a final state, the assistant reads the live order from the store and refreshes the record |
| Site scan | On the schedule (cron) set on the crawl source; checked every minute |
| Manual upload | Only when you upload |
Data feed schedules
Section titled “Data feed schedules”| Value | Meaning |
|---|---|
15m | Every 15 minutes |
hourly | Every hour |
6h | Every 6 hours |
daily | Every day at the hour you choose (Istanbul time, default 03). A fixed per-feed offset of 0–29 minutes is added so feeds choosing the same hour don’t all start at once |
manual | Only when run by hand |
With interval schedules the first run is immediate and later runs follow the last run by the interval. The scheduler checks for due feeds every minute; the same feed never runs twice at the same time.
Recommended setups
Section titled “Recommended setups”- Platforms with a product XML: a product feed every
15morhourly; orders instantly via the Data API or the inbound webhook. - Large catalogs (>1000 products) with the Data API: push incrementally and deactivate removed products with
DELETE. Usefull=trueonly if you can send the complete list in one request. - Carts:
PUT /api/v1/sepetleron every cart change. An unchanged cart isn’t rewritten, so abandonment is measured correctly.
© 2026 Erusoft