Allegro: return sync now fetches only recent changes
Kiero OMS remembers the last successful Allegro return sync window and fetches changed data with a safe time overlap on later runs.
Allegro: return sync now fetches only recent changes
What changed?
After a successful first run, Kiero OMS remembers the Allegro return sync position. Later runs ask Allegro for returns changed since that point instead of scanning the entire history again. The window overlaps by five minutes so a change saved exactly at the time boundary is not missed.
Benefit
Sync can process less data and refresh new or changed returns faster. Reprocessing the same window should not create a second case because existing returns are updated idempotently.
How to use it
Run Allegro return sync as before. After a successful run, later runs use the saved cursor. The first run and manual force mode continue to use the full or legacy sync path.
Important limitations
The cursor advances only after the window is processed successfully; after an error it stays at the previous position. The database migration and current application code are required. A full live-data production smoke test for incremental sync remains a separate step.

