AgentBIAgent with Business Intelligence for DTC sites

Back to the knowledge base

OPT-3

Feed refresh latency and incremental sync

Published:2026-11-21Views:0

For downstream consumers, how fresh a feed is matters more than how complete it is. After switching from full exports to incremental pushes, record the last-change time and sync acknowledgement per SKU, and report gaps as a SKU list rather than a single timestamp — an average hides individual stuck fields.

Incremental sync needs a reconciliation endpoint: each day compare price, stock and status fields on a small fixed sample between the feed and the landing page. When a mismatch appears, first determine whether the push failed or the mapping rule changed; do not patch the feed to mask an upstream problem.

This article covers sync latency and reconciliation only; it makes no judgement about stock values in any category or channel. Log sync failures as facts — if the numbers have not moved, record that too, without blame or pressure to change direction.

Official references

2026-11-22