Feed Updates
There are two types of updates, normal ones, and priority ones. The normal update is performed by a cronjob that runs every 15 minutes on any publication that is not expired, this means it also includes catalogs that haven't been active yet. When the update process runs, the client feed is checked for changes and if any changes are detected, any combination of the below-shown actions is performed.
NOTE: To prevent mid-air collision errors between feed changes and manual edits in Studio, the normal update is skipped should the process detect that the changes would collide with manual edits from Studio. Therefore, it can appear that the feed update will be skipped once and the publication is not updated in this run.
When a new offer is detected on the feed, it gets automatically added to the source and is inserted into the offers-grid that matches the present data on the offer. For further information see how are offers grouped into sections.
When changes to an offer (uses unique offer id to detect updates) are detected, these updates are merged into the existing offer. When performing the merge, it's important to keep in mind that updates from the feed always take priority over manual changes from Studio, and therefore, if a price had been manually edited in Studio, it will still react to real-time updates from the feed once they occur.
IMPORTANT NOTE: Since feed changes overwrite manual edits from Studio, it's important to make any changes to the offers images to the actual offer.images property and not to the image on the product as this would be overwritten once the feed changes or the order of products within the offer changes for some reason.
When an offer is deleted from the client's feed, the deleting is registered on the next completed update run and the offer is automatically removed from any occurrence within the Incito. This means that any manual changes are lost and the offer will be added as an entirely new product when it reappears on the feed.
