Sync and refresh
Fresh enough for review, calm enough to trust.
Coodra is built for reviewable retail decisions, so sync behavior should be clear about freshness, retries, and missing data.
Fresh enough for review
Coodra does not need every retail signal to update every second to be useful. It needs the data to be fresh enough for the decision being reviewed. Reorder and stock-risk decisions need recent sales and stock movement. Catalog cleanup can tolerate a calmer rhythm.
How sync issues should show up
State
Product behavior
Fresh
Use the signal normally and show the latest known review context.
Delayed
Show freshness and avoid overstating confidence.
Failed
Retry safely, surface the issue, and avoid using stale data as if it were new.
Missing field
Explain which recommendation type is affected.
Review timing matters
A retailer should know whether the queue is based on today, yesterday, or the last successful refresh. The more operational the decision, the more visible freshness should be.